
Add ability to use python-pymysql library as backend for MySQL connections. Update acceptance tests to use pyMySQL. Docs: https://wiki.openstack.org/wiki/PyMySQL_evaluation The same implementation as it's done for keystone: https://review.openstack.org/#/c/242134/ Change-Id: I669bec38286a863dab3e112e9442f2484bbe107c
puppet-tuskar
6.0.0 - 2015.1 - Kilo
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.