Page History

...

SID-VM  : VM with Strict Implicit Dedication required  

PID-VM  : VM with Preferred Implicit Dedication  

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,

                    Host 2 is chosen from the shared host as it is emplty. "Host 2" is now dedicated to account  A2

Use Case 2:  User U1 of Account A1, deploys a virtual machine VM2 with ED affinity type ,  

                    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 of Account A1,  deploys a virtual machine VM3 with NO dedication,

                   Host 3  is chosen from the shared pool,  (In this case, only Host 3 is a shared Host)

Use Case 4: User U1 of Account A1 (Green color), deploys a virtual machine VM1 with  SID,

                   Request Failed, No Host available

Use Case 5: User U4 of account A2,  deploys a virtual machine VM2 with  ED affinity type,

                   Host 1 is chosen form the pool of explicitly dedicated resources

Use Case 6:  User U5 of Account A3 (Blue Color),  deploys a virtual machine VM1 with SID,

                    Request Failed, No Host available

Use Case 7:  User U5 of Account A3, deploys a virtual machine VM2 with SID, 

                    Request Failed, No Host available.

Use Case 8:  User U5 of Account A3, deploys a virtual machine VM3 with NO Dedication, 

                    Host 3 is selected.

Use Case 9: User U3 of Account A2, deploys a VM with PID.

                   Host 2 is selected, VM with SID is OK if VM come from the same account

Use Case 10:User U3 of Account A2, deploys a VM with NO dedication .

                    Host2/Host3 can be chosen.

Use Case 11: User U5 of Account A3 deploys a VM with PID.

                    Search for Host having VMs of same account. If not available can go to shared host.

                     Host 3 is selected. 

Use Case 12: Once All the VMs in Host 2 is deleted, Host will get available for all users.

Use Case 13: Host 1 will remain dedicated to Domain D1 unless root admin changes dedication of this host.

Host Tags with Explicit and Implicit Dedication

1. If Host Tag is provided and Implicit Dedication is required, Host which is tagged as well as implicitly dedicated, will be allocated. If not found, fail the request. 
2. If host tag is provided and NO dedication is required, Host which is tagged but not implicitly or explicitly dedicated, will be allocated.  If not found, fail the request. 
3. If host tag is provided and Explicit dedication is required, Host which is tagged as well as explicitly dedicated, will be allocated.  If not found, fail the request. 

Migration of VMs

Migration is a Root Admin functionality, migrating VMs across dedicated hosts generates Alerts.

The following scenarios generate alerts:

Explicit Dedication :

VM is being migrated between :

• dedicated source host to non-dedicated host.
• non-dedicated source host to dedicated host.
• source host and destination hosts are dedicated to different accounts/domains.

Implicit Dedication :

• VM is deployed using strict implicit planner and moved to a destination host which has VMs of other account or VMs deployed using planner other than strict.
• VM is deployed using preferred implicit planner and moved to a destination host which has VM of other account or VMs deployed using a service offering other than ImplicitDedication 
• VM is not deployed using ImplicitDedication but moved between dedicated hosts. 

Deletion of Account/domain

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).  

Architecture and Design description

This feature will come as a separate plugin which will use the PluggableService to add the DedicatedResources feature APIs into CloudStack, the DedicatedResourceManager will be responsible for thread scheduling and the ExplicitDedicationProcessor will implement AffinityGroupProcessor adapter and  ImplicitDedicationPlanner will implement a deployment planner interface.

Panel

Ways to achieve Dedication: To Use Explicit Dedication: Create an Affinity Group of type "explicit dedication". Use that AG to deploy a VMRoot Admin dedicates the resource to the account/domain, CloudStack will internally create the affinity group of type ExplicitDedication. Use this affinity group while deploying the vm. To Use Implicit Dedication: Create a Service Offering with Implicit dedication planner. Choose a type: 'strict' or 'preferred'. Use that SO to deploy a VM.

Explicit Dedication Design

1. New Admin APIs to dedicate Zones/Pods/Clusters/Hosts to a domain or account (these APIs will come in a separate plugin)
2. list affinity types: Add a new type: explicit dedicationUser should be able to create affinity groups based on the explicit dedication type
3. Affinity group of type ExplicitDedication is created when the root admin dedicates a resource to any  account/domain.
4. User can associate above affinity group to VM during deployment.
5. A new ExplicitDedicationProcessor plugin that implements AffinityGroupProcessor adapter, will set deployment plan scope to the correct resource level (For AffinityGroupProcessor adapter see: https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS+-+Affinity-Anti-affinity+groups).
6. The Deployment Planning Manager will do the following:
   1.  Processors: Call the ExplicitDedicationProcessor to process the dedication request based on the explicitly dedicated resources for the user.
   2.  Planners: Call Deployment Planner to drill down to the right set of clusters to look for placement based on explicitly dedicated clusters/hosts inside them. 
   3.  Allocators: Call Allocators to match the requirement to explicit dedication.

New Addition: ExplicitDedicationProcessor

This will implement the process to set the scope of deployment plan to the correct resource level for planners to look into. This processor will implement AffinityGroupProcessor adapter.

Non-dedicated Resources will be added in Avoid List.

For Example:

              Zone Z has Pods P1,  P2.

              Pod P1 has Clusters C1, C2  and P2 has Cluster C3

              Clusters

              C1 -> h1 (dedicated A), h2 (dedicated B)

              C2 -> h3 (dedicated A)

              C3 -> h4, h5(dedicated B) 

