2021 meeting minutes

available at TransportPCE meetings
https://wiki.opendaylight.org/display/ODL/TransportPCE+meetings

• Since the last meeting, a large number of changes have been merged:

  • Changes associated with OTN implementation with intermediate switches

  • Migration of some of the functional tests (topology) towards RFC 8040

  • Changes associated with TAPI implementation: the sequence of the changes has been changed. The initial change associated with OTN link removal has been modified so that OTN links are not removed from the Abstacted T0 Multi-layer topology.

  • Reactivation of Unitary test for renderer.

  • “Remove forced revision imports in few tpce models”

  • ”Unofficial regenerator capability support in Yang” : some identities supported by some suppliers are no more the official one (R7.1). We agreed with Bala to modify the official model but some details need to be provided in a notice so that users understand it. Guillaume made what was needed to close the change which was merged.

  • _Power control support for 87.5 GHz spectrum width: Gilles reworked it, rebasing it, and solving issues appeared after the merge of the renderer unitary tests activation.

  • “Increase transportPCE tox verify job timeout” allows solving some issues with the gate

  • Guillaume opened a comment on the already merged change: ”Tapi Link creation refactoring”: Guillaume solved an issue associated with the support to lighty.io in another change. So, the comment may be closed now.

• All these changes have been backported on the stable/phosphorus branch.

