Feature Overview (aka. Goal Summary)  

MicroShift can be configured to work in offline scenarios (i.e. no active NIC, no active IP address). This is currently only a documented procedure of necessary configuration steps. This feature is about simplifying the with some supported automation

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

The goal of this feature is to supply some supported, simple automation to configure MicroShift correctly that it still works in offline scenarios. 

There are several ways on how to achieve this goal:

1. We provide a rpm package "microshift-offline" which includes the necessary scripts to create the offline configuration. That package would need to work with both rpm and ostree installations. The configuration would also need to work / support online scenarios.
2. Scripts/Tools to switch offline mode on/off, .e.g. an integration into the "microshift" cmd line tool, e.g. "microshift offline enable|disable"

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

<enter general Feature acceptance here>

Use Cases (Optional):

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

<your text here>

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.

<your text here>

Out of Scope

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

<your text here>

Background

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

<your text here>

Customer Considerations

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

<your text here>

Documentation Considerations

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. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, 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.

<your text here>