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] [Commented] (CLOUDSTACK-4276) Dedicated Resources: Private Zone functionality issues
Date Wed, 14 Aug 2013 23:27:49 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740401#comment-13740401
] 

Prachi Damle commented on CLOUDSTACK-4276:
------------------------------------------

One change to the listZone API by domainid:

- This API should work for all types of accounts by passing domainid. Not just the root admin.

Commit hash:	1260b9737336f37d967443a2e968a93d4a617552
CLOUDSTACK-4337 Dedicated Resources: Zone dedicated to an account should only be visible and
accessible to that account
Changes:
- When listing a zone, add clause in the search to check the account_id for a dedicated zone
- When listsing a zone with a domainid, add a similar clause.
- DomainCheck:: checkAccess() for a zone should consider that zone can now be dediacted to
a specific account and check access accordingly.

                
> Dedicated Resources: Private Zone functionality issues 
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-4276
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4276
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Prachi Damle
>            Assignee: Prachi Damle
>            Priority: Critical
>
> Dedicated Resources is being used to dedicated a zone to a domain, instead of the private
zone functionality.
> Private zone used to set the 'domainid' in the zone record. That is not being set now
by the dedicated resources feature.
> All usecases  (createNetwork, zone access checks, resource_domain_admin ) that depend
on the domainid, are not changed, so we need to set the domainid in the zone record in data_center
table for those usecases to work correctly.
> Fixed needed:
> createZone API:
> - This API stakes in domainid, set it to the zone record in the data_center table
> updateZone API:
> - This API uses 'isPublic' flag to set a private zone to public - if this flag is set
and the zone is dedicated, release the dedication and remove the domainid from the data_center
table
> listZone API:
> - This API already has 'domainid' parameter. We should allow list zones by domain for
Root admin.
> DedicateZone API:
> - set domainid in the data_center table
> ReleaseDedicatedZone API:
> - remove zoneid from the data_center table

--
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