-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
Feature Overview (aka. Goal Summary)
The OSD product overview in the OCM console is needed to improve the product awareness, ease of navigation, and discoverability of OpenShift Dedicated (OSD). Additionally, with multiple means to procure and pay for OSD, the overview page is going to be a key resource to provide customer with at-a-glance information about their options.
Goals (aka. expected user outcomes)
The goal is to provide users with information OSD, including an overview of the value proposition (with links to details), cloud provider options (AWS and GCP), purchase options (RH, RHM, Google cloud marketplace, trial), and billing options (RH annual subs or consumption based billing through RHM and Google cloud marketplace).
Ideally, we should look at the product page for ROSA to drive consistency in our product overview pages.
Requirements (aka. Acceptance Criteria):
- OSD overview page highlighting OSD details captured above
- OSD overview page should be accessible, regardless of whether customers have OSD clusters or not
- OSD product overview page should be linked from the OSD card on the OCM overview page
- The navigation items on HCC (console.redhat.com) should be updated to link to the specific product pages for ROSA/OSD
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.