e645272ef304fe3fa1ef43879a1b9524236c34fd
Go to file
Emilien Macchi e645272ef3 Generate Self-Signed Cert with SubjectAltNames
A new version of python urllib send us ugly warnings because our SSL
certificates don't have SubjectAltNames.
I re-generated some SSL certs with it, for both ipv4 & ipv6 deployments.
Change-Id: Ibed9f23869de9d2871c3d25e9bd24df809aa4c16
2016年04月13日 08:24:20 -04:00
2016年04月10日 18:24:43 +00:00
2015年06月23日 19:27:13 +00:00
2016年02月24日 14:50:52 -05:00
2016年02月26日 14:03:16 +01:00
2016年01月22日 09:58:05 -05:00
2016年03月28日 20:23:13 -07:00
2015年07月13日 14:58:14 -04:00
2016年04月07日 10:06:03 -04:00
2016年04月10日 18:24:43 +00:00

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 three jobs per supported Operating System (Ubuntu and CentOS): scenario001, scenario002 and scenario003.

OpenStack services are balanced between three 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 scenario-aio
ssl yes yes yes no
ipv6 centos7 centos7 centos7 no
keystone X X X X
glance rbd swift file file
nova rbd X X X
neutron ovs ovs linuxbridge ovs
cinder rbd iscsi iscsi
ceilometer X
aodh X
gnocchi rbd
heat X
swift X
sahara X
trove X
horizon X X
ironic X
zaqar X
ceph X
mongodb X

When the Jenkins slave is created, the run_tests.sh script will 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:

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 git://git.openstack.org/openstack/puppet-openstack-integration
cd puppet-openstack-integration
./all-in-one.sh

or

curl -sL http://git.openstack.org/cgit/openstack/puppet-openstack-integration/plain/all-in-one.sh | bash

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%