Versions Compared

Key

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

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

...

ProjectKey UpdatesBenefitsAssociated Jira Tickets
A&AI (14.0.1)
  1. Java 11 update
  2. Janusgraph update to 1.0.0 (question)
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.1.0)
  1. Support for REALM Client AuthorizationSettings
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 
  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. 

Moved this from New Delhi to Oslo

CDS (13.0.2)
  1. Support the external creation of the CDS DB
It is now possible to use a MariaDB DB, which is created outside of CDS
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
  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
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1632
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2082
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2081
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2148
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-1966
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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-3309

DMaaP


Documentation


NBI - External API Framework (13.0.1)


HolmesNo changesNo change
Integration


ModelingNo changesNo changes
MultiCloud (15.0.0)
  1. removed outdated or unsupported modules
Chart only contains modules, which work in Oslo release:
  • multicloud-fcaps
  • multicloud-k8s

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

OOM - common (13.2.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 "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-3312

OOM - cassandra (13.1.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

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)
  1. Add SecurityContext settings for "production" readiness
  2. Support new mariadb-operator release
  • Make mariadb chart "production" ready in respect to security policies

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

OOM - mariadb-init (13.0.2)
  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 (14.12.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 (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" ready in respect to security policies

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

OOM - postgres-init (13.0.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 - readinessCheck (13.1.1)
  1. Add SecurityContext settings for "production" readiness
  • Make readinessCheck chart "production" ready in respect to security policies

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-3288

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

OOF


OSA (SecCom)


Policy (14.0.5)
  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+


SDC (13.0.1)


SDN-C (15.0.0)
  1. removed dmaap-listener subchart
  • Chart only contains modules, which work in Oslo release

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

SO (13.0.2)


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-3288

UUI


VF-CNo changesNo changes
VNFSDKNo changesNo changes
VNFRQTSNo changesNo changes
VVPNo changesNo changes
BenchmarkNo changesNo changes
Infrastructure Improvements


...