• True
    • Show
      blocked on https://issues.redhat.com/browse/SWATCH-2176
    • False
    • Red
    • XCMSTRAT-15AWS Integration
    • 33% To Do, 33% In Progress, 33% Done
    • Hide

      Apr 24 (Eng)

      • Reviewed and closed the bug OCM-6772 - patch a null billing account should respond clear error message
      • OCM-6823 - service log should be generated once modify the billing account was deployed to stage and it is ready for QE verification

       

      Apr 17 (Eng)

      • ROSA-CLI changes Display billing account for ROSA Classic clusters whenever present are merged and should be in the next release (OCM-6142)
      • Progress on OCM-6147 revealed a difficulty in patching clusters using service accounts. Created a new card for further investigation (OCM-7456)
      • Started looking at the bug OCM-6772 - patch a null billing account should respond clear error message
      • SD-ADR-0186: Hybrid SaaS billing for ROSA remains in Review

       

      Mar 6, March 13th (Eng)

      •  [OCM]  No updates since the last report. There are no blocking items at this point. Remaining tasks from OCM-5117 are on track. 
      • [SWATCH] Swatch team continues to work on the prioritization of SWATCH-2176. It's unlikely that the team will start working on this before Q2.
      • Target end date revised to 2024/05/31.

       

      Feb 28 (Eng)

      • [OCM] Completed work on the automated setting/update of metered_by_rh attribute for ROSA (OCM-5464)
      • [OCM] AMS now allows billing account change via the cluster authorization endpoint for selected organizations (OCM-6154)
      • [OCM] AMS now accepts billing account setting for ROSA Classic clusters via the cluster authorization endpoint for selected organizations (OCM-6154)
      • [OCM] Reached out to the telemeter/cluster infrastructure teams to request the new metric/label that indicates the AMI used by ROSA Classic clusters and opened a RFE-5236 (OCM-6099)
      • [OCM] Clusters Service now Allow AWS billing account patching (OCM-6145) - currently in Review/available in the stage environment

      Feb 21 (Eng)

      • [OCM] New requirement identified for ROSA-CLI: Display billing account for ROSA Classic clusters (OCM-6142)
      • [OCM] New requirement identified for Clusters Service: Allow billing account patching (OCM-6145)
      • [OCM] New requirement identified for AMS: Accept billing accounts for ROSA Classic via the cluster authorizations endpoint (OCM-6154 and related to OCM-6145)
      • [OCM] Continued to work on the automated setting/update of metered_by_rh attribute for ROSA (OCM-5464)
      • [OCM] Initial analysis of OCM-6099 indicates that we don't currently have a telemeter metric that exposes the AMI used by the nodes. More investigation needed
      • [SWATCH] Swatch team continues to work on the prioritization of SWATCH-2176

       

      Feb 14 (Eng)

       

      Feb 7 (Eng)

      • [OCM] metered_by_rh label now takes into account the database attribute from the subscriptions table, which can be manually patched/overridden
      • [OCM] Work to automate the setting/update of metered_by_rh attribute for ROSA Classic clusters has started
      • [SWATCH] Requirements for Subscription Watch have been defined. Pending effort sizing and prioritization. Discussed in a meeting between OCM and SubWatch teams. See  notes.
      • [UI] There are no Console/UI changes required at this moment. 

       

      OCM 20 Mar (QE)

      • Test passed of using generic ami after enabled AMS capability
      • Test passed of allow billing account overriding for rosa classic
      • Test passed of metric data metered_by_rh for cluster
      • Test passed of billing account changed in ams side
      • Test failed of billing account changed in cs side, bug in discussion

       

      OCM 31 Jan (Eng)

      • AMS capabilities are now available
      • CS changes to skip image overriding for hybrid billing clusters are in place and (currently in review by QE)
      • Ability to set billing accounts for ROSA Classic clusters via a capability is now available (currently in review by Eng)
      Show
      Apr 24 (Eng) Reviewed and closed the bug OCM-6772 - patch a null billing account should respond clear error message OCM-6823 - service log should be generated once modify the billing account was deployed to stage and it is ready for QE verification   Apr 17 (Eng) ROSA-CLI changes Display billing account for ROSA Classic clusters whenever present are merged and should be in the next release (OCM-6142) Progress on OCM-6147 revealed a difficulty in patching clusters using service accounts. Created a new card for further investigation (OCM-7456) Started looking at the bug OCM-6772 - patch a null billing account should respond clear error message SD-ADR-0186 : Hybrid SaaS billing for ROSA remains in Review   Mar 6, March 13th (Eng)   [OCM]   No updates since the last report. There are no blocking items at this point. Remaining tasks from OCM-5117 are on track.  [SWATCH] Swatch team continues to work on the prioritization of SWATCH-2176. It's unlikely that the team will start working on this before Q2. Target end date revised to 2024/05/31.   Feb 28 (Eng) [OCM] Completed work on the automated setting/update of metered_by_rh attribute for ROSA (OCM-5464) [OCM] AMS now allows billing account change via the cluster authorization endpoint for selected organizations (OCM-6154) [OCM] AMS now accepts billing account setting for ROSA Classic clusters via the cluster authorization endpoint for selected organizations (OCM-6154) [OCM] Reached out to the telemeter/cluster infrastructure teams to request the new metric/label that indicates the AMI used by ROSA Classic clusters and opened a RFE-5236 (OCM-6099) [OCM] Clusters Service now Allow AWS billing account patching (OCM-6145) - currently in Review/available in the stage environment Feb 21 (Eng) [OCM] New requirement identified for ROSA-CLI: Display billing account for ROSA Classic clusters (OCM-6142) [OCM] New requirement identified for Clusters Service: Allow billing account patching (OCM-6145) [OCM] New requirement identified for AMS: Accept billing accounts for ROSA Classic via the cluster authorizations endpoint (OCM-6154 and related to OCM-6145) [OCM] Continued to work on the automated setting/update of metered_by_rh attribute for ROSA (OCM-5464) [OCM] Initial analysis of OCM-6099 indicates that we don't currently have a telemeter metric that exposes the AMI used by the nodes. More investigation needed [SWATCH] Swatch team continues to work on the prioritization of SWATCH-2176   Feb 14 (Eng) [OCM] Continued to work on the automated setting/update of metered_by_rh attribute for ROSA [OCM] New requirement: capture AMI used by worker nodes from openshift metrics - https://issues.redhat.com/browse/OCM-6099   [SWATCH] Swatch team continues to work on the prioritization of https://issues.redhat.com/browse/SWATCH-2176     Feb 7 (Eng) [OCM] metered_by_rh label now takes into account the database attribute from the subscriptions table, which can be manually patched/overridden [OCM] Work to automate the setting/update of metered_by_rh attribute for ROSA Classic clusters has started [SWATCH] Requirements for Subscription Watch have been defined. Pending effort sizing and prioritization. Discussed in a meeting between OCM and SubWatch teams. See  notes . [UI] There are no Console/UI changes required at this moment.    OCM 20 Mar (QE) Test passed of using generic ami after enabled AMS capability Test passed of allow billing account overriding for rosa classic Test passed of metric data metered_by_rh for cluster Test passed of billing account changed in ams side Test failed of billing account changed in cs side, bug in discussion   OCM 31 Jan (Eng) AMS capabilities are now available CS changes to skip image overriding for hybrid billing clusters are in place and (currently in review by QE) Ability to set billing accounts for ROSA Classic clusters via a capability is now available (currently in review by Eng)
    • CY24Q1
    • 0

      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.

            rhn-engineering-abhgupta Abhishek Gupta
            rhn-engineering-abhgupta Abhishek Gupta
            Cristiano Veiga Cristiano Veiga
            Tongtong Zhou Tongtong Zhou
            Aedin Collins Aedin Collins
            Victor Kareh Victor Kareh
            Cristiano Veiga Cristiano Veiga
            Abhishek Gupta Abhishek Gupta
            Kevin Cormier Kevin Cormier
            Not Needed Not Needed (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: