This epic tracks the doc changes after the new rabbitmq messagingBus and notificationsBus changes.

Goal:

As part of the new Jobs to be Done (JTBD) framework adopted by CCS, this must express the JOB that the customer needs to accomplish because of this Engineering epic.

The RabbitMQ interface has been expanded from a single parameter that specified the cluster name to an expandable structure, which apart from specifying the cluster can specify the user, and in a later version will specify the vhost, per service. Furthermore, provision has been made for the specification of global cluster names for the RabbitMQ messagingBus and notificationsBus sections implemented by the relevant services. This interface will be used by the RHOSO Admin.

Acceptance Criteria:

Documentation accepted by the PIDONE DFG

Mini content journey:

This must be completed as part of the refinement process

Reviewers: 

• Technical: Luca
• Peer: [Writer name] 
• QE: [name] 

Is this feature fully supported or technical preview? 

• Full support: The interface, the users 
• Tech preview (TP): VHost - FR6 fully supported __  

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  Danield tested

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://issues.redhat.com/browse/RHOSSTRAT-1135

What stage of the user journey are you targeting? 

• Adopt: Adoption or Greenfield feature (Early stage customer use) 
  update - auto upgrade - per service rabbitmq configuration
• Expand: Customizations, day 2 operations, troubleshooting, add features to control plane or data plane 

Who is your target persona? 

• RHOSO admin: Platform Engineer  - creator of the control plane

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

Different way of configuration

• 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 

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

• Deployment/Customization guide: Does the feature need to be enabled during the deployment process, or can it be enabled post-deployment? 
• Adoption/minor updates guide: Are there any considerations or impact of this feature on adoption from pre-18 environments or from earlier 18z versions?