Repository navigation
Conversation
…L generation block in install_stack.yaml without needing to deploy TripleO or touch the remote host Signed-off-by: Daniel Lawton <dlawton@redhat.com>
dlaw4608
force-pushed
the
ca_regen_playbook
branch
from
November 16, 2026 17:20
9658a95 to
8b2d95c
Compare
This file contains hidden or 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
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.
Add a localhost-only playbook that reuses the existing
simplecaroleto generate a CA and standalone server certificate without running
the full OpenStack deployment.
The playbook loads deployment defaults, accepts cloud-specific
overrides, and prints the generated certificate and key paths.
Installation and service restarts remain separate manual steps.
Usage:
Replace the overrides filename with your cloud’s configuration.
If local
sudorequires a password, add--ask-become-pass.The playbook prints the paths to the generated CA certificate/key
and server certificate/key in a temporary directory. Copy them to
a secure, persistent location before using them.
This command only generates files locally. Installing certificates,
updating client trust, and restarting services are separate steps.
Keep the CA private key on the management machine.