diskimage-builder/diskimage_builder/elements/dhcp-all-interfaces
waleedm b50b8489d8 fix ifupdown pkg map for dhcp-all-interfaces of redhat family
Now as network-scripts package is derprecated, and NM should be the default for managing networking in redhat OS family, we need ifup/down scripts for dhcp-all-interfaces element and no one is providing them
So adding the package map for redhat family in the element source

Change-Id: I11e596e17477c39b156617762c4c5b840754ed64
2023-04-05 09:44:40 +00:00
..
install.d
element-deps
package-installs.yaml
pkg-map fix ifupdown pkg map for dhcp-all-interfaces of redhat family 2023-04-05 09:44:40 +00:00
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

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

DIB_DHCP_CLIENT
  :Required: no
  :Default: internal
  :Description: When NetworkManager is in use, this setting conveys which DHCP
   client is in use for acquiring a DHCP address for the node. In some specific
   cases, where known that dhclient is the tested or most compatible default,
   specifically for Centos 7, 8, and 8-Stream, as well as derived distributions.
   Otherwise, the "internal" dhcp client is the default.
  :Example: DIB_DHCP_CLIENT