feat: add ansible execution environment for playbooks #806
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cardoe
force-pushed
the
ansible-start
branch
2 times, most recently
from
c30a353 to
8953184
Compare
nicholaskuechler
approved these changes
Mar 28, 2025
nicholaskuechler
approved these changes
Mar 28, 2025
cardoe
force-pushed
the
ansible-start
branch
4 times, most recently
from
2ab114b to
e26c3b0
Compare
cardoe
force-pushed
the
ansible-start
branch
7 times, most recently
from
eaa4a2d to
7ac048a
Compare
This creates an ansible based container that has ansible-runner as the executor inside which can then be loaded with playbooks and roles so that we can have a consistent way to configure different parts of the system or react to events in the system and execute a series of steps. To provide a consistent way to configure the overall system and react to events in the system. Some areas where this might be useful is for OpenStack Helm has a bootstrap bash script that executes on deployment. This is a big hardcoded blob and will be easier to be configurable via ansible.
cardoe
force-pushed
the
ansible-start
branch
6 times, most recently
from
d59b802 to
0a050b6
Compare
The current keystone bootstrap is a bash script which makes it hard to ensure that everything has been setup. By making it Ansible we can ensure that things are consistent. Unfortunately the openstack's role module does not support cross-domain or inherited like the CLI does so this hacks around it with ansible.builtin.command that then needs some hoops to avoid lint errors. Bump the keystone chart version which fixes volume mounts so that our inventory can be mounted into the bootstrap container.
This value is not used anywhere.
|
So this would require a all:
vars:
keystone_bootstrap_dex_url: "https://dex.dns.zone" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This creates an ansible based container that has ansible-runner as the executor inside which can then be loaded with playbooks and roles so that we can have a consistent way to configure different parts of the system or react to events in the system and execute a series of steps. To provide a consistent way to configure the overall system and react to events in the system. Some areas where this might be useful is for OpenStack Helm has a bootstrap bash script that executes on deployment. This is a big hardcoded blob and will be easier to be configurable via ansible.