openstack/ironic
Code Issues Proposed changes

Deprecate [agent]/manage_agent_boot

Browse Source 
This configuration directive is completely untested, undocumented,
and requires deployers to manually configure significant
infrastructure for it. It also bypasses several deploy-time sanity
checks around whether or not we expect the server to boot.
Deprecating it for removal in 2025.2 release.

Related-bug: #2071741
Change-Id: Id73d9097e9e4152c7b635a4269b548c9dbdda0a6
This commit is contained in:
Jay Faulkner 2024-07-02 15:20:52 -07:00
parent 3820fc19c9
commit 465bedbe7f
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
ironic/conf/agent.py
View File

@ -25,7 +25,8 @@ opts = [
help=_('Whether Ironic will manage booting of the agent ' help=_('Whether Ironic will manage booting of the agent '
'ramdisk. If set to False, you will need to configure ' 'ramdisk. If set to False, you will need to configure '
'your mechanism to allow booting the agent ' 'your mechanism to allow booting the agent '
'ramdisk.')), 'ramdisk. Deprecated for removal in 2025.2 release.'),
deprecated_for_removal=True),
cfg.IntOpt('memory_consumed_by_agent', cfg.IntOpt('memory_consumed_by_agent',
default=0, default=0,
mutable=True, mutable=True,

9
releasenotes/notes/deprecate-manage-agent-boot-8474287a11b485cc.yaml Normal file
View File

@ -0,0 +1,9 @@
---
deprecations:
- |
The ``[[agent]]manage_agent_boot`` configuration directive is being
deprecated. It is completely untested, and requires operators to
manually configure significant parts of infrastructure typically
handled by Ironic. Operators using this configuration are advised
to migrate away from it before it's scheduled removal during the
2025.2 cycle releases, coming out late 2025.