Date   

Re: [OpenDaylight TSC] [integration-dev] [opendaylight-dev] ODL Clustering issue - High Availability

Rohini Ambika
 

Thanks.

 

We have already tested CONTROLLER-2035 with Phosphorous SR2(created a patch with the fix) and the issue still persists when we do multiple restarts of the master node(approx. after 10th restart).

 

Thanks & Regards,

Rohini

Cell: +91.9995241298 | VoIP: +91.471.3025332

 

From: TSC@... <TSC@...> On Behalf Of Daniel de la Rosa
Sent: Thursday, July 28, 2022 9:50 PM
To: Rohini Ambika <rohini.ambika@...>; Venkatrangan Govindarajan <gvrangan@...>
Cc: Ivan Hrasko <ivan.hrasko@...>; integration-dev@...; dev@...; kernel-dev@...; TSC <tsc@...>
Subject: Re: [OpenDaylight TSC] [integration-dev] [opendaylight-dev] ODL Clustering issue - High Availability

 

[**EXTERNAL EMAIL**]

Rohini and all

 

Please use Phosphorus SR3 since CONTROLLER-2035 is fixed in that version. In any case, @Venkatrangan Govindarajan  will also get back to you in case he finds anything in the logs you provided

 

thanks

 

On Wed, Jul 27, 2022 at 5:45 AM Rohini Ambika via lists.opendaylight.org <rohini.ambika=infosys.com@...> wrote:

Hi,

 

ODL version – Phosphorous SR2

 

Thanks & Regards,

Rohini

 

From: dev@... <dev@...> On Behalf Of Ivan Hrasko
Sent: Wednesday, July 27, 2022 5:31 PM
To: integration-dev@...; dev@...; kernel-dev@...; kernel-dev@...
Subject: Re: [opendaylight-dev] ODL Clustering issue - High Availability

 

[**EXTERNAL EMAIL**]

Hello,

 

what is the ODL version please?

 

Best,

 

Ivan Hraško

Senior Software Engineer

 

PANTHEON .tech

Mlynské Nivy 56, 821 05 Bratislava

Slovakia

Tel / +421 220 665 111

 

MAIL / ivan.hrasko@...

WEB / https://pantheon.tech

 


Od: integration-dev@... <integration-dev@...> v mene používateľa Rohini Ambika via lists.opendaylight.org <rohini.ambika=infosys.com@...>
Odoslané: streda, 27. júla 2022 13:19
Komu: integration-dev@...; dev@...; kernel-dev@...; kernel-dev@...
Predmet: [integration-dev] ODL Clustering issue - High Availability

 

Hi All,

 

As presented/discussed in the ODL TSC meeting held on 22nd Friday 10.30 AM IST, posting this email to highlight the issues on ODL clustering use cases encountered during the performance testing.

 

Details and configurations as follows:

 

·         Requirement : ODL clustering for high availability (HA) on data distribution

·         Env Configuration:

o    3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node

o    CPU :  8 Cores

o    RAM : 20GB

o    Java Heap size : Min – 512MB Max – 16GB

o    JDK version : 11

o    Kubernetes version : 1.19.1

o    Docker version : 20.10.7

·         ODL features installed to enable clustering:

o    odl-netconf-clustered-topology

o    odl-restconf-all

·         Device configured : Netconf devices , all devices having same schema(tested with 250 devices)

·         Use Case:

o    Fail Over/High Availability:

§  Expected : In case any of the ODL instance gets down/restarted due to network splits or internal error, other instance in cluster should be available and functional. If the affected instance is having master mount, the other instance who is elected as master by re-election should be able to re-register the devices and resume the operations. Once the affected instance comes up, it should be able to join the cluster as member node and register the slave mounts.

§  Observation : When the odl instance which is having the master mount restarts, election happens among the other node in the cluster and elects the new leader. Now the new leader is trying to re-register the master mount but failed at a point due to the termination of the Akka Cluster Singleton Actor. Hence the cluster goes to idle state and failed to assign owner for the device DOM entity. In this case, the configuration of already mounted device/ new mounts will fail.  

·         JIRA reference : https://jira.opendaylight.org/browse/CONTROLLER-2035  

