Skip to content

Conversation

@slawqo
Copy link
Contributor

@slawqo slawqo commented Oct 6, 2025

To integrate data insights data from the control plane (OCP) collected by the insights-operator and data from the EDPM nodes, which is collected by the insights-client we need to have some kind of RHOSO cluster_id stored in the EDPM nodes somewhere.
This patch proposes to generate such RHOSO cluster_id as <ocp_cluster_id>: as such pair should clearly identify single RHOSO cluster because there can not be more that one OpenStack cluster deployed in single OCP namespace.
This ID is then set as ansible variable in the ansible group vars in the generated inventory for each OpenStackDataPlaneNodeSet created and edpm ansible role will then be able to write it on the edpm nodes.

Related: #OSPRH-19918

To integrate data insights data from the control plane (OCP)
collected by the insights-operator and data from the EDPM nodes, which
is collected by the insights-client we need to have some kind of RHOSO
cluster_id stored in the EDPM nodes somewhere.
This patch proposes to generate such RHOSO cluster_id as
<ocp_cluster_id>:<namespace> as such pair should clearly identify single
RHOSO cluster because there can not be more that one OpenStack cluster
deployed in single OCP namespace.
This ID is then set as ansible variable in the ansible group vars in the
generated inventory for each OpenStackDataPlaneNodeSet created and
edpm ansible role will then be able to write it on the edpm nodes.

Related: #OSPRH-19918
Signed-off-by: Slawek Kaplonski <[email protected]>
@openshift-ci openshift-ci bot requested review from fultonj and olliewalsh October 6, 2025 14:26
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

@slawqo: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/functional 9cb4291 link true /test functional
ci/prow/precommit-check 9cb4291 link true /test precommit-check
ci/prow/openstack-operator-build-deploy-kuttl-4-18 9cb4291 link true /test openstack-operator-build-deploy-kuttl-4-18
ci/prow/openstack-operator-build-deploy-kuttl 9cb4291 link true /test openstack-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@softwarefactory-project-zuul
Copy link

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/14b5d2e7525f468eb96b6f00a46e4749

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 57m 52s
podified-multinode-edpm-deployment-crc FAILURE in 36m 19s
cifmw-crc-podified-edpm-baremetal FAILURE in 1h 29m 30s
adoption-standalone-to-crc-ceph-provider FAILURE in 2h 34m 07s
openstack-operator-tempest-multinode FAILURE in 1h 40m 10s

@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

2 participants