Update RabbitMQ

[wimpers]

Note: release 3.5.8 marks the final patch in the 3.5.x series. RabbitMQ 3.5.x is no longer maintained. Upgrade, and refer to the current version of RabbitMQ instead.

Since the 3.5.x release is no longer maintained it might be advised to

• Go to Rabbitmq 3.6.x
• Find something else

[wimpers]

If there is a reason to go for something else, please link the relevant tickets in GH

[khenderick]

Ubuntu 16.04 only ships 3.5.7-1. Do you want us to manually maintain a set of packages fetched from other sources?

[wimpers]

@saelbrec points out that setting up 3 RabbitMQs isn't ideal. (I believe @kinvaris did some research about that)

The BAM isn't favor of maintaining our own set of packages or changing to something else .

Maybe we should start listing the issues OPS/ framework has with the current version of RabbitMQ. ( @khenderick @jeroenmaelbrancke @jtorreke @matthiasdeblock )

[khenderick]

There is #860 which was moved to internal openvstorage/org_quality#33
There was also this pre GitHub era ticket OVS-4469

[kinvaris]

@wimpers a few months ago we did some testing with a 3 node master setup. Here we saw that when shutting down 1 node the whole rabbitMQ cluster went down. Then I did some research about this and some forums pointed out you should at least have 4 nodes.

But a week ago we did some testing with 3 master nodes and the rabbitMQ cluster kept on going.

Although observing these results, I think it is recommended to have at least 4 nodes.