openstack
/
puppet-placement
Code Issues Proposed changes
OpenStack Placement Puppet Module
129 Commits 8 Branches 53 Tags 2.3 MiB
Ruby 49.1%
Puppet 43.2%
Python 7.7%
Go to file
ZhongShengping 5dceb01860 Allow db sync timeouts to be configurable 
As Openstack projects continue to have longer database migration
chains, the Puppet default timeout of 300 seconds for an execution
is becoming too short a duration on some hardware, leading to timeouts.
As projects continue to add more migration scripts without pruning
the base, timeouts will continue to become more frequent unless
this time can be expanded.

Change-Id: If98c83c16e981353780573f6f0f0f737f1374ba1
Closes-Bug: #1904962
 		2020-11-23 09:27:52 +08:00
doc Switch to newer openstackdocstheme and reno versions 2020-06-02 15:00:55 +02:00
examples Convert all class usage to relative names 2019-12-08 23:19:32 +01:00
lib/puppet Use anchor to require necessary packages 2020-05-04 02:03:22 +09:00
manifests Allow db sync timeouts to be configurable 2020-11-23 09:27:52 +08:00
releasenotes Allow db sync timeouts to be configurable 2020-11-23 09:27:52 +08:00
spec Allow db sync timeouts to be configurable 2020-11-23 09:27:52 +08:00
.gitignore Add .gitignore file 2018-12-20 10:39:55 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:33:57 +00:00
.zuul.yaml Add Puppet Litmus 2020-08-31 21:52:16 +02:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:50:18 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 23:03:25 +02:00
LICENSE Initial cookiecutter run and import from puppet-nova 2018-12-11 10:40:58 +00:00
README.md Add Puppet Litmus 2020-08-31 21:52:16 +02:00
Rakefile Initial cookiecutter run and import from puppet-nova 2018-12-11 10:40:58 +00:00
bindep.txt Add packages needed by tests 2018-12-20 10:43:16 +08:00
metadata.json Fix outdated files 2020-10-28 10:40:09 +08:00
setup.cfg Cleanup docs, testing and missed things 2018-12-13 09:37:43 +01:00
setup.py Initial cookiecutter run and import from puppet-nova 2018-12-11 10:40:58 +00:00
tox.ini Replace deprecated UPPER_CONSTRAINTS_FILE variable 2020-11-11 09:08:36 +08:00

README.md

Team and repository tags

Team and repository tags

Table of Contents

  1. Overview - What is the placement module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with placement
  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

Overview

The placement 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 placement service for OpenStack.

Module Description

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

Setup

What the placement module affects

  • Placement, the placement service for OpenStack.

Installing placement

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

Beginning with placement

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

Implementation

placement

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

Limitations

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

Development

Developer documentation for the entire puppet-openstack project.

Contributors