available at TransportPCE meetings
https://wiki.opendaylight.org/display/ODL/TransportPCE+meetings
ODL Argon release: we should release ODL Ar today. Last week, Gilles released all artifacts related to transportPCE after having merged all pending changes. Will remain the documentation to handle. Olivier will write a paragraph on impairment aware path computation.
Next deadline is Cl SR-3 on the 8th of May
Sulfur shall also be End of Life today. However, ODL community proposed to release Sulfur SR-4 as a courtesy release. We are invited to provide the corresponding tpce artifacts.
OFC: Nokia presented a demo “Network Management as code”. Javier will share the paper. Nokia also shared in OFC some elements on T-API 2.4. There were almost more than 11000 attendees in OFC this year, which brings it to the level we had before the pandemics. Nathan made different demonstrations based on One Engine and TransportPCE. UTD observed some contention issues with tpce when PMs are also polled by One-Engine. The provisioning of a service then can fail. Nathan changed the code to poll the PM directly from the device rather than passing through tpce. The problems is associated with configuration locking while reading the configuration and potential associated time-out. Guillaume mentions that this could happen when device do not have any candidate Data Store. Gilles mentioned that his recent change on the refactoring of the RequestProcessor class may solve this kind of concurrency issue.
Status on changes merged since last meeting:
Argon will be released the 16th of March. We are almost ready on transportPCE side. We will just need to bump the upstream dependencies to their latest version. Sulfur will be at that time EOL.
Cl-SR3 is targeted on the 8th of May
Status on changes merged since last meeting:
UTD question (Nathan) about the issue with Karaf Logs: is it still the case with the latest versions of PCE?
The Karaf client, no longer working is an issue we had some time ago, and which is not solved with the current Karaf version. It is an upstream bug in the Apache Karaf project. Karaf server is however still usable. So Karaf client does not need to be launched to observe the logs. However for UTD who wants to extract some messages from the LOG, it could be an issue. Lighty was not deeply tested by UTD. UTD is asking whether they should move to Lighty to solve this issue. Gilles answers that to him the real way to solve the issue is to use the nbi-notification module. However Nathan mentions that a lot of information is needed by their application, which would imply to write a lot of code to complement current implementation. Gilles explained that each TransportPCE module communicates to other modules through the mdsal-notification mechanism. Looking at the logs, it is quite easy to figure out which are the notifications sent through this process, and if need be, complement them and filter them from the Karaf Logs...
Status on changes merged since last meeting:
Gilles created a new relation chain of changes in the scope of the migration to Argon:
Since a while, Bala has experienced some issues with the equipment in the labs, on their candidate datastore, deleting interfaces (this is even not using the renderer, but doing it directly on the device pointing to the right url). He will provide more details about it.
Gilles observed on his side that we regularly lose during the tests some Netconf sessions. Bala observed previously the same kind of issues which were solved setting the Time_To_leave parameters.
Status on changes merged since last meeting:
OpenROADM device model update: it seems more reasonable to update the device model directly to 12.1 rather than 10.1, since it should cover all required functionality (GCC option, Y cable, 800G modeling…)
Status on transportpce changes merged since last meeting:
Status on transportpce changes merged since last meeting:
An equipment manufacturer works on R10.1 of device models. Bala did not identified major changes from 7.1 to 10.1. But the support is required in PortMapping. Rendering part should not be that much affected. The migration to 10.1 shall be needed to test the product as it will be released in the Open Lab. Currently UTD has one of their equipment which is a Switchponder with 100G line port. But the new unit shall be a 400G transponder. Having an example of configuration file for TPCE sims would help a lot.
Gilles released last week transportpce artifacts for Cl-SR2. ODL distribution Cl-SR2 should be delivered very soon, on time
Tomorrow is the deadline for submitting topics to the LFN DDF (13th to 16th of February) which will be virtual. Registration is free of charge. https://wiki.lfnetworking.org/display/LN/2023-02+LFN+Developer+Event+Topics+February
Guillaume proposed a contribution about the migration of the tests towards RFC 8040.
For mentorship (trainees can be funded by LFN), the deadline is the 3rd of March : https://wiki.lfnetworking.org/display/LN/LFN+Mentorship+Program
Status on transportpce-models changes merged since last meeting:
Status on transportpce changes merged since last meeting:
Bala is using Inteligy IDE, but can’t see the import of the OpenROADM yang files. This is associated with the move of those to transportpce-models dedicated repository. They should appear in external-dependencies when selecting project files view in this IDE.
Gilles released last week transportpce-models artifacts for Cl-SR2, and is planning to release transportpce Cl-SR2 artifacts tomorrow
Status on transportpce-models changes merged since last meeting:
Status on transportpce changes merged since last meeting:
Sprint 31 started at the end of the session
Status on transportpce changes merged since last meeting:
"Remove getNode method from OlmUtils": uses get node method of PortMapping rather than creating a redundant one in OLM Utils.
Status on transportpce-models changes merged since last meeting: all changes are associated with the integration in Cl-SR1, and bump of upstream dependencies to Cl-SR2
Status on transportpce changes merged since last meeting:
Sprint 30 shall be finished. We proposed during the meeting to organize the demo next week after the regular tpce meeting. The sprint demo can be recorded. Please contact Gilles if you can not attend and expect it to be recorded or if you prefer that we reschedule it.