Page History

...

1. Only Root Admin can dedicate zone, pod, cluster or host to specific domain or an account.
2. Only Root admin can implicitly dedicate a zone, pod, cluster or a host.
3. If a user does not belong to a domain which has dedicated resources, he cannot access the pod, cluster or host dedicated to that domain/account.
4. Users belonging to domain/account having dedicated resources, can access them but should not be allowed to modify.
5. 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
6. Only Root Admin can add a service offering with "isdedicated" option enabled. 
7. User/admin can enable the DeplovVM dedication flag. 

Use Cases: 

VM Deployment

The following figure graphically illustrates the allocation of hosts for VM deployment.

Host 1 is explicitly dedicated to domain D1, Host 2 is implicitly dedicated, and Host 3 is a shared host. 

SO is the Service Offering Dedication Flag and DVM is the DeployVM Dedication flag.

Image Added
For Domain D1:

Use Case 1:  User U1 from account A1,  deploys a virtual machine VM1 with SO=ON,
                    Host 2 is chosen from the pool of implicitly dedicated resources (In this case, only Host 2 is implicitly dedicated),  Implicitly Dedicated "Host 2" is now dedicated to account  A1
Use Case 2:  User U1 from Account A1, deploys a virtual machine VM2 with DVM=ON,  
                    Host 1 is chosen form the pool of explicitly dedicated resources (In this case, only Host 1 is explicitly dedicated)
Use Case 3: User U1 from account A1,  deploys a virtual machine VM3 without any flag ON,
                   Host 3  is chosen from the shared pool,  (In this case, only Host 3 is a shared Host)
Use Case 4: User U3 from Account A2,   deploys a virtual machine VM1 with SO=ON,
                   Request Failed, No Host available
Use Case 5: User U4 from account A2,  deploys a virtual machine VM2 with DVM=ON, 
                   Host 1 is chosen form the pool of explicitly dedicated resources

For Domain D2
Use Case 6:  User U5 from account A3,  deploys a virtual machine VM1 with SO=ON,
                    Request Failed, No Host available
Use Case 7:  User U5 from Account A3, deploys a virtual machine VM2 with DVM=ON, 
                    Request Failed, No Host available
Use Case 8:  User U1 from account A1,  deploys a virtual machine VM3 without any flag ON,                    Host 3  is chosen from the shared pool

1. If dedicated resources get exhausted for a domain/account, VM deployment will not fail unless implicit resources has no free empty host, provided  SO Implicit dedication flag: ON.
2. VMs that belong to two different offerings can be on the same host as long as they belong to the same account and host is implicitly dedicated . For e.g. If an instance is deployed by account user and : 
            a. If that account has dedicated resources, service offering flag "isdedicated" checked, then VM will be deployed on the dedicated host having VMs of same account or on the host which is empty.
            b. If that account has NO dedicated resources, service offering flag "isdedicated" checked then VM will be deployed on the host which is empty and that host will become dedicated to this account.
3. The dedicated VM of other accounts (e.g. A2 or A3 ) of same domain or other domain, cannot use above host, but can use an empty host or host having vms of same account(A2 or A3). 
4. If the service offering flag if OFF, the VM  will be deployed as CloudStack is doing now but should not use the host marked "dedicated for domain/account x".
5. If no such host exists, VM operation should fail. 
6. If the dedication is removed and host has NO dedicated VMs, then host will be available for all the accounts.

Dedicating resources to Domain/Account

...

1. Deleting an account will delete all the VMs, snapshots, templates, etc. of that account, and also removes the dedication of host, cluster or pod to that account.
2. Deleting a domain, will remove the dedication from the hosts, clusters or pods (if dedicated).   

VM Deployment

1. If dedicated resources get exhausted for a domain/account, VM deployment will not fail unless implicit resources has no free empty host, provided  SO Implicit dedication flag: ON.
2. VMs that belong to two different offerings can be on the same host as long as they belong to the same account and host is implicitly dedicated . For e.g. If an instance is deployed by account user and : 
            a. If that account has dedicated resources, service offering flag "isdedicated" checked, then VM will be deployed on the dedicated host having VMs of same account or on the host which is empty.
            b. If that account has NO dedicated resources, service offering flag "isdedicated" checked then VM will be deployed on the host which is empty and that host will become dedicated to this account.The dedicated VM of other accounts (e.g. A2 or A3 ) of same domain or other domain, cannot use above host, but can use an empty host or host having vms of same account(A2 or A3).  
3. If the service offering flag if OFF, the VM  will be deployed as CloudStack is doing now but should not use the host marked "dedicated for domain/account x".
4. If no such host exists, VM operation should fail. 
5. If the dedication is removed and host has NO dedicated VMs, then host will be available for all the accounts.
6. The following Figure graphically illustrates the allocation of hosts for VM deployment. Host 1 is explicitly dedicated to domain D1, Host 2 is implicitly dedicated, and Host 3 is a shared host. 
   Image Removed

Host Tags with isDedicated flag and dedicated resources

...