Deadline for contribution by
This page provides a summary of project-by-project release updates. The table shows the list of approved projects in Honolulu.
E2E Network Slicing
In this release, we have made some functional enhancements to NSMF, RAN NSSMF and Transport NSSMF. Further, various scenario combinations w.r.to Slice instance and slice sub-net instances allocation were tested and several gaps/bugs were addressed particularly for the deployment option in which all 3 NSSMFs are inside ONAP. End-to-end testing of Closed Loop and Intelligent Slicing was also performed. In this release, this use case has started using the CPS component in a limited way for RAN related configuration.
Different deployment options are now supported successfully which enables service providers to have the flexibility of using ONAP providing all Slice Management Functions or to integrate (domain)specific 3rd party NSSMFs with ONAP.
| Project | Key Updates | Benefits | |
|---|---|---|---|
| A&AI | - Functional Updates | Enhanced functionality for CCVPN and Network Slicing use case. The ability to control the CRUD interactions by client as part of the configurable multi-tenancy work. Enhanced User interface allowing users to browse, filter, and create dynamic complex queries with a visual builder. The User interface is schema-driven and can output results in card, table, visual, and downloadble formats. Enhanced visualizations of the model with enhancements in GraphGraph including attribute descriptions in Papyrus. Ease of maintenance since the AAI footprint was lessened, technologies updated, and code coverage increased. | |
| AAF | Not part of the release | Not part of the release | |
| APPC | Not part of the release | Not part of the release | |
| CLAMP | Not part of the release | Not part of the release | |
| CCSDK | CPS | Functional Updates....
| |
| CPS | Functional Updates | Provides ONAP components with the ability to deploy YANG modules at runtime. Provides ONAP components with the ability to persist data defined by YANG models. Provides isolation of data using the dataspace and anchor concepts. Provides shared access to network function CM data cache. | |
| DCAE | Functional Updates
Non-Functional
Bug Fixes
|
| |
| DMaaP | Non-Functional
|
| |
| Documentation | |||
| External API Framework | Functional Updates | Enhanced Service Ordering support for additional Service types. | |
| Holmes | - Non-functional Updates * Migrate Holmes from Cloudify-based deployment to Helm-based deployment. | Unified the deployment manner of ONAP. | |
| Integration | |||
| Logging | Not part of the release | Not part of the release | MSB |
| Modeling | Functional Updates | Enhanced functionality for ETSI Alignment Requirement. | |
| MultiCloud new E2E tests
New IPv4/Ipv6 Daily CI chain | |||
| Logging | Not part of the release | Not part of the release | |
| MSB | Main work is Bug Fixes (in preparation of Istanbul Release) MSB Frankfurt container will be used for the Honolulu release | ||
| Modeling | Functional Updates | REQ-458: Refined Configuration API allows for flexible modification of the CNF configuration. Configuration API allows to create, modify and delete k8s resource templates and it allows their parameterization base on dedicated or inherited from the CNF instance input parameters. REQ-458: Query API allows for the gathering of the filtered out the status of CNF what can be helpful to get precise information for particular resources belonging to the CNF. Query API produces results in the same format as Status API that offers the full set of information about CNF status. REQ-458: HealthCheck API allows for the execution of dedicated healthcheck jobs (similar to helm test operation) that can verify on demand the current status of the CNF. The API can be used also to retrieved the results of healthcheck job execution, which can be extended with Status/Query API | |
| Music | Not part of the release | Not part of the release | |
| CLI | Functional updates - metadata support is added in OCS schema | Metadata helps in annotating given command with context specific information. One of the use case is, in VTP, while modelling test cases, metadata helps in associating the test case with given release name. | OOM | Functional UpdatesAll ONAP components are updated to work properly in IPv4/IPv6 DualStack environment. This is as well tested in Daily CI, on DS networking (REQ-432) | OOF | Functional Updates
Non Functional Updates
Bug fixes
| UUI | Functional UpdatesIncrease the Input ways while creating slicing service, introducing IBN service into UUI Module Use the rectangular grid numbers for a coverage area to specify the area while creating a new slicing service Enhancement of Endpoint design's functionalities | Policy |
| Portal | Not part of the release | Not part of the release | |
| SDN-C | Functional Updates - ElasticSearch image updated to 7.9.x | All SDNC components are running on IPv4/IPv6 DS environment. | SDC | SO | VF-C |
| VID | - Functional Updates * ModernUI has been extended with PNF registration pages (for Service Models leveraging PNF resources) | Users are able to leverage VID GUI to execute PNF PnP use-case orchestration actions, beyond using SO API. (REQ-430) | VNFSDK | Enhanced verification on new certificate signature format. |
| VNFRQTS | Non-functional Updates
|
| |
| VVP | Functional Updates
| Better performance when running OVP Heat based VNF lifecycle validation. | Benchmark | Infrastructure Improvements |
This table shows use case blueprints:
Fix bug: Get VNF Package Artifact endpoint doesn't accept file extensions | Enhanced functionality for ETSI Alignment Requirement. | |
| MultiCloud | Functional Updates | REQ-458: Refined Configuration API allows for flexible modification of the CNF configuration. Configuration API allows to create, modify and delete k8s resource templates and it allows their parameterization base on dedicated or inherited from the CNF instance input parameters. REQ-458: Query API allows for the gathering of the filtered out the status of CNF what can be helpful to get precise information for particular resources belonging to the CNF. Query API produces results in the same format as Status API that offers the full set of information about CNF status. REQ-458: HealthCheck API allows for the execution of dedicated healthcheck jobs (similar to helm test operation) that can verify on demand the current status of the CNF. The API can be used also to retrieved the results of healthcheck job execution, which can be extended with Status/Query API |
| Music | Not part of the release | Not part of the release |
| CLI | Functional updates - metadata support is added in OCS schema | Metadata helps in annotating given command with context specific information. One of the use case is, in VTP, while modelling test cases, metadata helps in associating the test case with given release name. |
| OOM | Functional Updates | All ONAP components are updated to work properly in IPv4/IPv6 DualStack environment. This is as well tested in Daily CI, on DS networking (REQ-432) |
| OOF | Functional Updates
Non Functional Updates
Bug fixes
| |
| UUI | Functional Updates | Increase the Input ways while creating slicing service, introducing IBN service into UUI Module Use the rectangular grid numbers for a coverage area to specify the area while creating a new slicing service Enhancement of Endpoint design's functionalities |
| Policy | Functional Updates
Non-functional Updates
Poc
| |
| Portal | Not part of the release | Not part of the release |
| SDN-C | Functional Updates - ElasticSearch image updated to 7.9.x | All SDNC components are running on IPv4/IPv6 DS environment. |
| SDC | Functional Updates :
Non functional Updates :
| Enhance SDC compliance with ETSI standards, especially in VNF/CNF models,onboarding. Improved package signature checks (SOL007 package security). SDC now allows for un-licensed or externally licensed packages to be onboarded. SDC UI now provides better visibility on artifact distribution status per component Vulnerability and security improvements |
| SO | SO is split to multiple repos and no major change in the existing functionality of the SO has been brought in. SO is now based on Java 11. | Refactoring the internal architecture for betterment of the build time, issue resolution, lesser footprint and production readiness. |
| VF-C | Functional Updates
| |
| VID | - Functional Updates * ModernUI has been extended with PNF registration pages (for Service Models leveraging PNF resources) | Users are able to leverage VID GUI to execute PNF PnP use-case orchestration actions, beyond using SO API. (REQ-430) |
| VNFSDK | Functional Updates - Add support for signature in PCKS7 format under CSAR verification - Add support for PM dictionary validation (pm-dictionary-validate) | Enhanced verification on new certificate signature format. |
| VNFRQTS | Non-functional Updates
|
|
| VVP | Functional Updates
| Better performance when running OVP Heat based VNF lifecycle validation. |
| Benchmark | ||
| Infrastructure Improvements |
This table shows use case blueprints:
| Use Case Blueprint | Key Updates | Benefits | ||
| 5G Service Modeling | The 5G Service Modeling use case: (1) Developed a solution for vendors to deliver 3GPP TS28.540/541 5G NRM driven xNF models to ONAP. (2) The modeling solution has now been integrated into the CPS architecture and has driven the ONAP platform information model evolution. (3) In R8, the architecture was defined for a registry service to expose on-boarded NRM & vendor data to coordinate across use cases. (4) A new resource app Model was introduced to allow for flexible vendor model management in R8. (5) Discussions for onboarding NRM artifacts was explored in R8. | This use case is focused on making sure that ONAP will be able to work with a live 5G gNB base station. Currently, use cases are using simulators. The objective is to try to get everything in place for a live gNB launch. In R8, the Configuration Persistence Service (CPS) PoC has been approved to become a new platform component. Much of the ground work in this project has now been incorporated into CPS. | ||
| OOF SON | In this release, we mainly focused on testing the SON use case functionality with Honolulu release components, in particular the scenario wherein an offline trained ML-model provides additional inputs for Physical Cell Identity (PCI) optimization. | The basic framework for supporting ML-based SON is now supported. The framework also supports easy onboarding, and use of (offline trained) ML-models. This can be further enhanced based on service provider requirements. | ||
E2E Network Slicing | In this release, we have made some functional enhancements to NSMF, RAN NSSMF and Transport NSSMF. Further, various scenario combinations w.r.to Slice instance and slice sub-net instances allocation were tested and several gaps/bugs were addressed particularly for the deployment option in which all 3 NSSMFs are inside ONAP. End-to-end testing of Closed Loop and Intelligent Slicing was also performed. In this release, this use case has started using the CPS component in a limited way for RAN related configuration. | Different deployment options are now supported successfully which enables service providers to have the flexibility of using ONAP providing all Slice Management Functions or to integrate (domain)specific 3rd party NSSMFs with ONAP. | ||
| PNF software upgrade with schema update | In this release, we have made some functional enhancements to PNF software version with schema update procedure. | A schema update in relation to a xNF software upgrades is a routine for network upgrade to support new xNF features, improve efficiency or increase xNF capacity on the field, and to eliminate bugs. This use case provides to ONAP an advantage in orchestrating and managing the Life Cycle of a Network Services in-line with business and service objectives. In Rel 8, the feature will be enhanced with PNF sw version management during sw upgrade procedure. | ||
| CCVPN | In this release, two enhancements have been made. First, we have enhanced Transport Slicing by making it support modifying and reusing the existing TN NSSIs. Secondly, we enhanced CCVPN use-case to support multiple (3+) network domains. | Modification of existing TN NSSI is a required NSI life cycle operation defined by 3GPP. By supporting this operation, all the NSI life cycle operations are now supported by TN NSSMF. The support for multiple network domains are necessary to make the CCVPN use-case more generic and robust. | O-RAN Harmonization, we enhanced CCVPN use-case to support multiple (3+) network domains. | Modification of existing TN NSSI is a required NSI life cycle operation defined by 3GPP. By supporting this operation, all the NSI life cycle operations are now supported by TN NSSMF. The support for multiple network domains are necessary to make the CCVPN use-case more generic and robust. |
| O-RAN Harmonization | stndDefined VES development. | |||
O-RAN A1 Policy functions improved in CCSDK & SDNC Honolulu. Continued the convergence between ONAP and ORAN for the A1 interface. Refer to REQ-457. | The O-RAN A1 interface provides a flexible way for RAN operators to manage wide area RAN network optimization, reducing capex investment needs. Enhanced A1 interface controller and A1 Policy capabilities are now usable by any service provider deploying and using ONAP. 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 | ||||
| CNFO | Enhanced Day-2 operations for CNF (REQ-458) - K8s Plugin - Refined Configuration API - K8s Plugin - New Query API - K8s Plugin - New HealthCheck API - Native support for above mentioned in CDS | New functionalities deliver functions expose a set of mechanism for building custom functionality logic required for verification of the status of CNF after its deploymentits deployment. Now we can verify the status of CNF resources and we can implement properly pos deployment actions base on their state. Also, we expose a powerful mechanism for reconfiguration of the CNF or for its customization after the instantiation that in particular can be used for upgrading the instance of the CNF. | CNFO | THe configurations mechanism allows to instantiate or modify existing CNF resources and will utilize Day 0 information of the CNF as a base. |
Here is a list of a few subcommittees (use-case, architecture, security), OVP, and other activities.
...
| S3P Activity | Key Updates | Benefits |
| Stability | Leveraging of basic_* test collection to perform long duration tests | Detect possible memory leaks linked to the core components |
| Scalability | ||
| Performance | ||
| Manageability | ||
| Resilience | Basic tests (restart of a worker node) | |
| Usability | ||
| Code Footprint Reduction |
...