First of all, apologies if this belongs strictly to openstack-docs,
based on multiple discussions in Vancouver I'd like more people to be aware of
this.
As announced in April and at the summit in May, RabbitMQ
team at Pivotal would like to help with OpenStack documentation and operations
experie
On 9 June 2015 at 10:26:27, Michael Klishin (mklis...@pivotal.io) wrote:
> I will push for introducing the most basic timeout support
> in ctl in the next bug fix release.
Some (highly conservative, for the sake of backwards compatibility)
improvements are already merged and will be in
Nodes can become unavailable with Shovel or Federation as well.
While both plugins will enqueue undelivered/unconfirmed messages internally,
recovery can take a while or never happen. So replication is certainly
necessary.
RabbitMQ has a guide that mentions several possible failure scenarios:
htt
On 8 June 2015 at 15:10:15, Davanum Srinivas (dava...@gmail.com) wrote:
> I'd like to bring out a poll about deprecating the RabbitMQ mirrored
> queues for HA layout and replacing the AMQP clustering by shovel
> [0],
> [1]. I guess the federation would not be a good option, but let's
> consid
On 28 April 2015 at 16:44:32, Michael Klishin (mklis...@pivotal.io) wrote:
> At this stage I'm trying to understand the process more than
> anything. E.g. how can
> documentation improvements to Kilo be contributed after it
> ships.
>
> Some of the improvements we
On 28 April 2015 at 16:33:35, Davanum Srinivas (dava...@gmail.com) wrote:
> Hello Michael.
>
> Just moving your thread to the correct mailling list.
Apologies, I've signed up to openstack-docs now and will re-post there.
--
MK
Staff Software Engineer, Pivotal/RabbitMQ
On 28 April 2015 at 16:33:35, Davanum Srinivas (dava...@gmail.com) wrote:
> Have you seen this?
> https://github.com/openstack/ha-guide/tree/master/doc/high-availability-guide/ha_aa_rabbitmq
>
>
> That url was built from this github repo:
> https://github.com/openstack/ha-guide/tree/master/doc
Hi,
I'm a RabbitMQ engineering team member and we'd like to help improve OpenStack
docs
around it.
I've been reading the docs and making notes of what can be improved. We'd be
happy
to contribute the changes. However, we're not very familiar with the OpenStack
development
process and have a f