Ask Your Question

Why switching to ML2 while we had ovsplugin for neutron?

asked 2014-05-08 22:40:17 -0500

raghavendra gravatar image

The Icehouse version uses the ML2 plugin and looks like slowly deprecating ovs plugin in the coming versions. May I know why we are switching to ML2 while OVS(Open V Switch) plugins where used in neutron versions of Grizzly and Havana? I would request some details and adavantages listed.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-05-09 03:39:59 -0500

SGPJ gravatar image

updated 2014-05-09 03:47:33 -0500

In NutShell: Consider a use case, If you like to integrate a SDN with Neutron then with earlier model only one controller plugin can speak with neutron. Also you have each vendor giving they own neutron plugin. But with introduction of ML2 you can have multiple vendor controller speaking with neutron and easy to manage.


ML2 is functionally a superset of the monolithic openvswitch, linuxbridge, and hyperv plugins.

ML2 introduces several innovations to achieve its goals:

Cleanly separates management of network types from the mechanisms for accessing those networks,Makes types and mechanisms pluggable via drivers, Allows multiple mechanism drivers to access same network simultaneously.

Optional features packaged as mechanism drivers

Supports multi-segment networks, Flexible port binding, L3 router extension integrated as a service plugin, Replace existing monolithic plugins, Eliminate redundant code & Reduce development & maintenance effort.

New features:

Top-of-Rack switch control, Avoid tunnel flooding via L2 population, Heterogeneous deployments, Specialized hypervisor nodes with distinct network mechanisms, Integrate *aaS appliances and Roll new technologies into existing deployments.

Advantages of writing an ML2 Driver instead of a new monolithic plugin:

Much less code to write (or clone) and maintain

New neutron features supported as they are added

Support for heterogeneous deployments

Vendors integrating new plugins should consider an ML2 Driver instead

Existing plugins may want to migrate to ML2 as well.


Shankar Ganesh.P.J

edit flag offensive delete link more


Thank you Shankar Ganesh. It is very helpful.

raghavendra gravatar imageraghavendra ( 2014-05-15 06:40:16 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-05-08 22:40:17 -0500

Seen: 234 times

Last updated: May 09 '14