Date   

Re: [Transportpce-dev] [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

Guillaume Lambert
 

+ TSC and releases Mailing List

https://git.opendaylight.org/gerrit/c/transportpce/+/87715



De : Transportpce-dev@... [Transportpce-dev@...] de la part de Guillaume Lambert via Lists.Opendaylight.Org [guillaume.lambert=orange.com@...]
Envoyé : samedi 15 février 2020 14:12
À : THOUENON Gilles TGI/OLN; Luis Gomez; RENAIS Olivier TGI/OLN
Cc : Transportpce-dev@...
Objet : Re: [Transportpce-dev] [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

Note also that some gate jobs (tox docs-linkcheck) may fails since Gilles proposed his change yesterday because of the wiki migration...
https://git.opendaylight.org/gerrit/c/transportpce/+/87729

De : Transportpce-dev@... [Transportpce-dev@...] de la part de Guillaume Lambert via Lists.Opendaylight.Org [guillaume.lambert=orange.com@...]
Envoyé : samedi 15 février 2020 14:09
À : THOUENON Gilles TGI/OLN; Luis Gomez; RENAIS Olivier TGI/OLN
Cc : Transportpce-dev@...
Objet : Re: [Transportpce-dev] [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

Quick update: The branch is locked and I can't merge Gilles'fix by myself
https://git.opendaylight.org/gerrit/c/transportpce/+/87715


De : Transportpce-dev@... [Transportpce-dev@...] de la part de Guillaume Lambert via Lists.Opendaylight.Org [guillaume.lambert=orange.com@...]
Envoyé : samedi 15 février 2020 13:52
À : THOUENON Gilles TGI/OLN; Luis Gomez; RENAIS Olivier TGI/OLN
Cc : Transportpce-dev@...
Objet : Re: [Transportpce-dev] [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

Hello

Yes we dropped this artifact that was introduced for Karaf3/Karaf4 compatibility in a previous release.

De : Transportpce-dev@... [Transportpce-dev@...] de la part de Gilles Thouenon via Lists.Opendaylight.Org [gilles.thouenon=orange.com@...]
Envoyé : vendredi 14 février 2020 18:55
À : Luis Gomez; RENAIS Olivier TGI/OLN
Cc : Transportpce-dev@...
Objet : Re: [Transportpce-dev] [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

On Feb 14, 2020, at 9:31 AM, <olivier.renais@...> wrote:

 

Hi Luis,

What do you mean by quick. Tried to find Gilles but did not succed.

Could this be handled on Monday?

Regards

 

 

Olivier Renais 
Optical transport network architect 
ORANGE/TGI/OLN/WNI/AOT/ATA  

Fixe :  
Mobile :  
olivier.renais@...  

 

De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 17:48
À : LAMBERT Guillaume TGI/OLN
Cc : Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

 

Hi Guillaume it seems that at some point you guys removed TPCE features-transportpce artifact:

 

 

I am afraid without this, TPCE cannot be added to the Sodium SR2 Karaf distribution. I am not sure if you can do something quick, otherwise we will have to release distribution without TPCE.

 

BR/Luis

 




On Feb 14, 2020, at 1:19 AM, guillaume.lambert@... wrote:

 

Hi

 

Yes, it is done.

That’s what I meant by ‘self-service release’. As a committer, Gilles has the ability to do it.

Did you notice any problem ?

 

Guillaume

 

 

De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : jeudi 13 février 2020 18:12
À : LAMBERT Guillaume TGI/OLN
Cc : Richard Kosegi; Daniel de la Rosa; Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

 

 





On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:

 

Hi all

 

FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.

All ran smoothly.

 

Guillaume

 

De : mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

 

Just FYI,

 

jsonrpc was just released.

 

Richard.

 

On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:

Thanks Anil for all your help. 

 

Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2

 

 

Thanks

 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.

2. Release Distribution.

3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html

 


 

-- 

Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120

 

_________________________________________________________________________________________________________________________
 
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.

 

_________________________________________________________________________________________________________________________
 
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.

 

_________________________________________________________________________________________________________________________
 
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.

 

_________________________________________________________________________________________________________________________

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.
_________________________________________________________________________________________________________________________

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.
_________________________________________________________________________________________________________________________

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.
_________________________________________________________________________________________________________________________

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.
_________________________________________________________________________________________________________________________

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-dev][release] OpenDaylight Sodium SR2 release status

Luis Gomez
 

Thanks Thanh, just wanted to confirm. Gilles this means on Monday you will have to:

- bump project version to 0.4.3
- fix the features artifact
- release 0.4.3

BR/Luis


On Feb 14, 2020, at 12:22 PM, Thanh Ha <zxiiro@...> wrote:

Hi All,

They will need to bump and release 0.4.3. There is no way to back out of a release. Especially considering that it's been deployed to Maven Central at this point:


Regards,
Thanh

On Fri, 14 Feb 2020 at 14:04, Luis Gomez <ecelgp@...> wrote:
Anil, Thanh, is it possible to re-release the TPCE project in current version (0.4.2) or do they they need to bump project version (0.4.3) and then release again?

On Feb 14, 2020, at 9:55 AM, <gilles.thouenon@...> <gilles.thouenon@...> wrote:

I’ve just proposed a new change on stable/sodium branch to reintroduce the features-transportpce artifacts.
I need to leave. I’ll do my best to finalize that Monday morning.
Gilles
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 18:47
À : RENAIS Olivier TGI/OLN
Cc : LAMBERT Guillaume TGI/OLN; Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
We have just 1 week after Managed release (Feb 11) to release the official distribution. So this has to be fixed by Monday.


On Feb 14, 2020, at 9:31 AM, <olivier.renais@...> <olivier.renais@...> wrote:
 
Hi Luis,
What do you mean by quick. Tried to find Gilles but did not succed.
Could this be handled on Monday?
Regards
 
 
Olivier Renais 
Optical transport network architect 
ORANGE/TGI/OLN/WNI/AOT/ATA  
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 17:48
À : LAMBERT Guillaume TGI/OLN
Cc : Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Hi Guillaume it seems that at some point you guys removed TPCE features-transportpce artifact:
 
 
I am afraid without this, TPCE cannot be added to the Sodium SR2 Karaf distribution. I am not sure if you can do something quick, otherwise we will have to release distribution without TPCE.
 
BR/Luis
 



On Feb 14, 2020, at 1:19 AM, guillaume.lambert@... wrote:
 
Hi
 
Yes, it is done.
That’s what I meant by ‘self-service release’. As a committer, Gilles has the ability to do it.
Did you notice any problem ?
 
Guillaume
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : jeudi 13 février 2020 18:12
À : LAMBERT Guillaume TGI/OLN
Cc : Richard Kosegi; Daniel de la Rosa; Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
 




On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:
 
Hi all
 
FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.
All ran smoothly.
 
Guillaume
 
De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Just FYI,
 
jsonrpc was just released.
 
Richard.
 
On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:
Thanks Anil for all your help. 
 
Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2
 
 
Thanks
 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
 

 
-- 
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________

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-dev][release] OpenDaylight Sodium SR2 release status

Thanh ha <zxiiro@...>
 

Hi All,

They will need to bump and release 0.4.3. There is no way to back out of a release. Especially considering that it's been deployed to Maven Central at this point:


Regards,
Thanh


On Fri, 14 Feb 2020 at 14:04, Luis Gomez <ecelgp@...> wrote:
Anil, Thanh, is it possible to re-release the TPCE project in current version (0.4.2) or do they they need to bump project version (0.4.3) and then release again?

On Feb 14, 2020, at 9:55 AM, <gilles.thouenon@...> <gilles.thouenon@...> wrote:

I’ve just proposed a new change on stable/sodium branch to reintroduce the features-transportpce artifacts.
I need to leave. I’ll do my best to finalize that Monday morning.
Gilles
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 18:47
À : RENAIS Olivier TGI/OLN
Cc : LAMBERT Guillaume TGI/OLN; Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
We have just 1 week after Managed release (Feb 11) to release the official distribution. So this has to be fixed by Monday.


On Feb 14, 2020, at 9:31 AM, <olivier.renais@...> <olivier.renais@...> wrote:
 
Hi Luis,
What do you mean by quick. Tried to find Gilles but did not succed.
Could this be handled on Monday?
Regards
 
 
Olivier Renais 
Optical transport network architect 
ORANGE/TGI/OLN/WNI/AOT/ATA  
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 17:48
À : LAMBERT Guillaume TGI/OLN
Cc : Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Hi Guillaume it seems that at some point you guys removed TPCE features-transportpce artifact:
 
 
I am afraid without this, TPCE cannot be added to the Sodium SR2 Karaf distribution. I am not sure if you can do something quick, otherwise we will have to release distribution without TPCE.
 
BR/Luis
 



On Feb 14, 2020, at 1:19 AM, guillaume.lambert@... wrote:
 
Hi
 
Yes, it is done.
That’s what I meant by ‘self-service release’. As a committer, Gilles has the ability to do it.
Did you notice any problem ?
 
Guillaume
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : jeudi 13 février 2020 18:12
À : LAMBERT Guillaume TGI/OLN
Cc : Richard Kosegi; Daniel de la Rosa; Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
 




On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:
 
Hi all
 
FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.
All ran smoothly.
 
Guillaume
 
De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Just FYI,
 
jsonrpc was just released.
 
Richard.
 
On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:
Thanks Anil for all your help. 
 
Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2
 
 
Thanks
 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
 

 
-- 
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________

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-dev][release] OpenDaylight Sodium SR2 release status

Luis Gomez
 

Anil, Thanh, is it possible to re-release the TPCE project in current version (0.4.2) or do they they need to bump project version (0.4.3) and then release again?

On Feb 14, 2020, at 9:55 AM, <gilles.thouenon@...> <gilles.thouenon@...> wrote:

I’ve just proposed a new change on stable/sodium branch to reintroduce the features-transportpce artifacts.
I need to leave. I’ll do my best to finalize that Monday morning.
Gilles
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 18:47
À : RENAIS Olivier TGI/OLN
Cc : LAMBERT Guillaume TGI/OLN; Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
We have just 1 week after Managed release (Feb 11) to release the official distribution. So this has to be fixed by Monday.


On Feb 14, 2020, at 9:31 AM, <olivier.renais@...> <olivier.renais@...> wrote:
 
Hi Luis,
What do you mean by quick. Tried to find Gilles but did not succed.
Could this be handled on Monday?
Regards
 
 
Olivier Renais 
Optical transport network architect 
ORANGE/TGI/OLN/WNI/AOT/ATA  
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 17:48
À : LAMBERT Guillaume TGI/OLN
Cc : Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Hi Guillaume it seems that at some point you guys removed TPCE features-transportpce artifact:
 
 
I am afraid without this, TPCE cannot be added to the Sodium SR2 Karaf distribution. I am not sure if you can do something quick, otherwise we will have to release distribution without TPCE.
 
BR/Luis
 



On Feb 14, 2020, at 1:19 AM, guillaume.lambert@... wrote:
 
Hi
 
Yes, it is done.
That’s what I meant by ‘self-service release’. As a committer, Gilles has the ability to do it.
Did you notice any problem ?
 
Guillaume
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : jeudi 13 février 2020 18:12
À : LAMBERT Guillaume TGI/OLN
Cc : Richard Kosegi; Daniel de la Rosa; Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
 




On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:
 
Hi all
 
FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.
All ran smoothly.
 
Guillaume
 
De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Just FYI,
 
jsonrpc was just released.
 
Richard.
 
On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:
Thanks Anil for all your help. 
 
Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2
 
 
Thanks
 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
 

 
-- 
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________

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-dev][release] OpenDaylight Sodium SR2 release status

Luis Gomez
 

We have just 1 week after Managed release (Feb 11) to release the official distribution. So this has to be fixed by Monday.

On Feb 14, 2020, at 9:31 AM, <olivier.renais@...> <olivier.renais@...> wrote:

Hi Luis,
What do you mean by quick. Tried to find Gilles but did not succed.
Could this be handled on Monday?
Regards
 
 
Olivier Renais 
Optical transport network architect 
ORANGE/TGI/OLN/WNI/AOT/ATA  
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : vendredi 14 février 2020 17:48
À : LAMBERT Guillaume TGI/OLN
Cc : Daniel de la Rosa; Anil Belur; Release; TSC; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Hi Guillaume it seems that at some point you guys removed TPCE features-transportpce artifact:
 
 
I am afraid without this, TPCE cannot be added to the Sodium SR2 Karaf distribution. I am not sure if you can do something quick, otherwise we will have to release distribution without TPCE.
 
BR/Luis
 


On Feb 14, 2020, at 1:19 AM, guillaume.lambert@... wrote:
 
Hi
 
Yes, it is done.
That’s what I meant by ‘self-service release’. As a committer, Gilles has the ability to do it.
Did you notice any problem ?
 
Guillaume
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : jeudi 13 février 2020 18:12
À : LAMBERT Guillaume TGI/OLN
Cc : Richard Kosegi; Daniel de la Rosa; Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
 



On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:
 
Hi all
 
FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.
All ran smoothly.
 
Guillaume
 
De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Just FYI,
 
jsonrpc was just released.
 
Richard.
 
On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:
Thanks Anil for all your help. 
 
Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2
 
 
Thanks
 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
 

 
-- 
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________

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-dev][release] OpenDaylight Sodium SR2 release status

