Skip to content

Add top-level notificationsBus configuration#694

Merged
arxcruz merged 1 commit intoopenstack-k8s-operators:mainfrom
lmiccini:rmqchanges
Feb 25, 2026
Merged

Add top-level notificationsBus configuration#694
arxcruz merged 1 commit intoopenstack-k8s-operators:mainfrom
lmiccini:rmqchanges

Conversation

@lmiccini
Copy link
Contributor

@lmiccini lmiccini commented Feb 7, 2026

  • Add notificationsBus.cluster to all telemetry-enabled deployments
    • Use rabbitmq-notifications for va/hci and dt/uni05epsilon (dedicated cluster)
    • Use rabbitmq for all other deployments (default cluster)
  • Add notificationsBus.cluster: rabbitmq to all other service-values files as placeholder to enable kustomize component to work universally
  • Create lib/control-plane/messaging-bus kustomize component to inject notificationsBus from service-values ConfigMap into spec.notificationsBus
  • Remove deprecated nova.notificationsBus replacements from kustomization files (replaced by top-level spec.notificationsBus)
  • Update va/hci and dt/uni05epsilon to use new notificationsBus.cluster format instead of deprecated notificationsBusInstance

@lmiccini lmiccini requested a review from a team as a code owner February 7, 2026 15:13
@openshift-ci openshift-ci bot requested review from cjeanner and raukadah February 7, 2026 15:13
@softwarefactory-project-zuul
Copy link
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/4d56c550362b450cb0fd222c6ff30b4e

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-bgp-l3-xl SUCCESS in 4m 44s
✔️ rhoso-architecture-validate-bgp-l3-xl-adoption SUCCESS in 4m 22s
✔️ rhoso-architecture-validate-bgp_dt01 SUCCESS in 5m 08s
✔️ rhoso-architecture-validate-bgp_dt04_ipv6 SUCCESS in 5m 35s
✔️ rhoso-architecture-validate-bmo01 SUCCESS in 4m 50s
✔️ rhoso-architecture-validate-dcn SUCCESS in 4m 15s
✔️ rhoso-architecture-validate-dz-storage SUCCESS in 6m 49s
rhoso-architecture-validate-hci FAILURE in 4m 45s
✔️ rhoso-architecture-validate-hci-adoption SUCCESS in 5m 37s
✔️ rhoso-architecture-validate-multi-namespace SUCCESS in 5m 30s
✔️ rhoso-architecture-validate-nfv-ovs-dpdk-sriov-adoption SUCCESS in 5m 29s
✔️ rhoso-architecture-validate-nfv-ovs-dpdk-sriov-hci SUCCESS in 5m 32s
✔️ rhoso-architecture-validate-nova-three-cells SUCCESS in 4m 38s
✔️ rhoso-architecture-validate-nova01alpha SUCCESS in 5m 05s
✔️ rhoso-architecture-validate-nova02beta SUCCESS in 5m 58s
✔️ rhoso-architecture-validate-nova04delta SUCCESS in 5m 42s
✔️ rhoso-architecture-validate-nova04delta-adoption SUCCESS in 5m 28s
✔️ rhoso-architecture-validate-nvidia-mdev SUCCESS in 3m 52s
✔️ rhoso-architecture-validate-nvidia-vfio-passthrough SUCCESS in 3m 40s
✔️ rhoso-architecture-validate-nvidia-vfio-passthrough-adoption SUCCESS in 4m 08s
rhoso-architecture-validate-osasinfra FAILURE in 4m 34s
✔️ rhoso-architecture-validate-osasinfra-ipv6 SUCCESS in 6m 14s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 5m 56s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 6m 04s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov-2nodesets SUCCESS in 4m 42s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 SUCCESS in 4m 28s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets SUCCESS in 4m 40s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov-networker SUCCESS in 4m 29s
✔️ rhoso-architecture-validate-pidone SUCCESS in 4m 29s
✔️ rhoso-architecture-validate-sriov SUCCESS in 4m 35s
rhoso-architecture-validate-uni01alpha FAILURE in 4m 18s
✔️ rhoso-architecture-validate-uni01alpha-adoption SUCCESS in 5m 34s
✔️ rhoso-architecture-validate-uni02beta SUCCESS in 5m 57s
✔️ rhoso-architecture-validate-uni02beta-adoption SUCCESS in 3m 54s
✔️ rhoso-architecture-validate-uni04delta SUCCESS in 5m 37s
✔️ rhoso-architecture-validate-uni04delta-adoption SUCCESS in 5m 45s
rhoso-architecture-validate-uni04delta-ipv6 FAILURE in 5m 47s
✔️ rhoso-architecture-validate-uni04delta-ipv6-adoption SUCCESS in 4m 21s
rhoso-architecture-validate-uni05epsilon FAILURE in 5m 07s
✔️ rhoso-architecture-validate-uni05epsilon-adoption SUCCESS in 4m 17s
✔️ rhoso-architecture-validate-uni06zeta SUCCESS in 6m 18s
✔️ rhoso-architecture-validate-uni06zeta-adoption SUCCESS in 5m 38s
✔️ rhoso-architecture-validate-uni07eta SUCCESS in 5m 42s
✔️ rhoso-architecture-validate-uni07eta-adoption SUCCESS in 4m 50s
✔️ rhoso-architecture-validate-uni09iota SUCCESS in 5m 58s
✔️ rhoso-architecture-validate-uni09iota-adoption SUCCESS in 4m 54s

@lmiccini lmiccini force-pushed the rmqchanges branch 3 times, most recently from 4896475 to 50459b1 Compare February 10, 2026 12:19
@bogdando
Copy link
Contributor

please explain the template repurposing, in ci-framework-jobs downstream there is a lots of configurations relying on paths with template:, so the impact of this change is huge

This commit introduces a new messaging bus configuration structure
while replacing deprecated field names with their modern equivalents.

Changes:
- Add notificationsBus.cluster to all service-values files
  - Use rabbitmq-notifications for va/hci and dt/uni05epsilon (dedicated cluster)
  - Use rabbitmq for all other deployments (default cluster)
- Replace cellMessageBusInstance with messagingBus.cluster in nova cells
- Replace notificationsBusInstance with top-level notificationsBus.cluster
- Create lib/control-plane/messaging-bus kustomize component to inject
  notificationsBus from service-values ConfigMap into spec.notificationsBus
- Update va/hci and dt/uni05epsilon kustomization files to use new
  messaging-bus component instead of manual notificationsBusInstance replacement
- Update documentation (README files) to reflect new messagingBus structure

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Copy link
Contributor

@arxcruz arxcruz left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@openshift-ci
Copy link

openshift-ci bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: arxcruz, lmiccini
Once this PR has been reviewed and has the lgtm label, please assign cjeanner for approval. 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

@arxcruz arxcruz merged commit 6c0383e into openstack-k8s-operators:main Feb 25, 2026
6 checks passed
@karelyatin
Copy link
Contributor

/cherry-pick 18.0-fr5

@openshift-cherrypick-robot

@karelyatin: new pull request created: #703

Details

In response to this:

/cherry-pick 18.0-fr5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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.

5 participants