Revision b0b6d5ab
b/docs/upgrade/upgrade-0.16.rst | ||
---|---|---|
11 | 11 |
|
12 | 12 |
2. Upgrade packages, migrate the databases and configure settings. |
13 | 13 |
|
14 |
3. __placeholder__
|
|
14 |
3. Inspect and adjust resource limits.
|
|
15 | 15 |
|
16 | 16 |
4. Bring up all services. |
17 | 17 |
|
... | ... | |
108 | 108 |
pithos-host$ pithos-migrate upgrade head |
109 | 109 |
|
110 | 110 |
|
111 |
3. __placeholder__
|
|
112 |
================== |
|
111 |
3. Inspect and adjust resource limits
|
|
112 |
=====================================
|
|
113 | 113 |
|
114 |
Synnefo 0.16 brings significant changes at the project mechanism. Projects |
|
115 |
are now viewed as a source of finite resources, instead of a means to |
|
116 |
accumulate quota. They are the single source of resources, and quota are now |
|
117 |
managed at a project/member level. |
|
118 |
|
|
119 |
System-provided base quota are now handled through special purpose |
|
120 |
user-specific *base projects*, identified with the same UUID as the user. |
|
121 |
These have been created during the database migration process. They are |
|
122 |
included in the project listing with:: |
|
123 |
|
|
124 |
snf-manage project-list --base-projects |
|
125 |
|
|
126 |
All projects must specify quota limits for all registered resources. Default |
|
127 |
values have been set for all resources, listed with:: |
|
128 |
|
|
129 |
astakos-host$ snf-manage resource-list |
|
130 |
|
|
131 |
Column `base_default` (previously known as `default_quota`) provides the |
|
132 |
skeleton for the quota limits of user-specific base projects. Column |
|
133 |
`project_default` is new and acts as skeleton for `applied` (non-base) |
|
134 |
projects (i.e., for resources not specified in a project application). |
|
135 |
Project defaults have been initialized during migration based on the base |
|
136 |
default values: they have been set to `inf` if `base_default` is also `inf`, |
|
137 |
otherwise set to zero. |
|
138 |
|
|
139 |
This default, affecting all future projects, can be modified with:: |
|
140 |
|
|
141 |
astakos-host$ snf-manage resource-modify <name> --project-default <value> |
|
142 |
|
|
143 |
Till now a project definition contained one quota limit per resource: the |
|
144 |
maximum that a member can get from the project. A new limit is introduced: |
|
145 |
the grand maximum a project can provide to its members. This new project |
|
146 |
limit is initialized during migration as `max members * member limit` (if |
|
147 |
`max members` is not set, the double of current active members is assumed). |
|
148 |
|
|
149 |
Existing projects can now be modified directly through the command line. In |
|
150 |
order to change a project's resource limits, run:: |
|
151 |
|
|
152 |
astakos-host$ snf-manage project-modify <project_uuid> --limit <resource_name> <member_limit> <project_limit> |
|
153 |
|
|
154 |
With the new mechanism, when a new resource is allocated (e.g., a VM or a |
|
155 |
Pithos container is created), it is also associated with a project besides |
|
156 |
its owner. The migration process has associated existing resources with |
|
157 |
their owner's base project. Note that users who had made use of projects to |
|
158 |
increase their quota may end up overlimit on some resources of their base |
|
159 |
projects and will need to *reassign* some of their reserved resources to |
|
160 |
another project in order to overcome this restriction. |
|
114 | 161 |
|
115 | 162 |
4. Bring all services up |
116 | 163 |
======================== |
Also available in: Unified diff