Collection of scripts and manifests for module testing
Go to file
Ade Lee b02aab5174 Add puppet-ipaclient
The puppet-nova manifest file for novajoin references the
ipaclient module to register the undercloud node with IPA
by doing an ipa-client-install.  In order for the unit tests
to pass, puppet-ipa-client needs to be in the CI environment.

Change-Id: I8e9bd4ed859cc438a309d9a00dd278c65dbb822d
2017-01-11 13:12:09 -05: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 Re-enable Mistral testing 2017-01-06 11:37:59 -05:00
hiera Disable puppetlabs-mongodb dbpath_fix 2016-11-21 14:52:48 -07:00
manifests Merge "Remove testing for Glance Registry" 2017-01-09 20:14:33 +00:00
templates Add Designate test coverage to scenario003 2016-09-28 10:09:15 -04: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
all-in-one.sh Support of Ubuntu 16.04 LTS Xenial deployments 2016-05-26 20:40:18 -04:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:10:15 +02:00
copy_logs.sh Don't fail creating the log directory if it already exists 2016-12-05 10:24:35 -05:00
external_modules.txt Add puppet-ipaclient 2017-01-11 13:12:09 -05:00
functions Fix puppet log move for non-root 2016-12-02 21:20:31 +00: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 Fix beaker under centos 2017-01-04 16:38:33 -07:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
openstack_modules.txt Add puppet-qdr and puppet-cloudkitty 2016-10-18 07:47:11 -04:00
Puppetfile Add puppet-ipaclient 2017-01-11 13:12:09 -05:00
Rakefile Remove class_parameter_defaults puppet-lint check 2015-11-12 12:47:22 +01:00
README.md Re-enable Mistral testing 2017-01-06 11:37:59 -05:00
run_tests.sh Merge "Remove testing for Glance Registry" 2017-01-09 20:14:33 +00: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
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
mongodb X
watcher X

When the Jenkins slave is created, the run_tests.sh script will 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

or

curl -sL http://git.openstack.org/cgit/openstack/puppet-openstack-integration/plain/all-in-one.sh | bash

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

Contributors