Module for managing Oslo.* library
Go to file
Takashi Kajinami 551602d641 Add .pdkignore to exclude some files from tar ball
We've seen release job failures caused by too large tarball, which
contains irrelevant files like git history.

Let's exclude these files to reduce size of the archive.

The file is copied from the puppetlabs repositories with some files
specific to OpenStack projects added.

Change-Id: Ib2da55f670739f618664bd849daad5fc3c0db62c
(cherry picked from commit 1eedd9bcc7)
(cherry picked from commit 4cc62f4423)
2023-08-15 08:59:14 +00:00
doc Update openstackdocstheme to the latest version 2021-09-29 16:06:50 +08:00
examples Convert all class usage to relative names 2019-12-08 23:18:01 +01:00
manifests Fox wrong format of [cache] backend_argument 2022-11-30 02:47:16 +00:00
releasenotes coordination: Deprecate support of the etcd3 driver 2022-10-05 04:14:05 +00:00
spec Fox wrong format of [cache] backend_argument 2022-11-30 02:47:16 +00:00
types Add Oslo::Dbconn data type 2019-02-14 23:15:32 +01:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:25 +08:00
.gitreview Update .gitreview for stable/zed 2022-10-20 11:10:24 +00:00
.pdkignore Add .pdkignore to exclude some files from tar ball 2023-08-15 08:59:14 +00:00
.zuul.yaml Zed-only: Remove TripleO job 2023-05-19 13:50:27 +09:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:48:01 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 23:02:17 +02:00
LICENSE Update LICENSE 2018-04-06 20:14:58 +08:00 Drop version table from README 2022-02-18 19:41:57 +09:00
Rakefile Fix multiple bugs in puppet-oslo 2016-01-26 01:34:40 +08:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:19:29 +02:00
metadata.json Prepare Zed RC1 2022-10-05 04:14:22 +00:00
setup.cfg Add information technology in the setup.cfg 2021-10-01 06:54:49 +08:00 setuptools: Disable auto discovery 2022-03-29 10:41:18 +02:00
tox.ini Update TOX_CONSTRAINTS_FILE for stable/zed 2022-10-20 11:10:26 +00:00

Team and repository tags

Team and repository tags


Table of Contents

  1. Overview - What is the oslo module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with oslo
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Contributors - Those with commits
  8. Release Notes - Release notes for the project
  9. Repository - The project source code repository


The oslo module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects not part of the core software. The module its self is used to flexibly configure and manage the Puppet OpenStack common module for OpenStack.

Module Description

The oslo module is a thorough attempt to make Puppet capable of managing the entirety of oslo libraries. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the oslo module to assist in manipulation of configuration files.


What the oslo module affects

  • Oslo, the oslo libraries for OpenStack.

Installing oslo

oslo is not currently in Puppet Forge, but is anticipated to be added soon.  Once that happens, you'll be able to install oslo with:
puppet module install openstack/oslo

Beginning with oslo

To utilize the oslo module's functionality you will need to declare multiple resources.



oslo is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.


  • All the oslo types use the CLI tools and so need to be ran on the oslo node.


Developer documentation for the entire puppet-openstack project.


Release Notes