Page History

...

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 DedicatedResourcePlanner which will implement a deployment planner interface.

Dedication will be achieved as:

1. Admin adds Pod/cluster/host
2. Admin dedicates the pod/cluster/host to a domain/account using new dedication APIs 
3. Admin enables the pod/cluster/hostDedication will be used when:
4. If a request is placed to deploy a VM with Service Offering flag "isdedicated" ON
   1. Check if the account/domain has dedicated resources:
      1. If Yes, Place the VM in dedicated resource
      2. If No, Place the VM in new free empty host, make that host dedicated to that account.

Note: If Service Offering Flag is OFF, non-dedicated (shared) resources will be used.

API Changes:

Following APIs need to be updated.

Root Admin APIs

1. Dedication will be achieved using APIs by providing additional request parameters : domainid and accountid while creating pod, clusters or hosts.
2. Dedication can also be achieved by updating the above parameters for updatePod, updateCluster or updateHost APIs

• createPod

          Request parameter addition:

new APIs will be added:

• dedicatePod
• dedicateCluster
• dedicateHost
• listDedicatedPods
• listDedicatedClusters
• listDedicatedHosts

Existing API modification:

• updatePod
• listPods 
• addCluster
• deleteCluster
• updateCluster
• listClusters
• addHost
• updateHost
• listHosts
• createServiceOffering:  Request Parameter Addition:

DB Changes:

1. dedicated_resources (id, uuid, zone_id, pod_id, cluster_id, host_id, domain_id, account_id) :  This table contains the details about the patches for different XenServers versions.

   Field	Type	NULL	Key	Default	Extra
   id	bigint(20) unsigned	NO	PRI	NULL	auto_increment
   uuid	varchar(40)	NO		NULL
   description	varchar(999)	YES		NULL
   label	varchar(40)	YES		NULL
   timestamp	timestamp	YES		NULL
   url	varchar(999)	YES		NULL

2.  host_pod_ref table: Introduce two columns “domain_id” and "account_id". Default value for both should be null.
3.  cluster table:  Introduce two columns “domain_id” and "account_id". Default value for both should be null.
4.  host table:  Introduce two columns “domain_id” and "account_id". Default value for both should be null.
5. service_offering table: Introduce a column “isdedicated” in  service_offering table. Default value should be 0.

...

UI flow

• In "Add Pod" add a new option "Public" check option. If it is checked show 2 more list options of domain and account, set to the default value. 
• In "Add Cluster" add a new option "Public" check option. If it is checked show 2 more list options of domain and account, set to the default value
• In "Add Host" add a new option "Public" check option. If it is checked show 2 more list options of domain and account, set to the default value
• Display isPublic flag when listPods, listClusters, listHosts. 
• Set isPublic to true only when domainId or accountId is not null for the pod in the listPod response
• Add a check option: isdedicated in  "Add compute offering" windowTBD