Date   

Old RESTCONF northbound scheduled for removal

Robert Varga
 

Hello everyone,

as you might be aware, OpenDaylight ships two versions of RESTCONF northbound.

The first is the all-familiar implementation of draft-bierman-netconf-restconf-02, available at localhost:8181/restconf.

The second is the implementation of RFC8040, available at localhost:8181/rests.

TL;DR of this email is that we plan to completely remove the first implementation in our 2022.09 Chlorine release. If it is a problem for you, please speak out now.


There are multiple reasons driving this decision:

1. The old interface does not (and cannot) support YANG 1.1 action statements, i.e. there is no way to invoke them.

2. RFC8040 implementation is considered now considered a fully-maintained and production-ready equivalent.

3. The implementation is effectively frozen, receiving only minimal updates required for it to remain working in face of upstream API changes.

4. Bringing the implementation into a shape which is maintainable in the long term requires a large-scale refactor with the associated risk of introducing regressions.

5. The implementation is the only user of a number of pieces of upstream code, preventing that code from being removed.


The tracker issue for the removal is https://jira.opendaylight.org/browse/NETCONF-837 and the plan of action is as follows:

1. Phosphorus SR2, due out 2022-01-27, will issue a single (mild) warning on startup. We will continue to install the implementation as part of the 'odl-restconf' feature.

2. 2022.03 Sulfur, due out 2022-03-17, will not install the old implementation by default. Users will be required to explicitly install the 'odl-restconf-nb-bierman02' feature. The warning introduced in step 1. will be updated to warn about the fact the feature is no longer supported and scheduled for removal in the next major release.

3. Old implementation will be removed from the netconf git repository's master branch as soon as the 3.0.x stability branch for Sulfur is created -- i.e. March/April 2022.

4. 2022.09 Chlorine, due out in September 2022, will not include the old implementation.

Unless serious objections to this are raised by 2022-01-10 we will execute it exactly as outlined above.

Regards,
Robert


Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Phosphorus SR1

Daniel de la Rosa
 

Thank you Christophe and all. . @Luis Gomez , you can now proceed to release Phosphorus SR1 distribution. 


On Tue, Nov 30, 2021 at 2:59 AM <christophe.betoule@...> wrote:

Hello,

 

I have just successfully released TransportPCE for Phosphorus SR1 tagged with version 4.1.0.

You can find the log output here: https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/24/console

https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/24/console.log.gz

 

The release note will be updated soon.

 

Regards,

Christophe

 

De : integration-dev@... [mailto:integration-dev@...] De la part de Anil Belur
Envoyé : mardi 30 novembre 2021 01:55
À : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; TSC <tsc@...>
Cc : Andrew Grimberg <agrimberg@...>; Casey Cain <ccain@...>; Daniel de la Rosa <ddelarosa0707@...>; navid.ghazisaidi@...
Objet : [integration-dev] [opendaylight-dev][release] OpenDaylight - Phosphorus SR1

 

Hello All,

OpenDaylight Phosphorus SR1 version bump is complete and the staging repository is being promoted. The 'stable/phosphorus' branch is unlocked.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts.
2. Release Distribution once step 1. is complete.
3. Release notes CR needs a review. (https://git.opendaylight.org/gerrit/c/docs/+/98753)
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Phosphorus SR1 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://wiki.opendaylight.org/display/ODL/Phosphorus+SR1+Release+Approval

_________________________________________________________________________________________________________________________

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 Infrastructure] Gerrit update at 4:00pm PST today.

Jessica Wagantall <jwagantall@...>
 

Dear ODL community, 

First of all, my apologies for the downtime that happened last week in an attempt to update the Gerrit commit message options.
We have now found the cause of the problem and it has been corrected. 

The new change will be deployed today Nov 30th at 2:00pm PST
We do not expect another downtime and with some hope there would be just a small glitch if anything. 

Thanks again for your patience in letting us make these changes.
Jess

