Available queues in rabbitmq
Oh, so without the need to put an IP floating between hosts.
Good job, thanks for helping
Best
Alessandro
Il giorno 24/lug/2012, alle ore 17:49, Eugene Kirpichov ha scritto:
Hi Alessandro,
My patch is about removing the need for pacemaker (and it's pacemaker
Sorry for the delay, i was out from work.
Awesome work Eugene, I don't need the patch instantly as i'm still building the
infrastructure.
Will it will take alot of time to go in Ubuntu repositories?
Why you said you need load balancing? You can use only the master node and in
case the
Hi Alessandro,
My patch is about removing the need for pacemaker (and it's pacemaker
that I denoted with the term TCP load balancer).
I didn't submit the patch yesterday because I underestimated the
effort to write unit tests for it and found a few issues on the way. I
hope I'll finish today.
Oh, so without the need to put an IP floating between hosts.
Good job, thanks for helping
Best
Alessandro
Il giorno 24/lug/2012, alle ore 17:49, Eugene Kirpichov ha scritto:
Hi Alessandro,
My patch is about removing the need for pacemaker (and it's pacemaker
that I denoted with the term
On 07/23/2012 09:02 AM, Alessandro Tagliapietra wrote:
Hi guys,
just an idea, i'm deploying Openstack trying to make it HA.
The missing thing is rabbitmq, which can be easily started in
active/active mode, but it needs to declare the queues adding an
x-ha-policy entry.
Hi,
I'm working on a RabbitMQ H/A patch right now.
It actually involves more than just using H/A queues (unless you're
willing to add a TCP load balancer on top of your RMQ cluster).
You also need to add support for multiple RabbitMQ's directly to nova.
This is not hard at all, and I have the
On 07/23/2012 02:58 PM, Eugene Kirpichov wrote:
The only problem is, it breaks backward compatibility a bit: my patch
assumes you have a flag rabbit_addresses which should look like
rmq-host1:5672,rmq-host2:5672 instead of the prior rabbit_host and
rabbit_port flags.
Guys, can you advise on
The only problem is, it breaks backward compatibility a bit: my patch
assumes you have a flag rabbit_addresses which should look like
rmq-host1:5672,rmq-host2:5672 instead of the prior rabbit_host and
rabbit_port flags.
Guys, can you advise on a way to do this without being ugly and
Hi Jay,
Great idea. Thanks. I'll amend and test my patch, and then upload it
to codereview.
On Mon, Jul 23, 2012 at 12:18 PM, Jay Pipes jaypi...@gmail.com wrote:
On 07/23/2012 02:58 PM, Eugene Kirpichov wrote:
The only problem is, it breaks backward compatibility a bit: my patch
assumes you
Eugene,
I suggest just add option 'rabbit_servers' that will override
'rabbit_host'/'rabbit_port' pair, if present. This won't break anything, in
my understanding.
--
Best regards,
Oleg Gelbukh
Mirantis, Inc.
On Mon, Jul 23, 2012 at 10:58 PM, Eugene Kirpichov ekirpic...@gmail.comwrote:
Hi,
Yup, that's basically the same thing that Jay suggested :) Obvious in
retrospect...
On Mon, Jul 23, 2012 at 12:42 PM, Oleg Gelbukh ogelb...@mirantis.com wrote:
Eugene,
I suggest just add option 'rabbit_servers' that will override
'rabbit_host'/'rabbit_port' pair, if present. This won't break
+openstack-dev@
To openstack-dev: this is a discussion of an upcoming patch about
native RabbitMQ H/A support in nova. I'll post the patch for
codereview today.
On Mon, Jul 23, 2012 at 12:46 PM, Eugene Kirpichov ekirpic...@gmail.com wrote:
Yup, that's basically the same thing that Jay suggested
12 matches
Mail list logo
