openstack
/
puppet-rally
Code Issues Proposed changes
RETIRED, OpenStack Rally Puppet Module
84 Commits 4 Branches 56 Tags 1.8 MiB
Go to file
Doug Hellmann 764030bfa2 import zuul job settings from project-config 
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: Id23eae0adaab5149432e7ae2f276da0dbe81217e
Story: #2002586
Task: #24325
 		2018-08-31 08:41:22 -04:00
examples Add example manifest 2016-06-25 22:45:25 +08:00
lib/puppet Add rally_deployment as custom resource 2017-05-18 15:38:09 +02:00
manifests Add use_journal option for logging configuration 2018-01-15 16:20:44 +08:00
releasenotes/source Use Python to compute release notes version 2017-08-30 13:47:39 -07:00
spec Add use_journal option for logging configuration 2018-01-15 16:20:44 +08:00
tests puppet-rally: Initial commit 2016-01-02 17:08:09 -05:00
.gitignore Add basic structure for ReNo 2016-10-07 14:57:45 +00:00
.gitreview Update .gitreview for stable/queens 2018-02-20 22:19:25 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-31 08:41:22 -04:00
Gemfile Update Gemfile to pull spec_helper from stable/queens 2018-08-15 10:11:56 -06:00
LICENSE puppet-rally: Initial commit 2016-01-02 17:08:09 -05:00
README.md Update to the latest address in README 2017-09-21 12:30:18 +08:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:14:01 -05:00
bindep.txt Add Puppet package to bindep, for module build 2018-02-19 15:37:09 -05:00
metadata.json Prepare a new Queens release 2018-03-29 08:44:48 +08:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 08:54:16 +08:00
setup.py Add basic structure for ReNo 2016-10-07 14:57:45 +00:00
test-requirements.txt Remove pinned versions from test-requirements.txt 2018-01-16 12:29:49 +08:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/queens 2018-02-20 22:19:28 +00:00

README.md

Team and repository tags

Team and repository tags

rally

Table of Contents

  1. Overview - What is the rally module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with rally
  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 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 Benchmarking service for Openstack.

Module Description

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.

Setup

What the rally module affects

  • Rally, the Benchmarking service for Openstack.

Installing rally

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

Beginning with 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.

Implementation

rally

rally is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.

Limitations

  • All the rally types use the CLI tools and so need to be ran on the rally node.

Beaker-Rspec

This module has beaker-rspec tests

To run the tests on the default vagrant node:

bundle install
bundle exec rake acceptance

For more information on writing and running beaker-rspec tests visit the documentation:

Development

Developer documentation for the entire puppet-openstack project.

Contributors