puppet-openstack-integration

Create puppet folder layout * create fixtures directory that will contain manifests to run. * Add an empty scenario001.pp file to ensure our gate is properly working. This implementation is basic and is not definitive. It aims to scale-up later once we have multiple scenarios. Change-Id: I0149c7887c8e664ca895be8ce4df5f620c5c6d0c Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年07月13日 15:04:45 -04:00

#!/bin/bash -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

#

# Licensed under the Apache License, Version 2.0 (the "License"); you may

# not use this file except in compliance with the License. You may obtain

# a copy of the License at

#

# http://www.apache.org/licenses/LICENSE-2.0

#

# Unless required by applicable law or agreed to in writing, software

# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT

# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the

# License for the specific language governing permissions and limitations

# under the License.

run_tests.sh: default WORKSPACE to /tmp When I run p-o-i on my laptop, logs go into / which is weird. Default $WORKSPACE to /tmp, so when we run the scripts outside OpenStack Infra environment, logs are visible in a safe place. Change-Id: Ib8b0f9417098bcf703e31984804f2b72a8d93866

2017年01月12日 07:46:35 -05:00

export WORKSPACE=${WORKSPACE:-/tmp}

Rename PUPPET_VERSION to PUPPET_MAJ_VERSION PUPPET_VERSION is already used by puppetlabs/beaker and we don't want to overlap with this variable. So let's rename it to PUPPET_MAJ_VERSION to avoid strange behaviors when running Beaker jobs. Change-Id: I74be2eec2be53f59af196f37ee348ff6856af8bc

2016年06月07日 17:58:23 -04:00

export PUPPET_MAJ_VERSION=${PUPPET_MAJ_VERSION:-3}

run_tests: allow to run another scenario * create $SCENARIO environment variable. * test if fixtures/$SCENARIO.pp file exist or fail early. * in comment, drop OpenStack project names hard-coding. Change-Id: I80f07ba6ee2123bc24eb33eac6f600e2ea7c63da

2015年10月01日 12:46:02 -04:00

export SCENARIO=${SCENARIO:-scenario001}

Add ability to manually install puppet modules This commit adds the ability to manually install puppet modules. This is useful when using an installation method not provided by the PUPPETFILE_DIR environment variable. Change-Id: Ie6519d8adb989eaec59d2f3047205c4fa2212419

2016年02月16日 14:32:33 -08:00

export MANAGE_PUPPET_MODULES=${MANAGE_PUPPET_MODULES:-true}

Provide a toggle to disable repository management by puppet By default, repositories will be managed by puppet through manifests/repos.pp. If someone wants to set up different repositories outside of puppet entirely, he can "export MANAGE_REPOS=false" and run_tests will not run repos.pp. Change-Id: I3a09a2be1d2a064e784ed24f189fec41476330d9

2015年12月15日 15:27:32 -05:00

export MANAGE_REPOS=${MANAGE_REPOS:-true}

Align the stars to bring our CI back 1) Add 2GB swap by default Add some swap when running CI jobs, so we can reduce the number of failures in CI related to missing memory. By default 2GB, can be disabled or increased/decreased with parameters. 2) Promote RDO repository to have Oslo DB from master python-oslo-db 4.13.x releases are known to break Gnocchi. https://review.openstack.org/367221 will fix it, but it is not yet in any release, so RDO unpinned oslo.db until that happens. 3) Disable Ironic testing on Ubuntu. Packages are broken in recent Newton upgrade. They are working on it. 4) Enable br_netfilter kernel module on Ubuntu. See https://bugs.launchpad.net/cloud-archive/+bug/1621651 Even if it's not critical, it's a nice-to-have because it removed the ERROR that we had in neutron logs. We'll see how the bug report evolve and maybe remove this workaround. 5) Export lsmod in logs, easier for us to debug later. 6) Disable linuxbridge on scenario003 for Ubuntu Also see https://bugs.launchpad.net/cloud-archive/+bug/1621651 7) Pin Puppetlabs release package. Context: https://tickets.puppetlabs.com/browse/CPR-378 Change-Id: I732ef375a681f03af751ebb6ebd5b12df55a0ecc

2016年09月08日 13:43:30 -04:00

export ADD_SWAP=${ADD_SWAP:-true}

export SWAP_SIZE_GB=${SWAP_SIZE_GB:-2}

Implement all-in-one.sh script This script will help newcomers to run this script and deploy a simple scenario of an OpenStack Cloud with Puppet OpenStack modules. Change-Id: I559e5e0a0d21a02d04b3d999b77dee23bb38c341

2015年11月05日 12:02:15 -05:00

export SCRIPT_DIR=$(cd `dirname 0ドル` && pwd -P)

Add hiera support This change adds hiera support into the scenarios so we can override items via the common.yaml heira file if need be. This change adds support for two environment variables with run_tests.sh. HIERA_CONFIG - full path to the hiera yaml configuration file MANAGE_HIERA - used to enable/disable writing out a hiera.yaml config file Change-Id: Iad0050e09e0cc610e0eadc00e328151e88eee10e

2016年07月13日 13:50:17 -06:00

export HIERA_CONFIG=${HIERA_CONFIG:-${SCRIPT_DIR}/hiera/hiera.yaml}

export MANAGE_HIERA=${MANAGE_HIERA:-true}

Split out puppet logs To improve troubleshooting and readability, let's not have the puppet logs print to the console. This change updates the puppet apply to output the logs to puppet.log which will still be captured and provided in the CI results. When the puppet apply fails, we will grep for warnings and errors from the puppet log and only print those out which should simplify troubleshooting failures. Change-Id: I1084223f805f1960aebb9c5868fdef84ff3667e4

2016年10月31日 15:15:34 -06:00

export PUPPET_ARGS="${PUPPET_ARGS} --detailed-exitcodes --color=false --test --trace --hiera_config ${HIERA_CONFIG} --logdest ${WORKSPACE}/puppet.log"

Support of Ubuntu 16.04 LTS Xenial deployments Add support for Xenial deployments. * Disable SSL on Ubuntu Xenial deployments. * Pin puppetlabs-mysql to a recent commit (until they produce a new tag). * Disable Ceph on Ubuntu Xenial deployments, neither Hammer or Jewel currently work out of the box with puppet-ceph on Xenial. * Disable Horizon on Ubuntu Xenial deployments: not working yet. * Do not deploy UCA on Xenial, since we currently deploy Mitaka. * On Xenial, deploy Puppet using distro packaging, not puppetlabs.com. * Cleanup /etc/default/puppet on Xenial / Puppet4 runs (workaround) until we figure what is installing this file on Xenial nodepool image. All issues are documented here: See https://etherpad.openstack.org/p/puppet-openstack-xenial Change-Id: Ifc8c7e241add830c88b84c1f01770e5e15df1653

2016年04月20日 14:54:36 -04:00

export DISTRO=$(lsb_release -c -s)

Unpin Tempest Tempest has been fixed upstream. We shouldn't have to pin it anymore. Change-Id: I14ceda3ebad7797cbd278199ea3c3bc8151dbf66

2016年12月20日 11:16:58 -05:00

# If openstack/tempest is broken on master, we can pin the repository to a specific commit

# by using the following line:

# export TEMPEST_VERSION=${TEMPEST_VERSION:-'382a2065f3364a36c110bfcc6275a0f8f6894773'}

export TEMPEST_VERSION=${TEMPEST_VERSION:-'origin/master'}

Round 1 of Puppet 4 support This commit puts in place the ability to run puppet-openstack-integation against Pupept 4 by making release files and paths dynamic based off an environment variable, PUPPET_VERSION. Configurability is required because of the way Puppet 4 is installed, as an all-in-one package known as "PC1" or "puppet-agent" which includes Ruby, Facter 3, and other dependencies. Change-Id: Id3af52f4938378a5a620765321cecd547e079660

2016年03月15日 18:36:38 -07:00

