c73c228ae7
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 Also: require package before config file Before trying to build the guestagent config file from the template with Puppet, first install the package so we make sure /etc/trove is ready. Otherwise, Puppet will randomly fail to create the file, if the package is not installed yet. We need to squash the two changes otherwise CI will never pass. Change-Id: I9662c684c83933ffe6ede0337bc1770dd65b0ce7 Closes-Bug: #1528308
puppet-trove
7.0.0 - 2015.2 - Liberty
Table of Contents
- Overview - What is the trove module?
- Module Description - What does the module do?
- Setup - The basics of getting started with trove
- 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 trove 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 database service for Openstack.
Module Description
Setup
What the trove module affects:
- trove, the database service for Openstack.
Implementation
trove
trove is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Types
trove_config
The trove_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/trove/trove.conf file.
trove_config { 'DEFAULT/verbose' :
value => true,
}
This will write verbose=true in the [DEFAULT] section.
name
Section/setting name to manage from trove.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>
trove_conductor_config
The trove_conductor_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/trove/trove-conductor.conf file.
trove_conductor_config { 'DEFAULT/verbose' :
value => true,
}
This will write verbose=true in the [DEFAULT] section.
name
Section/setting name to manage from trove.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>
trove_guestagent_config
The trove_guestagent_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/trove/trove-guestagent.conf file.
trove_guestagent_config { 'DEFAULT/verbose' :
value => true,
}
This will write verbose=true in the [DEFAULT] section.
name
Section/setting name to manage from trove.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>
trove_taskmanager_config
The trove_taskmanager_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/trove/trove-taskmanager.conf file.
trove_taskmanager_config { 'DEFAULT/verbose' :
value => true,
}
This will write verbose=true in the [DEFAULT] section.
name
Section/setting name to manage from trove.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
Security
For security reasons, a separate in-cloud RabbitMQ cluster should be set up for Trove to use. The reason for this is that the guest agent needs to communicate with RabbitMQ, so it is not advisable to give instances access to the same RabbitMQ server that the core OpenStack services are using for communication.
Please note that puppet-trove cannot check if this rule is being followed, so it is the deployer's responsibility to do it.
Beaker-Rspec
This module has beaker-rspec tests
To run:
shell bundle install bundle exec rspec spec/acceptance
Development
Developer documentation for the entire puppet-openstack project.