• The following changes are still under review:

  • TAPI changes concerning notifications:

    • a new change “Fix few NPE in TAPI implementation” has just been pushed by Christophe and Gilles to fix some NPE in TAPI implementation, when creating 100GE service over TPDR

    • Javier rebase the TAPI series related to TAPI notifications

  • Reactivation of lighty : “Add and fix Phosphorus lighty.io”; A few things have been changed in the PortMapping. Need to be reviewed again.

  • "Enforce Pylint in CI via tox is mergeable". The Pylint configuration has been customized to make it fit with our needs. Fix me has been disabled on redundant code. It may however need to be rebased.

  • “Use environment variable for OLM timers”: this change proposed by Gilles and Christophe will allow to set specific OLM timer values according to specific environment variable set or not before launching Karaf. It allows decoupling the build step from the runtime step. Thus, we can change OLM timer values without having to recompile again, depending on the usage (test on real equipment versus test on HoneyNode simulators.

• Other Open changes in WIP:

  • Migration to Service model 10.0: we are waiting until R10.1 of OpenROADM is publically released to migrate directly to this last that brings some corrections that will ease the migration.

  • Final step of the migration of functional tests towards RFC 8040 has been put on hold

• Next DDF:  preliminary planning has been sent by Guillaume, who is proud to have 5 subjects proposed around transportPCE.

• It was the last meeting of the Year 2021. Next TransportPCE meeting will be hold the Jan 6, 2022 . In the meantime, Happy New Year's Eve

• P SR1 : approved and available for download. P SR2 is planned for the end of January.

• A question was sent by Santh about a compilation failure issue with TransportPCE. Guillaume answered, considering it was probably a Tail-f issue. The issue has been partially solved, and the device is now correctly mounted. However there are some remaining issues. Guillaume identified that it could be an issue with NETCONF (Santh uses Al distribution). His suggestion is to migrate to a more recent version.

• Since the last meeting, only one change has been merged: “Fix remaining Pylint warnings apart fixme & dup”

• There are more than 40 open changes which are in review.

• Gilles and Christophe have agreed on a strategy for tomorrows demo. The relation chain of changes related with T-API will be split into 2. They have reordered some of the changes so that they can merge earlier the 3 following changes : “Adaptation of xpdr mapping from OR to TAPI”, “Tapi link creation refactoring” and “Fix tapi get-topology-details functional tests”. Remaining chain of OTN changes has been put on top of this and is in the last review step.

• We are currently experiencing some issues of the gate.

  • The fix proposed by Javier to solve the issue associated with test 16 seems not to work. We still experience the issue. Javier is still trying to simulate the issue locally.

  • Some other changes fail due to either an issue to launch sims121 or an issue launching TransportPCE controller for tests221: according to Guillaume, this could be due to resource starvation issue (at the hyperviser level). He suggests we raise a ticket.

• Christophe highlight the fact that any change submitted should include some functional tests as soon as a new functionality is introduced. This shall be applied to the case of the change that were initiated by Peter. Javier agrees with this and will work on it.

• “Reintroduce nb-bierman02 support in new functional tests”, “Migrate topology funct tests to RFC 8040 step 1, 2 & 3” have been proposed by Guillaume and are under review.

• Migration of Service Model to 10.0: Gilles proposed 3 changes on this topic:

  • “Remove fix revision imports in tpce yang models” prepares the migration by removing revision forcing in TransportPCE yang models, and will allow to always retrieve the latest model revision available

  • “Upgrade to service Model 10.0” is the model migration in itself. The issue encountered compiling the new service model has been raised in OpenROADM MSA (Issue 853). PR 855 is solving this. It was presented this afternoon, and nobody complained. So it shall be part of service model 10.1. Olivier suggests to put this change in standby and wait until we get service model 10.1 available. This change breaks the API so that it will proposed for Sulfur.

  • “Remove service-endpoint grouping” does basically what we requested in OpenROADM Service model 10.1 through PR855. As observed on gerrit, it solves the compiling issue.

• Guillaume proposes to rework the change proposed by Bala “Model 7.1 change to support regenerator capability” so that we can have an “acceptable” solution

• “Power control support for 87.5 GHz spectrum width” : Shweta will try to address this changes before going for holidays.

• Next DDF: 5 subjects have been proposed around transportPCE by Nokia and Orange.

• Last public TransportPCE meeting of the year next week on the 16^th.

• P SR1: Christophe successfully released transportPCE in P SR1 the 30th of November.

  • The main features introduced in SR1 correspond to around 50 changes (100GE over OTN switches, T-API improvements, start of migration of functional tests toward RFC 8040, and a number of fixes).

  • P SR1 was approved.

  • Gilles updated docs project with the TransportPCE release notes.

  • P SR2 is scheduled for the 27^th of January 2022.

• RESTCONF api will change. Guillaume has initiated some work to migrate from Bierman to RFC8040 which will help to support this migration.

• Since the last meeting, the following changes have been merged:

  • “Fix some/more Pylint warnings” and “bump network dependency to 2.0.11” solves the issue of the Hexadecimal trace in the Logs.

  • Gilles will backport these changes on stable/phosphorus branch

• change 98757: “Set xponder-type in the mapping for transponders”:

  • for Xponders we put the type of xponder (mux or switch) which is embedded in the list of xponder in the device configuration, with the exception of  transpornders, we are still not putting anything in the mapping since in Release 1.21.1 this list and types were not provided by the devices. So when we don’t have the list of transponder we will put in the portmapping the “tpdr” type.

• change “Fix tapi get topology details functional test”: the change instead of using Databroker use network transaction service which allows providing a more reliable behavior

• change “Tapil ink creation refactoring”: provides a unification of tapicreatelink and TapiLinkUtil and avoids code duplications

• change “Adaptation of XPDR mapping from OR to TAPI”: solves some bugs and provides some modification of the way NEP are created

• change “OTN link deletion from T-API topology”: transforms OTN link to TAPI connections to be in line with TAPI implementation

• change “Unification iNodeEdgePoint _N and iNodeEdgePoint_N”: allows to use the same naming convention for this NEP in both the T0 and the T0 Full Multilayer topology.

• change “OpenROADM Xpdr link TAPI listener”: allows creating links directly from the update in the OpenROADM topology rather than using specific rpc to create roadm to roadm links and Transponder to roadm links

  • Christophe raised the question about the deletion of T-API links. => we need to confirm if the rpc delete link runs correctly for openroadm topologies

• change “Tapi connectivity upgrade”: Implementation of 100GE services in Tapi as an Ethernet service and OTN services for Muxponders and switchponders

• Javier has also been working on the TAPI notification services already addressed in the previous meeting.

• OTN switch changes series: Gilles will start addressing the comments received so far very soon.

• Guillaume also pushed 3 changes on Pylint and functional test migration towards RFC8040. “Enforce Pylint in CI via Tox”, “Fix remaining pylint warnings apart fixme & dup”, “Migrate topology functional tests to RFC 8040”

• Gilles started the work to migrate the service models to R10.0. But we have an issue and Christophe raised the corresponding issue in OpenROADM community.