Case 1: Deploy VM  for account A with explicit dedication, processors should set the scope of plan to Pod P1 since both dedicated hosts are in Pod P1 even if in different clusters. Also set the Pod P2 in avoid set

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.

System VMs and Virtual Routers:

System VMs and Virtual Router do not adhere to explicit dedication as they are owned by the system account and can be deployed on any host.

Implicit Dedication Design

1. Admin should be able to choose a planner while creating a Service Offering.
2. In Service Offering the list of planners will be shown, which include the new planner for Implicit Dedication: ImplicitDedicationPlanner
3. Along with selecting a planner, admin may choose to configure the planner being used by the service offering. This is done by passing name-value parameters to the createServiceOffering command.
4. The name-value parameters may be used by the planner when the service offering is selected for deploying the vm.
5. Admin can set the name-value parameter for 
   1. Strict Implicit Dedication as  "ImplicitDedicationMode = Strict" 
   2. Preferred Implicit Dedication as "ImplicitDedicationMode = Preferred"
6. These parameters will get stored in reference to the service_offering_id.
7. ImplicitDedicationPlanner takes the above parameters as input and  set the scope of the plan of the VM to choose implicitly dedicated resources.

New Planner: ImplicitDedicationPlanner

ImplicitDedicationPlanner will extend firstfitplanner and search only in the dedicated resources.

Updated API: createServiceOffering

createServiceOffering API will take in name-value parameters. In the api they can be passed by specifing the 'serviceofferingdetails' parameter. For implicit dedication the valid name-value pairs are

1. Strict Implicit Dedication as "ImplicitDedicationMode = Strict"
2. Preferred Implicit Dedication as "ImplicitDedicationMode = Preferred"

   Code Block
   title Example
   For example: A service offering may be created as follows using the api. http://<ip>:8080/client/api?command=createServiceOffering&serviceofferingdetails[0].ImplicitDedicationMode=Preffered&issystem=false&name=Preferred&displaytext=Preferred&storageType=shared&cpuNumber=1&cpuSpeed=500&memory=512&deploymentplanner=ImplicitDedicationPlanner&offerha=false&limitcpuuse=false&isvolatile=false

Change in the Existing Private Zone functionality:

Zones can be dedicated to domains while creation. Users in that domain can deployVm only in that dedicated zone.

Change:

1. Zones dedicated to a domain at the creation level will be considered as explicit dedication of zones. The functionality will be redirected to explicit dedication affinity group when VM (with explicit dedication) is deployed.
2. All the Zones will be listed, and if explicit type affinity group is provided, deployment will only happen if any of the resource in that zone will be dedicated to that user's account or domain.
   

Private zone functionality is now deprecated. To achieve the functionality of private zone, dedicate the zone at zone creation time.

System VMs and Virtual Router:

The presence of system vms and virtual routers on a host makes it unsuitable for strict implicit dedication, as the planner cannot implicitly dedicate the host since it has vms of another account (the default system account).

However the same host could be used for implicit dedication in preferred mode.

API Changes

Following new APIs will be added:

• Dedicating Resources (Explicit or Implicit) 
  • dedicateZone
  • dedicatePod
  • dedicateCluster
  • dedicateHost

      These are new admin APIs to dedicate a zone/pod/cluster/host for an account/domain.

      Parameters include:
       a)    ZoneId/PodId/ClusterId/HostId
       b)    DomainId
       c)    AccountId 

• Release dedication of resources ** releaseDedicatedZone
  • releaseDedicatedPod
  • releaseDedicatedCluster
  • releaseDedicatedHost

      These are new admin APIs to remove the dedication of zone/pod/cluster/host

       Parameters include:
       a)    ZoneId/PodId/ClusterId/HostId

• Listing Dedicated resources per account/domain** listDedicatedZones
  • listDedicatedPods
  • listDedicatedClusters
  • listDedicatedHosts

     These are new admin APIs to list dedicated pods/clusters/hosts for an account/domain.

     Parameters include:
       a)    zoneId/PodId/ClusterId/HostId
       b)    DomainId
       c)    AccountId

Note: List Dedicated resources APIs will list all the dedicated resources wrt the resource(zones/pods/clusters/hosts) if no parameter is provided. 

DB Changes:

1. New Table : dedicated_resources (id, uuid, zone_id, pod_id, cluster_id, host_id, domain_id, account_id)
      || Field || Type || Null || Key || Default || Extra ||

   id	bigint(20) unsigned	NO	PRI	NULL	auto_increment
   uuid	varchar(40)	YES	UNI	NULL
   data_center_id	bigint(20) unsigned	NO	MUL	NULL
   pod_id	bigint(20) unsigned	NO	MUL	NULL
   cluster_id	bigint(20) unsigned	NO	MUL	NULL
   host_id	bigint(20) unsigned	NO	MUL	NULL
   domain_id	bigint(20) unsigned	YES	MUL	NULL
   account_id	bigint(20) unsigned	YES	MUL	NULL

UI flow

• A resource can be dedicated at the time of adding it to CloudStack or at any point of time after it has been added.
• Dedicate <Resource> and Release<Resource> are the new action buttons added.

DRS? 

• This is applicable only for placement operations through CloudStack. This implementation is to only support scenarios where the HV does not do HA or DRS.