Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-2781

Console UI: Cluster Autoscaler "cores-total-max" and "memory-total-max" calculations for default values

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Console UI: Cluster Autoscaler "cores-total-max" and "memory-total-max" calculations for default values
    • True
    • Hide

      Needs backend work so that we don't continue to add business logic to UI codebase, but rather should be coming from the backend API.

      https://issues.redhat.com/browse/OCM-14180

      Show
      Needs backend work so that we don't continue to add business logic to UI codebase, but rather should be coming from the backend API. https://issues.redhat.com/browse/OCM-14180
    • False
    • To Do
    • 100% To Do, 0% In Progress, 0% Done

      Related to effort put for calculating the default maxNodesTotal value from 

      https://issues.redhat.com/browse/OCMUI-2226;

      As a follow up item after XCMSTRAT-161 feature release, we also require that the core size and memory size defaults that appear on the cluster autoscaler modal for day1 and day2 reflect the max node size possible.

       

      Pending:

      Discussion on whether we will add a validation if a user inputs a number greater than what is suggested as default value within the modal.

       

              Unassigned Unassigned
              dle.openshift David Lee
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: