Uploaded image for project: 'Container / Cluster Management (XCM) Strategy'
  1. Container / Cluster Management (XCM) Strategy
  2. XCMSTRAT-266

Enable setting scheduler NodeUtilization profiles

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • True
    • Hide

      Reason: Insufficient engineering capacity from OCM + ecosystem engineering.

      PTG: Will be take up once the bandwidth is available. 

      Show
      Reason : Insufficient engineering capacity from OCM + ecosystem engineering. PTG : Will be take up once the bandwidth is available. 
    • False
    • Not Selected
    • 0
    • 0% 0%
    • 0

      Feature Overview (aka. Goal Summary)  

      This feature will introduce customization for cluster scheduler that allows customer to set profiles such as "HighNodeUtilization" to maximize node utilization and reduce cost.

      Goals (aka. expected user outcomes)

      Customers can pass valid profile option to their {cluster or machinepool} (TBD based on design) that changes the scheduler options for their workloads . This will allow parity between self-managed OCP and ROSA/OSD clusters. 

      Requirements (aka. Acceptance Criteria):

      1. Configurability at the machine pool level
      2. Applicable only to the machine pools or the worker nodes that customer create/manage
      3. Allow shorter range of values -  default value to start
      4. The default value is standard/normal utilization
      5. an optional tested profile is at least "HighNodeUtilization"
      6. OCM UI, ROSA CLI, Terraform can configure this field.

      Use Cases (Optional):

      1. Cluster administrators want to maximize compute utilization and decrease compute costs by extension
      2. workloads can be right-sized by customers within specifically sized machinepools or labellled machines
      3. Administrators have self-managed OCP clusters using this capability and following same operations across different environments is preferred for deployment of workloads to managed cloud services.

      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

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      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.

            rh-ee-adejong Aaren de Jong
            rh-ee-adejong Aaren de Jong
            Yu Wang Yu Wang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: