Make default Planner generic to handle new action
Currently we have to amend the code of the Planner for each new added Watcher Action. This patch set will modifying the DefaultPlanner class and leverage the plugins-parameters blueprint so that we can configure weights via the configuration file. Documentation and unittest also be update in this patch. Co-Authored-By: Vincent Françoise <vincent.francoise@b-com.com> Change-Id: Ib794488fcafd1e153a7d7b1f7253686136501872 blueprint: configurable-weights-default-planner
This commit is contained in:
@@ -205,6 +205,9 @@ By doing so, your action will be saved within the Watcher Database, ready to be
|
||||
processed by the planner for creating an action plan which can then be executed
|
||||
by the Watcher Applier via its workflow engine.
|
||||
|
||||
At the last, remember to add the action into the weights in ``watcher.conf``,
|
||||
otherwise you will get an error when the action be referenced in a strategy.
|
||||
|
||||
|
||||
Scheduling of an action plugin
|
||||
==============================
|
||||
|
||||
Reference in New Issue
Block a user