Luis Gomez
 

Hi Guillaume it seems that at some point you guys removed TPCE features-transportpce artifact:


I am afraid without this, TPCE cannot be added to the Sodium SR2 Karaf distribution. I am not sure if you can do something quick, otherwise we will have to release distribution without TPCE.

BR/Luis


On Feb 14, 2020, at 1:19 AM, guillaume.lambert@... wrote:

Hi
 
Yes, it is done.
That’s what I meant by ‘self-service release’. As a committer, Gilles has the ability to do it.
Did you notice any problem ?
 
Guillaume
 
 
De : Luis Gomez [mailto:ecelgp@...] 
Envoyé : jeudi 13 février 2020 18:12
À : LAMBERT Guillaume TGI/OLN
Cc : Richard Kosegi; Daniel de la Rosa; Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
 


On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:
 
Hi all
 
FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.
All ran smoothly.
 
Guillaume
 
De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Just FYI,
 
jsonrpc was just released.
 
Richard.
 
On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:
Thanks Anil for all your help. 
 
Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2
 
 
Thanks
 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
 

 
-- 
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120
 
_________________________________________________________________________________________________________________________
 
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.
 
_________________________________________________________________________________________________________________________

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-dev][release] OpenDaylight Sodium SR2 release status

Guillaume Lambert
 

