Puppet provider for virtual switches.
OpenStack Release Bot
43ee6e8d17
Add file to the reno documentation build to show release notes for stable/2024.2. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2024.2. Sem-Ver: feature Change-Id: Ib87604f2a0436de290a6d3f79aa480c541c6a0ac |
||
|---|---|---|
| data | ||
| doc | ||
| lib | ||
| manifests | ||
| releasenotes | ||
| spec | ||
| .gitignore | ||
| .gitreview | ||
| .pdkignore | ||
| .zuul.yaml | ||
| bindep.txt | ||
| CHANGELOG.md | ||
| CONTRIBUTING.rst | ||
| Gemfile | ||
| hiera.yaml | ||
| LICENSE | ||
| metadata.json | ||
| Rakefile | ||
| README.md | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
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