mini content journey:

Reviewers:

• • Technical: ksundara@redhat.com 
• Peer: grakausk@redhat.com 
• QE: [name]
• Partner/Field (optional): [name]

Is this feature fully supported or technical preview?

• Full support

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?

• Only if we need a new title for the migration. Under exploration now.
• 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?

• Expand: Customizations, day 2 operations, troubleshooting, add features to control plane or data plane

Who is your target persona?

• RHOSO admin:  Platform Engineer
• OpenStack admin:  Cloud Administrator

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

• Procedures to implement or enable the feature
• Procedures to customize or configure the feature after installation
• Procedures or considerations for upgrades, adoption, or minor updates
• Procedures to verify that the feature is enabled and is working as expected
• Procedures to operate or maintain the feature
• Concepts that need to be explained or planning decisions that must be made before the user can perform any of these procedures
• Permissions level required (RHOSO/OCP) or security considerations
• Known issues, limitations, or troubleshooting guidance

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.

• Yes. See comments below

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: NFV
• Planning guide: Customer needs to plan for migration __ 
• Deployment/Customization guide: possible impact on both. TBD
• Adoption/minor updates guide: Don't know yet

(Optional) Documentation outline see child task that tracks creaion of outline
https://issues.redhat.com/browse/OSPRH-24852