OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• User can install OpenShift using HW version 15 for the VMs created so that the vSphere CSI driver works.

Why is this important?

• If the installer does not create the VMs using HW version 15, then the user must manually stop each VM in order to chnage the HW version post-install. The problem with not having HW15 whenever possible by default is - when CSI migration for vSphere drivers is enabled, then users will have broken clusters by default with non-working storage.

Scenarios

• User installs a OCP-4.10 cluster via IPI on vSphere >=6.7u3 and it has a functional CSI driver installed with all VMs on HW version 15.
• Users installs a OCP-4.10 cluster via UPI on vSphere >= 6.7u3 then it should have functional CSI driver with all VMs on HW version 15.
• User upgrades a OCP-4.9 cluster to OCP-4.10, then ideally we would like all VMs to be on HW 15 whenever supported by ESXi version, but if we can't upgrade HW version automatically, we need to provide manual instructions to the user about how they can upgrade the HW version of their VMs manually.

Acceptance Criteria

• CI - MUST be running successfully with tests automated with HW version 15 using IPI install.
• Release Technical Enablement - Provide necessary release enablement details and documents.
• As a admin if I install OCP-4.10 on vSphere >= 6.7u3, then all my VMs should be on HW version 15.
• As a admin if I install OCP-4.10 on vSphere >= 6.7u3, then all my VMs should be on HW version 15.
• As a admin if I upgrade a OCP-4.9 cluster to OCP-4.10 on vSphere >= 6.7u3 then either all my VMs should automatically be upgraded or I should have necessary documentation about how to manually upgrade HW version of my OCP vms.

Dependencies (internal and external)

1. The HW version 15 also depends on vSphere >=6.7u3. If vCenter server is on higher version that ESXI servers, we could have heterogeneous clusters and in which case we should pick highest common version supported by all hosts.

Previous Work (Optional):

1. …

Open questions::

1. Should the HW version selection be done automatically based on the capabilities of the vCenter? Or should the user be required to opt-in to using HW version 15?
2. Will the RHCOS image be updated to omit the HW version?

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>