[jira] [Commented] (CLOUDSTACK-4992) Domain/Account/User Sync Up Among Multiple Regions

["Alex Ough (JIRA)" <ji...@apache.org>]

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

Alex Ough commented on CLOUDSTACK-4992:
---------------------------------------

All,

Alex Huang, Alena and I had a conversation to find out the best solution for one remaining issue,
which is to prevent the changes from being sent to remote regions even when resource changes are occurred in the local region during FullScan
and these are what we decided.

1. A new parameter, 'originated_region_uuid', will be used to control the flow
   - during the realtime sync, the value will be the uuid of the local region to allow the changes to be transferred to remote regions,
   - during the full scan, the value will be the uuid of the remote region to prevent them from being transferred to remote regions even if the change was occurred in the local region.

2. To support this change, a new input param, 'originated_region_uuid', will be added to all methods to manage user/account/domain in AccountManager & DomainManager class.

3. To store the new input param value, a new field, 'originated_region_uuid', will be added to domain/account/user table and they will be populated with the current local region uuid when the fields are created during the schema changes because we can guarantee that the current user/account/domain resources were created in the local region.

4. The API interfaces to manage the user/account/domain will have an additional input param, 'originated_region_uuid', to support this change.

Please let me know if you have any comments.
Thanks

> Domain/Account/User Sync Up Among Multiple Regions
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-4992
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4992
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.4.0
>            Reporter: Alex Ough
>            Assignee: Alex Ough
>              Labels: features
>             Fix For: 4.4.0
>
>
> Currently, under the environment of cloudstack with multiple regions, each region has its own management server running with a separate database. So if we want to support multiple regions and provide one point of entry for a customer, we need to duplicate domain/account/user information of that customer to all of the databases of regions the customer accesses, which will cause data discrepancies when users update those data independently in each management server.
> So I'd like to provide a way to sync up the data using the messaging system introduced in 4.1.0. Using the events from each management server, updates from each region can be propagated to the rest regions and they can be executed accordingly.
> Discussion
> http://markmail.org/thread/k4x63ef55chcj4y5
> Wiki page
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain-Account-User+Sync+Up+Among+Multiple+Regions
> The implementation
> https://github.com/alexoughsg/Albatross/tree/albatross



--
This message was sent by Atlassian JIRA
(v6.2#6252)