search

redhat-cop / openshift-toolkit

A collection of code samples to help you get started with OpenShift
Apache License 2.0
234 stars 150 forks source link

Build UI layer for capacity planner tool #89

Closed etsauer closed 4 years ago

etsauer commented 5 years ago

We would like to build an "executive level" UI around our new capacity planner tool.

Currently the tool traverses an openshift cluster and collects quota, limit, and request data (real time usage data coming soon), and exposes it via a simple API.

The API presents 3 different layers of scope:

We would like to be able to visualize this information for leadership to give them some assistance in making decisions.

By default, we would want to display the cluster level metrics, but provide the ability to drill down into the namespace and pod. We get a lot of asks to "show be the top 10 largest namespaces" so the ability to sort based on any of the given metrics would be really helpful. Here is a sample of what we should by default for the cluster.


Total Cluster Size:
----
    Memory: 151.23707342147827 Gi
    CPU:    37.2 Cores

Amount Claimed By Quota:
----
    Memory: 12.0 Gi (7.934562424755168%)
    CPU:    2 Cores (5.376344086021505%)

Total Limits:
----
    Memory: 108.569046119228 Gi (71.78732281909478%)
    CPU:    11.444999999999997 Cores (30.766129032258053%)

Total Requests:
----
    Memory: 47.17162685096264 Gi (31.190518160518344%)
    CPU:    10.724999999999987 Cores (28.830645161290285%)
shah-zobair commented 5 years ago

@etsauer I have done something with Grafana dashboard. I can tweak that according to this requirement. Does that help here?

etsauer commented 5 years ago

@shah-zobair yes, that would be helpful to see. @raffaelespazzoli mentioned you were working on something for this.

garethahealy commented 4 years ago

@etsauer ; is this still needed? looking at the PR trail, looks like its solved via:

etsauer commented 4 years ago

I think we can close it.

On Thu, Dec 19, 2019, 10:43 Gareth Healy notifications@github.com wrote:

@etsauer https://github.com/etsauer ; is this needed? looking at the PR trail, looks like its solved via:

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/redhat-cop/openshift-toolkit/issues/89?email_source=notifications&email_token=ABCK2FWNZYD2ZIO7ECKAZ7LQZOJDLA5CNFSM4HJEPIB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHKALNA#issuecomment-567543220, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABCK2FXIMAUDNWRB5AXHX3DQZOJDLANCNFSM4HJEPIBQ .