Collection of scripts and manifests for module testing
Go to file
Paul Belanger bf878a5c6e
Fix up prepare-node-common playbook
Use the bool filter to default to false, if use_puppetlabs is missing.
Also attempt to fix up vars setting in .zuul.yaml

Change-Id: I277619847ed3a4c99845471a541820e559efab5d
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
2017-10-24 20:01:17 -04:00
contrib New SSL certificates 2016-10-29 18:13:34 -04:00
files New SSL certificates 2016-10-29 18:13:34 -04:00
fixtures Switch tempest to use RPM by default and disable trove 2017-10-11 15:32:54 +02:00
hiera Disable puppetlabs-mongodb dbpath_fix 2016-11-21 14:52:48 -07:00
manifests cinder: update key_manager when barbican isn't deployed 2017-10-24 20:09:40 +00:00
playbooks Fix up prepare-node-common playbook 2017-10-24 20:01:17 -04:00
templates Re-enable Designate on CentOS7 2017-02-02 22:15:04 +00:00
.gitignore Update SSL certificates with SubjectAltNames 2016-09-29 00:20:08 -04:00
.gitreview Added .gitreview 2015-06-23 19:27:13 +00:00
.zuul.yaml Fix up prepare-node-common playbook 2017-10-24 20:01:17 -04:00
all-in-one.sh all-in-one: run the script from p-o-i after clone 2017-02-02 11:30:23 -05:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:10:15 +02:00
configure_facts.sh Add Ceph Luminous support for CentOS 7 CI 2017-09-27 12:43:16 -04:00
copy_logs.sh Add support for dual oslo.messaging backend configuration 2017-08-27 10:44:31 -04:00
external_modules.txt Add puppet-archive to external modules 2017-09-07 10:16:18 -04:00
functions Add Zuul V3 support for Puppet Jobs 2017-09-28 22:37:09 -04:00
Gemfile Align stars to fix ci 2016-12-13 14:48:52 -07:00
install_modules_unit.sh Ensure $GEM_BIN_DIR is in $PATH 2016-06-13 14:11:46 -04:00
install_modules.sh install_modules: run gem with verbose option 2017-08-18 09:19:46 -07:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
openstack_modules.txt add vitrage 2017-02-14 16:55:08 +02:00
Puppetfile Updated from Puppet OpenStack modules constraints 2017-10-22 06:06:21 +00:00
Rakefile Align the stars 2017-02-01 22:36:10 -05:00
README.md Fix aio ssl in README.md 2017-09-22 09:36:39 +08:00
run_tests.sh Add missing sudo for swap actions 2017-10-18 08:24:10 -06:00

Team and repository tags

Team and repository tags

puppet-openstack-integration

Table of Contents

  1. Overview - What is Puppet OpenStack Integration?
  2. Description - What does the project do?
  3. Development - Guide for contributing
  4. All-in-one - How to deploy a cloud with Puppet
  5. Contributors - Those with commits

Overview

Puppet OpenStack Integration makes sure we can continuously test and validate OpenStack setups deployed with Puppet modules. The repository itself contains some scripts and Puppet manifests that help to deploy OpenStack in OpenStack Infrastructure environment.

Description

OpenStack Infrastructure is deploying four jobs per supported Operating System (Ubuntu and CentOS): scenario001, scenario002, scenario003 and scenario004.

OpenStack services are balanced between four scenarios because OpenStack Infastructure Jenkins slaves can not afford the load of running everything on the same node. One manifest (scenario-aio) is used for people who want to run a simple All-In-One scenario.

- scenario001 scenario002 scenario003 scenario004 scenario-aio
ssl yes yes yes yes no
ipv6 centos7 centos7 centos7 centos7 no
keystone X X X X X
tokens uuid uuid fernet fernet uuid
glance rbd swift file swift+rgw file
nova rbd X X rbd X
neutron ovs ovs linuxbridge ovs ovs
lbaas v2 v2 v2 v2
cinder rbd iscsi iscsi
ceilometer X
aodh X
panko X
designate bind
backup swift
gnocchi rbd
ec2api X
heat X X
swift X
sahara X
trove X
horizon X X
ironic X
zaqar X
murano X
mistral X
barbican X
ceph X X
ceph rgw X
vitrage X
watcher X
bgpvpn-api X
redis X
l2gw X
om rpc amqp1 rabbit rabbit rabbit rabbit
om notify rabbit rabbit rabbit rabbit rabbit

When the Jenkins slave is created, the run_tests.sh script will be executed. This script will execute install_modules.sh that prepare /etc/puppet/modules with all Puppet modules dependencies.

Then, it will execute Puppet a first time by applying a scenario manifest. If the first run executes without error, a second Puppet run will be executed to verify there is no change in the catalog and make sure the Puppet run is idempotent.

If Puppet runs are successful, the script will run Tempest Smoke tests, that will execute some scenarios & API tests. It covers what we want to validate, and does not take too much time.

Development

Developer documentation for the entire Puppet OpenStack project:

Note: SSL Certificates

puppet-openstack-integration ships it's own SSL keys and certificates in order to be able to test implementations secured over SSL/TLS.

It doesn't re-generate new ones every time for the sake of simplicity: we're not testing that we can generate certificates properly, we're testing services.

The configuration as well as the commands used to generate these keys and certificates are stored in the contrib directory.

All-In-One

If you're new in Puppet OpenStack and you want to deploy an All-In-One setup of an OpenStack Cloud with the Puppet modules, please follow the steps:

git clone git://git.openstack.org/openstack/puppet-openstack-integration
cd puppet-openstack-integration
./all-in-one.sh

Look at Description to see which services it will install (scenario-aio).

Contributors