Feature Overview (aka. Goal Summary)  

SMC-D and SMC-R are high speed connections implemented especially connecting Linux environments with each other. Especially when it comes to connections among LPARs and with SMC-R connections to z/OS.

Enablement for SMC-D/R is the same implementation and in a first stage support can be given w/o any change by just adding the device to the container via multus. In a second stage, it should be considered if there are OCP components which could be enabled to make use of SMC-D/R in case a device is connected.

Goals (aka. expected user outcomes)

SMC-D/R should be enabled in OpenShift

Requirements (aka. Acceptance Criteria):

SMC-D/R should work in OpenShift

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.