Skip to content

Add stop-openstack-services.yml playbook #809

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

Merged
merged 1 commit into from
Dec 15, 2023

Conversation

Alex-Welsh
Copy link
Member

Adds a new playbook to stop openstack services across the overcloud.

I was undecided as to whether this warrants its own playbook but I've needed to use it enough times now that I think other people might want it.

One function I was considering was a variable to change the docker stop to a docker restart which we could then redirect to in the case of the rabbitmq-reset.yml playbook.

@Alex-Welsh Alex-Welsh requested a review from a team as a code owner November 29, 2023 16:15
@Alex-Welsh Alex-Welsh force-pushed the stop-services-playbook branch 2 times, most recently from 8c6db24 to 6ebfcac Compare November 29, 2023 16:33
@Alex-Welsh Alex-Welsh force-pushed the stop-services-playbook branch from 6ebfcac to fe4c973 Compare December 6, 2023 13:56
@mnasiadka
Copy link
Member

Maybe a stupid question, but what's wrong with kolla-ansible stop? ;-)

@markgoddard
Copy link
Contributor

Maybe a stupid question, but what's wrong with kolla-ansible stop? ;-)

Slooooow

@mnasiadka
Copy link
Member

Maybe a stupid question, but what's wrong with kolla-ansible stop? ;-)

Slooooow

Correct answer, should we rework that upstream as well?

@markgoddard
Copy link
Contributor

Maybe a stupid question, but what's wrong with kolla-ansible stop? ;-)

Slooooow

Correct answer, should we rework that upstream as well?

How do you propose to do it?

@mnasiadka
Copy link
Member

Maybe a stupid question, but what's wrong with kolla-ansible stop? ;-)

Slooooow

Correct answer, should we rework that upstream as well?

How do you propose to do it?
Maybe a similar playbook, just for those time constrained - but we would probably need a better mechanism for being able to tell which services need stopping - maybe a playbook with a tag per play? It's going to be slower than this, but probably faster than kolla-ansible stop currently.

@Alex-Welsh
Copy link
Member Author

Maybe a stupid question, but what's wrong with kolla-ansible stop? ;-)

Slooooow

Correct answer, should we rework that upstream as well?

How do you propose to do it?
Maybe a similar playbook, just for those time constrained - but we would probably need a better mechanism for being able to tell which services need stopping - maybe a playbook with a tag per play? It's going to be slower than this, but probably faster than kolla-ansible stop currently.

Playbook with a tag per play that adds all the services to a list, then runs the stop all at once? Would be a lot faster than trying to stop them all individually.

@Alex-Welsh Alex-Welsh merged commit edd037b into stackhpc/yoga Dec 15, 2023
@Alex-Welsh Alex-Welsh deleted the stop-services-playbook branch December 15, 2023 11:17
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.

4 participants