cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Damle (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-4221) Dedicated Resources: changes to associate the dedicated resource with the 'ExplicitDedication' affinity group
Date Sat, 10 Aug 2013 18:21:48 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prachi Damle resolved CLOUDSTACK-4221.
--------------------------------------

    Resolution: Fixed
    
> Dedicated Resources: changes to associate the dedicated resource with the 'ExplicitDedication'
affinity group
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4221
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4221
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Prachi Damle
>            Assignee: Prachi Damle
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> The dedicated resources feature does not establish the correct relation between dedicated
resources and the ExplicitDedication’ affinity group that needs to be created to use the
resources during VM deployment.
> Changes are needed to associate dedication with the dedication affinity group. Since
the group is chosen during VM deployment, only the dedicated resources associated to the group
should be considered for deployment.
> This will also provide a better user experience since the affinity group will be created
when the resources are dedicated by the admin, and this group will be available to the users
during VM deployment. Users will not create a group themselves anymore.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message