openstack/puppet-openstack-integration
Code Issues Proposed changes
Collection of scripts and manifests for module testing
247 Commits 10 Branches 10 Tags 34 MiB
Puppet 78.3%
Shell 19.2%
Ruby 2.5%
53eb3a966d
Go to file
Sofer Athlan-Guyot 53eb3a966d Fix bug and non-idiom in bash scripts. 
Those small typos and non-idiom can lead to unexpected behavior, better
fix them now.

Change-Id: I218ba0f3bba832d0929fb52c21f7e66774da494e
Closes-Bug: #1561539
2016-03-24 14:39:05 +01:00
files scenario002: switch Keystone/Glance/Ironic/Nova to SSL 2016-03-14 16:34:29 -04:00
fixtures scenario003: disable sahara on ubuntu jobs 2016-03-15 15:45:04 -04:00
manifests bump RDO Mitaka to March 22th 2016-03-22 07:58:52 -04:00
.gitreview Added .gitreview 2015-06-23 19:27:13 +00:00
all-in-one.sh rename scenario003 to scenario-aio 2016-02-24 14:50:52 -05:00
functions Fix rspec testing outside of the Openstack CI. 2016-02-26 14:03:16 +01:00
Gemfile drop mock dependency 2016-01-22 09:58:05 -05:00
install_modules_unit.sh Fix bug and non-idiom in bash scripts. 2016-03-24 14:39:05 +01:00
install_modules.sh Fix bug and non-idiom in bash scripts. 2016-03-24 14:39:05 +01:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
Puppetfile Puppetfile: add puppet-oslo & puppet-octavia 2016-03-09 17:46:04 -05:00
Rakefile Remove class_parameter_defaults puppet-lint check 2015-11-12 12:47:22 +01:00
README.md scenario002: deploy RabbitMQ with IPv6 binding 2016-03-01 14:32:47 -05:00
run_tests.sh Round 1 of Puppet 4 support 2016-03-21 12:41:16 -07: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 no yes no no
ipv6 no yes no no
keystone X X X X
glance rbd swift file file
nova rbd X X X
neutron X X X X
cinder rbd iscsi iscsi
ceilometer X
aodh X
gnocchi rbd
heat X
swift X
sahara X
trove X
horizon X X
ironic 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