OpenStack Trove Puppet Module
Go to file
ZhongShengping f6c18d5653 Add 'openstack-db' tag to db-sync Exec resource
In order to make easy orchestration on all OpenStack db-sync, add this
tag so people can use this tag in composition layer.
A use case it to set some orchestration to make sure MySQL Galera is
ready before running any Exec with this tag.

Change-Id: I7baded10a128532f7267903fa8d14f576cd9f47a
Closes-Bug: #1755102
(cherry picked from commit 90863dce61)
2018-10-12 01:38:57 +00:00
examples Fix hosts lists in example.pp 2016-12-14 12:34:32 +01:00
lib/puppet Configure keystone authtoken options 2016-08-23 22:08:04 -03:00
manifests Add 'openstack-db' tag to db-sync Exec resource 2018-10-12 01:38:57 +00:00
releasenotes Add 'openstack-db' tag to db-sync Exec resource 2018-10-12 01:38:57 +00:00
spec Add 'openstack-db' tag to db-sync Exec resource 2018-10-12 01:38:57 +00:00
templates removing deprecated options from DEFAULT 2016-11-17 13:27:39 +01:00
.gitignore Add basic structure for ReNo 2016-03-14 08:36:32 -04:00
.gitreview Update .gitreview for stable/pike 2017-08-24 14:02:02 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-31 08:35:47 -04:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:08:00 -04:00
Gemfile Update Gemfile to pull spec_helper from stable/pike 2017-08-24 08:57:28 -06:00
LICENSE First commit 2014-05-18 01:38:51 -04:00
README.md Update URLs in documents according to document migration 2017-07-14 13:52:02 +08:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:34 -05:00
bindep.txt [pike] Add Puppet package to bindep, for module build 2017-10-28 14:48:39 +00:00
metadata.json Prepare for Pike post release 2018-01-16 16:42:28 -08:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 13:52:02 +08:00
setup.py Add basic structure for ReNo 2016-03-14 08:36:32 -04:00
test-requirements.txt Update openstackdocstheme>=1.16.0 2017-07-31 11:04:30 +08:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/pike 2017-08-24 14:02:02 +00:00

README.md

Team and repository tags

Team and repository tags

puppet-trove

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/backlog' :
  value => 4096,
}

This will write backlog=4096 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/auth_url' :
  value => http://localhost:5000/v2.0,
}

This will write auth_url=http://localhost:5000/v2.0 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/trove_auth_url' :
  value => http://localhost:5000/v2.0,
}

This will write trove_auth_url=http://localhost:5000/v2.0 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/network_driver' :
  value => trove.network.neutron.NeutronDriver,
}

This will write network_driver=trove.network.neutron.NeutronDriver 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:

bundle install
bundle exec rspec spec/acceptance

Development

Developer documentation for the entire puppet-openstack project.

Contributors