puppet-openstack-integration/install_modules.sh

#!/bin/bash

set -ex

if [ ! -z ${GEM_HOME} ]; then
    GEM_BIN_DIR=${GEM_HOME}/bin/
fi

export SCRIPT_DIR=$(cd `dirname $0` && pwd -P)
export PUPPETFILE_DIR=${PUPPETFILE_DIR:-/etc/puppet/modules}
source $SCRIPT_DIR/functions

gem install r10k --no-ri --no-rdoc

# make sure there is no puppet module pre-installed
rm -rf "${PUPPETFILE_DIR:?}/"*

install_modules

puppet module list
Revert "Initial run_tests.sh script" This reverts commit 2921e36c790dd255b560f322f9444bd6d30be5f6. Change-Id: I88055528d143325457cdc2461dedb37f703374b9 2015-08-07 09:21:41 -04:00			`#!/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
Revert "Initial run_tests.sh script" This reverts commit 2921e36c790dd255b560f322f9444bd6d30be5f6. Change-Id: I88055528d143325457cdc2461dedb37f703374b9 2015-08-07 09:21:41 -04:00			`set -ex`

Initial run_tests.sh script This reverts commit 8b9db6da8629bd9dfdc70395b2cfe15a3f9d71d6 and applies some changes to not break Puppet beaker jobs. * First init of run_tests.sh script that will just run install_modules.sh script with sudo. The script also makes sure GEM_HOME is set so we can install r10k from gems and run it later. * install_modules: make sure to find r10k binary Change-Id: I24c7494e7c9201915d9aa2bf314a9534ddd27dd5 2015-08-07 09:25:02 -04:00			`if [ ! -z ${GEM_HOME} ]; then`
			`GEM_BIN_DIR=${GEM_HOME}/bin/`
			`fi`

Fix scripts to be OSX compatible readlink on OSX does not support the -f option. As an alternative, we can use pwd -P to resolve the path. Change-Id: Ibaeadea9685f7a9603198ed1a509176cf70f9b21 Closes-Bug: #1506504 2015-10-15 09:59:57 -05:00			export SCRIPT_DIR=$(cd `dirname $0` && pwd -P)
install_modules: allow to customize PUPPETFILE_DIR Allow to change PUPPETFILE_DIR but keep '/etc/puppet/modules' by default. Change-Id: Ie32d18d477c271b2724290edbbfd4ae7ea110480 2015-09-23 10:01:35 -04:00			`export PUPPETFILE_DIR=${PUPPETFILE_DIR:-/etc/puppet/modules}`
Create functions for common bits * Move out some code from install_modules.sh to have a functions script. * Update install_modules.sh script to use functions. Change-Id: Ie87b8eac71d5edb555e9a1637bea84bc9e268497 2015-10-05 16:39:26 -04:00			`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
Revert "Initial run_tests.sh script" This reverts commit 2921e36c790dd255b560f322f9444bd6d30be5f6. Change-Id: I88055528d143325457cdc2461dedb37f703374b9 2015-08-07 09:21:41 -04:00			`gem install r10k --no-ri --no-rdoc`

install_modules: cleanup /etc/puppet/modules Make sure there is no puppet modules pre-installed in the image where we run integration testing by cleaning up the /etc/puppet/modules/* directory. Change-Id: I489717356b75b95c1a881b6f3e554cfec66ee6f1 2015-08-22 11:33:29 -04:00			`# make sure there is no puppet module pre-installed`
			`rm -rf "${PUPPETFILE_DIR:?}/"*`

Create functions for common bits * Move out some code from install_modules.sh to have a functions script. * Update install_modules.sh script to use functions. Change-Id: Ie87b8eac71d5edb555e9a1637bea84bc9e268497 2015-10-05 16:39:26 -04:00			`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
Revert "Initial run_tests.sh script" This reverts commit 2921e36c790dd255b560f322f9444bd6d30be5f6. Change-Id: I88055528d143325457cdc2461dedb37f703374b9 2015-08-07 09:21:41 -04:00			`puppet module list`