Add bits to use AFS mirrors Like we do in stable branches, deploy AFS mirrors. For now, use it only for UCA. Change-Id: I6574f5b1f99e6ae8021cff68949173c6cbba6960 Co-Authored-By: Paul Belanger <pabelanger@redhat.com>

2016年07月08日 09:13:40 -04:00

# NOTE(pabelanger): Setup facter to know about AFS mirror.

if [ -f /etc/nodepool/provider ]; then

source /etc/nodepool/provider

NODEPOOL_MIRROR_HOST=${NODEPOOL_MIRROR_HOST:-mirror.$NODEPOOL_REGION.$NODEPOOL_CLOUD.openstack.org}

NODEPOOL_MIRROR_HOST=$(echo $NODEPOOL_MIRROR_HOST|tr '[:upper:]' '[:lower:]')

CENTOS_MIRROR_HOST=${NODEPOOL_MIRROR_HOST}

repos: deploy ceph using OpenStack mirrors Deploy Ceph packages using OpenStack AFS mirrors to go faster and be more reliable in OpenStack Infrastructure. Change-Id: I3b96b7dfe20ba01a1d833b47fcfb184a458c6975

2016年07月19日 16:44:35 -04:00

UCA_MIRROR_HOST="${NODEPOOL_MIRROR_HOST}/ubuntu-cloud-archive"

repos: fix Ceph mirror when running outside p-o-i When running outside p-o-i (ie: beaker jobs), we don't execute run_tests.sh so we don't have the facts in place to configure mirrors. This patch makes sure the ceph_mirror_fact is empty by default, and overriden if used in p-o-i with run_tests. Change-Id: I375adcc4d5e436c40bae8ede5ee2ff7ab3b25409

2016年07月20日 17:04:38 -04:00

CEPH_MIRROR_HOST="${NODEPOOL_MIRROR_HOST}/ceph-deb-jewel"

Add bits to use AFS mirrors Like we do in stable branches, deploy AFS mirrors. For now, use it only for UCA. Change-Id: I6574f5b1f99e6ae8021cff68949173c6cbba6960 Co-Authored-By: Paul Belanger <pabelanger@redhat.com>

2016年07月08日 09:13:40 -04:00

else

CENTOS_MIRROR_HOST='mirror.centos.org'

repos: deploy ceph using OpenStack mirrors Deploy Ceph packages using OpenStack AFS mirrors to go faster and be more reliable in OpenStack Infrastructure. Change-Id: I3b96b7dfe20ba01a1d833b47fcfb184a458c6975

2016年07月19日 16:44:35 -04:00

UCA_MIRROR_HOST='ubuntu-cloud.archive.canonical.com/ubuntu'

repos: fix Ceph mirror when running outside p-o-i When running outside p-o-i (ie: beaker jobs), we don't execute run_tests.sh so we don't have the facts in place to configure mirrors. This patch makes sure the ceph_mirror_fact is empty by default, and overriden if used in p-o-i with run_tests. Change-Id: I375adcc4d5e436c40bae8ede5ee2ff7ab3b25409

2016年07月20日 17:04:38 -04:00

CEPH_MIRROR_HOST='download.ceph.com/debian-jewel'

Add bits to use AFS mirrors Like we do in stable branches, deploy AFS mirrors. For now, use it only for UCA. Change-Id: I6574f5b1f99e6ae8021cff68949173c6cbba6960 Co-Authored-By: Paul Belanger <pabelanger@redhat.com>

2016年07月08日 09:13:40 -04:00

fi

export FACTER_centos_mirror_host="http://${CENTOS_MIRROR_HOST}"

repos: deploy ceph using OpenStack mirrors Deploy Ceph packages using OpenStack AFS mirrors to go faster and be more reliable in OpenStack Infrastructure. Change-Id: I3b96b7dfe20ba01a1d833b47fcfb184a458c6975

2016年07月19日 16:44:35 -04:00

export FACTER_uca_mirror_host="http://${UCA_MIRROR_HOST}"

export FACTER_ceph_mirror_host="http://${CEPH_MIRROR_HOST}"

Add bits to use AFS mirrors Like we do in stable branches, deploy AFS mirrors. For now, use it only for UCA. Change-Id: I6574f5b1f99e6ae8021cff68949173c6cbba6960 Co-Authored-By: Paul Belanger <pabelanger@redhat.com>

2016年07月08日 09:13:40 -04:00

Rename PUPPET_VERSION to PUPPET_MAJ_VERSION PUPPET_VERSION is already used by puppetlabs/beaker and we don't want to overlap with this variable. So let's rename it to PUPPET_MAJ_VERSION to avoid strange behaviors when running Beaker jobs. Change-Id: I74be2eec2be53f59af196f37ee348ff6856af8bc

2016年06月07日 17:58:23 -04:00

if [ $PUPPET_MAJ_VERSION == 4 ]; then

Round 1 of Puppet 4 support This commit puts in place the ability to run puppet-openstack-integation against Pupept 4 by making release files and paths dynamic based off an environment variable, PUPPET_VERSION. Configurability is required because of the way Puppet 4 is installed, as an all-in-one package known as "PC1" or "puppet-agent" which includes Ruby, Facter 3, and other dependencies. Change-Id: Id3af52f4938378a5a620765321cecd547e079660

2016年03月15日 18:36:38 -07:00

export PATH=${PATH}:/opt/puppetlabs/bin

export PUPPET_RELEASE_FILE=puppetlabs-release-pc1

export PUPPET_BASE_PATH=/etc/puppetlabs/code

export PUPPET_PKG=puppet-agent

else

export PUPPET_RELEASE_FILE=puppetlabs-release

export PUPPET_BASE_PATH=/etc/puppet

export PUPPET_PKG=puppet

fi

source ${SCRIPT_DIR}/functions

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'Start (run_tests.sh)'

run_tests: allow to run another scenario * create $SCENARIO environment variable. * test if fixtures/$SCENARIO.pp file exist or fail early. * in comment, drop OpenStack project names hard-coding. Change-Id: I80f07ba6ee2123bc24eb33eac6f600e2ea7c63da

2015年10月01日 12:46:02 -04:00

if [ ! -f fixtures/${SCENARIO}.pp ]; then

echo "fixtures/${SCENARIO}.pp file does not exist. Please define a valid scenario."

exit 1

fi

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 [ $(id -u) != 0 ]; then

# preserve environment so we can have ZUUL_* params

refacto: create install_puppet function Change-Id: Iefed86a09eaf4e571d38c801f79e9fc989bc57d6

2016年06月08日 11:31:00 -04:00

export SUDO='sudo -E'

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

fi

Align the stars to bring our CI back 1) Add 2GB swap by default Add some swap when running CI jobs, so we can reduce the number of failures in CI related to missing memory. By default 2GB, can be disabled or increased/decreased with parameters. 2) Promote RDO repository to have Oslo DB from master python-oslo-db 4.13.x releases are known to break Gnocchi. https://review.openstack.org/367221 will fix it, but it is not yet in any release, so RDO unpinned oslo.db until that happens. 3) Disable Ironic testing on Ubuntu. Packages are broken in recent Newton upgrade. They are working on it. 4) Enable br_netfilter kernel module on Ubuntu. See https://bugs.launchpad.net/cloud-archive/+bug/1621651 Even if it's not critical, it's a nice-to-have because it removed the ERROR that we had in neutron logs. We'll see how the bug report evolve and maybe remove this workaround. 5) Export lsmod in logs, easier for us to debug later. 6) Disable linuxbridge on scenario003 for Ubuntu Also see https://bugs.launchpad.net/cloud-archive/+bug/1621651 7) Pin Puppetlabs release package. Context: https://tickets.puppetlabs.com/browse/CPR-378 Change-Id: I732ef375a681f03af751ebb6ebd5b12df55a0ecc

2016年09月08日 13:43:30 -04:00

if [ "${ADD_SWAP}" = true ]; then

