Commit a9a48bf
authored
Enable automatic node cleaning (#2019)
The goal is to automatically clean nodes on undeployment. This can be
done by ironic through automated cleaning. Unfortunately this will also
enable cleaning when a node transitions from `managable` to `available`.
This would block `osism sync ironic`, since it waits sequentially for
every node to reach the `available` state.
An alternative is to add an explicit clean step in python-osism. However
the `osism manage baremetal undeploy` command is currently a oneshot
request to ironic. Adding a cleaning step would require turning it inot
an asynchronous task.
The taken path is to enable automated cleaning explicitly on a per node
basis once it reaches the `available` state. Care has to be taken to
unset it before transitioning to `available`, since ironic sometimes
moves nodes to `manageable` when errors are encountered.
Depends-On: osism/metalbox#292
Signed-off-by: Jan Horstmann <horstmann@osism.tech>1 parent c84cd54 commit a9a48bf
1 file changed
Lines changed: 20 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
263 | 263 | | |
264 | 264 | | |
265 | 265 | | |
| 266 | + | |
| 267 | + | |
| 268 | + | |
| 269 | + | |
| 270 | + | |
266 | 271 | | |
267 | 272 | | |
268 | 273 | | |
| |||
345 | 350 | | |
346 | 351 | | |
347 | 352 | | |
| 353 | + | |
| 354 | + | |
| 355 | + | |
| 356 | + | |
| 357 | + | |
348 | 358 | | |
349 | 359 | | |
350 | 360 | | |
| |||
353 | 363 | | |
354 | 364 | | |
355 | 365 | | |
| 366 | + | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
| 370 | + | |
356 | 371 | | |
357 | 372 | | |
358 | 373 | | |
| |||
380 | 395 | | |
381 | 396 | | |
382 | 397 | | |
| 398 | + | |
| 399 | + | |
| 400 | + | |
| 401 | + | |
| 402 | + | |
383 | 403 | | |
384 | 404 | | |
385 | 405 | | |
| |||
0 commit comments