Hi all and thanks a lot for proposing help The first 2 issues are easy to understand and quite simple to reproduce. Since oxygen, we do not see anymore the “controller-config” node automatically conne

Thanks for confirming the complete removal of the controller-config mountpoint. We will remove that from our test bench. Since it was still mentioned in the oxygen and fluorine netconf user guides, I

Hi all Ariel, thanks for the proposal. Unfortunately, I am off for a few days for family reasons. If needed, I will let ATT be my proxy on that discussion today at the TSC. Today the blocking point fo

Hi Jakub, thanks a lot for the explanation. This is coherent with my observation when investigating the problem and also explains, at least partially, the last issue we had. I confirm it works well wh

Hi all Ariel, I am back at the office since yesterday. I've published our release plan details on jira https://jira.opendaylight.org/projects/TSC/issues/TSC-152 today I looked at Luis last week email

Hi I just take a look at your slide. About your question for the placement of TransportPCE, it can be considered as a network service or application. Note that TransportPCE embeds several component an

Hello All Ariel, I’d be happy to participate those meetings. BR Guillaume

Hi all +1 for Robert Jenkins automated jobs have been now for a week almost useless because of time out. An example among others if so needed: https://git.opendaylight.org/gerrit/#/c/78049/ Thanks in

Hello The result of the poll are Shweta Vachhani: +5 Gilles Thouenon : +5 We have already the quorum to promote Gilles and Shweta committers for transportpce. Congratulations to Gilles and Shweta ! No

Hello Along Shweta and Gilles promotion process, you can see in the email archives URL below that Xavier and Johan asked to step down from the transportpce project committers list (for inactivity reas

Thanks for the clarification Thanh, I will raise that point at our next meeting. PS: I remember Cédric had some difficulties when he tried to migrate because he had already a valid LFID.

Hi all Is there any update on this topic since those last emails? I’ve taken a look at the last TSC minutes and haven’t found anything. If the next DDF has to be collocated with the ONS NA, preferably

Thank you both for this feedback. As far as I am concerned, I see a potential interest in a cross-event with ONAP , OPNFV or FD.io communities. The collocated event ONAP DDF + OPNFV plugfest was last

Hi Stephen I am sharing your feedback and thinks it would make a lot of sense. Many linux distros use something similar to deal with staging packages in their repo, e.g. Fedora with stable/branched/ra

Hi Luis, thank you for the reminder. I suspect either mdsal-model-artifacts or ietf-yang-types-20130715 is not ready yet, or perhaps will no more supported in neon. Can someone confirm that point , pl

I agree with most Sam’s comments but I share Thanh’s feeling that having a separate branch for SR1,SR2,etc is a bad idea and that we’d better keep on using tag on the stable/release branch for that. I

Ivan, Luis, thanks a lot for your quick answers. The runtime problem has been solved with your help and karaf can now be launched. I still need to update iana & others model to fix some REST API error

Hi Luis We are planning to release transportPCE both in Fluorine SR2 and in neon. BR Guillaume

Hi Robert, I got more or less the same experience described by Sam. Last September, we cut the master branch from Fluorine to Neon. https://git.opendaylight.org/gerrit/#/c/75746/ But one month later,

Hi all Luis, I created a TransportPCE stable/neon branch yesterday with a config that was working last week.. But I got a Jenkins build failure because of obsolete poms. It appears that Mdsal binding