If the data is not yet collected in ES, I think we have to contact bitergia and ask how to do this. AFAIR it should be possible but we have to be careful not to override reserved indexes in ES.

AFAIR, there were special credentials to create custom dashboards in bitergia, is this what we are looking for? if so Casey can provide those.

Hi bgpcep devs, FYI performance regression has been detected here: https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-1node-bgp-ingest-all-neon/ And logged in this bug: https://jira.o

The blocker bug I was talking in the TSC call: https://jira.opendaylight.org/browse/CONTROLLER-1906 BR/Luis

Hi OFP devs, FYI a regression has been detected recently in stable/neon branch, see details in this ticket: https://jira.opendaylight.org/browse/OPNFLWPLUG-1074 BR/Luis

OK, nobody answered, I think we can cancel today’s meeting.

Hi int devs, Should we have integration call today? Jamo is still out but since we did not have call last week, maybe we should hold it or drop it if we do not have topics. Thoughts? BR/Luis

Hi Anubhav, We have already selected the interns for the projects of this OpenDaylight internship. Thanks for the interest and remember we are opening new projects every ~6 months. BR/Luis

OK, let me send mail to the SM projects. BTW I missed the last TSC call: was there any decision to create a Fluorine SR4 and if so by when?

Hi Emmett, Before going deep in your logs, have you made sure your controller runs all the features requires by the test, for example this test [1] uses odl-jolokia,odl-restconf, odl-clustering-test-a

+1

I am fine to release as it is, we can maybe add a comment in the release notes mentioning the BC 1.61 perf issue and the impact in karaf console SSH. BR/Luis

As I mentioned earlier, there has been some change in karaf fluorine so that now the first time you connect to the console via SSH (ssh -p 8101 karaf@...) can take more than 10 secs. This produc

Just to be clear, it is not 3.2 we are asking, it is >=3.1. Robot 3.1.X is perfectly valid and compatible with both formats. BR/Luis

Hi everybody, We have found some problem with robot version update: 1) Starting robot 3.1, there is a new syntax for FOR loops: *** Test Cases *** Example FOR ${element} IN @{ELEMENTS} Start Element $

I think we have to wait for next AR build and then ask Anil to create the spreadsheet for the new build as usual: https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-fluor

OK, just opened the ticket here: https://jira.opendaylight.org/browse/CONTROLLER-1900

Around 50 and now we get less than 5 so we are talking about 1 magnitude perf regression. The test itself does: 1) Start a singleton registration flap on every controller instance with this RPC: /rest

Looks like Karaf issue is gone: https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-3node-clustering-perf-bulkomatic-only-fluorine/ Maybe it was a temporary infra problem.

AFAIR the reason for using ubuntu docker was to run netopeer devices. I am not sure the same will work with centos docker but we can always try.