Ask Your Question
1

Does Neutron assume a default plugin or networking implementation?

asked 2017-04-19 06:20:26 -0600

PK gravatar image

updated 2017-04-20 04:22:39 -0600

I'm trying to figure out if OpenStack Neutron has a "default" networking implementation / plugin? Is ML2 + OVS or something else considered a default implementation for the network? Or are all possible core plugins equal?

To put it differently, is it correct to state that Neutron only defines the networking API, and particular implementation is up to plugin, and not fixed (can be arbitrary)?

Maybe that will sound like simple questions, but I am unable to find explicit statements on that in the docs. If it is documented please give a reference.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2017-04-20 04:42:07 -0600

Bernd Bausch gravatar image

Neutron is indeed a framework for managing virtual networks. How those virtual networks are implemented by the underlying infrastructure is determined by plugins, for example the core plugin for the core resources network, subnet and port, the L3 plugin for routers, the DHCP plugin for (you guessed it!) etc.

Neutron contains its own reference plugins. The reference for the core plugin is ML2, and the two reference mechanism drivers are LinuxBridge and OVS.

As far as I understand the meaning of "default", it means "will be used if nothing else is configured". If you don't configure a core plugin, Neutron won't work (I guess the neutron server would issue an error message and stop), so that in my mind, ML2 can't be considered "default". But perhaps that's just a semantic game.

edit flag offensive delete link more

Comments

Thank you for this brilliant explanation. One question - is the term "reference plugin" official? Or does this just mean plugins that are developed in the main repository?

PK gravatar imagePK ( 2017-04-20 05:12:46 -0600 )edit

In Cinder, the term "reference driver" is used for drivers developed by the Cinder team. Since "plugin"is the equivalent of "driver", I just stole that idea. I don't know if it is used as a official term, but it describes the concept.

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-21 06:57:04 -0600 )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

Stats

Asked: 2017-04-19 06:20:26 -0600

Seen: 38 times

Last updated: Apr 20