1. release@lists.opendaylight.org
  2. Messages
   Date   
controller-3.0.16 released

Robert Varga
 

Hello everyone,

controller-3.0.16 has been released. The only change is adoption of odlparent-8.1.9 and related upstreams.

Enjoy,
Robert

?
OpenPGP_signature

yangtools-7.0.13 released

Robert Varga
 

Hello everyone,

yangtools-7.0.13 has been released. Release notes are available here: https://jira.opendaylight.org/secure/ReleaseNote.jspa?projectId=10188&version=13120

Following issues have been resolved:

Improvement
[YANGTOOLS-1391] - Use java.lang.ref.Cleaner in GuavaSchemaSourceCache
Additionally, this release adopts odlparent-9.0.13.

Enjoy,
Robert

?
OpenPGP_signature

mdsal-7.0.14 released

Robert Varga
 

Hello everyone,

mdsal-7.0.14 has been released. The only change is adoption of odlparent-8.1.9 and yangtools-6.0.12.

Enjoy,
Robert

?
OpenPGP_signature

yangtools-6.0.12 released

Robert Varga
 

Hello everyone,

yangtools-6.0.12 has been released. This release only adopts odlparent-8.1.9.

Enjoy,
Robert

?
OpenPGP_signature

infrautils-2.0.13 released

Robert Varga
 

Hello everyone,

infrautils-2.0.13 has been released. This release adopts odlparent-9.0.13.

Enjoy,
Robert

?
OpenPGP_signature

infrautils-1.9.15 released

Robert Varga
 

Hello everyone,

infrautils-1.9.15 has been released. This release adopts odlparent-8.1.9.

Enjoy,
Robert

?
OpenPGP_signature

Re: [documentation] RTD Job - automation rule to activate branch/tag

Luis Gomez
 

Yeah, I do not see daexim stable/phosphorus docs for example: https://docs.opendaylight.org/projects/daexim/en/latest/, so it did not work, at least fully :(

Can you please make sure at least these MSI projects get the stable/phosphorous branch activated:

    odl-daexim
    odl-jsonrpc
    odl-lispflowmapping
    odl-openflowplugin
    opendaylight-ovsdb
    odl-transportpce



On Jan 24, 2022, at 3:43 PM, Anil Shashikumar Belur <abelur@...> wrote:

Greetings Luis:

I've run the script to activate all the projects. Please check and let me know if all the versions are active. 

Regards,
Anil


On Sun, Jan 23, 2022 at 4:39 AM Luis Gomez <ecelgp@...> wrote:
Hi Anil,

Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the projects:


I only have admin rights on distribution and I do not think at this moment we can afford to wait for all the project maintainers to do this individually.

Additionally, this admin person can add the rule you suggest to all the projects so that we do not need to run the script in future.

Once this is done, we can unblock this gerrit:


BR/Luis


On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur
odlparent-9.0.13 released

Robert Varga
 

Hello everyone,

odlparent-9.0.13 has been released. The release notes are here: https://jira.opendaylight.org/secure/ReleaseNote.jspa?projectId=10149&version=13123, fixing one regression:

Bug
[ODLPARENT-279] - Netty's epoll(2) support does not work
The full changelog is available here:
https://github.com/opendaylight/odlparent/blob/9.0.x/docs/NEWS.rst#version-9013

Enjoy,
Robert

?
OpenPGP_signature

odlparent-8.1.9 released

Robert Varga
 

Hello everyone,

odlparent-8.1.9 has been released. The release notes are here: https://jira.opendaylight.org/secure/ReleaseNote.jspa?projectId=10149&version=13128, fixing one regression:

Bug
[ODLPARENT-279] - Netty's epoll(2) support does not work
The full changelog is available here:
https://github.com/opendaylight/odlparent/blob/8.1.x/docs/NEWS.rst#version-819

Enjoy,
Robert

?
OpenPGP_signature

Re: [documentation] RTD Job - automation rule to activate branch/tag

Anil Belur
 

Greetings Luis:

I've run the script to activate all the projects. Please check and let me know if all the versions are active. 

Regards,
Anil


On Sun, Jan 23, 2022 at 4:39 AM Luis Gomez <ecelgp@...> wrote:
Hi Anil,

Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the projects:


I only have admin rights on distribution and I do not think at this moment we can afford to wait for all the project maintainers to do this individually.

Additionally, this admin person can add the rule you suggest to all the projects so that we do not need to run the script in future.

Once this is done, we can unblock this gerrit:


BR/Luis


On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur
Re: Phosphorus SR2 code freeze

Robert Varga
 

On 20/01/2022 11:24, Robert Varga wrote:
On 20/01/2022 08:25, Daniel de la Rosa wrote:
Hello all
Hello Daniel,

@Robert Varga <mailto:nite@...> i think we can pick a Phosphorus SR2 RC this week but let me know your thoughts based on the current AR state
Unfortunately I am still waiting for last round of updates for CONTROLLER-2025 to push out the MRI update. I expect this to happen this week.
We're *almost* there, except the ODLPARENT-279 issue, plus BGPCEP integration also found https://jira.opendaylight.org/browse/MDSAL-718.

Both should take a few days to clear.

REgards,
Robert

?
OpenPGP_signature

Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases

Robert Varga
 

On 21/01/2022 07:31, Robert Varga wrote:
On 20/01/2022 11:30, Robert Varga wrote:
    - Silicon is currently in its Security Support period past its last
    scheduled Service Release, hence will receive an unscheduled
    security-driven SR4 in near future


We can review this in the TSC but I think we can release Silicon SR4 after Phosphorus SR2 and before Sulfur. Thoughts?
Actually, these updates are already pushed out on the branch, i.e. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/537/ should be okay to release.
So pretty much everything is actually okay, except BGPCEP, which is showing regressions around TCP-MD5 handling. This is most probably related to netty-4.1.72+ upgrade in OSGi environment.
https://jira.opendaylight.org/browse/ODLPARENT-279 tracks this. It is also affecting Phosphorus SR2 (but that also has a different problem).

Regards,
Robert

?
OpenPGP_signature

Re: [documentation] RTD Job - automation rule to activate branch/tag

Luis Gomez
 

Hi Anil,

Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the projects:


I only have admin rights on distribution and I do not think at this moment we can afford to wait for all the project maintainers to do this individually.

Additionally, this admin person can add the rule you suggest to all the projects so that we do not need to run the script in future.

Once this is done, we can unblock this gerrit:


BR/Luis


On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur
Re: [OpenDaylight TSC] RTD Job - automation rule to activate branch/tag

Charles Eckel <eckelcu@...>
 

Hi Anil,

Thanks for pointing this out. I have been meaning to spend some time updating the Unimgr docs, and this is good to know. 
BTW, there is an open source themed Hackathon associated with NANOG 84,

Any interest in an OpenDaylight docs project team?

Cheers,
Charles

On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur
Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases

Robert Varga
 

On 20/01/2022 11:30, Robert Varga wrote:
    - Silicon is currently in its Security Support period past its last
    scheduled Service Release, hence will receive an unscheduled
    security-driven SR4 in near future


We can review this in the TSC but I think we can release Silicon SR4 after Phosphorus SR2 and before Sulfur. Thoughts?
Actually, these updates are already pushed out on the branch, i.e. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/537/ should be okay to release.
So pretty much everything is actually okay, except BGPCEP, which is showing regressions around TCP-MD5 handling. This is most probably related to netty-4.1.72+ upgrade in OSGi environment.

Regards,
Robert

?
OpenPGP_signature

Re: [E] Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases

Daniel de la Rosa
 

Hello Manoj, Robert and all

As suggested, this is a proposed schedule to release Silicon SR4. It's a bit accelerated but I think we can make it work


Please let me know if this works for you

Thanks 

On Thu, Jan 20, 2022 at 3:30 AM Chokka, Manoj <manoj.chokka@...> wrote:
Hi Daniel,

Since the changes are already done, could you prioritize silicon-SR4 first and then others.

Thank you,

BR, Manoj

