Feature Overview (aka. Goal Summary)  

Currently, the OCM console is centrally hosted in the AWS us-east-1 region. To achieve our goals around resiliency and business continuity, we will need to run the console in multiple regions. We should be running the console within each geographical boundary as opposed to within each region. That, however, still means moving the console from a single, centralized service to a regional service. The user experience for a regional console will also need to be determined.

Goals (aka. expected user outcomes)

The web UI running in the user’s browser should be able to reach out to the individual XCM instances within the geographical region to fetch and display the cluster information to the user.
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

The observable functionality that the user now has as a result of receiving this feature. Complete during New status.

Requirements (aka. Acceptance Criteria):

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

OCM UI pages in scope of the PoC:

• The cluster list and cluster detail screens will be part of this PoC
• The cluster provisioning wizards will be included in scope for the PoC and hence all day-1 and day-2 functionality will be part of the PoC
• The downloads/subscription pages within OCM will be part of the PoC

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.

Azure RO Integration

• Exists today
  NO
• Needed for ARO-HyperShift
  NO - Azure has its own Provision and List console. For layered services and other capabilities a regional Console might be required.

Managed Service Provider

      Maybe

Open Source

• Could be made Apache v2
  YES

Contains Sensitive Customer information (PI)

        FORWARDER

Multi-Region

• Data sovereignty
  YES - May only need to be GEO Located (one console for a number of regions, in Europe for example)
• Disaster recovery
  YES

FedRAMP

• Currently
  YES

Out of Scope

• OCM Dashboard: The OCM screen with the aggregated cluster metrics and insights data will not be part of this PoC
   

  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.