Hi Andy, Following our conversation this morning, I checked and all the robot jobs point to mininet slave 1, VTN coord deploy job for Hydrogen (old deploy job) uses mininet slave 2 (because it was fre

Hi all, Sorry for the delay. Here is M2 status for Integration: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Helium_Release_Plan#Release_Milestones BR/Luis

Hi Rocky, Just couple of comments: 1) I saw some projects like OSCP or Affinity although they do not participate in Helium. I believe the list of projects for Helium is in this wiki: https://wiki.open

Also regarding making OF13 plugin default in ODL, this is a change in master that does not apply to stable branch right? BR/Luis

Thanks Abhijit, FYI, I am preparing a few jenkins jobs to verify the swap. I will be able to report the outcome on next Monday call. BR/Luis

Just changed name to integration-master-verify-distributions for master branch or integration-hydrogen-verify-distributions for stable/hydrogen branch. I will send a mail for this and other changes I

Hi all, As part of our ongoing integration reorganization, most of our Jenkins jobs have been renamed today: https://jenkins.opendaylight.org/integration/view/All/ The most important are the new editi

Hi Rocky, thanks for the update. Gauges are nice and I also like the idea of plotting a dependency map based on project dependency declaration. BR/Luis

Hi, Integration Robot VM is down. Could you please take a look? Thanks/Luis

Thanks Andy, Please take your time, I have other things to do anyway and devs are quiet so far. Just a comment: I have been checking and we have 24 robot jobs x 40 stored build reports = 960 robot tes

Hi all, As a result of yesterday test tasks discussion we have created following groups with the goal to work and deliver something by next milestone M3 (07/07/2014): 1) Infrastructure: 1.1) Testopia

I see this issue when I enable and fire the job: https://jenkins.opendaylight.org/integration/view/Deploy%20Jobs/job/integration-master-deploy-vtn-coordinator-latest/125/console BR/Luis

That worked but next issue here: https://jenkins.opendaylight.org/integration/job/integration-master-deploy-vtn-coordinator-latest/126/console BR/Luis

Thanks Andy, it works now. BR/Luis

I think so, I checked and VTN coordinator in master runs on port 8083 so the test files you uploaded should be OK. However the VTN coordinator in stable/branch runs on port 8080 so the test file you u

OK, I fixed the stable branch issue with this patch: https://git.opendaylight.org/gerrit/#/c/8130/ Now you have VTN coordinator test running on both branches. BR/Luis

OK, CPqD is now in LF both mininet VMs so I will move this task to done. BR/Luis

Hi all, I started running the existing Robot suites we have for VTN Mgr and VTN Coord with controller -of13 option and I see problems in both: - VTN Mgr: The ping test to verify connectivity after VTN

Hi LF people, It is being a while (back in February) I detected an issue in LF Integration Lab when performing the “classic” ping test. The issue is mininet ping test (h1 ping h4 or pingall) does not

Hi all, It looks like we have a big regression in the OF13 flowmod test: https://jenkins.opendaylight.org/integration/job/integration-master-csit-base-of13/1658/robot/report/log.html From the time we