·         Akka configuration of all the nodes attached. (Increased the gossip-interval time to 5s in akka.conf file to avoid Akka AskTimedOut issue while mounting multiple devices at a time.)

 

 

Requesting your support to identify if there is any mis-configurations or any known solution for the issue .

Please let us know if any further information required.

 

Note : We have tested the single ODL instance without enabling cluster features in K8s cluster. In case of K8s node failure, ODL instance will be re-scheduled in other available K8s node and operations will be resumed.  

             

 

Thanks & Regards,

Rohini

 




Re: [opendaylight-dev] ODL Clustering issue - High Availability

Daniel de la Rosa
 

Rohini and all

Please use Phosphorus SR3 since CONTROLLER-2035 is fixed in that version. In any case, @Venkatrangan Govindarajan  will also get back to you in case he finds anything in the logs you provided

thanks

On Wed, Jul 27, 2022 at 5:45 AM Rohini Ambika via lists.opendaylight.org <rohini.ambika=infosys.com@...> wrote:

Hi,

 

ODL version – Phosphorous SR2

 

Thanks & Regards,

Rohini

 

From: dev@... <dev@...> On Behalf Of Ivan Hrasko
Sent: Wednesday, July 27, 2022 5:31 PM
To: integration-dev@...; dev@...; kernel-dev@...; kernel-dev@...
Subject: Re: [opendaylight-dev] ODL Clustering issue - High Availability

 

[**EXTERNAL EMAIL**]

Hello,

 

what is the ODL version please?

 

Best,

 

Ivan Hraško

Senior Software Engineer

 

PANTHEON .tech

Mlynské Nivy 56, 821 05 Bratislava

Slovakia

Tel / +421 220 665 111

 

MAIL / ivan.hrasko@...

WEB / https://pantheon.tech

 


Od: integration-dev@... <integration-dev@...> v mene používateľa Rohini Ambika via lists.opendaylight.org <rohini.ambika=infosys.com@...>
Odoslané: streda, 27. júla 2022 13:19
Komu: integration-dev@...; dev@...; kernel-dev@...; kernel-dev@...
Predmet: [integration-dev] ODL Clustering issue - High Availability

 

Hi All,

 

As presented/discussed in the ODL TSC meeting held on 22nd Friday 10.30 AM IST, posting this email to highlight the issues on ODL clustering use cases encountered during the performance testing.

 

Details and configurations as follows:

 

·         Requirement : ODL clustering for high availability (HA) on data distribution

·         Env Configuration:

o    3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node

o    CPU :  8 Cores

o    RAM : 20GB

o    Java Heap size : Min – 512MB Max – 16GB

o    JDK version : 11

o    Kubernetes version : 1.19.1

o    Docker version : 20.10.7

·         ODL features installed to enable clustering:

o    odl-netconf-clustered-topology

o    odl-restconf-all

·         Device configured : Netconf devices , all devices having same schema(tested with 250 devices)

·         Use Case:

o    Fail Over/High Availability:

§  Expected : In case any of the ODL instance gets down/restarted due to network splits or internal error, other instance in cluster should be available and functional. If the affected instance is having master mount, the other instance who is elected as master by re-election should be able to re-register the devices and resume the operations. Once the affected instance comes up, it should be able to join the cluster as member node and register the slave mounts.

§  Observation : When the odl instance which is having the master mount restarts, election happens among the other node in the cluster and elects the new leader. Now the new leader is trying to re-register the master mount but failed at a point due to the termination of the Akka Cluster Singleton Actor. Hence the cluster goes to idle state and failed to assign owner for the device DOM entity. In this case, the configuration of already mounted device/ new mounts will fail.  

·         JIRA reference : https://jira.opendaylight.org/browse/CONTROLLER-2035  

·         Akka configuration of all the nodes attached. (Increased the gossip-interval time to 5s in akka.conf file to avoid Akka AskTimedOut issue while mounting multiple devices at a time.)

 

 

Requesting your support to identify if there is any mis-configurations or any known solution for the issue .

Please let us know if any further information required.

 

Note : We have tested the single ODL instance without enabling cluster features in K8s cluster. In case of K8s node failure, ODL instance will be re-scheduled in other available K8s node and operations will be resumed.  

             

 

Thanks & Regards,

Rohini

 





ODL Clustering issue - High Availability

