cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-681) Dedicate Pod, Cluster or Host to a domain
Date Thu, 30 May 2013 08:09:21 GMT


ASF subversion and git services commented on CLOUDSTACK-681:

Commit 17267794adb2bab923fb20515a7b943780d61921 in branch refs/heads/master from [~saksham]
[;h=1726779 ]

CLOUDSTACK-681: Dedicated Resources - Explicit Dedication, Private zone, pod, cluster or host.

This feature allows a user to deploy VMs only in the resources dedicated to his account or

1. Resources(Zones, Pods, Clusters or hosts) can be dedicated to an account or domain.
   Implemented 12 new APIs to dedicate/list/release resources:
   - dedicateZone, listDedicatedZones, releaseDedicatedZone for a Zone.
   - dedicatePod, listDedicatedPods, releaseDedicatedPod for a Pod.
   - dedicateCluster, listDedicatedClusters, releaseDedicatedCluster for a Cluster
   - dedicateHost, listDedicatedHosts, releaseDedicatedHost for a Host.
2. Once a resource(eg. pod) is dedicated to an account, other resources(eg. clusters/hosts)
inside that cannot be further dedicated.
3. Once a resource is dedicated to a domain, other resources inside that can be further dedicated
to its sub-domain or account.
4. If any resource (eg.cluster) is dedicated to a account/domain, then resources(eg. Pod)
above that cannot be dedicated to different accounts/domain (not belonging to the same domain)
5. To use Explicit dedication, user needs to create an Affinity Group of type 'ExplicitDedication'
6. A VM can be deployed with the above affinity group parameter as an input.
7. A new ExplicitDedicationProcessor has been added which will process the affinity group
of type 'Explicit Dedication' for a deployment of a VM that demands dedicated resources.
   This processor implements the AffinityGroupProcessor adapter. This processor will update
the avoid list.
8. A VM requesting dedication will be deployed on dedicatd resources if available with the
user account.
9. A VM requesting dedication can also be deployed on the dedicated resources available with
the parent domains iff no dedicated resources are available with the current user's account
10. A VM (without dedication) can be deployed on shared host but not on dedicated hosts.
11. To modify the dedication, the resource has to be released first.
12. Existing Private zone functionality has been redirected to Explicit dedication of zones.
13. Updated the db upgrade schema script. A new table "dedicated_resources" has been added.
14. Added the right permissions in
15. Unit tests:  For the new APIs and Service, added unit tests under : plugins/dedicated-resources/test/org/apache/cloudstack/dedicated/
16. Marvin Test: To dedicate host, create affinity group, deploy-vm, check if vm is deployed
on the dedicated host.

> Dedicate Pod, Cluster or Host to a domain
> -----------------------------------------
>                 Key: CLOUDSTACK-681
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: pre-4.0.0
>            Reporter: deepti dohare
>            Assignee: Devdeep Singh
>             Fix For: 4.2.0
> Currently in CloudStack architecture, domains can have dedicated zones but not pods,
clusters or hosts. Dedicating a zone might be very expensive offering for an end users, whereas
dedicating a pod, cluster or a host may be more economical. 
> This feature will allow Root-Admin to dedicate resources to a specific domain that needs
private infrastructure for additional security or performance guarantees.
> Requirements described at: 
> Release Planning: 
> Dev List Discussion:
> Functional Spec:
> Feature Branch: Will come in as reviews

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