Files
685e5660533e689734faf050ff27b2b465dcc3ab
puppet-openstack-integration /install_modules.sh

40 lines
1.2 KiB
Bash
Raw Normal View History

#!/bin/bash
Add Puppetfile and install script This repo will be cloned by the puppet modules and used to install modules in functional tests. The script uses r10k to deploy modules from the Puppetfile because this is the Puppet Labs recommended way to manage puppet environments, and it is a popular method among our users. We install all modules from git, not the forge, because r10k does not give us dependency resolution so installing from the forge does not buy us anything. If the modules have stable branches in git, r10k uses the stable branch as a ref, otherwise it uses a tag (pinning to a specific release). If zuul-cloner is available, the script first installs the external modules with r10k, then extracts the OpenStack modules from the Puppetfile to install with zuul-cloner. In the future, this part may be split out into a JJB job. Note: because r10k purges the modules directory before installing modules, and this feature cannot be turned off[1], we must run r10k to install the external modules before running zuul-cloner to install the OpenStack modules. [1] https://github.com/puppetlabs/r10k/issues/172 Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015年06月30日 16:59:52 -07:00
set -ex
GEM_INSTALL_CMD="gem install --no-user-install --minimal-deps --verbose --no-document"
if [ -n "${GEM_HOME}" ]; then
GEM_BIN_DIR=${GEM_HOME}/bin/
export PATH=${PATH}:${GEM_BIN_DIR}
GEM_INSTALL_CMD="${GEM_INSTALL_CMD} --install-dir=$GEM_HOME --bindir=${GEM_BIN_DIR}"
fi
# NOTE(aschultz): since puppet 3 is now EOL, and beaker-puppet_install_helper
# version 0.6.0 has made the agent version the default, we need to symlink
# puppet to the /opt/puppetlabs version when specifically not version 3.
if [ -e /opt/puppetlabs/bin/puppet ]; then
export PUPPET_BASE_PATH=/etc/puppetlabs/code
export PATH=${PATH}:/opt/puppetlabs/bin:/opt/puppetlabs/puppet/bin
sudo -E ln -sfn /opt/puppetlabs/bin/puppet /usr/sbin/puppet
fi
export SCRIPT_DIR=$(cd `dirname 0ドル` && pwd -P)
export PUPPETFILE_DIR=${PUPPETFILE_DIR:-${PUPPET_BASE_PATH}/modules}
source $SCRIPT_DIR/functions
Add Puppetfile and install script This repo will be cloned by the puppet modules and used to install modules in functional tests. The script uses r10k to deploy modules from the Puppetfile because this is the Puppet Labs recommended way to manage puppet environments, and it is a popular method among our users. We install all modules from git, not the forge, because r10k does not give us dependency resolution so installing from the forge does not buy us anything. If the modules have stable branches in git, r10k uses the stable branch as a ref, otherwise it uses a tag (pinning to a specific release). If zuul-cloner is available, the script first installs the external modules with r10k, then extracts the OpenStack modules from the Puppetfile to install with zuul-cloner. In the future, this part may be split out into a JJB job. Note: because r10k purges the modules directory before installing modules, and this feature cannot be turned off[1], we must run r10k to install the external modules before running zuul-cloner to install the OpenStack modules. [1] https://github.com/puppetlabs/r10k/issues/172 Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015年06月30日 16:59:52 -07:00
print_header 'Start (install_modules.sh)'
print_header 'Install r10k'
$GEM_INSTALL_CMD r10k
# make sure there is no puppet module pre-installed
rm -rf "${PUPPETFILE_DIR:?}/"*
print_header 'Install Modules'
install_modules
Add Puppetfile and install script This repo will be cloned by the puppet modules and used to install modules in functional tests. The script uses r10k to deploy modules from the Puppetfile because this is the Puppet Labs recommended way to manage puppet environments, and it is a popular method among our users. We install all modules from git, not the forge, because r10k does not give us dependency resolution so installing from the forge does not buy us anything. If the modules have stable branches in git, r10k uses the stable branch as a ref, otherwise it uses a tag (pinning to a specific release). If zuul-cloner is available, the script first installs the external modules with r10k, then extracts the OpenStack modules from the Puppetfile to install with zuul-cloner. In the future, this part may be split out into a JJB job. Note: because r10k purges the modules directory before installing modules, and this feature cannot be turned off[1], we must run r10k to install the external modules before running zuul-cloner to install the OpenStack modules. [1] https://github.com/puppetlabs/r10k/issues/172 Change-Id: Ide59ef4bdf53a04957e3593815b7514a0e744e0e
2015年06月30日 16:59:52 -07:00
print_header 'Module List'
puppet module list
print_header 'Done (install_modules.sh)'