openstack/ironic
Code Issues Proposed changes

Document that DHCP-less deploy does work with debian-minimal

Browse Source 
Change-Id: I9ec4f9ceac0c5517ce59c6db3681ef9dc643ec14
This commit is contained in:
Dmitry Tantsur 2020-12-16 19:42:58 +01:00
parent a58b88c737
commit 3b15d543f1
2 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/admin/dhcp-less.rst
View File

@ -1,12 +1,6 @@
Layer 3 or DHCP-less ramdisk booting
====================================
.. warning::
As of the Victoria release, the ramdisk side of this feature does **NOT**
work out-of-box because of a conflict between NetworkManager and Glean_.
To use it properly you need to manually create a ramdisk with Glean_ taking
priority over any other network configuration.
Booting nodes via PXE, while universally supported, suffers from one
disadvantage: it requires a direct L2 connectivity between the node and the
control plane for DHCP. Using virtual media it is possible to avoid not only
@ -21,6 +15,16 @@ The Glean_ tool will look for a media labeled as ``config-2``. If found, the
network information from it will be read, and the node's networking stack will
be configured accordingly.
.. code-block:: console
ironic-python-agent-builder -o /output/ramdisk \
debian-minimal -e simple-init
.. warning::
The simple-init_ element is found to conflict to NetworkManager, which makes
this feature not operational with ramdisks based on CentOS, RHEL and Fedora.
The ``debian-minimal`` element seems to work correctly.
.. note::
If desired, some interfaces can still be configured to use DHCP.

3
releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml
View File

@ -2,4 +2,5 @@
issues:
- |
Building ramdisks for DHCP-less deploy using the ``simple-init`` element
does not currently work. The team is looking into possible solutions.
is known not to work for distributions using NetworkManager.
The ``debian-minimal`` element seems to work.