Add RHOSO cluster_id to be set in the ansible variables #1642
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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