- Overview - What is the rally module?
- Module Description - What does the module do?
- Setup - The basics of getting started with rally
- 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
The rally 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 not part of the core software. The module its self is used to flexibly configure and manage the FIXME service for Openstack.
The rally module is a thorough attempt to make Puppet capable of managing the entirety of rally. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the rally module to assist in manipulation of configuration files.
What the rally module affects
- Rally, the FIXME service for Openstack.
rally is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install rally with:
puppet module install openstack/rally
To utilize the rally module's functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. This is not an exhaustive list of all the components needed, we recommend you consult and understand the openstack module and the core openstack documentation.
rally is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
- All the rally types use the CLI tools and so need to be ran on the rally node.
This module has beaker-rspec tests
To run the tests on the default vagrant node:
bundle install
bundle exec rake acceptanceFor more information on writing and running beaker-rspec tests visit the documentation:
Developer documentation for the entire puppet-openstack project.