-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
Integrate Watcher Operator in OpenStack Operator
-
False
-
-
False
-
Not Selected
-
Proposed
-
?
-
Done
-
RHOSSTRAT-250 - RHOSO18 Realtime Dynamic Scheduling and workload optimisation - GA
-
?
-
rhos-workloads-evolution
-
?
-
0% To Do, 0% In Progress, 100% Done
-
-
Enhancement
-
Done
-
-
Goal:
- While Watcher is in Technology Preview support status, the watcher-operator is managed out of the OpenStack Operator. It's installed as standalone and the Watcher CR is managed out of the OpenStack Operator CRDs (openstackcontrolplane, openstackversion, etc...)
- In order to have Watcher as a fully supported service in RHOSO it needs to be integrated in the OpenStack Operator as any other service operator.
Acceptance Criteria:
- Watcher is integrated into OpenStack Operator following same pattern that the rest of service operators.
- Watcher operator deployed via OpenStack CR
- Watcher service deployment is managed via CRs OpenStackControlPlane, OpenStackVersion, etc...
- Move CI jobs to similar approach than the rest of service operators instead of post_deployment hook.
- Document the process to move from TechPreview Watcher Operator to fully supported one (likely, removing the Watcher CR and uninstallation of the operator before updating the OpenStack operator)
Open questions:
- What technical debt there is in watcher-operator that requires to be managed before integration?.
- Requirements in terms of documentation?
- Integration of bundles, csv installation, webhooks, etc..