Uploaded image for project: 'OpenShift UX Product Design'
  1. OpenShift UX Product Design
  2. PD-1369

[ROSA Hypershift] Subscription options should be reflected in the UI

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • OCM
    • None
    • False
    • None
    • False

      Specific requirements for ROSA (HyperShift) billing

      1. The seller account for ROSA is different than the other products and services that Red Hat will sell through the AWS marketplace
      2. ROSA customers will be able to purchase annual contracts and pay hourly for overages in addition to hourly billing and we will need the ability to handle contracts at GA itself. 
      3. ROSA billing model in AWS: SaaS contracts with hourly billing for overages.
      4. Annual contracts is a crucial feature that ROSA customers use currently
      1. ROSA billing will be based on two meters (dimensions)
      2. 4-vCPU-hour - for the worker node capacity
      3. cluster-hour - for the control plane (fixed price)

      https://docs.google.com/document/d/1oYrj2tXJ91EEjOQBTfY9jcdSc-D_WEo64efKwOj897g/edit# 

      Deliverables 

      1. Incorporate the new billing model in Hypershift ROSA UI
      2. Reflect changes in Subscriptions navigation 
      3. Reflect billing option in existing rosa hypershift clusters

      Marvel mockups/ Design doc

              Unassigned Unassigned
              rh-ee-smordech Shiri Mordechay Sofer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: