Collection of scripts and manifests for module testing
Go to file
Takashi Kajinami 0630bddecc Remove dependency on puppet-monasca
... because puppet-monasca is being retired.

Conflicts:
        Puppetfile
	zuul.d/base.yaml

Backport note:
- Resolved conflict caused by branch overrides.
- This backport includes the follow-up commit[1] to remove leftover.
- (Rocky and older) Resolved conflict caused by centralized .zuul.yaml
  used in older branches.

[1] f45e67023c

Change-Id: Ieba1856f60479b04db6f93a26a22e720c0179ba5
(cherry picked from commit 25009d7f3a)
(cherry picked from commit 7c2355740b)
(cherry picked from commit 370d3724ff)
(cherry picked from commit 9ea47a0b83)
(cherry picked from commit cd1cf9a2e8)
(cherry picked from commit 52d4f205c2)
(cherry picked from commit d3b37b5697)
2021-08-21 02:06:31 +09:00
contrib Fix ipv6 certificate to make it compliant with IDNA 2018-03-22 06:14:41 +00:00
files Fix ipv6 certificate to make it compliant with IDNA 2018-03-22 06:14:41 +00:00
fixtures keystone: enable fernet across all CI 2018-02-07 11:04:39 -07:00
hiera Remove leftovers from mongodb 2018-01-25 12:27:36 +01:00
manifests Change ceph caps to profile rbd 2018-07-03 21:49:41 +00:00
playbooks Disable selinux in CentOS7 beaker job 2021-05-25 23:05:27 +09:00
templates Re-enable Designate on CentOS7 2017-02-02 22:15:04 +00:00
.gitignore Update SSL certificates with SubjectAltNames 2016-09-29 00:20:08 -04:00
.gitreview OpenDev Migration Patch 2019-04-19 19:36:26 +00:00
.zuul.yaml Remove dependency on puppet-monasca 2021-08-21 02:06:31 +09:00
Gemfile Pin tempest versions with python2 support 2020-05-27 18:15:54 +02:00
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
Puppetfile Remove dependency on puppet-monasca 2021-08-21 02:06:31 +09:00
README.md Pin tempest versions with python2 support 2020-05-27 18:15:54 +02:00
Rakefile Align the stars 2017-02-01 22:36:10 -05:00
all-in-one.sh Pin tempest versions with python2 support 2020-05-27 18:15:54 +02:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:10:15 +02:00
configure_facts.sh Do not use mirror host for Ceph Luminous 2021-02-02 14:52:45 +00:00
copy_logs.sh Remove explicit compress of log files 2020-02-14 03:12:00 +00:00
external_modules.txt Remove leftovers from mongodb 2018-01-25 12:27:36 +01:00
functions Remove zuul-cloner usage 2019-09-18 12:37:00 +00:00
install_modules.sh Pin gettext < 3.3.0 2020-01-09 09:50:47 +00:00
install_modules_unit.sh Revert "Remove r10k env vars with proper args" 2018-02-06 03:34:38 +00:00
openstack_modules.txt Remove retired congress 2020-06-22 17:41:55 +02:00
run_tests.sh Remove reference to tempest-horizon repo 2021-02-17 00:08:05 +09:00

README.md

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 and scenario004.

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 scenario-aio
ssl yes yes yes yes no
ipv6 centos7 centos7 centos7 centos7 no
keystone X X X X X
glance rbd swift file swift+rgw file
nova rbd X X rbd X
neutron ovs ovs linuxbridge ovs ovs
lbaas v2 v2 v2 v2
cinder rbd iscsi iscsi
ceilometer X
aodh X
panko X
designate bind
backup swift
gnocchi rbd
ec2api X
heat X X
swift X
sahara X
trove X
horizon X X
ironic X
zaqar X
murano X
mistral X
barbican X
ceph X X
ceph rgw X
vitrage X
watcher X
bgpvpn-api X
redis X
l2gw X
om rpc amqp1 rabbit rabbit rabbit rabbit
om notify 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