0eda3d65ea
Ironic already has support for automatically setting a lessee on deployment, but it is only supported for direct deployments with Ironic, as it uses request context which is not preserved in the Nova driver. Now, when combined with the related Nova change, Ironic can support this behavior for fully integrated installations. On deploy time, Nova will set several fields -- including project_id -- in instance info. If enabled, Ironic will then use that project_id as the automatic lessee. The previous behavior of using the project_id from the request context is still supported as a fallback. This is being tracked in nova as blueprint ironic-guest-metadata. Closes-Bug: #2063352 Change-Id: Id381a3d201c2f1b137279decc0e32096d4d95012
24 lines
1.2 KiB
YAML
24 lines
1.2 KiB
YAML
features:
|
|
- |
|
|
Ironic now supports automatically setting node.lessee at deployment time
|
|
using metadata provided at deploy time, typically by OpenStack Nova. When
|
|
``[conductor]/automatic_lessee_source`` is set to ``instance``,
|
|
Ironic will set the lessee field on the node and remove it before cleaning.
|
|
upgrade:
|
|
- |
|
|
``[conductor]/automatic_lessee`` has been deprecated in favor of
|
|
``[conductor]/automatic_lessee_source``.
|
|
|
|
Standalone Ironic deployments previously setting ``automatic_lessee`` to
|
|
``True`` now may want to set ``automatic_lessee_source`` to ``request`` to
|
|
retain existing behavior.
|
|
|
|
Deployers explicitly setting ``automatic_lessee`` to false may want to set
|
|
``automatic_lessee_source`` to ``none`` to retain existing behavior. The
|
|
old configuration option, when explicitly set, will be honored until
|
|
fully removed.
|
|
- |
|
|
Ironic will now automatically set the node.lessee field for all
|
|
deployments by default when provided in node instance_info at deployment
|
|
time. Deployers are encouraged to review their security settings and
|
|
Ironic Secure RBAC documentation to ensure no unexpected access is granted. |