cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Ough (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4992) Domain/Account/User Sync Up Among Multiple Regions
Date Sun, 09 Mar 2014 22:53:42 GMT


Alex Ough commented on CLOUDSTACK-4992:

Added a new feature that was requested internally, which is to provide an option to assign
the same uuid when creating the same resources in other regions.
There is a new global parameter, 'multi.region.resource.uuid.match' whose default value is
If set to true, the uuid of the target resource will be assigned when the same resource is
created in other regions.
If set to false, each region will use different uuids for same resources. Default value is

> Domain/Account/User Sync Up Among Multiple Regions
> --------------------------------------------------
>                 Key: CLOUDSTACK-4992
>                 URL:
>             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
> 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
> Wiki page
> The implementation

This message was sent by Atlassian JIRA

View raw message