Page History

...

• Root Admins must be able to explicitly dedicate a zone, pod or cluster or host to a specific domain or account
• When deploying a VM, end user can optionally specify it to be placed on a dedicated resource
• Explicit dedication can be for a domain or account and can be a zone/pod/cluster/host; for example, if a cluster is explicitly dedicated to a domain, any account in that domain can share the hosts (as long as they DeployVM with dedication flag ondeploy a VM requesting dedication), but sharing is limited to accounts within that domain only. As another example, if a cluster is explicitly dedicated to an account, only that account’s VM can use those hosts in the dedicated cluster (as long as they DeployVM with dedication flag ondeploy a VM requesting dedication).
• AlternativelyOptionally, a host or cluster or pod or zone can be "implicitly" dedicated - this flag's description will be clarified below
• Strict Implicit dedication, when requested, meansImplicit dedication can be for a zone/pod/cluster/host, but not associated with any domain or account; however, during VM deployment, once chosen, a host will not be shared across multiple accounts – as an example, here is a reason: for deployment of certain types of applications, such as desktops, due to licensing reasons, no host can be shared between different accounts. However, pre-allocating specific (number of) hosts to each account is not desired as this will create forecasting issues/sub-optimal utilizationA service offering can optionally have an "implicitly" dedicated flag on - this flag's description will be clarified below in the table
• Preferred Implicit Dedication, when requested, means VM would prefer to share a host with another VM of this account, if possible, but could be placed with another account's VM, if needed

• Admin must be able to live migrate of such a VM to a resource not owned by the account, but an alert must be generated

• Fail the request if DeployVM dedication Flag is specified and SO has implicit dedication ON
• When you search implicitly dedicated “area” for a host (second table below), if there is already a host for this account, pick it up (instead of finding a new one every time)
• When you delete the last VM from a host in the implicit area, remove the association of the account with the host (i.e. make it implicit-free host as before)

• Non-requirement: Must be able to dedicate a primary storage to an account
• Non-requirement: for the domain/sub-domain admins to manage the resource - the root admin will remain the owner of the resources
• Non-requirement: In general, CloudStack must detect and provide warning of inappropriate location for a VM (such as a dedicated VM on a non-dedicated host) - this is not a specific requirement of this feature, but more of a generic requirement