print_header "Create $SWAP_SIZE_GB GB swapfile"

$SUDO dd if=/dev/zero of=/swapfile count=${SWAP_SIZE_GB}k bs=1M

$SUDO chmod 0600 /swapfile

$SUDO mkswap /swapfile

$SUDO swapon /swapfile

fi

Provision from pre-cached/pre-downloaded CirrOS image In run_tests.sh we symlink a cached image to /tmp/openstack/tempest or it is downloaded to that location using wget which is more reliable. Let's use that instead. Change-Id: I3777d9d035ceb31827b8df4264c2f7d213f50aea

2016年09月23日 09:20:44 -04:00

print_header 'Clone Tempest, plugins & pre-cache CirrOS'

Use zuul-cloner for tempest This will give us the ability to use the Depends-On header for it. Change-Id: I2eb90955cc639173214e1e85b05cf7df9fe37f21 Depends-On: I6972baa00131fafe0e608b05e18da0e9486b916e Depends-On: Ia7be12a441bfc0f68c089d6b98f0d4ba2fff96ed Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年08月26日 10:35:35 -04:00

# TODO(pabelanger): Move this into tools/install_tempest.sh and add logic so we

# can clone tempest outside of the gate. Also, tempest should be sandboxed into

# the local directory but works needs to be added into puppet to properly find

# the path.

if [ -e /usr/zuul-env/bin/zuul-cloner ] ; then

 /usr/zuul-env/bin/zuul-cloner --workspace /tmp --cache-dir /opt/git \

git://git.openstack.org openstack/tempest

centos7: stop installing horizon tempest plugin from source RDO now provides the package: https://review.openstack.org/#/c/349462 so we can use it like other services. Change-Id: I51d183467c45f5899c823118048854ba48fb7a93

2016年08月09日 10:18:04 -04:00

if uses_debs; then

 /usr/zuul-env/bin/zuul-cloner --workspace /tmp --cache-dir /opt/git \

git://git.openstack.org openstack/tempest-horizon

fi

Adjust how we pin (or not) Tempest depending on where we're running We don't want to pin Tempest if we're running inside the Tempest gate. This allows their patchsets to be properly tested inside the p-o-i jobs that are running there. If we're not running inside the Tempest gate, pin to whatever version is in TEMPEST_VERSION. Change-Id: If2221480fb13a69e64adc26fa6bc211bf563bfa8

2016年12月20日 08:48:23 -05:00

# Pin Tempest to TEMPEST_VERSION unless we're running inside the

# openstack/tempest gate.

if [[ "${ZUUL_PROJECT}" != "openstack/tempest" ]]; then

pushd /tmp/openstack/tempest

git reset --hard $TEMPEST_VERSION

popd

fi

Do a regular clone of tempest if we're running outside the gate Disable git_clone from scenario003, all-in-one.sh leverages run_tests which will now properly clone tempest if whether or not we're in the gate. Change-Id: I687464f26913bc9ee978e00e5c78efe91b062ec2

2015年11月25日 12:23:48 -05:00

else

Remove existed checkout before use avoid fatal error: `destination path 'XXX' already exists`, and prevent package download failure. Change-Id: I5ca84f43304397cb2017131ead6f321787ae09e1 Signed-off-by: guessi <guessi@gmail.com>

2016年03月02日 11:25:06 +08:00

# remove existed checkout before clone

$SUDO rm -rf /tmp/openstack/tempest

install tempest-horizon from source Tempest test for Horizon moved from Tempest to a dedicated plugin, called tempest-horizon. The plugin is currently not packaged in RDO or UCA but will be soon. Until this time, deploy the plugin from source. Change-Id: I509c044a874b77ae0f26d6c7938869fb0c492d87

2016年07月12日 09:52:59 -04:00

$SUDO rm -rf /tmp/openstack/tempest-horizon

Remove existed checkout before use avoid fatal error: `destination path 'XXX' already exists`, and prevent package download failure. Change-Id: I5ca84f43304397cb2017131ead6f321787ae09e1 Signed-off-by: guessi <guessi@gmail.com>

2016年03月02日 11:25:06 +08:00

Do a regular clone of tempest if we're running outside the gate Disable git_clone from scenario003, all-in-one.sh leverages run_tests which will now properly clone tempest if whether or not we're in the gate. Change-Id: I687464f26913bc9ee978e00e5c78efe91b062ec2

2015年11月25日 12:23:48 -05:00

# We're outside the gate, just do a regular git clone

git clone git://git.openstack.org/openstack/tempest /tmp/openstack/tempest

centos7: stop installing horizon tempest plugin from source RDO now provides the package: https://review.openstack.org/#/c/349462 so we can use it like other services. Change-Id: I51d183467c45f5899c823118048854ba48fb7a93

2016年08月09日 10:18:04 -04:00

if uses_debs; then

git clone git://git.openstack.org/openstack/tempest-horizon /tmp/openstack/tempest-horizon

fi

Adjust how we pin (or not) Tempest depending on where we're running We don't want to pin Tempest if we're running inside the Tempest gate. This allows their patchsets to be properly tested inside the p-o-i jobs that are running there. If we're not running inside the Tempest gate, pin to whatever version is in TEMPEST_VERSION. Change-Id: If2221480fb13a69e64adc26fa6bc211bf563bfa8

2016年12月20日 08:48:23 -05:00

pushd /tmp/openstack/tempest

Don't pin Tempest if jobs are run in Tempest gate Do not pin Tempest if the jobs are run in Tempest gate, so they can actually see the errors we have without the pin. Change-Id: I439dc6b8200a59f31c0227a124b4a2a6e8d443ba

2016年12月19日 15:11:34 -05:00

git reset --hard $TEMPEST_VERSION

Adjust how we pin (or not) Tempest depending on where we're running We don't want to pin Tempest if we're running inside the Tempest gate. This allows their patchsets to be properly tested inside the p-o-i jobs that are running there. If we're not running inside the Tempest gate, pin to whatever version is in TEMPEST_VERSION. Change-Id: If2221480fb13a69e64adc26fa6bc211bf563bfa8

2016年12月20日 08:48:23 -05:00

popd

Don't pin Tempest if jobs are run in Tempest gate Do not pin Tempest if the jobs are run in Tempest gate, so they can actually see the errors we have without the pin. Change-Id: I439dc6b8200a59f31c0227a124b4a2a6e8d443ba

2016年12月19日 15:11:34 -05:00

fi

