Implement Cleaning States
When a node has finished a workload, drivers should have the opportunity to run a set of tasks during immediately after tear down and before the node is available for scheduling again.
Blueprint information
- Status:
- Complete
- Approver:
- aeva black
- Priority:
- High
- Drafter:
- Josh Gachnang
- Direction:
- Approved
- Assignee:
- Josh Gachnang
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Josh Gachnang
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Implement Cleaning States
Addressed by: https:/
Implement execute clean steps
Addressed by: https:/
Implement Cleaning in DriverInterfaces
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Add /nodes/
Gerrit topic: https:/
Addressed by: https:/
Add cleaning/zapping support to IPA
Gerrit topic: https:/
Addressed by: https:/
Implement cleaning/zapping for the agent driver
Addressed by: https:/
Add support for cleaning in Ironic driver (Nova)
Addressed by: https:/
Change clean_steps to a dict
Gerrit topic: https:/
Addressed by: https:/
Add dispatch to all managers
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
03.16.2015 - REST API Items Open (3 4 & 5 on http://
*An API endpoint should be added to allow operators to see currently enabled clean steps and their ordering. This will be a GET endpoint at /nodes/
*GET requests to the node’s API (/nodes/<uuid>) and node detail API (/nodes/details) should return the current node.clean_step as well.
https:/
https:/
Notes entered on 159322:
Bumping this API change to Liberty, as discussed on IRC just now, for a couple reasons:
1. this change isn't necessary for the actual "cleaning" to occur, and we're very short on time for Kilo-3
2. the semantics are different for in-band and out-of-band drivers
3. it merely lists the steps which the driver(s) think they are going to take, which may not be the actual steps taken
Addressed by: https:/
Use task.spawn_after to maintain lock during cleaning
Addressed by: https:/
Add documentation for Cleaning
Addressed by: https:/
Cleaning docs followup: Add that it's new in Kilo
Addressed by: https:/
Prevent power actions on node in cleaning
Addressed by: https:/
Update docs: No power actions during cleaning
Addressed by: https:/
Clarify message for power action during cleaning
Work Items
Dependency tree
* Blueprints in grey have been implemented.