Hi

 

Yes, it is done.

That’s what I meant by ‘self-service release’. As a committer, Gilles has the ability to do it.

Did you notice any problem ?

 

Guillaume

 

 

De : Luis Gomez [mailto:ecelgp@...]
Envoyé : jeudi 13 février 2020 18:12
À : LAMBERT Guillaume TGI/OLN
Cc : Richard Kosegi; Daniel de la Rosa; Anil Belur; plastic-dev@...;
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Jamo Luhrsen; Casey Cain; THOUENON Gilles TGI/OLN
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

 

When ready, please go ahead and release using this job: https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/

 



On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:

 

Hi all

 

FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.

All ran smoothly.

 

Guillaume

 

De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

 

Just FYI,

 

jsonrpc was just released.

 

Richard.

 

On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:

Thanks Anil for all your help. 

 

Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2

 

 

Thanks

 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.

2. Release Distribution.

3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html

 


 

-- 

Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120

 

_________________________________________________________________________________________________________________________
 
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.

 

_________________________________________________________________________________________________________________________

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.


REMINDER: Seeking LF Networking & LF Edge Booth Demo Ideas for ONES

Brandon Wick
 

LFN Community:

We hope that you are planning to attend the Open Networking & Edge Summit North America, April 20-21, in Los Angeles, California. Those in attendance at the last four ONS events will recall that we hosted an LF Networking Booth that showcased many community-driven demos from the LFN technical project communities. Our goal is to showcase compelling uses of LFN Networking & LF Edge project technology to solve real world industry challenges. See this blog post from ONS Europe last fall to get a sense for what types of demos have been shown in the LF Networking Booth.

