Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

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.

Details: 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 Many more to come... Heterogeneous deployments Specialized hypervisor nodes with distinct network mechanisms Integrate *aaS appliances 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.

Thanks,

Shankar Ganesh.P.J

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.

Details:

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

ML2 introduces several innovations to achieve its goals: goals:

Cleanly separates management of network types from the mechanisms for accessing those networks networks

Makes types and mechanisms pluggable via drivers drivers

Allows multiple mechanism drivers to access same network simultaneously simultaneously

Optional features packaged as mechanism drivers drivers

Supports multi-segment networks

Flexible port binding binding

L3 router extension integrated as a service plugin

Replace existing monolithic plugins plugins

Eliminate redundant code code

Reduce development & maintenance effort effort

New features features

Top-of-Rack switch control control

Avoid tunnel flooding via L2 population Many more to come... population

Heterogeneous deployments deployments

Specialized hypervisor nodes with distinct network mechanisms mechanisms

Integrate *aaS appliances appliances

Roll new technologies into existing deployments

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

Much less code to write (or clone) and maintain maintain

New neutron features supported as they are added added

Support for heterogeneous deployments deployments

Vendors integrating new plugins should consider an ML2 Driver instead instead

Existing plugins may want to migrate to ML2 as well.

Thanks,

Shankar Ganesh.P.J

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.

Details:

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 networks,Makes types and mechanisms pluggable via drivers

drivers, Allows multiple mechanism drivers to access same network simultaneouslysimultaneously.

Optional features packaged as mechanism drivers

Supports multi-segment networks

networks, Flexible port binding

binding, L3 router extension integrated as a service plugin

plugin, Replace existing monolithic plugins

plugins, Eliminate redundant code

code & Reduce development & maintenance efforteffort.

New featuresfeatures:

Top-of-Rack switch control

control, Avoid tunnel flooding via L2 population

population, Heterogeneous deployments

deployments, Specialized hypervisor nodes with distinct network mechanisms

mechanisms, Integrate *aaS appliances

appliances and Roll new technologies into existing deploymentsdeployments.

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.

Thanks,

Shankar Ganesh.P.J