I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines? -- Thanks Anil

Hi ovsdb devs, We have question regarding ovsdb node-id: - When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644”

Hi Ed, Thanks for the inputsJ. Yes as per the pcap and the logs the request is reaching the Opendaylight. The default security groups which needs to be associated with the port when a vm is

Flavio helped me on IRC. To use bridge with different name than br-ex change in code is required: https://git.opendaylight.org/gerrit/#/c/22991/ Regards, Michal 2015-06-19 12:51 GMT+02:00 Michał

Hello everyone, I think that I have a problem which was described in this issue https://bugs.opendaylight.org/show_bug.cgi?id=1147 I'm trying to add opendaylight to existing openstack env, but when I

AAA, ALTO, DIDM, L2switch, NIC, Opflex, OVSDB, PCMM, Persistence, Reservation, SNBI, USC Project Leads: Your project still haven’t report RC1 test status, please do so. Please note TSC

Yes, I can see the br-int configuration in config data store before disconnect controller from the ovs node. I am removing the ovsdb node from config data store.

Chaudhry, do you see br-int bridge configuration in config data store before you disconnect the ovs from controller? How are you disconnecting the ovs from controller? by removing ovsdb node config

Sure Luis, i will add this test case later today. Sure Edward, I will file the bug

Hi Ravi, Sorry for not answering before, 2 things: 1) Can you make tomorrow’s Thursday integration call at 8AM PST details here [1]? This way you can check all open fronts we have in integration

Hi Luis, Can you send me some details on what are those CI Jenkins jobs we can start looking into and what feature requires additional automated test cases. I am going through the configuration

Chaudhry please leave a test case failing so that we know when the bug get fixed :)

My gut feeling is that if you are only deleting the connection, only the connection should be deleted from the config subsystem... and then if you create the connection again, on reconnect we should

What about step 1) it seems the first time you connect the ovsdb plugin programs the switch in config datastore...

Thanks Vishnoi. On what parameter does it makes this decision whether to initiate the create "br-int" request ? Checking the operational datastore or whether the bridge as entity connected to the

Only the connection to the OVSDB node has been deleted

There might be a subtlety here... was it just the connection that was deleted? Or also the accompanying configuration of bridges using that connection? Ed

​​ As per my understanding this is expected behavior. Config data store is meant for user configuration and operational data store is to reflect the operational state of the connected node. So in

Hi All, While playing with opendaylight controller with karaf feature installed ( odl-ovdb-openstack) observe few things. Need clarification on that. 1) If a clean OVS is connected with the