Puppet provider for virtual switches.
Go to file
2017-07-12 15:10:19 +00:00
lib Define a function for range to mask conversion 2017-06-12 07:32:21 -04:00
manifests Define a function for range to mask conversion 2017-06-12 07:32:21 -04:00
releasenotes Fix openstackdocstheme 2017-07-02 14:30:37 +08:00
spec Added test case for the function range_to_mask() 2017-06-14 07:11:31 -04:00
.gitignore Add basic structure for ReNo 2016-03-14 08:36:45 -04:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
bindep.txt Update tox configuration 2017-05-17 09:51:12 -06:00
CHANGELOG.md Release 4.0.0 2016-03-23 14:50:57 -04:00
Gemfile Update tox configuration 2017-05-17 09:51:12 -06:00
LICENSE Added LICENSE file 2013-01-16 21:39:20 -08:00
metadata.json Bump version for Pike M3 Dev 2017-06-08 15:34:22 -06:00
Rakefile OVS2.6 changes for DPDK 2017-04-04 08:59:50 -04:00
README.md Show team and repo badges on README 2016-11-25 17:43:44 +01:00
setup.cfg Change author in setup.cfg 2017-07-04 18:26:18 +05:30
setup.py Add basic structure for ReNo 2016-03-14 08:36:45 -04:00
test-requirements.txt Fix openstackdocstheme 2017-07-02 14:30:37 +08:00
tox.ini Add environment variable 2017-06-12 16:15:37 +08:00

Team and repository tags

Team and repository tags

VSwitch

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

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]'
}

Beaker-Rspec

This module has beaker-rspec tests

To run:

shell bundle install bundle exec rspec spec/acceptance

TODO:

  • OpenFlow controller settings
  • OpenFlow Settings
  • OpenFlow Tables
  • More facts
  • Others that are not named here