openstack/puppet-openstack-integration
Code Issues Proposed changes
Collection of scripts and manifests for module testing
77 Commits 11 Branches 10 Tags 35 MiB
Puppet 78.2%
Shell 19.3%
Ruby 2.4%
9d4a169004
Go to file
Denis Egorenko 9d4a169004 Remove workaround for Sahara 
Bug #1356053 was fixed in upstream and now we don't need specify
another service type for Sahara service.

Change-Id: I2d95f17a27bab3871ca561e6480655696df7557d
2015-10-15 19:28:16 +03:00
fixtures Remove workaround for Sahara 2015-10-15 19:28:16 +03: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 scenario002: add dashboard service 2015-10-12 17:25:43 -04:00
run_tests.sh scenario002: add dashboard service 2015-10-12 17:25:43 -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. 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
horizon 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