Collection of scripts and manifests for module testing
Go to file
Alfredo Moralejo f2b7245520 Replace Ceph Mimic by Nautilus in CentOS
Ceph Nautilus has now a stable release 14.2.0 and it's being packaged
in CentOS Storage SIG. Mimic release was not LTS so let's replace it
by Nautilus where possible.

Since nautilus, the supported store backend is LVM which can use a block
device directly (not loopback) or a LVM logical volume for OSDs.

This patch is creating a LVM structure to create the OSD used to
validate Ceph and switching scenario004 to use nautilus instead of
mimic, so we will keep testing both Luminous and Nautilus, LTS releases.

Depends-On: https://review.opendev.org/#/c/650263/
Change-Id: I81441237a8b7cf651fa6926b2eb3c4ed0d42bb58
2019-04-24 05:02:41 +00:00
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 placement: Use puppet-placement to deploy an extracted service 2019-02-27 13:31:26 +00:00
hiera Remove leftovers from mongodb 2018-01-25 12:27:36 +01:00
manifests Replace Ceph Mimic by Nautilus in CentOS 2019-04-24 05:02:41 +00:00
playbooks Replace openstack.org git:// URLs with https:// 2019-03-24 20:35:42 +00:00
templates Re-enable Designate on CentOS7 2017-02-02 22:15:04 +00:00
zuul.d Replace Ceph Mimic by Nautilus in CentOS 2019-04-24 05:02:41 +00:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:47:07 +08:00
.gitreview Added .gitreview 2015-06-23 19:27:13 +00:00
all-in-one.sh Replace openstack.org git:// URLs with https:// 2019-03-24 20:35:42 +00:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:10:15 +02:00
configure_facts.sh Replace Ceph Mimic by Nautilus in CentOS 2019-04-24 05:02:41 +00:00
copy_logs.sh Use hiera v5 format 2019-01-15 14:49:57 +01:00
external_modules.txt Add git_resource to replace vcsrepo 2019-02-26 14:51:19 -07:00
functions Add Ceph Nautilus support 2019-04-04 14:35:41 +02:00
Gemfile Revert "Checkout stable/pike for spec_helper" 2018-11-04 22:05:30 +00:00
install_modules_unit.sh Add puppet core providers for puppet6 2018-11-20 11:37:55 +01:00
install_modules.sh Pin r10k to 2.6.4 2018-09-27 09:52:52 +02:00
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-03-27 06:10:39 +00: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 Replace openstack.org git:// URLs with https:// 2019-03-24 20:35:42 +00:00
run_tests.sh Replace openstack.org git:// URLs with https:// 2019-03-24 20:35:42 +00: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 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
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://git.openstack.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