Rohini Ambika <rohini.ambika@...>
 

Hi All,

 

As presented/discussed in the ODL TSC meeting held on 22nd Friday 10.30 AM IST, posting this email to highlight the issues on ODL clustering use cases encountered during the performance testing.

 

Details and configurations as follows:

 

  • Requirement : ODL clustering for high availability (HA) on data distribution
  • Env Configuration:
    • 3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node
    • CPU :  8 Cores
    • RAM : 20GB
    • Java Heap size : Min – 512MB Max – 16GB
    • JDK version : 11
    • Kubernetes version : 1.19.1
    • Docker version : 20.10.7
  • ODL features installed to enable clustering:
    • odl-netconf-clustered-topology
    • odl-restconf-all
  • Device configured : Netconf devices , all devices having same schema(tested with 250 devices)
  • Use Case:
    • Fail Over/High Availability:
      • Expected : In case any of the ODL instance gets down/restarted due to network splits or internal error, other instance in cluster should be available and functional. If the affected instance is having master mount, the other instance who is elected as master by re-election should be able to re-register the devices and resume the operations. Once the affected instance comes up, it should be able to join the cluster as member node and register the slave mounts.
      • Observation : When the odl instance which is having the master mount restarts, election happens among the other node in the cluster and elects the new leader. Now the new leader is trying to re-register the master mount but failed at a point due to the termination of the Akka Cluster Singleton Actor. Hence the cluster goes to idle state and failed to assign owner for the device DOM entity. In this case, the configuration of already mounted device/ new mounts will fail.  

 

 

Requesting your support to identify if there is any mis-configurations or any known solution for the issue .

Please let us know if any further information required.

 

Note : We have tested the single ODL instance without enabling cluster features in K8s cluster. In case of K8s node failure, ODL instance will be re-scheduled in other available K8s node and operations will be resumed.  

             

 

Thanks & Regards,

Rohini

 


Re: [opendaylight-dev] ODL Clustering issue - High Availability

Rohini Ambika
 

Hi,

 

ODL version – Phosphorous SR2

 

Thanks & Regards,

Rohini

 

From: dev@... <dev@...> On Behalf Of Ivan Hrasko
Sent: Wednesday, July 27, 2022 5:31 PM
To: integration-dev@...; dev@...; kernel-dev@...; kernel-dev@...
Subject: Re: [opendaylight-dev] ODL Clustering issue - High Availability

 

[**EXTERNAL EMAIL**]

Hello,

 

what is the ODL version please?

 

Best,

 

Ivan Hraško

Senior Software Engineer

 

PANTHEON .tech

Mlynské Nivy 56, 821 05 Bratislava

Slovakia

Tel / +421 220 665 111

 

MAIL / ivan.hrasko@...

WEB / https://pantheon.tech

 


Od: integration-dev@... <integration-dev@...> v mene používateľa Rohini Ambika via lists.opendaylight.org <rohini.ambika=infosys.com@...>
Odoslané: streda, 27. júla 2022 13:19
Komu: integration-dev@...; dev@...; kernel-dev@...; kernel-dev@...
Predmet: [integration-dev] ODL Clustering issue - High Availability

 

Hi All,

 

As presented/discussed in the ODL TSC meeting held on 22nd Friday 10.30 AM IST, posting this email to highlight the issues on ODL clustering use cases encountered during the performance testing.

 

Details and configurations as follows:

 

·         Requirement : ODL clustering for high availability (HA) on data distribution

·         Env Configuration:

o    3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node

o    CPU :  8 Cores

o    RAM : 20GB

o    Java Heap size : Min – 512MB Max – 16GB

o    JDK version : 11

o    Kubernetes version : 1.19.1

o    Docker version : 20.10.7

·         ODL features installed to enable clustering:

o    odl-netconf-clustered-topology

o    odl-restconf-all

·         Device configured : Netconf devices , all devices having same schema(tested with 250 devices)

·         Use Case:

o    Fail Over/High Availability:

§  Expected : In case any of the ODL instance gets down/restarted due to network splits or internal error, other instance in cluster should be available and functional. If the affected instance is having master mount, the other instance who is elected as master by re-election should be able to re-register the devices and resume the operations. Once the affected instance comes up, it should be able to join the cluster as member node and register the slave mounts.

