openstack/puppet-openstack-integration
Code Issues Proposed changes
Collection of scripts and manifests for module testing
175 Commits 7 Branches 12 Tags 35 MiB
Puppet 78.2%
Shell 19.3%
Ruby 2.4%
6c272cdf16
Go to file
Emilien Macchi 6c272cdf16 rename scenario003 to scenario-aio 
scenario003 is going to be a scenario gated in OpenStack Infra.
It was created to be a AIO scenario, for our testers, so let's rename it
to scenario-aio.

In a further iteration, scenario003 will be a scenario used by our CI.

Change-Id: I53852757d013abfae10e5f4afd41ddbb18da3b03
2016-02-24 14:50:52 -05:00
fixtures rename scenario003 to scenario-aio 2016-02-24 14:50:52 -05:00
manifests Merge "keystone: manage admin user role before openrc" 2016-02-24 05:21:13 +00: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 Create manifests directory for common bits 2015-11-18 15:09:18 +00:00
Gemfile drop mock dependency 2016-01-22 09:58:05 -05:00
install_modules_unit.sh Fix scripts to be OSX compatible 2015-10-15 10:01:17 -05:00
install_modules.sh Fix scripts to be OSX compatible 2015-10-15 10:01:17 -05:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
Puppetfile Merge "Deploy MongoDB on scenario002" 2016-02-17 19:21:40 +00:00
Rakefile Remove class_parameter_defaults puppet-lint check 2015-11-12 12:47:22 +01:00
README.md rename scenario003 to scenario-aio 2016-02-24 14:50:52 -05:00
run_tests.sh Merge "Add ability to manually install puppet modules" 2016-02-17 03:45:05 +00: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 (scenario-aio) is used for people who want to run a simple All-In-One scenario.

- scenario001 scenario002 scenario-aio
keystone X X X
glance rbd file file
nova rbd X X
neutron 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