| | |
|---|
A&AI | Implemented new parent POM under org.onap.aai.aai-common.aai-parent for simplified management of 3rd party dependencies Upgrade to spring-boot 2 (partially complete) Model updates and edge rules changes in support of the following use cases: Papyrus XMI UML files for run-time data model reverse engineering Integration with sonarcloud
|
|
AAF | |
|
APP-C | Features: Resource resolution via CDS ODL Neon SR1 update with ONAP distribution vnfc/vf-module/v-server operations support for ansible LCMs New LCM commands implemented: ActivateNESw ConfigScaleIn DownloadNESw GetConfig LicenseManagement PostEvacuate PostMigrate PostRebuild PreConfigure PreEvacuate PreMigrate PreRebuild Provisioning StartTraffic StatusTraffic StopTraffic
Move northbound DMAAP adapter out from ODL OSGI Karaf base
Security: Removed hardcoded password for Maria DB Moved to non root processes for all APPC Pods Moved All connections to https Openstack password encrypted Fixed SQL injection vulnerability
Quality: |
|
CLAMP | Improve model driven control implementation by: Implementing a new Control Loop creation flow: Self Serve Control Loop(partially done will be continued in next release). Adding Tosca policy-model support for Operational Policies definitions.
Add integration to CDS for Actor/Action selection. Move from SearchGuard to OpenDistro for the ELK stack based Control Loop Dashboard. Improve security by: Removing even more vulnerabilities from the code at the point that there is none today!. Implementing all the SECCOM must have User Stories.
| Move closer to a full model driven Control Loop end to end in ONAP (from SDC, to Policy, to CLAMP to DCAE). Improve Security and Vulnarabilities.
|
CCSDK | For the Frankfurt Release, much of the work in CCSDK was focused on extending the Controller Design Studio (CDS) platform. This work is described in more detail below (see #CDS row below).
|
|
DCAE | DCAE Platform Enhancement MOD platform will eventually replace SDC_DCAE-DesignStudio. For Frankfurt, DCAE-MOD can be used to onboard DCAE components,compose flows (Service composition), generate and distribute dynamic blueprints into DCAE Platform/Runtime - enabling users to onboard and deploy MS on-demand DCAE Platform (Policy-Handler) enhancement enables automated policy based reconfiguration for DCAE MS in near real-time manner. Dynamic AAF certificate creation during component instantiation Helm chart optimization to control each platform component separate Dashboard Optimization Blueprint generator tool to simplify deployment artifact creation Deployment/bootstrap optimization
Following are new services components are delivered with Frankfurt. New DCAE service components delivered add into expanding ONAP/DCAE MS catalog; this enables new usecase support and data/analytics integration capabilties. Event Processors PM Subscription Handler DataLake Handlers
Analytics/RCA Acumos Adapter (PoC)
Acumos Adapter provides mechanism to onboard Models from Acumos into ONAP and onboard (through MOD into DCAE). This enables designer to use this model for deploying catalog for designers
Security Improvements Python 3.x migration Java 11 migration (VES, HV_VES, BBS-EP, SDK) Resolved all outstanding OJSI Switched external interfaces to HTTPS (VES, Dashboard, HV_VES)
|
|
DMaaP | DMaaP DR
Dynamic cert distribution from OOM AAF
Implement boolean flag in OOM to disable HTTP ports
Added more test cases
Addressed SECCOM/OJSI must have stories
Disabled external facing HTTP ports DMaaP MR
Enhance to protect all update operations in Kafka
Create Kafka image using Confluent 5.3.0
Create custom Zookeeper image using confluent 5.3.0
Disable the AAF authn/authz using a single flag
Securing the Kafka ZNodes using ACLs
Added Prometheus monitoring capability
Disabled external facing HTTP ports
Addressed SECCOM/OJSI must have stories
DMaaP BC
Upgrade to Java 11
Addressed SECCOM/OJSI must have stories
Disabled external facing HTTP ports
|
|
Documentation | For the Frankfurt release the doc team has provided Improved end to end user guides. A refined release note template to be used by all projects in ONAP. To ensure a common way of how to provide the release notes from a content such a look and feel perspective. In addition the documentation project continuously work with improving processes and tools for documentation. Enabling the community to as easy as possible document all the aspects of the ONAP platform. During the Frankfurt release cycle we have started the work to clean up available content, both on the wiki and readthedocs (docs.onap.org) as well as moving the documentation away from submodules according to the LFN documentation strategy. |
|
External API Framework | Security: Integration with AAF for automatic certitificate retrieval Migration from http to https Use common secret template to generate DB credentials Migration from Java 8 to Java 11 removal of nbi root container
Use Cases: 5G E2E Slicing, new support for CST and serviceType in Service Ordering
Bug fixes: Public HTTP port open | Improved security and integration with AAF, with automatic retrieval of Certificates using AAF Init on OOM install.
|
Holmes | Not part of the Frankfurt Release | Not part of the Frankfurt Release |
Integration | Daily and Gating chains, that were introduced in El Alto, have been improved especially from a security perspective. Since January, we performed more than 6000 installations and performed more than, 25,000 tests on 2 infrastructure (Orange + Azure)
We integrated a security category addressing
- Infrastructure CIS, vulnerability tests
- Check of the public end points
- Chase rooted pods
- Exclude any open debug java port The Frankfurt version will be much more secure than any version before (heavy work from OOM team - hardcoded password removing, templating, removing on certificates in pods). Moreover as we put in place these tests in CI, it is now possible to measure the progress in this area, which is key for production use. This version was the first version when we delineated between an experimental orchestration solution (used for cutting edge demos) and production grade features (requiring a better architecture, stability, security,..). Testing remains an area of improvement though some projects have already refactored their healthcheck test suites. |
|
Logging | Not part of Frankfurt Release | Not part of Frankfurt Release |
MSB | Features: Security: Migration from HTTP to HTTPS Using none-root user to run processes inside containers Upgrading version of some third-party dependencies
| Improved security and enabling access through MSB to Frankfurt APIs |
Modeling | ETSI alignment support: Support the ONBOARDING_PACKAGE directory for the original vendor ETSI package extraction Enhance APIs for the SO SOL003/SOL005 Adapter Support VNF package Subscription and Notification
Security
Use common secret template to generate DB credentials SECCOM Password removal from OOM HELM charts Enable micro-service access via MSB HTTPS
|
|
MultiCloud | Upgrade MultiCloud-StarlingX plugin to support onboarding and orchestration workload to StarlingX 3.0 Add containerized firewall as demo CNF to deploy over StarlingX 3.0 Decouple OpenStack HPA discovery logic from OpenStack Plugins | Enable the PoC of CNF orchestration to StarlingX 3.0 Flexibility to choose appropriate OpenStack HPA discovery logic during phase of deploying MultiCloud plugins |
Music | Separate rest api from core api to improve adoptability for applications wishing to use music as a library. Improved configuration of Cassandra connection to allow more flexibility with connection. Thread safe locking to prevent multiple requests conflicting when creating a lock. Lock clean up daemon to improve performance when there are stale locks present Updating helm charts to spring boot version of music Added support for https in MUSIC through AAF certificates Benchmark the SQL-based plugin for MUSIC (mdbc) with TPC benchmarks that are widely used in the DB Improved MUSIC performance through enhanced locking semantics, policies
| Improved performance, usability and security. |
CLI | Not part of Frankfurt Release | Not part of Frankfurt Release |
OOM | No OOM related architecture changes in this release. Support for sub-chart packages (sub-chart can be deployed independently if required) Use of k8s Secrets to apply configured/generated passwords Platform infrastructure deployment with TOSCA Bug Fixes
| Improved security and usability. |
OOF | Use cases: Migration to new policy lifecycle APIs. Along with architectural enhancements, this enables catering to self-serving control loops. 5G Network Slicing: Supports optimized Slice/Slice Subnet selection, which is a fundamental step in E2E slice orchestration. CCVPN: Supports model-driven route optimization for OTN paths between two domains.
Architectural enhancements: Re-architect Optimization Design Framework platform as independent optimization run-times and compile time libraries. Allows easier on-boarding new (and custom) optimizers with limited impact on existing optimizers. Enables run-time insertion of optimization models for the generic solvers.
Security: Non root processes for all OOF Pods All connections move to https Implemented SECCOM password retrieval recommendations
|
|
UUI | 5G network GUI （Support the whole flow of creating 5G network slicing service）: Provide CSMF portal for the network slicing customers Provide NSMF portal for the network slicing operators Enhance the Monitor Module for monitoring 5G network slicing
CCVPN GUI : Https: Update the frontend and backend service to https
|
|
Policy | New Features: Policy Update Notifications - When versions of policies are deployed/undeployed, an update notification is sent on Dmaap topic so that clients (DCAE in particular) can make Decision API call to get the latest policy that they should be enforcing. Native Policy Support for each PDP was implemented. Now users can use the APIs to create policies specific to a PDP such as Drools Rules, XACML XML policies and Apex policies. Consolidated the health check of all the components into the PAP. Previously each component had to be queried for health status, now a single call to the PAP can retrieve the health of all the components. NOTE: This does not include legacy components Configurable Pre-loading and pre-deployment of policies. When ONAP is brought up, the user can configure a set of default policies that can be created and deployed. Enhancements to Lifecycle APIs Enhancements to PAP Deployment API's Fetch policy deployment status: Clients will be able to poll the PAP API to find out when policies have been successfully or unsuccessfully deployed to the PDP's. A new API available for Create and Update PDP Groups A new API is introduced to deploy policies on specific PDPGroups
Statistics for XACML and Apex PDP components enhanced. Policy Distribution now uses the Lifecycle API and PAP deployment API to auto create and deploy policies upon service distribution. The legacy API's support were removed. XACML PDP New Features: Decision API for monitoring policies was enhanced to support an abbreviated list of policies. Decision API now supports naming policies for CCSDK project. Decision API now supports a closest match algorithm for optimization policies and enhancements were made to better support policies with "matchable" properties.
Drools PDP New Features Support for offline mode which allows users to run drools in a locked environment. Parameterize mvn repo urls and proxy settings which allows the users to build the docker images for drools-pdp and drools-application using their own CI pipelines. New Controller TOSCA Policy Type support so users can configure controllers during Design Time. Telemetry API enhanced to support Native and Controller TOSCA Policy Types.
Apex PDP New Features CDS as an actor in Control Loops is now fully supported. Introduced in Dublin, the new actor is now available to be used in Operational policies.
Maintenance and Security All components were upgraded to JDK 11 Many dependencies were upgraded to clear known security issues and/or to keep up with improvements in 3rd party libraries. For a full listing, see release notes. Hard coded passwords were removed from the components. Now readable from environment variables allowing OOM charts to use secrets for setting passwords.
Feature Improvements Treatment of PASSIVE state for PDPs: If a PDP fails to deploy one or more policies specified in a PDP-UPDATE message, PAP will undeploy those policies that failed to deploy to the PDP. This entails removing the policies from the Pdp Group(s), issuing new PDP-UPDATE requests, and updating the notification tracking data. Improvements in validation of Policy Types and Policies Fixes for Policy Versioning When retrieving a Policy Type, inherited policy types are now included in the API call along with referenced Data Types. Control Loop Operational and Guard TOSCA Policy Types were defined and implemented. The legacy yaml is still supported, but will be deprecated in the next release. Deployed API removed from API and now is supported in the PAP Control Loop actor code was re-designed and cleaned up enabled faster integration of new actors and operations for control loops. Control Loop Events were enhanced to support rate limiting of ONSET events to control the flooding of events from DCAE analytics. Drools PDP Improvements XACML PDP Improvements Apex PDP Improvements Changed JavaScript executor from Nashorn to Rhino as part of Java 11 upgrade. Passing parameters from ApexConfig to policy logic. Added support for interaction with CDS over gRPC
Experimental New PDP Monitoring GUI is available for experimental use to view PDP groups and the PDPs in those groups. Users can visualize the heartbeat, statistics, and health of the PDPs in each group. Drools PDP a new server pool implemented was contributed.
|
|
Portal | Angular Upgrade from 1.X to 7.0 - Portal and SDK (Backward Compatible) Close HTTP Ports (Portal, SDK) OParent 2.0 Migration & Self Release Jobs Address Security Vulnerabilities from Nexus-IQ (Jars and Javascript libraries) UI/TypeScript Test Coverage - (Portal Coverage 60% and SDK Coverage 63%) Spring Boot Migration (Portal only/ Partially Completed) Containers to run as Non-Root user
| Enhanced rich UI, improved backend performance, added reporting features and matured security. |
SDN-C | |
|
SDC | |
|
SO | ETSI alignment improvements - Ericcson, Huawei, Samsung, Verizon LCM evolution with API decision tree - Ericcson, Nokia, Bell Canada PNF orchestration Enhancements - Ericcson, Huawei, Nokia CCVPN Enhancement 5G Slicing - ATT, Amdocs, CMCC, Huawei, Wipro
|