Revision 111adca0 docs/design/resource-pool-projects.rst

b/docs/design/resource-pool-projects.rst
120 120
  cyclades.vm   project:uuid   None           5       1
121 121
  cyclades.vm   user:uuid      project:uuid   5       1
122 122

  
123
System default base quota
124
-------------------------
123
System default quota
124
--------------------
125 125

  
126 126
Each resource registered in the system is assigned a default quota limit.
127
A newly-activated user is given these limits as their base quota. Up to now,
128
a change in a default quota limit propagates to all users' base quota
129
(except if they have been customized). Since all users' base quota will be
130
controlled through their base projects, the default behavior of
131
``resource-modify`` will change to affect only future users (i.e.
132
construction of new base projects). However, new option
133
``--update-existing-base-projects`` will allow setting the limits to
134
existing base projects, too. This is useful, for example, when setting a
135
newly registered resource.
127
A newly-activated user is given these limits as their base quota. This is
128
till now done by copying the default limits as user's entries in
129
AstakosUserQuota. Default limits will from now on be copied into the base
130
project's resource definitions.
131

  
132
Conventional projects are created through a project application, which
133
may not specify limits for all resources registered in the system. In
134
fact, it may even be impossible to specify a resource, if it is set
135
``api_visible=False``. We have to somehow specify these limits. Defaulting
136
to zero is not appropriate: if we don't want to control a resource, we
137
would like it set to infinite. We thus need an extra skeleton, like the
138
one specifying the default base quota, in order to fill in missing limits
139
for conventional projects. It will be controled by a new option
140
``--project-default`` of command ``resource-modify``.
136 141

  
137 142
Private projects
138 143
----------------
......
392 397
  ------------------------
393 398
  cyclades.vm 100    50
394 399

  
395
``snf-manage quota`` will be removed; checking the integrity of the
396
Quotaholder will be provided by a new command ``reconcile-quota``.
397

  
398 400
A new command ``snf-manage project-modify`` will automate the process of
399 401
applying/approving applications in order to modify some project settings,
400 402
such as the quota limits.
......
402 404
Currently, the administrator can change the user base quota with:
403 405
``snf-manage user-modify <id> --set-base-quota <resource> <capacity>``.
404 406
This will be removed in favor of the ``project-modify`` command, so that all
405
quota are handled in a uniform way.
407
quota are handled in a uniform way. Similar to ``user-modify --all``,
408
``project-modify`` will get options ``--all-base`` and ``--all-non-base`` to
409
allow updating quota in bulk.
406 410

  
407 411
Migration steps
408 412
===============

Also available in: Unified diff