8f624221ea56d8232ac47ebde0bfc8ad82e38cde
Go to file
Takashi Kajinami 8f624221ea Apache: Disable default mods
We should load the required mods automatically instead of relying on
the list of modules loaded by puppetlabs-apache by default.
Change-Id: I8f60238ddb82c188dc2042ab38fedb3b0edbaef3
2023年08月07日 16:58:14 +09:00
2023年02月10日 19:34:08 +00:00
2023年08月07日 16:58:14 +09:00
2023年08月07日 16:58:14 +09:00
2023年05月25日 12:03:38 +09:00
2023年07月17日 15:41:31 +00:00
2019年04月19日 19:36:24 +00:00
2021年04月07日 18:58:58 +02:00
2016年08月12日 21:10:15 +02:00
2023年07月29日 04:17:24 +00:00
2023年06月20日 22:10:05 +09:00
2023年04月28日 16:20:33 +09:00
2022年07月23日 23:29:50 +09:00
2015年07月13日 14:58:14 -04:00
2023年02月27日 07:49:22 +00:00
2017年02月01日 22:36:10 -05:00
2023年07月31日 02:30:02 +09:00
2023年05月30日 01:14:52 +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, 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
ec2api X
heat X X
swift X
sahara X
trove X
horizon X X X X
ironic X
zaqar X
murano 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 amqp1 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

Description
Collection of scripts and manifests for module testing
Readme 36 MiB
Languages
Puppet 78.2%
Shell 19.5%
Ruby 2.3%