Epic Goal

• Add tech-preview support to install OpenShift on OpenStack with multiple failure domains.

Why is this important?

• Multiple (large) customers are requesting this configuration and installation type to provide a higher level of high availability.
• This could be a blocker for https://issues.redhat.com/browse/OSASINFRA-2999 even though technically that feature should be possible without this

Scenarios

1. Spread the control plane across 3 domains (each domain has a defined storage / network / compute configuration)
2. Indirectly we'll inherit from the features proposed by https://issues.redhat.com/browse/OCPCLOUD-1372

1. 1. Automatically add extra node(s) to the control plane
   2. Remove node(s) from the control plane
   3. Recover from a lost node incident

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. https://issues.redhat.com/browse/OCPCLOUD-1372 to be finished and delivered in 4.12

Previous Work (Optional):

1. https://issues.redhat.com/browse/OSASINFRA-2997

Open questions::

none for now.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Enhancement - https://github.com/openshift/enhancements/pull/1167
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>