-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Implement consistent way of define parallelization of Actions in ActionPlans
-
False
-
-
False
-
-
Not Selected
-
?
-
?
-
To Do
-
?
-
rhos-workloads-evolution
-
?
-
100% To Do, 0% In Progress, 0% Done
-
-
-
Goal:
Currently, watcher does not provide a consistent way of setting actions execution parallelization in the ActionPlans. While the weight applier provides a configuration parameter in watcher.conf to define parallelization by action type for the strategies using it, the node_resource_consolidation and workload_stabilization do not provide a way of ordering the migrations in concurrent groups and all migrations are configured to be executed in parallel (although the watcher-applier will effectively limit the number of concurrent actions executed by parameter max_workers.
The goal is to provide a common and consistent way of setting the paralellization that applies to all the strategies.
Open questions:
- Would it be convenient to set parallelization options per-audit / strategy via audit config? or system-wide per config file is good enough?