1f499360fc
Add an environment variable to control the creation of eth0/1 interface enablement scripts. With a tool such as glean, the presence of these scripts will indicate the interface is configured and configuration-drive settings will not be applied. This means in a non-dhcp situation like on Rackspace, network is broken. On Fedora, where later systemd provides "predictable network interface names" [1] eth0 & eth1 ironically aren't predictable so this just confuses things. You really need cloud-init or glean or something to bring up your interfaces in a sane fashion. This maintains the status-quo on centos-minimal, but disables creation for fedora-minimal. [1] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Change-Id: I3f1ffeb6de3b1f952292a144efab9554f7f99a5f |
||
---|---|---|
.. | ||
install.d | ||
pre-install.d | ||
root.d | ||
element-deps | ||
package-installs.yaml | ||
pkg-map | ||
README.rst |
=========== yum-minimal =========== Base element for creating minimal yum-based images. This element is incomplete by itself, you'll want to use the centos-minimal or fedora-minimal elements to get an actual base image. Use of this element will require 'yum' and 'yum-utils' to be installed on Ubuntu and Debian. Nothing additional is needed on Fedora or CentOS. The `DIB_OFFLINE` or more specific `DIB_YUMCHROOT_USE_CACHE` variables can be set to prefer the use of a pre-cached root filesystem tarball. If you wish to have DHCP networking setup for eth0 & eth1 via /etc/sysconfig/network-config scripts/ifcfg-eth[0|1], set the environment variable `DIB_YUM_MINIMAL_CREATE_INTERFACES` to `1`.