openstack
/
puppet-openstack-integration
Code Issues Proposed changes
Collection of scripts and manifests for module testing
384 Commits 10 Branches 10 Tags 34 MiB
Puppet 78%
Shell 19.4%
Ruby 2.5%
Go to file
Emilien Macchi ad5546a400 Rename PUPPET_VERSION to PUPPET_MAJ_VERSION 
PUPPET_VERSION is already used by puppetlabs/beaker and we don't want to
overlap with this variable. So let's rename it to PUPPET_MAJ_VERSION to
avoid strange behaviors when running Beaker jobs.

Change-Id: I74be2eec2be53f59af196f37ee348ff6856af8bc
 		2016-06-08 08:54:02 -04:00
files Generate Self-Signed Cert with SubjectAltNames 2016-04-13 08:24:20 -04:00
fixtures scenario003/xenial: disable trove 2016-05-31 11:51:33 -04:00
manifests Promote RDO repository to latest consistent URL 2016-06-07 06:04:33 +00:00
.gitreview Added .gitreview 2015-06-23 19:27:13 +00:00
Gemfile drop mock dependency 2016-01-22 09:58:05 -05:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
Puppetfile Updated from Puppet OpenStack modules constraints 2016-06-02 06:02:40 +00:00
README.md Change wiki to docs 2016-06-06 10:22:14 +00:00
Rakefile Remove class_parameter_defaults puppet-lint check 2015-11-12 12:47:22 +01:00
all-in-one.sh Support of Ubuntu 16.04 LTS Xenial deployments 2016-05-26 20:40:18 -04:00
external_modules.txt Puppetfile: pin puppetlabs-mysql to latest tag 2016-06-01 21:30:13 +00:00
functions functions: add defaults for ZUUL_BRANCH & ZUUL_REF 2016-04-20 09:42:31 -04:00
install_modules.sh Rename PUPPET_VERSION to PUPPET_MAJ_VERSION 2016-06-08 08:54:02 -04:00
install_modules_unit.sh Rename PUPPET_VERSION to PUPPET_MAJ_VERSION 2016-06-08 08:54:02 -04:00
openstack_modules.txt Puppetfile: add puppet-ovn module 2016-04-13 21:15:21 -04:00
other-requirements.txt Do not pre-install dependencies from OpenStack Infra 2016-04-14 16:29:52 -04:00
run_tests.sh Rename PUPPET_VERSION to PUPPET_MAJ_VERSION 2016-06-08 08:54:02 -04:00

README.md

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 three jobs per supported Operating System (Ubuntu and CentOS): scenario001, scenario002 and scenario003.

OpenStack services are balanced between three 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 scenario-aio
ssl yes yes yes no
ipv6 centos7 centos7 centos7 no
keystone X X X X
tokens uuid uuid fernet uuid
glance rbd swift file file
nova rbd X X X
neutron ovs ovs linuxbridge ovs
cinder rbd iscsi iscsi
ceilometer X
aodh X
gnocchi rbd
heat X
swift X
sahara X
trove X
horizon X X
ironic X
zaqar X
ceph X
mongodb 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:

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