Allow OCM customers to manage their notification preferences within the HCC notifications service

Feature Overview (aka. Goal Summary)

This feature will allow OCM customers to manage their notification preferences using the platform notification service within the hybrid cloud console. Customers will be able to specify which cluster events to be notified on, who gets notified for the events, the medium/channel of notification, and the frequency/format of the notification.

Instead of building all this functionality in OCM, we should leverage the functionality that exists in the platform notification service so that customers have a common UX around managing their notification preferences for the various Red Hat cloud services that they consume.

Goals (aka. expected user outcomes)

The primary goal is to allow OCM customers to manage their notification preferences for cluster events through the notification service within HCC.

Additionally, the feature should take into account the functionality that is already built into OCM around notifications. Customers should not see a regression in the functionality that is available to them through the existing OCM notifications feature via OSL (OpenShift Service Log).

Requirements (aka. Acceptance Criteria):

Event selection:

• Users can manage which events they get notified on.
• They should be able to filter for the events based on event type, severity, and the cluster that the event corresponds to.

User opt-in:

• Cluster owners should be opted-in to notifications for events for clusters that they provisioned.
• Additional notification contacts configured for a cluster in OCM should be automatically opted-in to receive notifications for events pertaining to the particular cluster.
• Additional users within the organization can opt-in to be notified for the different cluster events.

Cluster owner being notified:

• OSL currently includes the cluster owner by default for any notifications clusters that they provision
• Notification service should accept, as part of the event metadata, RH usernames that should be notified by default for the event

TAMs/CSMs being notified:

• OSL currently allows TAMs/CSMs to be notified for specific events
• The configuration is maintained in in OSL, indicating which events result in notification to TAM/CSM
• Notification service should accept, as part of the event metadata, RH usernames that should be notified by default for the event

Notification channel:

• Users should receive notifications on the email associated with their user account by default
• Users should be able to select the channel to receive the particular notification on

Notification frequency:

• Users should be able to configure their notification preferences to be notified via email immediately on as a daily summary. 

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Background

The feature should take into account the functionality that is already built into OCM around notifications. Customers should not see a regression in the functionality that is available to them through the existing OCM notifications feature (via OSL - OpenShift Service Log).
 

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.