In 2020, the Open Networking & Edge Summit is expanding to comprehensively cover Edge Computing, Edge Cloud, and IoT. Accordingly, the community demo zone is expanding to consider demo proposals from the LF Edge project community as well. Another change for this year is that demo managers and co-presenters need to be from LF Networking or LF Edge member companies. Submissions that include vendor companies also require that the vendors be sponsors of the Open Networking & Edge Summit event. Note: There are many event sponsorship options available at all price levels including a sponsorship option for the LFN/LFE Pavilion demos specifically. Please see the event prospectus to review the options and let me know if you have any questions.

The call for demo ideas for the Open Networking & Edge Summit North America is now open. 

Demos to be shown in the LFN/LFE booth will be chosen by LFN & LF Edge Project leadership using the following criteria:
  • Demos must include technology from at least one of the LF Networking or LF Edge projects (e.g. ONAP, OPNFV, Akraino, EdgeX Foundry)
    • Special consideration will be given to submissions that:
    • Showcase cross-project collaboration and integration
    • Map to a specific industry use case
    • Include participation and endorsement from a service provider organization
    • Show project diversity (e.g. projects not covered in other submissions)
The final number of demo stations is still TBD. Demos stations will again have a backdrop, signage, counter/table, chair(s) monitor, power, and Wi-Fi internet. Note: Apart from the event sponsorship requirement, there is no cost to host a standard demo in the LFN booth although additional power, internet, space, etc. may incur a cost.

Here are the key dates to keep in mind:
  • Feb 5: Demo idea solicitation email sent to community lists
  • Feb 26: Demo ideas submissions due
  • March 4: Demos ideas reviewed, chosen, and notifications sent
  • April 21-22: Demos shown at ONES North America
Demo manager responsibilities include:
  • Creating the demo concept and actual demo to be shown
  • Responding promptly to requests for information
  • Meeting all demo preparation deadlines
  • Setting up and testing the demo pre-show and taking down post-show
  • Staffing the demo during ONS expo hours (along with other designated team members to help share the load)
  • Being willing to participate in media activities, e.g. photos, videos
To submit your demo idea for consideration, please collect and provide the following information:
  • Demo title (10 words max)
  • Brief demo description (200 words max)
  • List of demo manager(s) with contact information 
  • List of open source projects involved
  • List of companies involved
  • Any extra requirements or special considerations
Submit your demo ideas by Feb 26th by filling in the Google Form here: https://docs.google.com/forms/d/e/1FAIpQLSfwjEfCcWUKMfiK404Uu51Zl70-8lqcRFCKKQ5vW3eeLOGAfw/viewform. If you cannot access the form, email bwick@... and I will send you the form over email.

Please let me know if you have any questions and we look forward to seeing your submissions!

Best, 

Brandon Wick
Senior Integrated Marketing Manager
The Linux Foundation
+1.917.282.0960


TSC Meeting Minutes for Feb 13, 2020

Abhijit Kumbhare
 

Hi TSC,

Please find & review the TSC meeting minutes below:


If you find something that needs to be amended, please let me know - we can update it on the confluence page above. 

Thanks,
Abhijit


Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

Luis Gomez
 

On Feb 13, 2020, at 3:56 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:

Hi all
 
FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.
All ran smoothly.
 
Guillaume
 
De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...; 
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status
 
Just FYI,
 
jsonrpc was just released.
 
Richard.
 
On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:
Thanks Anil for all your help. 
 
Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2
 
 
Thanks
 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
 

 
-- 
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120
 
_________________________________________________________________________________________________________________________

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-dev][release] OpenDaylight Sodium SR2 release status

Guillaume Lambert
 

Hi all

 

FYI, Gilles (in CC)  launched the self-service release job for transportPCE  this morning.

All ran smoothly.

 

Guillaume

 

De : release@... [mailto:release@...] De la part de Richard Kosegi
Envoyé : mercredi 12 février 2020 13:16
À : Daniel de la Rosa
Cc : Anil Belur; plastic-dev@...;
熊泉; Release; TSC; jsonrpc-dev@...; transportpce-dev@...; Luis Gomez; Jamo Luhrsen; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

 

Just FYI,

 

jsonrpc was just released.

 

Richard.

 

On Wed, Feb 12, 2020 at 5:12 AM Daniel de la Rosa <ddelarosa@...> wrote:

Thanks Anil for all your help. 

 

Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2

 

 

Thanks

 

 

On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.

2. Release Distribution.

3. Build and release packages on the CentOS/CBS repositories.

4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html

 


 

--

Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120

 

_________________________________________________________________________________________________________________________

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.


TSC Meeting Agenda for Feb 13, 2020 at 9 am Pacific

Abhijit Kumbhare
 

Next TSC meeting is Jan 30, 2020 at 9 am Pacific Time. The zoom session for the meeting is: https://zoom.us/j/219174946.

Agenda for this meeting is at:


If you need to add anything, please let me know or feel free to add to the page.

Thanks,
Abhijit


Aluminum Service Release Reduction Proposal

Abhijit Kumbhare
 

Folks,

There was a thread that Daniel had initiated about reducing the number of SRs to two. That thread is here:


I was going to reply to that thread to reignite the topic discussion before we vote on it - but since the title was Magnesium and we have decided the proposal was for Aluminum and beyond I am creating a new thread to resume the conversation. 

Daniel had created this SR schedule table in this page that I have edited to make a little easier to see the proposed changes:


Anyway please review and provide your feedback. The exact dates may be a little off (when I tried to make it more readable).

