Skip to end of banner
Go to start of banner

Magnesium Release

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 37 Next »


OpenDayLight Magnesium Release: Inputs to Marketing Communications

TSC#ProjectPTLNEW FEATURES or UPDATES in MAGNESIUM
237LISP Flow MappingLori Jakab

lorand.jakab@gmail.com

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

Arunprakash D

d.arunprakash@ericsson.com

Following activities has been done in Openflowplugin for Magnesium release:

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

Ajay Lele

ajayslele@gmail.com

For bgpcep project, apart from regular maintenance (bug-fixes, etc.) we plan to work on below features/enhancements in Mg release:

  1. https://jira.opendaylight.org/browse/BGPCEP-365 "BGP-LS topology provider support for Segment Routing"
  2. https://jira.opendaylight.org/browse/BGPCEP-833 "Add support for: Advertising Segment Routing Policies in BGP"
  3. https://jira.opendaylight.org/browse/BGPCEP-881 "Remove OSGi dependency from bgpcep modules"
  4. https://jira.opendaylight.org/browse/BGPCEP-715 "Enforce PCEP Checkstyle"
  5. https://jira.opendaylight.org/browse/BGPCEP-882 "Update PCEP code to latest RFC"
  6. https://jira.opendaylight.org/browse/BGPCEP-883 "Add suppot to Extended Metric in linkstate topology"
  7. https://jira.opendaylight.org/browse/BGPCEP-858 "Full implementation of RFC 5440" (this include the Topology Graph and Path Computation Algorithm)
  8. https://jira.opendaylight.org/browse/BGPCEP-495 "Support for BGP Persistance"
  9. https://jira.opendaylight.org/browse/BGPCEP-790 "Use ipv4-address-no-zone"
N/AControllerRobert Varga

nite@hq.sk


238Daexim

Ajay Lele

ajayslele@gmail.com

DAEXIM is a mature project now. We will continue to fix any bugs that are reported.

One new feature for consideration is filed as:
https://jira.opendaylight.org/browse/DAEXIM-14
It is dependent on:
https://jira.opendaylight.org/browse/CONTROLLER-1913

 More discussion is needed before we can commit to developing the feature.

241Netvirt

Karthikeyan Krishnan

karthikeyangceb007@gmail.com

  • 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

hema.gopalkrishnan@ericsson.com

Following activities are planned for Genius in the Magnesium release:

   New Features:-

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

   Enhancements

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

Chetan Arakere

chetan.arakere@altencalsoftlabs.com

236Integration-DistributionLuis Gomez

ecelgp@gmail.com

During this release we will work on adjusting the distribution for the new MRI projects as well as the required changes to verify the MRI projects.
240ServiceUtilsFaseela K

k.faseela@gmail.com

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.

252NETCONF

Balaji Varadaraju

bvaradar@luminanetworks.com

The current list of new features that are being targeted for fixing:
 
https://jira.opendaylight.org/browse/NETCONF-338 - NETCONF southbound requires notifications.yang model to be present on the device

 
The current list of bugs that are being targeted for fixing: 

https://jira.opendaylight.org/browse/NETCONF-625 - Race condition causes multiple notification subscriptions (diagnosed)

https://jira.opendaylight.org/browse/NETCONF-649  - Issue while expanding Mount Point in Opendaylight UI (Restconf) it displays 500 Error Code.

https://jira.opendaylight.org/browse/NETCONF-645  - Netconf client fails to detect error reply

https://jira.opendaylight.org/browse/NETCONF-646  - Impossible to subscribe to RESTCONF notification stream due to error

https://jira.opendaylight.org/browse/NETCONF-639 -  Netconf can confuse action definitions when they have equal name

https://jira.opendaylight.org/browse/NETCONF-631 -  Issue with ChoiceSchema(Mix) Node, NullPointer Exception while creating InstanceIdentifierContext for Choice(Mix Node) type. 

https://jira.opendaylight.org/browse/NETCONF-581 -  restconf to netconf translation doesn't honor the order of the keys for lists with multiple keys

https://jira.opendaylight.org/browse/NETCONF-574 -  No status for rogue device in callhome server API

249AAA

Venkat Govindarajan

vgovindarajan@luminanetworks.com

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

  1. https://jira.opendaylight.org/browse/AAA-178
  2. https://jira.opendaylight.org/browse/AAA-188

The current list of bugs that are being targeted for fixing

  1. https://jira.opendaylight.org/browse/AAA-186
  2. https://jira.opendaylight.org/browse/AAA-114
  3. https://jira.opendaylight.org/browse/AAA-120
256Neutron

Achuth Maniyedath

achuth.maniyedath@gmail.com

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

k.faseela@gmail.com

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

xiong.quan@zte.com.cn

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.

235JSONRPC

Richard Kosegi

richard.kosegi@gmail.com

No new features were planed in this release
N/APlastic

Allan Clarke

aclarke@pobox.com

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

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

N/1TransportPCEGuillaume Lambert
guillaume.lambert@orange.com

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 also comes with a newer OpenROADM service 5.1 Northbound interface. A limited support of TAPI version 2.1.2 allows to expose a abstracted WDM/OTN topology which masks OpenROADM topology complexity through a TAPI compliant Northbound Interface.


Enhancements
* OTN experimental support added in Magnesium SR0 for portmapping, topology, renderer and PCE (Service Handler not yet ready)
* Functional tests honeynode simulators OTN support and migration to Java 11
* 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 constraints calculation to a GNPy server.
* 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)
     It
exposes only one tapi-node, with all 100GE client ports of xpdr as owned-node-edge-point with a single SIP(Service Interface Point) when their associated line ports are connected to RDM infrastructure through XPONDER-INPUT and XPONDER-OUTPUT links
    - TAPI:service-interface-points to associate tapi service interface point (SIP) to an OpenROADM service-end-point



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

  • No labels