Magnesium Release
OpenDayLight Magnesium Release: Inputs to Marketing Communications
TSC# | Project | PTL | NEW FEATURES or UPDATES in MAGNESIUM |
---|---|---|---|
237 | LISP Flow Mapping | Lori 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. |
244 | OpenFlowPlugin | Arunprakash D | Following activities has been done in Openflowplugin for Magnesium release:
|
247 | BGPCEP | Ajay Lele | Apart from regular sustenance activities, below features were added:
|
N/A | Controller | Robert Varga |
|
238 | Daexim | Ajay Lele | Apart from regular sustenance activities, below feature was added:
|
241 | Netvirt | Karthikeyan Krishnan |
|
246 | Genius | Hema Gopalakrishnan | Following activities are planned for Genius in the Magnesium release: New Features:-
Enhancements
|
245 | OVSDB | Chetan Arakere |
|
236 | Integration-Distribution | Luis Gomez | During this release we added the ONAP Karaf distribution. This distribution is used by ONAP CCSDK project. |
240 | ServiceUtils | Faseela 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. |
252 | NETCONF | Balaji Varadaraju | The current list of new features that are being targeted for fixing: https://lf-opendaylight.atlassian.net/browse/NETCONF-625 - Race condition causes multiple notification subscriptions (diagnosed) https://lf-opendaylight.atlassian.net/browse/NETCONF-649 - Issue while expanding Mount Point in Opendaylight UI (Restconf) it displays 500 Error Code. https://lf-opendaylight.atlassian.net/browse/NETCONF-645 - Netconf client fails to detect error reply https://lf-opendaylight.atlassian.net/browse/NETCONF-646 - Impossible to subscribe to RESTCONF notification stream due to error https://lf-opendaylight.atlassian.net/browse/NETCONF-639 - Netconf can confuse action definitions when they have equal name https://lf-opendaylight.atlassian.net/browse/NETCONF-631 - Issue with ChoiceSchema(Mix) Node, NullPointer Exception while creating InstanceIdentifierContext for Choice(Mix Node) type. https://lf-opendaylight.atlassian.net/browse/NETCONF-581 - restconf to netconf translation doesn't honor the order of the keys for lists with multiple keys https://lf-opendaylight.atlassian.net/browse/NETCONF-574 - No status for rogue device in callhome server API |
249 | AAA | 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 |
256 | Neutron | 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 |
239 | Infrautils | Faseela 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. |
251 | DetNet | Quan 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. |
235 | JSONRPC | Richard Kosegi | No new features were planed in this release |
N/A | Plastic | Allan Clarke | Enhancements Features |
N/1 | TransportPCE | Guillaume 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.
New Features - 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.