Epic Goal*

What is our purpose in implementing this?  What new capability will be available to customers?

Per OCPSTRAT-1278, we want to support OCP on C3 instance type (baremetal) in order to enabled OCP virt on GCP. The C3 instance type supports the hyperdisk-balanced disks.

The goal is to validate that our GCP CSI operator can deploy the driver on C3 baremetal nodes and function as expected.

As OCP virt requires RWX to support VM live migration, we need to make sure the driver works with this access type with volumeType block.

 
Why is this important? (mandatory)

Product level priority to enabled OCP virt on GCP. Multiple customers are waiting for this solution. See OCPSTRAT-1278 for additional details.

 
Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. As a customer, I want to run OpenShift Virtualization on OpenShift running on GCP baremetal instance types.

 
Dependencies (internal and external) (mandatory)

PD CSI driver to support baremetal / C3 instance type

PD CSI driver to support block RWX

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - STOR
• Documentation - VIRT / Installer
• QE - STOR
• PX - 
• Others -

Acceptance Criteria (optional)

GCP PD CSI on C3 nodes passes the regular CSI tests + RWX with volumeType block. Actual VM live migration tests will be done by the virt team.

Drawbacks or Risk (optional)

Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be "Release Pending"