982f18c282
Run the tests in permissive mode but run sealert at the end to see if we have some SElinux alerts that we need to fix. We want to run catch_selinux_alerts function before exiting the script (with failure or success) so we can detect alerts: * right after first Puppet run * after second Puppet run * after Tempest run If an AVC is detected, fails so we can report the bugs in openstack-selinux and bring useful feedback. Change-Id: Iaef45c88232505600cbb80f82b195aafcc615474 |
||
|---|---|---|
| files | ||
| fixtures | ||
| manifests | ||
| .gitreview | ||
| all-in-one.sh | ||
| external_modules.txt | ||
| functions | ||
| Gemfile | ||
| generate_puppetfile.sh | ||
| install_modules_unit.sh | ||
| install_modules.sh | ||
| LICENSE | ||
| openstack_modules.txt | ||
| 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 three jobs per supported Operating System (Ubuntu and CentOS): scenario001, scenario002 and scenario003.
OpenStack services are balanced between three scenarios because OpenStack Infastructure Jenkins slaves can not afford the load of running everything on the same node. One manifest (scenario-aio) is used for people who want to run a simple All-In-One scenario.
| - | scenario001 | scenario002 | scenario003 | scenario-aio |
|---|---|---|---|---|
| ssl | yes | yes | yes | no |
| ipv6 | centos7 | centos7 | centos7 | no |
| keystone | X | X | X | X |
| glance | rbd | swift | file | file |
| nova | rbd | X | X | X |
| neutron | ovs | ovs | linuxbridge | ovs |
| cinder | rbd | iscsi | iscsi | |
| ceilometer | X | |||
| aodh | X | |||
| gnocchi | rbd | |||
| heat | X | |||
| swift | X | |||
| sahara | X | |||
| trove | X | |||
| horizon | X | X | ||
| ironic | X | |||
| zaqar | 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).