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

[OSD wizard] Calculate instance type times compute node count = total nodes and do quota check

    • False
    • Hide

      None

      Show
      None
    • False

      Ticket currently needs refinement of the Acceptance Criteria questions.

      Description of the Problem

      User tried to install a cluster with compute node vCPU greater than available quota limit. The cluster creation has been blocked with an error that generated from backend related to the quota limit at the time of cluster submission. Ideally OCMUI should be intelligent to detect the limit or perform the quota calculation and show the error at the time of compute node type or node count selection. Another option improvement could be, show the compute node count definition based on the available quota.

      See the attached recording Screen Recording 2024-11-29 at 7.16.20 PM.mov

      How reproducible:

      Always

      Steps to Reproduce:

      1. Open OCM UI staging 
      2. Login with a user with limited quota
        i.e. CCS Cluster quota is 2 and compute.node(vCPU) for CCS is 32.
      3. Open OSD wizard.
      4. At Billing model step, Select inline definition and click "Next" button.
        Subscription type as "Annual: Fixed capacity subscription from Red Hat"
        Infrastructure type as "Customer cloud subscription"
      5. Select the cloud provider as Google and proceed to next steps
      6. Reach to "Default machine pool" step.
      7. Select compute node type as "custom-8-32768 - 8 vCPU 32 GiB RAM"
      8. Select compute node count as "8"
      9. Click "Next" button and proceed to next steps.
      10. Reach to "Review and create" step and click "Create cluster"
      11. See the behavior.

      Actual results:

      At step 11, Cluster installation blocked with a backend error and reported in UI that indicate insufficient quota on compute node limit vs selected compute node type.

      Expected results:

      Indicate the insufficient quota earlier step in wizard ex: at the time of compute type or compute node selection from "Default machine pool" step.
      Proposal would be
      1. Warn the user when the quota limit exceed at the time of compute type and compute node selection. May be quota calculation should be done as part of validation.
      or
      2. Perform quota calculation in advance and show only available compute node type or counts definition from UI that satisfies the available quota.

      Acceptance Criteria:

      • Calculate remaining "compute node vCPU" remaining for validation.
      • Calculate remaining "memory ..." remaining for the user?
      • Disable mp instance whose node/memory counts would be greater than remaining quota, w/ disabled tooltip, ....or....
      • ...show error message upon selecting a mp instance type which would exceed remaining quota.

              dtaylor@redhat.com David Taylor
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: