1. TSC@lists.opendaylight.org
  2. Messages
   Date   
Re: Silicon SR1 CSIT check

Daniel de la Rosa
 

Thanks Robert. Sounds like we have two showstoppers then for Silicon SR1 coming from integration Lets see if @Luis Gomez  has time to check it out later this week

On Mon, May 17, 2021 at 11:15 PM Robert Varga <nite@...> wrote:


On 18/05/2021 04:46, Daniel de la Rosa wrote:
> Hello TSC and all
>
> Sorry for the delay. Here is the Silicon SR1 CSIT check for AR#288
>
> https://docs.google.com/spreadsheets/d/1zvD4xgiMlWCgg5ZBvxSRONY_LtLtzzNUeuA06-i7ukc/edit?usp=sharing
> <https://docs.google.com/spreadsheets/d/1zvD4xgiMlWCgg5ZBvxSRONY_LtLtzzNUeuA06-i7ukc/edit?usp=sharing>
>
> Please review at your earliest convenience

I think we have at least two problems.

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/daexim-csit-3node-clustering-basic-only-silicon/321/console.log.gz
is indicating:

> 2021-05-17T03:42:38,062 | ERROR | opendaylight-cluster-data-akka.actor.default-dispatcher-14 | ClusterActorRefProvider          | 205 - org.opendaylight.controller.repackaged-akka - 3.0.8 | No root guardian at [akka.tcp://opendaylight-cluster-data@...:2550]
> java.lang.IllegalArgumentException: Wrong protocol of [akka.tcp://opendaylight-cluster-data@...:2550/], expected [akka]
>       at akka.remote.RemoteActorRef.<init>(RemoteActorRefProvider.scala:671) ~[bundleFile:?]
>       at akka.remote.RemoteActorRefProvider.rootGuardianAt(RemoteActorRefProvider.scala:476) ~[bundleFile:?]

This seems to be a problem in int/test, where these:
./csit/libraries/ConfGen.py
./csit/variables/clustering/member_down.json
./tools/clustering/cluster-deployer/deploy.py

are assuming peer addresses are 'akka.tcp' -- and they are not with Artery.


We also have this:

> 2021-05-17T03:42:38,030 | INFO  | opendaylight-cluster-data-akka.actor.default-dispatcher-14 | Cluster                          | 205 - org.opendaylight.controller.repackaged-akka - 3.0.8 | Cluster Node [akka://opendaylight-cluster-data@...:2550] - No downing-provider-class configured, manual cluster downing required, see https://doc.akka.io/docs/akka/current/typed/cluster.html#downing

which I still need to track down -- it is either int/dist, int/test or
controller's fault.

Regards,
Robert
Re: Silicon SR1 CSIT check

Robert Varga
 

On 18/05/2021 04:46, Daniel de la Rosa wrote:
Hello TSC and all

Sorry for the delay. Here is the Silicon SR1 CSIT check for AR#288

https://docs.google.com/spreadsheets/d/1zvD4xgiMlWCgg5ZBvxSRONY_LtLtzzNUeuA06-i7ukc/edit?usp=sharing
<https://docs.google.com/spreadsheets/d/1zvD4xgiMlWCgg5ZBvxSRONY_LtLtzzNUeuA06-i7ukc/edit?usp=sharing>

Please review at your earliest convenience
I think we have at least two problems.

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/daexim-csit-3node-clustering-basic-only-silicon/321/console.log.gz
is indicating:

2021-05-17T03:42:38,062 | ERROR | opendaylight-cluster-data-akka.actor.default-dispatcher-14 | ClusterActorRefProvider | 205 - org.opendaylight.controller.repackaged-akka - 3.0.8 | No root guardian at [akka.tcp://opendaylight-cluster-data@...:2550]
java.lang.IllegalArgumentException: Wrong protocol of [akka.tcp://opendaylight-cluster-data@...:2550/], expected [akka]
at akka.remote.RemoteActorRef.<init>(RemoteActorRefProvider.scala:671) ~[bundleFile:?]
at akka.remote.RemoteActorRefProvider.rootGuardianAt(RemoteActorRefProvider.scala:476) ~[bundleFile:?]
This seems to be a problem in int/test, where these:
./csit/libraries/ConfGen.py
./csit/variables/clustering/member_down.json
./tools/clustering/cluster-deployer/deploy.py

are assuming peer addresses are 'akka.tcp' -- and they are not with Artery.


We also have this:

2021-05-17T03:42:38,030 | INFO | opendaylight-cluster-data-akka.actor.default-dispatcher-14 | Cluster | 205 - org.opendaylight.controller.repackaged-akka - 3.0.8 | Cluster Node [akka://opendaylight-cluster-data@...:2550] - No downing-provider-class configured, manual cluster downing required, see https://doc.akka.io/docs/akka/current/typed/cluster.html#downing
which I still need to track down -- it is either int/dist, int/test or
controller's fault.

Regards,
Robert

?
OpenPGP_signature

Silicon SR1 CSIT check

Daniel de la Rosa
 

Hello TSC and all

Sorry for the delay. Here is the Silicon SR1 CSIT check for AR#288


Please review at your earliest convenience


Thanks


On Thu, May 13, 2021 at 6:21 AM Robert Varga <nite@...> wrote:
Okay, this now all merged up. Next autorelease should have everything we
need for Silicon SR1.

Sorry about the delays, there were all sorts of shenanigans :(

Regards,
Robert



On 11/05/2021 03:40, Anil Belur wrote:
> I'm ok with postponing the code freeze. It's better to postpone a
> release than do additional releases. ;P
> The permissions have been reverted now. Cheers 
>
> On Tue, May 11, 2021 at 6:28 AM Daniel de la Rosa
> <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
>
>     Fine with me. So Anil Belur, can you pospone code freeze for two days ? 
>
>     Thanks 
>
>     On Mon, May 10, 2021 at 12:42 PM Robert Varga <nite@...
>     <mailto:nite@...>> wrote:
>
>         On 03/05/2021 04:57, Daniel de la Rosa wrote:
>         > Hells TSC and all
>         >
>         > Correction. Code freeze will be on May 10th at 10 am pst
>
>         Hey everyone,
>
>         unfortunately I missed this deadline, sorry.
>
>         Overall I have all MRI projects and BGPCEP done, with a notable
>         exception of NETCONF.
>
>         This would mean either not picking up anything of the ~20 patches
>         pending review in NETCONF -- and I would prefer not to do that,
>         as they
>         are really things that needs to be backported to Aluminium SR4
>         as well.
>
>         Any objections to a day or two extension to finish this up and
>         roll out
>         the MRI updates in time for Wednesday night's autorelease?
>
>         Thanks,
>         Robert
>
>         >
>         > Thanks
>         >
>         > On Thu, Apr 29, 2021 at 10:30 PM Daniel de la Rosa
>         > <ddelarosa0707@... <mailto:ddelarosa0707@...>
>         <mailto:ddelarosa0707@...
>         <mailto:ddelarosa0707@...>>> wrote:
>         >
>         >     Hello TSC and all
>         >
>         >     We are going to code freeze Silicon for all Managed
>         Projects ( cut
>         >     and lock release branches ) on Thursday May 6th 
>         >
>         >     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/Silicon+SR1+Release+Checklist
>         <https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist>
>         >   
>          <https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist
>         <https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist>>
>         >
>         >   
>          https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
>         <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>
>         >   
>          <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
>         <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>>
>         >
>         >
>         >
>         >
>         >
>
>
>
>
>

Re: [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)

Luis Gomez
 

+1 to archive

On May 13, 2021, at 11:37 PM, Anil Belur <abelur@...> wrote:

As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.  


TSC members, Please vote here. 


On Tue, Apr 27, 2021 at 1:11 PM Anil Belur <abelur@...> wrote:
As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:

* alt-datastores
* bier
* coe
* detnet
* dluxapps
* groupbasedpolicy
* nemo
* honeycomb/vbd
* of-config
* opflex
* packetcable
* sfc
* snmp4sdn
* snmp
* telemetry
* tsdr
* usc

I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.

TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).

Regards,
Anil
 

On Sun, Mar 28, 2021 at 10:42 AM Anil Belur via lists.opendaylight.org <abelur=linuxfoundation.org@...> wrote:
Hello TSC team:

As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months).

The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit. 
1. usc:
Total 3674 (delta 0), reused 3674 (delta 0)
* master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago)
2. packetcable:
* master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago)
3. opflex:
* master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago)

Once the review is approved by the TSC:
1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo.
2. The $PROJECT will be set to an inactive state on Gerrit.
3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit.  

Please add if I missed any projects, refer to the logs attached. 

[1.] https://www.opendaylight.org/about/lifecycle-releases

Regards,
Anil
Re: [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)

Anil Belur
 

As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.  


TSC members, Please vote here. 


On Tue, Apr 27, 2021 at 1:11 PM Anil Belur <abelur@...> wrote:
As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:

* alt-datastores
* bier
* coe
* detnet
* dluxapps
* groupbasedpolicy
* nemo
* honeycomb/vbd
* of-config
* opflex
* packetcable
* sfc
* snmp4sdn
* snmp
* telemetry
* tsdr
* usc

I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.

TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).

Regards,
Anil
 

On Sun, Mar 28, 2021 at 10:42 AM Anil Belur via lists.opendaylight.org <abelur=linuxfoundation.org@...> wrote:
Hello TSC team:

As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months).

The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit.
1. usc:
Total 3674 (delta 0), reused 3674 (delta 0)
* master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago)
2. packetcable:
* master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago)
3. opflex:
* master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago)

Once the review is approved by the TSC:
1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo.
2. The $PROJECT will be set to an inactive state on Gerrit.
3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit.  

Please add if I missed any projects, refer to the logs attached. 

[1.] https://www.opendaylight.org/about/lifecycle-releases

Regards,
Anil
Re: [E] Re: [OpenDaylight TSC] ODL Developer Event topics due 5/14

Ghazisaidi, Navid
 

Another one here:

https://wiki.lfnetworking.org/display/LN/2021-06-DD+-+ODL%3A+Release+Notes+Automation

 

Thanks,

Navid

 

 

From: <TSC@...> on behalf of Luis Gomez <ecelgp@...>
Date: Thursday, May 13, 2021 at 10:37 PM
To: Casey Cain <ccain@...>
Cc: TSC <TSC@...>, discuss <discuss@...>
Subject: [E] Re: [OpenDaylight TSC] ODL Developer Event topics due 5/14

 

Here is one:

 

 

BR/Luis



On May 13, 2021, at 12:11 PM, Casey Cain <ccain@...> wrote:

 

Hello, everyone 

 

I would like to remind everyone that the Developer & Testing Form topic submission deadline is tomorrow, Friday the 14th of June.  Currently, we do not have any submitted topics.  Please ensure that you submit your proposed topics as soon as possible.

 

