Add RHOSO cluster_id to be set in the ansible variables#1642
Add RHOSO cluster_id to be set in the ansible variables#1642slawqo wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
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]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: slawqo 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 |
|
@slawqo: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/14b5d2e7525f468eb96b6f00a46e4749 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 57m 52s |
|
PR needs rebase. DetailsInstructions 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. |
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