Epic Goal*

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

The IBM Power team would like to add support for the CIFS/SMB driver operator due to client requests.
The containers are currently built for ppc64le; however the operator does not include ppc64le.

Add metadata label to include ppc64le

the IBM Power QE team agreed to do the PR + testing. Storage team will do just the reviews.

 
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?

We have customer's request to use SMB CSI with OCP on ppc64le

 
Scenarios (mandatory) 

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

1. As an OCP on ppc64le admin i would like to deploy SMB CSI so that users can consume SMB shares.

 
Dependencies (internal and external) (mandatory)

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

We need ppc64le hardware to confirm it works as expected. The IBM Power QE team agreed to do the testing

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 - MULTIARCH
• PX - 
• Others -

Acceptance Criteria (optional)

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

SMB CSI CI returns green when used with OCP on ppc64le

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.

The stor team does not have access to ppc64le.

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”