2747613ca2
We are currently wasting about 10 minutes per deploy waiting for DHCP on interfaces that will never get it. By default, the timeout seems to be 5 minutes (the 10 minutes is because we boot both the IPA ramdisk and the deployed image, and each waits for 5 minutes), which is excessively long to get a DHCP response. This change shortens the time to 30 seconds. If an interface hasn't gotten a response in 30 seconds, chances are it's not going to. A 30 second wait should reduce our wasted time to 1 minute, which is more reasonable. This is being done in the systemd unit file because the -timeout option to dhclient doesn't seem to override what is configured in dhclient.conf, and doing it in the systemd file means that this change will be limited to only the interfaces configured by dhcp-all-interfaces. Change-Id: Ia8610e3def39c937eb0c861fdc9bc571ec39f9f4 Closes-Bug: 1626673 |
||
|---|---|---|
| .. | ||
| 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).