cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Ough <alex.o...@sungard.com>
Subject Re: [DISCUSS] Domain/Account/User Sync Up Among Multiple Regions
Date Mon, 04 Nov 2013 23:16:29 GMT
All,

Among the 2 approaches, I uploaded the implemented codes of the first
approach, master-slave architecture, here.
https://github.com/alexoughsg/albatross

And here is the design doc in the wiki.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain-Account-User+Sync+Up+Among+Multiple+Regions

Please review them and let me know what you think if you're interested!
Thanks
Alex Ough



On Thu, Oct 31, 2013 at 6:51 PM, Alex Ough <alex.ough@sungard.com> wrote:

> Great! Thanks a lot, Daan.
>
>
> On Thu, Oct 31, 2013 at 4:58 PM, Daan Hoogland <daan.hoogland@gmail.com>wrote:
>
>> you are added to jira, Alex
>>
>> On Thu, Oct 31, 2013 at 8:31 PM, Alex Ough <alex.ough@sungard.com> wrote:
>> > Thanks Chip, and can you also give a permission in Jira so that I can
>> > assign myself in its jira?
>> >
>> > Alex Ough
>> >
>> >
>> > On Thu, Oct 31, 2013 at 2:00 PM, Chip Childers <chipchilders@apache.org
>> >wrote:
>> >
>> >> Permission added.
>> >>
>> >> On Wed, Oct 30, 2013 at 12:19:23PM -0500, Alex Ough wrote:
>> >> > And I'd like to write the design document in the wiki page, but I
>> don't
>> >> > seem to have a permission to create pages.
>> >> > So can anyone give me the permission?
>> >> >
>> >> > My account in the wiki is alex.ough@sungard.com
>> >> >
>> >> > Thanks in advance.
>> >> > Alex Ough
>> >> >
>> >> >
>> >> > On Tue, Oct 29, 2013 at 3:38 PM, Alex Ough <alex.ough@sungard.com>
>> >> wrote:
>> >> >
>> >> > > I created a jira for this feature.
>> >> > >
>> >> > > https://issues.apache.org/jira/browse/CLOUDSTACK-4992
>> >> > >
>> >> > > But it doesn't allow for me to assign it to myself, so any
>> permission
>> >> do I
>> >> > > need for this?
>> >> > > If so, can anyone give me this permission?
>> >> > >
>> >> > > If there is anything missing, let me know.
>> >> > > Thanks
>> >> > > Alex Ough
>> >> > >
>> >> > >
>> >> > > On Fri, Oct 18, 2013 at 9:30 AM, Kishan Kavala <
>> >> Kishan.Kavala@citrix.com>wrote:
>> >> > >
>> >> > >> > -----Original Message-----
>> >> > >> > From: Alex Ough [mailto:alex.ough@sungard.com]
>> >> > >> > Sent: Thursday, 17 October 2013 11:25 PM
>> >> > >> > To: dev@cloudstack.apache.org; user@cloudstack.apache.org
>> >> > >> > Subject: Fwd: [DISCUSS] Domain/Account/User Sync Up Among
>> Multiple
>> >> > >> > Regions
>> >> > >> >
>> >> > >> > All,
>> >> > >> >
>> >> > >> > 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.
>> >> > >> >
>> >> > >> > I hope you guys have a chance to think about this and
give some
>> >> > >> feedbacks if
>> >> > >> > interested.
>> >> > >> > Thanks in advance.
>> >> > >> > Alex Ough
>> >> > >>
>> >> > >> [KK] Alex, it was discussed sometime back. Related thread
[1].
>> Sync up
>> >> > >> using messaging system is the right way to go.
>> >> > >>
>> >> > >>
>> >> > >> [1]
>> >> > >>
>> >>
>> http://www.mail-archive.com/cloudstack-dev@incubator.apache.org/msg20193.html
>> >> > >>
>> >> > >>
>> >> > >
>> >>
>> >>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message