diff options
| author | Dmitry Tantsur <divius.inside@gmail.com> | 2018-10-18 15:12:06 +0200 |
|---|---|---|
| committer | Dmitry Tantsur <divius.inside@gmail.com> | 2018-11-27 10:07:30 +0100 |
| commit | 68d62f2bee879306a4951b5d7dd54eabaa17d1bc (patch) | |
| tree | 3a3b48375c8de2315e4477fdb8a0b3b238aca249 /releasenotes | |
| parent | 0ea86814ad07278b6a7b542a34c80f0d0ac0f3c8 (diff) | |
| download | ironic-68d62f2bee879306a4951b5d7dd54eabaa17d1bc.tar.gz | |
Support for protecting nodes from undeploying and rebuilding
When handling the "pet" case, some nodes may be critical for the deployment.
For example, in an OpenStack installer like TripleO you may want to make
sure your controllers are not removed by an incorrect operation.
This changes introduces a new field "protected" on nodes. When it is
set to True, the "deleted" and "rebuild" provisioning actions fail with
HTTP 403. Deleting such nodes is also not possible.
Also adds "protected_reason" for the operators to specify the reason
a node is protected.
Story: #2003869
Task: #26706
Change-Id: I1950bf6dd65b6596cae69d431ef288e578a89d6e
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/protected-650acb2c8a387e17.yaml | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/releasenotes/notes/protected-650acb2c8a387e17.yaml b/releasenotes/notes/protected-650acb2c8a387e17.yaml new file mode 100644 index 000000000..154279329 --- /dev/null +++ b/releasenotes/notes/protected-650acb2c8a387e17.yaml @@ -0,0 +1,7 @@ +--- +features: + - | + It is now possible to protect a provisioned node from being undeployed, + rebuilt or deleted by setting the new ``protected`` field to ``True``. + The new ``protected_reason`` field can be used to document the reason + the node was made protected. |