55af0b29fb
... because it was deprecated during Yoga cycle[1] and has had no effect since then. [1] 3ff72b5736d94ff32535ab345df4cb588c95286f Change-Id: I7a24045ee414a0ae81aa7093621ce07d791e5e31
Team and repository tags
VSwitch
Table of Contents
- Overview - What is the AODH module?
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Release notes for the project
- Repository - The project source code repository
- Usage - The usage of the module
- TODO - What to do next
Overview
4.0.0 - 2016.1 - Mitaka
A Puppet module providing things for vSwitches. At the moment OVS is the only one I've added but please feel free to contribute new providers through Stackforge. It's based upon types and providers so we can support more then just OVS or one vSwitch type.
The current layout is:
- bridges - A "Bridge" is basically the thing you plug ports / interfaces into.
- ports - A Port is a interface you plug into the bridge (switch).
- configs - Configuration settings, if any
Development
Developer documentation for the entire puppet-openstack project.
Contributors
Release Notes
Repository
Usage
To create a new bridge, use the vs_bridge type:
vs_bridge { 'br-ex':
ensure => present,
}
You can then attach a device to the bridge with a virtual port:
vs_port { 'eth2':
ensure => present,
bridge => 'br-ex',
}
You can change the vswitch configuration settings using.
vs_config { 'parameter_name':
ensure => present,
value => "some_value"
}
For configuration parameters that are 'hash' data type, the resource name should be of the following format
parameter-name:key-name
Ex.
vs_config { 'external_ids:ovn-remote':
ensure => present,
value => 'tcp:127.0.0.1:6640'
}
For 'set/array' data types, value should be in the following format
'[<values>]'
Ex.
vs_config { 'array_key':
ensure => present,
value => '[2, 1, 6, 4]'
}
TODO:
- OpenFlow controller settings
- OpenFlow Settings
- OpenFlow Tables
- More facts
- Others that are not named here