Management of a maximum level of aggressiveness

Registered by Vincent Mahe on 2016-11-07

Today in Watcher it is not possible to configure the maximum level of aggressiveness the admin is ready to tolerate on his infrastructure. The aggressiveness means here the risk of impacting the SLA of the tenants workloads.
Moreover, the efficacy of an action plan is usually related to how much change the admin is ready to accept.
It would be useful to be able to configure the maximum level of aggressiveness which is globally allowed on the whole infrastructure (we may need to configure it on some subset in a further blueprint). This level of aggressiveness would act as some filtering threshold indicating which actions are allowed in the Action Plan delivered by the Decision Engine.

The strategies could take into account these aggressiveness parameters to adapt their algorithm accordingly. Or we can imagine that in a future Strategy Selector component, a strategy would be chosen according to the maximum level of aggressiveness, or we can also imagine that a strategy generates an Action Plan and that the filtering of actions is done by the Watcher Applier which would execute only the most important Actions.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Low
Drafter:
Vincent Mahe
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.