https://git.opendaylight.org/gerrit/#/c/74966/51..52 should address this, I think. Regards, Robert

This looks like a mismatch after upgrade, I'll check it out later today. Regards, Robert

Since the list is empty, it disappears, I think a 404 is is appropriate here. Regards, Robert

For netconf, I see 2 problems: 1) Issue installing the call home bundle: 2018-10-19T11:30:44,285 | ERROR | Blueprint Extender: 2 | NetconfCallHomeServer | 279 -

I quickly checked OFP and the issue is that before the patch the operational inventory used to return {"nodes":{}} when no OF nodes are connect and after the patch it returns

Looked through a few. Created two groups below: 1. good to merge, 2. not good to merge. Looks about 50/50 where things stand. 1. good: aaa: same failing suite, so ignore coe: same failing suite, so

Yes, the cloudbees folders plugin is working like you suggested - you can add jobs via list or a regex - but it does not recognize any existing jobs at the root level. I will keep playing and try to

Hi, There is currently a series of CSITs running with the Neon MRI on https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/92 So far there are lots of

I think JJB only supports Folders at the moment. I'm not entirely sure about the other plugins and Folders seem to be what cloudbees is pushing. If we want to investigate the other 4 plugins then we

Sorry, I had to take the kid to dentist and forgot about the new time… I will join for sure next week.

Done. One resulting patch needs review: https://git.opendaylight.org/gerrit/#/c/77096/ Thanks, Daniel

As discussed on the Integration call, I wrote docs for this: https://git.opendaylight.org/gerrit/77095 Let me know what you think. Daniel

Thanh, is there a possibility we could use one of the plugins below to get nested views? [1] looks like a good option with current support. It says the basic setup is free. [3] might be useable

https://meetings.opendaylight.org/opendaylight-integration/2018/integration/opendaylight-integration-integration.2018-10-18-21.00.html

Hi Documentation Committers, Please kindly review the following patches and merge if you agree: https://git.opendaylight.org/gerrit/#/c/75959/ Please kindly review the following patches and

+1 This would also be a nice addition to the stick/carrots - projects who are able to live up to the requirements of the MR would get a very significant extra benefit, and failing to do so would be a

I would propose that in Sodium, we only support one release: Managed Distribution/RPM/Debs. Self-Managed projects would be responsible for generating their own distribution, as well as packaging

In the spirit of common contributions to Managed projects, I might could do this level of split. It would be a huge TODO though. Just to maintain, maybe .1-.2 FTE. That's the thing, it's not

Agreed, but I think we will at some point arrive at two releases: Platform and Managed Apps... How difficult it to maintain that? How much of the current work is really project-specific? Can we just

Reviving a very old thread, thinking we should start discussing on today's integration call. Also, from an Int/Pack perspective, two thoughts: * It was a mess to have "two" Fluorine releases (Managed,