cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Damle (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-818) Document Dedicate Pod, Cluster or Host to a domain
Date Thu, 22 Aug 2013 23:49:51 GMT


Prachi Damle commented on CLOUDSTACK-818:

B] Following changes apply to dedication of pod/cluster/host
Admin Usecases
a)	Dedicate Resource (pod or cluster or host)
Current: Root admin can dedicate a pod/cluster/host using the DedicateXXX API to an account
or domain

Change: Root admin can still dedicate the resource to an account or domain. But in addinition
to dedication, CCP will internally:
-          Creates affinity group for the given account or domain of type ‘ExplicitDedication’
-          The resource gets dedicated to this affinity group. The group belongs to that account
or domain.
-          If the resource is dedicated to a domain,  the affinity group gets created for
the domain. Such a group is available to all accounts in that domain and any sub-domain

b)	Changes to ListDedicatedXXX API: The list API can take in affinity group id and list resources
under that group.

c)	Create/ Delete ‘ExplicitDedication’ AffinityGroup: 
Cuurent: Users can create/delete group of this type
-	Only root admin can create/delete this type of group.
-	When the group is deleted, following actions occur implicitly:
o	Any existing VMs using this group, will no longer use dedicated resources on restart. These
VMs will however keep running on same resources, only on restart dedication is not guaranteed.
o	The resources(host/cluster/pod) in the this group will no longer be dedicated to that account/domain
o	Group is deleted and not available to the users in that account/domain anymore

User Usecases
a)  Create/Delete ‘ExplicitDedication’ AffinityGroup
Current: User can create/delete affinity group of type ‘ExplicitDedication’
Change: User CANNOT create/delete group of type ‘ExplicitDedication’ / CCP will not expose
the ‘ExplicitDedication’ type to the user. Only Root admin can create/delete this type
of group
b)  DeployVM
Current: User has to first create affinity group and then pass it in deployVM API
Change: User does NOT create the group, group will be created by the admin during dedication
of resource.  This group will listed to the user in the VM wizard.
The user can choose this group if VM should be deployed to the dedication resource under that

Note: To use the dedicated host/cluster/pod user must choose the dedicated group during VM

c)How to change the VM from dedicated pod/cluster/host to a non-dedicated pod/cluster/host
-	User can update the VM’s affinity group from UI or using the updateVMAffinityGroup API.
The VM should be in ‘Stopped’ state to use this API.
-	Using this call, user can remove the ‘ExplicitDedication’ group associated to the VM.
-	When VM is started again, the deployment will no longer happen on dedicated resource. CCP
will try to deploy the VM on any non-dedicated resources available to the user.

d)  List ‘ExplicitDedication’ AffinityGroup
Current: User can list only the groups visible to his account 
Change: User can list groups belonging to his account + groups belonging to his domain and
parent domain

> Document Dedicate Pod, Cluster or Host to a domain
> --------------------------------------------------
>                 Key: CLOUDSTACK-818
>                 URL:
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>            Reporter: Radhika Nair
>            Assignee: Jessica Tomechak
>             Fix For: 4.2.0
> Dedicate Pod, Cluster or Host to a domain- Documentation

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message