On Thu, Jan 20, 2022 at 4:01 PM Robert Varga <nite@...> wrote:
On 20/01/2022 08:26, Daniel de la Rosa wrote:
> Hello Robert

Hey Daniel,

> On Mon, Jan 10, 2022 at 5:42 AM Robert Varga <nite@...
> <mailto:nite@...>> wrote:
>
>     Hello everyone,
>
>     these winter holidays we got a present in the form of Log4Shell, which
>     affects pretty much all artifacts we have ever released.
>
>     As per our release lifecycle rules, this means that:
>
>     - all release trains up to and including Aluminium are past their
>     End of
>     Life and will not be receiving a community-driven release
>
>     - Silicon is currently in its Security Support period past its last
>     scheduled Service Release, hence will receive an unscheduled
>     security-driven SR4 in near future
>
>
> We can review this in the TSC but I think we can release Silicon SR4
> after Phosphorus SR2 and before Sulfur. Thoughts?

Actually, these updates are already pushed out on the branch, i.e.
https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/537/
should be okay to release.

Regards,
Robert
aaa-0.14.8 released

Robert Varga
 

Hello everyone,

aaa-0.14.8 has been released. The only difference is adoption of odlparent-9.0.12 and related MRI upstreams.

Enjoy,
Robert

?
OpenPGP_signature

controller-4.0.8 released

Robert Varga
 

Hello everyone,

controller-4.0.8 has been released, the release notes are here:
https://jira.opendaylight.org/secure/ReleaseNote.jspa?projectId=10113&version=12906.

The following issues were addressed relative to 4.0.7:

Task
[CONTROLLER-2027] - Upgrade akka to 2.6.18
Bug
[CONTROLLER-2023] - Test logs polluted by ConfigurationException
[CONTROLLER-2025] - Fail to update entity ownership after owner is killed

Enjoy,
Robert

?
OpenPGP_signature

Re: [E] Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases

Chokka, Manoj <manoj.chokka@...>
 

Hi Daniel,

Since the changes are already done, could you prioritize silicon-SR4 first and then others.

Thank you,

BR, Manoj

On Thu, Jan 20, 2022 at 4:01 PM Robert Varga <nite@...> wrote:
On 20/01/2022 08:26, Daniel de la Rosa wrote:
> Hello Robert

Hey Daniel,

> On Mon, Jan 10, 2022 at 5:42 AM Robert Varga <nite@...
> <mailto:nite@...>> wrote:
>
>     Hello everyone,
>
>     these winter holidays we got a present in the form of Log4Shell, which
>     affects pretty much all artifacts we have ever released.
>
>     As per our release lifecycle rules, this means that:
>
>     - all release trains up to and including Aluminium are past their
>     End of
>     Life and will not be receiving a community-driven release
>
>     - Silicon is currently in its Security Support period past its last
>     scheduled Service Release, hence will receive an unscheduled
>     security-driven SR4 in near future
>
>
> We can review this in the TSC but I think we can release Silicon SR4
> after Phosphorus SR2 and before Sulfur. Thoughts?

Actually, these updates are already pushed out on the branch, i.e.
https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/537/
should be okay to release.

Regards,
Robert
Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases

Robert Varga
 

On 20/01/2022 08:26, Daniel de la Rosa wrote:
Hello Robert
Hey Daniel,

On Mon, Jan 10, 2022 at 5:42 AM Robert Varga <nite@... <mailto:nite@...>> wrote:
Hello everyone,
these winter holidays we got a present in the form of Log4Shell, which
affects pretty much all artifacts we have ever released.
As per our release lifecycle rules, this means that:
- all release trains up to and including Aluminium are past their
End of
Life and will not be receiving a community-driven release
- Silicon is currently in its Security Support period past its last
scheduled Service Release, hence will receive an unscheduled
security-driven SR4 in near future
We can review this in the TSC but I think we can release Silicon SR4 after Phosphorus SR2 and before Sulfur. Thoughts?
Actually, these updates are already pushed out on the branch, i.e. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/537/ should be okay to release.

Regards,
Robert

?
OpenPGP_signature

381 - 400 of 20634