...
available at TransportPCE meetings
https://lf-opendaylight.atlassian.net/wiki/display/ODL/TransportPCE+meetings
2024-11-21
General Information
- We still need to update the revision notes for Sc SR1.
Code Review
- No merged change this week.
Changes transportpce under review on master branch:
- “Handle modifications in existing RPCs and new RPCs”, “Create topo Context at Init for Alien & SBI”, “Add Tapi Abstracted Node to OR Topo” and “Add Func Test for Topology extension” pass the gate and are ready for merge after a clean-up.
- Relation Chain of Smartoptics :
- “Consistent cent. freq. width decimal precision” Corrects an issue where the nr of decimals for central frequency was 4 in ZtoA direction and 5 in AtoZ direction
- “Implement service-format 'other'” : This update introduce a new service-format which ensures the mc interface is 8GHz wider than the nmc interface.
- “Implement client create service frequency choice” : Implement the augmentations found in transportpce-service-spectrum-constraint@2023-09-07.yang. The opportunity for this change was discussed during the meeting and it revelency needs to be investigated.
- “New packages simplifying picking service frequency” : simplify selecting an available frequency range from which a subset may be setup for a new service. It has been reviewed by Olivier and LGTH.
- “Augment service-create adding frequency properties” : the yang file has be renamed from com-smartoptics-openroadm-service.yang to transportpce-service-spectrum-constraint. This change is ready to be merged unless there are clarifications to be made on ranges of values to be specified in the model.
- “Check if SRG has available PPs before access” : If all PPs are used for any SRG, node validation will crash in getRdmSrgClient because it tries to access the first element of the empty available PP set, causing path computation failure even if there are other SRGs with available PPs. This fixes the issue by moving the existing check for empty available SRG PPs to before trying to access the first element. The change is ready for review and passes the gate.
- “Ignore end node without available TPs in PCE” corrects a bug so that a node that has no available tps is effectively ignored. It is ready for review and passes the gate
- “Set ServiceFeasibilityCheck to false for some rpcs” from Jonas has been rebased and passes the gate. The change has been reviewed by Olivier. If Christophe review is positive, this change could be merged.
- “Add CEPlist to OTS NEP at init” : Add Cep list to Owned node edge points for Xponders at initialization corresponding to T0 configuration. This change allows completing the topology as required for the purpose of debugging the relation chain associated with the PCE link and node classes.
- “Fix ROADM provisioning for 7.1 models ” : Bala has added his signoff so that the change passes the pre-commit, but asks not to merge the change since additional work is needed. Especially when a 2.2.1 ROADM is connected first and a 7.1 connected after, the neighbor is not recognized and the links between them are not created. Bala needs to update some codes in the OLM to implement for 7.1 span-loss retrieval.
Other items
- Olivier briefly introduced the way topology extensions are managed
2024-11-14
General Information
- Scandium SR1 has been released the 11th of November. We still need to update the release notes.
Code Review
3 changes merged during the week : “Adjust tox ini tests sequencing”, “Yang file to augment OR Topology”, and “networkutils RPCs adjusted for topo extension”. This corresponds to the bottom relation chain on TAPI work.
Changes transportpce under review on master branch:
- “Handle modifications in existing RPCs and new RPCs” passes the gate and is ready for merge.
- “Add Tapi Abstracted Node to OR Topo” : still does not pass the gate but is probably due to an issue on the gate (221 tests).
- “Add Func Test for Topology extension” : still does not pass the gate but is probably due to an issue on the gate (221 tests).
- “Uninstall tapi feature at the end of functional tests” is a standalone change that could be merged on other branches than master (on master branch, the code it is already integrated in “Add Tapi Abstracted Node to OR Top”). The purpose of the change is to uninstall the tapi feature at the end of each tapi functional test.
- “Migrate to Apache Pekko” : allows to use Pekko in place of Akka. This change does not pass the gate. Robert has been added as a reviewer to help understanding us why.
- Relation Chain of Smartoptics : The changes at the bottom of the stack have been merged. Joakim shall rebase next changes on the master branch.
- “Augment service-create adding frequency properties” : the yang file shall be renamed from com-smartoptics-openroadm-service.yang to something like transportpce-service-spectrum-constraint.yang : including the name of an OEM in the title of the yang file suggests that this file is dedicated to specific equipment, which is not the case. Also having openroadm in the title could bring confusion as this is an extension of openroadm models but is not part of them.
- “Set ServiceFeasibilityCheck to false for some rpcs” from Jonas shall be rebased to check that it passes the gate.
- “Fix ROADM provisioning for 7.1 models ” : Bala shall add his signoff so that the change passes the pre-commit.
2024-09-19
General Information
- Scandium is not released yet because of some regressions detected in the NETCONF project. So we are waiting for the availability of the latest NETCONF dependency. Robert published this afternoon netconf-8.0.2 which corrects the bug we reported for the swagger issue.
- Ca-SR2 release is also pending for the same reason.
Code Review
No change merged during the week
Changes transportpce under review on master branch:
- Olivier pushed the relation chain associated with Node and Link Classes built for the T-API PCE on master, and set to abandoned more or less outdated corresponding changes on stable/calcium. This includes 4 changes, the initial one “Initial Tapi-2.1 node and link classes for PCE” focusing on 2.1 model that will never pass the gate since it does not compile (using unsupported Tapi models). The second , “Initial T-API 2.4 PCE link & Nodes Classes" that provides the classes based on current T-API model 2.4. “Add Tapi Topo File for test" provides the topology file that will be used for tests. Last one “Add Junit tests of Tapi link & Node classes” provides the test associated with these classes. All these changes are defined as WIP. They will be set as Active as soon as the test files have been refreshed with the latest version that allows going through all Junit tests.
- “Update portmapping model” should be abandoned. This change was pushed by Olivier but was done making a wrong assumption about the supporting-odu4 is configured in PortMapping and used later on. “Corrections of 121 tests (portMapping update)" shall also be set as abandoned.
- “Populate OM in portMapping and Topo” could be merged as soon as someone review it and potential adaptations are performed.
- “Fix a few bugs processing Topo” could be merged as soon as someone review it and potential adaptations are performed.
- “Link node Id to node name conversion in TAPI” has been submitted by Joakim. It Corrects an issue where a value such as ROADM-A-xxxxx would not return the node name ROADM-A. Joakim integrated the comments.
2024-09-12
General Information
- Scandium shall be released next week. Gilles released tpce artifacts. But some regressions were detected in the NETCONF project. So we will need to take into account the new NETCONF version.
- Gilles also started the release process for Ca-SR2 but NETCONF project has the same impact.
- Gilles raised a Jira Ticket NETCONF-1386 to highlight the fact that the swagger interface is again not working.
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
- Gilles reworked the relation chain of Olivier, squashing “modify imports to use last version of PortMapping” in change 113427
- Olivier made some corrections to “Update portMapping models” which allows passing 221 & tapi tests locally. However he stills experience some issues with 7.1 and hybrid tests, and requires help since the issues do not seem to be directly related to the adjustment.
- Nothing new this week on other changes.
2024-09-05
General Information
- Scandium shall be officially released in 2 weeks. Tpce Scandium migration is almost done.
- CA-SR2 is almost 1 month late. Gilles backported some changes on the stable/calcium branch. He is experiencing a lot of CI issues, mostly with maven-verify job. The root cause could be on the aaa project. It seems that, among other things, passwordService dependency is missing for org.opendayligth.aaa.datastore.h2.H2Store bundle.
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
- Some changes have been backported, but some tests do not pass, and maven-verify systematically fails on the different feature tests
- The changes concerning TAPI are in a different states than what has been pushed on master. This will need to be solved and clarified.
2024-08-29
General Information
- ODL's TSC has just been renewed: Technical Steering Committee (TSC) - OpenDaylight - Confluence (atlassian.net)
- Code Freeze for Scandium happened 2 weeks ago. Master branch shall be migrated to Titanium. The ODL Scandium release is planned on the 19th of September.
- Our ODL JIRA and Wiki have been migrated to Altassian Cloud. For Jira a double authentication is needed. Some convenient features have been lost (link with Gerrit change associated with the Jira Ticket not yet effective).
- LFN is thinking moving the tox-verify jobs from Jenkins to Github Action
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
- changes related to the IPoWDM use case and just upadated by Bala. They are now in review:
- “Add common-id to path-computation”: OK for merging, but before add a Jira ref
- “Read optical-operational-mode in temp-service-create” allows retrieving the op-modes provided in the requesting-interface-properties container of temp-service-create, which is needed for path computation with external pluggable. It currently fails at the service handler level. JUnit tests of servicehandler still need to be updated with code modification done.
- “Add OSNR calculations for IPoWDM use case” provides impairment aware path computation according to the operational modes provided in the temp-service-create in IPoWDM use case. Olivier shall review this change.
- One change from Ivan Hraško on migration from akka to Apache peko:
- “Migrate to Apache Pekko”: we need to wait for change111858 on controller project to be merged before merging it.
- changes on TAPI module proposed by Smartopics:
- “Frequency rounding error in GridUtils” is a new bug detected by smartoptics. At first sight, we are ok with this fix
- "Error due to empty list of XPDR in TAPI", "Error due to duplicate roadm node id key in TAPI", "Error in TAPI creating frequency ranges" are other bugs detected in TAPI. OK with that, but they are above the following change that still need a review...
- "New Tapi package dealing with frequency BitSets": proposes a new TAPI package dealing the frequencyBitSets. After exchange between Joakim and Olivier, this package has been refactored by Joakim… Need to be reviewed again by Olivier (and others)
- “Upgrade lightynode to Ca-SR1” : Gilles prefers to merge this change after major issues related to scandium migration have been fixed in order to have a stable simulator version for tests
- “Bump Upstream dependencies for 2024.09 Scandium”: Gilles started the migration of master branch to scandium. The compilation with JUnit tests is OK, but lots of functional tests are failing for two main reasons:
- the return of the request when the requested data in the datastore does not exist changed
- the netconf device notification registration is no longer effective with lightynode simulator (it works with honeynode, but honeynode is no longer used for TPCE functional tests on the CI)
- Gilles reported these issues towards upstream projects. Waiting for their feedbacks...
2024-07-25
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
Migration to Scandium shall start soon. Scandium will require Java 21 and Maven 3.9.5 for build and run.
The gate is in bad shape!
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
- ODL scandium release (planned for September) is underway in upstream projects: wil require Java-21 for build and runtime, and Maven-3.9.5+
Code Review
Changes transportpce under review:
...
Ca-SR1: has been approved by the TSC so that it shall be released in a short time
Code Review
Changes transportpce under review:
...
Ca-SR1: is still under TSC validation
K-SR3 has been released.
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
Ca-SR1: shall be under TSC validation, but a new issue has been identified in the NETCONF project. We could need to respin it...
K-SR3: Gilles released TPCE artifacts today morning. The release candidate shall be under TSC validation today.
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
Ca-SR1 shall be under TSC validation, but an issue has been identified (One dependency update on the AAA project was forgotten). Ca SR1 release process need to be respined now.
K-SR3 should be ready by 2 weeks.
Code Review
No change merged during last week.
...
Ca-SR1 is under progress: Gilles backported from master all changes of interest for the release. An issue detected by our functional test has been solved thanks to Pantheon regarding Lighty.io, but we still experience lots of issues with the gate, due to several cumulative issues on the infrastructure. Need to relaunch everything...
K-SR3 should start very soon.
Scandium is planned for September.
Code Review
Changes transportpce under review:
...
Ca-SR1: tpce artifact will need to be published next week as soon as the Netconf dependency is available.
K-SR3 should have been released last week, so it will come soon.
Scandium is planned for September.
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
No Meeting. Public holiday.
2024-05-02
Code Review
Changes merged since last meeting on transportpce:
...
LFN DTF summit will be hold on the 2nd and 3rd of May in San Jose. Deadline for registration is on the 12Th of May.
We are using Teams for tpce meetings, and the LFN recommends to use their Zoom tool. However neither Orange nor AT&T company authorize to use zoom tool...
Gilles published last week TPCE artifacts for Ca. For what concerns tpce, everything has been done. The distribution shall be released next week after the TSC as approved it.
A change in Netconf is currently under review to solve our OpenAPI issue.
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
Ca GA is still under progress and should be available very soon now. TPCE is more or less the only project that needs to be released now.
- Transportpce has been demonstrated last week during the OFC event. Bala provided some feedbacks. A lot of people followed the event this year and there was a lot of visitors on OpenROADM booth
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
LFN migrated its servers from US to Europe: as a result, JIRA, Gerrit and CI/CD experienced some issues that have been rather solved.
Ca should have been released on the 14Th but it is still under preparation.
Code Review
Changes merged since last meeting on transportpce-models and transportpce:
...
Ca release is on track. It is targeted the 21st of March. The TPCE master branch migration to Ca is in good shape.
- Registration and topic submission period is still open for the next DTF (Developer and Testing Forum) which will happen in San Jose the 2nd and 3rd of May.
Code Review
Changes merged since last meeting on transportpce-models:
...
Topic submission period is still open for the next DTF (Developer and Testing Forum) which will happen in San Jose in April.
- Ca preparation is ongoing with the target of 21st of March
Code Review
Changes merged since last meeting on transportpce-models:
...
Topic submission period is open for the next DTF (Developer and Testing Forum) which will happen in San Jose in April.
Code Review
Changes merged since last meeting on transportpce-models:
...
- The annual LFN 2024 mentorship program has been launched. Selection progress is already started. The deadline for submission is the 17th of March. This program allows mentoring students that are willing to contribute to a project.
Code Review
Changes merged since last meeting
...
- Next DTF Development and testing Forum will be hold in San Jose, collocated with ONE summit the 2nd and 3rd of May
Code Review
Changes merged since last meeting
...
ODL distribution for K-SR2 is released. Release notes have been updated.
Gilles started the migration of master branch to Ca (targeted mid-March) which seems to have important side-effects on TransportPCE current implementation. Hope it will not be too much difficult to adapt...
Code Review
Changes merged since last meeting
...
Potassium SR2 has just been approved by the TSC and the ODL distribution shall be released soon. For TransportPCE, the last changes that were pending (release note update in docs project) have been merged by Guillaume.
Gilles will probably start the migration of Master branches to Ca next week.
Robert informed the community about a migration to Java 21st planned in Ca SR1, and imposed in Scandium.
Code Review
Changes merged since last meeting
...
- Gilles released TransportPCE artifacts for K-SR2 + prepare its integration inside ODL distribtuion + prepare the release note on docs project
Code Review
Changes merged since last meeting
...
- Olivier is working on correcting and completing the OpenConfig device configuration for the lightynode simulator, making it closer to what we observe with equipment in the labs.
2024-01-18
Code Review
No change merged since last meeting
...
Sprint 34 was initiated. All non-closed issues of previous sprint have been included. An additional issue #774 was introduced : Create an OpenConfig configuration file. Some JIRA ticket describing OpenConfig models to be introduced in tpce models need also to be created.
Christophe made a small project to illustrate the bug we have in lightynode for openroadm-device 7.1 models (handling when statement). He reported the issue on the odl-kernel list. The Issue is identified in the yangtools project, but it seems difficult to solve it, and no solution will be provided in a short time. 2 workarounds have been proposed.
Bala is trying to fix the way we are building A and Z end containers in service-create and temp-service-create so that he can retrieve the operational mode supported by external pluggables to address IPoWDM case.
He also started to implement the power control RPC to address IPoWDM use case.
Bug: When we specify the port to use in the service-create (for SRGs ending an optical tunnel), tpce is currently picking the port based on first port available, not considering the port specified in the service-create. Gilles started to work on this bug but did not have the time to work on any use case. He asked Bala to create a JIRA ticket to better understand the associated use case.
2024-01-11
Code Review
changes merged since last meeting:
...