Feature Overview

...

Goals

This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature

• Some Grafana dashboards that show the existing components, high level utilization as well as hub resource utilization (CPU, Memory and Storage). The way we describe the usage should also reflect the available resource to grow
  • This should exist as an aggregated ACM view.  How much CPU is being used and what is left
  • How much Memory is being used and what is left
  • How much storage
• Then have similar details but for each component.  Though it should be noted that the available resource is shared
• If pods have limits, those should be articulated in the display along with available resources
• Similar to the HCP utilization dashboard, we should have panes that describe the data being shown and the fact that for a specific component the available CPU shown is for this component and all other components.
• The dashboard should be understood without having to go anywhere else.

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.

(Optional) Use Cases

This Section:

• Aggregated Dashboard for ACM's CPU, MEMORY AND STORAGE
• Individual dashboards per component
  • CLC
  • ALC
  • GRC
  • OBS
  • Storage
  • DR
  • Network
  • ...

Questions to answer

• Can we make predictions for each area on how much they can grow?

• • How many more clusters in CLC
  • How many more default sized apps?
  • How many more config Policies or Operator Policies

Out of Scope

• Guarantees, SLA's
• Detailed app or policies sizings
• ACM t-shirt sizings

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• All of the details we would like to display is already captured by the OCP Pod metrics

Customer Considerations

• RFE's for what additional details would be useful
• Some preview customers to review with

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)?