Mini Content Journey (RHOSO team)

Reviewers:

• Technical: jlibosva 
• Peer: jamsmith@redhat.com 
• QE: eolivare

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 or epic might still need a release note. Engineers need to follow the guidance set in[ __ How-to Jira with the docs team|https://spaces.redhat.com/display/RHOSPDOC/How-to-Jira+with+the+RHOS+docs+team].

What stage of the user journey are you targeting?

• Learn: Validated architectures, reference, FAQ(Gain Knowledge)

Who is your target persona?

• RHOSO admin:  Platform Engineer

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

• Most likely, the doc impact will be adding discrete steps to pre-existing procedures where IPv4 is used.

Are there any existing upstream or internal resources that the writer can use for planning and drafting the content? Consider the situational context of the existing content. Do a Google search for any possible resources that might help.

• Edu's internal configuration doc (in-progress)

Does the content require input from multiple DFGs?

• 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)

Does the content need to be included in any of the following guides?

• Validated architecture (VA) guide: Yes: Deploying a dynamic routing environment
• Planning guide: No.
• Deployment/Customization guide: No.
• Adoption/minor updates guide: No.