Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-1931

Automate Resource Quota Limit Increase Requests Based on ClusterPool Sizes

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Hive
    • False
    • False
    • Undefined

      Overview

      As a cloud account administrator looking to use the ClusterPool feature of Hive
      I want to automate the requests for cloud quota from the IaaS
      So that I can have a streamlined UX for changing ClusterPool sizes

      Summary

      Today, the process of translating between N ClusterPools running M clusters in one cloud account into the resource usage required to maintain that is totally manual. On top of that, the process of asking the cloud vendor behind the IaaS to enable sufficient quota in the account such that running all M of those clusters concurrently is also manual. This is a major gap in the UX for adopting ClusterPools and an issue that any user of pooled clusters will encounter on a managed infrastructure.

      Impact

      This impacts all administrators of IaaS accounts where someone's using ClusterPools

      Acceptance Criteria

      • a user can discover the total concurrent resource usage in an account for all ClusterPools that exist
      • a user can discover which resource requirements for ClusterPools in an account are not met by current account quota settings
      • a user can automatically send/generate said quota increase requests

      Notes

      This isn't 100% obviously a HIVE task, at least some part of this (the translation between a cluster and the resource footprint of the cluster on a given IaaS) should ideally be something that the installer can deliver, but regardless, this is a UX gap that all account admins will hit.

              julim Ju Lim
              skuznets@redhat.com Steve Kuznetsov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: