• Proposed title of this feature request
  • Document Impact of OCP updates on RHOSO control plane and dataplane
• What is the nature and description of the request?
  • overall idea is to have a section like we have in previous OSP upgrades documentation[1] and mention all the impacts expected as part of OCP updates on RHOSO control and dataplane. The spike https://issues.redhat.com/browse/OSPRH-14687 covers just one aspect of it i.e impact(ping losses during worker nodes reboot) on OSP centralized traffic and it's described in the comment https://issues.redhat.com/browse/OSPRH-14687?focusedId=26877746&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26877746

https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html-single/framework_for_upgrades_16.2_to_17.1/index#preparing_for_overcloud_service_downtime

• Why does the customer need this? (List the business requirements here)
  • Provides knowledge about impacts to a RHOSO-managed OpenStack environment when performing updates and upgrades to the deployment.
• List any affected packages or components.
  • Could potentially affect any service. Part of this request will to identify impacted services during environment updates and upgrades.

~~~ Moved from OSPRH into RHOSRFE as this is a larger effort than a single epic. Original context provided below ~~~

Goal:

• The parent initiative is tracking Automation of OCP updates, We need to document what all impacts OCP update causes to RHOSO control and dataplane.

As part of Spike https://issues.redhat.com/browse/OSPRH-14687 Impact of OCP updates on centralized OSP dataplane traffic was observered, So those should also be noted along with any other impact observed as part of the parent initiative on RHOSO control and data plane.

Feature Overview (mandatory - Complete while in New status)
An elevator pitch (value statement) that describes the Feature in a clear, concise way. ie: Executive Summary of the user goal or problem that is being solved, why does this matter to the user? The “What & Why”... 
<your text here>

Goals (mandatory - Complete while in New status)
Provide high-level goal statement, providing user context and expected user outcome(s) for this Feature

• Who benefits from this Feature, and how? 
• What is the difference between today’s current state and a world with this Feature?
  <your text here>

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
…
<your text here>
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.
<your text 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..
<your text here>
 
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>
Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

  Reviewed By	Team Name	Accepted	Notes