At the moment, the planner has a single plugin which hosts two algorithsm: derive_overlay, which inspects a WL and derives an overlay description, and expand_workload, which can transform the workload to some unspecied rules. As an example, the workload may contain cardinality information for tasks, and the expand_workload could expand that to a certain number of tasks.
The latter algorithm is not well defined and scoped, I think -- it is more a placeholder for workload specific transformations. That might suffice to justify its existance? Either way, I think this functionality would be better placed on the workload manager, even if this expansion step can happen before the planner derives the overlay description.
If we keep it in the planner, I would like to split that into two plugins at least, because the functionalities are unrelated.
At the moment, the planner has a single plugin which hosts two algorithsm:
derive_overlay
, which inspects a WL and derives an overlay description, andexpand_workload
, which can transform the workload to some unspecied rules. As an example, the workload may containcardinality
information for tasks, and theexpand_workload
could expand that to a certain number of tasks.The latter algorithm is not well defined and scoped, I think -- it is more a placeholder for workload specific transformations. That might suffice to justify its existance? Either way, I think this functionality would be better placed on the workload manager, even if this expansion step can happen before the planner derives the overlay description.
If we keep it in the planner, I would like to split that into two plugins at least, because the functionalities are unrelated.