4d165a20f7
These options are required to use some features in cinder (live extension of attached volumes). Change-Id: I0f3b89e8ba174ffd0588269e3024d2f1367a6108 |
||
|---|---|---|
| contrib | ||
| files | ||
| fixtures | ||
| hiera | ||
| manifests | ||
| playbooks | ||
| templates | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| all-in-one.sh | ||
| bindep.txt | ||
| configure_facts.sh | ||
| copy_logs.sh | ||
| external_modules.txt | ||
| functions | ||
| Gemfile | ||
| install_modules_unit.sh | ||
| install_modules.sh | ||
| LICENSE | ||
| openstack_modules.txt | ||
| Puppetfile | ||
| Puppetfile_unit | ||
| Rakefile | ||
| README.md | ||
| run_tests.sh | ||
| unit_modules.txt | ||
Team and repository tags
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 5 jobs per supported Operating System (Ubuntu and CentOS): scenario001, scenario002, scenario003, scenario004, and scenario005.
The manifest files under the fixtures directory is used to compose the required services for each senario. The manifest files under the manifests directory is used to set up basic set of a single component (like nova, cinder and so on).
OpenStack services are balanced between 5 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 | scenario004 | scenario005 | scenario-aio |
|---|---|---|---|---|---|---|
| ssl | yes | yes | yes | yes | yes | no |
| ipv6 | centos9 | centos9 | centos9 | centos9 | centos9 | no |
| keystone | X | X | X | X | X | X |
| glance | rbd | swift | file | rbd | cinder | file |
| nova | rbd | X | X | rbd | X | X |
| placement | X | X | X | X | X | X |
| neutron | ovs | ovs | ovn | ovs | ovn | ovs |
| cinder | rbd | iscsi | iscsi | iscsi | ||
| manila | cephfs | lvm | ||||
| ceilometer | X | X | ||||
| aodh | X | X | ||||
| designate | bind | |||||
| backup | ceph | swift | ||||
| gnocchi | rbd | swift | ||||
| heat | X | X | ||||
| swift | X | |||||
| trove | X | |||||
| horizon | X | X | X | X | X | |
| ironic | X | |||||
| zaqar | X | |||||
| magnum | X | |||||
| mistral | X | |||||
| barbican | X | X | ||||
| ceph | X | X | ||||
| ceph mds | X | |||||
| ceph rgw | X | |||||
| vitrage | X | |||||
| watcher | X | |||||
| vpnaas | X | X | ||||
| taas | X | |||||
| bgpvpn-api | X | |||||
| bgp-dr | X | |||||
| memcached | X | X | X | X | X | X |
| redis | X | X | X | X | X | |
| l2gw | X | |||||
| octavia | X | X | ||||
| om rpc | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit |
| om notify | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit |
| oslo.cache | redis | sentinel | memcache | memcache | memcache | memcache |
| tooz | redis | sentinel | redis | redis | redis | |
| jobboard | redis | sentinel |
When the Jenkins slave is created, the run_tests.sh script will be 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:
Note: SSL Certificates
puppet-openstack-integration ships it's own SSL keys and certificates in order to be able to test implementations secured over SSL/TLS.
It doesn't re-generate new ones every time for the sake of simplicity: we're not testing that we can generate certificates properly, we're testing services.
The configuration as well as the commands used to generate these keys and certificates are stored in the contrib directory.
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 https://opendev.org/openstack/puppet-openstack-integration
cd puppet-openstack-integration
./all-in-one.sh
Look at Description to see which services it will install (scenario-aio).