openstack/puppet-openstack-integration
Code Issues Proposed changes
Collection of scripts and manifests for module testing
75 Commits 11 Branches 10 Tags 35 MiB
Puppet 78.2%
Shell 19.3%
Ruby 2.4%
5151d89164
Go to file
Sebastien Badia 5151d89164 puppetfile: Added corosync module 
puppetlabs/corosync dependency was added in openstack/openstack_extras in
change-id I5d98d8f9494bb7df4466022b3d49ac6392deb1a5, let's reflect this change.

Change-Id: I8b158fedb7f9f149a3bb9c5325b9d208d1a560df
2015-10-10 02:56:45 +00:00
fixtures scenario001: deploy & test Trove 2015-10-05 17:14:48 -04:00
.gitreview Added .gitreview 2015-06-23 19:27:13 +00:00
functions Create functions for common bits 2015-10-06 15:57:56 +00:00
Gemfile Revert "Initial run_tests.sh script" 2015-08-07 09:21:41 -04:00
install_modules_unit.sh Create install_modules_unit.sh 2015-10-06 15:58:09 +00:00
install_modules.sh Create functions for common bits 2015-10-06 15:57:56 +00:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
Puppetfile puppetfile: Added corosync module 2015-10-10 02:56:45 +00:00
Rakefile Initial import to gate on 2015-08-04 19:35:58 -04:00
README.md scenario001: deploy & test Trove 2015-10-05 17:14:48 -04:00
run_tests.sh Merge "run_tests: allow to run another scenario" 2015-10-02 07:14:15 +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. 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.

- scenario001 scenario002
keystone X X
glance X X
nova X X
neutron X X
cinder X
ceilometer X
heat X
swift X
sahara X
trove 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:

Contributors