puppet-openstack-integration

Show team and repo badges on README This patch adds the team's and repository's badges to the README file. The motivation behind this is to communicate the project status and features at first glance. For more information about this effort, please read this email thread: http://lists.openstack.org/pipermail/openstack-dev/2016-October/105562.html To see an example of how this would look like check: https://gist.github.com/755ac686eb44bb391b3e757184de4faf Change-Id: I2187ed90aee53739a81f2879dc665e33b72e9dea

2016年11月25日 17:10:23 +01:00

Team and repository tags

========================

Update and replace http with https for doc links 1) Update doc links according to OpenStack document migration 2) Use https instead of http for docs links Change-Id: I6bc6f9c831a2d0e4686c5edad37caa827afad7db

2017年09月18日 20:00:47 -07:00

[![Team and repository tags](https://governance.openstack.org/tc/badges/puppet-openstack-integration.svg)](https://governance.openstack.org/tc/reference/tags/index.html)

Show team and repo badges on README This patch adds the team's and repository's badges to the README file. The motivation behind this is to communicate the project status and features at first glance. For more information about this effort, please read this email thread: http://lists.openstack.org/pipermail/openstack-dev/2016-October/105562.html To see an example of how this would look like check: https://gist.github.com/755ac686eb44bb391b3e757184de4faf Change-Id: I2187ed90aee53739a81f2879dc665e33b72e9dea

2016年11月25日 17:10:23 +01:00

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

puppet-openstack-integration

============================

#### Table of Contents

1. [Overview - What is Puppet OpenStack Integration?](#overview)

2. [Description - What does the project do?](#description)

3. [Development - Guide for contributing](#development)

Fix link to All-in-one section Anchor tags are autogenerated for headers using lower case, at least with GitHub's Markdown engine. Change-Id: Id5b40699042823650086cb0bf8afe95b3c0268d9

2016年08月26日 10:56:27 +01:00

4. [All-in-one - How to deploy a cloud with Puppet](#all-in-one)

Implement all-in-one.sh script This script will help newcomers to run this script and deploy a simple scenario of an OpenStack Cloud with Puppet OpenStack modules. Change-Id: I559e5e0a0d21a02d04b3d999b77dee23bb38c341

2015年11月05日 12:02:15 -05:00

5. [Contributors - Those with commits](#contributors)

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

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

-----------

Fix outdated number of scenarios mentioned Currently we have 5 scenarios instead of 4. Change-Id: I045d758e09b7639cdca628ea7d230997cd45007b

2024年09月15日 00:54:23 +09:00

OpenStack Infrastructure is deploying 5 jobs per supported Operating System

Fix old description about scenario tests Now we use CentOS 9 instead of CentOS 8. Also scenario 005 has been added to test ml2 + ovn by [1]. [1] 6f090cc74d0eaa6ae835864ff70856bd1e812efc Change-Id: Ie5546e9695f41c1302cd6cfce5e3f9b3a9172514

2022年07月04日 00:07:20 +09:00

(Ubuntu and CentOS): scenario001, scenario002, scenario003, scenario004, and

scenario005.

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

Explain usage of fixtures/manifests directory Change-Id: I9621db45b19487c8639f6cbfb404e427a85fcafc

2021年06月06日 22:03:07 +09:00

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).

Fix outdated number of scenarios mentioned Currently we have 5 scenarios instead of 4. Change-Id: I045d758e09b7639cdca628ea7d230997cd45007b

2024年09月15日 00:54:23 +09:00

OpenStack services are balanced between 5 scenarios because OpenStack

Update the README about the third scenario Change-Id: I0aed8a145a7a819f07ce250cd390c50c6197dceb

2016年02月26日 14:57:19 -05:00

Infastructure Jenkins slaves can not afford the load of running everything on

the same node.

rename scenario003 to scenario-aio scenario003 is going to be a scenario gated in OpenStack Infra. It was created to be a AIO scenario, for our testers, so let's rename it to scenario-aio. In a further iteration, scenario003 will be a scenario used by our CI. Change-Id: I53852757d013abfae10e5f4afd41ddbb18da3b03

2016年02月24日 14:50:52 -05:00

One manifest (scenario-aio) is used for people who want to [run a simple All-In-One

Fix link to All-in-one section Anchor tags are autogenerated for headers using lower case, at least with GitHub's Markdown engine. Change-Id: Id5b40699042823650086cb0bf8afe95b3c0268d9

2016年08月26日 10:56:27 +01:00

scenario](#all-in-one).

Implement all-in-one.sh script This script will help newcomers to run this script and deploy a simple scenario of an OpenStack Cloud with Puppet OpenStack modules. Change-Id: I559e5e0a0d21a02d04b3d999b77dee23bb38c341

2015年11月05日 12:02:15 -05:00

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

|:----------:|:-----------:|:-----------:|:-----------:|:-----------:|:-----------:|:------------:|

| ssl | yes | yes | yes | yes | yes | no |

| ipv6 | centos9 | centos9 | centos9 | centos9 | centos9 | no |

| keystone | X | X | X | X | X | X |

Use httpd+mod_wsgi to run glance-api This makes glance-api run by httpd+mod_wsgi instead of standalone eventlet service. This allows us to enable ssl for glance endpoints. Note that this change switches glance backend in scenario 004 from rgw to file, because usage of rgw causes circular dependencies. Swift API is already tested by tempest, and we assume that usage of swift store driver to integrate glance and ceph is not as much popular as one of rbd store driver. Change-Id: I888f288bde30c5eeb2d33facd1e55aaddd670450

2021年11月24日 02:27:05 +09:00

| glance | rbd | swift | file | rbd | cinder | file |

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

| nova | rbd | X | X | rbd | X | X |

| placement | X | X | X | X | X | X |

| neutron | ovs | ovs | ovn | ovs | ovn | ovs |

Test redis sentinel coordination backend tooz 6.1.0 introduced support for authentication and SSL for Redis Sentinel connections. Switch the coordination backend to Sentinel to test this deployment pattern. Note that redis storage driver in gnocchi does not yet support SSL and authentication for Sentinel so it still continues using Redis. Change-Id: Ie429773523280aa15d2da3eec9bd775364b44333

2024年04月02日 23:45:11 +09:00

| cinder | rbd | iscsi | | | iscsi | iscsi |

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

| manila | | | | cephfs | lvm | |

| ceilometer | X | X | | | | |

| aodh | X | X | | | | |

| designate | | | bind | | | |

Test ceph volume backup driver This enables ceph volume backup driver in scenario 001 so that we can test deployment of the driver. Change-Id: Ia07f1be0491bb25a0e5d7b518e9c764a6281474d

2023年07月28日 23:14:17 +09:00

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

| gnocchi | rbd | swift | | | | |

| heat | X | | X | | | |

| swift | | X | | | | |

| trove | | | X | | | |

Enable horizon in scenario 002 ... to test installation of ironic-dashboard. Depends-on: https://review.opendev.org/900799 Change-Id: Ib8ad54cbee1b3002ff643083d6a97d28a25268c7

2023年11月14日 00:04:32 +09:00

| horizon | | X | X | X | X | X |

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

| ironic | | X | | | | |

| zaqar | | X | | | | |

| magnum | | | X | | | |

| mistral | | | X | | | |

| barbican | | X | X | | | |

| ceph | X | | | X | | |

| ceph mds | | | | X | | |

| ceph rgw | | | | X | | |

| vitrage | X | | | | | |

Move watcher to scenario001 Watcher requires telemetry services from a functional point of view, so I think it's good to deploy and test them together. Change-Id: I90b12c9a9674eda7c7b94111c7951e598224a68b

2024年10月29日 18:08:08 +01:00

| watcher | X | | | | | |

Enable cloudkitty Depends-on: https://review.opendev.org/957429 Change-Id: Ib4972776ae6b87906681d0a06c65add887020e55 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>

2025年02月13日 00:53:38 +09:00

| cloudkitty | X | | | | | |

Test deployment with VPNaaS + ml2 ovn driver The neutron-vpnaas plugin supports deployment with ml2 + ovs since 2024.1 . Enable the plugin and its agent to test the new capability to deploy the plugin. Depends-on: https://review.opendev.org/930070 Change-Id: I7c79ba34d5a39639bffdc9278a8455e8eec10bbf

2024年09月15日 23:13:52 +09:00

| vpnaas | | | | X | X | |

Enable Neutron TaaS This enables the Tap-as-a-Service plugin in neutron to test the deployment support we recently added to puppet-neutron. Depends-on: https://review.opendev.org/906016 Change-Id: I1bed97477fa737733d5b59b7de085e61494c69f9

2024年01月18日 11:27:50 +09:00

| taas | | | | X | | |

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

| bgpvpn-api | | | | X | | |

| bgp-dr | | | | X | | |

Test redis (sentinel) cache backend oslo.cache 3.7.0 introduced new options to use redis or redis sentinel as backend. To test the functionality to configure this backend, switch the cache backend in scenario001(Redis) and scenario002(Sentinel). The switch is made only in CentOS because Caracal (or master) packages are not available for Ubuntu, but may be later made in Ubuntu as well once UCA Caracal is released. Change-Id: Ieb681f5bbbf28e1963ab346c17e07265769da4e6

2024年04月02日 23:36:36 +09:00

| memcached | X | X | X | X | X | X |

octavia: Enable jobboard settings Octavia introduced the jobboard driver for amphora v2. Although we are using noop drivers in our CI at this moment, we can enable the feature for testing. Depends-on: https://review.opendev.org/907685 Change-Id: I4789a9b6aa289cf6926931bf82dab5b5dd02fa8f

2024年02月04日 21:07:24 +09:00

| redis | X | X | X | X | X | |

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

| l2gw | | | | X | | |

| octavia | | | | X | X | |

Stop testing amqp1 messaging driver amqp1 driver of the oslo.messaging library was deprecated and it is no longer tested. This replaces usage of the driver by the RabbitMQ driver. Depends-on: https://review.opendev.org/861070 Change-Id: I17666d9507564acb05a69143879ca2ec4b0bdeb0

2023年08月14日 23:12:31 +09:00

Remove scenario 000 integration job The job has been kept non-voting for very long. Because we already have number of integration jobs, which are all superset of this tiny job, let's remove the job to reduce the resource we consume for testing. Change-Id: I7a07def6d53af069814b6565d8563ce757b26719

2023年07月17日 20:15:59 +09:00

Test redis (sentinel) cache backend oslo.cache 3.7.0 introduced new options to use redis or redis sentinel as backend. To test the functionality to configure this backend, switch the cache backend in scenario001(Redis) and scenario002(Sentinel). The switch is made only in CentOS because Caracal (or master) packages are not available for Ubuntu, but may be later made in Ubuntu as well once UCA Caracal is released. Change-Id: Ieb681f5bbbf28e1963ab346c17e07265769da4e6

2024年04月02日 23:36:36 +09:00

Use redis sentinel for taskflow backend Switch taskflow backend in scenario 005 from redis to redis sentinel to improve deployment architecture coverage. The feature is not yet available in ubuntu packages we use so the switch is done only in CentOS. Depends-on: https://review.opendev.org/923693 Change-Id: I1372ce42f8f416003adce1b3ff343779524fe215

2024年07月09日 12:03:40 +09:00

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

This is a typo fix from "will exectued" to "will be executed" Change-Id: Ifae703701299d9d994365669f67026b983136e35

2017年03月03日 09:30:53 -05:00

When the Jenkins slave is created, the *run_tests.sh* script will be executed.

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

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

Update URLs in documents according to document migration Change-Id: I461c6e560f1a01eaee28e0287d103dd89f2a203e

2017年07月14日 12:48:12 +08:00

[Tempest](https://docs.openstack.org/tempest/latest/overview.html) Smoke

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

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:

Update URLs in documents according to document migration Change-Id: I461c6e560f1a01eaee28e0287d103dd89f2a203e

2017年07月14日 12:48:12 +08:00

* https://docs.openstack.org/puppet-openstack-guide/latest

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

Update SSL certificates with SubjectAltNames A recent update to urllib tightened some checks around SSL [1]. This prompted an update to Devstack in order to work properly [2]. Jobs running into this problem without having a SubjectAltName provided will see an error that looks like: SSLError: hostname '127.0.0.1' doesn't match either of '127.0.0.1', 'localhost' Let's also update the certificates to provide the SubjectAltName and provide a way to easily update the certificates if required in the future. [1]: https://github.com/shazow/urllib3/blob/df9d503a8ea767e8a2ee95b3e75a914480c93de6/CHANGES.rst#118-2016年09月26日 [2]: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=69e3c0aac99981f17c76c22111e5c397824b8428 Change-Id: I94a586b333ba6a99ef831c853a19ab127b502d6f

2016年09月28日 17:15:16 -04:00

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.

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

Implement all-in-one.sh script This script will help newcomers to run this script and deploy a simple scenario of an OpenStack Cloud with Puppet OpenStack modules. Change-Id: I559e5e0a0d21a02d04b3d999b77dee23bb38c341

2015年11月05日 12:02:15 -05:00

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:

```bash

Fix Repository Change-Id: I5356da8e8f5b2650298ae57ad2e31e8bdb6d93a0

2019年04月21日 12:59:10 +08:00

git clone https://opendev.org/openstack/puppet-openstack-integration

Implement all-in-one.sh script This script will help newcomers to run this script and deploy a simple scenario of an OpenStack Cloud with Puppet OpenStack modules. Change-Id: I559e5e0a0d21a02d04b3d999b77dee23bb38c341

2015年11月05日 12:02:15 -05:00

cd puppet-openstack-integration

./all-in-one.sh

```

Look at [Description](#description) to see which services it will install

rename scenario003 to scenario-aio scenario003 is going to be a scenario gated in OpenStack Infra. It was created to be a AIO scenario, for our testers, so let's rename it to scenario-aio. In a further iteration, scenario003 will be a scenario used by our CI. Change-Id: I53852757d013abfae10e5f4afd41ddbb18da3b03

2016年02月24日 14:50:52 -05:00

(scenario-aio).

Implement all-in-one.sh script This script will help newcomers to run this script and deploy a simple scenario of an OpenStack Cloud with Puppet OpenStack modules. Change-Id: I559e5e0a0d21a02d04b3d999b77dee23bb38c341

2015年11月05日 12:02:15 -05:00

Split scenarios001 in two scenarios * Split scenario001 in two scenarios: scenario001 and scenario002 * Create README and initiate Puppet OpenStack Integration documentation. Depends-On: Iba6791199f7a2c7fef24b1e8752ed0b564b8512f Depends-On: Id8366cd5d2ddf6da468ecc7adb7d55eb8be4c8d8 Change-Id: Iec58e1cd01963155f35b099f7d9a8a97c26a8d27

2015年10月02日 09:39:01 -04:00

Contributors

------------

* https://github.com/openstack/puppet-openstack-integration/graphs/contributors

openstack/puppet-openstack-integration - puppet-openstack-integration - OpenDev: Free Software Needs Free Tools

145 lines

7.7 KiB

Markdown

Raw Normal View History

openstack/puppet-openstack-integration - puppet-openstack-integration - OpenDev: Free Software Needs Free Tools

145 lines 7.7 KiB Markdown Raw Normal View History Unescape Escape

145 lines

7.7 KiB

Markdown

Raw Normal View History