Event Details:

 

Thanks,

Casey Cain

Technical Program Manager / Community Architect

Linux Foundation

_________________

IRC: CaseyLF

WeChat: okaru6

Voice: +1.408.641.0193



 
Re: ODL Developer Event topics due 5/14

Luis Gomez
 

Here is one:


BR/Luis

On May 13, 2021, at 12:11 PM, Casey Cain <ccain@...> wrote:

Hello, everyone 

I would like to remind everyone that the Developer & Testing Form topic submission deadline is tomorrow, Friday the 14th of June.  Currently, we do not have any submitted topics.  Please ensure that you submit your proposed topics as soon as possible.

Event Details:

Thanks,
Casey Cain
Technical Program Manager / Community Architect
Linux Foundation
_________________
IRC: CaseyLF
WeChat: okaru6
Voice: +1.408.641.0193
ODL Developer Event topics due 5/14

Casey Cain
 

Hello, everyone 

I would like to remind everyone that the Developer & Testing Form topic submission deadline is tomorrow, Friday the 14th of June.  Currently, we do not have any submitted topics.  Please ensure that you submit your proposed topics as soon as possible.

Event Details:

Thanks,
Casey Cain
Technical Program Manager / Community Architect
Linux Foundation
_________________
IRC: CaseyLF
WeChat: okaru6
Voice: +1.408.641.0193
Re: [E] Re: [release] int/pack revival

Guillaume Lambert
 

+1

 