I will initiate a TSC vote next week.

Thanks,
Abhijit


Re: [opendaylight-dev][release] OpenDaylight Sodium SR2 release status

Daniel de la Rosa
 

Thanks Anil for all your help. 

Let me add Plastic and other Detnet PTL ( not sure if Detnet list is active) in case they want to be part of Sodium SR2


Thanks



On Tue, Feb 11, 2020 at 8:40 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.
4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


[opendaylight-dev][release] OpenDaylight Sodium SR2 release status

Anil Belur
 

Hello All,

OpenDaylight Sodium SR2 version bump is complete and the repository has been promoted. Nexus is still copying files over but should appear in the next few hours.

Following activities need to be completed:
1. Self-managed projects: Need to proceed with releasing your project if you are interested in being part of Sodium SR2 release.
2. Release Distribution.
3. Build and release packages on the CentOS/CBS repositories.
4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html


Re: TSC Vote to release latest build # 340 as Sodium SR2

Daniel de la Rosa
 

With 6 votes in favor, Sodium SR2 has been approved. @Anil Belur please proceed with the release so i can then let SM projects know.

Thank you all. 

On Mon, Feb 10, 2020 at 11:35 AM Daniel De La Rosa <ddelarosa@...> wrote:
Thanks @Luis Gomez , @Jamo Luhrsen and @Srinivas Rachakonda ...  All projects have signed off CSIT tests so we are now ready to vote on #340 to become Sodium SR2

TSC team, please vote ASAP



Thank you all

On Mon, Feb 10, 2020 at 8:31 AM Jamo Luhrsen <jluhrsen@...> wrote:
Hi all,

the build we are looking at is from autorelease job #340

integration-test is done and the tracking sheet is ready for projects
to check off. Once this is done, and our Vote is in, we can officially
release Sodium SR2.

https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1469072210

Thanks,
JamO


On 2/9/20 4:34 PM, Abhijit Kumbhare wrote:
Thanks Anil & JamO! I have updated the vote for the Sodium Release 2 to be for autorelease #339 - and also made it changeable (as Jamo had already voted on autorelease #334 and may want to change the vote).

On Sun, Feb 9, 2020 at 2:03 PM JamO Luhrsen <jluhrsen@...> wrote:


On 2/9/20 8:31 AM, Jamo Luhrsen wrote:
Thanks Anil,

I think the autorelease build you trigger started before the last merge
job completed from the 5 patches you merged. I kicked off another one
and probably that's what we can use:

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/340

and the integration-test job we will need to vet when in completes in aprox
8 hours:

https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sodium/479/

Thanks,
JamO



Thanks,
JamO


On 2/9/20 4:48 AM, Anil Belur wrote:
Greetings Daniel: 

All changes are merged. I've also triggered AR build #339 which should pick up these changes.


Thanks,
Anil

On Sat, Feb 8, 2020 at 8:03 AM Daniel De La Rosa <ddelarosa@...> wrote:
Anil and all, 

So it turns out that https://jira.opendaylight.org/browse/NETCONF-655 wasn't an issue after all ... more details in the tickets

but we still want to merge these two OVSDB issues, come up with a new RC, CSIT and then release sodium SR2



So @Anil Belur can you merge these gerrits coming from these two OVSDB jira tickets? 






so we can pick a new Sodium SR2 RC... 


Thanks


On Thu, Feb 6, 2020 at 9:04 AM Daniel de la Rosa via Lists.Opendaylight.Org <ddelarosa=luminanetworks.com@...> wrote:
Thank you Jamo and Srinivas for signing off these CSIT tests.. so all we have left is TSC decision on these 4 blockers.. We will review this in our next TSC meeting but let us if you have any feedback before that.. 



On Wed, Feb 5, 2020 at 1:23 PM Daniel De La Rosa <ddelarosa@...> wrote:
Team, 

We have picked up Sodium AR # 334 as a new SR2 RC...  so please the sodium sr2 new RC on your respective projects


There was a possible blocker 


but it looks like this is not a problem with more heap memory. This was working with same memory with Sodium but broke with SR1 and SR2 RC... yet not a blocker since there is a workaround. 

Also @Robert Varga please confirm that these issues are not blockers for Sodium SR2






On Tue, Feb 4, 2020 at 10:38 AM Jamo Luhrsen <jluhrsen@...> wrote:
FYI, I used the distribution [0] created in the revert patch and I
hit an OOM crash. I'm not able to say yet if it's the same
problem Luis filed [1] or new. This is with a simple netconf
test to mount 10 devices with large yang schemas.

JamO

[0] https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/controller/karaf/0.11.2-SNAPSHOT/karaf-0.11.2-20200204.174523-21.zip
[1]
https://jira.opendaylight.org/browse/CONTROLLER-1928

On 2/4/20 10:32 AM, Daniel De La Rosa wrote:
Thanks Luis and Robert.. let's pick #334 if it is successful tonight



On Tue, Feb 4, 2020 at 10:18 AM Luis Gomez <ecelgp@...> wrote:
FYI, we just reverted the offending patch with the help of Robert:


We can go ahead and pick the next green sodium AR.

BR/Luis


On Feb 1, 2020, at 6:53 AM, Robert Varga <nite@...> wrote:

On 30/01/2020 20:21, Daniel De La Rosa wrote:
@Robert Varga <mailto:nite@...>  and rest of the controller team, do
you think that this
issue, ttps://jira.opendaylight.org/browse/CONTROLLER-1928
<https://jira.opendaylight.org/browse/CONTROLLER-1928> can be solved in
the next days?

