Collection of scripts and manifests for module testing
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenStack Proposal Bot 7c1d0eff96 Updated from Puppet OpenStack modules constraints 1 week ago
contrib Fix ipv6 certificate to make it compliant with IDNA 1 year ago
files Add GPG-KEY-ceph 1 year ago
fixtures Remove nova_placement and switch scenario001 to use placement 2 months ago
hiera Remove leftovers from mongodb 1 year ago
manifests Merge "Fix sites-enabled warning" 3 weeks ago
playbooks Remove zuul-cloner usage 2 weeks ago
templates Re-enable Designate on CentOS7 2 years ago
zuul.d Reparent puppet-openstack-base to legacy-base 2 weeks ago
.gitignore Dissuade .gitignore references to personal tools 9 months ago
.gitreview OpenDev Migration Patch 2 months ago
Gemfile Move to opendev 2 months ago
LICENSE Add LICENSE file 4 years ago
Puppetfile Updated from Puppet OpenStack modules constraints 1 week ago
Puppetfile_unit Add mount_core module needed by puppet-swift 7 months ago Remove Neutron LBaaS 2 months ago
Rakefile Align the stars 2 years ago Move to opendev 2 months ago
bindep.txt Move other-requirements.txt to bindep.txt 2 years ago Replace Ceph Mimic by Nautilus in CentOS 2 months ago Use hiera v5 format 6 months ago
external_modules.txt Add git_resource to replace vcsrepo 4 months ago
functions Remove zuul-cloner usage 2 weeks ago Pin r10k to 2.6.4 9 months ago Add puppet core providers for puppet6 7 months ago
openstack_modules.txt placement: Use puppet-placement to deploy an extracted service 4 months ago Remove zuul-cloner usage 2 weeks ago

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

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