Page History

...

-          Root Admins must be able to dedicate a zone, pod or cluster or host to a specific domain or account

-          Alternatively, a host or cluster or pod or zone can be "implicity" dedicated - this flag's description will be clarified below

-          A service offering can optionally have an "implictly" dedicated flag on - this flag's 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

-          When deploying a VM, end user can optionally specify it to be placed on a dedicated resource

-          Only VMs that belong to the domain/sub-domain accounts should be deployed/started on the dedicated (implict and explicit) hosts under the zone/pod/cluster/host

-          Only VMs that are requested with dedication flag can use those dedicated resources

-          If during deploy or start of a VM that corresponds to an offering with dedication on, and 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

-           if a "non-dedicated" VM is requested and there is no space available from non-dedicated area in the cloud, the request must fail, even if there is space in the dedicated area

-          Only VMs that are requested with dedication flag (implicit or explicit) can use those dedicated resources

-          admin must be able to live migrate -          Migration of such a VM to a resource not owned by the account must fail, but an alert must be generated

-          In general, CloudStack must detect and provide warning of inappropriate location for a VM (such as a dedicated VM on a non-dedicated host)

-          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

...

...