We do have https://git.opendaylight.org/gerrit/c/controller/+/87336, but
that does need careful review.

Bye,
Robert




--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120






--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


TSC Vote to release latest build # 340 as Sodium SR2

Daniel de la Rosa
 

Thanks @Luis Gomez , @Jamo Luhrsen and @Srinivas Rachakonda ...  All projects have signed off CSIT tests so we are now ready to vote on #340 to become Sodium SR2

TSC team, please vote ASAP



Thank you all

On Mon, Feb 10, 2020 at 8:31 AM Jamo Luhrsen <jluhrsen@...> wrote:
Hi all,

the build we are looking at is from autorelease job #340

integration-test is done and the tracking sheet is ready for projects
to check off. Once this is done, and our Vote is in, we can officially
release Sodium SR2.

https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1469072210

Thanks,
JamO


On 2/9/20 4:34 PM, Abhijit Kumbhare wrote:
Thanks Anil & JamO! I have updated the vote for the Sodium Release 2 to be for autorelease #339 - and also made it changeable (as Jamo had already voted on autorelease #334 and may want to change the vote).

On Sun, Feb 9, 2020 at 2:03 PM JamO Luhrsen <jluhrsen@...> wrote:


On 2/9/20 8:31 AM, Jamo Luhrsen wrote:
Thanks Anil,

I think the autorelease build you trigger started before the last merge
job completed from the 5 patches you merged. I kicked off another one
and probably that's what we can use:

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/340

and the integration-test job we will need to vet when in completes in aprox
8 hours:

https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sodium/479/

Thanks,
JamO



Thanks,
JamO


On 2/9/20 4:48 AM, Anil Belur wrote:
Greetings Daniel: 

All changes are merged. I've also triggered AR build #339 which should pick up these changes.


Thanks,
Anil

On Sat, Feb 8, 2020 at 8:03 AM Daniel De La Rosa <ddelarosa@...> wrote:
Anil and all, 

So it turns out that https://jira.opendaylight.org/browse/NETCONF-655 wasn't an issue after all ... more details in the tickets

but we still want to merge these two OVSDB issues, come up with a new RC, CSIT and then release sodium SR2



So @Anil Belur can you merge these gerrits coming from these two OVSDB jira tickets? 






so we can pick a new Sodium SR2 RC... 


Thanks


On Thu, Feb 6, 2020 at 9:04 AM Daniel de la Rosa via Lists.Opendaylight.Org <ddelarosa=luminanetworks.com@...> wrote:
Thank you Jamo and Srinivas for signing off these CSIT tests.. so all we have left is TSC decision on these 4 blockers.. We will review this in our next TSC meeting but let us if you have any feedback before that.. 



On Wed, Feb 5, 2020 at 1:23 PM Daniel De La Rosa <ddelarosa@...> wrote:
Team, 

We have picked up Sodium AR # 334 as a new SR2 RC...  so please the sodium sr2 new RC on your respective projects


There was a possible blocker 


but it looks like this is not a problem with more heap memory. This was working with same memory with Sodium but broke with SR1 and SR2 RC... yet not a blocker since there is a workaround. 

Also @Robert Varga please confirm that these issues are not blockers for Sodium SR2






On Tue, Feb 4, 2020 at 10:38 AM Jamo Luhrsen <jluhrsen@...> wrote:
FYI, I used the distribution [0] created in the revert patch and I
hit an OOM crash. I'm not able to say yet if it's the same
problem Luis filed [1] or new. This is with a simple netconf
test to mount 10 devices with large yang schemas.

JamO

[0] https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/controller/karaf/0.11.2-SNAPSHOT/karaf-0.11.2-20200204.174523-21.zip
[1]
https://jira.opendaylight.org/browse/CONTROLLER-1928

On 2/4/20 10:32 AM, Daniel De La Rosa wrote:
Thanks Luis and Robert.. let's pick #334 if it is successful tonight



On Tue, Feb 4, 2020 at 10:18 AM Luis Gomez <ecelgp@...> wrote:
FYI, we just reverted the offending patch with the help of Robert:


We can go ahead and pick the next green sodium AR.

BR/Luis


On Feb 1, 2020, at 6:53 AM, Robert Varga <nite@...> wrote:

On 30/01/2020 20:21, Daniel De La Rosa wrote:
@Robert Varga <mailto:nite@...>  and rest of the controller team, do
you think that this
issue, ttps://jira.opendaylight.org/browse/CONTROLLER-1928
<https://jira.opendaylight.org/browse/CONTROLLER-1928> can be solved in
the next days?

We do have https://git.opendaylight.org/gerrit/c/controller/+/87336, but
that does need careful review.

Bye,
Robert




--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120






--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


Re: [controller-dev] TSC Vote to release latest build # 334 as Sodium SR2

JamO Luhrsen
 

Hi all,

the build we are looking at is from autorelease job #340

integration-test is done and the tracking sheet is ready for projects
to check off. Once this is done, and our Vote is in, we can officially
release Sodium SR2.

https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1469072210

Thanks,
JamO


On 2/9/20 4:34 PM, Abhijit Kumbhare wrote:
Thanks Anil & JamO! I have updated the vote for the Sodium Release 2 to be for autorelease #339 - and also made it changeable (as Jamo had already voted on autorelease #334 and may want to change the vote).

On Sun, Feb 9, 2020 at 2:03 PM JamO Luhrsen <jluhrsen@...> wrote:


On 2/9/20 8:31 AM, Jamo Luhrsen wrote:
Thanks Anil,

I think the autorelease build you trigger started before the last merge
job completed from the 5 patches you merged. I kicked off another one
and probably that's what we can use:

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/340

and the integration-test job we will need to vet when in completes in aprox
8 hours:

https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sodium/479/

Thanks,
JamO



Thanks,
JamO


On 2/9/20 4:48 AM, Anil Belur wrote:
Greetings Daniel: 

All changes are merged. I've also triggered AR build #339 which should pick up these changes.


Thanks,
Anil

On Sat, Feb 8, 2020 at 8:03 AM Daniel De La Rosa <ddelarosa@...> wrote:
Anil and all, 

So it turns out that https://jira.opendaylight.org/browse/NETCONF-655 wasn't an issue after all ... more details in the tickets

but we still want to merge these two OVSDB issues, come up with a new RC, CSIT and then release sodium SR2



So @Anil Belur can you merge these gerrits coming from these two OVSDB jira tickets? 






so we can pick a new Sodium SR2 RC... 


Thanks


On Thu, Feb 6, 2020 at 9:04 AM Daniel de la Rosa via Lists.Opendaylight.Org <ddelarosa=luminanetworks.com@...> wrote:
Thank you Jamo and Srinivas for signing off these CSIT tests.. so all we have left is TSC decision on these 4 blockers.. We will review this in our next TSC meeting but let us if you have any feedback before that.. 



On Wed, Feb 5, 2020 at 1:23 PM Daniel De La Rosa <ddelarosa@...> wrote:
Team, 

We have picked up Sodium AR # 334 as a new SR2 RC...  so please the sodium sr2 new RC on your respective projects


There was a possible blocker 


but it looks like this is not a problem with more heap memory. This was working with same memory with Sodium but broke with SR1 and SR2 RC... yet not a blocker since there is a workaround. 

Also @Robert Varga please confirm that these issues are not blockers for Sodium SR2






On Tue, Feb 4, 2020 at 10:38 AM Jamo Luhrsen <jluhrsen@...> wrote:
FYI, I used the distribution [0] created in the revert patch and I
hit an OOM crash. I'm not able to say yet if it's the same
problem Luis filed [1] or new. This is with a simple netconf
test to mount 10 devices with large yang schemas.

JamO

[0] https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/controller/karaf/0.11.2-SNAPSHOT/karaf-0.11.2-20200204.174523-21.zip
[1]
https://jira.opendaylight.org/browse/CONTROLLER-1928

On 2/4/20 10:32 AM, Daniel De La Rosa wrote:
Thanks Luis and Robert.. let's pick #334 if it is successful tonight



On Tue, Feb 4, 2020 at 10:18 AM Luis Gomez <ecelgp@...> wrote:
FYI, we just reverted the offending patch with the help of Robert:


We can go ahead and pick the next green sodium AR.

BR/Luis


On Feb 1, 2020, at 6:53 AM, Robert Varga <nite@...> wrote:

On 30/01/2020 20:21, Daniel De La Rosa wrote:
@Robert Varga <mailto:nite@...>  and rest of the controller team, do
you think that this
issue, ttps://jira.opendaylight.org/browse/CONTROLLER-1928
<https://jira.opendaylight.org/browse/CONTROLLER-1928> can be solved in
the next days?

We do have https://git.opendaylight.org/gerrit/c/controller/+/87336, but
that does need careful review.

Bye,
Robert




--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120





Re: [controller-dev] TSC Vote to release latest build # 334 as Sodium SR2

Abhijit Kumbhare
 

Thanks Anil & JamO! I have updated the vote for the Sodium Release 2 to be for autorelease #339 - and also made it changeable (as Jamo had already voted on autorelease #334 and may want to change the vote).


On Sun, Feb 9, 2020 at 2:03 PM JamO Luhrsen <jluhrsen@...> wrote:


On 2/9/20 8:31 AM, Jamo Luhrsen wrote:
Thanks Anil,

I think the autorelease build you trigger started before the last merge
job completed from the 5 patches you merged. I kicked off another one
and probably that's what we can use:

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/340

and the integration-test job we will need to vet when in completes in aprox
8 hours:

https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sodium/479/

Thanks,
JamO



Thanks,
JamO


On 2/9/20 4:48 AM, Anil Belur wrote:
Greetings Daniel: 

All changes are merged. I've also triggered AR build #339 which should pick up these changes.


Thanks,
Anil

On Sat, Feb 8, 2020 at 8:03 AM Daniel De La Rosa <ddelarosa@...> wrote:
Anil and all, 

So it turns out that https://jira.opendaylight.org/browse/NETCONF-655 wasn't an issue after all ... more details in the tickets

but we still want to merge these two OVSDB issues, come up with a new RC, CSIT and then release sodium SR2



So @Anil Belur can you merge these gerrits coming from these two OVSDB jira tickets? 






so we can pick a new Sodium SR2 RC... 


Thanks


On Thu, Feb 6, 2020 at 9:04 AM Daniel de la Rosa via Lists.Opendaylight.Org <ddelarosa=luminanetworks.com@...> wrote:
Thank you Jamo and Srinivas for signing off these CSIT tests.. so all we have left is TSC decision on these 4 blockers.. We will review this in our next TSC meeting but let us if you have any feedback before that.. 



On Wed, Feb 5, 2020 at 1:23 PM Daniel De La Rosa <ddelarosa@...> wrote:
Team, 

