Details
-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
5
-
False
-
False
-
Undefined
-
Workloads Sprint 200, Workloads Sprint 201, Workloads Sprint 202, Workloads Sprint 203, Workloads Sprint 204, Workloads Sprint 205, Workloads Sprint 207, Workloads Sprint 208, Workloads Sprint 210, Workloads Sprint 211, Workloads Sprint 212, Workloads Sprint 214, Workloads Sprint 215, Workloads Sprint 216, Workloads Sprint 217
Description
Part of improvements in scheduling/descheduling in 4.9
Mentioned in https://docs.google.com/document/d/1hfyqJPJYboeKhA68HYzw06dr5Rkd1o2GMzXv76Fr1YI/edit
Running the Descheduler in a dry-mode
Potential applications:
- to report what improvements could be made to cluster (profile suggestions, reporting the current state of cluster)
- have descheduler dump information from decision making (e.g. state of duplicates before running eviction)
