Skip to content

Multi-namespace test#693

Closed
vakwetu wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
vakwetu:add-skmo
Closed

Multi-namespace test#693
vakwetu wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
vakwetu:add-skmo

Conversation

@vakwetu
Copy link
Copy Markdown
Contributor

@vakwetu vakwetu commented Feb 6, 2026

Add multi-namespace SKMO support

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

Depends-On: openstack-k8s-operators/ci-framework#3684

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/7722c30130f04cd09027a0b3923bf965

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 3m 42s

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b7107ca6b6b9463abb5f2e6a1502b487

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 3m 20s

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/e80052b9e68442a1bc0f660dfab2f580

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 4m 08s

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2b22395d6dcb4815b5a96d9bf4ea949f

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 3m 26s

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/f23489c0613b4c5e99b5b475942ddecb

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 3m 52s

@vakwetu vakwetu changed the title Initial multi-namespace test Multi-namespace test Mar 10, 2026
@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/bfaeb55987b540058763ff4030f3d2e0

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 3m 50s

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b87d1836b34846cfa9469f80cb3c9327

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 3m 13s

@vakwetu
Copy link
Copy Markdown
Contributor Author

vakwetu commented Mar 10, 2026

recheck

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/0de17485fe724363b91a0ed36ca28816

✔️ noop SUCCESS in 0s
rhoso-architecture-validate-multi-namespace-skmo FAILURE in 3m 24s

Comment thread automation/vars/multi-namespace-skmo.yaml
Comment on lines +41 to +42
# Allow src_file paths to traverse outside the stage path
_path = (source / f).resolve()
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approving this sets precedence that .. traversal in src_file is an acceptable pattern.

I think that's OK. I think it's good to promote DRY instead of requiring the same files to be copied (avoid drift).

An alternative is to do a symlink, but I think that would make things more messy. Let's just be clear that there will be cases where from other VAs/DTs could be used.

@abays
Copy link
Copy Markdown
Contributor

abays commented Mar 23, 2026

@vakwetu Would you prefer to merge this first, or do you want to just bundle everything together in #716 like it seems you are doing?

@vakwetu
Copy link
Copy Markdown
Contributor Author

vakwetu commented Mar 23, 2026

@abays I'm still testing #716 so I'd prefer to go ahead and merge this first. In 716, I was just getting a head start in case I got it all tested beforehand.

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

This change depends on a change that failed to merge.

Change openstack-k8s-operators/ci-framework#3684 is needed.

Copy link
Copy Markdown
Contributor

@fultonj fultonj left a comment

Choose a reason for hiding this comment

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

This looks like a good VA and a bulk of the work is done. I'd like to request some markdown files however.

There's no markdown files in this PR explaining what it is and what it does.

Please add them. Use this as an example:

https://github.com/openstack-k8s-operators/architecture/blob/main/examples/va/hci/README.md

Anyone should be able to clone this repo and use kustomize to build the example CRs by following the read README files. We shouldn't require people to read automation/vars/multi-namespace-skmo.yaml

Comment thread examples/va/multi-namespace-skmo/control-plane/kustomization.yaml
Comment on lines +41 to +42
# Allow src_file paths to traverse outside the stage path
_path = (source / f).resolve()
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approving this sets precedence that .. traversal in src_file is an acceptable pattern.

I think that's OK. I think it's good to promote DRY instead of requiring the same files to be copied (avoid drift).

An alternative is to do a symlink, but I think that would make things more messy. Let's just be clear that there will be cases where from other VAs/DTs could be used.

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 hooks for cross-region CA trust, transport URL setup,
  and barbican-keystone-listener configuration
- 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
- README documenting the SKMO scenario and deployment stages

Depends-On: openstack-k8s-operators/ci-framework#3684

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Ade Lee <alee@redhat.com>
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Mar 23, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vakwetu
Once this PR has been reviewed and has the lgtm label, please ask for approval from fultonj. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

This change depends on a change that failed to merge.

Change openstack-k8s-operators/ci-framework#3684 is needed.

@vakwetu
Copy link
Copy Markdown
Contributor Author

vakwetu commented Mar 23, 2026

comments addressed. added wip till testing is complete

@vakwetu
Copy link
Copy Markdown
Contributor Author

vakwetu commented Mar 23, 2026

recheck

@vakwetu vakwetu closed this Mar 27, 2026
@vakwetu
Copy link
Copy Markdown
Contributor Author

vakwetu commented Mar 27, 2026

This PR was superseded by #716

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants