Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-15963

Create a standard way for adjusting limits and requests to the addon-framework components

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected

      Feature Overview

      Goals

      Allow users to set the limits on memory and cpu for add-on components.

      Provide a standard way for add-on developers to offer a way to set limits for add-on components.

      Ensure customers have a simple, standardised way to set limits on all add-ons.

      Ensure all new add-ons adhere to this standard.

      Requirements

      This Section: A list of specific needs or objectives that a Feature must
      deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
      If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
      it does not shift the feature.

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a
      requirement for ALL features.
      YES
      Release Technical Enablement Provide necessary release enablement details
      and documents.
      YES

      (Optional) Use Cases

      Edge scenarios with very limited resources

      Questions to answer

      Out of Scope

      Background, and strategic fit

      Customers may need to manage the resource consumption on spokes for a majority of use cases.

      One key is far edge: https://issues.redhat.com/browse/ACM-626

      But resources = $ so ensuring control of them is key.

      Assumptions

      Should use the same key/value pairs for all add-ons
      Goal is for it feel as "cut and paste equal” if possible.
      Use same config structure.
      Ensure a clean and easy UX experience that offers consistency across all add-ons.

      Customer Considerations

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this
        product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have a doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content
        Strategy.
      • What concepts do customers need to understand to be successful in
        [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical
        Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or
        Release Note)?

              leyan@redhat.com Le Yang
              asimonel August Simonelli
              Hui Chen Hui Chen
              August Simonelli August Simonelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: