cc138ca445
This patch is aim to add a specific class for managing trove quota related parameters. Change-Id: Id84e0ac02809f9adb6e5d3027a10eb1e2063e88f Closes-Bug: #1469577 |
||
---|---|---|
examples | ||
lib/puppet | ||
manifests | ||
spec | ||
templates | ||
.fixtures.yml | ||
.gitignore | ||
.gitreview | ||
Gemfile | ||
LICENSE | ||
metadata.json | ||
Rakefile | ||
README.md |
puppet-trove
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 Stackforge, an effort by the Openstack infrastructure team to provide continuous integration testing and code review for Openstack and Openstack community projects not 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.
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.