From a599f898dc16e398387169fa01f2e9444f7af519 Mon Sep 17 00:00:00 2001 From: Dmitry Tantsur Date: Tue, 15 Dec 2020 14:48:04 +0100 Subject: 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 --- doc/source/admin/dhcp-less.rst | 6 ++++++ releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml | 5 +++++ 2 files changed, 11 insertions(+) create mode 100644 releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml 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 diff --git a/releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml b/releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml new file mode 100644 index 000000000..f6b5020a1 --- /dev/null +++ b/releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml @@ -0,0 +1,5 @@ +--- +issues: + - | + Building ramdisks for DHCP-less deploy using the ``simple-init`` element + does not currently work. The team is looking into possible solutions. -- cgit v1.2.1