Make version of tempest configurable This patch makes tempest version configurable so we can override it in CI for DLRN promotion jobs for stable branches. There have been some backwards incompatible changes in tempest and ceilometer ( https://review.openstack.org/#/c/395506/ ) not tagged yet in stable/newton. In order to get p-o-i pass with this commits we need to use an updated version of tempest. Change-Id: Ifb37a5a3a809c8a94d055d9cdc2b880e1ec9a115

2016年11月12日 16:07:55 +01:00

Provision from pre-cached/pre-downloaded CirrOS image In run_tests.sh we symlink a cached image to /tmp/openstack/tempest or it is downloaded to that location using wget which is more reliable. Let's use that instead. Change-Id: I3777d9d035ceb31827b8df4264c2f7d213f50aea

2016年09月23日 09:20:44 -04:00

# NOTE(pabelanger): We cache cirros images on our jenkins slaves, check if it

# exists.

if [ -f ~/cache/files/cirros-0.3.4-x86_64-disk.img ]; then

# Create a symlink for tempest.

ln -s ~/cache/files/cirros-0.3.4-x86_64-disk.img /tmp/openstack/tempest

else

wget http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img -P /tmp/openstack/tempest

fi

refacto: create install_puppet function Change-Id: Iefed86a09eaf4e571d38c801f79e9fc989bc57d6

2016年06月08日 11:31:00 -04:00

install_puppet

refacto: move run_puppet & catch_selinux_alerts into functions Change-Id: I78324c8787b129e91f1ac32694085bde5b6043fe

2016年06月08日 11:44:10 -04:00

PUPPET_FULL_PATH=$(which puppet)

Add hiera support This change adds hiera support into the scenarios so we can override items via the common.yaml heira file if need be. This change adds support for two environment variables with run_tests.sh. HIERA_CONFIG - full path to the hiera yaml configuration file MANAGE_HIERA - used to enable/disable writing out a hiera.yaml config file Change-Id: Iad0050e09e0cc610e0eadc00e328151e88eee10e

2016年07月13日 13:50:17 -06:00

if [ "${MANAGE_HIERA}" = true ]; then

configure_hiera

fi

refacto: move run_puppet & catch_selinux_alerts into functions Change-Id: I78324c8787b129e91f1ac32694085bde5b6043fe

2016年06月08日 11:44:10 -04:00

integration tests: use dstat to monitor system Dstat is a tool used to monitor system in real-time. It's used by Devstack in OpenStack gate to monitor system during jobs. This tool would be useful for Puppet OpenStack Integration jobs so we would be able to monitor the system during Puppet & Tempest runs, and help us to debug eventual failures. Change-Id: I5b6d6c662f1c23478ba0e0fb4f3d861a060abce7 Depends-On: I79c5b9521265e97595d3323149ba6e7d1e8e972b

2015年08月29日 12:22:57 -04:00

if uses_debs; then

Install ebtables for missing br_netfilter On fresh new ubuntu, modprobe command fails with error complaining br_netfilter. After installing ebtables, it got through it. Change-Id: I53ae0d6e057b1845a53960bb4f7f96ebddab4336 Closes-Bug: #1644329

2016年11月23日 10:36:22 -08:00

$SUDO apt-get install -y dstat ebtables

integration tests: use dstat to monitor system Dstat is a tool used to monitor system in real-time. It's used by Devstack in OpenStack gate to monitor system during jobs. This tool would be useful for Puppet OpenStack Integration jobs so we would be able to monitor the system during Puppet & Tempest runs, and help us to debug eventual failures. Change-Id: I5b6d6c662f1c23478ba0e0fb4f3d861a060abce7 Depends-On: I79c5b9521265e97595d3323149ba6e7d1e8e972b

2015年08月29日 12:22:57 -04:00

elif is_fedora; then

refacto: create install_puppet function Change-Id: Iefed86a09eaf4e571d38c801f79e9fc989bc57d6

2016年06月08日 11:31:00 -04:00

$SUDO yum install -y dstat setools setroubleshoot audit

run_tests: install selinux tools SElinux tools will be useful for us to provide SElinux alerts reports during our CI jobs. Change-Id: Icce81078d91bbed12b9dbba3c53416476d594a09

2016年04月12日 09:21:55 -04:00

$SUDO service auditd start

catch SElinux alerts in permissive mode Run the tests in permissive mode but run sealert at the end to see if we have some SElinux alerts that we need to fix. We want to run catch_selinux_alerts function before exiting the script (with failure or success) so we can detect alerts: * right after first Puppet run * after second Puppet run * after Tempest run If an AVC is detected, fails so we can report the bugs in openstack-selinux and bring useful feedback. Change-Id: Iaef45c88232505600cbb80f82b195aafcc615474

2016年04月11日 20:16:20 -04:00

# SElinux in permissive mode so later we can catch alerts

setenforce will not return 1 on run_tests.sh checking selinuxenabled exit code before will ensure that the script does not exit prematurely, since the bash -e flag is set Change-Id: Id4f0831612f69f448e627453352bd88ce089da2f

2016年06月09日 16:18:03 +02:00

$SUDO selinuxenabled && $SUDO setenforce 0

integration tests: use dstat to monitor system Dstat is a tool used to monitor system in real-time. It's used by Devstack in OpenStack gate to monitor system during jobs. This tool would be useful for Puppet OpenStack Integration jobs so we would be able to monitor the system during Puppet & Tempest runs, and help us to debug eventual failures. Change-Id: I5b6d6c662f1c23478ba0e0fb4f3d861a060abce7 Depends-On: I79c5b9521265e97595d3323149ba6e7d1e8e972b

2015年08月29日 12:22:57 -04:00

fi

# use dstat to monitor system activity during integration testing

if type "dstat" 2>/dev/null; then

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'Start dstat'

$SUDO dstat -tcmndrylpg --top-cpu-adv --top-io-adv --nocolor | $SUDO tee --append /var/log/dstat.log > /dev/null &

integration tests: use dstat to monitor system Dstat is a tool used to monitor system in real-time. It's used by Devstack in OpenStack gate to monitor system during jobs. This tool would be useful for Puppet OpenStack Integration jobs so we would be able to monitor the system during Puppet & Tempest runs, and help us to debug eventual failures. Change-Id: I5b6d6c662f1c23478ba0e0fb4f3d861a060abce7 Depends-On: I79c5b9521265e97595d3323149ba6e7d1e8e972b

2015年08月29日 12:22:57 -04:00

fi

run_tests: run dstat before r10k'ing modules r10k install is randomling taking lot of time ot be installed [1]. This patch executes dstat before installing r10k & puppet modules, so we can see in dstat logs what is consumming CPU & memory during r10k setup. (1] http://goo.gl/XJ9xky) Change-Id: Ie98bede043339b47e9e928e5c964a6ba70090860

2016年02月23日 23:08:08 -05:00

if [ "${MANAGE_PUPPET_MODULES}" = true ]; then

$SUDO ./install_modules.sh

fi

Create puppet folder layout * create fixtures directory that will contain manifests to run. * Add an empty scenario001.pp file to ensure our gate is properly working. This implementation is basic and is not definitive. It aims to scale-up later once we have multiple scenarios. Change-Id: I0149c7887c8e664ca895be8ce4df5f620c5c6d0c Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年07月13日 15:04:45 -04:00

# Run puppet and assert something changes.

set +e

Provide a toggle to disable repository management by puppet By default, repositories will be managed by puppet through manifests/repos.pp. If someone wants to set up different repositories outside of puppet entirely, he can "export MANAGE_REPOS=false" and run_tests will not run repos.pp. Change-Id: I3a09a2be1d2a064e784ed24f189fec41476330d9

2015年12月15日 15:27:32 -05:00

if [ "${MANAGE_REPOS}" = true ]; then

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'Install repos'

$SUDO $PUPPET_FULL_PATH apply $PUPPET_ARGS -e "include ::openstack_integration::repos"

Allow run_tests.sh to be rerun This updates the return code checking to allow for rerunning of the script when the puppet fails. Previously it would error out if puppet returned 0 when there were no changes which is not correct. This change updates the return code check for puppet to include 0 and 2 for the repo configuration and initial puppet run. Change-Id: I5252b7561ea589f3f49f7f6b43269328b326aa7e

2016年07月13日 10:22:40 -06:00

RESULT=$?

if [ $RESULT -ne 0 ] && [ $RESULT -ne 2 ]; then

run_tests: fail if repos are not installed when asked Stop the script if Puppet fails to deploy repositories. It can happens in case of repo downstimes or timeouts. Change-Id: I01326be2bc4ab8380ce2a371a6def38011a0523f

2016年06月09日 21:28:16 -04:00

print_header 'Puppet failed to install repositories.'

exit 1

fi

Add update step after enabling OpenStack repos In specific cases, there may be conflicts between packages provided by Centos and RDO repos. In that case RDO repos should be used. To avoid any of these issues, this patch updates packages right after enabling the repos. Change-Id: Ide3265c5dc84971f19da2b5af049693cff5442b4

2016年11月25日 18:27:47 +01:00

if is_fedora; then

print_header 'Updating packages'

$SUDO yum update -y

if [ $? -ne 0 ]; then

print_header 'Error updating packages'

exit 1

fi

Provide a toggle to disable repository management by puppet By default, repositories will be managed by puppet through manifests/repos.pp. If someone wants to set up different repositories outside of puppet entirely, he can "export MANAGE_REPOS=false" and run_tests will not run repos.pp. Change-Id: I3a09a2be1d2a064e784ed24f189fec41476330d9

2015年12月15日 15:27:32 -05:00

fi

run_tests: fail if repos are not installed when asked Stop the script if Puppet fails to deploy repositories. It can happens in case of repo downstimes or timeouts. Change-Id: I01326be2bc4ab8380ce2a371a6def38011a0523f

2016年06月09日 21:28:16 -04:00

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header "Running Puppet Scenario: ${SCENARIO} (1st time)"

run_tests: allow to run another scenario * create $SCENARIO environment variable. * test if fixtures/$SCENARIO.pp file exist or fail early. * in comment, drop OpenStack project names hard-coding. Change-Id: I80f07ba6ee2123bc24eb33eac6f600e2ea7c63da

2015年10月01日 12:46:02 -04:00

run_puppet $SCENARIO

Create puppet folder layout * create fixtures directory that will contain manifests to run. * Add an empty scenario001.pp file to ensure our gate is properly working. This implementation is basic and is not definitive. It aims to scale-up later once we have multiple scenarios. Change-Id: I0149c7887c8e664ca895be8ce4df5f620c5c6d0c Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年07月13日 15:04:45 -04:00

RESULT=$?

set -e

Allow run_tests.sh to be rerun This updates the return code checking to allow for rerunning of the script when the puppet fails. Previously it would error out if puppet returned 0 when there were no changes which is not correct. This change updates the return code check for puppet to include 0 and 2 for the repo configuration and initial puppet run. Change-Id: I5252b7561ea589f3f49f7f6b43269328b326aa7e

2016年07月13日 10:22:40 -06:00

if [ $RESULT -ne 0 ] && [ $RESULT -ne 2 ]; then

run_tests: add more debug when Puppet fails Add more debug when Puppet fails during first and second run. It will help people debugging CI to figure why job failed. Change-Id: I9ef32afaa594a65be6ed49f40bd8fba735fe2c70

2016年04月21日 09:52:23 -04:00

print_header 'First Puppet run contains errors in catalog.'

Split out puppet logs To improve troubleshooting and readability, let's not have the puppet logs print to the console. This change updates the puppet apply to output the logs to puppet.log which will still be captured and provided in the CI results. When the puppet apply fails, we will grep for warnings and errors from the puppet log and only print those out which should simplify troubleshooting failures. Change-Id: I1084223f805f1960aebb9c5868fdef84ff3667e4

2016年10月31日 15:15:34 -06:00

catch_puppet_failures

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'SELinux Alerts (1st time)'

catch SElinux alerts in permissive mode Run the tests in permissive mode but run sealert at the end to see if we have some SElinux alerts that we need to fix. We want to run catch_selinux_alerts function before exiting the script (with failure or success) so we can detect alerts: * right after first Puppet run * after second Puppet run * after Tempest run If an AVC is detected, fails so we can report the bugs in openstack-selinux and bring useful feedback. Change-Id: Iaef45c88232505600cbb80f82b195aafcc615474

2016年04月11日 20:16:20 -04:00

catch_selinux_alerts

Create puppet folder layout * create fixtures directory that will contain manifests to run. * Add an empty scenario001.pp file to ensure our gate is properly working. This implementation is basic and is not definitive. It aims to scale-up later once we have multiple scenarios. Change-Id: I0149c7887c8e664ca895be8ce4df5f620c5c6d0c Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年07月13日 15:04:45 -04:00

exit 1

fi

Split out puppet logs To improve troubleshooting and readability, let's not have the puppet logs print to the console. This change updates the puppet apply to output the logs to puppet.log which will still be captured and provided in the CI results. When the puppet apply fails, we will grep for warnings and errors from the puppet log and only print those out which should simplify troubleshooting failures. Change-Id: I1084223f805f1960aebb9c5868fdef84ff3667e4

2016年10月31日 15:15:34 -06:00

timestamp_puppet_log

Create puppet folder layout * create fixtures directory that will contain manifests to run. * Add an empty scenario001.pp file to ensure our gate is properly working. This implementation is basic and is not definitive. It aims to scale-up later once we have multiple scenarios. Change-Id: I0149c7887c8e664ca895be8ce4df5f620c5c6d0c Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年07月13日 15:04:45 -04:00

# Run puppet a second time and assert nothing changes.

set +e

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header "Running Puppet Scenario: ${SCENARIO} (2nd time)"

run_tests: allow to run another scenario * create $SCENARIO environment variable. * test if fixtures/$SCENARIO.pp file exist or fail early. * in comment, drop OpenStack project names hard-coding. Change-Id: I80f07ba6ee2123bc24eb33eac6f600e2ea7c63da

2015年10月01日 12:46:02 -04:00

run_puppet $SCENARIO

Create puppet folder layout * create fixtures directory that will contain manifests to run. * Add an empty scenario001.pp file to ensure our gate is properly working. This implementation is basic and is not definitive. It aims to scale-up later once we have multiple scenarios. Change-Id: I0149c7887c8e664ca895be8ce4df5f620c5c6d0c Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年07月13日 15:04:45 -04:00

RESULT=$?

set -e

if [ $RESULT -ne 0 ]; then

run_tests: add more debug when Puppet fails Add more debug when Puppet fails during first and second run. It will help people debugging CI to figure why job failed. Change-Id: I9ef32afaa594a65be6ed49f40bd8fba735fe2c70

2016年04月21日 09:52:23 -04:00

print_header 'Second Puppet run is not idempotent.'

Split out puppet logs To improve troubleshooting and readability, let's not have the puppet logs print to the console. This change updates the puppet apply to output the logs to puppet.log which will still be captured and provided in the CI results. When the puppet apply fails, we will grep for warnings and errors from the puppet log and only print those out which should simplify troubleshooting failures. Change-Id: I1084223f805f1960aebb9c5868fdef84ff3667e4

2016年10月31日 15:15:34 -06:00

catch_puppet_failures

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'SELinux Alerts (2nd time)'

catch SElinux alerts in permissive mode Run the tests in permissive mode but run sealert at the end to see if we have some SElinux alerts that we need to fix. We want to run catch_selinux_alerts function before exiting the script (with failure or success) so we can detect alerts: * right after first Puppet run * after second Puppet run * after Tempest run If an AVC is detected, fails so we can report the bugs in openstack-selinux and bring useful feedback. Change-Id: Iaef45c88232505600cbb80f82b195aafcc615474

2016年04月11日 20:16:20 -04:00

catch_selinux_alerts

Create puppet folder layout * create fixtures directory that will contain manifests to run. * Add an empty scenario001.pp file to ensure our gate is properly working. This implementation is basic and is not definitive. It aims to scale-up later once we have multiple scenarios. Change-Id: I0149c7887c8e664ca895be8ce4df5f620c5c6d0c Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2015年07月13日 15:04:45 -04:00

exit 1

fi

Split out puppet logs To improve troubleshooting and readability, let's not have the puppet logs print to the console. This change updates the puppet apply to output the logs to puppet.log which will still be captured and provided in the CI results. When the puppet apply fails, we will grep for warnings and errors from the puppet log and only print those out which should simplify troubleshooting failures. Change-Id: I1084223f805f1960aebb9c5868fdef84ff3667e4

2016年10月31日 15:15:34 -06:00

timestamp_puppet_log

scenario001: configure and run tempest * configure tempest with a separated manifest * put Puppet return code testing in a function * execute both manifests (tempest would be the last one) * run tempest at the end of run-tests.sh This is now a PoC for Keystone. We might need to adjust the way to run Tempest to be more flexible and support different scenarios. Co-Authored-By: Paul Belanger <pabelanger@redhat.com> Depends-On: I7c3d20a61aa88a25f1215cccb4cb36168eab05c5 Change-Id: I4b8f7fa7a694743758ea2073b532184c587899d1

2015年07月29日 10:57:52 -04:00

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'Prepare Tempest'

Run Tempest plugins We want to run Tempest tests for a maximum of projects we're testing. Tests are moving from Tempest tree to projects tree. It takes care of installing tempest-lib which is required system wide to run Tempest plugin tests. To run tests from projects tree, we need to run tox with -eall-plugin option. This patch aims to change the way we run tox. It also set manage_tests_packages to True so puppet-tempest will take care of packaging dependencies required to run Tempest plugins tests in RDO. Depends-On: Iac9a57c2ba006bb2a660d2b54ee05bbe68125abf Depends-On: I8f26968b5b817ffbb9f4dc4a0cb19ca0a1ef7d3d Change-Id: I0942a7c9456d18528a2d84e143ae056973a7674f

2016年02月23日 15:39:35 -05:00

# Tempest plugin tests require tempest-lib to be installed

$SUDO pip install tempest-lib

copy_logs: add Stackviz data Stackviz will be useful to monitor performance and debug our Tempest jobs. See https://github.com/openstack/stackviz Change-Id: Ia909a8da9975b465f3d94de0cdaea56529bb325e

2016年07月05日 17:54:20 -04:00

# We need latest testrepository to run stackviz correctly

$SUDO pip install -U testrepository

centos7: stop installing horizon tempest plugin from source RDO now provides the package: https://review.openstack.org/#/c/349462 so we can use it like other services. Change-Id: I51d183467c45f5899c823118048854ba48fb7a93

2016年08月09日 10:18:04 -04:00

# install from source now on ubuntu until packaged

if uses_debs; then

cd /tmp/openstack/tempest-horizon; $SUDO python setup.py install

fi

install tempest-horizon from source Tempest test for Horizon moved from Tempest to a dedicated plugin, called tempest-horizon. The plugin is currently not packaged in RDO or UCA but will be soon. Until this time, deploy the plugin from source. Change-Id: I509c044a874b77ae0f26d6c7938869fb0c492d87

2016年07月12日 09:52:59 -04:00

run_tests: generate testrepository.subunit all the time Make sure testrepository.subunit file is generated whether tempest failure or success. It will help to provide actual results on http://status.openstack.org/openstack-health (without that patch, we only have success jobs) Change-Id: Iaa7f9f3434d75bdf1dbf605b1b520a97a0131df8

2016年02月23日 23:23:04 -05:00

set +e

scenario001: deploy & test Aodh Aodh is the new service that replaces Ceilometer Alarm. This patch aims to: * deploy Aodh in scenario001 (beside Ceilometer). * drop ceilometer alarm code (replaced by puppet-aodh). * add TelemetryAlarming testing (to validate Telemetry Alarm with Aodh). Change-Id: I1acde0fad6c36429562d8576663c4cb9d393a79d

2015年10月26日 07:30:29 +09:00

# Select what to test:

scenario002: switch Keystone/Glance/Ironic/Nova to SSL * Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments. * Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again later in a next iteration. * Deploy Ironic API under WSGI instead of eventlet. * Switch Glance API, Ironic API and Keystone to SSL. * Configure Tempest with SSL endpoints when needed. * Reduce the Ironic tests because of [1]. [1] https://bugs.launchpad.net/ironic/+bug/1554237 Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not implemented in this patch. Note #2: we don't enable SSL for Neutron because of https://bugs.launchpad.net/neutron/+bug/1514424 Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014

2016年03月01日 18:50:40 -05:00

# Smoke suite

Manually run test runner for tempest The tempest tox.ini is going to be changed to use the tempest run runner, however the CLI is slightly different. To avoid being broken by the change this commit switches to just using tox as a venv wrapper and manually calling the test runner inside that venv. This should isolate us from any changes in the tox.ini and also make how we execute tests explicit. Change-Id: I0529c2922242d8ed9c92ef718328e09f3ea9e05b

2016年07月30日 12:43:08 -04:00

echo "smoke" > /tmp/openstack/tempest/test-whitelist.txt

scenario002: switch Keystone/Glance/Ironic/Nova to SSL * Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments. * Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again later in a next iteration. * Deploy Ironic API under WSGI instead of eventlet. * Switch Glance API, Ironic API and Keystone to SSL. * Configure Tempest with SSL endpoints when needed. * Reduce the Ironic tests because of [1]. [1] https://bugs.launchpad.net/ironic/+bug/1554237 Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not implemented in this patch. Note #2: we don't enable SSL for Neutron because of https://bugs.launchpad.net/neutron/+bug/1514424 Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014

2016年03月01日 18:50:40 -05:00

# Horizon

Manually run test runner for tempest The tempest tox.ini is going to be changed to use the tempest run runner, however the CLI is slightly different. To avoid being broken by the change this commit switches to just using tox as a venv wrapper and manually calling the test runner inside that venv. This should isolate us from any changes in the tox.ini and also make how we execute tests explicit. Change-Id: I0529c2922242d8ed9c92ef718328e09f3ea9e05b

2016年07月30日 12:43:08 -04:00

echo "dashboard" >> /tmp/openstack/tempest/test-whitelist.txt

scenario002: switch Keystone/Glance/Ironic/Nova to SSL * Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments. * Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again later in a next iteration. * Deploy Ironic API under WSGI instead of eventlet. * Switch Glance API, Ironic API and Keystone to SSL. * Configure Tempest with SSL endpoints when needed. * Reduce the Ironic tests because of [1]. [1] https://bugs.launchpad.net/ironic/+bug/1554237 Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not implemented in this patch. Note #2: we don't enable SSL for Neutron because of https://bugs.launchpad.net/neutron/+bug/1514424 Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014

2016年03月01日 18:50:40 -05:00

# Aodh

Manually run test runner for tempest The tempest tox.ini is going to be changed to use the tempest run runner, however the CLI is slightly different. To avoid being broken by the change this commit switches to just using tox as a venv wrapper and manually calling the test runner inside that venv. This should isolate us from any changes in the tox.ini and also make how we execute tests explicit. Change-Id: I0529c2922242d8ed9c92ef718328e09f3ea9e05b

2016年07月30日 12:43:08 -04:00

echo "TelemetryAlarming" >> /tmp/openstack/tempest/test-whitelist.txt

scenario002: switch Keystone/Glance/Ironic/Nova to SSL * Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments. * Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again later in a next iteration. * Deploy Ironic API under WSGI instead of eventlet. * Switch Glance API, Ironic API and Keystone to SSL. * Configure Tempest with SSL endpoints when needed. * Reduce the Ironic tests because of [1]. [1] https://bugs.launchpad.net/ironic/+bug/1554237 Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not implemented in this patch. Note #2: we don't enable SSL for Neutron because of https://bugs.launchpad.net/neutron/+bug/1514424 Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014

2016年03月01日 18:50:40 -05:00

scenario001: run Gnocchi tempest tests * drop workaround to deploy Gabbi from pip, and use RDO package. * Add gnocchi in the Puppet Tempest interface. * Add gnocchi tests in the list of tests we want to run. Change-Id: I51094b28c42f7c64d4357f49d0932e027cbd6310

2016年05月19日 22:24:22 +02:00

# Gnocchi

Manually run test runner for tempest The tempest tox.ini is going to be changed to use the tempest run runner, however the CLI is slightly different. To avoid being broken by the change this commit switches to just using tox as a venv wrapper and manually calling the test runner inside that venv. This should isolate us from any changes in the tox.ini and also make how we execute tests explicit. Change-Id: I0529c2922242d8ed9c92ef718328e09f3ea9e05b

2016年07月30日 12:43:08 -04:00

echo "gnocchi.tempest" >> /tmp/openstack/tempest/test-whitelist.txt

scenario001: run Gnocchi tempest tests * drop workaround to deploy Gabbi from pip, and use RDO package. * Add gnocchi in the Puppet Tempest interface. * Add gnocchi tests in the list of tests we want to run. Change-Id: I51094b28c42f7c64d4357f49d0932e027cbd6310

2016年05月19日 22:24:22 +02:00

scenario002: switch Keystone/Glance/Ironic/Nova to SSL * Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments. * Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again later in a next iteration. * Deploy Ironic API under WSGI instead of eventlet. * Switch Glance API, Ironic API and Keystone to SSL. * Configure Tempest with SSL endpoints when needed. * Reduce the Ironic tests because of [1]. [1] https://bugs.launchpad.net/ironic/+bug/1554237 Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not implemented in this patch. Note #2: we don't enable SSL for Neutron because of https://bugs.launchpad.net/neutron/+bug/1514424 Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014

2016年03月01日 18:50:40 -05:00

# Ironic

# Note: running all Ironic tests under SSL is not working

# https://bugs.launchpad.net/ironic/+bug/1554237

Manually run test runner for tempest The tempest tox.ini is going to be changed to use the tempest run runner, however the CLI is slightly different. To avoid being broken by the change this commit switches to just using tox as a venv wrapper and manually calling the test runner inside that venv. This should isolate us from any changes in the tox.ini and also make how we execute tests explicit. Change-Id: I0529c2922242d8ed9c92ef718328e09f3ea9e05b

2016年07月30日 12:43:08 -04:00

echo "api.baremetal.admin.test_drivers" >> /tmp/openstack/tempest/test-whitelist.txt

scenario002: switch Keystone/Glance/Ironic/Nova to SSL * Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments. * Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again later in a next iteration. * Deploy Ironic API under WSGI instead of eventlet. * Switch Glance API, Ironic API and Keystone to SSL. * Configure Tempest with SSL endpoints when needed. * Reduce the Ironic tests because of [1]. [1] https://bugs.launchpad.net/ironic/+bug/1554237 Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not implemented in this patch. Note #2: we don't enable SSL for Neutron because of https://bugs.launchpad.net/neutron/+bug/1514424 Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014

2016年03月01日 18:50:40 -05:00

scenario002: deploy & test Zaqar puppet-zaqar is freshly new and we want to test it. * configure mongodb replicaset (required for zaqar): 'openstack'. * deploy zaqar on scenario002 with mongodb backend. * configure tempest to test zaqar. * run TestManageQueue tempest tests in tempest. Note about TestManageQueue: Zaqar does not maintain Tempest tests, and run their own functional testing tools. api.messaging.test_queues tests are known to work, so they will be the only tests run in our CI to validate Zaqar is working. Note: * SSL does not work out of the box, we need to add support for WSGI deployment with Apache, but Zaqa does not provide WSGI app, it's in their roadmap. * IPv6 binding on default wsgi does not work, so using IPv4 now. Change-Id: I1aa563f37aa7a231b2218f79b72c73c668d968f3

2016年02月17日 15:30:37 -05:00

# Zaqar

Manually run test runner for tempest The tempest tox.ini is going to be changed to use the tempest run runner, however the CLI is slightly different. To avoid being broken by the change this commit switches to just using tox as a venv wrapper and manually calling the test runner inside that venv. This should isolate us from any changes in the tox.ini and also make how we execute tests explicit. Change-Id: I0529c2922242d8ed9c92ef718328e09f3ea9e05b

2016年07月30日 12:43:08 -04:00

echo "v2.test_queues.TestManageQueue" >> /tmp/openstack/tempest/test-whitelist.txt

scenario003: deploy and test mistral Do not merge, testing with v3 auth * Deploy Mistral on scenario003 * Run Tempest tests for Mistral * Bump repo to recent RDO repo that contains a fix in Mistral to make Tempest tests working. Change-Id: Ia43427cc207ee5b7b95e9610f06a568992fb58cd

2016年04月09日 11:50:00 -04:00

scenario002: Enable ec2api tempest tests Depends-On: I2a60bde92e8522362fefebc34c99cbb0346c6347 Change-Id: Ibebf638af2bf4daf867b7d06856bdf7758de54d3

2016年08月17日 14:40:32 +02:00

# ec2api

Reduce the amount of ec2api tests from 161 to 14 The previous ec2api tempest regex was matching 161 tests so we were trying to run all of that, greatly affecting testing duration. We're lowering that to 14 which is much more reasonable. Change-Id: Ib662094e588414bf7a87d2b9659d8e9ead0a0077

2016年11月25日 11:52:47 -05:00

# VPN tests require VPNaaS, which doesn't work yet in puppet-tempest.

# As soon as enabling neutron_vpnaas_available works there, the VPN tests can

# be included.

echo "ec2api.tests.functional.api.*test_create_delete(?!.*_vpn_connection)" >> /tmp/openstack/tempest/test-whitelist.txt

scenario002: Enable ec2api tempest tests Depends-On: I2a60bde92e8522362fefebc34c99cbb0346c6347 Change-Id: Ibebf638af2bf4daf867b7d06856bdf7758de54d3

2016年08月17日 14:40:32 +02:00

Add cinder backup to scenario002 Configure cinder backup to use swift and test Change-Id: I9b645b2e7b76e97403b95459578979ec9f53c0b4 Depends-On: I588c9864cd20c75de7caecf733603a3587c34d12

2016年10月02日 23:34:09 -04:00

# Cinder Backup

echo "VolumesBackupsAdminV2Test" >> /tmp/openstack/tempest/test-whitelist.txt

scenario002: enable Barbican and Volume Encryption testing Start testing Barbican for real. Depends-On: I7a51c1a3baae5fd96b75cc73acd4c8c3e2c4ade5 Change-Id: I034a38bb7adde9f39db99b1a82715ce11e8ca63b

2016年07月08日 15:59:50 -04:00

# Cinder encrypted volumes

Enable TestEncryptedCinderVolumes tests (for real) https://review.openstack.org/#/c/363142/ was merged but it was basically noop since the pattern to enable the test was wrong and reviewers missed it. This patch enables TestEncryptedCinderVolumes tests for real. Change-Id: Iee97dfc3fc9b6a313f274dc1bee11ff8c1611782

2016年09月30日 11:17:43 -04:00

echo "TestEncryptedCinderVolumes" >> /tmp/openstack/tempest/test-whitelist.txt

scenario002: enable Barbican and Volume Encryption testing Start testing Barbican for real. Depends-On: I7a51c1a3baae5fd96b75cc73acd4c8c3e2c4ade5 Change-Id: I034a38bb7adde9f39db99b1a82715ce11e8ca63b

2016年07月08日 15:59:50 -04:00

Re-enable Mistral testing This reverts commit 4d6b918cefaad43ef1c3d0ee018bca067b2cc5e2. It activates Mistral testing again, module one test that fails all the time: https://bugs.launchpad.net/mistral/+bug/1654555 Change-Id: I763fd9b13ba94d1e76682a7a1c4264d7507c922c

2016年07月08日 16:39:31 -04:00

# Mistral

# We have to ignore a smoke test because of:

# https://bugs.launchpad.net/mistral/+bug/1654555

echo "test_create_and_delete_workflow" >> /tmp/openstack/tempest/test-whitelist.txt

Disable lbaas listener tests On ubuntu these tests are flakey with ocata-m1. Let's disable them for now. Change-Id: Id0141edd8bf40449ef26b49ae94121f6779e0c3f

2016年12月01日 10:26:05 -07:00

if uses_debs; then

Update ubuntu excludes for ocata-m2 Since ocata-m2 has been published in proposed for UCA, let's see what tests still fail. Depends-On: I272c03f19d7182c4a731a1ef0fcbc2b9c6ca0b97 Change-Id: I4c8e102dea02e931abdc708f6ad2c508765a4c5b

2017年01月19日 10:04:16 -07:00

# TODO(aschultz): check this after ocata-m3 is published for UCA

Remove tempest pin for UCA This is a partial revert of the pin we implemented as part of I2330faf700230fe40119169347ad72f8332d0821 to be able to promote the RDO packages. Change-Id: Id19998448591e9e3fb997602ec95a51cb2070889

2016年12月01日 10:21:15 -07:00

# 1) this will disable the lbaas listeners tests for ubuntu only due to flakey

Disable lbaas listener tests On ubuntu these tests are flakey with ocata-m1. Let's disable them for now. Change-Id: Id0141edd8bf40449ef26b49ae94121f6779e0c3f

2016年12月01日 10:26:05 -07:00

# failures

Update ubuntu excludes for ocata-m2 Since ocata-m2 has been published in proposed for UCA, let's see what tests still fail. Depends-On: I272c03f19d7182c4a731a1ef0fcbc2b9c6ca0b97 Change-Id: I4c8e102dea02e931abdc708f6ad2c508765a4c5b

2017年01月19日 10:04:16 -07:00

EXCLUDES="--regex=^(?!neutron_lbaas.tests.tempest.v2.api.test_listeners_.*admin.ListenersTestJSON.*$).*"

Disable lbaas listener tests On ubuntu these tests are flakey with ocata-m1. Let's disable them for now. Change-Id: Id0141edd8bf40449ef26b49ae94121f6779e0c3f

2016年12月01日 10:26:05 -07:00

else

Re-enable Mistral testing This reverts commit 4d6b918cefaad43ef1c3d0ee018bca067b2cc5e2. It activates Mistral testing again, module one test that fails all the time: https://bugs.launchpad.net/mistral/+bug/1654555 Change-Id: I763fd9b13ba94d1e76682a7a1c4264d7507c922c

2016年07月08日 16:39:31 -04:00

 EXCLUDES="--regex=^(?!mistral_tempest_tests.tests.api.v2.test_executions.ExecutionTestsV2.test_get_list_executions.*$).*"

Disable lbaas listener tests On ubuntu these tests are flakey with ocata-m1. Let's disable them for now. Change-Id: Id0141edd8bf40449ef26b49ae94121f6779e0c3f

2016年12月01日 10:26:05 -07:00

fi

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'Running Tempest'

Run Tempest plugins We want to run Tempest tests for a maximum of projects we're testing. Tests are moving from Tempest tree to projects tree. It takes care of installing tempest-lib which is required system wide to run Tempest plugin tests. To run tests from projects tree, we need to run tox with -eall-plugin option. This patch aims to change the way we run tox. It also set manage_tests_packages to True so puppet-tempest will take care of packaging dependencies required to run Tempest plugins tests in RDO. Depends-On: Iac9a57c2ba006bb2a660d2b54ee05bbe68125abf Depends-On: I8f26968b5b817ffbb9f4dc4a0cb19ca0a1ef7d3d Change-Id: I0942a7c9456d18528a2d84e143ae056973a7674f

2016年02月23日 15:39:35 -05:00

cd /tmp/openstack/tempest

pin tempest See context: https://review.openstack.org/#/c/325520/ Change-Id: If00246874a66b73d79affc9cef56e71088b534f9

2016年06月03日 23:54:29 -04:00

Stop using tox This commit abandons the tox usage in run_tests.sh script. At this point tox is only being used to create a venv and not run any tests. The primary advantage tox gives you is maintaining separate test environments by handling the venv management, job commands, etc. Since we are only using it venvs, tox is a bit heavyweight when we can just call virtualenv and pip directly. This just make it more explict so people can see exactly what is happening when we run tempest. It also continues the work to decouple running the tests in CI from the tempest repo itself. Change-Id: I57ded07a2fd2cde4d532f65e68bacbf62547cf1f

2016年09月13日 11:38:31 -04:00

virtualenv --system-site-packages run_tempest

run_tempest/bin/pip install -U .

Disable lbaas listener tests On ubuntu these tests are flakey with ocata-m1. Let's disable them for now. Change-Id: Id0141edd8bf40449ef26b49ae94121f6779e0c3f

2016年12月01日 10:26:05 -07:00

run_tempest/bin/tempest run --whitelist_file=/tmp/openstack/tempest/test-whitelist.txt --concurrency=2 $EXCLUDES

run_tests: generate testrepository.subunit all the time Make sure testrepository.subunit file is generated whether tempest failure or success. It will help to provide actual results on http://status.openstack.org/openstack-health (without that patch, we only have success jobs) Change-Id: Iaa7f9f3434d75bdf1dbf605b1b520a97a0131df8

2016年02月23日 23:23:04 -05:00

RESULT=$?

set -e

Run Tempest plugins We want to run Tempest tests for a maximum of projects we're testing. Tests are moving from Tempest tree to projects tree. It takes care of installing tempest-lib which is required system wide to run Tempest plugin tests. To run tests from projects tree, we need to run tox with -eall-plugin option. This patch aims to change the way we run tox. It also set manage_tests_packages to True so puppet-tempest will take care of packaging dependencies required to run Tempest plugins tests in RDO. Depends-On: Iac9a57c2ba006bb2a660d2b54ee05bbe68125abf Depends-On: I8f26968b5b817ffbb9f4dc4a0cb19ca0a1ef7d3d Change-Id: I0942a7c9456d18528a2d84e143ae056973a7674f

2016年02月23日 15:39:35 -05:00

testr last --subunit > /tmp/openstack/tempest/testrepository.subunit

Stop using tox This commit abandons the tox usage in run_tests.sh script. At this point tox is only being used to create a venv and not run any tests. The primary advantage tox gives you is maintaining separate test environments by handling the venv management, job commands, etc. Since we are only using it venvs, tox is a bit heavyweight when we can just call virtualenv and pip directly. This just make it more explict so people can see exactly what is happening when we run tempest. It also continues the work to decouple running the tests in CI from the tempest repo itself. Change-Id: I57ded07a2fd2cde4d532f65e68bacbf62547cf1f

2016年09月13日 11:38:31 -04:00

run_tempest/bin/tempest list-plugins

catch SElinux alerts in permissive mode Run the tests in permissive mode but run sealert at the end to see if we have some SElinux alerts that we need to fix. We want to run catch_selinux_alerts function before exiting the script (with failure or success) so we can detect alerts: * right after first Puppet run * after second Puppet run * after Tempest run If an AVC is detected, fails so we can report the bugs in openstack-selinux and bring useful feedback. Change-Id: Iaef45c88232505600cbb80f82b195aafcc615474

2016年04月11日 20:16:20 -04:00

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'SELinux Alerts (Tempest)'

catch SElinux alerts in permissive mode Run the tests in permissive mode but run sealert at the end to see if we have some SElinux alerts that we need to fix. We want to run catch_selinux_alerts function before exiting the script (with failure or success) so we can detect alerts: * right after first Puppet run * after second Puppet run * after Tempest run If an AVC is detected, fails so we can report the bugs in openstack-selinux and bring useful feedback. Change-Id: Iaef45c88232505600cbb80f82b195aafcc615474

2016年04月11日 20:16:20 -04:00

catch_selinux_alerts

Add a function for generating action headers In order to help be able to determine what part of the script a failure occurs in, this change adds a print header function and updates the shell scripts to print some header information for various actions. Change-Id: I8e622c4d1c9c03aa3dbcb27712a346ce3284003f

2016年04月14日 14:04:57 -06:00

print_header 'Done (run_tests.sh)'

run_tests: generate testrepository.subunit all the time Make sure testrepository.subunit file is generated whether tempest failure or success. It will help to provide actual results on http://status.openstack.org/openstack-health (without that patch, we only have success jobs) Change-Id: Iaa7f9f3434d75bdf1dbf605b1b520a97a0131df8

2016年02月23日 23:23:04 -05:00

exit $RESULT

openstack/puppet-openstack-integration - puppet-openstack-integration - OpenDev: Free Software Needs Free Tools

274 lines

9.4 KiB

Bash

Raw Normal View History

openstack/puppet-openstack-integration - puppet-openstack-integration - OpenDev: Free Software Needs Free Tools

274 lines 9.4 KiB Bash Raw Normal View History Unescape Escape

274 lines

9.4 KiB

Bash

Raw Normal View History