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

Improve OpenStack's documentation on RabbitMQ as needed #5

Closed
michaelklishin opened this issue Mar 27, 2015 · 11 comments
Closed

Improve OpenStack's documentation on RabbitMQ as needed #5

michaelklishin opened this issue Mar 27, 2015 · 11 comments

Comments

@michaelklishin
Copy link
Member

Filing it here for the lack of a more suitable place.

We need to review OpenStack's documentation on RabbitMQ setup and maintenance, and contribute improvements as we see fit.

@michaelklishin
Copy link
Member Author

Some specific points of improvement:

  • Mention RAM and disk limits, in particular what values are dangerous (and where defaults don't fit production needs)
  • Recommend Erlang 17.x
  • They suggest using the guest user. It really should be a separate user, e.g. named "openstack", as "guest" is limited to localhost connections in recent releases.
  • We should recommend using "autoheal" for partition handling.
  • Recommend an odd number of nodes

@michaelklishin
Copy link
Member Author

Started a thread about his on openstack-docs. This means at least one addition to the above points: our own guide dedicated to OpenStack, similar to the one on EC2.

We need to collect a list of topics it should cover.

@michaelklishin
Copy link
Member Author

This section should recommend using our apt repositories as opposed to relying on Ubuntu/Debian ones, which are at least 6 months behind.

@michaelklishin
Copy link
Member Author

This section also mentions rabbitmq-plugins, which doesn't seem to be a valid package for either Debian or Ubuntu.

@michaelklishin
Copy link
Member Author

This section should briefly mention what the cookie is. It currently leaves out the fact that the cookie can be anything, suggesting the user copies it from the first node after starting it. Can be clarified.

@michaelklishin
Copy link
Member Author

This guide should mention partition handling strategies and link to our related guides.

@michaelklishin
Copy link
Member Author

The above guide could mention automatic clustering and again, link to our docs.

@michaelklishin
Copy link
Member Author

This guide mentions that RabbitMQ has to be restarted to enable queue mirroring. I'd say we should consider mentioning policies.

@michaelklishin
Copy link
Member Author

Active/Passive (DRBD) guide also mentions the cookie.

@michaelklishin
Copy link
Member Author

I believe this is no longer as relevant as it was in spring 2015. Documentation improvements never end and evolve with deployment strategies, so I think this should be closed now.

michaelklishin pushed a commit that referenced this issue Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant