Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »


General information

The mailing-lists have been migrated, this includes transportPCE dev list.
The presentation about transport PCE for the Tech work stream (public session) will be on the 27th.
It has been asked by the TSC, and shall be technical. A good starting point could be to reuse the presentation made top OpenROADM user Group.
The gate was broken two days ago, this means the project shall be rebuilt if no Maven cache repo is used.

Coding activity

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.


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 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.


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.

“Setting transponder power level when SRG Rx power range does not exist”   Susmitha made a change to set transponder power level when SRG Rx power range does not exist.

Javier working with Nokia has pushed a change  initiating Device Notification Listener functionality.
They propose to provide contribution that focus on listening to device notifications in order to trigger some network topology updates associated with the state of nodes and tps.

Docker refactoring : HoneyNode Docker refactoring is ongoing.

“Bump project to 2.0.0 and fix feature deployment change” allows bumping Master branch on Aluminum.

Several change have been made to reduce the technical debt and fix different spotbug issues (Separate changes for PCE, Common & Network and Renderer modules).
This changes also allows solving some of the SONAR issues.


General information

There will be a vote today for Magnesium Release, but they are still experiencing issues with some of the projects.
Guillaume did not manage to stage the release because some dependencies are still missing.

Code review

Docker refactoring for Java 11 : Honeynode has been upgraded to Java11. The Docker that launch the simulators needed also to be upgraded.
In the docker file some changes have been made to introduce a hierarchy. Previously as all simulators and configurations were built directly on the image, the dockers used a lot of memory.
Using the Multi-stage feature of Docker, the size of the image went down from 800 to 240 Mbytes.  Also only one image is now used for all configurations. A script starts several container with their own configuration file. An option has been added to check the health of the simulators by using the REST API.

Adding SAPI/DAPI to Renderer function has been completed also removing some warnings that were generated previously and hardcoded lines.

“Update configuration files and tests” change is focusing on correcting the clfi and addresses of the nodes, and managing OMS attributes and other deprecated attributes  that were moved to the common model.


General information

Magnesium release is postponed. A bug in karaf prevent some of the modules to start correctly.
Trying to stage the release, it seems that some NETCONF dependencies are not available so that we can’t stage it.

Code review

Ongoing changes on the master branch:

A change has been provided by Anil related to the documentations (migration to Python 3).
Some Changes can be pushed on Master branch. If a change is OK we can then cherry pick it and propose it for Magnesium.

Gilles is working on some adds to the topology management and the renderer to handle OTN link creation in the topology. This code has not been pushed on the repository.

Bala has been working on checkstyle issues for SAPI/DAPI code and will push it this afternoon.

We are working with Fossology to check the licenses associated with the GUI code. After we have checked licenses are compatible, the GUI code will be pushed on Gitlab.


General information

Magnesium will probably be postponed but we are ready to integrate the release.
We have received some guidelines about the migration of the Wiki (Casey Cain).

Code review

toJava functions introduced by the Magnesium migration do not support null.
The code of GNPy has been changed accordingly (addressing the case where PCE sending a request to GNPy to calculate a path, without sating the wavelength).

The transportPCE features have been reorganized . odltransportpce gathers now all features associated with tpce, ord and api models.
A feature has been added for t-api, as well as an for the inventory. The creation of a t-api bundle was not leading to creation of t-api artifact which breaks karaf.
A change has been proposed to publish the artifact locally, so that they are available to be run in Karaf

The documentations have been reviewed to include OTN support, GNPY, and T-API support (for the export of the topology).
Some example have been provided to explain how to configure OTN devices using intermediate (East/west) APIs, waiting for a full end to end support (planned in later releases of Magnesium).


General information

We manage to release tpce for Na SR2.

Magnesium code freeze should have been on Monday the 10th 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.

  • No labels