Provide RabbitMQ management UI through HAProxy

[Jimmy McCrory]

When running HAProxy on each of the infrastructure hosts, the management UI of the local RabbitMQ server container should be configured as a backend.

This UI is invaluable for quickly checking the health of a RabbitMQ server, and it's especially helpful when troubleshooting to be able to compare the states of each individual server.

[Jean-Philippe Evrard (jean-philippe-evrard)]

No backport of new features to Kilo will be done during the project. I'll mark this request in Kilo as "Won't fix"

[Wade Holler (wade-holler)]

I did not see work on this bug and thought I would try to help with a review:

https://review.openstack.org/#/c/317675/

After creating review I found
https://review.openstack.org/#/c/276712/ (status Merge Conflict)
https://review.openstack.org/#/c/276672/ (status "")

My guess is above two didn't make it into these comments automatically because their commit messages didn't have the Closes-Bug: text. just a guess.

No offense to George and his work was meant.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/317675
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=b5b2bb9af4149304286734ab75f42d2b2730f2b2
Submitter: Jenkins
Branch: master

commit b5b2bb9af4149304286734ab75f42d2b2730f2b2
Author: wade-holler <email address hidden>
Date: Tue May 17 18:46:38 2016 +0000

    Add RabbitMQ mgmt UI through HAProxy

    Backgroud: Bug Requests ability to access
    RabbitMQ management UI through HAproxy

    Approach:
    --Add rabbitmq ui port 15672 to HAProxy
    --DO NOT Add monitoring user by default,
    instead key on existence of rabbitmw_monitoring_userid
    in user_variables.yml
    --ADD user_variables.yml update per above with
    explanation
    --Add "monitoring" user to rabbitmq for monitoring with
    "monitoring" user tag
    --Add monitoring user passwd var to user_secrets
    --Add features: release note

    Closes-Bug: 1446434

    Change-Id: Idaf02cad6bb292d02f1cf6a733dbbc6ff4b4435e

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/openstack-ansible 14.0.0.0b1 development milestone.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 14.0.0.0b2 development milestone.