Puppet provider for virtual switches.
Go to file
Alfredo Moralejo fc04875852 Add fail_mode parameter to OVS Ports
According to info in https://bugs.launchpad.net/tripleo/+bug/1640812
when setting a OVS bridge with physical interface we need to
define fail_mode in OVS_EXTRA parameter of ifcfg to make
sure it's set at the desired mode after reboot.

This patch adds new parameter fail_mode to vs_port (as ifcfg is created
as part of vs_port, not vs_bridge) and defaults it to required value "standalone".

Similar patch was implemented to os-net-config in
e479535b50

Change-Id: I5f7448e3504c9190d7fe5f4a7958c604ef91a058
Closes-Bug: #1656795
(cherry picked from commit 026f64ade4)
2017-02-17 07:55:21 +00:00
lib Add fail_mode parameter to OVS Ports 2017-02-17 07:55:21 +00:00
manifests Modify the OVS DPDK package name to openvswitch 2016-08-05 16:46:49 +05:30
releasenotes Puppet OpenStack Newton RC2 2016-09-26 13:58:08 +00:00
spec Add fail_mode parameter to OVS Ports 2017-02-17 07:55:21 +00:00
.gitignore Add basic structure for ReNo 2016-03-14 08:36:45 -04:00
.gitreview Update .gitreview for stable/newton 2016-09-27 12:42:19 -04:00
CHANGELOG.md Release 4.0.0 2016-03-23 14:50:57 -04:00
Gemfile Use stable/newton spec helper 2016-09-28 10:54:09 -06:00
LICENSE Added LICENSE file 2013-01-16 21:39:20 -08:00
README.md Release 4.0.0 2016-03-23 14:50:57 -04:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-19 22:38:44 -05:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:13:12 +02:00
metadata.json Prepare 9.5.0 release 2017-01-17 13:36:47 -07:00
setup.cfg Add basic structure for ReNo 2016-03-14 08:36:45 -04:00
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

README.md

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