Epic Goal*

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

Test and document cross subscription access with Azure File CSI. In some environments OCP and the storage are not deployed with the same subscription.

 
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?

Support advanced model from large companies where different resources are spread across multiple subscriptions.

We already support this model with EFS, see STOR-990, as per OCP hybrid cloud strategy we should have similar capabilities and experience across the major public clouds.

 
Scenarios (mandatory) 

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

1. As an architect,  In my corporate structure each department have their own Azure subscription. I want to allow any internal organisation to use their own storage accounts with their applications deployed on a centrally-managed Openshift platform 

 
Dependencies (internal and external) (mandatory)

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

Confirm if this is testonly or it requires eng work.

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

Acceptance Criteria (optional)

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

Same test as STOR-990, the Azure File CSI driver should perform the same whether the storage is on the same subscription ID as OCP or not.

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”