This spike is to try to identify ways to ingest OpenStack cluster-level data to Insights.

I connected with the Insights and CCX team and they gave me some guidance.

A potential way to accomplish this could be to add OSP CRD(s) to the OIO (OpenShift Insights Operator) gatherers. A PR can be sent and we can use "Cluster-bot" Slack App to spin up an OCP cluster that gathers data from our CRDs.

Things to investigate as part of this spike:

• Can we use the OSP meta operator to collect all the info we want to expose and have this gathered by the OIO? Or any other alternative (vs. multiple gatherers, or a dedicated operator for OSP Insights)
• Any potential limits (the Insights team mentioned, that they collect the data every 2 hours and there's a limit of 8MB per archive)

I'd suggest having a small PoC that can feed basic info about an OSP cluster such as the topology ([eg|https://github.com/openshift/insights-operator/tree/master/docs/insights-archive-sample/config/node]. of OCP cluster topology). As a bonus, we can try to query this data via Trino (eg. what's the max number of nodes of an OSP deployment).

For us to verify if the data is gathered we can ping the Insights team (contact tremes1@redhat.com) with the cluster ID (created by cluster-bot) and they should be able to give us more information.

To consider this Spike as done we should have written document https://docs.google.com/document/d/1r3sC_7ZU7qkxvafpEkAJKMTmtcWAwGOI6W_SZGkvP6s/edit with info about:

• list of options to implement, with pros and cons enumerated
• decision about preferable path to go with (after discussing various options with the Insights team representative,
• PoC showing that choosen solution works and we can move on with it.