2021 meeting minutes

Meetings connection details

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

12/16/2021

Code Review

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

Q&A

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 06 Jan 2022 . In the meantime, Happy New Year's Eve

12/09/2021

General information

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.

Code Review

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.

Q&A

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.

12/02/2021

General information

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.

Code Review

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.

Q&A

Next DDF:
- Gilles and Christophe proposed as a topic, an Overview of transportPCE feature, including a short demo
- Nokia will also propose 2 topics: one about what they have done in transportPCE, one about what they plan to do next
- Guillaume has proposed one topic on release management, and one about tox jobs parallelization.

11/25/2021

General information

P SR1: the release has been postponed two weeks later (MRI project not ready yet) to the 2^nd of December. transportPCE shall then be staged between the 2^nd and the 9^th of December
Releng project shall move to Maven 3.8.
Transportpce mailing list: a mail was sent by Shanth with regards to issues experienced when connecting to Cisco devices. Some additional logs were sent but logs are only partial. Guillaume shall provide an answer.
Last TSC meeting summary provides a link to connect to Slack dedicated to discussions with the ODL community.

Code Review

Since the last meeting, the following changes have been merged:
- the beginning of the otn suite (merged and backported to stable P branch)
- the bump to netconf dependencies to 2.09, and then to 2.0.10. As a result, now part of TransportPCE LOG includes Hexadecimal codes when connecting to a NETCONF device. This issue has been raised to Robert who shall fix it very soon.
- Guillaume made some changes related with migration towards RFC8040, “Migrate portmapping functional tests to RFC8040” (merged, to be backported to P), “Run pre-commit autoupdate”, “Enforce Autopep8”, “Remove u prefix obsoleted by python 3”, “Fix some Pylint profile” (could be merged), “Enforce Pylint with a score >=8.97 in CI” (not to be merged)
- ”Fix null Supported CEP Qual. on TAPI node creation“ has still one comment to be addressed. A Jira ticket could be created to keep trace, allowing to merge this change
A lot of changes failed last week, probably due to instability with T-API tests.
- “Fix tapi get-topology-details functional test” should solve this issue
- All Changes related to the use of intermedaite otn-switches shall be rebased on this fix to check on the gate its positive effects.
T-API changes suite:
- Tapi link creation refactoring tries to reduce code duplication, and includes latest changes associated with proposed link naming convention
- Update TAPI connectivity service on port change : Christophe is currently testing it.
Gilles will backport all recently merged changes on the stable P branch.
Robert recently released Si SR3.4 to address some Netconf issues (Si SR4 is not planned)
- We may experience an issue with Si SR3, because the test suite for tox parallelization implies to be activated on releng project, what has not been done yet...

Q&A

Next DDF:
- we can submit some topics until the 4^th of December here: https://wiki.lfnetworking.org/display/LN/2022+LFN+Developer+Event+Topics+January
- Guillaume will propose a talk on the different way to manage projects (MSI/ MRI/self-managed) and another talk about tox test parallelization
- Highstreet will probably propose a topic on ONAP and Tpce
- Guillaume suggest to proposed talk to introduce the tpce roadmap
- Javier would like to propose a talk about T-API development performed on tpce with probably a small demo and another talk could be about what Nokia plans for next transportPCE contributions.

11/18/2021

General information

TransportPCE was released on the 5th of November for Si SR3. Since we release TransportPCE (SM project depending only from MRI upstream projects) before MSI projects, it led to exchange on the community, and Robert highlighted that tpce could become an MRI project. We are not so clear on the different commitments that are associated with MRI project. Gilles suggests everyone has a look to the related documentation, and we'll discuss this point again next week.
- https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html
- OpenDaylight distribution, integrating TransportPCE has been released on the 11th of November in the Si SR3.
- Gilles proposed a change in the doc project to update the release note from the Jira tickets associated with Si branch.
- Gilles is not sure that the parallelization of test is effective on stable/silicon branch. According to a mail from Guillaume, we may have to update Releng to make this effective. Gilles will discuss this with Guillaume.
P SR1: Gilles has backported some change from the master branch to P. However, waiting for the unlock of our stable/phosphorus branch before merging all associated changes.
- According to the ODL schedule (Phosphorus SR1 Release Checklist), the branch shall be unlocked tomorrow. Christophe propose to handle P release. (Official distribution with tpce due on the 22^nd of November)
An issue was raised by Shanth about the NETCONF connection between TransportPCE and their Cisco equipment. Guillaume shall provide an answer.

Code Review

Since our last meeting, almost 20 changes have been merged (T-API related, Tox/functional tests related, SONAR portMapping issues, as well as some changes from the OTN suite).
Change 97868 (Fix null Supported CEP Qual. on TAPI node creation) was merged while one comment from Guillaume had not been addressed. It was decided to open a new Jira Ticket to track the comment which could be long to manage.
Change 98531 (Bump netconf dependency to 2.0.9) could be merged.
Status on the OTN switch series:
- Guillaume already merged 3 of the changes. Gilles has reworked all changes considering the comments made by Guillaume and Christophe.
- Apart from ”New functional test with intermediate otn switch” for which a test needs to be renamed from 12 to 14, the other changes can be merged as they are.
T-API change suite:
- Gilles and Christophe started to test « Update TAPI connectivity service on port Change ».
- Javier will send his postman collection associated with T-API so that Christophe and Gilles can test it.
- In the update of the connectivity-services when a state changes, all services supported by the out of service connectivity service shall be updated. We agree on this expected behavior but it seems that right now, when a photonic layer service is out of service, the upper layer services’ state is not refreshed. Javier will check this.
In “Migrate portmapping functional test to RFC8040”, Guillaume changed the url for tox tests. Gilles would prefer to wait until he has merged some of the changes of the OTN suite, prior to merge this one to limit the amount of work.
Change 98001 (Reactive renderer UT): Gilles would prefer waiting that all series on otn switch would be merged before rebasing this change, to minimize conflits to manage.
Change 97599 (Model 7.1 changes to support regenerator capabilities): Bala needs to elaborate the Jira Ticket before we discuss if something more needs to be made.

