You can define parent-child relationships to help manage quotas. Quotas that are assigned to a parent group are automatically assigned to all related child groups.
==============
When you create a group, by default, it cannot be the owner of an object. To create or modify an existing group to be able to be the owner of an object, use the can_own attribute with the corresponding group management command. This is important because groups can be owners of objects that are subject to quotas. Setting the can_own attribute on a group can be used to prevent users from avoiding their quotas by changing the owner of an object to themselves or a group of which they are member (either directly or through another group they are member of) that also has the can_own attribute set.
==============
Using the sample groups created in the previous sections, the following procedure describes how to organize the WarnGroup and ISVAdvancedDevGroup groups as children of the DevelopmentPackages parent to maintain quota entries and users.
Follow these steps:
quota info WarnGroup quota info ISVAdvancedDevGroup
group create DevelopmentPackages quota modify WarnGroup bw=4G parent=DevelopmentPackages quota modify ISVAdvancedDevGroup bw=4G parent=DevelopmentPackages
quota list
The quota list appears:
Principal Warn / Burst CPU MEM BW DISK Description ------------------------------------------------------------------------------------------- DevelopmentPackages - / - - - - - \_ ISVAdvancedDevGroup - / 50% 4.00 4.00 GB 4.00 Gbps 500.00 GB Burst Quota \_ WarnGroup 75% / - 4.00 4.00 GB 4.00 Gbps 500.00 GB Warn Quota
Note: When a quota has a parent, all quotas in the quota hierarchy are enforced.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|