As Red Hat SREP, I can access clusters for troubleshooting by authorizing against the specific XCM instance

Feature Overview (aka. Goal Summary)  

The SREP team uses the backplane service to get access to clusters for debugging and troubleshooting. The backplane service is integrated with OCM (AMS) and relies on the authorization and RBAC provided by OCM to manage cluster access for the SREP team members. With a regionally distributed XCM architecture, the backplane service will need to reach out to the specific XCM instance, in the region where the cluster is provisioned, for authorization and to gain access to the cluster for debugging and troubleshooting.

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Goals (aka. expected user outcomes)

The goal for SREP team is to be able to effectively monitor, debug, and fix issues with customer clusters in an environment where customer cluster metadata is distributed across multiple regional XCM instances.

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

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

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.