On May 7, 2022, at 12:43 PM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thanks for the update.  If that's the case, @Luis Gomez  please proceed to release Sulfur distribution at your earliest convenience 

On Thu, May 5, 2022 at 1:33 AM <gilles.thouenon@...> wrote:

Hello Daniel,

 

I believe that we can reasonably consider that TransportPCE will not be able to integrate the GA distribution of Sulfur. We could not complete the project migration due to many issues we are facing and that are still under investigation.

The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.

 

On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?

 

If I try to summarize the situation and issues that are still open:

• Openroadm models compilation (assembling issue - see my email of 2022-04-27)
• Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
• Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
• Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
• Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…

 

Best regards,

Gilles

 

 

 

Orange Restricted

De : release@... <release@...> De la part de Guillaume Lambert via lists.opendaylight.org
Envoyé : mercredi 4 mai 2022 17:14
À : Daniel de la Rosa <ddelarosa0707@...>; Anil Shashikumar Belur <abelur@...>; THOUENON Gilles INNOV/NET <gilles.thouenon@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; OpenDaylight Discuss <discuss@...>; TSC <tsc@...>; Casey Cain <ccain@...>; Andrew Grimberg <agrimberg@...>; Luis Gomez <ecelgp@...>
Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

 

Hi Daniel

 

I let Gilles answer the question since he is in charge of this TPCE release.

We can put that at the TSC agenda tomorrow.

 

BR

Guillaume

 

De : Daniel de la Rosa <ddelarosa0707@...>
Envoyé : mercredi 4 mai 2022 16:41
À : Anil Shashikumar Belur <abelur@...>; LAMBERT Guillaume INNOV/NET <guillaume.lambert@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; OpenDaylight Discuss <discuss@...>; TSC <tsc@...>; Casey Cain <ccain@...>; Andrew Grimberg <agrimberg@...>; Luis Gomez <ecelgp@...>
Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

 

Thanks Anil .. So @LAMBERT Guillaume TGI/OLN  are you going to skip Sulfur to TPCE? I can start with Sulfur SR1 code freeze as scheduled next week while Sulfur GA is getting ready

 

 

 

On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:

+tsc

 

On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].

Many thanks to everyone who contributed to the Sulfur release.

Regards,
Anil Belur

 

Orange Restricted

_________________________________________________________________________________________________________________________

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.

On May 7, 2022, at 12:43 PM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thanks for the update.  If that's the case, @Luis Gomez  please proceed to release Sulfur distribution at your earliest convenience 

On Thu, May 5, 2022 at 1:33 AM <gilles.thouenon@...> wrote:

Hello Daniel,

 

I believe that we can reasonably consider that TransportPCE will not be able to integrate the GA distribution of Sulfur. We could not complete the project migration due to many issues we are facing and that are still under investigation.

The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.

 

On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?

 

If I try to summarize the situation and issues that are still open:

• Openroadm models compilation (assembling issue - see my email of 2022-04-27)
• Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
• Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
• Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
• Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…

 

Best regards,

Gilles

 

 

 

Orange Restricted

De : release@... <release@...> De la part de Guillaume Lambert via lists.opendaylight.org
Envoyé : mercredi 4 mai 2022 17:14
À : Daniel de la Rosa <ddelarosa0707@...>; Anil Shashikumar Belur <abelur@...>; THOUENON Gilles INNOV/NET <gilles.thouenon@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; OpenDaylight Discuss <discuss@...>; TSC <tsc@...>; Casey Cain <ccain@...>; Andrew Grimberg <agrimberg@...>; Luis Gomez <ecelgp@...>
Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

 

Hi Daniel

 

I let Gilles answer the question since he is in charge of this TPCE release.

We can put that at the TSC agenda tomorrow.

 

BR

Guillaume

 

De : Daniel de la Rosa <ddelarosa0707@...>
Envoyé : mercredi 4 mai 2022 16:41
À : Anil Shashikumar Belur <abelur@...>; LAMBERT Guillaume INNOV/NET <guillaume.lambert@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; OpenDaylight Discuss <discuss@...>; TSC <tsc@...>; Casey Cain <ccain@...>; Andrew Grimberg <agrimberg@...>; Luis Gomez <ecelgp@...>
Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

 

Thanks Anil .. So @LAMBERT Guillaume TGI/OLN  are you going to skip Sulfur to TPCE? I can start with Sulfur SR1 code freeze as scheduled next week while Sulfur GA is getting ready

 

 

 

On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:

+tsc

 

On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].

Many thanks to everyone who contributed to the Sulfur release.

Regards,
Anil Belur

 

Orange Restricted

_________________________________________________________________________________________________________________________

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.

What: Ingress, Nexus, Jenkins sandbox and production maintenance

When: Now

Why: The Hypervisor on these servers has a failing NIC which is resulting in dropped packets. We are migrating the systems before the issue worsens

Impact: Each system will be down for approximately 15 minutes

Jenkins is being placed in shutdown mode. Maintenance will start when jobs complete

Thank you,
Vanessa

On Mar 4, 2022, at 4:01 PM, Daniel Farrell <dfarrell07@...> wrote:

