Puppet provider for virtual switches.
Go to file
Flavio Percoco 3bf8dbb121 Show team and repo badges on README
This patch adds the team's and repository's badges to the README file.
The motivation behind this is to communicate the project status and
features at first glance.

For more information about this effort, please read this email thread:

http://lists.openstack.org/pipermail/openstack-dev/2016-October/105562.html

To see an example of how this would look like check:

https://gist.github.com/3178920eb6542706ec68fd0ff3681cde

Change-Id: Idf8f19aff1675c0e5efc666671c20249f68a595b
2016-11-25 17:43:44 +01:00
lib Added leading zeros to the pci address set by facter 2016-09-09 13:23:19 +05:30
manifests Modify the OVS DPDK package name to openvswitch 2016-08-05 16:46:49 +05:30
releasenotes Prepare 6.0.0 release 2016-11-16 22:36:44 +00:00
spec Switch to rspec-puppet-facts 2016-10-05 17:13:28 -06: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 Move other-requirements.txt to bindep.txt 2016-08-12 21:13:12 +02:00
CHANGELOG.md Release 4.0.0 2016-03-23 14:50:57 -04:00
Gemfile Gemfile: rely on puppet-openstack_spec_helper for dependencies 2016-03-30 12:27:31 -04:00
LICENSE Added LICENSE file 2013-01-16 21:39:20 -08:00
metadata.json Prepare 6.0.0 release 2016-11-16 22:36:44 +00:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-19 22:38:44 -05:00
README.md Show team and repo badges on README 2016-11-25 17:43:44 +01:00
setup.cfg Changed the home-page to point Openstack Puppet Homepage 2016-10-04 11:24:16 +05:30
setup.py Add basic structure for ReNo 2016-03-14 08:36:45 -04:00
test-requirements.txt Add basic structure for ReNo 2016-03-14 08:36:45 -04:00
tox.ini Add basic structure for ReNo 2016-03-14 08:36:45 -04: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