On Wed, Nov 24, 2021 at 4:35 PM Jessica Wagantall via lists.opendaylight.org <jwagantall=linuxfoundation.org@...> wrote:

Hi Team!..

Merging this change seems to have caused an issue bringing the service back. 

I have for now reverted it and will debug it further before attempting to merge again. 
Will let you know next time is ready!

Thanks a ton for your patience!
Jess




Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Phosphorus SR1

Christophe Betoule
 

Hello,

 

I have just successfully released TransportPCE for Phosphorus SR1 tagged with version 4.1.0.

You can find the log output here: https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/24/console

https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/24/console.log.gz

 

The release note will be updated soon.

 

Regards,

Christophe

 

De : integration-dev@... [mailto:integration-dev@...] De la part de Anil Belur
Envoyé : mardi 30 novembre 2021 01:55
À : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; TSC <tsc@...>
Cc : Andrew Grimberg <agrimberg@...>; Casey Cain <ccain@...>; Daniel de la Rosa <ddelarosa0707@...>; navid.ghazisaidi@...
Objet : [integration-dev] [opendaylight-dev][release] OpenDaylight - Phosphorus SR1

 

Hello All,

OpenDaylight Phosphorus SR1 version bump is complete and the staging repository is being promoted. The 'stable/phosphorus' branch is unlocked.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts.
2. Release Distribution once step 1. is complete.
3. Release notes CR needs a review. (https://git.opendaylight.org/gerrit/c/docs/+/98753)
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Phosphorus SR1 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://wiki.opendaylight.org/display/ODL/Phosphorus+SR1+Release+Approval

_________________________________________________________________________________________________________________________

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.


[opendaylight-dev][release] OpenDaylight - Phosphorus SR1

Anil Belur
 

Hello All,

OpenDaylight Phosphorus SR1 version bump is complete and the staging repository is being promoted. The 'stable/phosphorus' branch is unlocked.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts.
2. Release Distribution once step 1. is complete.
3. Release notes CR needs a review. (https://git.opendaylight.org/gerrit/c/docs/+/98753)
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Phosphorus SR1 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://wiki.opendaylight.org/display/ODL/Phosphorus+SR1+Release+Approval


Re: Phosphorus SR1 TSC approval

Daniel de la Rosa
 

Hello TSC and all

Gentle reminder to approve phosphorus AR #278

Thanks

On Fri, Nov 26, 2021 at 9:17 AM Daniel de la Rosa via lists.opendaylight.org <ddelarosa0707=gmail.com@...> wrote:

Thanks!  yes #233 looks good so I have updated the the vote for #278


Please approve at your earliest convenience

Thanks

On Fri, Nov 26, 2021 at 12:27 AM Robert Varga <nite@...> wrote:
On 26/11/2021 01:56, Daniel de la Rosa wrote:
> Hello Robert. Just saw your vote as no on this, so we will use 278 and
> try the approval tomorrow

Thanks. Btw. the test job from #278 failed, but a retry here:
https://jenkins.opendaylight.org/releng/job/integration-distribution-test-phosphorus/233/
looks reasonable.

Regards,
Robert

>
> Thanks
>
> On Thu, Nov 25, 2021 at 1:26 PM Daniel de la Rosa
> <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
>
>     Hello TSC and all
>
>     Please proceed to approve Phosphorus SR1
>
>     Only TSC members can vote
>
>
>     Thanks
>
>
>     --
>     Daniel de la Rosa
>     ODL Release Manager
>
> --
> Daniel de la Rosa
> ODL Release Manager
>


Re: Phosphorus SR1 TSC approval

Daniel de la Rosa
 

Thanks!  yes #233 looks good so I have updated the the vote for #278


Please approve at your earliest convenience

Thanks

On Fri, Nov 26, 2021 at 12:27 AM Robert Varga <nite@...> wrote:
On 26/11/2021 01:56, Daniel de la Rosa wrote:
> Hello Robert. Just saw your vote as no on this, so we will use 278 and
> try the approval tomorrow

Thanks. Btw. the test job from #278 failed, but a retry here:
https://jenkins.opendaylight.org/releng/job/integration-distribution-test-phosphorus/233/
looks reasonable.

Regards,
Robert

>
> Thanks
>
> On Thu, Nov 25, 2021 at 1:26 PM Daniel de la Rosa
> <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
>
>     Hello TSC and all
>
>     Please proceed to approve Phosphorus SR1
>
>     Only TSC members can vote
>
>
>     Thanks
>
>
>     --
>     Daniel de la Rosa
>     ODL Release Manager
>
> --
> Daniel de la Rosa
> ODL Release Manager
>


Re: Jenkins jobs: maven-3.8 as default

Guillaume Lambert
 

Hello

+1 for me too


BR

Guillaume


De : TSC@... <TSC@...> de la part de Anil Belur <abelur@...>
Envoyé : jeudi 25 novembre 2021 23:47:09
À : Robert Varga
Cc : tsc@...
Objet : Re: [OpenDaylight TSC] Jenkins jobs: maven-3.8 as default
 
+1 on moving to mvn38.

Cheers,
Anil

On Wed, Nov 24, 2021 at 10:43 PM Robert Varga <nite@...> wrote:
Hello TSC members,

during infrastructure-side preparation for odlparent-10's requirement of
maven-3.8+ in Sulfur, we have discovered an issue with our current JJB
setup.

It essentially means that attempts to override job group definitions'
use of maven-3.5 are fruitless.

After sparing a bit with Anil on Slack, we have concluded that the
cleanest solution is to:
- set our default to mvn38
- remove all current overrides of this default

This would result in all our jobs using maven-3.8, including Silicon and
Phosphorus.

This change is purely in our build infrastructure and nothing changes in
terms of the ability to build Silicon/Phosphorus projects with maven-3.5+.

In terms of compatibility, I have been using maven-3.8.2+ for all local
builds for a couple of months now and experienced no issues at all.

There is another angle to this, which is that maven-3.8.1 is a security,
as detailed here:
https://maven.apache.org/docs/3.8.1/release-notes.html#cve-2020-13956
https://maven.apache.org/docs/3.8.1/release-notes.html#cve-2021-26291

Hence we would like to merge
https://git.opendaylight.org/gerrit/c/releng/builder/+/98646 and follow
that up with a cleanup of superfluous mvn-version directives.

Are there any objections to this plan of action?

Thanks,
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.


Re: Phosphorus SR1 TSC approval

Robert Varga
 

On 26/11/2021 01:56, Daniel de la Rosa wrote:
Hello Robert. Just saw your vote as no on this, so we will use 278 and try the approval tomorrow
Thanks. Btw. the test job from #278 failed, but a retry here: https://jenkins.opendaylight.org/releng/job/integration-distribution-test-phosphorus/233/ looks reasonable.

Regards,
Robert

Thanks
On Thu, Nov 25, 2021 at 1:26 PM Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
Hello TSC and all
Please proceed to approve Phosphorus SR1
Only TSC members can vote
Thanks
--
Daniel de la Rosa
ODL Release Manager
--
Daniel de la Rosa
ODL Release Manager


Re: Phosphorus SR1 TSC approval

Daniel de la Rosa
 

Hello Robert. Just saw your vote as no on this, so we will use 278 and try the approval tomorrow 

Thanks 

On Thu, Nov 25, 2021 at 1:26 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
Hello TSC and all

Please proceed to approve Phosphorus SR1

Only TSC members can vote


Thanks


--
Daniel de la Rosa
ODL Release Manager

--
Daniel de la Rosa
ODL Release Manager


Re: Jenkins jobs: maven-3.8 as default

Anil Belur
 

+1 on moving to mvn38.

Cheers,
Anil

On Wed, Nov 24, 2021 at 10:43 PM Robert Varga <nite@...> wrote:
Hello TSC members,

during infrastructure-side preparation for odlparent-10's requirement of
maven-3.8+ in Sulfur, we have discovered an issue with our current JJB
setup.

It essentially means that attempts to override job group definitions'
use of maven-3.5 are fruitless.

After sparing a bit with Anil on Slack, we have concluded that the
cleanest solution is to:
- set our default to mvn38
- remove all current overrides of this default

This would result in all our jobs using maven-3.8, including Silicon and
Phosphorus.

This change is purely in our build infrastructure and nothing changes in
terms of the ability to build Silicon/Phosphorus projects with maven-3.5+.

In terms of compatibility, I have been using maven-3.8.2+ for all local
builds for a couple of months now and experienced no issues at all.

There is another angle to this, which is that maven-3.8.1 is a security,
as detailed here:
https://maven.apache.org/docs/3.8.1/release-notes.html#cve-2020-13956
https://maven.apache.org/docs/3.8.1/release-notes.html#cve-2021-26291

Hence we would like to merge
https://git.opendaylight.org/gerrit/c/releng/builder/+/98646 and follow
that up with a cleanup of superfluous mvn-version directives.

Are there any objections to this plan of action?

Thanks,
Robert






Re: [E] Re: [release] Phosphorus SR1 RC

Daniel de la Rosa
 

Hello Sangwook and all

Ok if that's the case and these OFP and OVSDB issues can be fixed later, I'll sent a TSC approval request for AR #277 Integration #231 as Phosphorus SR1

Thanks





Thanks 

On Wed, Nov 24, 2021 at 4:48 PM Ha, Sangwook <sangwook.ha@...> wrote:
Hi Daniel,

The failure of openflowplugin-csit-3node-clustering-bulkomatic-only-phosphorus for integration-distribution-test-phosphorus #230 is because of BindException (testing was aborted), but there would be a few failing test cases even if it was completed normally. And I believe all three failing Jenkins jobs (2 OpenFlow Plugin & 1 OVSDB) are affected by the same clustering issue, which won't be fixed for this release.

Thanks,
Sangwook

On Wed, Nov 24, 2021 at 7:19 AM Daniel de la Rosa <ddelarosa0707@...> wrote:
Thanks Luis

On Tue, Nov 23, 2021 at 4:22 PM Luis Gomez <ecelgp@...> wrote:
OK, int/test changes are merged now.

On Nov 23, 2021, at 3:36 PM, Ha, Sangwook <sangwook.ha@...> wrote:

3 integration/test patches for OpenFlow Plugin are ready for review (submitted one more to address an EOS test case):


Luis, please take a look at the changes.

Thanks,
Sangwook

On Tue, Nov 23, 2021 at 12:08 PM Sangwook Ha via lists.opendaylight.org <sangwook.ha=verizon.com@...> wrote:
In addition to the integration/test change 98642, we need some additional changes for OpenFlow Plugin tests to support the stricter URL requirements & status code change (204 for RPC with empty response):


I'm running some test jobs in the sandbox now, and should be ready for review.

Thanks,
Sangwook

On Tue, Nov 23, 2021 at 11:23 AM Robert Varga <nite@...> wrote:
On 22/11/2021 23:11, Daniel de la Rosa wrote:
>
>
> it seems that there are still BGPCEP, OVSDB and OFP issues
>
> https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/
> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/>

Okay, so BGPCEP should be all clear, the RESTCONF regression blocking
OFP perf tests is resolved.

One of the OVSDB failures has a controller tracker, but we won't be able
to fix it for SR1.

Th eonly outstanding item I am currently tracking is this:
https://git.opendaylight.org/gerrit/c/integration/test/+/98642

Luis, can you review it, please?

So this is what we are getting after all these fixes...


two OFP tests are still failing.. are we ok with picking RC with these two issues? @Robert Varga @Luis Gomez @Ha, Sangwook ?


 

Thanks,
Robert









Phosphorus SR1 TSC approval

Daniel de la Rosa
 

Hello TSC and all

Please proceed to approve Phosphorus SR1

Only TSC members can vote


Thanks

--
Daniel de la Rosa
ODL Release Manager


Re: ODL Twitter Account Status

Robert Varga
 

On 15/11/2021 11:05, Robert Varga wrote:
On 26/10/2021 00:37, Brandon Wick wrote:
Hi All,
Hello Brandon,
Hello Brandon, Jill,

Here's the status on the ODL Twitter account.

#################

Unfortunately, due to some staffing changes in the past we are unable to access the ODL Twitter account. (The recovery email associated with the account is not a Linux Foundation email address).

We have made multiple formal requests via Twitter Help Center to recover this data and have, so far, been unsuccessful. We just made another formal request last week and will explore other recovery options if this time is again unsuccessful.
Do we have an update on this?

Thanks,
Robert


Re: [E] Re: [release] Phosphorus SR1 RC

Sangwook Ha
 

Hi Daniel,

The failure of openflowplugin-csit-3node-clustering-bulkomatic-only-phosphorus for integration-distribution-test-phosphorus #230 is because of BindException (testing was aborted), but there would be a few failing test cases even if it was completed normally. And I believe all three failing Jenkins jobs (2 OpenFlow Plugin & 1 OVSDB) are affected by the same clustering issue, which won't be fixed for this release.

Thanks,
Sangwook


On Wed, Nov 24, 2021 at 7:19 AM Daniel de la Rosa <ddelarosa0707@...> wrote:
Thanks Luis

On Tue, Nov 23, 2021 at 4:22 PM Luis Gomez <ecelgp@...> wrote:
OK, int/test changes are merged now.

On Nov 23, 2021, at 3:36 PM, Ha, Sangwook <sangwook.ha@...> wrote:

3 integration/test patches for OpenFlow Plugin are ready for review (submitted one more to address an EOS test case):


Luis, please take a look at the changes.

Thanks,
Sangwook

On Tue, Nov 23, 2021 at 12:08 PM Sangwook Ha via lists.opendaylight.org <sangwook.ha=verizon.com@...> wrote:
In addition to the integration/test change 98642, we need some additional changes for OpenFlow Plugin tests to support the stricter URL requirements & status code change (204 for RPC with empty response):


I'm running some test jobs in the sandbox now, and should be ready for review.

Thanks,
Sangwook

On Tue, Nov 23, 2021 at 11:23 AM Robert Varga <nite@...> wrote:
On 22/11/2021 23:11, Daniel de la Rosa wrote:
>
>
> it seems that there are still BGPCEP, OVSDB and OFP issues
>
> https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/
> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/>

Okay, so BGPCEP should be all clear, the RESTCONF regression blocking
OFP perf tests is resolved.

One of the OVSDB failures has a controller tracker, but we won't be able
to fix it for SR1.

Th eonly outstanding item I am currently tracking is this:
https://git.opendaylight.org/gerrit/c/integration/test/+/98642

Luis, can you review it, please?

So this is what we are getting after all these fixes...


two OFP tests are still failing.. are we ok with picking RC with these two issues? @Robert Varga @Luis Gomez @Ha, Sangwook ?


 

Thanks,
Robert









Re: [OpenDaylight Infrastructure] Gerrit update at 4:00pm PST today.

Jessica Wagantall <jwagantall@...>
 

Hi Team!..

Merging this change seems to have caused an issue bringing the service back. 

I have for now reverted it and will debug it further before attempting to merge again. 
Will let you know next time is ready!

Thanks a ton for your patience!
Jess


Re: [OpenDaylight Infrastructure] Gerrit update at 4:00pm PST today.

Jessica Wagantall <jwagantall@...>
 

Hi Team!.. 

Small reminder.. this is about to start

Thanks!
Jess

On Wed, Nov 24, 2021 at 12:11 PM Jessica Wagantall <jwagantall@...> wrote:
Dear community, 

We have a small change in ODL Gerrit ready to be merged at 4:00pm PST today.

This change will allow links to jira.linuxfoundation.org to be properly directed when
using "LF-Jira" in your commit messages:

We do not expect any service downtime and we expect this to be fairly quick,
however you might notice a small glitch during this time. 
Please know that this will be under control.

Thanks so much!
Jess


[OpenDaylight Infrastructure] Gerrit update at 4:00pm PST today.

Jessica Wagantall <jwagantall@...>
 

Dear community, 

We have a small change in ODL Gerrit ready to be merged at 4:00pm PST today.

This change will allow links to jira.linuxfoundation.org to be properly directed when
using "LF-Jira" in your commit messages:

We do not expect any service downtime and we expect this to be fairly quick,
however you might notice a small glitch during this time. 
Please know that this will be under control.

Thanks so much!
Jess


Re: [E] Re: [release] Phosphorus SR1 RC

Daniel de la Rosa
 

Thanks Luis

On Tue, Nov 23, 2021 at 4:22 PM Luis Gomez <ecelgp@...> wrote:
OK, int/test changes are merged now.

On Nov 23, 2021, at 3:36 PM, Ha, Sangwook <sangwook.ha@...> wrote:

3 integration/test patches for OpenFlow Plugin are ready for review (submitted one more to address an EOS test case):


Luis, please take a look at the changes.

Thanks,
Sangwook

On Tue, Nov 23, 2021 at 12:08 PM Sangwook Ha via lists.opendaylight.org <sangwook.ha=verizon.com@...> wrote:
In addition to the integration/test change 98642, we need some additional changes for OpenFlow Plugin tests to support the stricter URL requirements & status code change (204 for RPC with empty response):


I'm running some test jobs in the sandbox now, and should be ready for review.

Thanks,
Sangwook

On Tue, Nov 23, 2021 at 11:23 AM Robert Varga <nite@...> wrote:
On 22/11/2021 23:11, Daniel de la Rosa wrote:
>
>
> it seems that there are still BGPCEP, OVSDB and OFP issues
>
> https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/
> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/>

Okay, so BGPCEP should be all clear, the RESTCONF regression blocking
OFP perf tests is resolved.

One of the OVSDB failures has a controller tracker, but we won't be able
to fix it for SR1.

Th eonly outstanding item I am currently tracking is this:
https://git.opendaylight.org/gerrit/c/integration/test/+/98642

Luis, can you review it, please?

So this is what we are getting after all these fixes...


two OFP tests are still failing.. are we ok with picking RC with these two issues? @Robert Varga @Luis Gomez @Ha, Sangwook ?


 

Thanks,
Robert









Jenkins jobs: maven-3.8 as default

Robert Varga
 

Hello TSC members,

during infrastructure-side preparation for odlparent-10's requirement of maven-3.8+ in Sulfur, we have discovered an issue with our current JJB setup.

It essentially means that attempts to override job group definitions' use of maven-3.5 are fruitless.

After sparing a bit with Anil on Slack, we have concluded that the cleanest solution is to:
- set our default to mvn38
- remove all current overrides of this default

This would result in all our jobs using maven-3.8, including Silicon and Phosphorus.

This change is purely in our build infrastructure and nothing changes in terms of the ability to build Silicon/Phosphorus projects with maven-3.5+.

In terms of compatibility, I have been using maven-3.8.2+ for all local builds for a couple of months now and experienced no issues at all.

There is another angle to this, which is that maven-3.8.1 is a security, as detailed here:
https://maven.apache.org/docs/3.8.1/release-notes.html#cve-2020-13956
https://maven.apache.org/docs/3.8.1/release-notes.html#cve-2021-26291

Hence we would like to merge https://git.opendaylight.org/gerrit/c/releng/builder/+/98646 and follow that up with a cleanup of superfluous mvn-version directives.

Are there any objections to this plan of action?

Thanks,
Robert