OpenStack Trove Puppet Module
Go to file
Takashi Kajinami 22ef63f8f9 Prepare to rename trove::api::service_credentials
This class is used by all services but is still kept under the api
directory.

Change-Id: I4016752d94da35ea257f9c76079a33797151640b
2024-03-25 14:10:57 +09:00
doc Update openstackdocstheme to the latest version 2021-09-29 16:06:51 +08:00
examples Use service credential parameters to define keystone v3 auth 2020-05-06 21:36:00 +09:00
lib/puppet Merge "Use new openstackclient tag" 2023-11-20 18:21:36 +00:00
manifests Prepare to rename trove::api::service_credentials 2024-03-25 14:10:57 +09:00
releasenotes Prepare to rename trove::api::service_credentials 2024-03-25 14:10:57 +09:00
spec Prepare to rename trove::api::service_credentials 2024-03-25 14:10:57 +09: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
.pdkignore Exclude release note files 2023-08-11 18:00:42 +09:00
.zuul.yaml Add Puppet Litmus 2020-09-11 10:14:39 +00: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
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:54:29 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 23:07:14 +02:00
LICENSE First commit 2014-05-18 01:38:51 -04:00
metadata.json Bump supported Debian version to 12 (Bookworm) 2023-11-18 09:25:57 +00:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:34 -05:00
README.md Remove resource types for per-daemon config files 2022-07-15 18:05:59 +09:00
setup.cfg Add information technology in the setup.cfg 2021-10-01 06:54:50 +08:00
setup.py setuptools: Disable auto discovery 2022-03-29 10:42:57 +02:00
tox.ini Stop configuring install_command in tox. 2021-09-29 18:21:19 +09: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. Development - Guide for contributing to the module
  7. Contributors - Those with commits
  8. Release Notes - Release notes for the project
  9. 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_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>

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.

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

Repository