Atom feed of this document
  
 

 Plug-in architecture

The original Compute network implementation assumed a basic model of isolation through Linux VLANs and IP tables. Networking introduces support for vendor plug-ins, which offer a custom back-end implementation of the Networking API. A plug-in can use a variety of technologies to implement the logical API requests. Some Networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide similar benefits.

Table 7.3. Available networking plug-ins
Plug-in Documentation
Big Switch Plug-in (Floodlight REST Proxy) This guide and http://www.openflowhub.org/display/floodlightcontroller/Neutron+REST+Proxy+Plugin
Brocade Plug-in This guide and https://wiki.openstack.org/wiki/Brocade-neutron-plugin
Cisco http://wiki.openstack.org/cisco-neutron
Cloudbase Hyper-V Plug-in http://www.cloudbase.it/quantum-hyper-v-plugin/
Linux Bridge Plug-in http://wiki.openstack.org/Neutron-Linux-Bridge-Plugin
Mellanox Plug-in https://wiki.openstack.org/wiki/Mellanox-Neutron/
Midonet Plug-in http://www.midokura.com/
ML2 (Modular Layer 2) Plug-in https://wiki.openstack.org/wiki/Neutron/ML2
NEC OpenFlow Plug-in https://wiki.openstack.org/wiki/Neutron/NEC_OpenFlow_Plugin
Open vSwitch Plug-in This guide.
PLUMgrid This guide and https://https://wiki.openstack.org/wiki/PLUMgrid-Neutron
Ryu Plug-in This guide and https://github.com/osrg/ryu/wiki/OpenStack
VMware NSX Plug-in This guide and NSX Product Overview, NSX Product Support

Plug-ins can have different properties for hardware requirements, features, performance, scale, or operator tools. Because Networking supports a large number of plug-ins, the cloud administrator can weigh options to decide on the right networking technology for the deployment.

In the Havana release, OpenStack Networking introduces the Modular Layer 2 (ML2) plug-in that enables the use of multiple concurrent mechanism drivers. This capability aligns with the complex requirements typically found in large heterogeneous environments. It currently works with the existing Open vSwitch, Linux Bridge, and Hyper-v L2 agents. The ML2 framework simplifies the addition of support for new L2 technologies and reduces the effort that is required to add and maintain them compared to earlier large plug-ins.

[Note]Plug-in deprecation notice

The Open vSwitch and Linux Bridge plug-ins are deprecated in the Havana release and will be removed in the Icehouse release. The features in these plug-ins are now part of the ML2 plug-in in the form of mechanism drivers.

Not all Networking plug-ins are compatible with all possible Compute drivers:

Table 7.4. Plug-in compatibility with Compute drivers
Plug-in Libvirt (KVM/QEMU) XenServer VMware Hyper-V Bare-metal
Big Switch / Floodlight Yes
Brocade Yes
Cisco Yes
Cloudbase Hyper-V Yes
Linux Bridge Yes
Mellanox Yes
Midonet Yes
ML2 Yes Yes
NEC OpenFlow Yes
Open vSwitch Yes
Plumgrid Yes Yes
Ryu Yes
VMware NSX Yes Yes Yes
Questions? Discuss on ask.openstack.org
Found an error? Report a bug against this page

loading table of contents...