Background: Currently, CloudStack allows cloud admins to dedicate a zone to a tenant. While this is useful in certain scenarios, for several end-users this is a very expensive offering. This feature is to enable more economical options, but still preserve several of the benefits of the private zone offering. This feature allows admins to dedicate resources to a specific tenant that needs private infrastructure for additional security or performance guarantees. This feature also allows admins to dedicate resources to resellers. Re-sellers in turn can ‘resell’ the infrastructure to their customers.
Requirements:
- Root Admins must be able to dedicate a zone, pod or cluster or host to a specific domain or account
- A compute service offering could let an end-user select if dedication is required or not
- Any zone can have “implicit” dedication flag on or off – this flag’s description will be clarified below
- Only VMs that belong to the domain/sub-domain accounts should be deployed/started on the hosts under the zone/pod/cluster/host
- Only VMs that are requested with dedication flag can use those dedicated resources
- If during a VM deploy or start operation, there are no available resources among the hosts dedicated to the account then CloudStack should fail the operation. Appropriate error message should be logged and event generated
- Optionally, a global setting can allow the VM to be deployed on a parent domain/sub-domain if there is no space available in the account/sub-domain/domain's dedicated resources
- Optionally, if implicit dedication flag is set for a zone, a new, unused host is found for fulfilling this request and added to the list of "dedicated" resource for this account and will be used for future fulfillment
- Migration of a VM to a resource not owned by the account must fail
- Must be able to dedicate a primary storage to an account
- at this time, there is no requirement for the domain/sub-domain admins to manage the resource - the root admin will remain the owner of the resources
|
Service Offering requested with dedication ON |
Service Offering requested with dedication OFF |
|---|---|---|
Account (or sub-domain or domain) has dedicated host/cluster/pod/Zone AND Implicit dedication flag ON |
Place VM in a dedicated area if space available; if no space in dedicated area, find a new free host and place VM and make the host part of the dedicated host for this account/sub-domain/domain |
Place VM in a non-dedicated area |
Account (or sub-domain or domain) has NO dedicated host/cluster/pod/Zone AND Implicit dedication flag ON |
find a new free host and place VM and make the host part of the dedicated host for this account/sub-domain/domain to be used for future requests |
Place VM in a non-dedicated area |
Account (or sub-domain or domain) has dedicated host/cluster/pod/Zone AND Implicit dedication flag OFF |
Place VM in a dedicated area if space is available. if no space available in dedicated area, FAIL request |
Place VM in a non-dedicated area |
Account (or sub-domain or domain) has NO dedicated host/cluster/pod/Zone AND Implicit dedication flag OFF |
Fail the request |
Place VM in a non-dedicated area |