Goal: 

Update Configuring Persistent Storage guide [1] with a section that provides a procedure to enable Notifications in Glance.

Acceptance Criteria:

The doc provides a small procedure that describes the notification parameters required to enable notification in Glance.

Mini Content Journey

Reviewers:

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

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
• No: Exemption approved by <STAKEHOLDER NAME>

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?

• 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
• OpenStack user: SysAdmin or Developer

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

• Procedures to implement or enable the feature

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://github.com/openstack-k8s-operators/glance-operator/tree/main/config/samples/notifications 

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)

(Optional) Documentation outline If applicable, the writer can start brainstorming about the information design for the content. This is understood to only be a draft placeholder and subject to change as the content is authored and reviewed.

• Enabling notifications in the Image service (Procedure)
  • To enable, verify, and disable