Puppet-contrail
Table of Contents
- Overview - What is the puppet-contrail module?
- Module Description - What does the module do?
- Setup - The basics of getting started with puppet-contrail
- 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
A Puppet Module is a collection of related content that can be used to model the configuration of a discrete service.
Module Description
The puppet-contrail module is a thorough attempt to make Puppet capable of managing the entirety of OpenContrail. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the puppet-contrail module to assist in manipulation of configuration files.
Setup
What the puppet-contrail module affects
- puppet-contrail, the Juniper SDN service.
Installing puppet-contrail
example% puppet module install enovance/contrail
Beginning with puppet-contrail
To utilize the puppet-contrail module's functionality you will need to declare multiple resources. The following is a modified excerpt from the spinalstack module. This is not an exhaustive list of all the components needed, we recommend you consult and understand the spinalstack module and the core openstack documentation.
Define a puppet-contrail node
class { 'contrail': }
Implementation
puppet-contrail
Puppet-contrail is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
*
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.