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

As a cloud operator I would like to adopt my existing 17.1 OpenStack environment where the control plane is running on RHEV so that I am on a Red Hat supported platform & architecture.

XMLWordPrintable

    • As an Adoption team member, I want automation to deploy OpenStack 17.1 with control plane on RHEV that can be networked together with OpenShift, so that I can test adopting that deployment into podified 18.0.
    • 42
    • False
    • False
    • OSPRH-3714Red Hat OpenStack 18.0 Data Plane Adoption [FR1]
    • Committed
    • No Docs Impact
    • To Do
    • OSPRH-3714 - Red Hat OpenStack 18.0 Data Plane Adoption [FR1]
    • openstack-operator-container-1.0.5-1
    • Committed
    • Committed
    • 0% To Do, 0% In Progress, 100% Done
    • Release Note Not Required
    • Automated
    • 2024Q2
    • Rejected

      The goal here is to create a RHV VM set onto which we deploy OSP 17.1 source environment with controller fencing configured, and an OpenShift that will serve as the destination for adopting the control plane, and verify that Adoption can be performed from source to destination by running the Adoption test suite on this setup. We do not need this set up to be "spin up on demand per CI job", but we do need it to be resettable to initial state (either by restoring from snapshot or other form of clean up) so that we can run jobs on it serially one after another. And the setup should be re-deployable relatively easily in case it breaks (there should be at least documentation for it if not automation).

      Test hardware requirements

      Definition of Done:

      • A reproducible source OSP 17.1 environment setup, using fencing configured to use RHEV.
      • A reproducible destination RHOSO 18.0 environment setup.
      • A zuul integration job that executes the Adoption test suite to run the Adoption process.
      • No functional testing is required. The purpose of this job is to validate the workflow, not the function of the cloud.
      • The integration job must be periodically run, and added to release criteria.
      • Content used must be from downstream in order to validate the content that we are proposing to release to customer.

              rhn-engineering-sgolovat Sergii Golovatiuk
              rhn-engineering-jpretori Jesse Pretorius
              Archana Singh Archana Singh
              rhos-dfg-upgrades
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: