In order to better understand the LICENSE Change-Id: I4bec16724f0442908eca95d2f4c15220f3ac7ca9 Depends-On: Id1a39a34278b9727cd083d89a63ea31342a28fee
Team and repository tags
Table of Contents
- Overview - What is the octavia module?
- Module Description - What does the module do?
- Setup - The basics of getting started with octavia
- 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 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.
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.
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.