Goal: 

• Adoption jobs based on CI framework  adoption_osp_deploy (the Uni jobs as yet) need to able to configure and execute the data-plane-adoption test suite with multi-cell variables. (Currently the Uni jobs need to use FR2 branch of data-plane-adoption repo, they don't work with main branch.)

Environment:

• Source: RHOSO 17.1 with RHEL 9.2
• Destination: RHOSO 18.0 with RHEL 9.2

Request:

• Implement the required infrastructure changes in https://github.com/openstack-k8s-operators/ci-framework/tree/main/scenarios/adoption
• Implement the required OSP configuration in https://github.com/openstack-k8s-operators/data-plane-adoption/tree/main/scenarios
• Ensure architecture automation is defined similar to https://github.com/openstack-k8s-operators/architecture/blob/main/automation/vars/uni05epsilon.yaml#L24 with separate Greenfield versus Adoption automation steps

Acceptance Criteria:

• Adoption Uni job executed via CI framework configures the data-plane-adoption test suite correctly with new variables introduced as part of multi-cell work.
  • The adoption workflow is executed successfully in this scenario.
  • It adopts multicell tripleo (osp17.1) into rhoso 18
  • The OSP topology/configuration implemented is similar enough to the target RHOSO topology/configuration that it does not cause a service dysfunction
• It IS necessary to make a pilot Uni job deploying multiple cells as part of this story, but it may be not included into promotion/component etc pipelines.
• Multi cell tripleo topology from install yamls is translated into osp deploy plugin of ci-framework in the process

Note:
A fully working tempest result is out of scope for this Epic. It is crucial that it is out of scope to keep this Epic's work at a manageable size.

Further context:

• Multi-cell support was finished in https://github.com/openstack-k8s-operators/data-plane-adoption/pull/517
• uni05epsilon currently tests 3 cell greenfield deployment, so the adoption job should also test 3 cells by using the same uni05epsilon naming