puppet-openstack-integration/README.md
Emilien Macchi 76813468bd Re-enable Mistral testing
This reverts commit 4d6b918cef.
It activates Mistral testing again, module one test that fails all the
time:
https://bugs.launchpad.net/mistral/+bug/1654555

Change-Id: I763fd9b13ba94d1e76682a7a1c4264d7507c922c
2017-01-06 11:37:59 -05:00

5.9 KiB

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