# how does ml2 work specifically?

I'm trying to understand how the ml2 works. I'm kinda new to openstack. I was reading/watching these:

Let's say we have 1 Network node, and 2 compute nodes. compute-1 node is running OVS and compute-2 linuxbridge.

From what I understand:

User instantiates a VM.
Nova finds the right compute host, let\'s say the one with the OVS (compute-1), and instructs Neutron-server accordingly.
Now, from what I understand, Neutron server has an ML2 plugin.
This plugin has to instruct the Neutron agent running on the compute host.
The Neutron agent is the one that generates the openflow/ovsdb rules on the compute host.
So the ML2 plugin on the Neutron-server is using a Mechanism driver. If it communicates with compute-1, it uses the openvswitch MechDriver.


Does this mean that the MechDriver is only relevant on a network node? The reason I ask is that I think I saw it was used on the compute host as well in the conf file. Or I did not understand anything, and the Mechdriver is relevant to the Neutron agent and not to the server??

edit retag close merge delete

Sort by » oldest newest most voted

Thanks, but I still don't undestand the answers to the questions that I asked. I have already read those posts, and many others. My question is simply to understand the flow of who against whom and where. So I will phrase it as questions:

Let's say I set up a simple openstack with 1 network node and 2 computes. I understand that the neutron service (API) is running on the network node. Now, say I add a simple tenant network, with some subnet. Neutron service (API) is notified that I would like to create such network, and Neutron talks to ML2 plugin. 1. Does ML2 talk directly to the mechanism driver? 2. Does that mean that the mechanism driver code is only relevant for the network node? 3. Who calls the neutron agent on the network node and on the compute node? Neutron service? Neutron ML2 plugin? Neutron ML2 mechanism driver? 4. Is the whole purpose of the agent to set rules in the vSwitch and set up ports locally? 5. Does the neutron agent ever initiate something, or only does as it is told? 6. Does it always act locally (i.e. changes things only on the server it's running on)?

more

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).

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.

more

Regarding you major concern see
http://aqorn.com/understanding-openst...
Take a look also at this old link https://www.rdoproject.org/networking...
Neutron Server is actually Neutron API Server to provide ML2 features to it's ovs agent running on Compute,
it should be first updated itself ( in old times) . In meantime Neutron Server comes ready to provide ML2 aware
API for neutron-openvswitch-agent

more