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 |
||
|---|---|---|
| .. | ||
| environment.d | ||
| yum.repos.d | ||
| element-deps | ||
| element-provides | ||
| README.rst | ||
============== centos-minimal ============== Create a minimal image based on CentOS 7. 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. This element cannot be used with the base element, therefore must pass the -n flag to disk-image-create when using this element. 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. By default, `DIB_YUM_MINIMAL_CREATE_INTERFACES` is set to enable the creation of `/etc/sysconfig/network-scripts/ifcfg-eth[0|1]` scripts to enable DHCP on the `eth0` & `eth1` interfaces. If you do not have these interfaces, or if you are using something else to setup the network such as cloud-init, glean or network-manager, you would want to set this to `0`.