Collection of scripts and manifests for module testing
Go to file
Takashi Kajinami 9af824a5ca ironic: Configure cinder options
Scenario 002 has cinder enabled. Although we do not run actual tests
using cinder storage driver, enabling these options may allow us to
ensure at least the configuration can be applied without any error.

Change-Id: I2180b11fe640f20161beeedef3b2b44a1825ea08
2024-05-05 02:47:55 +00:00
contrib Fix ipv6 certificate to make it compliant with IDNA 2018-03-20 22:38:03 +01:00
files Merge "Fix wrong facility for swift logs" 2023-02-10 19:34:08 +00:00
fixtures ironic: Disable notification to nova in acceptance tests 2024-05-05 02:47:46 +00:00
hiera Apache: Disable default mods 2023-08-07 16:58:14 +09:00
manifests ironic: Configure cinder options 2024-05-05 02:47:55 +00:00
playbooks Drop rubygem-rexml 2024-04-19 01:40:06 +09:00
templates Debian/Ubuntu: Fix rndc.key file path in rndc.conf 2023-12-10 00:20:02 +09:00
zuul.d Merge "Bump puppet minor versions" 2024-03-08 14:45:31 +00:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:47:07 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:36:24 +00:00
all-in-one.sh Unpin bundler 2023-12-19 07:56:57 +00:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:10:15 +02:00
configure_facts.sh Restore FACTER_ environments 2023-10-15 01:29:31 +09:00
copy_logs.sh Capture rsync config file 2024-02-01 18:16:07 +09:00
external_modules.txt Bump puppetlabs-stdlib to 9.0.0 2023-09-21 03:15:02 +09:00
functions Drop logic for old puppet-ceph branches 2024-03-08 18:23:24 +09:00
Gemfile Use openstack_spec_helper from zuul checkout 2022-07-23 23:29:50 +09:00
install_modules_unit.sh Add puppet core providers for puppet6 2018-11-20 11:37:55 +01:00
install_modules.sh Refactor puppet installation in integration job 2023-11-09 23:37:51 +09:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
openstack_modules.txt Remove murano 2024-03-06 01:19:57 +00:00
Puppetfile Updated from Puppet OpenStack modules constraints 2024-04-12 02:43:55 +00:00
Puppetfile_unit Updated from Puppet OpenStack modules constraints 2024-03-07 02:45:44 +00:00
Rakefile Align the stars 2017-02-01 22:36:10 -05:00
README.md Test redis sentinel coordination backend 2024-04-12 00:25:56 +09:00
run_tests.sh tempest: Avoid unnecessary package installation 2024-04-20 23:27:26 +09:00
unit_modules.txt Prepare list of modules used in unit tests 2023-02-26 01:40:54 +09:00

Team and repository tags

Team and repository tags

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. All-in-one - How to deploy a cloud with Puppet
  5. 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 four 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 four 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 swift+rgw 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
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 (redis)

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).

Contributors