openstack
/
puppet-oslo
Code Issues Proposed changes
Module for managing Oslo.* library
472 Commits 9 Branches 95 Tags 4.4 MiB
Ruby 51.3%
Puppet 44.2%
Python 4.4%
Pascal 0.1%
Go to file
Takashi Kajinami d0dd31ee35 db: Use ensure_packages to manage backend package 
... instead of skipping the resource definition in case the same is
already defined. This allows us to detect any conflicting definitions
defined in multiple manifests.

Change-Id: Id78c6c1553973b57b4b9e7edaf8d029d833f4722
 		2023-07-28 13:14:52 +09: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 db: Use ensure_packages to manage backend package 2023-07-28 13:14:52 +09:00
releasenotes Remove support for Puppet 6 2023-05-22 12:28:31 +09:00
spec db: Use ensure_packages to manage backend package 2023-07-28 13:14:52 +09:00
types remove legacy db connection check with proper types 2023-07-25 22:52:20 +09:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:25 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:42:55 +00:00
.zuul.yaml Remove TripleO job 2023-03-13 11:19:56 +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
README.md 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 Remove support for Puppet 6 2023-05-22 12:28:31 +09:00
setup.cfg Add information technology in the setup.cfg 2021-10-01 06:54:49 +08:00
setup.py setuptools: Disable auto discovery 2022-03-29 10:41:18 +02:00
tox.ini Replace deprecated UPPER_CONSTRAINTS_FILE variable 2020-11-11 09:08:35 +08:00

README.md

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.

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