Code Issues Proposed changes

4c40b18e2a7f5637450a7f7c7d8bfb60efc62de1

Go to file

Clone

Open with VS Code Open with VSCodium Open with Intellij IDEA

Emilien Macchi 4c40b18e2a Split scenarios001 in two scenarios

* Split scenario001 in two scenarios: scenario001 and scenario002
* Create README and initiate Puppet OpenStack Integration documentation.
Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f
Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8
Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月03日 14:37:26 -04:00

fixtures

Split scenarios001 in two scenarios

2015年10月03日 14:37:26 -04:00

.gitreview

Added .gitreview

2015年06月23日 19:27:13 +00:00

Gemfile

Initial import to gate on

2015年08月04日 19:35:58 -04:00

install_modules.sh

Cleanup some legacy code

2015年10月01日 12:32:47 -04:00

LICENSE

Add LICENSE file

2015年07月13日 14:58:14 -04:00

Puppetfile

Puppetfile: bump apt from 1.8.x to 2.1x

2015年09月23日 15:02:11 -04:00

Rakefile

Initial import to gate on

2015年08月04日 19:35:58 -04:00

README.md

Split scenarios001 in two scenarios

2015年10月03日 14:37:26 -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

Overview - What is Puppet OpenStack Integration?
Description - What does the project do?
Development - Guide for contributing
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 | |-----------------------------------------

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.