Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Several changes to RabbitMQ cartridge #2

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

anefassa
Copy link
Contributor

  • Fixed issues which prevented multiple instances of RabbitMQ from starting in different openshift applications running on the same node. (This was mainly related to the management plugin attempting to bind to all interfaces). Change needed in rabbitmq.config.erb.install
  • Fixed md5 checksum issue. Correct syntax requires double space between md5 and filename. This fix was still missing in one place and therefore would cause RabbitMQ to be downloaded everytime.
  • Fixed inconsistency in variable name. BROKER_IP and BROKER_HOST were both being used and therefore the same variable name and code could not be used by scalable and non-scalable apps. Now consistent across the board.
  • Expose RabbitMQ Admin Gui and api for browser access and also publish admin port for access in scalable applications. This allows for instance to have a scalable app that has a perl component (or other) monitoring Rabbit through the management plugin.
  • Included app name into Rabbit nodename config. This is not technically necessary but can help Openshift administrator determine to which app a certain Rabbit process belongs to, especially when Rabbit is part of scalable app and the app name is then not part of the DNS name of the Rabbit Gear.

anefassa added 6 commits June 13, 2014 16:39
…ack IP assigned to the specific app. Otherwise multiple apps using RabbitMq can't be started. Also added config to prevent Management plugin from binding to old 55672 port, instead only binds to 15672
…uniqueeness to avoid Erlang conflicts and makes it easier to identify instance in scalable apps.
… and in other places as BROKER_IP causing inconsistency in var name for scalable and non-scalable apps. Now using OPENSHIFT_RABBITMQ_BROKER_HOST everywhere.
…e that there is an unresolved issue related to Apache rewrite rules decoding the virtual host reference in the URL which prevents the GUI and API from being fully functional. However this should allow the user to do most browsing through Adming GUI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant