Consolidation of SDC user roles into a single designer role
SO
ETSI alignment improvements - Ericcson, Huawei, Samsung, Verizon
SOL005 adaptation
SOL003 adaptation
SOL002 adaptation
SOL004 - Using the ETSI catalog manager for the SDC models.
PNF orchestration Enhancements - Ericcson, Huawei, Nokia
PNF sotware upgrade
PNF PNP enhancement
CCVPN Enhancement
MDONS support - Fujitsu
Eline support - Bell, Huawei, CMCC
5G Slicing - ATT, Amdocs, CMCC, Huawei, Wipro
NSSMF Adapter implementation
Support of Allocate, Deallocate, Activate and deactivate of the Core NSSMF.
VF-C
Migrate VF-C catalog to Modeing etsicatalog to provide common ETSI catalog service
Support TOSCA based VNF validation for OVP&CVC
Add VF-C CLI command to improve the VF-C usability
Use common secret template to generate DB credentials
SECCOM Password removal from OOM HELM charts
Enable micro-service access via msb https
VID
Security
Adherence to ONAP Logging Spec v1.2 Update to Portal SDK v2.6 Use common secret template to generate DB credentials Java 11 migration from JDK 8 And more...
Bug fixes
Refresh after Add VF Module fails Generates different VF module name during scale out And many more...
For an end-user VID is easier to use.
For a system admin, VID is easier to deploy and manage.
VNFSDK
Security:
HTTPS is enabled for VTP and Marketplace REST Services
Non-Root user is enabled for container
Direct Vulnerability issues are resolved
Features:
VTP REST API is contributed into TMF Test API specification 704-710 / 913 v19.5
VTP Portal is incubated.
Along with CLI, enabled VNF lifecycle testing.
VNFRQTS
Updated Virtual-Function Event Streaming (VES) Event Listener specification to version 7.1.1
Significant updates to VNF security requirements
VVP
OVP testsuite
Migrated OVP VNF Life-cycle validation testsuite to VVP test-engine repo from integration repo.
Preload Plugin Capability
Enhanced VVP validation script for a pluggable preload template creation. Users can write their own plugin to generate preload templates when executing the vvp validation scripts.
ONAP client
Created python client to interact with various onap applications. Currently used by OVP VNF testsuite to model and instantiate a VNF for lifecycle badging.
Benchmark
Amar: Looks inactive
Infrastructure Improvements
Amar: See integration updates
This table shows use case blueprints:
Use Case Blueprint
Key Updates
Benefits
5G
E2E Network Slicing
(a new E2E use case for Frankfurt, we'd also like to apply to publish a separate Blueprint White Paper for E2E Network Slicing use case, same as the community did for other use cases in every release)
5G Network Slicing is one of the key features of 5G. The essence of Network Slicing is in sharing network resources (PNFs, VNFs, CNFs) while satisfying widely varying and sometimes seemingly contradictory requirements to different customers in an optimal manner. Same network is expected to provide different Quality of Experience to different consumers, use case categories and industry verticals including factory automation, connected home, autonomous vehicles, smart cities, remote healthcare, in-stadium experience and rural broadband. An End-to-End Network Slice consists of RAN, Transport and Core network slice sub-nets. This Use Case intends to demonstrate the modeling, orchestration and assurance of a simple network slice (e.g. eMBB). While 3GPP standards are evolving and 5G RAN and core are being realized, this Use Case will start with realizing an E2E Network Slice with a simple example of a 5G RAN, Core and Transport Network Slice sub-nets. It will also align with relevant standard bodies (e.g., 3GPP, ETSI, TM Forum) as well as other open initiatives such as O-RAN where relevant, with respect to both interfaces as well as the functional aspects.
Key features in Frankfurt:
Tenants and network operators can order slice-based services
Enables network slice creation as well as reuse
Supports many of the slice lifecycle management operations
Key capabilities added for ONAP Frankfurt release:
ONAP Frankfurt provides basic capabilities for Network Slice Orchestration
Supports Network Slice lifecycle operations of E2E Slice Design and Creation, Activation, Deactivation and Termination
Provides CSMF and NSMF functionality implemented within ONAP
Supports E2E Slice design including design of Communication Service, Service Profile and Network Slice Template
Supports selection of suitable NST and suitable NSI, covering the scenario of new NSI creation by providing suitable slice profile
Interacts with an external Core NSSMF
This use case is a multi release effort and we will continue to provide more enhancements and features based on what we've implemented in Frankfurt in the subsequent releases.
The ONAP based E2E Network Slicing solution allows a service provider to manage the slices and its constituents by leveraging ONAP existing capabilities.
enables the slice-consumer to request for and activate a network slice on-demand without being concerned about network internals, which is very essential for industry-vertical
An operation guidance will be provided on ONAP wiki in which explicit instructions are provided to help any interested parties to experience ONAP based E2E Network slicing management.
CCVPN
Adding two extension functions / sub use cases for Frankfurt.
End-to-end E-LINE services across the domains over OTN NNI handover. The Frankfurt demonstration includes L1(OTN) and L2(ETH) Topology discovery from multiple domains controllers with in an operator and provide VPN service provision in OTN and ETH network. Use case specific developments have been realized in SO, OOF, A&AI, SDN-C and U-UI components
Multi-Domain Optical Network Service(MDONS). The MDONS sub use-case aims to automate the design, activation & operations resulting from an optical transport (L0/L1) service request exchange between service providers and/or independent operational entities within a service provider network by delivering E2E optical orchestration capabilities into ONAP.Use case specific developments have been realized in SDC, SO, A&AI, SDN-C and U-UI components
E-LINE over OTN NNI extends upon the CCVPN use case by incorporating support for L1/L2 network management capabilities leveraging open standards& common data models such as the IETF ACTN-based transport YANG models.
MDONS extends upon the CCVPN use-case by incorporating support for L0/L1 end customer services that span service provider domains, with a plan to support inter-carrier optical services.
MDONS defines a unified optical service model based upon OpenROADM, T-API, MEF 63, and MEF 64 models, and allows integration of optical domain controllers using either the Open ROADM or TAPI service models.
BBS
In Frankfurt, the BBS team focused mainly on bug fixes, improving the BBS use case multi-vendor support and documentation. This is based on feedback received from many showcases during the previous ONAP releases. The BBS use case continues providing inputs to standardization bodies like BBF (Broadband Forum) in the context of the CloudCO framework interfaces definition.
1. Establishment of a subscriber's HSIA (High Speed Internet Access) service from an ONT to the Internet drain
2. Support the change of location for ONT devices (Nomadic ONT devices)
2.1 PNF (Re-)Registration for an ONT 2.2 Service location modification that is detected by ONAP's analytic and enforced by APEX policy engine
O-RAN Harmonization
Tactical Use Case Blueprint
PNF support
Change Management
Control Loop
DaaS
HPA
K8s cloud region
Significant progress in supporting
Distributed Applications and Distributed network functions.
Multi-tenancy
Multi party K8s Clusters
Provider networks and Multiple Virtual networks on per Cluster
Complex applications
Various deployment intents (Generic Placement intent, Network workload intent)
Logical Clouds for network slices with soft-isolation.
Scaling
Here is a list of a few subcommittees (use-case, architecture, security), OVP, and other activities.
Subcommittee
Key Updates
Benefits
Arch Subcommittee
Security Subcommittee
Modeling Subcommittee
Standards Harmonization
Other Activities
OVP
CDS
Finally, here is a list of S3P activities (security, documentation covered above)