Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

**** Note: PTL, please update key updates by end of September ***

...

This page provides a summary of project-by-project release updates.  

Project

Key Updates

Benefits

Associated Jira Tickets

A&AI (

14

15.0.1)

  1. Java 11 update

  2. Janusgraph update to 1.0.

0 (question)
  1. 1

AAI is still on Java 8. Newer Java versions are required to update some dependencies

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-3734

Authentication (

14

15.

1

0.0)

  1. Support for REALM Client AuthorizationSettings

The feature adds the possibility to
  1. Update keycloak-config-cli and oauth2-proxy versions

  2. Compatibility to keycloak version 26.x

The feature adds the possibility to add "authorizationService" configuration to a Realm client (https://www.keycloak.org/docs/latest/authorization_services/index.html)

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-3306

CCSDK

  1. provide incident API 

  2. Upgrade to OpenDaylight Potassium release

  3. Remove deprecated Biermann interface

  4. Begin work to upgrade to OpenDaylight Calcium release

  1. Preliminarily provide an incident management framework to reduce the pressure on OSS/BSS by aggregating lots of anomalous data into a small number of incidents. 

  2. Update to OpenDaylight Potassium will refresh third party dependencies to a more current version.

  3. Biermann interface is no longer supported in OpenDaylight.  This code is fairly complex and requires substantial work for each OpenDaylight upgrade.  Removal of this code will relieve this support overhead.

  4. OpenDaylight Calcium is a large update.  It is not clear whether this work will fit in the ONAP Oslo release.  Our plan is to begin this to create our Oslo branches based on Potassium once it is stable and then begin work on the Calcium port in the master branch so that , if not complete, it can easily be deferred to Paris.

Moved this from New Delhi to Oslo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-3991

CDS (13.0.

2CLICPS

3)

  1. Support the external creation of the CDS DB
It is now possible to use a MariaDB DB, which is created outside of CDS
  1. Update CDS Blueprint Processor to Java 17

  2. Add SecurityContext settings for "production" readiness

  1. Fix security vulnerabilities

  2. Make cassandra chart "production" ready in respect to security policies

https://lf-onap.atlassian.net/browse/CCSDK-4059

CLI

CPS (13.0.1)

  1. Enhancement of CPS-Core endpoints

  2. XML Support

  3. Granular Control of CPS Notification

  4. Metrics For DMI endpoints and Rest Template replacement

  5. Continuous performance enhancement

  6. NCMP interfaces (Legacy) now support AlternateId

  1. This has help to streamline API responses , response codes

  2. Bring the capability to return the response in the XML format from the CPS Core APIs

  3. This allows subscription with dataspace, anchor, and xpath filters to produce notifications accordingly.

  4. Improved metrics For DMI endpoints have helped to enhance monitoring, efficiency and scalability

  5. Enhance testing accuracy and efficiency and more reliable system performance.

Jira Legacy
  1. Supporting alternateId allows integration with systems that utilize different identifier formats also enhances NCMP scalability and robustness.

  • Jira Legacy
    serverSystem Jira

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  • serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1632

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-

1632
  • 2082

  • Jira Legacy
    serverSystem Jira

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  • serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2081

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-

2082 Jira LegacyserverSystem JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyCPS-2148
  • 2148

  • Jira Legacy
    serverSystem Jira

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyCPS-2081

DCAEGEN2-Services (15.0.0)

  1. removed outdated or unsupported modules

Chart only contains modules, which work in Oslo release (e.g. using native Kafka instead of DMaaP):

  • dcae-datalake-admin-ui

  • dcae-datalake-des

  • dcae-datalake-feeder

  • dcae-hv-ves-collector

  • dcae-ms-healthcheck

  • dcae-prh

  • dcae-ves-collector

  • dcae-ves-openapi-manager

Jira Legacy
serverSystem Jira

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyCPS-1966DCAEGEN2-Services

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-3309

DMaaP

Documentation

Cleanup of deprecated modules.

Update of the ONAP logo.

Interactive architecture diagram updated.

NBI - External API Framework (13.0.1)

Holmes

No changes

No change

Integration

Modeling

No changes

No changes

MultiCloud (15.0.

0

2)

  1. removed outdated or unsupported modules

Chart only contains modules, which work in Oslo release

(e.g. using native Kafka instead of DMaaP)

:

dcae
  • multicloud-

datalake-admin-ui
  • dcae-datalake-des

  • dcae-datalake-feeder
  • dcae-hv-ves-collector
  • dcae-ms-healthcheck
  • dcae-prh
  • dcae-ves-collector
  • dcae-ves-openapi-manager
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3309

    DMaaPDocumentationNBI - External API Framework (13.0.1)HolmesNo changesNo changeIntegrationModelingNo changesNo changesMultiCloud (15.0.0)
    1. removed outdated or unsupported modules
    Chart only contains modules, which work in Oslo release:
  • multicloud-fcaps
  • multicloud-k8s
    • fcaps

    • multicloud-k8s

    Make chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3309

    OOM - common (13.2.10)

    1. extend securityContext setings in _pod template to fix policy violations 

    2. add resources entry to the Cassandra-Operator instance template

    Templates will support:

    • common settings to make ONAP charts "production" ready in respect to security policies.

    • Offer more options to cassandra instance creation via Operator

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-

    3309

    3312

    OOM -

    common

    cassandra (13.

    2

    1.

    6)
    1. extend securityContext setings in _pod template to fix policy violations 
    2. add resources entry to the Cassandra-Operator instance template

    Templates will support:

    common settings to make ONAP charts

    1)

    1. Add SecurityContext settings for "production" readiness

    2. Optimize settings and specify "resource" settings

    • Make cassandra chart "production" ready in respect to security policies

    .
  • Offer more options to cassandra instance creation via Operator
  • Jira LegacyserverSystem

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3312

    OOM -

    cassandra

    mariadb-galera (13.

    1

    2.

    1

    3)

    1. Add SecurityContext settings for "production" readiness

    Optimize settings and specify "resource" settings
    1. Support new mariadb-operator release

    • Make

    cassandra
    • mariadb chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3312
    OOM - mariadb-galera (13.2.3

    OOM - mariadb-init (13.0.2)

    1. Add SecurityContext settings for "production" readiness

    Support new mariadb-operator release
    • Make

    mariadb
    • mongodb chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    OOM -

    mariadb-init

    mongodb (

    13

    14.

    0

    12.

    2

    4)

    1. Add SecurityContext settings for "production" readiness

    • Make mongodb chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    OOM - mongodb-init (

    14

    13.

    12

    0.

    4)
    1. Add SecurityContext settings for "production" readiness
    Make mongodb

    2)

    1. new component to support mongodb configuration

    • Provides the possibility to configure externally created mongoDB instances

    OOM - postgres (13.1.0)

    1. Add SecurityContext settings for "production" readiness

    • Make postgres chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    OOM -

    mongodb

    postgres-init (13.0.

    2)
    1. new component to support mongodb configuration
    • Provides the possibility to configure externally created mongoDB instances
    OOM - postgres (13.1.0)
    1. Add SecurityContext settings for "production" readiness
    Make postgres chart "production"

    3)

    1. Add SecurityContext settings for "production" readiness

    • Make mongodb-init chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    OOM -

    postgres-init

    readinessCheck (13.

    0

    1.

    3

    1)

    1. Add SecurityContext settings for "production" readiness

    • Make

    mongodb-init
    • readinessCheck chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    OOM -

    readinessCheck

    timescaleDB (13.

    1

    0.1)

    1. Add SecurityContext settings for "production" readiness

    2. Update image version

    • Make readinessCheck chart "production" ready in respect to security policies

    Jira Legacy
    • Use an updated postgres image version

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    OOM - timescaleDB (13.0.1)
    1. Add SecurityContext settings for "production" readiness
    2. Update image version
    • Make readinessCheck chart "production" ready in respect to security policies
    • Use an updated postgres image version

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-

    3288OOFOSA (

    3310

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3310

    OOF

    OSA (SecCom)

    Policy (

    14

    15.0.

    5

    1)

    1. High Availability Support for ACM-R and Participants

    2. Addition and removal of elements in ACM migration

    3. Allow migration to be performed in stages

    4. Prepare, Review and Migrate-precheck APIs in ACM

    5. Support for Postgres database in drools pdp

    6. Add SecurityContext settings for "production" readiness

    1. High availability feature in ACM ensures continuous operation with minimal downtime of the application even in the event of failures by distributing workloads across redundant systems.

    2. Advanced migration capabilities like addition/removal of elements feature, facilitates the user to migrate the existing software system to a newer system with wider range of extended capabilities.

    3. Staging feature allows the migration of ACM instances in complex systems where the workflow invokes the same element for multiple operations. This feature adds robustness to the existing migration feature in clamp.

    4. Introduction of prepare, precheck and review Apis adds advanced capabilities for the user to query and understand the present runtime state of the system before triggering a new operation in ACM.

    5. Drools pdp component can now be used with both mariadb and postgres databases with the removal of mariadb dependency from the code.

    6. Make policy chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyPOLICY-4913

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyPOLICY-4917

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyPOLICY-4957

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyPOLICY-4914

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyPOLICY-4215
     

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3288

    Portal-NG (13.0.1)

    1. Angular update from 13 to 16+

    2. Make chart "production" ready in respect to security policies

    RAN-SIM

    RAN Simulator enhancements

    RAN Simulator enhancements

    SDC (13.0.1)

    SDN-C (15.0.0)

    1. removed dmaap-listener subchart

    2. Upgrade to OpenDaylight Potassium release

    3. Remove deprecated Biermann interface

    4. Begin work to upgrade to OpenDaylight Calcium release

    • Chart only contains modules, which work in Oslo release

    • Update to OpenDaylight Potassium will refresh third party dependencies to a more current version.

    • Biermann interface is no longer supported in OpenDaylight.  This code is fairly complex and requires substantial work for each OpenDaylight upgrade.  Removal of this code will relieve this support overhead.

    • OpenDaylight Calcium is a large update.  It is not clear whether this work will fit in the ONAP Oslo release.  Our plan is to begin this to create our Oslo branches based on Potassium once it is stable and then begin work on the Calcium port in the master branch so that , if not complete, it can easily be deferred to Paris.

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3309
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDNC-1846

    SO (13.0.2)

    STRIMZI
    1. SO migration to Jave 17

    • SO migration to Java 17

    STRIMZI (13.0.2)

    1. support latest Strimzi-operator and Kafka version

    2. Add SecurityContext settings for "production" readiness

    1. Update to latest version

    2. Make policy chart "production" ready in respect to security policies

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-3311

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM

    -3288UUI1.Version Updates
    • Upgrade PostgreSQL to 42.7.3
    • Upgrade nimbus-jose-jwt to 9.4
    Upgrade to the latest version Jira LegacyserverSystem JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

    -3288

    UUI

    1. Version Updates

    • Upgrade PostgreSQL to 42.7.3

    • Upgrade nimbus-jose-jwt to 9.4

    1. Multi-Operator Knowledge Q&A Function Based on MaaS

    • The frontend service adds a new page for building the knowledge assistant and knowledge base.

    • The backend service provides a unified interface for building a knowledge base.

    • The backend service provides a unified interface for building a knowledge Q&A assistant.

    • The backend service provides a unified interface for accessing the knowledge Q&A assistant.

    • The backend service is connected to Operator A's MaaS platform.

    • The backend service is connected to Operator B 's MaaS platform.

    • Upgrade to the latest version

    • Supports the creation and deletion of knowledge bases, including kv databases, vector databases.

    • Developers can create the same Q&A assistant compatible with various operators' MaaS systems.

    • User from different operators to easily access and utilize the same Q&A Assistant.

    • Offers scalability and flexibility to facilitate the addition of new large models and knowledge bases in the future, adapting to evolving business requirements.

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyUSECASEUI-840

    VF-C

    No changes

    No changes

    VNFSDK

    No changes

    No changes

    VNFRQTS

    No changes

    No changes

    VVP

    No changes

    No changes

    Benchmark

    No changes

    No changes

    Infrastructure Improvements

    Version Updates

    • Kubernetes

    (>= v1.28.6
    • (>= v1.28.6)

    • Cert-Manager (1.16.2)

    • Istio (v1.

    23
    • 24.

    0
    • 1)

    • Operators:

      • Strimzi-Kafka (0.

    42
      • 44.0)

      • K8ssandra-

    operator
      • Operator (v1.

    18
      • 20.

    0
      • 2)

      • Mariadb-

    operator
      • Operator (0

    .29
      • .36.0)

      • Postgres-Operator - CrunchyData (5.7.2)

      • MongoDB-Operator - Percona (1.18.0)

    • Keycloak (

    22
    • 26.0.

    4
    • 6)

    - Instructions updated

    Latest versions of infrastructure components solve security fixes, are supported and deliver the latest features

    This table shows use case blueprints:

    Use Case Blueprint

    Key Updates

    Benefits

    5G

    No changes

    No changes

    E2E Network Slicing

    No changes

    No changes

    PNF software upgrade without schema update

    No changes

    No changes

    PNF software version onboarding

    No changes

    No changes

    CCVPN

    No changes

    No changes

    BBS

    No changes

    No changes

      O-RAN Harmonization

    TBD

    TBD

    Tactical Use Case Blueprint

    PNF support

    No changes

    No changes

    Change Management

    No changes

    No changes

    Control Loop

    No changes

    No changes

    K8s cloud region

    No changes

    No changes

    Scaling

    No changes

    No changes

    Here is a list of a few subcommittees (use-case, architecture, security), Anuket Assurance, and other activities.

    Subcommittee

    Key Updates

    Benefits

    Arch Subcommittee

    • ONAP Streamlining evolution 

    • Clean-up for unused components

    ONAP users can leverage their CD (Continuous Deployment) mechanisms to pick-and-choose desired ONAP functions for network automation solutions.

    Security Subcommittee

    • Recommendations for package upgrades

    • Add python compatibility module

    • CLM scan for Portal NG

    ONAP component security enhancements

    Modeling Subcommittee

    No changes

    No changes

    Standards Harmonization

    TBD

    TBD

    Other Activities

    Anuket Assurance

    TBD

    TBD

    Controller Design Studio (CDS)

    Anchor
    CDS
    CDS

    No changes

    No changes

    Finally, here is a list of S3P activities (security, documentation covered above)

    S3P Activity

    Key Updates

    Benefits

    Stability

    No changes

    No changes

    Scalability

    No changes

    No changes

    Performance

    No changes

    No changes

    Manageability

    No changes

    No changes

    Resilience

    No changes

    No changes

    Usability

    No changes

    No changes

    Code Footprint Reduction

    No changes

    No changes