openstack
/
puppet-openstack-integration
Code Issues Proposed changes
Collection of scripts and manifests for module testing
91 Commits 10 Branches 10 Tags 34 MiB
Puppet 77.9%
Shell 19.5%
Ruby 2.5%
Go to file
Nate Potter ce3dd1991d Add openrc file creation to AIO script 
This patch will add the creation of an openrc file
containing the credentials a user needs to use their
OpenStack deployment to the end of the AIO script.

Change-Id: I1353d9e1a3b026f0c6d56d6cfd2f0581866bed90
 		2015-11-10 23:10:31 +00:00
fixtures Merge "Implement all-in-one.sh script" 2015-11-06 23:53:56 +00:00
.gitreview Added .gitreview 2015-06-23 19:27:13 +00:00
Gemfile gemfile: Added netaddr package 2015-10-16 19:29:20 +03:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
Puppetfile puppetfile: bump corosync to 0.8.0 2015-10-16 13:01:19 +00:00
README.md Implement all-in-one.sh script 2015-11-06 08:58:37 -05:00
Rakefile Initial import to gate on 2015-08-04 19:35:58 -04:00
all-in-one.sh Add openrc file creation to AIO script 2015-11-10 23:10:31 +00:00
functions Implement all-in-one.sh script 2015-11-06 08:58:37 -05:00
install_modules.sh Fix scripts to be OSX compatible 2015-10-15 10:01:17 -05:00
install_modules_unit.sh Fix scripts to be OSX compatible 2015-10-15 10:01:17 -05:00
run_tests.sh Implement all-in-one.sh script 2015-11-06 08:58:37 -05: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 two jobs per supported Operating System (Ubuntu and CentOS): scenario001 and scenario002.

OpenStack services are balanced between two scenarios because OpenStack Infastructure Jenkins slaves can not afford the load of running all on the same node. One manifest (scenario003) is used for people who want to run a simple All-In-One scenario.

- scenario001 scenario002 scenario003
keystone X X X
glance X X X
nova X X X
neutron X X X
cinder X X
ceilometer X
heat X
swift X
sahara X
trove X
horizon X 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 (scenario003).

Contributors