...
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).
02/14/2020
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.