Ask Your Question

Revision history [back]

Neutron OVS agent is building configuration provided by in openvswitch_agent.ini at it's start-up
I also believe that OVS agent is responsible for Neutron/OVS work flow on Network and Compute Nodes via talking to Neutron Server , running on Controller ( along with Nova API Server).
See details here:- https://ask.openstack.org/en/question/10987/why-nova-computes-interacts-with-neutron-server/
See also :- http://abregman.com/2016/01/04/openstack-neutron-introduction/
Per link above

Openvswitch L2 agent configured to work with OVS, using ovsdb. 
In general L2 agent runs on hypervisor and and communicates with neutron server using RPC. Normally will be installed on the network and compute nodes. Its main job is to watch and notify when devices added or removed and to configure the network on the host accordingly.  It can handle linux bridges, OVS and  security group rules.

Neutron OVS agent is building configuration provided by in openvswitch_agent.ini at it's start-up
I also believe that OVS agent is responsible for Neutron/OVS work flow on Network and Compute Nodes via talking to Neutron Server , running on Controller ( along with Nova API Server).
See details here:- https://ask.openstack.org/en/question/10987/why-nova-computes-interacts-with-neutron-server/
See also :- http://abregman.com/2016/01/04/openstack-neutron-introduction/
Per link above

Openvswitch L2 agent configured to work with OVS, using ovsdb. 
In general L2 agent runs on hypervisor and and communicates with neutron server using RPC. Normally will be installed on the network and compute nodes. Its main job is to watch and notify when devices added or removed and to configure the network on the host accordingly.  It can handle linux bridges, OVS and  security group rules.

Next

One common example for its usage would be new created vm with single nic that must be connected to some network. The actual connection is done by L2 agent that makes sure it connected to the right network. It also handles  OVS flows, Linux bridges, VLAN tagging and security groups.

Neutron OVS agent is building configuration provided by in openvswitch_agent.ini at it's start-up
I also believe that OVS agent is responsible for Neutron/OVS work flow on Network and Compute Nodes via talking to Neutron Server , running on Controller ( along with Nova API Server).
See details here:- https://ask.openstack.org/en/question/10987/why-nova-computes-interacts-with-neutron-server/
See also :- http://abregman.com/2016/01/04/openstack-neutron-introduction/
Per link above

Openvswitch L2 agent configured to work with OVS, using ovsdb. 
An example for modular plugin would be the popular ML2 which implements v2 API. It delegates the calls to the different drivers. There are mechanism drivers and type drivers. Types are types of segmentation like VLAN, gre, vxlan. Mechanism drivers suppose to ensure that the type driver properly applied given the specific networking mechanisms that have been enabled.

Next

In general L2 agent runs on hypervisor and and communicates with neutron server using RPC. Normally will be installed on the network and compute nodes. Its main job is to watch and notify when devices added or removed and to configure the network on the host accordingly.  It can handle linux bridges, OVS and  security group rules.
 Openvswitch L2 agent configured to work with OVS, using ovsdb.

Next

One common example for its usage would be new created vm with single nic that must be connected to some network. The actual connection is done by L2 agent that makes sure it connected to the right network. It also handles  OVS flows, Linux bridges, VLAN tagging and security groups.