diff options
author | Dmitry Tantsur <dtantsur@protonmail.com> | 2020-12-15 14:48:04 +0100 |
---|---|---|
committer | Dmitry Tantsur <dtantsur@protonmail.com> | 2020-12-15 14:48:04 +0100 |
commit | a599f898dc16e398387169fa01f2e9444f7af519 (patch) | |
tree | e908fc11c3cfc17b980ee0565ec656f29aaed8e1 /doc | |
parent | 255fac17a08aaaf11aff94cb9799ad41c7e64c58 (diff) | |
download | ironic-a599f898dc16e398387169fa01f2e9444f7af519.tar.gz |
Document the current status of the DHCP-less deploy
I could not make the ramdisk side work on a variety of distributions,
the same problem has been confirmed by another contributor. Until we
get a working procedure for building a ramdisk, add an ugly warning
to the documentation.
Change-Id: I12100539b9987fcb47ba81c75ec96ed501d50c82
Diffstat (limited to 'doc')
-rw-r--r-- | doc/source/admin/dhcp-less.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/source/admin/dhcp-less.rst b/doc/source/admin/dhcp-less.rst index a009d81a2..3e848389f 100644 --- a/doc/source/admin/dhcp-less.rst +++ b/doc/source/admin/dhcp-less.rst @@ -1,6 +1,12 @@ 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 |