Skip to content

Conversation

@MoteHue
Copy link
Contributor

@MoteHue MoteHue commented Nov 18, 2025

No description provided.

@MoteHue MoteHue requested a review from a team as a code owner November 18, 2025 15:18
@MoteHue
Copy link
Contributor Author

MoteHue commented Nov 18, 2025

This would be good to backport too :)

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces valuable documentation and scripts for managing Octavia TLS certificates. The documentation is comprehensive but could be improved with some corrections to numbering and formatting for better clarity. The accompanying shell scripts are functional but contain some issues, such as using non-standard exit codes and suppressing error outputs, which could hinder debugging. I have provided specific suggestions to address these points and enhance the overall quality and robustness of the changes.

@MoteHue MoteHue force-pushed the support-persisting-octavia-ca branch 2 times, most recently from be8e59e to 8aa76ba Compare November 18, 2025 15:49
@MoteHue MoteHue added documentation Improvements or additions to documentation enhancement New feature or request Caracal Targets the Caracal OpenStack release backport Backport needed labels Nov 18, 2025
@MoteHue MoteHue force-pushed the support-persisting-octavia-ca branch from 8aa76ba to 9958a80 Compare November 18, 2025 16:26
Comment on lines 71 to 74
Octavia uses mutual TLS to secure communication between the amphorae and
Octavia services. It uses a private CA to sign both client and server
certificates. We use the kolla-ansible built-in support for generating these
certificates:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a bit clearer about if you should do this to refresh certificates or if it's only needed for an initial deployment. It just kinda jumps into commands without saying what they're going to do and why we run them

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added more context

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the record, I'd prefer these to be ansible playbooks, but I don't really want to hold this PR up to change it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do agree playbooks would be nice, but I don't really have the time right now to rewrite these, this is just me extracting existing scripts from a customer site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Backport needed Caracal Targets the Caracal OpenStack release documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants