Mini Content Journey

Reviewers:

• Technical: [fernando royo]
• Peer: [Greg Rakauskas\
• 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?

• Yes: Writer fills in the Release Note Text and Release Note Type in the doc epic fields. This is not the engineering epic. This RN is usually reserved for documentation epics that trail behind product features or that cover functionality that doesn't have a parent feature (rare but still happens).

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?

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

• https://review.opendev.org/c/openstack/ovn-octavia-provider/+/950686/2/doc/source/admin/driver.rst
• https://review.opendev.org/c/openstack/ovn-octavia-provider/+/950686/2/doc/source/contributor/loadbalancer.rst

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)

• Module Title (Reference)

• Outline of parameters/options/data to be included

• Module Title (Reference)

• Outline of parameters/options/data to be included

Upstream docs source: https://issues.redhat.com/browse/OSPRH-8241