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
This commit is contained in:
parent
255fac17a0
commit
a599f898dc
@ -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
|
||||
|
5
releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml
Normal file
5
releasenotes/notes/dhcp-less-less-2a35df67d840f9d5.yaml
Normal file
@ -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.
|
Loading…
Reference in New Issue
Block a user