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

Add RabbitMQ install roles #45

Open
cognifloyd opened this issue Sep 29, 2020 · 7 comments
Open

Add RabbitMQ install roles #45

cognifloyd opened this issue Sep 29, 2020 · 7 comments

Comments

@cognifloyd
Copy link
Collaborator

cognifloyd commented Sep 29, 2020

SUMMARY

Add generic roles for installing rabbitmq. They should span simple use-cases (single server) to clustered server.
Since this is a collection, we can break the installation down into multiple roles so that users can pick and choose the roles they need.

I'm thinking of something similar to the roles in community.mongodb.

Are there any suggestions on how to break down the set of install roles?
Once there is some feedback, I can work on either porting or re-writing some external roles.

ISSUE TYPE
  • Feature Idea
COMPONENT NAME

Misc rabbitmq roles

@cognifloyd
Copy link
Collaborator Author

cognifloyd commented Sep 29, 2020

One of my goals in putting these generic roles together here, is so that disparate communities can work together on installation roles for common dependencies.

I've heard that the openstack.rabbitmq_server role is a good starting point. So, I'll start looking through that to see how many different roles we might want here.

@odyssey4me
Copy link
Collaborator

I'm open to this idea. I'm also open to seeing thoughts on what the roles may be. The openstack-ansible role is somewhat monolithic which has its benefits and drawbacks. It might be worthwhile to break things out into multiple roles - for example, one to do initial install, one to configure and perhaps one specially suited to cluster management. Having multiple roles may make each one simpler to maintain... That said, I've not thought it through in much detail.

@cognifloyd
Copy link
Collaborator Author

Yes. I want to split this out into multiple roles. We could have one meta role that orchestrates the other roles to ease transition from openstack's role.

I've been busy with a new job, so I'll get back to this very soon. :)

@cognifloyd
Copy link
Collaborator Author

cognifloyd commented Jul 7, 2021

So here are the roles I think we could have:

  • community.rabbitmq.rabbitmq_repository: Add the deb/rpm/etc package repository
  • community.rabbitmq.rabbitmq_install: Install rabbitmq itself
  • community.rabbitmq.rabbitmq_config: Setup rabbitmq.conf and optionally add plugins, policies, vhosts, users
  • community.rabbitmq.rabbitmq_cluster: setup primary cluster node and have secondary nodes join

We might end up with another utility role or two, but that's the first stab at splitting it up.

@Andersson007
Copy link
Contributor

@odyssey4me @aitorpazos what do you think of the suggested roles? ^

@Andersson007
Copy link
Contributor

The battery included approach sounds good to me:) I'm not sure about the particular modules, that's why we're asking you, folks.

@DanceMore
Copy link

$newJob "likes ansible" but they've never bothered to use "modules" or "galaxy" or advanced features like that....

I'm trying to modernize things and I'm pretty shocked to see that community.rabbitmq can't configure repos and install the packages for me ...?

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

No branches or pull requests

4 participants