Recovery method customization

Registered by Abhishek Kekane on 2017-04-19

As of now masakari uses taskflow to execute the failure workflow which has certain recovery actions which are predefined and executed in linear way. In future if operator wants to add/remove any existing task to any of this flow then three is no way to do so rather than making changes in the code. For example in case of host-failure recovery workflow predefined flow is;
 disable_compute_node, prepare_ha_enabled_instances, evacuate and confirm_evacuate. If operator wants to remove task disable_compute_node from the flow then it's not possible with current implementation.

Use Case:
Operator may want to add/remove tasks from the existing flow based on the requirements.

Blueprint information

Status:
Not started
Approver:
SamP
Priority:
High
Drafter:
Abhishek Kekane
Direction:
Approved
Assignee:
Abhishek Kekane
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/recovery-method-customization,n,z

Addressed by: https://review.openstack.org/458022
    Prepare specs repository for Pike

Addressed by: https://review.openstack.org/458023
    Recovery method customization

Addressed by: https://review.openstack.org/571409
    Implementation of recovery method customization

Addressed by: https://review.openstack.org/583127
    WIP : Add hooks for recovery method customization plugins

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.