OpenStack Release Bot cfeea1a051 Update TOX_CONSTRAINTS_FILE for stable/2024.1
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/2024.1 branch, tests will
continue to use the upper-constraints list on master.

Change-Id: I2cf110a5ba38033c03d0010ba1316dec88cf45ed
2024-04-18 10:51:44 +00:00
2023-10-17 11:05:19 +09:00
2024-04-14 15:40:20 +09:00
2024-04-18 10:51:42 +00:00
2023-08-11 18:01:47 +09:00
2016-03-23 14:50:57 -04:00
2023-10-17 11:05:19 +09:00
2013-01-16 21:39:20 -08:00
2024-04-15 22:36:40 +09:00
2020-09-14 23:42:42 +02:00
2022-03-29 11:19:25 +00:00

Team and repository tags

Team and repository tags

VSwitch

Table of Contents

  1. Overview - What is the AODH module?
  2. Development - Guide for contributing to the module
  3. Contributors - Those with commits
  4. Release Notes - Release notes for the project
  5. Repository - The project source code repository
  6. Usage - The usage of the module
  7. 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
Description
Puppet provider for virtual switches.
Readme 48 MiB
Languages
Ruby 75.8%
Puppet 14.8%
Python 9.4%