openstack team mailing list archive

[Eric Windisch <eric@xxxxxxxxxxxxxxxx>]

Sebastien,  

For my part, I don't do *any of it*. I'm the author of the ZeroMQ implementation, where this is a non-issue.

I think that having the Rabbit queues decoupled makes a lot of sense, especially since the code to do this can be generalized across multiple RPC implementations. (i.e. this would be a win for Qpid as well)   I'm clearly not a die-hard RabbitMQ admin -- is there a reason to use clustering over a decoupled solution for a greenfield application?  

--  
Eric Windisch


On Friday, May 25, 2012 at 17:54 PM, Sébastien Han wrote:

> Why don't you use the RabbitMQ builtin cluster solution?
> I setup an active/active cluster with the buildin mecanism and put an HAProxy on top with a priority on a specific node. (weight and backup options).
>  
> For the mirrored queues don't we need to edit the openstack code?
>  
> Cheers.
> ~Seb
>  
>  
>  
> On Fri, May 25, 2012 at 10:10 PM, Eric Windisch <eric@xxxxxxxxxxxxxxxx (mailto:eric@xxxxxxxxxxxxxxxx)> wrote:
> > I feel that the best way to deploy RabbitMQ is to run multiple independently queue servers and have separate consumers to these servers. You can then do client-side balancing to select which Rabbit server messages go. To get that in Nova today would be pretty minor -- especially after the matchmaker lands (this can provide client-side balancing of servers).  
> >  
> > --  
> > Eric Windisch
> >  
> >  
> > On Friday, May 25, 2012 at 09:18 AM, Stephen Gran wrote:
> >  
> > > Hello,
> > >  
> > > I am investigating various high availability options for a pending
> > > deploy of open stack. One of the obvious services to make resilient is
> > > the mq service. We're going to be using rabbitmq, and we'll most likely
> > > have N of them in a standard rabbit mq cluster behind a load balancer
> > > configured as active/passive. One of the obvious improvements on this
> > > would be to use mirrored queues to protect against message loss as well
> > > as service downtime.
> > >  
> > > Are there recommended ways of doing this? I see that I can use durable
> > > queues, which might work around the problems of openstack checking queue
> > > parameters on reconnect, but it seems a shame there's not an obvious way
> > > to do this out of the box. Unless I'm missing something?
> > >  
> > > Cheers,
> > > --  
> > > Stephen Gran
> > > Senior Systems Integrator - guardian.co.uk (http://guardian.co.uk)
> > >  
> > > Please consider the environment before printing this email.
> > > ------------------------------------------------------------------
> > > Visit guardian.co.uk (http://guardian.co.uk) - newspaper of the year
> > >  
> > > www.guardian.co.uk (http://www.guardian.co.uk) www.observer.co.uk (http://www.observer.co.uk) www.guardiannews.com (http://www.guardiannews.com)  
> > >  
> > > On your mobile, visit m.guardian.co.uk (http://m.guardian.co.uk) or download the Guardian
> > > iPhone app www.guardian.co.uk/iphone (http://www.guardian.co.uk/iphone)
> > >  
> > > To save up to 30% when you subscribe to the Guardian and the Observer
> > > visit www.guardian.co.uk/subscriber (http://www.guardian.co.uk/subscriber)  
> > > ---------------------------------------------------------------------
> > > This e-mail and all attachments are confidential and may also
> > > be privileged. If you are not the named recipient, please notify
> > > the sender and delete the e-mail and all attachments immediately.
> > > Do not disclose the contents to another person. You may not use
> > > the information for any purpose, or store, or copy, it in any way.
> > >  
> > > Guardian News & Media Limited is not liable for any computer
> > > viruses or other material transmitted with or as part of this
> > > e-mail. You should employ virus checking software.
> > >  
> > > Guardian News & Media Limited
> > >  
> > > A member of Guardian Media Group plc  
> > > Registered Office
> > > PO Box 68164
> > > Kings Place
> > > 90 York Way
> > > London
> > > N1P 2AP
> > >  
> > > Registered in England Number 908396
> > >  
> > >  
> > > _______________________________________________
> > > Mailing list: https://launchpad.net/~openstack
> > > Post to : openstack@xxxxxxxxxxxxxxxxxxx (mailto:openstack@xxxxxxxxxxxxxxxxxxx)
> > > Unsubscribe : https://launchpad.net/~openstack
> > > More help : https://help.launchpad.net/ListHelp
> > >  
> > >  
> > >  
> >  
> >  
> >  
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx (mailto:openstack@xxxxxxxxxxxxxxxxxxx)
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >  
>