06a9b12199
... because the actual option in oslo.messaging was deprecated. Depends-on: https://review.opendev.org/925778 Change-Id: I4c6667dd4316ad3d7f40e706103b5fada215314b
Team and repository tags
oslo
Table of Contents
- Overview - What is the oslo module?
- Module Description - What does the module do?
- Setup - The basics of getting started with oslo
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Release notes for the project
- 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.
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.