Date   

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


Re: 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


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: 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: 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


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






Re: [E] [OpenDaylight TSC] TSC Meeting for January 20, 2022 at 10 pm Pacific

Ghazisaidi, Navid
 

Hi All, 

I won't be able to attend tonight's call. Sangwook will proxy me.

Regards,
Navid

On Wed, Jan 19, 2022 at 5:54 AM Guillaume Lambert via lists.opendaylight.org <guillaume.lambert=orange.com@...> wrote:

Hello OpenDaylight Community,


The next TSC meeting is January 20 , 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/3DIEAQ


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] Log4Shell impacts on ODL releases

Chokka, Manoj
 

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: 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


Re: Phosphorus SR2 code freeze

Robert Varga
 

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.

Sorry for the delay,
Robert

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-phosphorus-mvn35-openjdk11/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-phosphorus-mvn35-openjdk11/>
Thanks
On Mon, Jan 10, 2022 at 8:00 AM Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
Hello TSC and all
We are going to code freeze Phosphorus for all Managed Projects (
cut and lock release branches ) on Monday January 17th 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+SR2+Release+Checklist
<https://wiki.opendaylight.org/display/ODL/Phosphorus+SR2+Release+Checklist>
https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
<https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>
--
Daniel de la Rosa
ODL Release Manager


Re: Log4Shell impacts on ODL releases

Daniel de la Rosa
 

Hello Robert 

On Mon, Jan 10, 2022 at 5:42 AM Robert Varga <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? 
 

- Phosphorus is currently in its normal support period, hence will have
this (and other) issues resolved in the upcoming run-of-the-mill SR2

- Sulfur release train currently mirrors Phosphorus in the parts which
are affected, it will be updated at the same time and Sulfur GA will be
on par with Phosphorus SR2

Regards,
Robert






Re: Phosphorus SR2 code freeze

Daniel de la Rosa
 

Hello all

@Robert Varga i think we can pick a Phosphorus SR2 RC this week but let me know your thoughts based on the current AR state


Thanks

On Mon, Jan 10, 2022 at 8:00 AM Daniel de la Rosa <ddelarosa0707@...> wrote:
Hello TSC and all

We are going to code freeze Phosphorus for all Managed Projects ( cut and lock release branches ) on Monday January 17th 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+SR2+Release+Checklist

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

--
Daniel de la Rosa
ODL Release Manager


TSC Meeting for January 20, 2022 at 10 pm Pacific

Guillaume Lambert
 

Hello OpenDaylight Community,


The next TSC meeting is January 20 , 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/3DIEAQ


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.


RTD Job - automation rule to activate branch/tag

Anil Belur
 

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: Unscheduled Silicon SR4 release

Daniel de la Rosa
 

Hello Robert and all. Sure but next tsc meeting is on January 20th. Hopefully this can wait until then 

Thanks 

On Mon, Jan 10, 2022 at 5:46 AM Robert Varga <nite@...> wrote:
Hello everyone,

as per my previous email, we need to spin an unscheduled security-driven
Service Release on the Silicon release train.

The MRI part of this is already done and the projects are ready to
integrate here: https://git.opendaylight.org/gerrit/q/topic:mri-silicon-sr4

I will raise the ticket to get the patches merged and we should be
releasing Silicon SR4 as soon as practical. Daniel, can you drive that
conversation at the next TSC meeting, please?

Thanks,
Robert





--
Daniel de la Rosa
ODL Release Manager


Phosphorus SR2 code freeze

Daniel de la Rosa
 

Hello TSC and all

We are going to code freeze Phosphorus for all Managed Projects ( cut and lock release branches ) on Monday January 17th 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+SR2+Release+Checklist

https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
--
Daniel de la Rosa
ODL Release Manager


Unscheduled Silicon SR4 release

Robert Varga
 

Hello everyone,

as per my previous email, we need to spin an unscheduled security-driven Service Release on the Silicon release train.

The MRI part of this is already done and the projects are ready to integrate here: https://git.opendaylight.org/gerrit/q/topic:mri-silicon-sr4

I will raise the ticket to get the patches merged and we should be releasing Silicon SR4 as soon as practical. Daniel, can you drive that conversation at the next TSC meeting, please?

Thanks,
Robert


Log4Shell impacts on ODL releases

Robert Varga
 

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

- Phosphorus is currently in its normal support period, hence will have this (and other) issues resolved in the upcoming run-of-the-mill SR2

- Sulfur release train currently mirrors Phosphorus in the parts which are affected, it will be updated at the same time and Sulfur GA will be on par with Phosphorus SR2

Regards,
Robert


Season's Greetings and TSC Meeting for January 6, 2022 at 10 pm Pacific

Guillaume Lambert
 

Hello OpenDaylight Community,

 

I would like to start this message by wishing you a happy new year.

May 2022 bring everyone more health and happiness and success.


The next TSC meeting is January 6 , 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/5S4EAQ


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.

261 - 280 of 14296