cb68e4142e
Since a chance in puppet-keystone (1], we now match an endpoint with a service name/type. ) [1] http://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=0a4e06abb0f5b3f324464ff5219d2885816311ce Change-Id: I09c80c1c9b816a4dc734a268010fe8569ca8ec03 Closes-Bug: #1528308
puppet-tuskar
7.0.0 - 2015.2 - Liberty
Table of Contents
- Overview - What is the tuskar module?
- Module Description - What does the module do?
- Setup - The basics of getting started with tuskar
- 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
Overview
The tuskar 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 as part of the core software. The module itself is used to flexibly configure and manage the management service for Openstack.
Module Description
Setup
What the tuskar module affects:
- tuskar, the management service for Openstack.
Implementation
tuskar
tuskar is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Types
tuskar_config
The tuskar_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/tuskar/tuskar.conf file.
tuskar_config { 'DEFAULT/verbose' :
value => true,
}
This will write verbose=true in the [DEFAULT] section.
name
Section/setting name to manage from tuskar.conf
value
The value of the setting to be defined.
secret
Whether to hide the value from Puppet logs. Defaults to false.
ensure_absent_val
If value is equal to ensure_absent_val then the resource will behave as if ensure => absent was specified. Defaults to <SERVICE DEFAULT>
Limitations
Development
Developer documentation for the entire puppet-openstack project.