Go to file
Takashi Kajinami bdf0c6f1b4 key_manager: Add service user options for Barbican key manager
This change introduces some parameters to set up the service user token
feature for Barbican key manager, which was implemented during the Xena
cycle[1].

This basically replicates the implementation in puppet-keystone class.
We should not make this dependent on puppet-keystone to avoid circular
dependency between puppet-oslo and puppet-keystone.

[1] 162039467ad0dfc5e25a16b75d9072d607690702

Change-Id: I6d94318929cf4bcfc61180494110d0e5812356c0
2021-09-23 22:07:01 +09:00
2021-03-27 15:31:57 +08:00
2020-05-04 14:39:35 +09:00
2019-02-14 23:15:32 +01:00
2019-04-19 19:42:55 +00:00
2021-05-14 11:52:44 +09:00
2018-04-06 20:14:58 +08:00
2021-09-17 17:36:10 +08:00
2016-01-26 01:34:40 +08:00
2020-08-31 21:49:04 +02:00
2016-05-20 00:14:52 +02:00

Team and repository tags

Team and repository tags

oslo

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

Overview

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.

Following versions of oslo libraries are get from requirements.txt in each project.

Name oslo.cache oslo.config oslo.concurrency oslo.context oslo.db oslo.log oslo.messaging oslo.middleware oslo.policy oslo.reports oslo.rootwrap oslo.serialization oslo.utils oslo.versionedobjects oslo.service oslo.i18n oslo.vmware
Aodh n/a >=2.6.0 n/a >=0.2.0 >=1.12.0 >=1.2.0 !=2.8.0,>2.6.1 !=2.0.0,>=1.2.0 >=0.5.0 n/a n/a >=1.4.0 >=1.9.0 n/a >=0.1.0 >=1.5.0 n/a
Barbican n/a >=3.2.0 >=2.3.0 >=0.2.0 n/a >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 n/a >=0.5.0 n/a n/a >=1.10.0 >=3.4.0 n/a >=1.0.0 >=1.5.0 n/a
Cinder n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.2.0 >=0.13.0 >=1.0.0 >=1.5.0 >=1.16.0
Ceilometer n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.4.0 n/a >=1.0.0 >=1.5.0 n/a
Designate n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.4.0 n/a >=1.0.0 >=1.5.0 n/a
Glance n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.2.0 n/a >=1.0.0 >=1.5.0 n/a
Gnocchi n/a >=2.6.0 n/a n/a n/a >=1.0.0 n/a ? >=0.3.0 n/a n/a >=1.4.0 >=1.6.0 n/a n/a n/a n/a
Heat >= 0.8.0 >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.4.0 >= 0.13.0 >=1.0.0 >=1.5.0 n/a
Ironic n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.2.0 >= 0.13.0 >=1.0.0 >=1.5.0 n/a
Keystone >= 0.8.0 >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.2.0 n/a >=1.0.0 >=1.5.0 n/a
Manila n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.4.0 n/a >=1.0.0 >=1.5.0 n/a
Mistral n/a >=3.2.0 >=2.3.0 n/a >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 n/a n/a n/a n/a >=1.10.0 >=3.2.0 n/a >=1.0.0 n/a n/a
Murano n/a >=3.2.0 n/a >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 n/a n/a >=1.10.0 >=3.4.0 n/a >=1.0.0 >=1.5.0 n/a
Neutron n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >=0.5.0 >=0.6.0 >=2.0.0 >=1.10.0 >=3.4.0 >= 0.13.0 >=1.0.0 >=1.5.0 n/a
Rally n/a >=3.2.0 n/a >=3.2.0 >=4.1.0 >=1.14.0 n/a n/a n/a n/a n/a >=1.10.0 >=3.4.0 n/a n/a >=1.5.0 n/a
Sahara n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 >= 0.5.0 n/a >=2.0.0 >=1.10.0 >=3.4.0 n/a >=1.0.0 >=1.5.0 n/a
Tempest n/a >=3.2.0 >=2.3.0 n/a n/a >=1.14.0 n/a n/a n/a n/a n/a >=1.10.0 >=3.2.0 n/a >=1.0.0 >=1.5.0 n/a
Trove n/a >=3.2.0 >=2.3.0 >=0.2.0 >=4.1.0 >=1.14.0 !=2.8.0,!=3.1.0,>2.6.1 >=3.0.0 n/a n/a n/a >=1.10.0 >=3.4.0 n/a >=1.0.0 >=1.5.0 n/a
Tuskar n/a >=2.3.0 n/a n/a >=2.4.1 n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
Swift n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
Zaqar >= 0.8.0 >=3.2.0 n/a >=0.2.0 n/a >=1.14.0 n/a n/a >= 0.5.0 n/a n/a >=1.10.0 >=3.2.0 n/a n/a >=1.5.0 n/a

Setup

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.

Implementation

oslo

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

Limitations

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

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

Repository

Description
Module for managing Oslo.* library
Readme 4.7 MiB
Languages
Ruby 53.2%
Puppet 42.3%
Python 4.3%
Pascal 0.2%