[
https://issues.apache.org/jira/browse/CLOUDSTACK-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735988#comment-13735988
]
ASF subversion and git services commented on CLOUDSTACK-4168:
-------------------------------------------------------------
Commit b965032b57a6023859fbc4b0faad533dc8adc2dc in branch refs/heads/4.2 from
[~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b965032 ]
CLOUDSTACK-4168 Root Admin should be able to create 'ExplicitDedication'
affinity group at domain level and make it available for all accounts in the
domain
Changes:
- 'ExcplicitDedication' type of group can be created/deleted by Root admin only
- Users can no longer create this type of affinity group
- RootAdmin can create this type of affinitygroup at domain level. Such a
domain level group is available for all accounts in that domain for listing and
for use during deployVM.
- The domain level affinitygroup should be visible to the users in that domain,
domain admins and Root admin.
> Root Admin should be able to create 'ExplicitDedication' affinity group at
> domain level and make it available for all accounts in the domain
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4168
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4168
> 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
>
>
> AffinityGroup of type 'ExplicitDedication' should be allowed to be created
> and deleted by RootAdmin only.
> And it should be possible for the admin to create it at domain level.
> This is necessary for the dedicated resources feature to tie up correctly to
> the affinity groups.
--
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