We have picked up Sodium AR # 334 as a new SR2 RC...  so please the sodium sr2 new RC on your respective projects


There was a possible blocker 


but it looks like this is not a problem with more heap memory. This was working with same memory with Sodium but broke with SR1 and SR2 RC... yet not a blocker since there is a workaround. 

Also @Robert Varga please confirm that these issues are not blockers for Sodium SR2






On Tue, Feb 4, 2020 at 10:38 AM Jamo Luhrsen <jluhrsen@...> wrote:
FYI, I used the distribution [0] created in the revert patch and I
hit an OOM crash. I'm not able to say yet if it's the same
problem Luis filed [1] or new. This is with a simple netconf
test to mount 10 devices with large yang schemas.

JamO

[0] https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/controller/karaf/0.11.2-SNAPSHOT/karaf-0.11.2-20200204.174523-21.zip
[1]
https://jira.opendaylight.org/browse/CONTROLLER-1928

On 2/4/20 10:32 AM, Daniel De La Rosa wrote:
Thanks Luis and Robert.. let's pick #334 if it is successful tonight



On Tue, Feb 4, 2020 at 10:18 AM Luis Gomez <ecelgp@...> wrote:
FYI, we just reverted the offending patch with the help of Robert:


We can go ahead and pick the next green sodium AR.

BR/Luis


On Feb 1, 2020, at 6:53 AM, Robert Varga <nite@...> wrote:

On 30/01/2020 20:21, Daniel De La Rosa wrote:
@Robert Varga <mailto:nite@...>  and rest of the controller team, do
you think that this
issue, ttps://jira.opendaylight.org/browse/CONTROLLER-1928
<https://jira.opendaylight.org/browse/CONTROLLER-1928> can be solved in
the next days?

We do have https://git.opendaylight.org/gerrit/c/controller/+/87336, but
that does need careful review.

Bye,
Robert




--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120




Re: [controller-dev] TSC Vote to release latest build # 334 as Sodium SR2

JamO Luhrsen
 



On 2/9/20 8:31 AM, Jamo Luhrsen wrote:
Thanks Anil,

I think the autorelease build you trigger started before the last merge
job completed from the 5 patches you merged. I kicked off another one
and probably that's what we can use:

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/340

and the integration-test job we will need to vet when in completes in aprox
8 hours:

https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sodium/479/

Thanks,
JamO



Thanks,
JamO


On 2/9/20 4:48 AM, Anil Belur wrote:
Greetings Daniel: 

All changes are merged. I've also triggered AR build #339 which should pick up these changes.


Thanks,
Anil

On Sat, Feb 8, 2020 at 8:03 AM Daniel De La Rosa <ddelarosa@...> wrote:
Anil and all, 

So it turns out that https://jira.opendaylight.org/browse/NETCONF-655 wasn't an issue after all ... more details in the tickets

but we still want to merge these two OVSDB issues, come up with a new RC, CSIT and then release sodium SR2



So @Anil Belur can you merge these gerrits coming from these two OVSDB jira tickets? 






so we can pick a new Sodium SR2 RC... 


Thanks


On Thu, Feb 6, 2020 at 9:04 AM Daniel de la Rosa via Lists.Opendaylight.Org <ddelarosa=luminanetworks.com@...> wrote:
Thank you Jamo and Srinivas for signing off these CSIT tests.. so all we have left is TSC decision on these 4 blockers.. We will review this in our next TSC meeting but let us if you have any feedback before that.. 



On Wed, Feb 5, 2020 at 1:23 PM Daniel De La Rosa <ddelarosa@...> wrote:
Team, 

We have picked up Sodium AR # 334 as a new SR2 RC...  so please the sodium sr2 new RC on your respective projects


There was a possible blocker 


but it looks like this is not a problem with more heap memory. This was working with same memory with Sodium but broke with SR1 and SR2 RC... yet not a blocker since there is a workaround. 

Also @Robert Varga please confirm that these issues are not blockers for Sodium SR2






On Tue, Feb 4, 2020 at 10:38 AM Jamo Luhrsen <jluhrsen@...> wrote:
FYI, I used the distribution [0] created in the revert patch and I
hit an OOM crash. I'm not able to say yet if it's the same
problem Luis filed [1] or new. This is with a simple netconf
test to mount 10 devices with large yang schemas.

JamO

[0] https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/controller/karaf/0.11.2-SNAPSHOT/karaf-0.11.2-20200204.174523-21.zip
[1]
https://jira.opendaylight.org/browse/CONTROLLER-1928

On 2/4/20 10:32 AM, Daniel De La Rosa wrote:
Thanks Luis and Robert.. let's pick #334 if it is successful tonight



On Tue, Feb 4, 2020 at 10:18 AM Luis Gomez <ecelgp@...> wrote:
FYI, we just reverted the offending patch with the help of Robert:


We can go ahead and pick the next green sodium AR.

BR/Luis


On Feb 1, 2020, at 6:53 AM, Robert Varga <nite@...> wrote:

On 30/01/2020 20:21, Daniel De La Rosa wrote:
@Robert Varga <mailto:nite@...>  and rest of the controller team, do
you think that this
issue, ttps://jira.opendaylight.org/browse/CONTROLLER-1928
<https://jira.opendaylight.org/browse/CONTROLLER-1928> can be solved in
the next days?

We do have https://git.opendaylight.org/gerrit/c/controller/+/87336, but
that does need careful review.

Bye,
Robert




--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120



--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120


1821 - 1840 of 14295