Hi Andy, another favor regarding OVSDB, I will need to send following command to mininet: sudo ovs-vsctl set-manager ptcp:6640 But I realized, you only allow sudo for "mn", can you please add

Thanks Andy again for your quick response.

Sending to the VTN team as well. Per Anees' suggestion - will include Hideyuki-san and Yun-san in the Wednesday meeting invite. ----- Forwarded by Abhijit Kumbhare/San Jose/IBM on 11/25/2013 03:08 PM

Luis, you are the man buddy. We will get you more docs and functions in coming days sir. Thanks, -Brent From: Madhu Venugopal <mavenugo@...> Date: Monday, November 25, 2013 5:43 PM To: Luis Gomez

Excellent. Thanks Luis. Thanks, Madhu On 11/25/13, 1:02 PM, Luis Gomez wrote:

Luis, I've added it to the Jenkins shell script. I haven't run the job since, but I've already verified that the changes will take properly on the next run. -Andy- -- Andrew J Grimberg Systems

Hi Andy, We will need your “scripting” skills here. Do you think it would be possible to add the line bellow into the ${WORKSPACE}/opendaylight/configuration/config.ini file on the Jenkins

OK, thanks to the Postman examples I have the system test nailed down with the steps below: - Configure mininet in passive mode (sudo ovs-vsctl set-manager ptcp:6640) - Start mininet with

Hi Prasanna and all, Given this is the first time we join the call and the deep technical level of the discussion, I think it was kind of difficult (at least for me) to follow the entire

Hi Baohua and all, The code is not in the repo because nobody has merged it yet. I believe this is because maybe it is not clear how to merge code so I will explain to everybody: If you open the

Hi folks in integration group, and anyone knows about the formal release: Excuse me. Just would like to let you know that SNMP4SDN haven’t provide the artifacts to ServiceProvider. Apologies for

hi,luis. Not found your code in the repo, so I tried all cases in the repo's tool directory, there's no failure found. So I guess there's something wrong in the environment setup? Could

Hi Luis, Exactly. The correct solution is to identify the appropriate Controller-ip-address to set based on the reachability information towards the switch via OVSDB. And as Brent

Hi Brent, Thanks for your quick answer. I will try the examples from Postman and let you know. For the question about which controller IP should be configured in the OVS bridge, I still think

Hi all, The release deliverable of VTN Project consists of VTN Manager and VTN Coordinator. The current artifacts for the Virtualization Edition, however, have not included VTN Coordinator

Hi Luis, Thanks so much for the feedback, this is really awesome! I threw in some thoughts, Im sure the others have additional input due to their better knowledge of the core controller but here are

Hi Baohua, See all the failures I get after re-running the suite when container manager file in included: [odluser@odl-test-tools ~]$ pybot -v CONTROLLER:10.125.136.52 -v MININET:10.125.136.53

Hi folks, Just started writing system test plan for OVSDB and I found one issue, one possible improvement and one general question. 1) Lets starts with the issue: with a controller with 2 IP

Also, can you or anyone else review and merge the code? Thanks/Luis On Nov 22, 2013, at 11:06 PM, "Baohua Yang" <yangbaohua@...> wrote:

I thought the same but when I run the suite again, it fails in different cases. Let me do another test in the lab and send you the results. On Nov 22, 2013, at 11:06 PM, "Baohua Yang" <yangbaohua@...>