§  Observation : When the odl instance which is having the master mount restarts, election happens among the other node in the cluster and elects the new leader. Now the new leader is trying to re-register the master mount but failed at a point due to the termination of the Akka Cluster Singleton Actor. Hence the cluster goes to idle state and failed to assign owner for the device DOM entity. In this case, the configuration of already mounted device/ new mounts will fail.  

·         JIRA reference : https://jira.opendaylight.org/browse/CONTROLLER-2035  

·         Akka configuration of all the nodes attached. (Increased the gossip-interval time to 5s in akka.conf file to avoid Akka AskTimedOut issue while mounting multiple devices at a time.)

 

 

Requesting your support to identify if there is any mis-configurations or any known solution for the issue .

Please let us know if any further information required.

 

Note : We have tested the single ODL instance without enabling cluster features in K8s cluster. In case of K8s node failure, ODL instance will be re-scheduled in other available K8s node and operations will be resumed.  

             

 

Thanks & Regards,

Rohini

 


Re: ODL Clustering issue - High Availability

Ivan Hrasko
 

Hello,


what is the ODL version please?


Best,


Ivan Hraško

Senior Software Engineer

 

PANTHEON .tech

Mlynské Nivy 56, 821 05 Bratislava

Slovakia

Tel / +421 220 665 111

 

MAIL / ivan.hrasko@...

WEB / https://pantheon.tech




Od: integration-dev@... <integration-dev@...> v mene používateľa Rohini Ambika via lists.opendaylight.org <rohini.ambika=infosys.com@...>
Odoslané: streda, 27. júla 2022 13:19
Komu: integration-dev@...; dev@...; kernel-dev@...; kernel-dev@...
Predmet: [integration-dev] ODL Clustering issue - High Availability
 

Hi All,

 

As presented/discussed in the ODL TSC meeting held on 22nd Friday 10.30 AM IST, posting this email to highlight the issues on ODL clustering use cases encountered during the performance testing.

 

Details and configurations as follows:

 

  • Requirement : ODL clustering for high availability (HA) on data distribution
  • Env Configuration:
    • 3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node
    • CPU :  8 Cores
    • RAM : 20GB
    • Java Heap size : Min – 512MB Max – 16GB
    • JDK version : 11
    • Kubernetes version : 1.19.1
    • Docker version : 20.10.7
  • ODL features installed to enable clustering:
    • odl-netconf-clustered-topology
    • odl-restconf-all
  • Device configured : Netconf devices , all devices having same schema(tested with 250 devices)
  • Use Case:
    • Fail Over/High Availability:
      • Expected : In case any of the ODL instance gets down/restarted due to network splits or internal error, other instance in cluster should be available and functional. If the affected instance is having master mount, the other instance who is elected as master by re-election should be able to re-register the devices and resume the operations. Once the affected instance comes up, it should be able to join the cluster as member node and register the slave mounts.
      • Observation : When the odl instance which is having the master mount restarts, election happens among the other node in the cluster and elects the new leader. Now the new leader is trying to re-register the master mount but failed at a point due to the termination of the Akka Cluster Singleton Actor. Hence the cluster goes to idle state and failed to assign owner for the device DOM entity. In this case, the configuration of already mounted device/ new mounts will fail.  

 

 

Requesting your support to identify if there is any mis-configurations or any known solution for the issue .

Please let us know if any further information required.

 

Note : We have tested the single ODL instance without enabling cluster features in K8s cluster. In case of K8s node failure, ODL instance will be re-scheduled in other available K8s node and operations will be resumed.  

             

 

Thanks & Regards,

Rohini

 


ODL Clustering issue - High Availability

Rohini Ambika
 

Hi All,

 

As presented/discussed in the ODL TSC meeting held on 22nd Friday 10.30 AM IST, posting this email to highlight the issues on ODL clustering use cases encountered during the performance testing.

 

