Aborting node deployment
The utility-ramdisk blueprint[1] will make the ramdisk to ask the Ironic API for the next task it has to execute, when the deployment is set to be aborted, in the next iteration with the Ironic API, the API will just tell the node to stop everything it's doing and power-off, the API should also be responsable for cleaning up the target state of that node.
Some deployments can't be aborted, for e.g firmware updates. When the driver is about to start a deployment (after validations) it should mark that deployment as interruptible[2].
[1] https:/
[2] https:/
API Design:
The provisionment of a node is an asynchronous task that could be trigged via the Ironic API by sending a PUT request to the /nodes/
In order to abort that task, this blueprint proposes the following design on the Ironic API:
* Using the DELETE method to trigger the abortion
* DELETE as an asynchronous task
The client could issue a DELETE to the /nodes/
Issuing a DELETE to the /nodes/
Issuing a DELETE to the /nodes/
Blueprint information
- Status:
- Complete
- Approver:
- aeva black
- Priority:
- Undefined
- Drafter:
- Lucas Alvares Gomes
- Direction:
- Needs approval
- Assignee:
- Lucas Alvares Gomes
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Lucas Alvares Gomes
Related branches
Related bugs
Sprints
Whiteboard
Lucas, in the API, would DELETE of an in-progress-
-Deva
Yes, I thinking of it as a task running in the background, so once the deployment is completed that task is gone and it would return 404. But it looks abit inconsistent, so I think we might want to discuss a bit more how such triggers are going to work in our API, please take a look at https:/
-Lucas