openstack/puppet-openstack-integration
Code Issues Proposed changes
Collection of scripts and manifests for module testing
1,693 Commits 11 Branches 10 Tags 35 MiB
Puppet 78.2%
Shell 19.3%
Ruby 2.4%
cf77be5c48
Go to file
Alfredo Moralejo cf77be5c48 Make gem install options explicit 
The default behavior of `gem install` with regard to the location of the
installed gems and binaries is different in CentOS7, CentOS8 and Ubuntu
so let's make options explicit to get the desired behavior in all cases
and configurations, what means getting gems installed under GEM_HOME to
avoid depending on system wise PATH declarations and installed gems.

Change-Id: I992a930491f65ba9871c3f94806afce54bef9c7b
2020-01-10 15:02:00 +05:30
contrib Fix ipv6 certificate to make it compliant with IDNA 2018-03-20 22:38:03 +01:00
files Add GPG-KEY-ceph 2018-04-11 22:24:00 +02:00
fixtures Add CentOS8 support and jobs 2019-12-20 10:18:18 +00:00
hiera Remove leftovers from mongodb 2018-01-25 12:27:36 +01:00
manifests Merge "Use keystone::bootstrap" 2020-01-09 11:40:38 +00:00
playbooks beaker jobs: fix path for copy_logs.sh 2019-07-30 19:48:02 +00:00
templates Re-enable Designate on CentOS7 2017-02-02 22:15:04 +00:00
zuul.d Add support for RDO CentOS8 repos and run CentOS8 jobs 2020-01-02 16:22:47 +05:30
.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 Make gem install options explicit 2020-01-10 15:02:00 +05:30
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:10:15 +02:00
configure_facts.sh Add support for RDO CentOS8 repos and run CentOS8 jobs 2020-01-02 16:22:47 +05:30
copy_logs.sh Use hiera v5 format 2019-01-15 14:49:57 +01:00
external_modules.txt Invert the logic of Puppetfile 2019-12-20 17:08:09 -05:00
functions Invert the logic of Puppetfile 2019-12-20 17:08:09 -05:00
Gemfile Move to opendev 2019-04-22 09:11:52 +08:00
install_modules_unit.sh Add puppet core providers for puppet6 2018-11-20 11:37:55 +01:00
install_modules.sh Make gem install options explicit 2020-01-10 15:02:00 +05:30
LICENSE Add LICENSE file 2015-07-13 14:58:14 -04:00
openstack_modules.txt placement: Use puppet-placement to deploy an extracted service 2019-02-27 13:31:26 +00:00
Puppetfile Updated from Puppet OpenStack modules constraints 2019-12-21 06:09:35 +00:00
Puppetfile_centos8 Invert the logic of Puppetfile 2019-12-20 17:08:09 -05:00
Puppetfile_unit Add mount_core module needed by puppet-swift 2018-11-30 16:46:35 +01:00
Rakefile Align the stars 2017-02-01 22:36:10 -05:00
README.md Remove Neutron LBaaS 2019-05-13 14:47:24 +02:00
run_tests.sh Add support for RDO CentOS8 repos and run CentOS8 jobs 2020-01-02 16:22:47 +05:30

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
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
bgp-dr 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