Feature Overview (aka. Goal Summary)  

As a customer, I should be able to use a single private offer from Red Hat to use with ROSA clusters provisioned using either the Classic or the HCP deployment model.

ROSA Classic and ROSA with HCP are configured as separate products on the AWS marketplace, preventing customers from directly benefiting from a single private offer across all their ROSA clusters, regardless of the deployment model. This feature will enable SaaS billing for both deployment models to overcome this challenge for ROSA customers.
 

Goals (aka. expected user outcomes)

Usage from both ROSA Classic and ROSA with HCP clusters should be squared against a customer's prepaid contract quantities purchased through the private offer. Customers should not be charged on-demand prices as long as their usage is within the pre-purchased contract quantities.
 

Requirements (aka. Acceptance Criteria):

The user workflow has been discussed in detail in this document.
https://docs.google.com/document/d/1LRnQjD0hZiZGjI17_l54DhkBcWFYP1VH-Fqm0Cvw0OI/

Use Cases (Optional):

The use cases and customer scenario are captured in this document.
https://docs.google.com/document/d/1LRnQjD0hZiZGjI17_l54DhkBcWFYP1VH-Fqm0Cvw0OI/

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

ROSA is a single product and “Classic” and “hosted control planes (HCP)” are two different deployment model options available to customers for their ROSA clusters. Behind the scenes, on the AWS marketplace, ROSA Classic and ROSA with HCP are set up as two different marketplace product listings. Private offers are associated with a particular product and cannot span multiple products on the AWS marketplace. This presents a challenge for our ROSA customers that would want to leverage the private offer discounts for usage of all their ROSA clusters, regardless of the deployment model.

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.