Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-5699

ROSOCP: container-level recommendations, with history

XMLWordPrintable

    • False
    • None
    • False
    • COST-5706Resource Optimization for OpenShift
    • 100% To Do, 0% In Progress, 0% Done

      Feature Overview:

      Since the CMMO sends data every 6 hours by default, just showing the last recommendation means users are going to miss recommendations (e. G. when they go to sleep and look back at Cost Management, most probably they will have missed already one run of Kruize).

      Let’s add dollar value and historical recommendations to what we have in RHIN-871

      [ ] Must: attach a dollar value (what you would have saved in that period of time had you adopted that recommendation), in the Optimizations page

      [ ] Must: attach a dollar value (what you would have saved in that period of time had you adopted that recommendation), in the Project > Optimizations tab

      [ ] Must: in the OpenShift > Project > Optimizations tab, show historical (ie. past) recommendations for up to 90 days, including boxplots, etc. I. e. "these were the recommendations I was showing yesterday", "these were the recommendations I was showing on MMDDYYYY", etc

      [ ] Must: in the OpenShift > Project > Historical data tab, show the cost comparison if Mr User had applied the given recommendations

      [ ] Should: Group by cluster/namespace, show number of optimizations and be able to sort by it (COST-4519)

      [ ] Could: allow users to set the coefficients Kruize should work with (eg. 20%-33%-50% of acceptable spare capacity from usage vs request vs limit), and navigate recommendations based on that: “what would be the 7-day-based recommendation if I were looking at with with 20% spare capacity? What if 33% spare capacity? What if 40%?”

      [ ] Could: allow users to 

      • Acknowledge a recommendation and make it disappear from the current recommendations (ie. “archive” it). When historical recommendations will be available, archived recommendations should be accessible.
      • Disable recommendations for a Kubernetes object (container/project/node/cluster/replicaset/…) for some period of time (eg. 1 day, 7 days, 30 days, forever). Show an indication that recommendations are disabled for such object and allow the user to re-enable them. When recommendations are disabled, they may not even be generated, and accessing recommendations that would have been generated while disabled is not required.

       

      Apparently ROS OCP is storing this already, it's just the UI is only displaying the last recommendation.

       

      Docs:

      Yes. 

       

      SMEs and Stakeholders:

       

              Unassigned Unassigned
              pgarciaq@redhat.com Pau Garcia Quiles
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: