This updates the release notes to reflect 2024.03 Calcium.
Change-Id: I2532c7cefad5dac0acd4ace116b1ad7ffd96f598
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
.. jira_fixed_issues::
:project: AAA
- :versions: 0.18.0-0.18.2
+ :versions: 0.19.0-0.19.3
Known Issues
============
.. jira_known_issues::
:project: AAA
- :versions: 0.18.0-0.18.2
+ :versions: 0.19.0-0.19.3
========================
No changes.
-
New Features
============
No new features.
.. jira_fixed_issues::
:project: BGPCEP
- :versions: 0.20.0-0.20.4
+ :versions: 0.21.0-0.21.4
Known Issues
============
.. jira_known_issues::
:project: BGPCEP
- :versions: 0.20.0-0.20.4
+ :versions: 0.21.0-0.21.4
Behavior/Feature Changes
========================
-This release does not support running mixed-versions clusters. This precludes in-place on-line upgrades,
-as 2023.09 Potassium nodes cannot interchange data with nodes running previous versions in a compatible
-manner. In order to perform the upgrade to 2023.09 Potassium, upgrade one node to this version, then reduce
-the cluster to that single node, then upgrade all the other nodes and then re-grow the cluster to include
-those nodes.
+The ``OpenDaylight Blueprint`` extender has been trimmed down, removing support for the following
+XML elements:
-This upgrade is not directly reversible, once upgraded, a node cannot be downgraded to below 2023.09 Potassium.
+* ``action-implementation``
+* ``action-instance``
+* ``notification-listener``
+* ``rpc-implementation``
+* ``rpc-service``
+* ``specific-reference-list``
+* ``static-reference``
New Features
============
Deprecated and Removed Features
===============================
-Distributed Datastore's ``ask-based`` protocol has been deprecated in this release. Enabling it
-will cause a warning to be logged. Configuration knob along with the actual implementation
-is schedule for removal in a future release.
+Distributed Datastore's ``ask-based`` protocol has been removed in this release. The experimental
+``odl-controller-exp-netty-config`` feature has been removed as well.
Resolved Issues
===============
.. jira_fixed_issues::
:project: CONTROLLER
- :versions: 8.0.0-8.0.2
+ :versions: 9.0.0-9.0.2
Known Issues
============
.. jira_known_issues::
:project: CONTROLLER
- :versions: 8.0.0-8.0.2
+ :versions: 9.0.0-9.0.2
.. jira_fixed_issues::
:project: INFRAUTILS
- :versions: 6.0.0-6.0.2
+ :versions: 6.0.5-6.0.6
Known Issues
============
.. jira_known_issues::
:project: INFRAUTILS
- :versions: 6.0.0-6.0.2
+ :versions: 6.0.5-6.0.6
Behavior/Feature Changes
========================
-The Binding mapping of ``type bits`` YANG statement has been updated to use a dedicated common
-superinterface, ``BitsTypeObject``. Furthermore individual bits within these classes are now represented
-as primitive ``boolean`` values rather than nullable ``Boolean`` objects.
+No behaviour changes.
New Features
============
-Both ``DOMRpcProviderService`` and ``RpcProviderService`` have gained the ability to register single-type
-and flexible multi-type RPC implementations. ``RpcConsumerRegistry`` have gained the ability to access single-RPC
-handles. These capabilities are based on new codegen feature, which generates ``@FunctionalInterface`` interfaces
-for each individual ``rpc``, similar to how ``action`` statements are processed.
-
-Binding code generator now recognizes ``RFC8040 rc:yang-data`` extensions and generates corresponding interfaces.
+No new features.
Deprecated Features
===================
-``NotificationService.registerNotificationListener()`` method has been deprecated, along with its Binding
-specification interfaces based on ``NotificationListener``. These will be removed in a future major release.
-
-``RpcProviderService.registerRpcImplementation()`` methods, ``RpcConsumerRegistry.getRpcService()`` methods and
-Binding specification interfaces based on ``RpcService`` have been deprecated. These will be removed in a future
-major release.
+No deprecated features.
Removed Features
===================
-No removed features.
+``NotificationService.registerNotificationListener()`` method has been removed, along with its Binding
+specification interfaces based on ``NotificationListener``.
+
+``RpcProviderService.registerRpcImplementation()`` methods, ``RpcConsumerRegistry.getRpcService()`` methods and
+Binding specification interfaces based on ``RpcService`` have been removed.
Resolved Issues
===============
.. jira_fixed_issues::
:project: MDSAL
- :versions: 12.0.0-12.0.2
+ :versions: 13.0.0-13.0.1
Known Issues
============
.. jira_known_issues::
:project: MDSAL
- :versions: 12.0.0-12.0.2
+ :versions: 13.0.0-13.0.1
Behavior/Feature Changes
========================
-The ``odl-restconf-nb-rfc8040`` feature has been renamed to ``odl-restconf-nb``.
+The transport layer of the NETCONF protocol implementation has been completely refactored. This effort has all but
+unified the 'normal' and 'call-home' mode of operation. This results in a more maintaintanable codebase with much
+easier feature parity between the two modes.
+
+RESTCONF implementation has been been refactored to a large extent, taking advantage of JAX-RS asynchronous requests,
+so that operations on the datastore and NETCONF devices no longer pin the HTTP thread.
+
+The OpenAPI component has been completely modernized. It is now based on Swagger UI vesion 5.13.0 and is memory
+usage has been brought under control.
+
New Features
============
-Support for subscribing to mounted NETCONF devices has been added. See
-`NETCONF-745 <https://jira.opendaylight.org/browse/NETCONF-745>`__ for details.
-
-A new RESTCONF query extension has been added. This supports reporting only leaf values which have actually
-changed. See `NETCONF-862 <https://jira.opendaylight.org/browse/NETCONF-862>`__ for details.
+No new features.
Deprecated and Removed Features
===============================
-RPC definitions in ``netconf-node-topology.yang`` have been deprecated. Their functionality is completely covered
-by manipulating the configuration datastore.
+The ``odl-yanglib`` experimental feature has been removed.
Resolved Issues
===============
.. jira_fixed_issues::
:project: NETCONF
- :versions: 6.0.0-6.0.4
+ :versions: 7.0.0-7.0.4
Known Issues
============
.. jira_known_issues::
:project: NETCONF
- :versions: 6.0.0-6.0.4
+ :versions: 7.0.0-7.0.4
New Features
============
-``yang-maven-plugin`` now executes during incremental builds and does its best to not overwrite
-unchanged outputs.
+No new features.
Removed Features
================
-``AugmentationNode`` and ``AugmentationIdentifer`` constructs have been removed.
+No removed features.
Deprecated Features
===================
.. jira_fixed_issues::
:project: YANGTOOLS
- :versions: 11.0.0-11.0.2
+ :versions: 12.0.0-13.0.2
Known Issues
============
.. jira_known_issues::
:project: YANGTOOLS
- :versions: 11.0.0-11.0.2
+ :versions: 12.0.0-13.0.2
Code Review / docs.git / commitdiff