Allow the developer of a watcher plugin to add specific parameters

Registered by Jean-Emile DARTOIS on 2016-02-25

In Watcher, it is possible to deploy and configure new strategies,actions,planners,ect and associate each "plugin" to a Python class, without the need to redeploy a new version of Watcher.

However, it should be possible to pass some extra parameters depending of the configuration of the openstack cluster or some behaviour ( timeout, weights, ect) on which watcher is operating.

This is the reason why, we should give the possibility to the developer to add some parameters on each plugins.

Blueprint information

Status:
Complete
Approver:
Antoine Cabot
Priority:
Essential
Drafter:
Jean-Emile DARTOIS
Direction:
Approved
Assignee:
Vincent Fran├žoise
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-1
Started by
Antoine Cabot on 2016-05-17
Completed by
Antoine Cabot on 2016-05-30

Related branches

Sprints

Whiteboard

Related Blueprint: https://blueprints.launchpad.net/nova/+spec/making-live-migration-api-friendly

Gerrit topic: https://review.openstack.org/#q,topic:bp/plugins-parameters,n,z

Addressed by: https://review.openstack.org/312143
    Specs for plugins-parameters

Addressed by: https://review.openstack.org/314036
    Enabled config parameters to plugins

Addressed by: https://review.openstack.org/314037
    Documentation for plugins-parameters

Addressed by: https://review.openstack.org/320529
    Watcher plugins table in Guru meditation reports

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.