OpenStack Trove Puppet Module
Go to file
OpenDev Sysadmins 307fff83b2 OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:34:13 +00:00
doc Follow the new PTI for document build 2018-02-28 14:42:12 +08:00
examples Change keystone v2.0 to v3 2019-02-24 13:57:27 +01:00
lib/puppet Make providers use auth_url for authentication 2018-08-03 14:11:47 +02:00
manifests Use validate_legacy 2019-02-23 23:12:52 +01:00
releasenotes Update master for stable/stein 2019-03-22 16:55:13 +00:00
spec Service_token_roles_required missing in the server config file 2019-02-15 10:03:10 +08:00
templates Remove deprecated rabbit_hosts 2018-12-07 09:56:06 +08:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:25 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:34:13 +00:00
.zuul.yaml switch documentation job to new PTI 2018-08-31 08:24:47 -04:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:20:27 +02:00
CHANGELOG.md Modify http to https. 2018-12-11 15:14:29 +08:00
Gemfile Load puppet-openstack_spec_helper locally during tests 2018-02-12 10:53:40 +08:00
LICENSE First commit 2014-05-18 01:38:51 -04:00
metadata.json Bump version for the start of Train 2019-03-25 07:27:59 -06:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:34 -05:00
README.md Add Beaker-Rspec to the table of contents 2019-04-17 09:42:45 +08:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-02 18:20:45 +01:00
setup.py Add basic structure for ReNo 2016-03-14 08:36:32 -04:00
tox.ini Update min tox version to 2.0 2018-10-16 11:40:19 +08:00

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. Beaker-Rspec - Beaker-rspec tests for the project
  7. Development - Guide for contributing to the module
  8. Contributors - Those with commits
  9. Release Notes - Release notes for the project
  10. Repository - The project source code repository

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/v3,
}

This will write auth_url=http://localhost:5000/v3 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/v3,
}

This will write trove_auth_url=http://localhost:5000/v3 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

Release Notes

Repository