Hi, Script url: https://git.opendaylight.org/gerrit/#/c/74743/ After commit, the Jenkins-releng is failing with below

Hi, According to your saying, there are few points I don't understand. I choose to use ODL zip. So I need to achieve: 1. Execute "mvn clean install" in projects successfully. 2. As a result of 1,

Do you need separate RPMs per module? Or can you just built a typical ODL zip and use that? If the latter, then you can just keep your branches per projects, along with patches and just build a

Hi, I build my own distribution of ODL as RPM package for deployment. The situation goes like: 1. Build my own sub-module for HWvTEP L3 support under netvirt. 2. Re-modified topology-manager under

Hi Luis, Yes, if nothing is changed in the config to be pushed, then the existing thing won't be affected. To delete a dashboard or a visualization, I think we should do that manually. Otherwise, we

For dealing with private messages from unregisterred users, til we can set `/mode yournick +R`. Thanks, Anil

Why don't we use the corresponding test-tool for each release? I mean NETCONF-504 is fixed so there is no need to use Nitrogen-SR3 (or Oxygen-SR2) test-tool for all releases. We should use Oxygen

All, Apologies for taking longer than I expected to get through back-from-vacation tasks!! Here’s a quick summary of the items we discussed: The location of models and internal directory is pretty

+1 on having registered users joining channels. However, most private message spam is still being sent. Not sure if there is anyway to deal with that. Thanks, Anil

merged.

https://git.opendaylight.org/gerrit/74821 bumps the testtool to Oxygen SR2 (1.4.2). Bye, Robert

Hi Dibya, see my answers below: please do fyi, when we were looking at this in the past we decided to use single ES index for all that is test data and call it: opendaylight-test. After that apply

https://meetings.opendaylight.org/opendaylight-integration/2018/integration/opendaylight-integration-integration.2018-08-02-17.14.html

Hey... sorry... the TSC is just before this meeting and most of us hang on to that until it's done and then join the integration meeting. JamO

This idea came from Sam on IRC. The problem with __init__.robot is that you can't do the teardown that way, AND you have to call pybot on folders, not specific suites. JamO

That's to be expected and we'll be there to assist them if they need help. We have a topic and entry message to provides details on how to get registered and why they were redirected. Regards, Thanh

I've not noticed any spam (on ODL IRC channels), but if you think this is Good Idea, then go for it... I don't know what percentage of current IRC users have registered - you'll at least initially

Isn't this a bit complicated? I remember previously we used to have an _init.py file where we used to have common start suite and stop suite. Is that not available right now? Thanks, Faseela

Nope, aside from my client not playing nice -- it seems to join before performing registration :) Regards, Robert

Hi Luis, I noticed that the build number ordering is incorrect. It detects the test-run as a keyword. It's a minor fix and I will send the patch soon. The other thing is, index pattern. There are two