Q&A

We could not demonstrate 2x200G in Supercomputing (no available product at the time of the demonstration). A video was displayed.
OFC 2022 demonstration : Bala discussed with Andrea. Regen support on devices might shift from January which was first availability to a later date. 3x100G might be supported by some equipment at the time of OFC demonstration. UTD has still in mind to demonstrate path computation relying on GNPy
DDF will be beginning of January (https://wiki.lfnetworking.org/pages/viewpage.action?pageId=53609047). Subject to be presented must be submitted before the 3^rd of December. Any proposal is welcome.

11/11/2021

November 11 being a public holiday in France, this TransportPCE public meeting is cancelled.

10/28/2021

General information

ODL Phosphorus Release: Guillaume, as the TSC chair, made a quote for the marketing message. TransportPCE is mentioned.
Our Jenkins/Gerrit and JIRA may be unvailable next week due to maintenance operations. Beware, since we must release Si SR3.
Si SR3: The release date is planned for the 4th of November. The release of Kernel project is planned next Monday. Then the release of self-managed project is planned for the 4th of November. Our stable branch shall be unlocked on Monday. The time slot we have is between the 1st and the 4th of November. Shweta shall cherry-pick today the changes on stable Si branch. She identified 20+ changes to be backported. TransportPCE Project version need to up increased: for Si SR3, it shall be 3.3.0-snapshot (Phosphorus is 4 and S is 5).
Gilles, Christophe and Guillaume being on PTO next week, Shweta will take care of releasing TransportPCE for Si SR3.
P SR1 is planned for the 22^nd of November. Gilles suggest that we regularly (every weeks) backport changes done on master branch to P. Gilles already made this. Currently, most of changes are failing due to a bad project version in one change related to swagger feature.
Orange made a demo of HoneyNode to UTD. UTD proposes to make some development around PM generation in order to have an optical node emulator a litle bit more dynamic.

Code Review

“Initial OR T-API mapping : topology” is not a new change merged this week, but supports some ongoing discussions on the way to compute the SIP UUID. At the end we decided to follow Javiers approach on the SIP naming convention
“Refactor KAraf builds for test and tox.Ini” and “Remove upstream dependencies version ordering” have been merged
Extend T-API feature Documentation needs to be rebased on top of master. Then it can be merged
Update developer guide for Si and P changes : Olivier will add a comment on the creation of ODUC-4 (comparison with OTUC-4)
Fix bug in OLM spanloss computation needs to be reviewed before being merged. Christophe proposed to review it.
Reactive renderer UT : creates a lot of merge conflict. Gilles will work on it after he addresses the OTN serie. It will be put above the otn serie.
T-API changes chain : all the changes below the T-API functional test, apart from the Junit tests change, solve bugs. They are ready to be merged. All the changes above need to be reviewed. Javier is ready to demonstrate their behavior during next meeting. Christophe mentions that we may need to do some refactoring to avoid code duplication. This could be made in parallel to code reviews.
Another change is not in this relation : “Fix rule format for service interface Point”. It has been dissociated to simplify its merge.
OTN switch changes chain : Gilles will move to the bottom the changes associated with bug solving to reduce the relation chain and simplify its merge.

Q&A

Gilles confirms that ODUC4 and OTUC4 could be created at the same time. We did not identify use cases where OTUC4 and ODUC4 could have different end points. If TransportPCE had to be modified, it would not be so trivial

Cisco models issue : Phosphorus bump brings an issue in the way some the tailf-ncs-plan@2019-11-28 yang model is imported (associated with a YangTool issues)

09/30/2021

Code Review

_Refactoring of the port Mapping relation chain has been merged. This includes “Add a portMapping Util class”, “Fix most PortMapping Sonar Issues”, Use constant for PortMapping log messages step1/2/3
_Guillaume is still working on other changes to reduce the cyclomatic complexity (PortMapping Refactoring changes)
_Christophe worked on B100G E2E functional test that Guillaume considers as ready to merge
_“Model 7.1 change to support regenerator capability” : deviation to model does not work. Another possibility would be to make an extension to the OR yang models, but Bala did not have the time to test it.
Gilles as created a Jira Ticket about the fact we have lost the swagger interface with transport PCE which is needed to use notably the API doc. Guillaume mentions that it use a lot of ports and might not be needed on every node in case of a deployment. AT&T confirms this is useful for them

09/23/2021

General information

Phosphorus is coming soon despite a few failures with BGPCEP project.

Code Review

7.1 models does not support the regen identity. OR community did not want to create a minor release just for this. It was agreed with the vendors to manually add this identity in 7.1 models (org-openroadm-port-types), to support regen feature.
If we don’t add this identity on the controller side, the controller will fail accessing the transponders.
Guillaume suggests we use deviation to add the needed enum, but we may generate some java object that is not exactly structured as the object resulting from manual add in the device models made by OEMs. Bala will try this approach.

For what concerns change 97600 rather than changing the models, removing the deprecated enumerations, we could probably use tox to patch the models and remove the deprecated identities.

Guillaume started working on “switch functional test to RFC 8040 url”. He investigated on solving portMapping SONAR issues (“Add a PortMapingUtil class”; “Fix most PortMapping issues”)
“Use constants for PortMapping log Message” (step1 & step2) also fix a few SONAR messages and bring some consistency in the way LOG message are handled.

Christophe worked on “Code consolidation for end to end B100G services” which addresses 400G transponder and 100G:400G muxponder use cases.
He has also provided on a test suite using 7.1 transponder versions and 2.2.1 ROADM versions : “B100G end to end functional tests”.

09/16/2021

General information

Phosphorus code freeze will come soon (still one issue in BGPCEP).
Guillaume proposes that we envisage rolling to take on PTL role and ask for potential candidatures

Code Review

_Gilles merged almost all the change associated with P migration
_Notification stream selection update is ready to go, now that conflict have been solved.
_Peter has pushed some code that shall be rebased on “Improve container support in tox.ini” which solves some docker issues
_“Fix portmapping sonar issues” has been pushed by Guillaume as WIP . He will address cyclomatic issues in a different change.

09/09/2021

Bala had a discussion with Andrea and Janeth. They want to go for Supercomputing (End of November).
The base of the demo will be the same as the one presented in OFC 2021 with potentially new equipment (400G, 2x100G over a 200G, Regen).
We could probably focus on intermediate rate provisioning and on path computation for high rate relying on GNPy for the demo of both Supercomputing & OFC 2022

ODL marketing team (contacts Casey Cain Brandon Wick ) is also looking for demo to market : we could talk of the OFC demo (some elements have been publically released by UTD)
Some expectations also about 5G. OpenROADM is supposed to be a good candidate for 5G WDM backbones but this plan was not yet realized or tested yet.

http://www.gazettabyte.com/home/2018/3/28/will-white-boxes-predominate-in-telecom-networks.html
https://www.infinera.com/wp-content/uploads/HR-Operator-Strategies-for-5G-Transport-July-2020_WP.pdf

Code Review

Power control support for 87.5 Ghz Spectrum width : we need to clarify the constant we use (and probably adjust their names to make it more comprehensible) when we compare them with input.getwidth to make some decision and calculate the power for Flexgrid operation.
Fix OLM timer for ROADM crossconnect power setup can be merged
Guillaume has started refactoring the code of the OLM because it was raising a lot of Spotbugs issues and warnings (Refactor OLM PowerMgmtImpl class)
Thierry refactored NBI notifications and serviceHandlerImpl to address some comments and correct some issues. He has also updated the docs on NBINotifications
Notification Stream selection update : Shweta updated NetConfTopologyListener to read notification steams (OpenROADM or Netconf) supported by device and adjust the subscription accordingly.

07/08/2021

General information

Guillaume will be on vacation during 3 weeks. Christophe and Gilles will take their vacation in August.
Next week meeting is cancelled.
Phosphorus kernel project are almost ready, so that we could bump the dependencies. The code freeze which was planned beginning of August will be slightly delayed.
Si SR2 will also come at the beginning of August but shall be delayed.

General information

Next week will be the developer forum happening at the same time as OFC.
Si SR1 shall be approved today. We shall be ready by next Thursday.
Next week meeting will be canceled so that everybody can assist/participate to OFC and the LFN developer forum.

Code Review

Notification support for 7.1 device will allow to capture alarms for 7.1 devices. The change pushed on Master includes changes from Gilles.
Shweta pushed another change for switching-pool mapping update from notifications sent by equipment which solves a locking issue with the equipment that we had in previous version of the code.
Guillaume proposes to merge the changes as well as the one on Power control for 87.5 Ghz channels.

Guillaume merged portmapping functional test on master and cherry picked them on the Si branch
Bala will try to move Port mapping change to support Muxponder capability for B100G to the bottom of relation chain
Add missing if cap type for B100G could be merged.
We won’t have time to integrate Port Mapping change to support muxponders capability for B100G on Si SR1
Christophe pushed the functional test associated with the latest modifications brought in the PCE to handle OTUC4, ODUC4, and 100GE supported on ODUCN

The change “Reduce the number of service notifications sent” pushed by Thierry answers a request raised in the context of the MDONS use case to avoid the generation of unnecessary intermediate notifications.

Guillaume is currently working on automation to remove unneeded trailing spaces and tabs.

Gilles mentions we would have an interest in parallelizing tox jobs.
Guillaume agrees but mentions that we will have an issue as this can probably not be done right now with Jenkins Releng which relies on a project that is maintained by the LFN.
This means we would need to do this outside Jenkins Releng and need to manage the updates and maintain it ourselves.
Some solutions relying on python may be used but they are based on detox which is now obsolete.

Gilles can proceed with releasing tpce in Si SR1 as it is.

05/27/2021

05/27/21 is rescheduled at 2pm Paris Time to avoid overlap with OpenROADM meetings

General information

Silicon SR1 is in good shape.
Developer forum from the 7 to the 10Th of June is open to registration (free registration). Most sessions on ODL are planned on Tuesday with also some on ONAP. Unfortunately it is at the same time as OFC.

Code Review

Guillaume rebased OTN topology on top of the fix he provided.
The dependencies for Si SR1 have been bump. We should now use these ones (odl parent 8.1.2, Netconf 1.13.2, mdsal 7.07…).
Guillaume has pushed a change related to this (Bump dependencies to newer Silicon dev versions).
This change and the change “Fix new checkstyle issues found by odlparent 8.1.2“ shall be cherry-picked and merged on top of the relation chain for Si SR1 .
The change of Bala made on stable Si will also need to be rebased after this has been done.

“Add missing if-cap-type for B100G” : has been modified to consider the latest modifications made on other changes
“Device renderer for Muxponder” : fixes a bug that was noticed during testing with lab equipment.
“Distinguish flex vs fixed for PCE 400G” : also fixes a bug associated with central frequency handling.
“Renderer support for higher rate” is adding support for OTUCn and ODUCn support in muxponder to create infrastructure connection type for OTN high rate services.

For Si SR1 we will have a fix for OTN topology and all what is above this patches in the relation chain.
Gilles pushed a change to update the configuration file for Honey node, providing some adds for 400G transponders and muxponders. This includes profiles. The file has been reorganized

05/20/2021

General information

Si SR1 branch is locked. Al SR4 should be coming by 2 or 3 weeks.
Gilles experience some issues but shall be able to prepare tpce staging for Si.
Committers election : Bala and Christophe have been proposed as committers. They got 100% accepts from expressed votes.The election must be now approved by the TSC.

Code Review

Fix the misplacement of service notifications : Thierry made a change related to service notifications to avoid that notifications for service creation are sent before the service state is updated in the MD-SAL .
Some notifications were added in case the implementation of the service fails.

Guillaume proposed a few commits to fix some remaining build warnings and optimize gates logs and behavior:

Use maven batch and quiet modes inside tox :
Mute snapshots download status :
Fix mockito initMocks deprecation warnings :
Fix Javadocs warning in common PortMapping :
Ignore JsonString converter…
Fix lighty build warnings :
……
Mute lighty reflective access warning :
Fix deprecated warnings caused by Yangtools update :

OTN-topology creation fix : in this change Shweta moved ifCaptype conversion method for different version of devices in Portmapping. This change is dedicated to Silicon. Change-ids must be changed among the different branches. The change for silicon is ready (Gilles adjusted the commit message) and can be cherry picked to master
OTN topology creation fix shall be abandoned (change id not correct since it is already present on Si branch)
Notification support for 7.1 devices (95985): this change is dedicated to master.

Christophe put 2 changes on top of a serie but forgot to rebase one of the changes on master. He will correct it and push all the relation chain.
Gilles has his change with the configuration files for Xponders modifying xponders A2 and C2 ready, but is waiting for this relation chain to be cleaned up before to push it; between Device Renderer for muxponder and PortMapping functional test for B100G muxponder.
This could be however pushed in another non optimal way if this induces too much delay.

Renderer interface delete for B100G TPDR change is needed for OFC demonstration.
Shweta pushed some changes to solve a number of issues with the PCE. One fix the issue about the fact that PCE doesn’t find SRG for unidirectional configurations. The other solves the fact that PCE picks the wrong a and z end termination points (first available tp even if not connected)
Bala is currently working on the Renderer for 7.1 devices, but did not succeed in solving the issue where the Renderer fails finding list of supporting interfaces. He may need help to understand this behavior observed with HoneyNode.

05/13/2021

Code Review

Add NBI notification feature documentation : the documentation has been completed.
Depending on the order the test were scheduled and if we were using lighty, some test returned either 201 or 200 code. Guillaume has provided a change to solve this.
Lighty is now supported on the SI branch
Bump deps to new Si dev version, may solve some issues uncounterd by AT&T. AT&T did not have the time to test it.
Shweta provided a change that solve some issues associated with Netconf operations translation (put->replace) on some vendor’s devices through “Update device transaction operations” change. Provided change allows solving this issue for power setting (OLM), connection setting and interface creation (Renderer) on all the devices AT&T currently has in their labs
A bug in OLM ServicePower Turndown (TRNSPRTPCE439) has been raised by Gilles, but Shweta explained that the issue raised in fact corresponds to standard operation.
In “Notification support for 7.1 devices” a listener is created for notification that allows to update the mapping when a switching pool has been created on a device. This change was developed on stable Si, but the code has changed since Gilles refactored this part of the code on master branch. Gilles propose to backport part of the code he has refactored (2 changes) to Silicon, and Shweta proposed to rebase her code on this. After that we will cherry-pick the change of Shweta on master branch.
Javier has been handling the comments provided through the different reviews on his code.

“Port mapping functional test for 7.1 device” change pushed by Bala is changing version naming in the different classes (7.1 -> 7.1.0). It is also modified in the xml config file, which leads to an issue in HoneyNode because the enum is not supported in the OpenROADM models. Port capabilities were also adjusted for network port changing if-cap type from if OTUCn-ODUCn to if-otsigroup. Guillaume proposes to split the change into 2, one focusing on 7.1.0 adjustments and the other handling all other adjustments.

04/15/2021

General information

Silicon is officially published and is available on the official download page.

Code Review

Guillaume has merged several changes : “Increase sims startup timeout in functional tests”, “Improve docs/conf.py” and some Gilles contribution on changes in portmapping : “Handle notification reception on port state change” as well as “Refactor (un)registration of device listeners” and “Update portmapping on port state notification”

Last changes from Javier were discussed (“T-API common service RPC implementation”, “TAPI connectivity service rpcs Impl”, “TAPI Netconf topology listener”)

Gilles has pushed different changes associated with Honeynode and functional test to check port status update in portMapping and topology:
_Adapt existing Honeynode config to device 7.1 : includes different configuration files compatible with 7.1 OR models (ROADM, transponders and muxponders at that time)
_Upgrade Honeynode sim for device 1.2.1 and 7.1 allows to have the same behavior as for device 1.2.1 for port state notification
_Change way to start simulators is a refactoring of the code that will allow working with hybrid configuration (several config simulationg devices of different releases)
_New functional test for device change notification : these new test suite includes different equipment release and allows setting a 100GE service. The change of state on device ports _triggering port mapping changes and topology updates is checked.
_Refactor (un)registration of device listener allows to solve a scalability issue with device listener instantiation and simplifies the topologyListener class.

Guillaume pushed a change that modifies the script to install Honeynode, to improve the Gate behavior.
Thierry has provided the doc section that concerns nbi-notification module in developer and user guides

04/08/2021

General information

Silicon release is officially published.
Netconf is now MRI, meaning the project won’t use anymore snapshot which will make our life easier to manage dependency.
Guillaume mentions we could in this context, propose to be handled as a managed project for Phosphorus.
Anyway, this does not change the situation about our lack of committers and the way we are staffed. Being handled as a managed project brings a lot of constraints.
The developer forum is planned around the 10th of June and it will be a virtual event.

Code Review

Code review

Javier contributions have been merged this morning.
Flexgrid has also been merged on Master branch.
Resource deletion issue in OpenROADM topology : following the creation and the deletion of a service, the resources were not correctly released.
The bug has been fixed by Gilles.
Shweta is currently working on functional tests on OLM. She is experiencing some issues while trying to access specific PMs using filters.

01/14/2021

General information

Current master branch now based on Si works back again.

AL SR2 Is in good shape, it shall be ready by Monday.
DDF forum is scheduled from the 1st to the 4th of February. Registration is free but needed in case of submission. Submission are due tomorrow.

Code review

Javier exposed what he plans to work on in the coming weeks. This includes some extension of T-API module to support the topology, the connectivity and the notification service. Javier wants to store the T-API context in the MD-SAL.

Emmanuelle has rebased Flexgrid contribution on the master branch.
Javier thinks he has solved all the comment made on his patches.
Emmanuelle has started integrating Thierry’s code on notifications. She worked on NBI notification module. This module is now available as an optional module so that we do not have any issue when no Kafka container is available. She also modified Lighty to activate or not the notification module addressing the same issue.

Emmanuelle presented a summary of the work she did on Flexgrid.

01/07/2021

General information

Current master branch now based on Si is broken.
We are experiencing a compilation issue with newest YangTools. MDSAL-651 - Getting issue details... STATUS

We expect a new delay on Al SR2 releasing (initially planned next Monday).

Code review

All the changes associated with Flexgrid have been merged on stable Al branch and will be included in Al SR2.

Emmanuelle will cherry pick these changes on Silicon as soon as the yang tools bug has been solved.
Gilles confirms we are ready for Al SR2.

Javier has addressed almost all the comment on its changes. He is currently working on the T-API module.
It seems important to store the T-API topology in the MDSAL since Javier will enrich our NorthBound T-API implementation.
There is no objection to do so. This will allow to have a T-API topology stored in the controller directly in the MDSAL rather than in Mongo DB that is not supported in ODL.

Thierry pushed a change concerning the addition of a new maven module to handle notification. The second change is about the implementation of the Kafka notification publishing service.

Last change is concerning the functional tests associated with this new functionality (Kafka notification publishing)

12/17/2020

11/26/2020

General information

Mg SR3 branch is still not locked (fixing infra issues).

Code review

Bala’s changes on PortMapping and 7.1 models have been reviewed by Guillaume and Gilles.
Only “bug fixes in Portmapping 7.1.0” last patchset still needs to be reviewed. Guillaume suggests that Gilles merges the relation chain.
Align and improve portmapping versions Step2 is ready for review.
Reformat api Yang models with pyang has been reviewed. It could also be merged (after Portmapping).

Javier presented Nokia’s latest works.

Honeycomb modifications on 1.2.1 have been pushed to Gitlab.
Changes associated with Netconf notifications handling have been pushed on Gerrit (Step1 to 8).
A thread is created for each notification to avoid bug identified as TRNSPRTPCE-249. Step1 to 6 were introduced during last meeting.
Step7: When a service notification is received by the Service Handler, this last compares the elements of the topology and their states with the elements included in the different path-descriptions of service-path-list.
The state of the services affected by these state changes are refreshed by the SH.
Step8 : Honeynode 1.2.1 simulator has been modified to include the implementation of Circuit Packs notifications in DeviceNotificationProducer and the implementation of CP update datastore in DeviceChange listener.

11/19/2020

General information

We are part of Al SR1, though it seems the marketing annoucement are not more brodcasted on the mailing-lists.

Mg SR3 : Managed project have still some CIST issues, so we will experience some delay in the code freeze.
The cherrypick have been done, but we will need to stage Mg SR3 when ODL Release allows to do do.

Code review

PortMapping for 7.1 : A couple of comments have been made on the different changes. AT&T has been testing the code on transponders and 400G muxponders.
At that time only transponders are supported with the current code. It seems that managing muxp-profile (in device model) will take time.
And network model may suffer from limitations that will not ease the management of 400G muxponders.
The proposal is that Gilles or Guillaume address the comments made on Bala changes. Bala will send his presentation on suggestions for adaptation of the Portmapping.
We will then dig into the models and handle the muxponder case at a later step after we make sure everybody is in line with the way to do it.

Nokia / Javier has provided several changes associated with its initial contribution.The changes are WIP and no review is expected yet.

Step1 focuses on the implementation on the device listener to process notifications from Netconf devices. Every time a new notification is sent a new thread is open.
Step 2 focuses on adding the operational and administrative state to topological elements.
Step 3 is focusing on upgrading the states according to the received notifications.
Step 4 is adding a basic model to provide an interface between the topology manager and the service-handler.
Step 5 : when a netconf device generates a notification, this trigs a modification in the topology which is sent to the service handler
Step6: the test of the port status is introduced in the PCE.

Guillaume added pyang tox profile to check/format api models and the documentation spelling.

11/12/2020

General information

Gilles proceed to release of Al SR1 last week.
Mg SR3 : Code freeze for Managed project will start on the 16^th of November.

Code review

Gilles presented the approach that what used to consolidate the T-API topology export.

Two levels of topology can now be provided : “T0 Multi-layer Topology” provides a global abstraction of otn-network and WDM topology. Only the units that are physically connected to the WDM infrastructure through X-ponder to ROADM link are represented in the topology. “Transponder 100GE” provides a second level of abstraction where only transponders of the WDM layer are represented. The full WDM domain (providing any to any connectivity) is represented as a single node with Node Edge Port that correspond to the client port of the transponders.

Fix a bug in PortMapping : in some devices in the lab the xponder-subtree does not give all details for the connection map (lately inserted pluggable not reported) making PortMapping failing.
Bala solved this, reinitializing the logical connection point for which details are missing.

Emmanuelle has aligned the topology on 7.1 openROADM models (Common, Device, Network models). She split the changes to ease review, meaning a lot of them do not pass the gate.

11/5/2020

General information

Managed project are ready for Al SR1 since today. Gilles is going to prepare the staging of the release.
The latest work done on T-API will not be integrated in Al SR1 since it is still in review.
The TSC election process has been postponed to the end of November (but self-nominations coming soon).

Code review

Lighty support in Al : Lighty now works with Al (add annotation dependency, increased memory allocated to make it run, PathComputation service Impl was using BindingDOM codec service from karaf which has been changed to AdaptorContext serializer)
Now that lighty is activated for the test, TPCEUtils also needs to be updated if we change models.
Using Lighty on Al, we will rely on a stable version. But for Silicon, Lighty needs to be uploaded from maven central, and it is not currently available. This is the reason of the change “Lighty support Silicon migration”
Portmapping for 7.1.0 models : Bala changed the portmapping to enable 7.1 models. Supported interface capability implementation has changed. Interface capabilities are now more port childs but are now handled as an augmentation and mc-capbilities are now handle through profiles.
Emmanuelle mentions that she will wait for the portmapping to be merged so that she can rebase her Topology change (common models need to be changed for both) .
7.1 Honeynode simulators can be downloaded from
https://gitlab.com/Orange-OpenSource/lfn/odl/honeynode-simulator/-/tags/honeynode-plugin-aggregator-7.0.0
Bump to silicon : Guillaume split the change done by Emmanuelle since he wanted to reuse some of the code changes in AL
T-API : Gilles made a change to strengthen independence between UT in OLM (not strictly related to T-API). A second change allows sharing a common Datastore context for all unitary test in T-API (Static class). The 3 following changes are dedicated to the consolidation of T-API topology. Only ports and node that are attached to the ROADM are considered. Second step allows to build a multilayer topology that includes both transponders and OTN devices. Step3 allows building the same abstraction as we were building in the initial development (only transponders and WDM layer). Last change includes the tests associated with T-API.

10/29/2020

General information

Aluminium SR1 deadline is tomorrow for managed project.The branch has been locked this week.
It will be unlocked when managed project will be ready which will allow us to migrate.
There were a couple of evolutions on dependencies, which have been considered but can’t be merged in the current state.

Code review

A few Jsr305 useless dependencies have been removed from poms.

Sodium SR4 coming soon but what to put into it ? most of Mg work is focused on OTN and Na does not have this feature

Alumium branch locked since 08/03.

Code review

Gilles did most of the premilmary work to bump to Alumium but it is not yet completed.
This was a huge change, Onoging work to split it.
Aluminium does not buit with jdk 11.0.4. The version used must be at least 11.0.6
Among other things, the API change impacts yangtools generated lists.
The type used is now Map instead of List.

Some bugs found on real equipment with Mg SR2. JIRA tickets to come.

Flex grid stll on work, especially functests that needed an update on honeynode (now merged)

07/30/2020

General information

Magnesium SR2 : there are still some issues with some of the Managed project artifacts.

It shall be solved this week, and self managed project shall have one week to release after this has been solved.

The current estimated date to release Magnesium SR2 is of next week. Daniel de La Rosa will send a mail to Shweta as soon tpce can be released.

Code review

All changes related to Mg SR2 have been merged .
Orange started working on the migration towards Aluminum, which introduces an API disruption, and changes in the DataStore context. This will be the priority for Orange, coming back from vacation since the migration will imply a lot of work.

Javier is back from vacation. Il we will work on rebasing and splitting changes provided by Nokia but also needs to focus on his master study report.

AT&T is experiencing issues with the Portmapping update in some cases after a configuration has been performed on Xponders. AT&T suggested to create an rpc targeting devices that triggers portmapping updates for debugging purposes.

Some issues in developing the test suite for the flex-grid capability. This requires the device to advertise mc-capabilities for degree/SRG in the operational data. A new operational data file (oper-ROADMD.xml), where these capabilities were added has been created. However, mounting the device using the honeynode-simulator, only the operational data appear.

07/23/2020

General information

06/18/2020

General information

ONES virtual event planned next week.
Orange proposed 1 session for TPCE, 1 for BGPCEP and one about LFN infra migrations and ODL scheules synchronization.

Ongoing talks to propose a Na SR4 release update

Code review

Shweta and Susmitha started to prepare the Flex Grid migration.
Power control for flexgrid submitted by Shweta has been merged.

Some troubles with running functional tests on MAC OS
=> ongoing fixes and update of the honeynode zip files
=> Also ongoing refactoring of Functional tests

UUID stabilization on TAPI topo merged

Many update from Orange Labs Egypt and Gi

lles on Junit tests => They started to work on the common modules

Jonas bug fix / improvements merged

Ongoing huge work on the SH-renderer API update

Some bug fixes on the OTN nodes

06/11/2020

General information

There won’t be any ONES EU event. It will be replaced by the virtual ONES NA event in September.

LFN is still in the process of releasing Na SR3. We are ready to be part of it

Code review

Dependencies have been bumped to Mg SR2 on the master branch.

Thanh made a contribution to remove a dependency that what preventing ….. some jobs/features to be updated. Sonar ?
Parallelly, there was a discussion to update the image for functionald from 8c 8G to 4c 16G. => cheaper with more RAM !

OLE made several Junit test contributions. This allowed improving significantly the coverage in tpce to 40%. They will focus on the common module in the coming weeks.

Gilles started working on Junit test for network model. Change 90244 has been merged. It does not cover OTN topology which is covered in another change 90372 for which the review is ongoing.

Jonas proposed 2 changes, one to improve the way we handle spanloss, and the other to fix an OTN PCE bug.

Emmanuelle pushed 2 changes on Lighty.io.
In the first, one missing yang model registration has been solved. The pom has also been updated. Now the tapi API can be used with lighty.
In Lighty refactoring (90379), she cleaned up some dependencies that were not used, add checkstyle from ODL parent and fix checkstyle violations.

Some functional test have been added for t-api.With lighty.io, it is loaded by default contrary to Karaf.
It appears taht some misconfigaration in bundle/feature tapi configuration prevented it from being loaded correctly by default in the ODL distribution => fixed

Gilles fixed a bug in the PCE OTN node that was introduced when solving spotbugs issues.

Run autopep8 on functional tests…..

Honeynode has been updated to support the interleave capability.

Catch portmapping failure is solving some issues with some of the new OTN switch equipment AT&T has on its platform. PortMapping was failing because there are some mandatory parameters missing in the equipment configuration.

SH-Renderer-API: Bala will start looking to Olivier’s comments beginning next week. Guillaume proposes to rebase this change on the current master.

06/04/2020

General information

Artifacts for Na SR3 have been published.

Orange has proposed a discussion on tpce Mg Release at Next DDF Forum (virtual Event)

Code review

Ahmed completed some functional test to check the behavior of the PCE in different conditions related to the presence or absence of OMS attributes.
The test notably checks that the PCE does not propose path relying on some links that do not contains OMS attributes.

SH-Renderer API code to handle OTN : the code is almost ready. Before Bala starts working on functional tests, Olivier will make a functional review of the code.

Fix tapi execution : Emmanuelle fixed a null pointer exception and adapted the Junit tests.

Emmanuelle has refactored some functional tests. Guillaume would like AT&T to check and give the confirmation that the behavior is still correct in a MacOS environment

NETCONF-666 bug has been corrected and merged on Mg. It may solve the issue we observed with NETCONF notifications generated by devices in case of multiple Netconf sessions.

05/28/2020

General information

We are officially part of Mg SR1. It will be announce today or tomorrow.
Deadline for managed project for Na SR3 is tomorrow. We are ready for integration in this release, but Netconf artifact is still missing, so that we cannot stage the release.
Wiki URL has again changed from wiki.lfn… to wiki.opendaylight.org, which brings a lot of issues. Guillaume sent a mail to highlight this.
Ongoing discussion on the virtual ONS summit.

The stable Mg branch is locked. So there will not be any additional change backported to it.

Code review

OLE made some contributions on the PCE to adapt the code in the following of the Junit test they made.
Emmanuelle as developed a GNPY stub to help OLE in developing/running the Junit tests for the PCE.
Bala made a change (WIP) on the service Handler. He added otn-service-path method in SH model-mapping and updated renderer to differentiate WDM and OTN service.
The service-path was also updated with connection type.

OLE has added some Junit Tests for the PCE, increasing the overall coverage.
They also provide the Orange Gitlab LFN-dedicated space with the documentation for the GUI.
Gilles has pushed the “bump project version to magnesium SR1” on the stable magnesium branch.
Mg SR1 is planned for the^4th of May (Managed project). We will have then one week to perform the staging.
The change on SAPI/DAPI shall be adapted (creation of SAPI/DAPI based on a HashMap of 16 Bytes, with preferably the ability to retrieve the original string from the hashmap).
The Change has been rebased (new dependencies) and put as work in progress.
OpenROADM service model 6.1 has been also rebased on new dependencies. The problem is that it modifies the service handler and does not allow to pass the end to end tests.
AT&T will analyze the log and reason for the failure of the functional tests.

Gilles pushed 2 changes to handle topology after an OTN service has been created and to align the Renderer operation with the PCE. This allows notably to update the topology with OTU4, ODTU4 (Structured ODU4) links, used and available bandwidth. ODU0, ODU2e and ODU4 services can be provisioned through otn-service-path and supporting OTU4/Och through service-path rpc.

04/9/2020

General Information

TSC would like to have a transportPCE presentation during a TWS meeting. AT&T is ready to support this.
Proposal to make it next Monday, but this can probably be planned at a later date which better fit with our constraints.
Martin raised the question on whether we shall try to push transportPCE for being a Managed Project.
The lack of effective committers would make it difficult at this date.
Martin suggested to discuss with the TSC this at the end of the presentation (mentioning current elements that may need to be solved).

The LFN has decided to migrate the mailing list. We shall receive of invitation to subscribe to the new mailing list.
For Aluminium we have to think about the old Controller API removal.
This may have an impact, on the code, but most the work was already done on the databroker migration from September for Sodium.
The Wiki shall be migrated before beginning of May.

Code review

“Update config files and tests” has been merged. It improves the testing environment for GNPY, modifying the config files.
“Improve HoneyNode Docker script” has been merged. The script to initiate the simulators has been changed.
“update lighty.io build script for Mg SR0 support”: Balla made some modifications updating dependencies and was able to build the lighty locally.

Narayan has started working on the support of 2.2.1 Devices in the inventory. He has an issue with the database management.
“Upgrade OpenROADM service model to 6.1” : Susmitha has removed old 5.1 service Model.
She suggests to keep old models in common, because a lot of modules are still using them.

03/26/2020

General information

A release note and a marketing announcement have been prepared. All self-managed projects (including transportPCE) will be in the official distribution.
GUI source code has been published on Orange public Gitlab, the docs have not been published but exist in Microsoft Word docx format, they must be converted in MarkDown.

Code review

“HoneyNode and tox scripts BSD compatible” has been merged : the idea was to rewrite tox scripts and the launcher so that they are BSD compatible and can be used on Mac.

“Calculate Spanloss crashes when OTS is not present” : Susmitha add a check on whether the OTS interface is present or not.

We manage to release tpce for Na SR2.

Magnesium code freeze should have been on Monday the 10^th of February. Bus as BGPCEP project is not ready, Mg shall be stable only on next Monday.
Guillaume has bumped the dependency and also migrated tox to use controller with JDK 11 and sims with JDK 8(not merged at that time).
Currently the project is building with JDK 8 and 11 with Sodium. JDK 11 is mandatory for Mg.

Maven verified job needs to be migrated to JDK 11 (currently building on JK8). So this should not affect the current code.
A patch has been proposed to releng/builder to migrate. It has been merged during the meeting. So the gate is now using JDK11.

Code review

When AT&T is pushing code, the building process fails. LFN doc tools needs Python 3.6 . ATT changes need to be rebased on the current master to use the new version of tox.ini
PCE consolidation (according to Jonas comment, and OSNR calculation improvement) has been merged.
The PCE OTN initial code has been reworked through “Adapt PCE code for OTN services” commit which has been merged.

OTN renderer code and PCE code have been put on top of Upgrade to service-path1.7
OTN renderer code was initialy rebased on service path 1.7 before it was cleaned-up leading now to a merge conflict. The way to solve this has been identified during the meeting.

Guillaume is currently trying to rebase the Magnesium dependencies on top of the master branch.
There are some changes in the yang tools : they have changed the implementation of yang list leading to the impossibility of sorting correctly these list.
This breaks the functional tests.

AT&T has started working on service and network models 6.1 integration. There are some issues , probably coming from common models.
Bala has also started working on including SAPI and DAPI field on interface Builders (OTU4 creation) in the renderer but functional test fails (at the Topology level)
AT&T identified an issue with ODL parsing device responses to Netconf config edit. They need to investigate a bit further to understand whether the issue comes from ODL (NETCONF) or from the equipment.

02/06/2020

General information

The next DDF won’t be collocated with the ONS. It will be associated with the ONAP event in Seoul.

Magnesium code freeze for Managed project is beginning next week. This means that the API won’t change.

Code review

Guillaume fixed the problems with tox profiles and the gate works again.

Ahmed managed to finish his work on GNPY and addressed most of Jonas comments on the PCE. The problem of identifier for fiber and EDFA has been fixed.
The only remaining point of discussion concerns the Belmann Ford algorithm and latency management, but Jonas agreed for the merge.

Shweta has addressed all the comments made from a functional view on the renderer which was also realigned to the service-path 1.7.
AT&T has started working on the upgrade to Service and Network models 6.1.

Christophe and Gilles pushed the new version of the PCE. They have reviewed all the code and have updated it to perform the path calculation for OTN service (OTU4 from network to network ports on OpenROADM topology, ODU4 from network to network ports on otn-topology relying on an OTU4 link, and 10GE/ODU2 & 1GE/ODU0 from client to client ports relying on an ODU4 link. They had to change the structure to introduce a new interface PceNode where generic methods are defined. These last being implemented by PceOpticalNode (previous PceNode) and PceOtnNode.

The part that misses for Magnesium are :

OTU/ODU link population in the topology : Christophe and Gilles will work on their side on method in the topology building to create link in topology. Shweta and Bala will focus on renderer
Service deletion which shall be quite straight-forward

Emmanuelle worked on HoneyNode which can be built and run on Java11. We are currently making tests to validate the solution.

Guillaume managed to make the code build with Magnesium, but still have some issues to solve. The community has introduced spotBugs (similar to SONAR) which raises some errors.

2021 meeting minutes

[data-colorid=c39d4o5jqk]{color:#444444} html[data-color-mode=dark] [data-colorid=c39d4o5jqk]{color:#bbbbbb}[data-colorid=andsakkakh]{color:#444444} html[data-color-mode=dark] [data-colorid=andsakkakh]{color:#bbbbbb}Meetings connection details

12/16/2021

Code Review

Q&A

12/09/2021

General information

Code Review

Q&A

12/02/2021

General information

Code Review

Q&A

11/25/2021

General information

Code Review

Q&A

11/18/2021

General information

Code Review

Q&A

11/11/2021

10/28/2021

General information

Code Review

Q&A

10/21/2021

General information

Code Review

10/14/2021

General information

Code Review

10/7/2021

General information

Code Review

09/30/2021

Code Review

09/23/2021

General information

Code Review

09/16/2021

General information

09/09/2021

Code Review

08/26/2021

General information

Code Review

08/19/2021

General information

Code Review

08/12/2021

General information

Code Review

07/08/2021

General information

Code Review

06/24/2021

General information

Code Review

06/17/2021

General information

Code Review

06/03/2021

General information

Code Review

05/27/2021

General information

Code Review

05/20/2021

General information

Code Review

05/13/2021

General information

05/06/2021

General information

Code Review

04/29/2021

General information

Code Review

04/22/2021

Meetings connection details