Skip to end of metadata
Go to start of metadata

OpenDayLight Magnesium Release: Inputs to Marketing Communications

237LISP Flow MappingLori Jakab

The LISP Flow Mapping project doesn't actively plan any major new features during the Magnesium release, but will keep the code up to date with platform changes and updates, and will review external contributions.

Arunprakash D

Following activities has been done in Openflowplugin for Magnesium release:

  • Cluster stability, scale and perf improvements
  • Bug Fixes
  • Upgrade improvements
  • Documentation improvements

Ajay Lele

Apart from regular sustenance activities, below features were added:

  • Support for missing features from RFC 5440 [PCRequest/PCReply, Topology Graph, TED, Path Computation Algorithms: CSPF, SAMCRA (Self-Adaptive Multiple Constraints Routing Algorithm)]
  • BGP-LS topology provider support for Segment Routing
N/AControllerRobert Varga


Ajay Lele

Apart from regular sustenance activities, below feature was added:

  • Option to batch data while performing import operation, to enable processing of very large data sets.

Karthikeyan Krishnan

  • New Features 
    • There is no new feature is gone in this release from netvirt application.
  • Cluster stability, scale and perf improvements
  • Bug Fixes  (It includes the more bug fixes in ELAN, ACL, NAT, L3VPN, IPv6 modules)
  • Upgrade improvements
246GeniusHema Gopalakrishnan

Following activities are planned for Genius in the Magnesium release:

   New Features:-

  •  BFD support for OF Tunnels
  • CSIT for OF Tunnel BFD


  • OF Tunnel Enhancements
  • Scale and Performance Improvements
  • Bug Fixes

Chetan Arakere

236Integration-DistributionLuis Gomez

During this release we added the ONAP Karaf distribution. This distribution is used by ONAP CCSDK project.
240ServiceUtilsFaseela K

The serviceutils project is not planning any major new feature in Magnesium.

We will be reactive to any bug fixes required by the projects that depend on us.

We will be bumping any required 3rd-party dependencies as well as upstream dependencies.


Balaji Varadaraju

The current list of new features that are being targeted for fixing: - NETCONF southbound requires notifications.yang model to be present on the device

The current list of bugs that are being targeted for fixing: - Race condition causes multiple notification subscriptions (diagnosed)  - Issue while expanding Mount Point in Opendaylight UI (Restconf) it displays 500 Error Code.  - Netconf client fails to detect error reply  - Impossible to subscribe to RESTCONF notification stream due to error -  Netconf can confuse action definitions when they have equal name -  Issue with ChoiceSchema(Mix) Node, NullPointer Exception while creating InstanceIdentifierContext for Choice(Mix Node) type. -  restconf to netconf translation doesn't honor the order of the keys for lists with multiple keys -  No status for rogue device in callhome server API


Venkat Govindarajan

Apart from the bugs and regular maintenance activities, there are the planned improvements for Magnesium


The current list of bugs that are being targeted for fixing


Achuth Maniyedath

Only version bumping activities in progress

No new feature development planned for this release.

Critical bugs to be fixed will be added later

239InfrautilsFaseela K

The infrautils project is not planning any major new feature in Magnesium.

We will be reactive to any bug fixes required by the projects that depend on us.

We will be bumping any required 3rd-party dependencies.

We have no intention of becoming release instead of snapshot integrated in Sodium.

251DetNetQuan Xiong

Magnesium is the first release for detnet project. The detnet project is planning new features in Magnesium as following shown.

Time Syn Feature: Manage time synchronism information , configuration and configure it to DetNet devices by SBI protocol.
Topologe Feature: Manage Manage DetNet bridges information and configuration, also the topology of the DetNet domain.
E2E Feature: Manage Manage flow information and E2E service configuration.
QoS Feature: Manage priority mapping and queue configuration.
PCE Feature: Calculate the optimal path and DetNet related information based on the topology and flow information.
SB Plugin Feature: Push the DetNet configuration to DetNet devices by SBI protocol.


Richard Kosegi

No new features were planed in this release

Allan Clarke

* Output expansion of arrayed data now supports multiple outputs per array index
* Performance improvements

* Support for wildcarding in binding variables to portions of input data

N/1TransportPCEGuillaume Lambert

TransportPCE magnesium release is a major step forward in the control of open optical infrastructure domain since it brings many new features. The most important one is a first experimental support for OTN on top of the already existing OpenROADM WDM support. This release comes with a newer OpenROADM service 5.1 Northbound interface. It is also worthwile to mention a limited support of TAPI version 2.1.2. It is used to expose (through a TAPI compliant Northbound Interface) an abstracted WDM/OTN topology that masks the OpenROADM topology complexity to higher layer controllers/orchestrator.

* OTN experimental support added in Magnesium SR0 for portmapping, topology, renderer and PCE (Service Handler not yet ready)
* Honeynode simulators upgrade to support OTN as well as the migration to Java 11 for functional tests
* Service Path API upgraded to new version 1.7
* OpenROADM service (Northbound API) upgraded to version 5.1.0
* Some Bugs fixes

New Features
* GNPy server connection support. This allows to offload PCE impairment aware  path calculation to a GNPy server, or to validate a path precomputed by transportPCE, including the impacts of non linear effects .
* External database connector experimental support. This connector allows to populate an external (MariaDB) Inventory Database, currently limited to OpenROADM version 1.2.1 devices
* limited support of TAPI version 2.1.2 (Northbound API)

    - TAPI:get-topology-details rpc to abstract nodes from OpenROADM openroadm-topology (WDM and OTN)

OTN XPONDERS in the abstracted T-API topology appear as one node in the DSR/ODU layer (with 1GE/ODU0, 10GE/ODU2e or 100GE/ODU4 Node Edge Points (NEP)), and one node in the photonic-Media layer with a single OMS/OTSI NEP. Both nodes are interconnected through a transitional link. Couples of 100GE Transponders are represented through a single node ( layer-protocol-name = ETH).

It is possible to import a lot of this information directly from JIRA.

PTLs, please add more context about what has changed in this release and why it is important if it is not already included in the JIRA description.

Key odl project Reporter Description

  • No labels