Hi Ahmed, I see some of the questions also apply to non DC use cases so maybe we can structure the questions as follows: Do you use SDN? If No, what is the reason for not adopting SDN? (add Other to t

FYI in current release process, SM projects are not checked at all, they are responsible to deliver valid release based on the right version. BR/Luis

BTW tomorrow I have kids doctor appointment at 8AM, I should be done by 9AM, but if I am late Jamo can start with int/test Q&As. BR/Luis

Sodium SR4 common distribution is released here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.11.4/ Please proceed with post-rel

Hi Guillaume, Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run

FYI there are a bunch of CSIT jobs failing like this one: https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-1node-gate-flow-services-all-silicon/2/console The issue is reported here: htt

Hello everyone, Mg SR2 official release is available here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.12.2/ Please proceed wit

Not sure if this is tribal knowledge but every release I have to manually patch JJB for some misses: https://git.opendaylight.org/gerrit/c/releng/builder/+/87973 I have not checked yet the patch for t

Branching is not a problem, the real work is to update all the jenkins jobs after the branching. Some of them need special adjustments, not easy to automate today.

Yeah, I saw this INFO.yaml file in some thread, but has this 'new' process been properly explained to TSC and community in general? maybe I missed it. BR/Luis

As I said in this morning TSC, we have ODL interns helping moving content from old wiki to new wiki. If PTLs just fix the project landing page links to point to the right old wiki links, the interns c

FYI Sodium SR3 distribution is released here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.11.3/ Please proceed with the rest of

Netvirt is back in distribution: https://git.opendaylight.org/gerrit/c/integration/distribution/+/90040

If the patch builds, I would recommend to merge it so that we can re-add netvirt in distribution and run netvirt CSIT. As we discussed in yesterday's integration call, it will take a while to adjust e

Hello everyone, FYI since last week it is not possible to build a distribution because dependent artifacts have expired in Nexus. In order to restore the distribution build, as well as the CSIT, we ha

Thanks Andy and Thanh, the information you provided is sufficient for me at least. BR/Luis

I think the reporting part is well explained, My personal questions on Nexus IQ: - When I see a particular ODL project report, what does Nexus IQ analyze? all artifacts (jar, zip, tarball, etc) under

I think it is mostly user training (how to navigate things in the GUI, generate reports, etc) and some detail on what Nexus IQ currently checks: source code, jars, tarballs, etc. KKS or anyone, anythi

Hi Casey, KKS (and maybe others) has some questions on how to use Nexus IQ (get filtered reports, etc) as well as how Nexus IQ elaborates the reports (source code, binaries, distribution tarball, etc)

+1 for Somashekhar