De : release@... [mailto:release@...] De la part de navid.ghazisaidi via lists.opendaylight.org
Envoyé : jeudi 13 mai 2021 06:51
À : Luis Gomez; Venkatrangan Govindarajan
Cc : Release; TSC
Objet : [E] Re: [release] int/pack revival

 

+1

 

On May 12, 2021 21:37, Venkatrangan Govindarajan <gvrangan@...> wrote:

+1

 

On Wed, May 12, 2021, 23:42 Luis Gomez <ecelgp@...> wrote:

Hi TSC and other community members,

As discussed in last week TSC call we plan to revive integation/packaging project to start the docker/helm work there.

Since we need TSC approval to revive a project, can we please start a TSC vote here?

Here is my +1

BR/Luis



_________________________________________________________________________________________________________________________

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: [release] Silicon SR1 code freeze

Robert Varga
 

Okay, this now all merged up. Next autorelease should have everything we
need for Silicon SR1.

Sorry about the delays, there were all sorts of shenanigans :(

Regards,
Robert

On 11/05/2021 03:40, Anil Belur wrote:
I'm ok with postponing the code freeze. It's better to postpone a
release than do additional releases. ;P
The permissions have been reverted now. Cheers 

On Tue, May 11, 2021 at 6:28 AM Daniel de la Rosa
<ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:

Fine with me. So Anil Belur, can you pospone code freeze for two days ? 

Thanks 

On Mon, May 10, 2021 at 12:42 PM Robert Varga <nite@...
<mailto:nite@...>> wrote:

On 03/05/2021 04:57, Daniel de la Rosa wrote:
> Hells TSC and all
>
> Correction. Code freeze will be on May 10th at 10 am pst

Hey everyone,

unfortunately I missed this deadline, sorry.

Overall I have all MRI projects and BGPCEP done, with a notable
exception of NETCONF.

This would mean either not picking up anything of the ~20 patches
pending review in NETCONF -- and I would prefer not to do that,
as they
are really things that needs to be backported to Aluminium SR4
as well.

Any objections to a day or two extension to finish this up and
roll out
the MRI updates in time for Wednesday night's autorelease?

Thanks,
Robert

>
> Thanks
>
> On Thu, Apr 29, 2021 at 10:30 PM Daniel de la Rosa
> <ddelarosa0707@... <mailto:ddelarosa0707@...>
<mailto:ddelarosa0707@...
<mailto:ddelarosa0707@...>>> wrote:
>
>     Hello TSC and all
>
>     We are going to code freeze Silicon for all Managed
Projects ( cut
>     and lock release branches ) on Thursday May 6th 
>
>     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/Silicon+SR1+Release+Checklist
<https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist>
>   
 <https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist
<https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist>>
>
>   
 https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
<https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>
>   
 <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
<https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>>
>
>
>
>
>




?
OpenPGP_signature

[E] Re: [release] int/pack revival

Ghazisaidi, Navid
 

+1

On May 12, 2021 21:37, Venkatrangan Govindarajan <gvrangan@...> wrote:
+1

On Wed, May 12, 2021, 23:42 Luis Gomez <ecelgp@...> wrote:

Hi TSC and other community members,

As discussed in last week TSC call we plan to revive integation/packaging project to start the docker/helm work there.

Since we need TSC approval to revive a project, can we please start a TSC vote here?

Here is my +1

BR/Luis
Re: [release] int/pack revival

Venkatrangan Govindarajan
 

+1


On Wed, May 12, 2021, 23:42 Luis Gomez <ecelgp@...> wrote:
Hi TSC and other community members,

As discussed in last week TSC call we plan to revive integation/packaging project to start the docker/helm work there.

Since we need TSC approval to revive a project, can we please start a TSC vote here?

Here is my +1

BR/Luis
int/pack revival

Luis Gomez
 

Hi TSC and other community members,

As discussed in last week TSC call we plan to revive integation/packaging project to start the docker/helm work there.

Since we need TSC approval to revive a project, can we please start a TSC vote here?

Here is my +1

BR/Luis
Re: [release] ODL Helm chart meeting

Luis Gomez
 

Sorry guys, yesterday I had an emergency and I could not attend the meeting. All is fine now, I hope we can finally resume work next week.

As per last TSC call, we need a vote to revive int/pack project in order to use it for docker/helm. Let me start that in another thread.

BR/Luis


On May 7, 2021, at 9:52 AM, Casey Cain <ccain@...> wrote:

I've updated the meeting to take place on Tuesdays going forward.  :)

Best,
Casey Cain
Technical Program Manager / Community Architect
Linux Foundation
_________________
IRC: CaseyLF
WeChat: okaru6
Voice: +1.408.641.0193


On Fri, May 7, 2021 at 9:44 AM manoj chokka <cmanoj8@...> wrote:
Tuesday is ok for me too.

BR
Manoj

On Fri, May 7, 2021 at 7:38 PM Jeff Hartley <intensifysecurity@...> wrote:
Agreed on Tuesdays.

-Jeff


On Thu, May 6, 2021 at 10:21 PM Luis Gomez <ecelgp@...> wrote:
Tuesday is better for me in general.

On May 6, 2021, at 6:28 PM, Anil Belur <abelur@...> wrote:

Hi Luis, 

Is the new meeting time (Tuesday 6:30-7:00 PM PDT) going to change for all meetings going forward? 
It's okay for me. Is everyone else ok with this time change from Monday to Tuesday? Please reply here.

Cheers,
Anil

On Tue, May 4, 2021 at 2:55 PM Luis Gomez <ecelgp@...> wrote:
Hi Anil,

Please move the meeting to Tuesday same time if nobody objects as Monday turns out to be very busy for me.

BR/Luis

On May 3, 2021, at 6:41 PM, Anil Belur <abelur@...> wrote:

Hi Luis, 

The last two weeks there was no attendance here, please let us know if the meeting needs to be moved/rescheduled to a diff time that works for everyone.

Cheers,
Anil 

On Mon, Apr 26, 2021 at 12:59 PM Casey Cain <ccain@...> wrote:
I've created the meeting.  :)

Please let me know if you need anything else. 

Best,
Casey Cain
Technical Program Manager / Community Architect
Linux Foundation
_________________
IRC: CaseyLF
WeChat: okaru6
Voice: +1.408.641.0193


On Sun, Apr 25, 2021 at 7:34 PM Anil Belur <abelur@...> wrote:
Hi Luis, 

I'll message Casey to send out a meeting request, if not I'll start a zoom meeting for this week so that we can start the discussions. 

Cheers,
Anil

On Mon, Apr 26, 2021 at 11:10 AM Luis Gomez <ecelgp@...> wrote:
Hi Casey,

Can you please set "Helm Chart" meeting every Monday 6:30-7:00 PM PDT starting this Monday?

Thanks/Luis
TSC Meeting for May 13 , 2021 at 10 pm Pacific

Guillaume Lambert
 

Hello OpenDaylight Community,

 Next TSC meeting is May 13, 2021 at 10 pm Pacific Time.
The agenda proposal and the connection details for this meeting are available at the following URL:
https://wiki.opendaylight.org/x/BCEF

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.

As I will be on PTO and vacation these next days, Daniel in CC gently accepted to be my proxy for this meeting.

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: JSONRPC test plan for Phosphorous and beyond

Daniel de la Rosa
 

Hello Richard 

We just need you to check on the CSIT for the upcoming releases... We have asked you on some jsonrpc issues with Silicon GA


but we didnt get any response. No worries, because we will ask you again for Silicon SR1 :) I'll cc you when the time comes


