Re: [release] Sulfur code freeze
On Fri, Apr 1, 2022 at 4:11 PM Robert Varga <nite@...> wrote: On 31/03/2022 17:41, Robert Varga wrote: Hello Robert and all it looks like we still have several issues are we still tracking some of these issues in jira tickets?
|
|
2022 TSC Chairperson Election
Casey Cain
The self-nomination period for OpenDaylight TSC Chairperson is now open. The role of the TSC Chair is to lead the TSC through meetings and discussions on relevant topics. This election and nomination process is limited to TSC Members. Any TSC Member can nominate themselves, run for election, and vote in the election for the TSC Chair. The self-nomination period will be from to . Interested TSC members may self-nominate here: https://wiki.opendaylight.org/x/mG8EAQ Please let me know if you have any questions. Best, Casey Cain Senior Technical Community Architect Linux Foundation _________________ WeChat: okaru6 WhatsApp: +1.503.779.4519
|
|
2022 OpenDaylight TSC Election Results
Casey Cain
Please join me in congratulating the winners of the 2022 ODL TSC Election!
We look forward to their leadership in the OpenDaylight Community! I would also like to thank the outgoing TSC members. Luis Gomez, Navid Ghazisaidi, and Oleskii Mozghovyi. Your contributions to the community have been greatly appreciated and we hope you continue to support the community in the future. Best, Casey Cain Senior Technical Community Architect Linux Foundation _________________ WeChat: okaru6 WhatsApp: +1.503.779.4519
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 31/03/2022 17:41, Robert Varga wrote:
Alright, everything has been merged up.So looking at https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/185/ we have plenty of badness. The core problem is that a ton of test suites are depending on OPERATIONAL_API, which points to old RESTCONF, which is no longer installed by default. I have https://git.opendaylight.org/gerrit/c/releng/builder/+/100359 to install it for now, but we need to eventually (very soon) ditch it. Luis, any idea on how to fix that in a sensible manner? Also, RF is now reporting a ton of ugly 'Keyword 'BuiltIn.Run Keyword Unless' is deprecated.' messages -- I'll take a peek next week unless somebody beats me to it. Finally, I am tracking two regressions in MD-SAL (already fixed) and one in NETCONF (next on the list), but I'd like to get a better reading on CSIT before rolling out the corresponding releases out. Regards, Robert
|
|
Re: [release] Sulfur code freeze
Thanks Robert... On Thu, Mar 31, 2022 at 8:41 AM Robert Varga <nite@...> wrote: On 31/03/2022 01:20, Robert Varga wrote: Ok great. @Anil Belur and/or @Luis Gomez maybe you can take a look at this
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 31/03/2022 01:20, Robert Varga wrote:
On 29/03/2022 01:13, Robert Varga wrote:Alright, everything has been merged up.On 28/03/2022 00:10, Robert Varga wrote:This is now cleared, netconf-3.0.0 is out there. Most of the MSI update patches are done -- except openflowplugin.On 24/03/2022 01:24, Daniel de la Rosa wrote:Okay, so I am down to 3 call sites, which fall into two categories:A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :( int/dist and autorelease need to have their jobs updated to use maven-3.8, please review the patches here: https://git.opendaylight.org/gerrit/c/releng/builder/+/100304 https://git.opendaylight.org/gerrit/c/releng/builder/+/100306 I am writing up the release notes and upgrade guide next. Bye, Robert
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 29/03/2022 01:13, Robert Varga wrote:
On 28/03/2022 00:10, Robert Varga wrote:This is now cleared, netconf-3.0.0 is out there. Most of the MSI update patches are done -- except openflowplugin.On 24/03/2022 01:24, Daniel de la Rosa wrote:Okay, so I am down to 3 call sites, which fall into two categories:A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :( Upgraded spotbugs is finding some badness which was introduced in https://git.opendaylight.org/gerrit/c/openflowplugin/+/91313 and I need to figure out how to fix it. BGPCEP still has a four contributions left for review, I will take care of that tomorrow. Regards, Robert
|
|
2022 Mentorship Program - Call for Mentors
Casey Cain
Today, we’re excited to open the call for mentors and project proposals for the 2022 LF Networking Mentorship Program. The Program is intended to provide a formal structure to connect mentors and student developers from around the globe to contribute their enthusiasm, time, and experience toward building sustainable LFN communities. Why should you consider mentoring for LF Networking Mentorship Program?
I am interested in mentoring but how do I get started?
While mentors will be on a voluntary basis, the hired mentees will be eligible to receive a stipend. As an added bonus, each mentee who successfully completes the Program will be invited and financially sponsored by LF Networking to attend an event/conference and present their work to the broader community (specific event TBD but will be during Q3 or Q4 of this year or Q1 of the following year). If you have any questions, please contact mentorship@lfnetworking.org We look forward to your submission of a mentorship project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the LF Networking communities. Best, Casey Cain Senior Technical Community Architect Linux Foundation _________________ WeChat: okaru6 WhatsApp: +1.503.779.4519
|
|
TSC Meeting for March 31, 2022 at 10 pm Pacific
Guillaume Lambert
Hello OpenDaylight Community,
The next TSC meeting is March 31, 2022 at 10 pm Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available in the wiki
at the following URL:
If you need to add anything, please let me know or add it there.
The meeting minutes will be at the same location after the meeting is over.
Best Regards
Guillaume
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 28/03/2022 00:10, Robert Varga wrote:
On 24/03/2022 01:24, Daniel de la Rosa wrote:Okay, so I am down to 3 call sites, which fall into two categories:A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :( 1. old RESTCONF's URI parser leafref support. I think I can perform sufficient surgery to make this work without having to rewrite that thing (as was done for new RESTCONF, where this is a breeze) 2. two instances of a weird interaction with XML codec. It is not that weird, I understand what is going on, it just needs a bit of more work. I will need another day to deal with them and, fingers crossed, UTs should agree. Regards, Robert
|
|
ODL TSC Seats
Casey Cain
Hello everyone, At the last TSC meeting, we discussed updating the size of the TSC. We agreed that 3 Committer and 2 Community seats seemed to make sense instead of the current 7 seats. There was an agreement to wait and see if we had enough eligible candidates submit their nominations before making any changes. However, we did not receive enough qualified nominations. I ask that current TSC members review the proposal and vote to update the size of the TSC here: Total Seats will change from 7 to 5. Please let me know if you have any questions. Best, Casey Cain Senior Technical Community Architect Linux Foundation _________________ WeChat: okaru6 WhatsApp: +1.503.779.4519
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 24/03/2022 01:24, Daniel de la Rosa wrote:
On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@... <mailto:nite@...>> wrote:A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :( I expect to have them cleared tomorrow, Tuesday the latest, at which point I'll activate the supercommitter rights and roll things out. The upgrade guide will come right after that, e.g. Tue or Wed. Regards, Robert
|
|
Re: [release] Sulfur code freeze
Olivier Dugeon
Hello Robert, all, Le 21/03/2022 à 15:17, Robert Varga a écrit :
On 21/03/2022 14:45, Olivier Dugeon via lists.opendaylight.org wrote: Latest patches have been submitted:
The first two have been reviewed and are ready to be merged. Latest one needs to be reviewed. The only point that is remaining for BGPCEP, is to clean the compilation from various warning message. I don't know if we include these now or wait for Sulfur SR1. Regards Olivier
--
Olivier Dugeon Orange Expert, Future Networks Open Source Referent Orange/IMT/OLN/WTC/IEE/iTeQ fixe : +33 2 96 07 28 80 mobile : +33 6 82 90 37 85 olivier.dugeon@... _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
Re: [release] Sulfur code freeze
On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@...> wrote: On 21/03/2022 14:24, Robert Varga wrote: That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release
Daniel de la Rosa ODL Release Manager
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 21/03/2022 14:24, Robert Varga wrote:
On 20/03/2022 19:50, Robert Varga wrote:So fixing RESTCONF here is going to require a yangtools-8.0.2 release. The problem is that we lost a DataSchemaContextTree capability which was provided indirectly via SchemaNode.getPath() -- the details are in YANGTOOLS-1412.On 19/03/2022 16:37, Daniel de la Rosa wrote:bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naive.I am still working through netconf/bgpcep, plus the bump to MSI projects. I'll keep you posted. I expect to have that fixed today and finish the RESTCONF integration tomorrow, so that the MRI bump should (fingers crossed) over the weekend. It is way later than planned, expected or hoped, but unfortunately it is what it is. There is silver lining here, though: this effort found two bugs that have been squashed after lurking around for 7 years. I'll keep you posted, Robert
|
|
TSC Meeting for March 24, 2022 at 9 am Pacific
Guillaume Lambert
Hello OpenDaylight Community,
The next TSC meeting is March 24, 2022 at 9 am Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available
in the wiki
at the following URL:
If you need to add anything, please let me know or add it there.
The meeting minutes will be at the same location after the meeting is over.
Best Regards
Guillaume
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
Re: OpenDaylight 2022 TSC Election Nomination period is open
Casey Cain
Hello everyone, This is a reminder that the self-nomination period for the TSC election has been extended to 24 March 2022. Community members interested in joining the TSC must self-nominate before the nomination period closes here: https://wiki.opendaylight.org/x/Zl0EAQ. Best, Casey Cain Senior Technical Community Architect Linux Foundation _________________ WeChat: okaru6 WhatsApp: +1.503.779.4519
On Wed, Mar 16, 2022 at 6:54 AM Casey Cain <ccain@...> wrote:
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 21/03/2022 14:45, Olivier Dugeon via lists.opendaylight.org wrote:
Alright, anyway it's going to take a couple of days to sort out the RESTCONF stuff, so that (and the javadoc jobs) are the real blockers.Not yet for BGPCEP. I discover some late bugs on new PCE server last week. Patch is ready. I'll submit it this afternoon, just right after last verification. Regards, Robert
|
|
Re: [release] Sulfur code freeze
Olivier Dugeon
Hello Robert, Le 21/03/2022 à 14:24, Robert Varga a écrit :
On 20/03/2022 19:50, Robert Varga wrote: Not yet for BGPCEP. I discover some late bugs on new PCE server last week. Patch is ready. I'll submit it this afternoon, just right after last verification. Regards Olivier
--
Olivier Dugeon Orange Expert, Future Networks Open Source Referent Orange/IMT/OLN/WTC/IEE/iTeQ fixe : +33 2 96 07 28 80 mobile : +33 6 82 90 37 85 olivier.dugeon@... _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 20/03/2022 19:50, Robert Varga wrote:
On 19/03/2022 16:37, Daniel de la Rosa wrote:bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naive.I am still working through netconf/bgpcep, plus the bump to MSI projects. I'll keep you posted. serviceutils is also ready to integrate, but there's a problem needing action in global-jjb: javadocs jobs are using mvn35 and thus end up exploding like here: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/32/ Even when we tell the job to use mvn38, it will unpack the correct maven, but will attempt to use mvn35: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/33/console Regards, Robert
|
|