Collection of scripts and manifests for module testing
Go to file
Takashi Kajinami 1f47845ddb Avoid using internal exec resources for dependencies
... so that we can refactor resources in ceph::pool.

Change-Id: I98c66422b92a5a1b64ab90f646713f60b175645e
(cherry picked from commit 9e4cd7852e)
(cherry picked from commit e9ca68508f)
(cherry picked from commit c3bb6192dc)
(cherry picked from commit 079c55c99a)
2024-10-15 16:26:56 +09: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 Test ceph volume backup driver 2024-10-15 16:26:23 +09:00
hiera Remove leftovers from mongodb 2018-01-25 12:27:36 +01:00
manifests Avoid using internal exec resources for dependencies 2024-10-15 16:26:56 +09:00
playbooks Ensure en language pack is installed 2024-09-29 06:23:08 +00:00
templates Designate: Use appropriate IP version for bind and mdns 2023-02-28 20:14:11 +09:00
zuul.d Remove murano 2024-03-08 18:08:25 +09:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:47:07 +08:00
.gitreview Update .gitreview for stable/2023.1 2023-04-05 15:34:12 +00:00
all-in-one.sh Fix installing puppet in Debian. 2021-04-07 18:58:58 +02:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:10:15 +02:00
configure_facts.sh CentOS: Switch to Antelope release 2023-04-19 13:11:22 +09:00
copy_logs.sh Stop testing amqp1 messaging driver 2024-02-05 16:27:03 +09:00
external_modules.txt Unpin puppet-ssh_keygen 2022-08-16 19:50:16 +09:00
functions Remove unused logic with outdated comments 2023-02-26 04:42:44 +00: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 Fix non-existing option of 'bundle install' 2022-12-05 18:34:09 +09:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
openstack_modules.txt Remove murano 2024-03-08 18:08:25 +09:00
Puppetfile Remove murano 2024-03-08 18:08:25 +09:00
Puppetfile_unit Updated from Puppet OpenStack modules constraints 2023-03-10 02:16:58 +00:00
Rakefile Align the stars 2017-02-01 22:36:10 -05:00
README.md Test ceph volume backup driver 2024-10-15 16:26:23 +09:00
run_tests.sh Remove puppet-ec2api 2024-03-08 12:29:13 +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 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 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
ironic X
zaqar X
magnum X
mistral X
barbican X X
ceph X X
ceph mds X
ceph rgw X
vitrage X
watcher X
bgpvpn-api X
bgp-dr X
redis X X X
l2gw X
octavia X X
om rpc rabbit rabbit rabbit rabbit rabbit rabbit
om notify rabbit rabbit rabbit rabbit rabbit rabbit

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