Epic Goal

• Transfer ownership of "delivering LVMS on MicroShift" from the MicroShift team to the LVMS team.

Why is this important?

• We should treat MicroShift as a base layer and ensure that layered product delivery is managed by the team that owns the layered product, in conjunction with the MicroShift team for assistance and advice.

Scenarios

1. The LVMS team will be responsible for updating the image references and manifests in the microshift-storage RPM for new releases.
2. The LVMS team will be responsible for ensuring that the public images used by microshift-storage are made available to users with a regular OCP pull secret (not a CI secret).
3. The LVMS team will be responsible for ensuring that the public images used by public releases of microshift-storage are kept online for the lifetime of the MicroShift release and not deleted.
4. The RPM definition can continue to live in the openshift/microshift repository, to simplify the package build and delivery.
5. The MicroShift team will provide advice, guidance, reviews, and other support to facilitate this work.

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. ...

Previous Work (Optional):

1. ...

Open questions::

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• 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>