Mini Content Journey (RHOSO team)

Reviewers:

• Technical: rhn-support-gthiemon 
• Peer: kgilliga@redhat.com, jamsmith@redhat.com 
• QE: lavraham 

Is this feature fully supported or technical preview?

• Full support: Documentation will be published on the customer portal

Does the procedural content need to be tested by QE?

• Yes: QE needs to create a doc testing ticket per How-to Jira with the docs team

Does the documentation epic need a release note in addition to the feature?

• No: The engineering feature (RHOSSTRAT-176) will have a release note.

What stage of the user journey are you targeting?

• Adopt

Who is your target persona?

• OpenStack admin:  Cloud Administrator

What type of information does the user need to know in order to use the feature?

• See outline below.

Are there any existing upstream or internal resources that the writer can use for planning and drafting the content?

• Upstream doc that is migrated downstream

Does the content require input from multiple DFGs?

• Yes: Writer creates spikes or stories under this epic and assigns them to the relevant writers for scoping
• No: Stories are not required unless the epic needs to be divided to user stories that can be delivered separately (for personal use, consider sub-tasks instead)

(Optional) Documentation outline

• Migrating a RHOSP 17.1 dynamic routing environment
• Process overview
• Prerequisites
• Procedure
• Validation