Implement Zapping States
Zapping encompasses all long running, manual, destructive tasks an operator may want to take either between workloads, or before the first workload has been assigned to a node.
Blueprint information
- Status:
- Complete
- Approver:
- aeva black
- Priority:
- High
- Drafter:
- Josh Gachnang
- Direction:
- Approved
- Assignee:
- Josh Gachnang
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- John Stafford
- Completed by
- Jim Rollenhagen
Related branches
Related bugs
Sprints
Whiteboard
SUPERSEDED BY https:/
Gerrit topic: https:/
Addressed by: https:/
Implement Zapping States
Gerrit topic: https:/
Addressed by: https:/
Add zapping API
There's essentially no code done. I'm bumping to the next cycle.
- Devananda, 13 March 2015
Addressed by: https:/
Implement Zapping States
Gerrit topic: https:/
Addressed by: https:/
Zapping spec follow up
Addressed by: https:/
Cache agent clean steps on node
Addressed by: https:/
WIP: Add Zap states
Addressed by: https:/
WIP: Add zapping to conductor
Addressed by: https:/
Update documentation related to zapping
Addressed by: https:/
Add db migration test for zap_step
SUPERSEDED BY https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
