Reinaldo, I figured out my problem just now. That is because of incorrect port mentioned in 04-libnetconfd.xml. As I installed netopeer using docker and it uses port 1831:830 for talking to netconf

I will test again later today and get back to you. In the meantime, can you test something simple? Change header to <Accept: application/xml> and perform GET again. I seem to remember an issue around

Thanks Luis. Please revert just the OVSDB bundle versions. FYI, we are currently re-architecting the code in a different branch topic/schema and we have bumped up the versions. The

Hi All, I’m not sure if this is normal but it seem to look odd to me. When I use the restconf to put the f1.xml flow to the controller the flows looks fine on the OVS switch. But when I try to

OK Madhu, I can take care of these changes. I am almost sure I had to commit this automatic patch from jenkins because the editions build was failing. Anyway, I will do according to your

This is the exact error I get in OSGi command line: 2014-04-01 15:49:21.307 PDT [pool-34-thread-1] ERROR o.o.c.s.c.n.NetconfDevice#libnetconfd - Netconf client NOT started.

Thanks Reinaldo. I installed docker image mentioned at https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Docker_image and I am able to see the response sent by server

Hi Luis, Thats because of this : commit 9ad9918a8144e5a5ea83ed85f5a81e3d3cfcbca9 Author: jenkins-integration <jekins-integration@...> Date: Tue Apr 1 16:00:34 2014

Hi Madhu, Still fails, please check the latest OSGi console when base edition starts and also when we try to create bridge through BD API:

Hi, If all you want to do is look at CPU usage for the app then you can connect to it using jconsole which ships with the jdk. To use console do the following, 1. Start controller with the -jmx switch

FYI, they use YourKit to plot the CPU graphs, does anybody in Integration have experience with this tool? Begin forwarded message: From: Anil Vishnoi <vishnoianil@...> Subject: Re:

Brian, The IP addresses are reversed. Sorry about that. -Moiz From: FREEMAN, BRIAN D [bf1936@...] Sent: Tuesday, April 01, 2014 4:27 AM To: Moiz Raja (moraja); Lakshman Mukkamalla (lmukkama) Subject:

Hi Luis, Unless you are using an older version of OVS in your testbed, this IPFIX change should not impact you. But, I realized that our new topic branch could have caused this issue. We have a

Thanks Madhu ;)

Hi Luis, We modified the code to include IPFIX. Not sure if that is causing this issue. I will look into it and get back to you. Thanks, -Madhu

Hi Devs, Since today we have problems in the base edition system test like it is not possible to create a bridge using Bridge Domain API. Have you changed anything that could impact this

Fwding to Integration group. Begin forwarded message:

Punal, I think running on the same VM would work but only if it was multi-homed. In the configuration for exabgp we have to specify the IP address of the peer. If the peer IP is the same as what I am

Hi Moiz, I followed your steps to create single bgp peer but was unable to establish bgp session. Do we need two seperate vm's to create bgp session? Here is the log after executing "exabgp

Andy, I'll get it working with virtualenv and let you know if we can go with that option. -Moiz ________________________________________ Sent: Monday, March 31, 2014 2:34 PM To: Moiz Raja