478f8208ad
This patch enables robust and complete testing of a compute scenario where RBD is used for Cinder and Nova. * Allow cinder.pp and nova.pp to configure RBD backend. * Switch scenario001 to run Cinder and Nova with RBD backend. * Update README with more documentation about Cinder & Nova backends. * Configure volume_clear option to 'none' so volumes are quickly deleted. * Enable rbd_default_features to 15 to increase ceph performances. * Increase compute build_interval in Tempest to 60s, useful for Bootfromvolume test where instance deletion can take time with RBD backend. Depends-On: I69a7d40e7d1847be06a843986ace4f0602272fe1 Depends-On: I7302b89da5a995e779ec349ab0c0f519c69a3a98 Depends-On: Ic410cb66e7620b6ca6acbea38360d8dd890000c9 Change-Id: I5c8d9cf2ff8fc361553b3eed73b697ad87170434 |
||
|---|---|---|
| fixtures | ||
| manifests | ||
| .gitreview | ||
| all-in-one.sh | ||
| functions | ||
| Gemfile | ||
| install_modules_unit.sh | ||
| install_modules.sh | ||
| LICENSE | ||
| Puppetfile | ||
| Rakefile | ||
| README.md | ||
| run_tests.sh | ||
puppet-openstack-integration
Table of Contents
- Overview - What is Puppet OpenStack Integration?
- Description - What does the project do?
- Development - Guide for contributing
- All-in-one - How to deploy a cloud with Puppet
- 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 | rbd | file | file |
| nova | rbd | X | X |
| neutron | X | X | X |
| cinder | rbd | iscsi | iscsi |
| ceilometer | X | ||
| aodh | X | ||
| gnocchi | X | ||
| 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 (scenario003).