b91e212434
If rdisc6 is available, a node using this element will loops until DIB_DHCP_TIMEOUT is reached because of a missing 'break' when rdisc6 return code is 0. This will mark the dhcp-interface@.service unit as failed (because it has the same timeout) and not bring any network interface online. Change-Id: I034dcda94d765f236950ebcbee36789f5bdc515f Closes-Bug: #1854717 Signed-off-by: Hervé Rousseau <hroussea@cern.ch> |
||
---|---|---|
.. | ||
install.d | ||
element-deps | ||
package-installs.yaml | ||
pkg-map | ||
README.rst |
=================== dhcp-all-interfaces =================== Autodetect network interfaces during boot and configure them for DHCP The rationale for this is that we are likely to require multiple network interfaces for use cases such as baremetal and there is no way to know ahead of time which one is which, so we will simply run a DHCP client on all interfaces with real MAC addresses (except lo) that are visible on the first boot. On non-Gentoo based distributions the script /usr/local/sbin/dhcp-all-interfaces.sh will be called early in each boot and will scan available network interfaces and ensure they are configured properly before networking services are started. On Gentoo based distributions we will install the dhcpcd package and ensure the service starts at boot. This service automatically sets up all interfaces found via dhcp and/or dhcpv6 (or SLAAC). Environment Variables --------------------- DIB_DHCP_TIMEOUT :Required: No :Default: 30 :Description: Amount of time in seconds that the systemd service(or dhclient) will wait to get an address. Should be increased in networks such as Infiniband. :Example: DIB_DHCP_TIMEOUT=300