Thanks 

On Mon, May 10, 2021 at 2:53 AM Richard Kosegi <richard.kosegi@...> wrote:
Hi Daniel,

I think I'll be able to support the JSONRPC project in the foreseeable future.

Any specific action is required?

Regards,
Richard

On Fri, 7 May 2021 at 21:54, Daniel de la Rosa <ddelarosa0707@...> wrote:
Hello Richard and Anton 

We would like to know if you are planning to keep supporting JSONRPC as a managed project and everything that implies, or transition it back to self managed mode. 

Please let us know as soon as possible

Thanks 
Re: [release] Silicon SR1 code freeze

Anil Belur
 

I'm ok with postponing the code freeze. It's better to postpone a release than do additional releases. ;P
The permissions have been reverted now. Cheers 

On Tue, May 11, 2021 at 6:28 AM Daniel de la Rosa <ddelarosa0707@...> wrote:
Fine with me. So Anil Belur, can you pospone code freeze for two days ? 

Thanks 

On Mon, May 10, 2021 at 12:42 PM Robert Varga <nite@...> wrote:
On 03/05/2021 04:57, Daniel de la Rosa wrote:
> Hells TSC and all
>
> Correction. Code freeze will be on May 10th at 10 am pst

Hey everyone,

unfortunately I missed this deadline, sorry.

