This group is locked. No changes can be made to the group while it is locked.
Re: ODL Inventory
Khaldoon Al Zoubi <khaldoon.alzoubi@...>
Thanks Sam. Actually, this what I thought I need to do (only include odl-ovsdb-southbound-impl in my features.xml), but I am not sure what part I am missing. I believe the devstack & ODL connection works since I am able to see neutron elements in datastore when executing commands like (neutron net-create net-1). So feature odl-neutron-service works.toggle quoted messageShow quoted text
However, when I am running ODL purely from the OVSDB project it works and I can see the operational nodes. So, I am missing something in my project.
Thanks Sam as always.
From: Sam Hague [mailto:shague@...]
Sent: Thursday, June 25, 2015 2:41 PM
To: Khaldoon Al Zoubi
Subject: Re: [ovsdb-dev] ODL Inventory
the OVSDB southbound plugin  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 stack.sh 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  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.
----- Original Message -----
From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>