[TSC-252] NETCONF Magnesium Release Plan Created: 07/Nov/19  Updated: 07/Nov/19

Status: Open
Project: tsc
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Project Plan Priority: Medium
Reporter: Balaji Varadaraju Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

ODL Project: netconf
ODL Release:
ODL Participation: SNAPSHOT_Integrated (Managed)
ODL Checkpoint: Initial

 Description   

For NETCONF Magnesium release we are planning to work on the following items.

 

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

 
 
 
 
 

 

 

 


Generated at Wed Feb 07 20:45:39 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.