Epic Goal*

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

Google introduced support for a new disk type "hyperdisk-balanced-high-availability" we need to support it in OCP.

Hyperdisk Balanced High Availability volumes to synchronously replicate data across two zones in the same region. You can also use Hyperdisk Balanced High Availability volumes in scenarios that require write access to the same volume multiple zones.

https://docs.cloud.google.com/compute/docs/disks/hd-types/hyperdisk-balanced-ha

We're not introducing it as default nor automatically create a SC, admin would need to create a new SC

 
Why is this important? (mandatory)

What are the benefits to the customer or Red Hat?   Does it improve security, performance, supportability, etc?  Why is work a priority?

hyperdisk-balanced-high-availability is important for customers who want data replication; also we need to be in sync with what GCP offers to the marker.

 
Scenarios (mandatory) 

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

1. As an admin I want to offer hyperdisk-balanced-high-availability to my users through a new SC
2. As a user I want to deploy applications backed by hyperdisk-balanced-high-availability in order to get data redundancy.

 
Dependencies (internal and external) (mandatory)

What items must be delivered by other teams/groups to enable delivery of this epic. 

We need to enable it in the driver see STOR-2792

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 - STOR
• QE - STOR
• PX - 
• Others -

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

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”