Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-14852

Integrate Watcher Operator in OpenStack Operator

XMLWordPrintable

    • Integrate Watcher Operator in OpenStack Operator
    • False
    • Hide

      None

      Show
      None
    • 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
    • Hide
      .The Optimize service (watcher) is now integrated into the OpenStack Operator

      Before this update, the Optimize service (watcher) was provided as a technical preview that was installed with its own Operator. With this update, the Optimize service is now integrated into the OpenStack Operator and is fully supported.

       If you have installed the Optimize service as a technical preview, you must remove the Optimize service Operator and any custom resource of kind `Watcher` before updating your RHOSO deployment to 18.0.14 or later.
      Show
      .The Optimize service (watcher) is now integrated into the OpenStack Operator Before this update, the Optimize service (watcher) was provided as a technical preview that was installed with its own Operator. With this update, the Optimize service is now integrated into the OpenStack Operator and is fully supported.  If you have installed the Optimize service as a technical preview, you must remove the Optimize service Operator and any custom resource of kind `Watcher` before updating your RHOSO deployment to 18.0.14 or later.
    • 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..

              amoralej1@redhat.com Alfredo Moralejo Alonso
              amoralej1@redhat.com Alfredo Moralejo Alonso
              rhos-workloads-evolution
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: