openstack/kolla.git/ansible/roles/rabbitmq/templates/rabbitmq-env.conf.j2, branch master

Remove Ansible from Kolla

2016-11-16T04:34:17+00:00

Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b

Revert "Bind EPMD to api interface address"

2016-09-24T03:25:28+00:00

This issue still exsits when disable ipv6 feature. This reverts commit 5480bd9b1d3a9efcd3618ddf12718d2621ceeb47. Change-Id: I1e6c6bff5585cf5a49890668203d6971112c32f1

Bind EPMD to api interface address

2016-09-14T03:35:10+00:00

Closes-Bug: #1562701 Change-Id: Ica68bdee81223232995bc21ad5e5d5fbf9e8b05f

Adding required check for Orchestration Kubernetes

2016-09-12T19:32:42+00:00

Thgis PS add missing check for Kubernetes orchestration engine, without these changes, running kolla-ansible genconfig fails for Kubernetes environment. TrivialFix Change-Id: I25eeb7ae3ddba7c924f6d48aa24afdbe74227170

Fix intf address for RabbitMQ and disable cluster for Kube

2016-08-10T13:40:54+00:00

enable_rabbitmq_cluster is now a "yes" by default but you can set it to "no" if you want to disable clustering under any circumstances. The agreement made at OpenStack in Austin was that Kolla-Kubernetes would concentrate on RabbitMQ and MariaDB without clustering but with persistent storage and workload migration, then examine how to do proper distributed functionality as the project progresses, so I am just following what we'd already agreed upon. First, it helps us deal with issues of version upgrades without dealing with clustered version upgrades and the synchronization thereof. Second, it provides an alternative model for durability when used in Kubernetes. Understand that, if we disable RabbitMQ's clustering, Kubernetes is still able to re-schedule the queue off of a failed node in ways that Kolla-Ansible is not. There are known issues with RabbitMQ clustering, especially with auto-heal turned on. For many small-to-mid-sized clusters, it's going to provide for a better operator experience to have the known potential for a 30 second blip after RabbitMQ node failure than it is to have the known potential for partition and data loss and/or manual operations after you've turned off auto-heal. Kolla-kubernetes has already turned off host networking for the RabbitMQ pod; it's safe to set the interface address in the Kubernetes context. The question was asked why don't I just set the RabbitMQ cluster to be a single instance. It's unlikely that Kubernetes RabbitMQ with a PetSet will be clustered in the same declaritive fashion as the rabbitmq-clusterer plugin. Easier to just disable it and worry about how to configure the kube-friendly clustered RabbitMQ at a later point in time. Furthermore, it's an entirely valid case for many OpenStack control planes hosted atop Kolla-Kubernetes to accept the possibility of a 30-60 second blip in lieu of the long and questionable history of RabbitMQ clustering in production. Co-authored-by: Ryan Hallisey Change-Id: I7f0cb22d29a418fce4af8d69f63739859173d746 Partially-implements: blueprint api-interface-bind-address-override

Clarify comment about binding erlang to IPv4

2016-04-11T09:16:37+00:00

The comment was confusing and not explaining what the real issue is when binding erlang to an IPv4 address. Change-Id: I819ea137fa37c0b2711efb1e7cb1e518ae26b9ab Related-Bug: #1562701

Fix rabbitmq crash in centos gate

2016-04-11T06:28:19+00:00

Please refer to the Closes-Bug identifier for detailed information pertaining to this issue. Closes-Bug: #1562701 Change-Id: I77563930e14e11ea48e7edfef0bff80002279381

Use ubuntu Mitaka repo

2016-03-14T15:52:48+00:00

The rabbitmq-server package is upgraded to 3.5.7 in cloud-archive so we update centos to match The xen-utils package now needs an explict version, xen-utils-4.6 is what is provided by cloud-archive mitaka Libvirt 1.3 is in the ubuntu cloud-archive. This has a new daemon for logging that needs further implementation in newton. For now, it has been disabled within the qemu.conf Co-Authored-By: Jeffrey Zhang TrivialFix Change-Id: I84217824817c484b6800a64cbd7767b127a3098e

Make Heka collect RabbitMQ logs

2016-02-19T20:32:25+00:00

Partially implements: blueprint heka Change-Id: I8fd3324daf15e52712591c2b3cbec613d82b73b3

Use rabbitmq-clusterer when deploying

2015-11-03T04:51:45+00:00

Change-Id: I2a9c6fa16444a2142ab77f58d188eda84a2e59fd Partially-Implements: blueprint rabbitmq-clusterer