cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4276) Dedicated Resources: Private Zone functionality issues
Date Tue, 13 Aug 2013 00:47:49 GMT

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

ASF subversion and git services commented on CLOUDSTACK-4276:
-------------------------------------------------------------

Commit 3ad0008c899014870b7e94f75c167695644efa4b in branch refs/heads/4.2 from [~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3ad0008 ]

CLOUDSTACK-4276 Dedicated Resources: Private Zone functionality issues

Changes:
createZone API:
- This API takes 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

                
> 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