Template:

Networking Definition of Planned

Epic Template descriptions and documentation

Epic Goal

Move the configure-ovs alternative feature from tech preview to GA.

Why is this important?

There are numerous customers waiting for this feature, and while we wanted to maintain some control over initial adoption by shipping it as tech preview, it is also important to open it up to the broader customer base as quickly as possible.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority+ is set by engineering
• Epic must be Linked to a +Parent Feature
• Target version+ must be set
• Assignee+ must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.
• Ensure that our documentation is sufficient in terms of what is and is not allowed, as well as what is required for the customer to do in order for the feature to work as intended.
• Ideally we will have worked with a small number of customers to ensure the feature as it stands meets their needs.

...

Dependencies (internal and external)

1.

...

Previous Work (Optional):

1. https://issues.redhat.com/browse/OPNET-282

Open questions::

1. Will enough customers have tried the tech preview by the time 4.17 GAs? Typically there is a lag between when a release ships and when customers start to adopt it.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>