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.
Go to file
Takashi Kajinami 7e2afcda8f
Revert "Make CentOS 9 integration jobs voting"
11 months ago
contrib Fix ipv6 certificate to make it compliant with IDNA 5 years ago
files CentOS: Install gpg keys from repository 2 years ago
fixtures Merge "Enable Telemetry service in scenario002" 1 year ago
hiera Remove leftovers from mongodb 5 years ago
manifests Merge "Ubuntu: Touch /etc/neutron/fwaas_driver.ini" 12 months ago
playbooks Drop support for Fedora and CentOS/RHEL<8 1 year ago
templates Re-enable Designate on CentOS7 6 years ago
zuul.d Revert "Make CentOS 9 integration jobs voting" 11 months ago
.gitignore Dissuade .gitignore references to personal tools 4 years ago
.gitreview OpenDev Migration Patch 4 years ago
Gemfile Move to opendev 4 years ago
LICENSE Add LICENSE file 8 years ago
Puppetfile Updated from Puppet OpenStack modules constraints 12 months ago
Puppetfile_unit Bump version of yumrepo_core to 1.0.7 2 years ago Enable Telemetry service in scenario002 1 year ago
Rakefile Align the stars 6 years ago Fix installing puppet in Debian. 2 years ago
bindep.txt Move other-requirements.txt to bindep.txt 7 years ago Ceph: Use centos-8-stream instead of centos-8 1 year ago Merge "CentOS: Capture yum repository files" 12 months ago
external_modules.txt Remove sysctl module dependency 1 year ago
functions Add support for for CentOS Stream 9 1 year ago Clean r10k installation 2 years ago Add puppet core providers for puppet6 4 years ago
openstack_modules.txt Remove monasca from module list 1 year ago Tempest: Update options to include/exclude tests 1 year 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. For CentOS it is also deploying a job(scenario000) with very tiny installation.

The manifest files under the fixtures directory is used to compose the required services for each senario. The manifest files under the manifests directory is used to set up basic set of a single component (like nova, cinder and so on).

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.

- scenario000 scenario001 scenario002 scenario003 scenario004 scenario-aio
ssl yes yes yes yes yes no
ipv6 centos8 centos8 centos8 centos8 centos8 no
keystone X X X X X X
glance rbd swift file swift+rgw file
nova rbd X X rbd X
placement X X X X X
neutron ovs ovs linuxbridge ovs ovs
cinder rbd iscsi iscsi
ceilometer X X
aodh X X
designate bind
backup swift
gnocchi rbd swift
ec2api X
heat X X
swift X
sahara X
trove X
horizon X X
ironic X
zaqar X
murano X
magnum X
mistral X
barbican X X
ceph X X
ceph rgw X
vitrage X
watcher X
bgpvpn-api X
bgp-dr X
redis X X
l2gw X
om rpc amqp1 amqp1 rabbit rabbit rabbit rabbit
om notify rabbit 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).