OpenStack Trove Puppet Module
Go to file
Alex Schultz 4f9b1c46ed Add rspec-puppet-facts to the spec_helper
This change adds the rspec-puppet-facts gem to the spec helper so that
we can centralize the management of the base operating systems that we
support. rspec-puppet-facts allows us to simplify our unit tests and
provides a more complete list of Operating Systems and their associated
facts for the unit tests.  With this change we can now loop over and
test CentOS, Debian, Fedora, RedHat, and Ubuntu by simply providing a
list of supported os to rspec-puppet-facts.

Additionally this change includes a central object for managing our
supported os list for rspec-puppet-facts and providing our default facts
like os_service_default. This central object should replace the usage of
@default_facts within the unit tests for each module.

Change-Id: I4770ec921ee7bd608b46aa07eae8b173cb9d554e
2016-01-14 20:15:39 +03:00
examples Add Puppet 4.x lint checks 2015-03-16 18:41:48 +00:00
lib/puppet Remove trove ubuntu package hack 2015-12-03 16:05:00 +01:00
manifests Introduce amqp_durable_queues option 2016-01-07 04:04:40 +00:00
spec Add rspec-puppet-facts to the spec_helper 2016-01-14 20:15:39 +03:00
templates Use swift_url variable in the template instead of the hardcoded url. 2015-12-11 15:44:13 +01:00
.gitignore Try to use zuul-cloner to prepare fixtures 2015-10-08 15:20:39 -07:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
CHANGELOG.md release: prepare 7.0.0 (liberty) 2015-11-26 09:31:33 +01:00
Gemfile Add rspec-puppet-facts to the spec_helper 2016-01-14 20:15:39 +03:00
LICENSE First commit 2014-05-18 01:38:51 -04:00
metadata.json release: prepare 7.0.0 (liberty) 2015-11-26 09:31:33 +01:00
Rakefile Checkout openstack-integration from master 2015-11-26 11:46:22 +01:00
README.md Merge "Typo in README.md" 2016-01-07 20:27:21 +00:00

puppet-trove

7.0.0 - 2015.2 - Liberty

Table of Contents

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

Installing trove

puppet module install openstack/trove

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 child 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.

Contributors