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

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

Commit b41e6e929d5f4f9483c326268a7b36779d23dc38 in branch refs/heads/4.1 from 
[~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=b41e6e9 ]

CLOUDSTACK-1636: Removed the concept of owner region. Removed region_id from 
user/account and domain tables. Removed forwarding of api calls to owner 
region. Removed api_key and secret_key from region table. Included related DB 
upgrade changes.

                
> AWS Regions - Remove the concept of having an owner region for 
> domain/account/user objects.
> -------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1636
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1636
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>         Environment: Latest build from 4.1
>            Reporter: Sangeetha Hariharan
>            Assignee: Kishan Kavala
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> AWS Regions - Remove the concept of having an owner region for 
> domain/account/user objects.
> Since CloudStack is NOT responsible for propagation of domain/account/user 
> data between regions , there  should be no need for us to maintain a  a 
> concept of 1 region being the owner for domain/account/user and allow 
> delete/edit operations to be done only by owners.
> There will be no need to have a region_id in domain/account/user tables.
> There will be no need to have apikey and secret key being stored for region 
> tables.

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

Reply via email to