The ShiftStack team deals in two separate matters:

• The OpenStack-specific part of the OpenShift installer
• The OpenStack compatibility layer for OpenShift

The output of the team is not OpenShift features, but rather making OpenShift leverage OpenStack features.

Since we don't add new capabilities to OpenShift, the Conformance test suite is for us a mere regression-test suite.

In order to test the features we implement, we need a framework that interrogates the underlying OpenStack infrastructure to verify OpenStack-specific invariants.

For example:

• check that an instance is booted from volume when `install-config` says so
• check that the master nodes are created in a server group with the policy defined in `install-config`
• check that Octavia is correctly set when used as a load-balancer in OpenShift.

The OpenStack-specific tests will live in their own repository, of which we will have ownership.

This repository will contain tests created by developers while developing features and bugfixes, alongside with QE when performing automated verification.

The tests will be compiled in a binary (initially, in one single suite); then we will then instrument Prow to execute them in their own step in the OpenStack CI workflows.

The expected outcome is: OpenStack-specific tests running right after the canonical Conformance suite, in every run of `e2e-openstack`, in presubmits and periodics alike, without the need for spinning any additional cluster.

This work will support the OpenShift organisation in the effort to phase out Origin as a home for all the OpenShift tests, and to transition towards federated suites owned by the teams.