Collection of scripts and manifests for module testing
Puppet Shell Ruby HTML
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
contrib Fix ipv6 certificate to make it compliant with IDNA Mar 20, 2018
files Add GPG-KEY-ceph Apr 11, 2018
fixtures Test bgp-dragent in scenario004 Aug 16, 2018
hiera Remove leftovers from mongodb Jan 25, 2018
manifests Set bgp_router_id to a fixed ip Aug 21, 2018
playbooks Run metadata-json-lint test in lint job Aug 14, 2018
templates Re-enable Designate on CentOS7 Feb 2, 2017
.gitignore Update SSL certificates with SubjectAltNames Sep 29, 2016
.gitreview Added .gitreview Jun 23, 2015
.zuul.yaml Set ubuntu scenario003 and 004 as non voting Aug 20, 2018
Gemfile Load puppet-openstack_spec_helper locally during tests Feb 12, 2018
LICENSE Add LICENSE file Jul 13, 2015
Puppetfile Updated from Puppet OpenStack modules constraints Aug 21, 2018 Test bgp-dragent in scenario004 Aug 16, 2018
Rakefile Align the stars Feb 2, 2017 Replace port 35357 with 5000 Jul 23, 2018
bindep.txt Move other-requirements.txt to bindep.txt Aug 12, 2016 Pick proper mirror for ceph apt::pin Aug 20, 2018 Allow running poi scenarios on Fedora Jun 13, 2018
external_modules.txt Module stankevich/python has been moved to voxpupuli Jul 31, 2018
functions Change Puppet repo for Bionic Jul 27, 2018 Revert "Remove r10k env vars with proper args" Feb 6, 2018 Remove PUPPET_MAJ_VERSION check for unit modules Feb 6, 2018
openstack_modules.txt add vitrage Feb 14, 2017 Merge "Test bgp-dragent in scenario004" Aug 17, 2018

Team and repository tags

Team and repository tags


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


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.


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
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
bgp-dr 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 script will be executed. This script will execute 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.


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.


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://
cd puppet-openstack-integration

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