On 28/09/2021 13:33, Robert Varga wrote:

On 28/09/2021 05:24, Robert Varga wrote:

On 27/09/2021 21:18, Daniel de la Rosa wrote:

It seems that we are still having Bgp and pcep issues but are they all critical ? Or can we fix them later so we can release phosphorus  ?

Yeah, it's three test cases, all of them are PCEP-related. They are failing reliably, which seems to indicate a systemic problem.

I'll try to see if I can debug/repro it tomorrow. We might punt to SR1 (which is around the corner) if it ends up being something hard.

Alright, this looks like a pccmock issue:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/bgpcep-csit-1node-userfeatures-all-phosphorus/179/robot-plugin/log.html.gz#s1-s2-k2-k3 https://jira.opendaylight.org/browse/BGPCEP-981 tracks it.

Okay, I think I found the culprint. A fixed bgpcep should be out in about two hours or so and should be reflect in next AR build.

Bye,
Robert

On 28/09/2021 05:24, Robert Varga wrote:

On 27/09/2021 21:18, Daniel de la Rosa wrote:

It seems that we are still having Bgp and pcep issues but are they all critical ? Or can we fix them later so we can release phosphorus  ?

Yeah, it's three test cases, all of them are PCEP-related. They are failing reliably, which seems to indicate a systemic problem.
I'll try to see if I can debug/repro it tomorrow. We might punt to SR1 (which is around the corner) if it ends up being something hard.

Alright, this looks like a pccmock issue:

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/bgpcep-csit-1node-userfeatures-all-phosphorus/179/robot-plugin/log.html.gz#s1-s2-k2-k3

https://jira.opendaylight.org/browse/BGPCEP-981 tracks it.

Regards,
Robert

On 27/09/2021 21:18, Daniel de la Rosa wrote:

It seems that we are still having Bgp and pcep issues but are they all critical ? Or can we fix them later so we can release phosphorus  ?

Yeah, it's three test cases, all of them are PCEP-related. They are failing reliably, which seems to indicate a systemic problem.

I'll try to see if I can debug/repro it tomorrow. We might punt to SR1 (which is around the corner) if it ends up being something hard.

Regards,
Robert

On Thu, Sep 23, 2021 at 5:08 AM Robert Varga <nite@... <mailto:nite@...>> wrote:
On 23/09/2021 05:54, Daniel de la Rosa wrote:
>
> Phosphorus AR#212 integration #169 has only one test case failed
>
> bgpcep
https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/
<https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/> <https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/
<https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/>>
>
> so looks to me like a good RC candidate
It seems we have a few regressions in both BGP and PCEP. I suspect I
know the culprit behind at least one of the failures, should have an
updated bgpcep ready later today.
Regards,
Robert

On 24/09/2021 06:23, Daniel de la Rosa wrote:

On Thu, Sep 23, 2021 at 1:32 PM Robert Varga <nite@... <mailto:nite@...>> wrote:
On 20/09/2021 05:57, Daniel de la Rosa wrote:
> Hello TSC and all
Hey Daniel,

> As we agree, I have updated the filters on this page.
>
> https://wiki.opendaylight.org/display/ODL/Phosphorus+Release
<https://wiki.opendaylight.org/display/ODL/Phosphorus+Release>
> <https://wiki.opendaylight.org/display/ODL/Phosphorus+Release
<https://wiki.opendaylight.org/display/ODL/Phosphorus+Release>>
>
> to try to capture the bug fixes and enhancements for each of the
managed
> projects since phosphorus started ( 3/17/2021).
>
> Please  let us know if this list of jira tickets is
representative of
> the work for each of your projects in this release. Additionally and
> more important, please  provide a summary on the page or reply
with this
> email, with the highlights for each of your projects so LFN
> marketing can get ready for this release.
As I stated before, I do not believe Confluence is the right tool here
for long term.
Since we are already maintaining release notes here:
https://docs.opendaylight.org/en/latest/release-notes/
<https://docs.opendaylight.org/en/latest/release-notes/>
I think that page should be our primary "release notes" collateral.
I have started updating individual project release notes, like
Controller:
https://docs.opendaylight.org/en/latest/release-notes/project/controller.html
<https://docs.opendaylight.org/en/latest/release-notes/project/controller.html>
yes i agree, this does look better than the confluence page ...  and I think you meant this page right?
https://docs.opendaylight.org/en/latest/release-notes/projects/controller.html <https://docs.opendaylight.org/en/latest/release-notes/projects/controller.html>
which looks great, so lets go with this page. I'll just link the confluence page to this page instead

I am glad you like it, all MRI projects have been updated to the best of my knowledge.

