[
https://issues.apache.org/jira/browse/CLOUDSTACK-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839177#comment-13839177
]
Alex Ough commented on CLOUDSTACK-4992:
---------------------------------------
After changing codes to master, I found there is an issue blocking this,
CLOUDSTACK-3190.
Currently, I'm trying to fix the blocker to move on this issue.
> 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: Future
> Reporter: Alex Ough
> Assignee: Alex Ough
> Labels: features
> Fix For: Future
>
>
> 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 of the first approach, master-slave architecture.
> https://github.com/alexoughsg/albatross
--
This message was sent by Atlassian JIRA
(v6.1#6144)
