OpenStack Octavia Puppet Module
Go to file
ZhongShengping 7acccc6b09 Dissuade .gitignore references to personal tools
Developers run all sorts of different tools within Git repositories,
any of which can leave their own special trashfiles all over the
place. We can't every hope to catalog them all, so better to
recommend developers simply configure a global core.excludesfile to
filter the irrelevant files which tend to get created by their
personal choice of tools. Add a comment block explaining this, for
clarity, and remove the one current editor-specific entry present.

We can, and should of course, continue to list files created by the
tools recommended by our workflow (test frameworks, documentation
and packaging builds, et cetera).

This change is a port of Ib58a57267b064e4142686de6c37a70dbff04b9a7
from the openstack-dev/cookiecutter repository.

Change-Id: I4da107a989ac25cda4419cf2678ae672cf6ffba6
2018-10-08 11:39:24 +08:00
doc Follow the new PTI for document build 2018-02-28 14:42:11 +08:00
lib/puppet puppet-octavia: Initial commit 2016-03-09 18:09:58 -05:00
manifests Fix the duplicated vars defined 2018-09-13 17:27:59 -04:00
releasenotes Add release note for database change 2018-09-14 12:18:25 +02:00
spec Merge "Added missing DB params to init class" 2018-09-06 21:51:56 +00:00
tests Fix the smoke testing link 2018-07-30 12:31:32 -04:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:24 +08:00
.gitreview Added .gitreview 2016-03-08 10:45:44 +00:00
.zuul.yaml switch documentation job to new PTI 2018-08-31 08:24:41 -04:00
Gemfile Load puppet-openstack_spec_helper locally during tests 2018-02-12 10:53:38 +08:00
LICENSE Update LICENSE 2018-04-06 20:14:49 +08:00 Add the missing 'Table of Contents' 2018-08-28 13:35:58 +00:00
Rakefile puppet-octavia: Initial commit 2016-03-09 18:09:58 -05:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:19:11 +02:00
metadata.json Bump version for the start of Stein 2018-08-30 12:10:30 -06:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 08:53:31 +08:00 Add basic structure for ReNo 2016-10-07 14:57:23 +00:00
tox.ini fix tox python3 overrides 2018-06-08 14:23:32 +08:00

Team and repository tags

Team and repository tags


Table of Contents

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


The octavia 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 scalable load balancer service for OpenStack.

Module Description

The octavia module is a thorough attempt to make Puppet capable of managing the entirety of octavia. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the octavia module to assist in manipulation of configuration files.


What the octavia module affects

  • Octavia, the scalable load balancer service for OpenStack.

Installing octavia

octavia is not currently in Puppet Forge, but is anticipated to be added soon.  Once that happens, you'll be able to install octavia with:
puppet module install openstack/octavia

Beginning with octavia

To utilize the octavia module's functionality you will need to declare multiple resources.



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


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


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:


Developer documentation for the entire puppet-openstack project.


Release Notes