Details and configurations as follows:

 

  • Requirement : ODL clustering for high availability (HA) on data distribution
  • Env Configuration:
    • 3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node
    • CPU :  8 Cores
    • RAM : 20GB
    • Java Heap size : Min – 512MB Max – 16GB
    • JDK version : 11
    • Kubernetes version : 1.19.1
    • Docker version : 20.10.7
  • ODL features installed to enable clustering:
    • odl-netconf-clustered-topology
    • odl-restconf-all
  • Device configured : Netconf devices , all devices having same schema(tested with 250 devices)
  • Use Case:
    • Fail Over/High Availability:
      • Expected : In case any of the ODL instance gets down/restarted due to network splits or internal error, other instance in cluster should be available and functional. If the affected instance is having master mount, the other instance who is elected as master by re-election should be able to re-register the devices and resume the operations. Once the affected instance comes up, it should be able to join the cluster as member node and register the slave mounts.
      • Observation : When the odl instance which is having the master mount restarts, election happens among the other node in the cluster and elects the new leader. Now the new leader is trying to re-register the master mount but failed at a point due to the termination of the Akka Cluster Singleton Actor. Hence the cluster goes to idle state and failed to assign owner for the device DOM entity. In this case, the configuration of already mounted device/ new mounts will fail.  

 

 

Requesting your support to identify if there is any mis-configurations or any known solution for the issue .

Please let us know if any further information required.

 

Note : We have tested the single ODL instance without enabling cluster features in K8s cluster. In case of K8s node failure, ODL instance will be re-scheduled in other available K8s node and operations will be resumed.  

             

 

Thanks & Regards,

Rohini

 


