...
Project | Key Updates | Benefits |
---|---|---|
A&AI |
| |
AAF |
| |
APP-C | Features:
Security:
Quality:
| |
CLAMP |
|
|
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 71833544 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.
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.
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
| |
DMaaP | DMaaP DR DMaaP MR | |
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) 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:
| Improved security and enabling access through MSB to Frankfurt APIs |
Modeling | ETSI alignment support:
Security
| |
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 |
| Improved performance, usability and security. |
CLI | Not part of Frankfurt Release | Not part of Frankfurt Release |
OOM |
| Improved security and usability. |
OOF | Use cases:
Architectural enhancements:
Security:
| |
UUI |
| |
Policy | New Features:
Maintenance and Security
Feature Improvements
Experimental
| |
Portal |
| Enhanced rich UI, improved backend performance, added reporting features and matured security. |
SDN-C | ||
SDC | upgrade in R6 Frankfurt#TEST-CASE-2test-case-2
| |
SO |
| |
VF-C |
| |
VID | Security Adherence to ONAP Logging Spec v1.2 Bug fixes Refresh after Add VF Module fails | 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 |
| |
VVP | OVP testsuite
Preload Plugin Capability
ONAP client
| |
Benchmark | Amar: Looks inactive | |
Infrastructure Improvements | Amar: See integration updates |
This table shows use case blueprints:
Use Case Blueprint | Key Updates | Benefits | |
5G | 5G use case covers a few independent use cases which improves the ONAP capabilities on PNF management. Key use cases which are supported in ONAP Frankfurt release:
| ||
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:
Key capabilities added for ONAP Frankfurt release:
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. |
| |
PNF software upgrade without schema update | PNF software updates are routine for network upgrades to support new features, improve efficiency or increase capacity on the field, and to eliminate bugs. This use case positions ONAP as a vantage point in orchestrating and managing PNF software upgrades inline with the business and service objectives. Deployment and orchestration of new network services over both VNFs and PNFs in a model and software driven way simplifies the network management. As 5G networks will host a large number of PNFs from multiple vendors, streamlining service upgrades that involve PNF software changes through ONAP will reduce the OPEX substantially. The following upgrade scenarios are supported in ONAP Frankfurt release: | ||
PNF software version onboarding is a key feature to onboard the vendor provide PNF software version into the ONAP internal PNF descriptor. This PNF software version information will be used by ONAP Run Time components for the purpose of PNF life cycle management. | |||
CCVPN | Adding two extension functions / sub use cases for Frankfurt.
|
| |
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 | |
O-RAN Harmonization | See 5G | ||
Tactical Use Case Blueprint | |||
PNF support | See 5G | ||
Change Management |
| ||
Control Loop | DaaS | HPASee above | |
K8s cloud region | Significant progress in supporting
Integration with Macro instantiation flow and with CDS for vFW Use Case
| ||
Scaling |
|
Here is a list of a few subcommittees (use-case, architecture, security), OVP, and other activities.
Subcommittee | Key Updates | Benefits | ||||||
Arch Subcommittee | No new updates | |||||||
Security Subcommittee | ONAP security continued to improve in the Frankfurt release.
| |||||||
Modeling Subcommittee | See above | |||||||
Standards Harmonization | See Prague slides | |||||||
Other Activities | ||||||||
OVP | Ongoing | |||||||
Controller Design Studio (CDS)
| Design Time
Run Time
ONAP Component integration
Use Case:
| Design Time
Benefits
Benefits
Benefits
. NOTE:
|
Finally, here is a list of S3P activities (security, documentation covered above)
S3P Activity | Key Updates | Benefits |
Stability | See Catherine's comment below | |
Scalability | See Catherine's comment below | |
Performance | See Catherine's comment below | |
Manageability | See Catherine's comment below | |
Resilience | See Catherine's comment below | |
Usability | See Catherine's comment below | |
Code Footprint Reduction | See Catherine's comment below |