Hey Luis, Jamo, Al, Faseela,!

Omg yes miss you all and the ODL community.  Yes it's fine to remove me. I'm working on Submariner these days, K8s multicluster L3 networking and multicluster service discovery.

I really appreciate you all, thanks for being such good friends and teachers for me.

Daniel

On Fri, Mar 4, 2022, 3:31 PM Luis Gomez <ecelgp@...> wrote:

Sounds really interesting, glad to hear you are still contributing to open source projects :)

On Mar 4, 2022, at 12:27 PM, Faseela K <k.faseela@...> wrote:

Yes Luis .. I moved back to Ericsson from Cisco, and now back to some opensource work.. but involved in istio and envoy projects 🙂

On Fri, Mar 4, 2022, 9:19 PM Luis Gomez <ecelgp@...> wrote:

Thanks Faseela, I hope things are going well for you :)

On Mar 4, 2022, at 12:17 PM, Faseela K <k.faseela@...> wrote:

Fine to remove me 🙂

Really miss all those good old odl days 🙂🙂

On Fri, Mar 4, 2022, 9:06 PM Luis Gomez <ecelgp@...> wrote:

You were not in the "to" list because you are still around :)

On Mar 4, 2022, at 12:05 PM, Jamo Luhrsen <jluhrsen@...> wrote:

yes, it's fine to remove me.

miss you guys though :)

JamO

On 3/4/22 12:03 PM, Luis Gomez wrote:

Hello,

You are receiving this email because you still show up as integration/test committer in the ODL project. Since you do not have a contribution for quite some time, I wonder if any of you is interested in continuing as committer, otherwise we will remove your name from the list. No answer means no interest.

Thanks
Luis

On Mar 4, 2022, at 12:27 PM, Faseela K <k.faseela@...> wrote:

Yes Luis .. I moved back to Ericsson from Cisco, and now back to some opensource work.. but involved in istio and envoy projects 🙂

On Fri, Mar 4, 2022, 9:19 PM Luis Gomez <ecelgp@...> wrote:

Thanks Faseela, I hope things are going well for you :)

On Mar 4, 2022, at 12:17 PM, Faseela K <k.faseela@...> wrote:

Fine to remove me 🙂

Really miss all those good old odl days 🙂🙂

On Fri, Mar 4, 2022, 9:06 PM Luis Gomez <ecelgp@...> wrote:

You were not in the "to" list because you are still around :)

On Mar 4, 2022, at 12:05 PM, Jamo Luhrsen <jluhrsen@...> wrote:

yes, it's fine to remove me.

miss you guys though :)

JamO

On 3/4/22 12:03 PM, Luis Gomez wrote:

Hello,

You are receiving this email because you still show up as integration/test committer in the ODL project. Since you do not have a contribution for quite some time, I wonder if any of you is interested in continuing as committer, otherwise we will remove your name from the list. No answer means no interest.

Thanks
Luis

On Mar 4, 2022, at 12:18 PM, MORTON JR., AL <acmorton@...> wrote:

Ok, my address still works and I continue to lurk, although I wasn’t a committer. So It turns-out this message wasn’t for us (JamO, me, others that I also miss...).

 

Thanks for the clarification Luis,

Al

 

From: integration-dev@... <integration-dev@...> On Behalf Of Luis Gomez via lists.opendaylight.org
Sent: Friday, March 4, 2022 3:07 PM
To: Jamo Luhrsen <jluhrsen@...>
Cc: R P Karthika . <r.p.karthika@...>; Faseela K <k.faseela@...>; tomas.markovic@...; Daniel Farrell <dfarrell07@...>; shague@...; integration-dev@...
Subject: Re: [integration-dev] Int/test committer list cleanup

 

You were not in the "to" list because you are still around :)

On Mar 4, 2022, at 12:05 PM, Jamo Luhrsen <jluhrsen@...> wrote:

 

yes, it's fine to remove me.

miss you guys though :)

JamO

On 3/4/22 12:03 PM, Luis Gomez wrote:

Hello,

You are receiving this email because you still show up as integration/test committer in the ODL project. Since you do not have a contribution for quite some time, I wonder if any of you is interested in continuing as committer, otherwise we will remove your name from the list. No answer means no interest.

Thanks

Luis

On Mar 4, 2022, at 12:17 PM, Faseela K <k.faseela@...> wrote:

Fine to remove me 🙂

Really miss all those good old odl days 🙂🙂

On Fri, Mar 4, 2022, 9:06 PM Luis Gomez <ecelgp@...> wrote:

You were not in the "to" list because you are still around :)

On Mar 4, 2022, at 12:05 PM, Jamo Luhrsen <jluhrsen@...> wrote:

yes, it's fine to remove me.

miss you guys though :)

JamO

On 3/4/22 12:03 PM, Luis Gomez wrote:

Hello,

You are receiving this email because you still show up as integration/test committer in the ODL project. Since you do not have a contribution for quite some time, I wonder if any of you is interested in continuing as committer, otherwise we will remove your name from the list. No answer means no interest.

Thanks
Luis