Re: ODL Inventory

Sam Hague


the OVSDB southbound plugin [1] will populate the topology with the ovsdb node information, including the bridges and ports. With devstack as part of the local.conf config the ODL address is specified. In the final steps of the the OVSDB Manager entry is set to that address and the OVSDB nodes will connect to ODL. The OVSDB southbound plugin will see that connection and begin to populate the MDSAL operational datastore - stores the node, the bridge, the ports as termination points.

From there the netvirt [2] application listens for the operational updates. netvirt also listens on the neutron events coming from the northbound side. With these two sets of events netvirt will satisfy the neutron requests.

The openflow nodes inventory is populated via the openflowplugin. When the OVSDB nodes connect and netvirt sees that it will create the required bridges, i.e, br-int, and then set the Controller address. Those bridges will then connect to ODL openflowplugin port and openflowplugin will add the switches to the inventory.

So you just need the odl-ovsdb-southbound-impl or odl-ovsdb-southbound-impl-ui feature to get the southbound plugin which will get the inventory for you.

Thanks, Sam

[1] ovsdb/southbound/southbound-impl
[2] ovsdb/openstack

----- Original Message -----
From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: ovsdb-dev@...
Sent: Thursday, June 25, 2015 12:15:05 PM
Subject: [ovsdb-dev] ODL Inventory


I can’t figure out how OVSDB populate ODL Inventory based on openstack (i.e.
specifically after ./ is complete). Also, is there a feature I can
include in my project to do that.

Thanks much.


ovsdb-dev mailing list

Join to automatically receive all group messages.