Feature Overview (aka. Goal Summary)  

This feature is a follow up to XCMSTRAT-190 to take the outcome and learnings from the PoC and implement the changes in the console to deliver an internal preview. The changes will need to be behind a feature flag to ensure that external customers are not impacted by and exposed to changes that are in-flight.

Goals (aka. expected user outcomes)

The OCM console running in the user’s browser should be able to reach out to the individual regional OCM instances to allow customers to provision and manage HCP clusters lifecycled by the regional OCM instances using a single/global console. The console should not persist any cluster data to avoid violating any data residency requirements.

Interfaces: UI, OCM CLI, ROSA CLI, OCM SDK

Teams: SREP, AppSRE, OCM, OCMUI

Requirements (aka. Acceptance Criteria):

• As a customer, I can connect to the console to list and view the details for my clusters provisioned in different cloud provider regions within the geographic region.
• As a customer, I can connect to the console to provision a new cluster within any of the cloud provider region.
• As a customer, I can connect to the console to perform day-2 operations like scale, configure, and update my clusters provisioned in the cloud provider regions.

The internal preview release will cover all OCM UI pages, including the dashboard page. The user experience might be tweaked based on the results of the PoC and we might have to add a region filter for the aggregate view on the dashboard page.

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

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

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.