.. _onap-release-notes:
-'London' Release Notes
-======================
+'NewDelhi' Release Notes
+========================
-This page provides the release notes for the ONAP 'London' release. This
+This page provides the release notes for the ONAP 'NewDelhi' release. This
includes details of software versions, known limitations, and outstanding
trouble reports.
Details on the specific items delivered in each release by each component is
maintained in the component specific release notes.
-'London' Major Release 12.0.0
------------------------------
+'NewDelhi' Major Release 14.0.0
+-------------------------------
+-----------------------------------+-----------------------------------------+
| **Project** | Open Network Automation Platform (ONAP) |
+-----------------------------------+-----------------------------------------+
-| **Release name** | London |
+| **Release name** | NewDelhi |
+-----------------------------------+-----------------------------------------+
-| **Release version** | 12.0.0 |
+| **Release version** | 14.0.0 |
+-----------------------------------+-----------------------------------------+
-| **Release date** | 2023, July 6th |
+| **Release date** | 2024, not released yet |
+-----------------------------------+-----------------------------------------+
-Features
---------
-
-ONAP 'London' focusses on:
-
-- ONAP takeaways to get feedback from consumers on what we need to prioritize
-- ONAP evolution definition and mission statement refresh
-- Modularity and module bundles for specific use cases (O-RAN SMO, Network
- slicing etc.)
-- Managing unmaintained projects
-- Formalizing ONAP as key player in open RAN @ O-RAN SC TOC Level
-- Getting first project: CPS road for gold badge
-- SBOMs delivery
-- Streamlining Release Management tasks
-- Implementing Service Mesh with ISTIO
-- Improving software quality by fixing bugs and upgrading components packages
-- First implementation of Java 17
-
-Functional Requirements
------------------------
-
-Richer Set of Cloud Native Functionality
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-- Implements ASD-based CNF package onboarding and lifecycle orchestration.
-- Support 3GPP 28.582 APIs for slicing use case.
-
-E2E Network Slicing
-^^^^^^^^^^^^^^^^^^^
-
-Added support for 3GPP 28.532 based APIs in NSSMF for network slicing, with
-focus on RAN slicing.
-
-Control Loop Evolutions
-^^^^^^^^^^^^^^^^^^^^^^^
+ONAP is evolving. We took efforts in streamlining processes and roles and
+NewDelhi release is the first one with agreed simplified software development
+life cycle governance.
-- Improvements to CLAMP Automation Composition Management (ACM).
-- Metadata driven API Generation.
-- Improved Metrics and SLAs.
-- Improved Testing.
-
-Extended O-RAN Integration
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-- Enhancements for Configuration Management notification from O-RAN network
- functions over O1 interface.
-
-Controllers
-^^^^^^^^^^^
-
-- A1 policy and platform enhancements from CCSDK.
-
-Service Design
-^^^^^^^^^^^^^^
+OpenSSF Gold Standard
+---------------------
-- Support for constraints.
-- UI support for view/edit/import data types.
-- Increased support for TOSCA functions.
-- Removed need for USER_ID cookie and header.
+We are proud to announce that first ONAP project achieved OpenSSF Gold
+standard. It will give ONAP consumers great confidence in the quality,
+security, and reliability of CPS.
-Inventory
-^^^^^^^^^
+Java 17
+-------
-- Addition of Cell and Neighbour objects.
+First ONAP projects (CCSDK, CPS, UUI and Policy) completed their upgrades to
+Java 17. Spring boot (uplift to v3.1.2) and OpenApi 3 upgrades were also
+performed. These upgrades allow benefits of patched vulnerabilities and
+software efficiencies in the latest versions.
-ONAP Operations Manager
-^^^^^^^^^^^^^^^^^^^^^^^
+CPS
+---
-- Introduction of "Production" ONAP setup.
-- Removal of unsupported components (AAF, Portal, Contrib,...).
-- Update of component helm charts to use common templates and practices.
-- Introduction of Kubernetes Operators for Cassandra (k8ssandra-operator) - to
- support latest Cassandra version (optional for London) and Keycloak.
+ONAP CPS project continued efforts in improvement of read/write, query
+operations, and huge reduction of memory consumption allowing for improved
+query performance and improve stability.
-Non-Functional Requirements
----------------------------
+Modeling
+--------
-The following 'non-functional' requirements are followed in the 'London'
-Release:
+Modeling project added provision of YANG modules automation tools, which helps
+improve the YANG development efficiency and check the version update of the
+YANG model.
-Security
-^^^^^^^^
+OOM
+---
-- SBOMs generation.
-- Packages upgrades to limit number of affecting vulnerabilities.
+OOM project team added support for Gateway-API in Ingress template (13.0.1) as
+well as support for mariadb-operator (13.0.2). All ONAP MariaDB instances will
+now be created with the latest version by default using the mariaDB-operator.
+Added Galera clients (e.g. SO, SDNC) will use access to "primary" pod to avoid
+"Deadlocks". Additionally added default role creation to ServiceAccount for
+better access management.
-Documentation
-^^^^^^^^^^^^^
+SDC
+---
-- Interactive architecture diagram updated
-- End-2-End guides removed because they have become outdated due to
- unmaintained projects.
+SDC implemented-services update capability directly in yaml was added, more
+comprehensive support for defining behavior of interface operations and
+adaptability to define CSAR structure and content to suit the requirements of
+individual models.
-Tests & Integration
-^^^^^^^^^^^^^^^^^^^
+CCSDK
+-----
-- Minor bug fixes, package upgrades and python version fixes.
-- Migration out of Orange infra and pipelines was started.
+CCSDK continued maintaining alignment with OpenDaylight release schedule by
+upgrading to OpenDaylight Argon version, Service Release 2. This allows latest
+ONAP user to make use of latest OpenDaylight software when they use latest
+release of ONAP.
+PortalNG
+--------s
-.. important::
- Some non-functional requirements are not fully finalized. Please, check
- details at :doc:`Integration <onap-integration:usecases/release_non_functional_requirements>`
+We introduced new PortalNG as a maintained alternative to the unmaintained
+Portal project. Allows ONAP user to make informed decisions on software use of
+maintained and unmaintained projects.
Documentation Sources
---------------------
-The formal ONAP 'London' Release Documentation is available
+The formal ONAP 'NewDelhi' Release Documentation is available
in :ref:`ReadTheDocs<master_index>`.
The `Developer Wiki <http://wiki.onap.org>`_ remains a good source of
- `Badging Requirements <https://github.com/coreinfrastructure/best-practices-badge>`_
- `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
-In the London release,
-- 100% projects passed 90% of the OpenSSF badge
-- 86% passed the OpenSSF badge
-- 11% projects passed the OpenSSF Silver badge
+In the NewDelhi release,
+
+- 100% projects passed 95% of the OpenSSF badge
+- 94% passed the OpenSSF badge
+- 24% projects passed the OpenSSF Silver badge
+- 1 project passed the OpenSSF Gold badge
Project specific details are in the :ref:`release notes<component-release-notes>`
for each component.
ONAP Maturity Testing Notes
---------------------------
-For the 'London' release, ONAP continues to improve in multiple areas of
+For the 'NewDelhi' release, ONAP continues to improve in multiple areas of
Scalability, Security, Stability and Performance (S3P) metrics.
More details in :ref:`ONAP Integration Project<onap-integration:master_index>`
Code Review / doc.git / blobdiff