Define when an action plan is stale/invalid

Registered by Antoine Cabot on 2016-09-12

Today in Watcher we generate an action plan after an audit but we never define an expiry date or an event that can invalidate this action plan.
For example we could set a configurable expiration time like 24h that will make all action plan older than 24h no longer valid.
We could also have an invalidation trigger of all action plans when a specific event occurs in the cluster data model. The end of execution of an action plan should also superseed all previous action plans as the cluster state has been modified.
We should add a new state "superseded" for the action plan.

Blueprint information

Status:
Complete
Approver:
Antoine Cabot
Priority:
Medium
Drafter:
Antoine Cabot
Direction:
Approved
Assignee:
licanwei
Definition:
Approved
Series goal:
Accepted for pike
Implementation:
Implemented
Milestone target:
milestone icon pike-1
Started by
Antoine Cabot on 2016-11-04
Completed by
Alexander Chadin on 2017-04-05

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/stale-action-plan,n,z

Addressed by: https://review.openstack.org/386293
    Define when an action plan is stale/invalid

Addressed by: https://review.openstack.org/391383
    check the state of action plan

Addressed by: https://review.openstack.org/432193
        Define when an action plan is stale/invalid

Addressed by: https://review.openstack.org/440927
    stale the action plan

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.