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 23:33:19 GMT


ASF subversion and git services commented on CLOUDSTACK-681:

Commit 8ece25c1f2bd6d0126c2a22b42e1c4da65fc2856 in branch refs/heads/master from Jessica Wang
[;h=8ece25c ]

CLOUDSTACK-681: deployment planner - create compute offering dialog - deployment planner dropdown
- add blank option and make it as default option. Not pass anything to API call when blank
option is selected.

> 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