...
3. Shared Resources: All the non-dedicated resources.
4. SO dedication flag: a new Parameter in Service Offering. if ON, Use Implicitly Dedicated Resources
5. DVM dedication flag: a new Parameter in deployVirtualMachine API, if ON, VM is deployed on explicitly dedicated resources
The above parameters in 4 and 5 have been removed as per discussion.
For Implicit Dedication,
14. Strict Implicit dedication, a new type in Affinity Groups will indicate deployment on : VM with this requirement will be deployed on the host having VMs of same account.
25. Preferred Implicit dedication, a new type in Affinity Groups will indicate deployment : VM with this requirement will be deployed on host having VMs of same account if possible, otherwise can be place in shared resources
For Explicit Dedication,
36. Explicit dedication, a new type will be added in Affinity Groups which will indicate deployment on explicitly dedicated resources.
...
| VM requesting dedication | VM NOT requesting dedication |
Explicitly Dedicated Resources | Pick from Explicitly dedicated else fail | Pick from shared resources else fail |
NO Explicitly Dedicated Resources | Fail the request | Pick from shared resources else failresources else fail |
...
Host 1 is explicitly dedicated to domain D1, Host 2 is implicitly dedicated, and Host 3 is a shared host. 2 is implicitly dedicated, and Host 3 is a shared host.
Note: In this feature, we are assuming that host can be implicitly dedicated upfront.
SID-VM : VM with Strict Implicit Dedication required
...
ED-VM : VM with Explicit Dedication required
VM : VM with no dedication required
Use Case 1: User U3 of Account A2 (Red color), deploys a virtual machine VM1 with SID affinity type,
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 4: User U1 of Account A1 (Green color), deploys a virtual machine VM1 with SID affinity type,
Request Failed, No Host available
...
Use Case 6: User U5 of Account A3 (Blue Color), deploys a virtual machine VM1 with SID affinity type,
Request Failed, No Host available
...
Use Case 9: User U3 of Account A2, deploys a VM with PID affinity type.
Host 2 is selected, VM with SID is OK if VM come from the same account
...
Use Case 11: User U5 of Account A3 deploys a VM with PID affinity type.
Search for Host having VMs of same account. If not available can go to shared host.
...
...
Case 2: Deploy VM for account B with explicit dedication, processors should set the scope of plan to Zone Z since the dedicated hosts are in Pod P1 and P2 , with parent being the zone itself. Also set the Cluster C2 in avoid set.
Default Processor Existing Planners and Allocators will be modified to make sure that dedicated resources are not picked, when dedication is not NOT required.
...
...
...
...