[
https://issues.apache.org/jira/browse/CLOUDSTACK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739975#comment-13739975
]
Prachi Damle commented on CLOUDSTACK-4319:
------------------------------------------
This is exactly as designed now to be compatible to the private zone
functionality of 3.0.x. Originally a dedicated zone required an affinitygroup
to be present in the API call.
Now if a user can see and access the dedicated zone, he should be able to
deploy VM in that zone even without providing any affinity group.
API works with or without the affinity group when the zone is dedicated and
accessible to the user.
This is what my design change email had mentioned:
No, this is intentional and per design now.
This is exactly as designed now to keep it compatible to private zone
functionality. Originally a dedicated zone required an affinitygroup to be
present in the API call.
But now if a user can see the dedicated zone and the zone is available to him,
he should be able to deploy VM in that zone even without providing any affinity
group.
API works with or without the affinity group when the zone is dedicated and
accessible to the user. This is true for a dedicated zone only, to use a
dedicated pod/cluster/host affinitygroup is needed.
-----------------------------------------------------------------------------------------------
This is what my design change email had mentioned:
A] Zone dedication (aka private zone functionality)
Admin zone dedication usecase
o Root Admin can dedicate a zone to an account/domain during zone creation
o CloudPlatform will internally create an affinity group for that
account/domain and dedicate the zone to that group.
User VM deployment usecase:
o The affinity group created above will be available to the user and users
need not create the affinity group themselves
o At API level, for a dedicated zone, the VM deployment API will work with or
without passing in the affinity group.
> Able to Create A VM on a Dedciated Zone without using the affinity group.
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4319
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4319
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.2.0
> Reporter: Kiran Koneti
> Priority: Critical
> Fix For: 4.2.0
>
>
> Created a setup in the below mentioned way:
> Zone-->POD-->Cluster-->2Hosts.
> 1)I created 2 domains apart from the Root Domain having two accounts for each
> domain.
> 2)Dedicated the Zone to non root domain.
> 3)Dedicated the one host to account in the same domain.
> 4)Observed that 2 affinity groups are created and the while deploying the VM
> i haven't selected any of the affinity groups and the VM creation was
> Successful.
> The expected Result is the VM creation should be failed as the Zone is
> dedicated and no affinity group is selected.
--
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
