Feature Overview  
As part of RHOSO 19, we want to simplify delivery and enable service updates to new upstream versions.  In order to make that possible, we need to shift from our container model to a Source to Image model

Goals:

• All containers are Source to Image (multi-stage builds are ok)
• Only 2 total layers:  1 base image common to all services and service leaf containers  (multiple layers causes significant build system challenges)
• All consistency items (UID/GID, etc) should be in base
• Coordinate/Investigate upstream layout with Release Delivery to ease import process
• repos should be container files directly, not through a tool like TCIB

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

 
Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view
…

• The container structure has been changed to use a base container as the first layer and then service containers built on top of that.
• The container images have been tested as part of the overall release of the product.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.

• The testing of this feature will be included as part of the over all testing of the release and will not be included here.

Documentation Considerations __(Initial completion while in Refinement status):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
The list of container images that are included with the list will have to be revised for the OSP 18.0 version. There should be no other customer facing impact.

Questions to Answer __(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>