As for marketing ... what is really the marketing strategy being
executed? Is it just a simple article on www.opendaylight.org
<http://www.opendaylight.org>?
Yes, an article that highlights new features, enhancements and fixes In Phosphorus. We agree on the last TSC to dedicate time on the next meeting to review this as  a group. Hoep you can join us to review these release notes

Ah, yeah, my timing was off last time, joined exactly one hour late :(

Regards,
Robert

Hello everyone,

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

OpenDaylight currently requires Java 11 at compile-time and *should* be able to run on everything up to Java 17. This *should* is currently not enforced by our CI, but I am not aware of any reasons this would not be the case.

Java 17 is the next LTS release, which there are multiple support options available, with at least 8 years of support being available.

As per our usual OpenDaylight support policy, we are currently supporting Java 17 runtime on a best-effort policy: any issues found will be dealt with to the extent considered feasible.

Going forward, though, we will require Java 17 as both compile-time and runtime very soon, simply because of the language feature options becoming available:
- https://openjdk.java.net/jeps/361 (switch expressions)
- https://openjdk.java.net/jeps/371 (hidden classes)
- https://openjdk.java.net/jeps/378 (text blocks)
- https://openjdk.java.net/jeps/394 (instanceof pattern matching)
- https://openjdk.java.net/jeps/395 (records)
- https://openjdk.java.net/jeps/409 (sealed classes)
- https://openjdk.java.net/jeps/415 (deserialization filters)
- https://jdk.java.net/17/release-notes#JDK-8251989 (improved CHA)

Furthermore, there are a ton of runtime improvements, which we can take into implementation considerations, like https://bugs.openjdk.java.net/browse/JDK-8266074. We want to take advantage to these ASAP.

IIUC, there are only a few issues which prevents us from adopting JDK 17 as a requirement:
- maven-xtend-plugin compatibility (due to Guice, what a surprise), which should be solved in 2.26.0, whenever that is available
- SpotBugs compatibility, which should be addressed in 4.4.x series


With all this in picture, I believe the proper course in OpenDaylight is to have:
- Sulfur (22.03) supporting both JDK11 and JDK17 at compile-time, with artifacts compatible with JDK11+
- All of Sulfur being validated with JDK17
- Chlorine (22.09) to require JDK17+

Unless there are any objections, this is the current plan of record. If you disagree, please holler now.

Regards,
Robert

On 20/09/2021 05:57, Daniel de la Rosa wrote:

Hello TSC and all

Hey Daniel,

As we agree, I have updated the filters on this page.
https://wiki.opendaylight.org/display/ODL/Phosphorus+Release <https://wiki.opendaylight.org/display/ODL/Phosphorus+Release>
to try to capture the bug fixes and enhancements for each of the managed projects since phosphorus started ( 3/17/2021).
Please  let us know if this list of jira tickets is representative of the work for each of your projects in this release. Additionally and more important, please  provide a summary on the page or reply with this email, with the highlights for each of your projects so LFN marketing can get ready for this release.

As I stated before, I do not believe Confluence is the right tool here for long term.

Since we are already maintaining release notes here: https://docs.opendaylight.org/en/latest/release-notes/

I think that page should be our primary "release notes" collateral.

I have started updating individual project release notes, like Controller:
https://docs.opendaylight.org/en/latest/release-notes/project/controller.html

The end result is very maintainable structure, which can be just updated (perhaps subject to automation), rather than recreated every time anew.

As for marketing ... what is really the marketing strategy being executed? Is it just a simple article on www.opendaylight.org?

Regards,
Robert

On 23/09/2021 18:24, Robert Varga wrote:

On 21/09/2021 02:01, Anil Belur wrote:

Hello all,

The master branch is locked for Phosphorus code freeze and branch cutting ("stable/phosphorus") and master branch will be promoted to next (Sulphur). Once the version bump and the release activities are complete, I will notify the status here.

It seems Jenkins/JJB integration is busted. I have filed https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22956 for that.

To explain: it is failing since Sep 21, hence Jenkins jobs do not reflect Gerrit branches mapping:
- all -phosphorus jobs still refer to master branch
- there are no -sulfur jobs

Regards,
Robert

On 21/09/2021 02:01, Anil Belur wrote:

Hello all,
The master branch is locked for Phosphorus code freeze and branch cutting ("stable/phosphorus") and master branch will be promoted to next (Sulphur). Once the version bump and the release activities are complete, I will notify the status here.

It seems Jenkins/JJB integration is busted. I have filed https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22956 for that.

Bye,
Robert

On 23/09/2021 05:54, Daniel de la Rosa wrote:

Phosphorus AR#212 integration #169 has only one test case failed
bgpcep https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/ <https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/>
so looks to me like a good RC candidate

It seems we have a few regressions in both BGP and PCEP. I suspect I know the culprit behind at least one of the failures, should have an updated bgpcep ready later today.

Regards,
Robert

_________________________________________________________________________________________________________________________

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.

On 22/09/2021 06:14, Daniel de la Rosa wrote:

On Tue, Sep 21, 2021 at 2:45 AM Anil Belur <abelur@... <mailto:abelur@...>> wrote:
On Tue, Sep 21, 2021 at 3:29 PM Daniel de la Rosa
<ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
Thanks Anil. Robert,  please correct me if I'm wrong, but we
have to wait for [1] to be fixed before we can pick a RC
[1]
https://git.opendaylight.org/gerrit/c/integration/test/+/97467
<https://git.opendaylight.org/gerrit/c/integration/test/+/97467>
Anil, i think next release code name should be Sulfur
<https://en.wikipedia.org/wiki/Sulfur>
Yes, We need Luis or someone from the integration team to merge
97467, then we can pick up the subsequent AR build. 97467 is merged, so i guess i can pick AR #211, Integration #167. There are some CSIT failures
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/integration-distribution-test-phosphorus/167/csit_failed_tests.txt.gz <https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/integration-distribution-test-phosphorus/167/csit_failed_tests.txt.gz>
so i guess we have to just evaluate that. @Anil Belur <mailto:abelur@...>  can you produce the spreadsheet for phosphorus? i dont have privileges to come up with a new one

I have retriggered the job, as the OVSDB/OFP test cases failed with:

Waiting to initialize infrastructure...
WARN: Failed to initialize stack. Reason: Resource CREATE failed: Forbidden: resources.vm_1_group.resources[0].resources.instance: Quota exceeded for ram: Requested 8192, but already used 999424 of 1000000 ram (HTTP 403) (Request-ID: req-5e8808dd-c609-418c-83e7-a0078a080051)

i.e. instance limits, again :(

Bye,
Robert

Sure, I think I caught up with int/dist and int/test pending patches, let me know if something is missing review/merge.

BR/Luis

On 21/09/2021 14:44, Robert Varga wrote:

On 15/09/2021 21:40, Robert Varga wrote:

On 15/09/2021 17:29, Luis Gomez wrote:

Looks like we have a regression on bgpcep:

https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/ <https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/>

Yes, the failures are caused by int/test's libraries not being able to deal with the new Entity Ownership Service implementation.

Tomas is working on fixing that here: https://git.opendaylight.org/gerrit/c/integration/test/+/97467

Once that is addressed and we still have real failures, we'll solve them through a bgpcep version bump.

So aside from the CSIT updates we'll also need an updated bgpcep release because we have busted BMP server-side and all test tools.
bgpcep-0.16.5 is being promoted now to address these issues.

So stable/phosphorus should be okay (once jobs are populated), but sulfur needs https://git.opendaylight.org/gerrit/c/integration/distribution/+/97582 merged.

Luis, can you take a look, please?

Thanks,
Robert

Regards,
Robert

Regards,
Robert

BR/Luis

On Sep 14, 2021, at 1:41 PM, Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:

Hello TSC and all

We are going to codefreezePhosphorus for all Managed Projects ( cut and lock release branches ) on Monday September 20th at 10 am pst

Please remember that we only allow blocker bug fixes in release branch after code freezes

Daniel de la Rosa
ODL Release Manager

Thanks

ps. Release schedule and checklist for your reference

https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Checklist <https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Checklist>

https://docs.opendaylight.org/en/latest/release-process/release-schedule.html <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>



Thanks


Thanks

On 15/09/2021 21:40, Robert Varga wrote:

On 15/09/2021 17:29, Luis Gomez wrote:

Looks like we have a regression on bgpcep:

https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/ <https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/>

Yes, the failures are caused by int/test's libraries not being able to deal with the new Entity Ownership Service implementation.
Tomas is working on fixing that here: https://git.opendaylight.org/gerrit/c/integration/test/+/97467
Once that is addressed and we still have real failures, we'll solve them through a bgpcep version bump.

So aside from the CSIT updates we'll also need an updated bgpcep release because we have busted BMP server-side and all test tools.

bgpcep-0.16.5 is being promoted now to address these issues.

Regards,
Robert

Regards,
Robert

BR/Luis

On Sep 14, 2021, at 1:41 PM, Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:

Hello TSC and all

We are going to codefreezePhosphorus for all Managed Projects ( cut and lock release branches ) on Monday September 20th at 10 am pst

Please remember that we only allow blocker bug fixes in release branch after code freezes

Daniel de la Rosa
ODL Release Manager

Thanks

ps. Release schedule and checklist for your reference

https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Checklist <https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Checklist>

https://docs.opendaylight.org/en/latest/release-process/release-schedule.html <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>



Thanks


Thanks