Content Comparison

• Schema version update v28:

  • Cell Object:
    new attribute cell.band so that the frequency band info can be storedAAI,

  • Neighbour Object:
    new attribute neighbour.relation-type so that the neighbour relation type can be stored (e.g. NR_NR, NR_LTE, LTE_GSM etc.)

• tracing support in aai-resources
• dependency updates

Upgrade to OpenDaylight Argon version, Service Release 2

• CPS Path Improvement, we recently added %, >,<, OR, Contains functionality and use of recursive SQL to fetch descendants in CPS Path querying
• Upgrade to Java 17, Spring boot uplift to v3.1.2 and OpenApi 3.
• Support Multiple CM-Handles for NCMP Get Bulk Operation 
• Completed top-level data nodes support, patch operation for multiple data nodes is now supported.
• Significant improvement of read/write and query operations 
• Improve stability by huge reduction of memory consumption
• OpenSSF Best Practices GOLD badge

• The enhanced queries allow client to avail of such queries and possible move certain filter operations back to CPS does reducing data transfer and complexity on the client side.
• Improved performance will allow clients to process more data at greater speed.
• Upgrade of Java, Spring Boot and OpenAPI will help significantly improve vulnerability assessment and security assessment.
• The memory reduction apart from stability will also reduce the footprint of the whole system and any related cost.
• Bulk operations will reduce the amount of calls client need to make in certain use cases.
• Support for multiple top level nodes for all operations allow clients to use any operations with models that have multiple root nodes which is quiet common.
• Achieving OpenSSF Gold standard will give client great confidence in the quality, security and reliability of CPS. 

• Updated Java to Version 17

No changes

• Add support for YANG modules automation

• Provides YANG modules automation tools, which helps improve the YANG development efficiency and check the version update of the YANG model.

• Add support for Gateway-API in Ingress template (13.0.1)
• Add support for mariadb-operator (13.0.2)

• Besides the Istio Ingress APIs now the support for Gateway API is added to the templates (https://istio.io/latest/docs/tasks/traffic-management/ingress/gateway-api/), which includes:
  
  • TCP Routes
  • UDP Routes
• MariaDB-operator (https://github.com/mariadb-operator/mariadb-operator) offers a declative way to manage MariaDB instances, including:
  • logical DBs, Users, Grants
  • HA (e.g. Galera)
  • Backup and restore
  • Support for latest MariaDB releases

• MariaDB DBs (version 11.1.2) will be created via Operator (13.0.1)

• All ONAP MariaDB instances will now be created with the latest version by default using the mariaDB-operator
• Add Galera clients (e.g. SO, SDNC) will use access to "primary" pod to avoid "Deadlocks" 

• Add default role creation to ServiceAccount

• Via global option it can be decided, whether the ServiceAccount Chart includes the required roles
• This supports the deployment of single ONAP components without a "common" roles-wrapper
  (see ONAP deployment evolution)

• Java 11 upgraded to Java 17
• Latest version of Spring Framework and Springboot supported
• Support for update and upgrade on CLAMP ACM

• Amount of security vulnerabilities drastically reduced
• Users can now update and upgrade their ACM compositions

• First full release
• Adapt the PortalNG to the build, test and release processes of the community

• Introduce new PortalNG as a maintained alternative to the unmaintained portal project

• Support for update of service through import of service template
• Support for update of service through import of service CSAR
• Support for adding/updating interfaces on services
• Support for TMF641 v4.1 milestone and jeopardy events
• Support for timeout in operation implementations
• Support for customization of CSAR generation on a per model basis

• Services can be updated directly in yaml when desired

• More comprehensive support for defining behaviour of interface operations

• Adaptability to define CSAR structure and content to suit the requirements of individual models

Fix the security vulnerabilities.

Better security for all the ONAP flows

• Optimize the intent report processing process and provide the intent report export capability
• Complete component upgrades, including java upgrades to version17, and so on

• Support offline viewing of intent report information
• Upgrade component version will help improve vulnerability assessment and control risk

No Changes