Re: [controller-dev] ovs related queries: ofport_request purpose and range
Venkata Siva Vijayendra Bhamidipati
Picking this up from yesterday.. Yes, it sounds like Connection Manager is what I will need to look into – I wanted to know where the port info that is pushed by the ovs is received by the ODL controller and stored (I’ve not even cloned the ovsdb directory btw, so I’m guessing the ovsdb plugin isn’t kicking in at all, and I don’t see any ovs* files in the plugins directory either, so this must be all open flow, right?) – I infer that the switch manager then picks that info up – I’ll now continue looking into it and ping back in case I have any questions.. Thanks a lot for the pointers!
From: Madhu Venguopal <mavenugo@...>
Date: Wednesday, January 15, 2014 at 6:26 PM
To: "Bhamidipati, Vijay" <vbhamidipati@...>, "controller-dev@..." <controller-dev@...>, "ovsdb-dev@..." <ovsdb-dev@...>
Subject: Re: [controller-dev] ovs related queries: ofport_request purpose and range
Sorry, I dont quite get your question.
getNodesLearnt() gets the info from SwitchManager which maintains the Switch/Node properties.
and we can obtain the info from there.
There is also Connection Manager maintains all the Connection information and it gets that info from the southbound plugins
(Openflow, OVSDB, etc...) when a node gets connected to the controller. Is that what you are looking for ?
On 1/15/14, 4:55 PM, ebaysf, vbhamidipati wrote: