Goal:

• Review existing docs and make sure that they align with the feature implementation as described in the epic https://issues.redhat.com/browse/OSPRH-11035

Acceptance Criteria:

• Existing docs are updated and verified: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/configuring_networking_services/config-qos-policies_rhoso-cfgnet#qos-rules_qos
• Any other docs that are relevant are updated and verified

Open questions:

From doc planning template:

• 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 doc epic need a release note in addition to the parent feature?

• Yes - Writer fills in the Release Note Text and Release Note Type in the doc epic fields (not the engineering epic)

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

• https://www.ovn.org/support/dist-docs/ovn-nb.5.html
• https://bugs.launchpad.net/neutron/+bug/2015376
• https://docs.openstack.org/neutron/latest/admin/config-qos-min-bw.html
•  

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

• 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

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

•  
• Planning guide: Are there prerequisites or planning decisions to add to the Planning guide? Maybe
• SME: Rodolfo
• QE: Bharath M V