sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e129fad7f8
diskimage-builder/diskimage_builder/elements/dhcp-all-interfaces/README.rst

42 lines
1.7 KiB
ReStructuredText
Raw Normal View History

Create docs site containing element READMEs We currently do not have the ability to create a docs site which outlines all the elements. Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b
2015-02-07 10:30:02 +00:00
===================
dhcp-all-interfaces
===================
Add element to run DHCP on all network interfaces. Ensures that all network interfaces are present in /etc/network/interfaces. Any interface not already defined there will be added and configured for DHCP. Change-Id: I27e0902e62804e8d719acd7288109bd0e294fd16
2013-03-05 17:34:19 +00:00
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
Only configure DHCP for real interfaces Updates the generate-interfaces-file.sh script in the dhcp-all-interfaces element so that we only add interfaces that have real MAC addresses. The generate-interfaces-file.sh script is run early enough in the boot process (before OVS is initialized) that this isn't usually a problem unless you execute it manually by hand after booting. Then you'll end up with network/DHCP configs for all of your OVS bridges, etc. This patch avoids configuring all of the virtual interfaces which have generated MAC addresses. Change-Id: I7a705084aa5b11305ac0ec5ca37fd2e87a2ae8b7 Closes-bug: 1239479
2014-01-21 20:58:45 +00:00
DHCP client on all interfaces with real MAC addresses (except lo) that
are visible on the first boot.
Add element to run DHCP on all network interfaces. Ensures that all network interfaces are present in /etc/network/interfaces. Any interface not already defined there will be added and configured for DHCP. Change-Id: I27e0902e62804e8d719acd7288109bd0e294fd16
2013-03-05 17:34:19 +00:00
Add Gentoo to the dhcp-all-interfaces element This makes use of the dhcpcd package and it's ability to run on all interfaces by default. We disable the privacy extensions and dhcp overriding the hostname (both are enabled by default). Other than that it 'just works' and was the method used to bring up interfaces on Gentoo Openstack images before we switched to building with DIB. Change-Id: I02c14927d70b22f560c6fc149fefca0f93933f56
2016-03-31 00:48:19 +00:00
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).
Make DHCP timeout configurable As noted in the bug, there may be circumstances where a longer timeout than the current default is needed. This patch allows users to tune this timeout for their environment if need be. Change-Id: I173f3dad684894fbc3c27dece5ae15b5f63bae5a Closes-Bug: 1654027
2017-01-04 17:21:03 +00:00
Environment Variables
---------------------
DIB_DHCP_TIMEOUT
:Required: No
:Default: 30
Set the dhclient timeout to match DIB_DHCP_TIMEOUT On initial boot when networking is brought up by cloud-init this is the timeout that dhclient adheres to. Centos configures "timeout 300" (for an EC2 bug) in their cloud image, which results in a 5 minutes delay to boot in cases where no dhcp available (e.g. IPv6 SLAAC). To reduce this boot delay and to provide consistency with places where we have set other dhcp timeouts set this to DIB_DHCP_TIMEOUT. Change-Id: I119a002070501c3dfe7c6730b07ee25f422b85b0 Related-Bug: #1758324
2018-04-05 13:12:09 +00:00
: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.
Make DHCP timeout configurable As noted in the bug, there may be circumstances where a longer timeout than the current default is needed. This patch allows users to tune this timeout for their environment if need be. Change-Id: I173f3dad684894fbc3c27dece5ae15b5f63bae5a Closes-Bug: 1654027
2017-01-04 17:21:03 +00:00
:Example: DIB_DHCP_TIMEOUT=300
dhcp-all-interfaces: opt let NetworkManager doit. NetworkManager is quite capable to do automatic interface configuration. NetworkManager will by default try to auto-configure any interface with no configuration. It will use DHCP for IPv4 and Router Advertisements to decide how to initialize IPv6. It will most likely do it just as good, or better than the dhcp-all-interfaces.sh script. Since dhcp-all-interfaces clean out all ifcfg files in 60-remove-cloud-image-interfaces it means NetworkManager will by default attempt auto configuration for all interfaces. This change add's and environment variable: DIB_DHCP_NETWORK_MANAGER_AUTO (default: false) When DIB_DHCP_NETWORK_MANAGER_AUTO is set to `true` only the NetworkManager config will be written. The dhcp-all-interfaces service will not be installed. Hence dhcp-all-interfaces will not write any config files, allowing NetworkManager to just do it's thing. Change-Id: Id6f8d6aaaf52a78175bb6c065ec88274c364834e
2022-01-23 22:09:11 +00:00
DIB_DHCP_NETWORK_MANAGER_AUTO
:Required: No
:Default: false
:Description: When NetworkManager is detected, and this is set to true the
dhcp-all-interfaces service will not be installed. Only the NetworkManager
configuration will be added. NetworkManager is quite capable to do automatic
interface configuration. NetworkManager will by default try to
auto-configure any interface with no configuration, it will use DHCP for
IPv4 and Router Advertisements to decide how to initialize IPv6.
:Example: DIB_DHCP_NETWORK_MANAGER_AUTO=true
Reference in New Issue Copy Permalink