Overall I have all MRI projects and BGPCEP done, with a notable
exception of NETCONF.

This would mean either not picking up anything of the ~20 patches
pending review in NETCONF -- and I would prefer not to do that, as they
are really things that needs to be backported to Aluminium SR4 as well.

Any objections to a day or two extension to finish this up and roll out
the MRI updates in time for Wednesday night's autorelease?

Thanks,
Robert

>
> Thanks
>
> On Thu, Apr 29, 2021 at 10:30 PM Daniel de la Rosa
> <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
>
>     Hello TSC and all
>
>     We are going to code freeze Silicon for all Managed Projects ( cut
>     and lock release branches ) on Thursday May 6th 
>
>     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/Silicon+SR1+Release+Checklist
>     <https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist>
>
>     https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
>     <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>
>
>
>
>
>

Re: [release] Silicon SR1 code freeze

Daniel de la Rosa
 

Fine with me. So Anil Belur, can you pospone code freeze for two days ? 

Thanks 

On Mon, May 10, 2021 at 12:42 PM Robert Varga <nite@...> wrote:
On 03/05/2021 04:57, Daniel de la Rosa wrote:
> Hells TSC and all
>
> Correction. Code freeze will be on May 10th at 10 am pst

Hey everyone,

unfortunately I missed this deadline, sorry.

Overall I have all MRI projects and BGPCEP done, with a notable
exception of NETCONF.

This would mean either not picking up anything of the ~20 patches
pending review in NETCONF -- and I would prefer not to do that, as they
are really things that needs to be backported to Aluminium SR4 as well.

Any objections to a day or two extension to finish this up and roll out
the MRI updates in time for Wednesday night's autorelease?

Thanks,
Robert

>
> Thanks
>
> On Thu, Apr 29, 2021 at 10:30 PM Daniel de la Rosa
> <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
>
>     Hello TSC and all
>
>     We are going to code freeze Silicon for all Managed Projects ( cut
>     and lock release branches ) on Thursday May 6th 
>
>     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/Silicon+SR1+Release+Checklist
>     <https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist>
>
>     https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
>     <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>
>
>
>
>
>

Re: [release] Silicon SR1 code freeze

Robert Varga
 

On 03/05/2021 04:57, Daniel de la Rosa wrote:
Hells TSC and all

Correction. Code freeze will be on May 10th at 10 am pst
Hey everyone,

unfortunately I missed this deadline, sorry.

Overall I have all MRI projects and BGPCEP done, with a notable
exception of NETCONF.

This would mean either not picking up anything of the ~20 patches
pending review in NETCONF -- and I would prefer not to do that, as they
are really things that needs to be backported to Aluminium SR4 as well.

Any objections to a day or two extension to finish this up and roll out
the MRI updates in time for Wednesday night's autorelease?

Thanks,
Robert


Thanks

On Thu, Apr 29, 2021 at 10:30 PM Daniel de la Rosa
<ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:

Hello TSC and all

We are going to code freeze Silicon for all Managed Projects ( cut
and lock release branches ) on Thursday May 6th 

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/Silicon+SR1+Release+Checklist
<https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Checklist>

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




?
OpenPGP_signature

Re: JSONRPC test plan for Phosphorous and beyond

Richard Kosegi <richard.kosegi@...>
 

Hi Daniel,

I think I'll be able to support the JSONRPC project in the foreseeable future.

Any specific action is required?

Regards,
Richard


On Fri, 7 May 2021 at 21:54, Daniel de la Rosa <ddelarosa0707@...> wrote:
Hello Richard and Anton 

We would like to know if you are planning to keep supporting JSONRPC as a managed project and everything that implies, or transition it back to self managed mode. 

Please let us know as soon as possible

Thanks 
701 - 720 of 14407