Deadline for contribution by RC0
Key Highlights (1 Pager): ONAP Istanbul Oct-2021 Updates_V5
This page provides a summary of project-by-project release updates. The table shows the list of approved projects.
|APPC||Not part of the release||Not part of the release|
|CLAMP||Not part of the release (Merged into Policy)|
- All DCAE microservices migration to helm was completed in Istanbul release. Since Honolulu, 13 additional MS has been delivered added for Helm deployment support and parallel support under Cloudify/blueprint (legacy) retained for regression/backward compatibility
- Helm-generator tool (as POC) available for generating DCAE component helm-chart given component spec. This tool will be integrated with MOD/design flow to support helm chart generation and distribution for Jakarta release.
- SliceAnalysis and KPI-Computation MS migrated from ConfigDb to CPS
- HV_VES microservice was adapted to support stdDefined domain introduced under VES7.2.1 spec
- Enhanced PMSH Microservice to support subscription property updates, config updates to support 'n' subscriptions, support resource name in filter
- Implemented CPS client interface (replacing ConfigDb)
No major functional changes.
Consolidated Message Router and Bus Controller repos.
Sonar & Security updates.
Simplified repo structure.
|External API Framework||Not part of the release||Not part of the release|
Some bugs are fixed so Holmes gets more stable.
Gating on Python tests
Stability of the test environment
More cases automatically tested
|Logging||Not part of the release||Not part of the release|
Some bug fix and parameter optimization
Further changes in k8splugin related to Helm spec support allow for the better and more reliable deployment of complex CNFs defined as a helm package.
|Music||Not part of the release||Not part of the release|
|CLAMP Client Policy and TOSCA Handling|
|Policy Handling Improvements|
|System Attribute Improvements|
|Portal||Not part of the release||Not part of the release|
|SDC||SDC can be used for onboarding resources and designing services with models other than SDC AID|
CNF Orchestration flows in SO have been enhanced (REQ-627).
Internal architecture improvements started in H release have been extended.
Defect fixes and enhancements in E2E slicing, CCVPN usecase realization.
CSIT has been improved.
VNF Macro LCM operation enabled for Create, Delete and Model update for VNF (REQ-883)
Improved S3P and maintainability of SO with divide and conquer strategy.
Validate the new changes at the earlier stage.
|VF-C||Stability and security improvement|
|VID||Not part of the release||Not part of the release|
This table shows use case blueprints:
|Use Case Blueprint||Key Updates||Benefits|
E2E Network Slicing
|OOF-SON||Better alignment with O-RAN O1|
Bulk PM / PM Data Control Improvements
PM data collection control provides 5G network operators with a dynamic and more efficient way to configure performance measurement collection on a selected subset of PNFs/VNFs in the network and complements the existing PM data collection and processing capabilities in ONAP/DCAE. An initial version has been delivered in Rel 7 (5G / Bulk PM / PM Control -
REQ-715 Bulk PM / PM Data Control Improvements
Control Loop in TOSCA
|CLAMP (Control Loop Automation Management Platform) functionalities, recently moved to Policy project , want to provide a Control Loop Lifecycle management architecture. A control Loop is a key concept for Automation and assurance Use Cases and remain a top priority for ONAP as an automation platform. This requirement wants to improve Control Loop LCM architecture focusing on an abstract CL management logic, isolating CL logic vs ONAP component logic, providing a common CL Design time catalogue with a generic CL definition, and elaborate API to integrate with other design systems as well as 3PP component integration. PoCs have been progressed in ONAP Rel G and H in this area, CL LCM redesign has reached a relevant viable set of features and it is ready to be moved in Rel I to mainstream as part of the Policy framework.|
|CCVPN||CCVPN Enhancements (REQ-719) to support Intent Based Networking (IBN), as well as support for Cloud Leased Line services.||CCVPN, in conjunction with the IBN use-case, offers the Intent based Cloud Leased Line service|
|O-RAN Harmonization||VES, O1, CNF, SMO|
|A1 Policy Management|
The O-RAN A1 interface provides a flexible way for RAN operators to steer/inform RAN management.
ONAP Istanbul delivers improvments for managing A1 Policies (part of the O-RAN A1specification) and terminating the A1 interface for A1 Policies.
This functionality is also used downstream in O-RAN-Source Community (OSC) Non-RealTime RIC project, strengthening alignment between ONAP & OSC.
|Tactical Use Case Blueprint|
|K8s cloud region|
CNF Orchestration Enhancements (REQ-627)
|With changes introduced in REQ-627 we will have finally information about created CNF resources in k8s cluster. This information can be utilized later on i.e. in closed-loop context. CNF Healthcheck Workflow in SO will let to monitor the status of CNF deployed into k8s cluster and whether it is healthy or not. Further changes in k8splugin related to Helm spec support allow for the better and more reliable deployment of complex CNFs defined as a helm package.|
Here is a list of a few subcommittees (use-case, architecture, security), Anuket Assurance, and other activities.
Controller Design Studio (CDS)
Finally, here is a list of S3P activities (security, documentation covered above)
|S3P Activity||Key Updates||Benefits|
|Code Footprint Reduction|