Hi folks, I’m finished with part 1 of the pipeline description used in ovsdb’s net-virt: http://www.flaviof.com/blog/work/how-to-odl-with-openstack-part1.html if you can please, take a peek and

What was the solution for the cases where ODL connects to the ovsdb nodes? In that case odl only has the ip:port of the node to make the outgoing connection. The idea in this thread is to use the

Just to address the question from following mail. The way you specify the columns to select operation is you call setColumn(..) on a select. Example: Select<GenericTableSchema> bridgeSelect =

This can be done in OvsdbNodeCreateCommand. The issue I see there is changing the signature of the OvsdbNodeCreateCommand’s constructor. Let me know if its ok to change the signature and pass

And why change ConnectionInfo (that really really is info about the ip and port...) Ed

Prateek, Question... why not in the OvsdbNodeCreateCommand where all of the other operational info is being created and written? Ed

Hi Ed, The way I am implementing this is: In OvsdbConnectionManager’s connected method, I’ll set system-Id from external_ids of open_Vswitch table in ConnectionInfo key (I’ll modify yang to add

Hi Ed, I do not know the protocol, does the OVSDB send all the data to the manager once you set the manager in the OVS? @ what point do we create the ovsdb id for the

Sharon, That UUID should already be there with whatever OpenVSwitch object we have... no need to ask for it again... Ed

I'm guessing we need the uuid of the OVS to start and create the Operational State. ________________________________________ Sent: Wednesday, April 22, 2015 2:58 PM To: Prateek Garg (prategar) Cc:

Prateek, Why are you doing a select? (curious) :) Ed

Hi, While implementing this use case I need some help using the select operation of ovsdb library. I am trying to read the Open_vSwitch table to get the data in external-ids. I am doing the

Hi Sam, Could you provide me a link for item #4, I don't see an ovsdb csit from here https://jenkins.opendaylight.org/releng/view/CSIT-1node/ Thanks, George

1) API freeze achieved. (All externally accessible APIs [Stable and Provisional] may not be modified.) Yes/No. Yes 2) Document word counts for each documents: (Please provide word counts for ascii

Hello, Please submit M4 status for OVSDB. The M4 template: https://lists.opendaylight.org/pipermail/release/2015-March/001669.html Thanks, George

The config/operational synch is best handled a little differently. When you try to config an ovsdb-node to connect... you don't *really* know the systemid... just the IP:port. The way we solved this

Hi, In my opinion, the we can replace the node-id of the ovsdb node in md-sal to contain system_id from external properties. This would make sure that the config and operation store are in synch in

Hello guys, No matter how hard I try (have multiple port/interfaces on OVS Bridge, have disconnected/connected manager), the Node TerminationPoint list remains empty and also the

Hi, We are working on establishing a VXLAN tunnel between two OVS and we are not sure if Helium SR3 supports this kind of feature by setting up through the RESTCONF API. Could you give us some

Hi ovsdb dev team, I observed that OvsdbPortUpdateCommand checks updated rows of ports only. However it misses on further updates of Interfaces. So some attributesdo not end up in the operational