Re: [OpenDaylight Infrastructure] [integration-dev] [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Sulfur SR1 release status

Luis Gomez
 

OK, release is done and patches are merged now.

On Jul 14, 2022, at 9:07 AM, Ivan Hrasko <ivan.hrasko@...> wrote:

Documentation chain:



Od: integration-dev@... <integration-dev@...> v mene používateľa Daniel de la Rosa <ddelarosa0707@...>
Odoslané: sobota, 9. júla 2022 5:21
Komu: Anil Belur; THOUENON Gilles TGI/OLN
Kópia: 'integration-dev@...' (integration-dev@...) (integration-dev@...); Release; TSC; OpenDaylight Infrastructure; Andrew Grimberg; Casey Cain; Rudy Grigar; Luis Gomez; LAMBERT Guillaume TGI/OLN
Predmet: Re: [integration-dev] [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Sulfur SR1 release status
 
Thanks Anil. 

Luis, as @LAMBERT Guillaume TGI/OLN  and @THOUENON Gilles TGI/OLN mentioned, they are done with their artifacts so please proceed with the distribution for Sulfur SR1

Now, in the absence of Guillaume, who can help with updating documentation? 

On Thu, Jul 7, 2022 at 3:56 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sulfur SR1 version bump is complete and the staging repository is being 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 SR1.
2. Release Distribution once step 1. is complete.
3. Release notes merge CR: https://git.opendaylight.org/gerrit/c/docs/+/101776
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Sulfur SR1 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://wiki.opendaylight.org/display/ODL/Sulfur+SR1+Release+Approval




Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Sulfur SR1 release status

Ivan Hrasko
 

Documentation chain:

https://git.opendaylight.org/gerrit/c/docs/+/101847/3




Od: integration-dev@... <integration-dev@...> v mene používateľa Daniel de la Rosa <ddelarosa0707@...>
Odoslané: sobota, 9. júla 2022 5:21
Komu: Anil Belur; THOUENON Gilles TGI/OLN
Kópia: 'integration-dev@...' (integration-dev@...) (integration-dev@...); Release; TSC; OpenDaylight Infrastructure; Andrew Grimberg; Casey Cain; Rudy Grigar; Luis Gomez; LAMBERT Guillaume TGI/OLN
Predmet: Re: [integration-dev] [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Sulfur SR1 release status
 
Thanks Anil. 

Luis, as @LAMBERT Guillaume TGI/OLN  and @THOUENON Gilles TGI/OLN mentioned, they are done with their artifacts so please proceed with the distribution for Sulfur SR1

Now, in the absence of Guillaume, who can help with updating documentation? 

On Thu, Jul 7, 2022 at 3:56 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sulfur SR1 version bump is complete and the staging repository is being 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 SR1.
2. Release Distribution once step 1. is complete.
3. Release notes merge CR: https://git.opendaylight.org/gerrit/c/docs/+/101776
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Sulfur SR1 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://wiki.opendaylight.org/display/ODL/Sulfur+SR1+Release+Approval


Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Sulfur SR1 release status

Daniel de la Rosa
 

Thanks Anil. 

Luis, as @LAMBERT Guillaume TGI/OLN  and @THOUENON Gilles TGI/OLN mentioned, they are done with their artifacts so please proceed with the distribution for Sulfur SR1

Now, in the absence of Guillaume, who can help with updating documentation? 

On Thu, Jul 7, 2022 at 3:56 PM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sulfur SR1 version bump is complete and the staging repository is being 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 SR1.
2. Release Distribution once step 1. is complete.
3. Release notes merge CR: https://git.opendaylight.org/gerrit/c/docs/+/101776
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Sulfur SR1 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://wiki.opendaylight.org/display/ODL/Sulfur+SR1+Release+Approval


Invitation: ODL Pipelines Meeting @ Tue Jul 12, 2022 22:00 - 23:00 (PDT) (integration-dev@lists.opendaylight.org)

Casey Cain
 

ODL Pipelines Meeting
Please use this registration link to register for the meeting. Once you've registered you will receive a unique Zoom URL to participate in the meeting. If you'd like to have someone else participate
 
Please use this registration link to register for the meeting. Once you've registered you will receive a unique Zoom URL to participate in the meeting. If you'd like to have someone else participate, do not share your Zoom URL, please use the URL in this invite:
https://zoom-lfx.platform.linuxfoundation.org/meeting/98955795719

When

Tuesday Jul 12, 2022 ⋅ 22:00 – 23:00 (Pacific Time - Los Angeles)

Location

https://zoom-lfx.platform.linuxfoundation.org/meeting/98955795719
View map

Invitation from Google Calendar

You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event.

Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more


[opendaylight-dev][release] OpenDaylight - Sulfur SR1 release status

Anil Belur
 

Hello All,

OpenDaylight Sulfur SR1 version bump is complete and the staging repository is being 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 SR1.
2. Release Distribution once step 1. is complete.
3. Release notes merge CR: https://git.opendaylight.org/gerrit/c/docs/+/101776
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Sulfur SR1 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://wiki.opendaylight.org/display/ODL/Sulfur+SR1+Release+Approval


[it-infrastructure-alerts][notice] ODL Gerrit maintenance window (17:30 Sun, July 10 2022 - 19:30 Sun, July 10 2022 PT)

Anil Belur
 

What: LF will update the ODL Gerrit system to 3.5.1.

When: 17:30 Sun, July 10 2022 - 19:30 Sun, July 10 2022 PT (10:00 Mon, July 11 - 12:00 Mon, July 11, 2022 AEST)

Why: LF will install system updates and update the Gerrit version to 3.5.1.
 
Impact: Users may not able to access other services (Gerrit, Jenkins, Sonar, Nexus) during this time.

Jenkins will be put in shutdown mode before the window starts and any long-running Jenkins jobs _will_ be canceled if they don't complete before the start of the window.
Notices will be posted to the mailing lists and in the #opendaylight channel on LFN-tech slack at the start and end of the maintenance.

Thanks,
Anil Belur


Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR3 release status

Luis Gomez
 

On Jul 1, 2022, at 2:53 PM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Hello Anil and all. 

TransportPCE has released their artifacts 

So Luis, please proceed with the distribution 

Thanks 

On Thu, Jun 2, 2022 at 12:47 AM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,

OpenDaylight Phosphorus SR3 version bump is complete and the staging repository has been promoted. The 'stable/phosphorus' branch remains unlocked and ready for development.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Phosphorus SR3.
2. Release Distribution once the 1. is complete.
3. Release notes - https://git.opendaylight.org/gerrit/c/docs/+/101432.
4. Update ODL downloads page [1.].

Many thanks to everyone who contributed to the Phosphorus SR3 release.

Regards,
Anil Belur

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

--
Daniel de la Rosa
ODL Release Manager



Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR3 release status

Daniel de la Rosa
 

Hello Anil and all. 

TransportPCE has released their artifacts 

So Luis, please proceed with the distribution 

Thanks 

On Thu, Jun 2, 2022 at 12:47 AM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,

OpenDaylight Phosphorus SR3 version bump is complete and the staging repository has been promoted. The 'stable/phosphorus' branch remains unlocked and ready for development.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Phosphorus SR3.
2. Release Distribution once the 1. is complete.
3. Release notes - https://git.opendaylight.org/gerrit/c/docs/+/101432.
4. Update ODL downloads page [1.].

Many thanks to everyone who contributed to the Phosphorus SR3 release.

Regards,
Anil Belur

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

--
Daniel de la Rosa
ODL Release Manager


[opendaylight-dev][release] OpenDaylight - Phosphorus SR3 release status

Anil Belur
 

Hello All,

OpenDaylight Phosphorus SR3 version bump is complete and the staging repository has been promoted. The 'stable/phosphorus' branch remains unlocked and ready for development.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Phosphorus SR3.
2. Release Distribution once the 1. is complete.
3. Release notes - https://git.opendaylight.org/gerrit/c/docs/+/101432.
4. Update ODL downloads page [1.].

Many thanks to everyone who contributed to the Phosphorus SR3 release.

Regards,
Anil Belur

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


Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

Luis Gomez
 

On May 12, 2022, at 10:56 AM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thanks Luis and Anil, So can we get a distribution now ? 

On Sun, May 8, 2022 at 5:40 PM Luis Gomez <ecelgp@...> wrote:
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:


BR/Luis

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.



Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

Daniel de la Rosa
 

Thanks Luis and Anil, So can we get a distribution now ? 


On Sun, May 8, 2022 at 5:40 PM Luis Gomez <ecelgp@...> wrote:
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:


BR/Luis

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.


Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

Anil Belur
 

Please review the following CR that adds a new job for chlorine stream on JDK17/CentOS8.


On Tue, May 10, 2022 at 8:49 AM Anil Belur via lists.opendaylight.org <abelur=linuxfoundation.org@...> wrote:
IIRC openjdk17 is going to be supported for chlorine, while the release was approved with openjdk11. 
We only have a single AR job that is building with openjdk11 for Chlorine, we should probably change this to support JDK11 and/or JDK17.

On Mon, May 9, 2022 at 6:17 PM Ivan Hrasko <ivan.hrasko@...> wrote:

The patch is using openjdk11 also for chlorine?

Is that correct?


I was expecting openjdk 17.


Best,

Ivan


Od: integration-dev@... <integration-dev@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: pondelok, 9. mája 2022 2:39:57
Komu: Daniel de la Rosa
Kópia: THOUENON Gilles TGI/OLN; LAMBERT Guillaume INNOV/NET; Anil Shashikumar Belur; integration-dev@...; Release; OpenDaylight Discuss; TSC; Casey Cain; Andrew Grimberg; Transportpce-dev@...
Predmet: Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
 
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:


BR/Luis

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.





Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

Anil Belur
 

IIRC openjdk17 is going to be supported for chlorine, while the release was approved with openjdk11. 
We only have a single AR job that is building with openjdk11 for Chlorine, we should probably change this to support JDK11 and/or JDK17.

On Mon, May 9, 2022 at 6:17 PM Ivan Hrasko <ivan.hrasko@...> wrote:

The patch is using openjdk11 also for chlorine?

Is that correct?


I was expecting openjdk 17.


Best,

Ivan


Od: integration-dev@... <integration-dev@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: pondelok, 9. mája 2022 2:39:57
Komu: Daniel de la Rosa
Kópia: THOUENON Gilles TGI/OLN; LAMBERT Guillaume INNOV/NET; Anil Shashikumar Belur; integration-dev@...; Release; OpenDaylight Discuss; TSC; Casey Cain; Andrew Grimberg; Transportpce-dev@...
Predmet: Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
 
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:


BR/Luis

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.





Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status

Ivan Hrasko
 

The patch is using openjdk11 also for chlorine?

Is that correct?


I was expecting openjdk 17.


Best,

Ivan


Od: integration-dev@... <integration-dev@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: pondelok, 9. mája 2022 2:39:57
Komu: Daniel de la Rosa
Kópia: THOUENON Gilles TGI/OLN; LAMBERT Guillaume INNOV/NET; Anil Shashikumar Belur; integration-dev@...; Release; OpenDaylight Discuss; TSC; Casey Cain; Andrew Grimberg; Transportpce-dev@...
Predmet: Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
 
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:


BR/Luis

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.

1 - 20 of 14631