diskimage-builder/diskimage_builder/elements/centos-minimal/environment.d/10-centos-distro-name.bash

export DISTRO_NAME=centos
export DIB_RELEASE=${DIB_RELEASE:-7}

# by default, enable DHCP configuration of eth0 & eth1 in network
# scripts.  See yum-minimal for full details
export DIB_YUM_MINIMAL_CREATE_INTERFACES=${DIB_YUM_MINIMAL_CREATE_INTERFACES:-1}

# Useful for elements that work with fedora (dnf) & centos
export YUM=${YUM:-yum}
Port centos-minimal to yum-minimal Now that we have a generic yum-minimal element, just use it in centos instead of rinse. Adding base as an element-provides of yum-minimal because this element conflicts with the base element. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I15275d821781171c118f21aa0c0bca55f65a65b3 2015-03-22 17:45:07 +00:00			`export DISTRO_NAME=centos`
			`export DIB_RELEASE=${DIB_RELEASE:-7}`
yum-minimal: do not configure eth0 & eth1 for DHCP automatically 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 2015-12-14 04:26:11 +00:00
			`# by default, enable DHCP configuration of eth0 & eth1 in network`
			`# scripts. See yum-minimal for full details`
			`export DIB_YUM_MINIMAL_CREATE_INTERFACES=${DIB_YUM_MINIMAL_CREATE_INTERFACES:-1}`
Revert "Revert "Pre-install pip/virtualenv packages"" This reverts commit a645fa4ffb3c819f38ce1c66e83eb409c587c55d. It is really devstack causing problems here; it was removing the python-virtualenv package & re-installing using pip (see depends-on). This failed because the pip-install we did here removed the egg-file that rpm expected to be there, so rpm bailed out on the removal. But even if it worked, this just leads you back down the path of the original problem; that the system packaged version can be re-installed and overwrites the pip installed version. Thus I still believe this is the correct thing to do in the dib element. Note it is not a common problem (devstack aside); most jobs don't touch python-virtualenv & related packages (the one we did notice this on was being brought over from travisci where it was required for some reason). Change-Id: I82acb865378a0fa5903a6267bfcee0e2962eced0 Depends-On: Ib0edf6c4ee8a510e9d671213de35d787f56acfed 2016-07-14 03:43:06 +00:00
			`# Useful for elements that work with fedora (dnf) & centos`
			`export YUM=${YUM:-yum}`