Add support for setting extra network options for ML2 plugin

Bug #1200767 reported by Kyle Mestery
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Kyle Mestery

Bug Description

The ML2 plugin is deprecating support for the OVS and LinuxBridge plugins at some future point. The plugin works with the existing OVS and LinuxBridge agents. Adding support to devstack to configure extra options (similar to how this was done for LinuxBridge and OVS [1]) would be a nice addition for developers of ML2.


Kyle Mestery (mestery)
Changed in devstack:
assignee: nobody → Kyle Mestery (mestery)
Kyle Mestery (mestery)
Changed in devstack:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

Fix proposed to branch: master

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (master)

Submitter: Jenkins
Branch: master

commit b772659f9df8153caa3b0fa155614d2d6504541e
Author: Kyle Mestery <email address hidden>
Date: Fri Jul 19 14:26:53 2013 +0000

    Update the ML2 configuration in devstack

    This commit adds support to devstack to set ML2 options including
    MechanismDrivers, TypeDrivers, and TypeDriver specific configuration for ML2
    when running with devstack.

    This also allows for simple configuration of VLAN, GRE, and VXLAN ML2 devstack
    setups with the OVS agent as follows:

        # VLAN configuration

        # GRE tunnel configuration

        # VXLAN tunnel configuration

    Fixes bug 1200767

    Change-Id: Ib16efac13440b5d50658a0e6be35bc735510a262

Changed in devstack:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.