|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Gilles Thouenon
Hello Daniel,
I believe that we can reasonably consider that TransportPCE will not be able to integrate the GA distribution of Sulfur. We could not complete the project migration due to many issues we are facing and that are still under investigation. The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.
On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
If I try to summarize the situation and issues that are still open:
Best regards, Gilles
De : release@... <release@...>
De la part de Guillaume Lambert via lists.opendaylight.org
Hi Daniel
I let Gilles answer the question since he is in charge of this TPCE release. We can put that at the TSC agenda tomorrow.
BR Guillaume
De : Daniel de la Rosa <ddelarosa0707@...>
Thanks Anil .. So @LAMBERT Guillaume TGI/OLN are you going to skip Sulfur to TPCE? I can start with Sulfur SR1 code freeze as scheduled next week while Sulfur GA is getting ready
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
_________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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-dev][release] OpenDaylight - Sulfur release status
Guillaume Lambert
Hi Daniel
I let Gilles answer the question since he is in charge of this TPCE release. We can put that at the TSC agenda tomorrow.
BR Guillaume
De : Daniel de la Rosa <ddelarosa0707@...>
Thanks Anil .. So @LAMBERT Guillaume TGI/OLN are you going to skip Sulfur to TPCE? I can start with Sulfur SR1 code freeze as scheduled next week while Sulfur GA is getting ready
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
_________________________________________________________________________________________________________________________ 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-dev][release] OpenDaylight - Sulfur release status
Thanks Anil .. So @LAMBERT Guillaume TGI/OLN are you going to skip Sulfur to TPCE? I can start with Sulfur SR1 code freeze as scheduled next week while Sulfur GA is getting ready On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
|
|
|
|
TSC Meeting for May 5, 2022 at 9 am Pacific
Guillaume Lambert
Hello OpenDaylight Community,
The next TSC meeting is May 5, 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:
https://wiki.opendaylight.org/x/CnoEAQ
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-dev][release] OpenDaylight - Sulfur release status
Anil Belur
+tsc On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
|
|
|
|
TSC Meeting for April 28, 2022 at 10 pm Pacific
Guillaume Lambert
Hello OpenDaylight Community,
The next TSC meeting is April 28, 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:
https://wiki.opendaylight.org/x/yHgEAQ 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: [E] Re: [OpenDaylight TSC] [release] Sulfur code freeze
Sangwook Ha
OFP clustering is not very stable yet but I'm okay with addressing it later with SR1. Thanks, Sangwook On Tue, Apr 26, 2022 at 11:02 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
|
|
|
|
TSC approval of Sulfur GA
Hello TSC Please approve Sulfur AR #30 as RC for Sulfur GA as soon as possible Thanks Daniel de la Rosa ODL Release Manager |
|
|
|
Re: [release] Sulfur code freeze
On Tue, Apr 26, 2022 at 12:55 PM Robert Varga <nite@...> wrote: On 15/04/2022 02:23, Daniel de la Rosa wrote: ok @Ha, Sangwook and all TSC, if you are ok with releasing Sulfur in its current state, AR#30 and integration #220, please approve it at I'll also send another email just for the approval Thank you all
|
|
|
|
MRI projects in churn
Robert Varga
Hey everyone, especially those working on ODL
We are currently transitioning to JDK17 as part of Chlorine MRI bump. Unfortunately we are at this point 11 days past the deadline, so things are moving quickly. The reason for that is because JDK17 is giving us https://openjdk.java.net/jeps/409 Sealed Classes. Sealing an abstract class or an interface is, strictly speaking, an API-breaking change. While it does not break users per se, it can break them in two cases: - they are using switch expressions, in which case making a class sealed can expose the user to new exhaustiveness checks: suddenly a switch expression may become exhaustive without a 'default' branch superfluous and unreachable (which is good) causing a build failure (which is bad) - they are mocking or otherwise creating new subclasses/implementations of sealed classes/interfaces. Hence this work needs to occur in parallel, which unfortunately also inflicts an autorelease-like dev experience on people working on breaking edge MRI. Most of the breaking stuff is in, but nevertheless there may be times when your (or jenkins.odl) build breaks. If that happens, please retry with 'mvn -U' to get latest snapshots. If it's jenkins or -U does not help, please ping me -- I am trying to keep up with this, but there will be things I miss. I expect things to begin to settle down in about a week, with ETA to normal integration being a week after that. I'll keep you posted here. At the moment this pertains to odlparent, yangtools, mdsal and controller, all of which require JDK17 to build. infrautils is joining the party soon. aaa, netconf and bgpcep will follow. Sorry about the inconvenience, Robert |
|
|
|
Re: [release] Sulfur code freeze
Robert Varga
On 15/04/2022 02:23, Daniel de la Rosa wrote:
Anyhow, Integration test for AR#15 still has some issuesSo we have latest AR here: https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/29/ Triggered by Sangwook, because the previous run failed. We can expect AR #30 in ~4 hours and test results from that in another ~3 hours. Based on the results of https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/219/, the release is GO from my perspective. There seem to be OFP issues, though, I think Sangwook has the final say. On the BGPCEP side of things, we have two failures: 1. one of them is a BGP policy 409, which I need to investigate, but I do not believe it's anything major 2. BGP ingest is plagued by https://jira.opendaylight.org/browse/CONTROLLER-2043, but I honestly think this is an environment issue At any rate, looking at the schedule, we are *way* past the release date and in fact should be releasing Sulfur SR1 on 4/28, i.e. in two days. I think we should just release as is, get the marketing stuff out, etc. and circle back for SR1 -- say, in two weeks. That would give us a few days of breathing time (I know I need some) and see what's what. We also are ~2 weeks past the Chlorine MRI bump, so that switching gears makes a ton of sense -- I really want Chlorine to get us back on track with the calendar :) Regards, Robert |
|
|
|
Re: Old RESTCONF northbound scheduled for removal
Robert Varga
On 15/03/2022 18:44, Robert Varga wrote:
On 01/12/2021 11:14, Robert Varga wrote:[snip] The old implementation is no longer present in netconf/master, hence this item is slated for delivery in 2022.09 Chlorine.4. 2022.09 Chlorine, due out in September 2022, will not include the old implementation. Regards, Robert |
|
|
|
Re: The road to Java 17
Robert Varga
On 25/09/2021 00:00, Robert Varga wrote:
Hello everyone,Hello again, as you might have noticed, Java 17 has been released: https://jdk.java.net/17/ with reference implementation here: https://jdk.java.net/java-se-ri/17[snip] IIUC, there are only a few issues which prevents us from adopting JDK 17 as a requirement:These issues have been addressed. With all this in picture, I believe the proper course in OpenDaylight is to have:Both these items are delivered, all projects participating on Sulfur GA verify each patch with both JDK11 and JDK17. - Chlorine (22.09) to require JDK17+This is now slated for delivery: odlparent/master and yangtools/master both require JDK17 and are taking advantage of JDK17 features. More projects are slated to follow. Regards, Robert |
|
|
|
Re: [release] Switching default build node to centos8-builder-4c-4g
Robert Varga
On 22/04/2022 10:11, Anil Belur wrote:
+1 We should be able switch to CentOS8 for the jobs that require JDK17, but there could be a few caveats that we should consider before we move the rest of the builders nodes.Hmm, that would be a major problem and really soon. Sigul is part of stage jobs -- stage i.e. build + sign. We are exactly 2 patches away from odlparent/master requiring JDK17 to build -- and that just does not work on CentOS7. We need either Sigul+CentOS8 or JDK17+CentOS7. The former is obviously the preferred solution. Or, we need decoupling of stage's build and sign steps in a reliable manner -- which would really call for Jenkins Pipelines, but we have not even dipped our toes in that particular ocean... Regards, Robert On Thu, Apr 21, 2022 at 9:14 AM Robert Varga <nite@... <mailto:nite@...>> wrote: |
|
|
|
Re: [release] Switching default build node to centos8-builder-4c-4g
Anil Belur
+1 We should be able switch to CentOS8 for the jobs that require JDK17, but there could be a few caveats that we should consider before we move the rest of the builders nodes. Sigul (artifact signing) is built on CentOS7 and may not be compatible when we try to sign artifact on CentOS8. On Thu, Apr 21, 2022 at 9:14 AM Robert Varga <nite@...> wrote: Hello everyone, |
|
|
|
Re: [release] [OpenDaylight TSC] Switching default build node to centos8-builder-4c-4g
Ivan Hrasko
+1 Od: release@... <release@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: piatok, 22. apríla 2022 1:57:03 Komu: Robert Varga Kópia: infrastructure@...; release@...; tsc@... Predmet: Re: [release] [OpenDaylight TSC] Switching default build node to centos8-builder-4c-4g LGTM, any change for updating current infra is +1 for me :)
> On Apr 20, 2022, at 4:14 PM, Robert Varga <nite@...> wrote: > > Hello everyone, > > we are currently defaulting to centos7-builder-4c-4g here: https://github.com/opendaylight/releng-builder/blob/master/jjb/defaults.yaml#L19= > > CentOS7 is ancient and cannot support our releases going forward, as it lacks JDK17 -- which is scheduled to be required for Chlorine. > > MRI projects have already switched to CentOS (Stream) 8, like here: https://github.com/opendaylight/releng-builder/blob/master/jjb/netconf/netconf.yaml#L17= > > That having been said and provided we get a fix for https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826, I propose we switch the default build node to CentOS 8 and deal with whatever fallout -- probably in June, as that is essentially quiet with only Chlorine prep on the table. > > Whaddya say? > > Thanks, > Robert > > > > > |
|
|
|
Re: Switching default build node to centos8-builder-4c-4g
Luis Gomez
LGTM, any change for updating current infra is +1 for me :)
toggle quoted message
Show quoted text
On Apr 20, 2022, at 4:14 PM, Robert Varga <nite@...> wrote: |
|
|
|
Re: [integration-dev] [releng][TSC] Sulfur release status - master branch has been locked
Anil Belur
On Thu, Apr 21, 2022 at 12:16 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello all, The version bump is complete, the master branch is promoted to the next release (Chlorine) and the "stable/sulfur" branch has been created. Note: The master branch (Chlorine) is unlocked and open for development, while the "stable/sulfur" branch remains locked until the Sulfur release. New Jenkins jobs for the Chlorine stream will be added once the CR [1.] get merged. Regards, Anil Belur |
|
|
|
[integration-dev] [releng][TSC] Sulfur release status - master branch has been locked
Anil Belur
Hello all, The master branch is locked for Sulfur code freeze and branch cutting ("stable/sulfur") and master branch will be promoted to next (Chlorine), which will be the development version. Once the version bump and the release activities are complete, I will notify the status here. Regards, Anil Belur |
|
|
|
Switching default build node to centos8-builder-4c-4g
Robert Varga
Hello everyone,
we are currently defaulting to centos7-builder-4c-4g here: https://github.com/opendaylight/releng-builder/blob/master/jjb/defaults.yaml#L19= CentOS7 is ancient and cannot support our releases going forward, as it lacks JDK17 -- which is scheduled to be required for Chlorine. MRI projects have already switched to CentOS (Stream) 8, like here: https://github.com/opendaylight/releng-builder/blob/master/jjb/netconf/netconf.yaml#L17= That having been said and provided we get a fix for https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826, I propose we switch the default build node to CentOS 8 and deal with whatever fallout -- probably in June, as that is essentially quiet with only Chlorine prep on the table. Whaddya say? Thanks, Robert |
|
|