Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
vakwetu
force-pushed
the
add_skmo
branch
2 times, most recently
from
5c879e4 to
4300f16
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b7e9a45c2dc540e683237f9d199a301c ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 01m 57s |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/9a0c3d521a444791a9cb4da2cf7cedca ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 15m 25s |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/17da5110aa71420dbf164b2d3651f1bf ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 27m 13s |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2382ae10dbf24bc185e36fba76f1ffc5 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 34s |
|
recheck |
vakwetu
force-pushed
the
add_skmo
branch
2 times, most recently
from
ddb6a04 to
7da97ce
Compare
Configure the multi-namespace SKMO scenario with: - SKMO-specific control-plane kustomization for the central region with barbican-keystone-listener pool_name and RabbitMQ memory reduction (4Gi -> 2Gi) for compact clusters - Barbican keystone listener pool_name configuration for both central (regionOne) and leaf (regionTwo) regions - Automation stages updated to reference SKMO-specific paths - Post-stage hook for populating cross-region transport URL - Wait conditions adjusted for parallel deployment - Correct keystone endpoint values for leaf region - CA trust configuration between central and leaf regions - Symlink net-env for SKMO to reuse multi-namespace networking Depends-On: openstack-k8s-operators/ci-framework#3684 Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Ade Lee <alee@redhat.com>
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/9e5fc4b91c634fd3bf5d511b0afa0c50 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 08m 47s |
…ooks Add support for Shared Keystone Multi-region OpenStack (SKMO) deployments with cross-region Barbican keystone listener: Playbooks: - prepare-leaf.yaml: Pre-stage hook that creates a TransportURL CR in the central region for the leaf's barbican-keystone-listener, copies the generated secret to the leaf namespace, extracts rootca-internal CA cert from central and adds it to the leaf's custom-ca-certs bundle, and waits for central Keystone and openstackclient readiness with retry logic - configure-leaf-listener.yaml: Post-stage hook that patches the leaf OpenStackControlPlane with the cross-region transport_url for the barbican-keystone-listener - trust-leaf-ca.yaml: Post-stage hook that extracts the leaf region's rootca-public and rootca-internal CA certs and adds them to the central region's custom-ca-certs bundle - ensure-central-ca-bundle.yaml: Ensures the central CA bundle secret exists before the leaf control plane deployment Scenario: - va-multi-skmo.yml reproducer scenario configuration - multi-namespace-skmo architecture scenario symlink Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Ade Lee <alee@redhat.com>
Configure the multi-namespace SKMO scenario with: - SKMO-specific control-plane kustomization for the central region with barbican-keystone-listener pool_name and RabbitMQ memory reduction (4Gi -> 2Gi) for compact clusters - Barbican keystone listener pool_name configuration for both central (regionOne) and leaf (regionTwo) regions - Automation stages updated to reference SKMO-specific paths - Post-stage hook for populating cross-region transport URL - Wait conditions adjusted for parallel deployment - Correct keystone endpoint values for leaf region - CA trust configuration between central and leaf regions - Symlink net-env for SKMO to reuse multi-namespace networking Depends-On: openstack-k8s-operators/ci-framework#3684 Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Ade Lee <alee@redhat.com>
1 participant
Add multi-namespace SKMO scenario and playbooks
Add support for Shared Keystone Multi-region OpenStack (SKMO)
deployments with cross-region Barbican keystone listener:
Playbooks:
in the central region for the leaf's barbican-keystone-listener,
copies the generated secret to the leaf namespace, extracts
rootca-internal CA cert from central and adds it to the leaf's
custom-ca-certs bundle, and waits for central Keystone and
openstackclient readiness with retry logic
leaf OpenStackControlPlane with the cross-region transport_url
for the barbican-keystone-listener
region's rootca-public and rootca-internal CA certs and adds
them to the central region's custom-ca-certs bundle
secret exists before the leaf control plane deployment
Scenario: