Revision ef5d2c1c
b/Changelog | ||
---|---|---|
6 | 6 |
Since v0.13 most of the Synnefo components have been merged into a single |
7 | 7 |
repository and have aligned versions. |
8 | 8 |
|
9 |
v0.15next |
|
10 |
============= |
|
11 |
|
|
12 |
Released: UNRELEASED |
|
13 |
|
|
14 |
Synnefo-wide |
|
15 |
------------ |
|
16 |
|
|
17 |
* Replace accumulative projects with pool projects: |
|
18 |
|
|
19 |
* Projects are now viewed as a source of finite resources. A member can |
|
20 |
reserve a part of these resources up to a specified limit. |
|
21 |
|
|
22 |
* Base quota are now offered through a special purpose user-specific base |
|
23 |
project, identified with the same UUID as the user. |
|
24 |
|
|
25 |
* Each actual resource (Cyclades VM, network, floating IP and Pithos |
|
26 |
container) is now also associated with a project besides the owner. |
|
27 |
|
|
28 |
* In resource creation, project defaults to the user-specific base |
|
29 |
project, if not specified otherwise. It is also possible to change the |
|
30 |
project assignment of an existing resource. |
|
31 |
|
|
32 |
* All existing resources have been assigned to the respective |
|
33 |
user-specific base projects. |
|
34 |
|
|
35 |
Astakos |
|
36 |
------- |
|
37 |
|
|
38 |
* Decouple projects from applications: |
|
39 |
|
|
40 |
* Support project creation (by the system) and modification (by a |
|
41 |
privileged user) without the need to submit/approve an application. |
|
42 |
|
|
43 |
* View applications as modifications. When a project is uninitialized |
|
44 |
(e.g. an application for a new project is pending), no further |
|
45 |
modification is allowed. |
|
46 |
|
|
47 |
* Applications are removed from the API. A project's last application is |
|
48 |
only accessible as part of the project details. |
|
49 |
|
|
50 |
* Decouple project state from application state; they can be combined by |
|
51 |
an API client, if needed. |
|
52 |
|
|
53 |
* Changes concerning quota and pool projects: |
|
54 |
|
|
55 |
* A project must provide limits for all registered resources. On project |
|
56 |
activation, resources missing are automatically completed using a |
|
57 |
skeleton. |
|
58 |
|
|
59 |
* Field `uplimit' of registed resources is exposed as `base_default' and |
|
60 |
provide the skeleton for user-specific base projects. A new field |
|
61 |
`project_default' is introduce to act as a skeleton for conventional |
|
62 |
projects. |
|
63 |
|
|
64 |
* The quotaholder now also records project quota besides user quota. The |
|
65 |
two types of holders are distinguished with a prefix: `user:' and |
|
66 |
`project:'. |
|
67 |
|
|
68 |
* The quota API is extended to make project quota available. |
|
69 |
|
|
70 |
* Projects can be set `private', making it accessible only to its owner and |
|
71 |
members. |
|
72 |
|
|
9 | 73 |
v0.14next |
10 | 74 |
========= |
11 | 75 |
|
Also available in: Unified diff