After installing VMware vCloud Director a couple of default roles are created. One of these roles is the “Organization Administrator”. An Organization Administrator finishes setting up the organization by adding members and setting policies and preferences (from the vCloud Director User’s Guide). Actually, an Organization Administrator can configure everything within the boundaries of the organization: users, networks, resource usage and the vApps / VMs.
An Organization Administrator can also set policies, e.g. the storage- and vApp template lease: these setting determines how long a vApp is available before deleted. Another policy is the quotas policy, there are two available:
- Running VM quota: Number of running VMs running concurrently within the organization;
- Stored VM quota: The number of stored VMs within the organization;
I can imagine that in some situations you don’t want you Organization Administrator to determine how many VMs can run concurrently within the organization (s)he’s responsible for. It’s ok that the Org Admin decides how the available resources are used, but the number of running VMs is related to the required quantity of vCloud Director licenses: The more running VMs you have, the more licenses you need…Is this what you want?
Can we disallow an Organization Administrator to change these policies? Yes we can…by login in as a cloud administrator and changing the Org Admin default role:
Deselect the “Edit Quotas Policy” and you’re all set! (As an alternative you can create your own custom Org Admin role) The result is that the Org Admin cannot configure the quotas anymore, they are only set by the cloud administrator…
What are your ideas? Do you want to allow an Org Admin to set the maximum number of running VMs? Why or…why not?