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).
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
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) ondata distribution
·Env Configuration:
o3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node
oCPU : 8 Cores
oRAM : 20GB
oJava Heap size : Min – 512MB Max – 16GB
oJDK version : 11
oKubernetes version : 1.19.1
oDocker version : 20.10.7
·ODL features installed to enable clustering:
oodl-netconf-clustered-topology
oodl-restconf-all
·Device configured : Netconf devices , all devices having same schema(tested with 250 devices)
·Use Case:
oFail 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.
·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.
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
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) ondata distribution
·Env Configuration:
o3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node
oCPU : 8 Cores
oRAM : 20GB
oJava Heap size : Min – 512MB Max – 16GB
oJDK version : 11
oKubernetes version : 1.19.1
oDocker version : 20.10.7
·ODL features installed to enable clustering:
oodl-netconf-clustered-topology
oodl-restconf-all
·Device configured : Netconf devices , all devices having same schema(tested with 250 devices)
·Use Case:
oFail 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.
·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.
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) ondata 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.
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.
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
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) ondata distribution
·Env Configuration:
o3 node k8s Cluster ( 1 master & 3 worker nodes) with 3 ODL instances running on each node
oCPU : 8 Cores
oRAM : 20GB
oJava Heap size : Min – 512MB Max – 16GB
oJDK version : 11
oKubernetes version : 1.19.1
oDocker version : 20.10.7
·ODL features installed to enable clustering:
oodl-netconf-clustered-topology
oodl-restconf-all
·Device configured : Netconf devices , all devices having same schema(tested with 250 devices)
·Use Case:
oFail 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.
·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.
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) ondata 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.
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.
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) ondata 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.
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.
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.
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.
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.
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)
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 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.
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.
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.].
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.].
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.].
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…
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.
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.
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…
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.
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.
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…
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.
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.
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…
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.
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.
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…
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.
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.
