IntenDeadline for contribution by
This
...
table shows use case blueprints:
Use Case Blueprint | Sub-Blueprint |
Key Updates | Benefits |
Functional
- Model updates as part of CCVPN Transport Slicing Feature
- Model updates as part of xNF Software Upgrade feature
- Model updates as part of Multi-tenancy
- Updates to SDC model parsing to support Bulk PM/PM Data Control Extension & E2E Network Slicing features
- Configurable ability to control concurrency locking
- Configurable ability to enforce ownership of owning entity on pnf crud interactions (Multi-tenancy poc)
- Enhancements to the model based on physical inventory
- Support for nested json formatted responses using the as-tree=true parameter for traversal mS calls
Non-functional
- Updated microservices to run as non-root
- Spring boot 2 upgrades to our microservices
- Enhanced logging
- Added limits to aai pods
- Update mS based on license scan findings
- mS dependencies updated to work towards upgrading to Java 11 in future release
Deprecation Notice
- ESR Server is retired
- ESR GUI is retired
- AAI Sparky UI is not supported in Guilin nor is its supporting mS data-router, search-data-service, or elastic. Targeted for retirement in Honolulu
- Ability to support additional use cases
- Greater architecture flexibility
- OOM helm charts refactoring:
- Name standardization
- Automated certificate generation
- New repository added for ORAN-related work to allow better alignment with ORAN release schedule
- Support to running Servlce Logic Interpreter as a springboot-based microservice, outside of OpenDaylight karaf container.
- Major OpenDaylight release update : Sodium SR4
- Completed migration from Java 8 → Java 11
- Python 3.8 support
- Integration with ORAN
- Looser coupling between CCSDK and OpenDaylight so that downstream users of ONAP are not tightly coupled to a specific OpenDaylight version.
Functional
- Support for ONAP & 3GPP/ORAN alignment using StdDefined VES notification in DCAE
- Self-serve control loop enhancements through MOD (NiFi)
- External X.509 certificate from CMPv2 server integration for DCAE collectors (VES & DFC)
- VESCollector optimization
- Cloudify Container optimization (new base image plugins loaded in-container)
- MOD/Runtime – Enable configuration for dynamic topic support
- Dashboard UI optimization
- PMSH Enhancements (DCAEGEN2-2164)
Non-Functional
- K8S v1.17 support through DCAE Cloudify K8S plugins
- Python 3.8 support enabled for several DCAE components (Heartbeat mS, PMSH mS, MOD/DistriubtorAPI mS, MOD/OnboardingAPI mS, Policy Library; aligned to ONAP common base image
- Stdout log compliance
- Completed Java 11 upgrade (RESTConf, PM-Mapper, DFC, VES-Mapper, SON-handler, TCA-gen2, DL-Feeder, InventoryAPI, ServiceChangeHandler, MOD/RuntimeAPI, MOD/Bp-gen)
Security
- Hardcoded password removed and managed dynamically through K8S secret (Cloudify, Bootstrap, DeploymentHandler, Dashboard)
- All Vulnerability updates/fixes completed
- Best practice compliance - Containers must have no more than one main process
Performance/benchmarking
- VESCollector
- HV-VESCollector
New DCAE Microservice
- DL – Data Exposure Service (DES)
- Slice-Analysis MS
(Both services are used for realizing 5g/Slicing usecase in Guilin)
Deprecation Notice
- TCA-CDAP (replaced by TCA-gen2)
- Integration with other opensource projects such as ORAN and standards body such as 3GPP
- Usability improvement through Dashboard and MOD enhancements
- DCAE Orchestration support on K8S 1.15 and upward
- Operator specific external certificate support via CMPv2
- Non-functional & Security features implemented improves upon S3P goals
- Support for additional usecases through new Microservices
- Updated to Java 11 on some components
- Updated few dependencies related to security vulnerabilities
Documentation validation and improvements in the following areas:
- Setting Up ONAP
- ONAP on HA Kubernetes Cluster
- OOM Quickstart Guide
- Instructions for HA Kubernetes cluster on AWS - Platform Operations
- oom_user_guide
- Robot Framework
- Backup and Restore
- Logging & Analytics - User Guides
- SDC Design & Run Time activities
- Tutorial (vFW)
- Control loop design & run time activities
- Tutorial (vFWCL)
Functional :
- Enhancements made to Service Order API TMF 641 to support Network Slice Activation/Deactivation and Termination
- Added support for Service Catalog and Ordering Management of macro mode type Service Specifications i.e. new support for when SDC instantiationType = macro
- New support added to onboard third party Service Specifications via the Service Catalog TMF 633 API
Non-Functional :
- Dependency updates
- Updated Helm charts to add container limits
- fixed containers that were running as root
- The benefit of supporting Network Slicing Activation/Deactivation, Macro mode Services and third party Service Specifications is that the External API Framework now can expose these ONAP features externally with Standard based APIs.
- Updated to Java 11
- Changed the base image to the official ONAP base image.
- Updated some dependencies.
- Enhanced to support MDONS close loop.
- Add new Infrastucture CI tests
- Certificate expiration date
- Nodeports SSL verification
- Nodeport connection verification
- Refactoring of infrastructure helm test
- Refactoring of infrastructure k8s tests to get a cluster Snapshot after the installation and after the test execution including accurate logs
- Update end to end use cases inluded in CI tests
- pnf registration
- 5gBulkpm
- Add E2E integration tests to cover new stndDefined VES events (hvves)
- CMVPv2 (on-going)
- Add new tests aligned with Seccom requirements
- Tests that the python ans java versions of the upstream components used in ONAP are aligned with Seccom (ongoing)
- Automaric Verification that pod limits are defined
- Manuel tests on licence in the pods (tern)
- ONAP Python SDK integrated in test-suites (deprecation of onap-tests framework), including the support of GR API, macro mode. New use cases added to CI (pythonsdk-tests) : Basic_vm, basic_network, basic_cnf, basic_clamp
- Add DCAE tls init container to robot pod for cert secure communication with DCAE application
- Improve PNF simulator (use strict hostname checking, read passwords to stores from files)
- Reinsourcing of xtesting docker building in KF repo ans CI chaînes)
- Hosting if all CI results in KF backend (daily, gating)
- Update java and python base images
- Labs update with new approach to redeploy on weekly basis
- WindRiver (full performance audit, reinstallation needed after Guilin))
- Azure
Full kanban: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=221
Adoption of pythonsdk leads to more trust in the tests executed in CI. The goal is to test ONAP (not only the use cases supported by ONAP) and get a good coverage of the components.
More tests to improve global ONAP quality and detect problems as early as possible (eg certifiate expiration date)
More security tests
Functional :
- Support SDC-ETSI catalog manager direct interface
Non Functionals :
- Optimize docker image
- Dependency updates
- Migration to the public mariadb
- Eliminate mandatory dependence on MSB
Functional:
- Enable Helm Chart support in MultiCloud artifactbroker
Non Functionals:
- Update to java 11
Enable CNF orchestration with artifacts in native helm charts
Functional :
- Auto-discovery feature is enabled in profile
- profile management is added into ocomp feature to support ONAP environment configuration
Non Functionals :
- Updated to Java 11
- Vulnerability fix is improved
Functional
- Storage class support
- Ingress support
- Automation of certificates for components
Non-Functional
- helm v2/v3 support
- kubernetes 1.15 → 1.19 support
- helm chart size reduction
Deprecation Notice
- nfs share will not be supported in next release
- Support of CaaS offer such as AKS (OOM is tested against it)
- More reliable deployments
Functional
- Optimization Apps required for E2E Network Slicing (NSI Selection, NSSI Selection, NSI/NSSI Termination)
- Improvements in SON app to support machine learning based inputs
- Support for Inter-domain route optimization
- Improvements in HAS optimizer to support generic objective functions
Non-Functional
- All python applications are upgraded to python 3.8
- Automatic certification intialization in helm charts
- Improved code coverage
- Code quality improvements
- Security vulnerability fixes
- With the introduction of generic objective function in HAS, New objectives can be designed directly using policy instances. We can support more use cases without much code changes.
- Improved security and stability of the system.
Functional :
- Transport 5G Slicing: Adding endpoint parameters to the Slicing Tasks portal and adapting other parameters to support the transport of An and Cn region
- E2E Network Slicing: Supporting KPI Monitoring data shown to users and also supporting standard API interface for KPI monitoring, and KPI data reporting to tenant/operator
- Remove modules that are no longer used
Non Functionals :
- Updated to Java 11
- Dependency updates
- Upgrade HTTPS certificate
- Support use case
- Optimize image, easier to deploy
- Make system safer
- New Guard Filter added to existing suite of Guard Policies
- New Matchable Policy Type to readily support on-boarding policy enforceable applications by the users of ONAP
- Policy Lifecycle & Administration API: Query/Delete by policy name & version without policy type
- Apex-PDP enhancements:
- Support multiple event & response types coming from a single endpoint
- Standalone installation now supports Tosca-based policies
- Legacy policy format has been removed
- Support chaining/handling of gRPC failure responses
- Policy Distribution: HPA decoders & related classes have been removed
- Policy Engine: Deprecated
- Actor Model: Support various use cases and provide more flexibility to Policy Designers
- Multi-tenancy: Basic initial support using the existing features
- E2E Network Slicing: Added ModifyNSSI operation to SO actor
- Consolidated health check: Indicate failure if there aren’t enough PDPs registered
- Legacy operational policies: Removed from all components
- Docker images: All based on alpine yielding a smaller footprint
- Kubernetes integration:
- All components return with non-zero exit code in case of application failure
- All components log to standard out (i.e., k8s logs) by default
- Continue to write log files inside individual pods, as well
- OOM helm charts refactoring:
- Name standardization
- Automated certificate generation
- Resource section added to components
- Greater flexibility for application-specific use
- Cleaner integration with Kubernetes
Non Functional:
- Make Portal Database run as non-root - REQ-362
- Cassandra container is the only one pending
- Access Portal Database using non-root user - REQ-358
- Hard Coded passwords Removal - REQ-361
- portal-app, portal-sdk, portal-db
- Updating Vulnerable direct dependencies - REQ-323
- All except for Portal's Spring upgrade completed
- Upgrade Logging specification
- Portal and SDK
Others:
- Released 3.3.0 Version of SDK
- Enhancements to Reporting Feature in SDK
Deprecation Notice:
- Removed Zookeeper Dependency
The Non functional features implemented will improve the security and stability of the Application.
The enhancements to the Reporting feature of SDK adds new capabilities like Server side pagination, dashboards etc and improves the performance of the reporting engine.
The new 3.3.0 Version of SDK comes with complete Angular 7 support and tag libraries/ templates that can be used by for rapid UI application development and addresses vulnerable direct dependencies.
- Major OpenDaylight release update : Sodium SR4
- Completed migration from Java 8 → Java 11
- Python 3.8 support
- Support for MDONS Extension
Functional :
Onboard new HELM type for CNF orchestration
ETSI alignment improvements
Test topology Auto design
Non Functionals :
- Update to Java11
- Update to Python 3
- auto certificate generation and retrieval
- Dependency updates
Deprecation notice :
DCAE-DS plugin is now deprecated (replaced by DCAE-MOD)
Native HELM package onboarding & mapping to SDC Data model for CNF distribution and orchestration.
Improved compliance & support for ETSI SOL004 & SOL007 (Network Service Descriptor & Package)
Allows re using an existing service test template, to speed up testing in multiple environments
Improved security, update of base frameworks, ease of deployment, closed vulnerabilities
Reduced foot print
Functional :
Functional :
- Improve Instance storage function
- Remove components which are no longer used or maintained
Non Functionals :
- Updated to Java 11
- Optimize docker image
- Dependency updates
- Increase code coverage
Support use case
Optimize image, easier to deploy
Functional :
- Audit Info Screen Enhancements
- Pause VF Modules Instantiation
- Change Mangement PNF Improvements.
Non Functionals :
- Updated to Java 11
- Optimize docker image
- Dependency updates
- Increase code coverage
Functional:
- Robot integration is enabled in VTP
- cnf conformance is integrated in VTP for performing CNF conformance check
- Scenario management REST API is supported in VTP for dynamic test management
- Fix broken VNF Market UI and Improved VNF Market Rest API
- Add a few validation rules for VNF/PNF
R-972082, R-130206, R-816745
Non Functionals :
- Updated to Java 11
- Optimized the docker image
- Dependency updates
- Auto certificate generation
- Increase code coverage
- Update official documentation
- Activate CSITs for validation and refrepo project
- Vulnerability fix is improved
- New validation rules for PNF/VNF
- Reduced size of refrepo image
- All functions of VNFSDK are up&run
- Updated documentation
- CSITs are active
Non Functionals
- Published updated VNF Event Streaming Listener specification 7.2 with support for accepting events defined by external defined standards bodies such as 3GPP
Functional :
- Bug fixes and updates to align w/ updates to VNFRQTs VNF Heat Template requirements ("R-20453", "R-26351", "R-26506", "R-681859")
- Updates to test-engine/onap-client for executing OVP VNF Life-Cycle Instantiation badging.
This table shows use case blueprints:
...
First steps towards realizing Machine Learning (ML) based SON. Offline trained ML model used to provide additional inputs for PCI optimization. Provides interface for fetching PM data to determine additional inputs for optimization related to SON.
...
Benefits of OOF SON use case: A modular and generic control-loop based framework to realize various SON functions. The interfaces and network models are aligned with 3GPP and O-RAN.
Increment in Guilin
Enables onboarding ML models to realize ML-based SON use cases. This facilitates use of ML to determine the optimization model to be used, and to provide additional inputs for the optimization engine.
...
This use case incorporated the 5G RAN Wireless Network Resource Model (NRM) into ONAP.
The 5G NRM is defined from the 3GPP standards 3GPP TS28.540 & 3GPP TS28.541 which builds upon the FNIM, UIM specified in 3GPP TS28.620 and TS28.622
The 5G NRM is a common vendor agnostic network model inspired from the standards which provides a common basis for all wireless vendors to have a set of parameters that are in common across the vendor so that service providers have a more uniform set of objects, parameters and models to represent a wireless network.
...
Development of support for Standard Defined (stndDefined) VES Event. This new domain of a VES event would allow ONAP to support many more standards based & standards defined messages.
It opens the possibility for ONAP to support a wide variety of messaging from Optical, Wireless, Core and Transport standards.
"stndDefined" is a new VES domain. And it is described in the VES 7.2 specification VES 7.2 and also in the readthedocs. It also introduces a new field "namespace" to be published onto the DMaaP bus which allows for internal routing of the information coming from xNFs. For example 3GPP_Configuration would indicate a CM type information coming from an xNF.
...
- Added support for standardized A1 protocol (O-RAN A1-AP v1.1) - now supports multiple A1 versions - and new versions can be added easily
- Added A1 Policy Management Service
- Query A1 Policy Types in near-RT-RICs
- Create/Query/Update/Delete A1 Policy Instances in near-RT-RICs
- Query Status for A1 Policy Instances
- Maintain transient cache of RAN’s A1 Policy information
- Added support for multiple near-RT-RICs (with multi-version support)
- Added Unified REST & DMaaP NBI for A1 Policy Management
- Add support for TLS/HTTPS REST for southbound A1 interfaces (and NBIs)
- Converged ONAP & O-RAN-SC A1 Adapter/Controller functions in ONAP SDNC/CCSDK
...
CCSDK/SDNC now supports managing A1 Policies, multiple A1 targets in the RAN, multi-version support for different A1 targets, converged DMaaP & REST interfaces, and secure communication (to/from RAN and to/from ONAP functions.
Functionality is now available for use in further use cases in ONAP H+.
Functionality available for standalone use, or in a larger ONAP deployment.
Available for use in O-RAN OSC.
...
- Realization of RAN, Core and Transport NSSMFs within ONAP, supporting the respective NSSI creation, activation, deactivation and termination. RAN and Core NSSMF interfaces are aligned with 3GPP, while Transport NSSMF's interfaces are aligned with IETF TSCi.
- Supporting connectivity to an external RAN NSSMF outside ONAP.
- Basic model provisioning including NSST, sliceProfiles and E2E connection information.
- Support of a simple Closed Loop scenario involving RAN domain
- Support of a simple offline trained ML model for Intelligent Slicing in the RAN domain
- First steps towards KPI monitoring by the operator/slice tenant
- First steps towards Core NF configuration
- Core NF Simulator and RAN NF Simulator enhancement
...
- Enables different deployment options and greater interoperability of Slice Management functions through a loosely-coupled architecture supporting standards-based interfaces.
- Supports 2 different deployment configurations for RAN Slicing functionality.
- Enables new Closed Loop functionalities to be realized with the existing framework.
- Enables ONAP to directly set up and configure Network Functions.
...
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 6 (5G / Bulk PM / PM Control - REQ-129). Planned enhancements for Rel 7 intend to further increase the capability and the dynamicity of this feature.
...
PM control is a critical business function because it is vital to enable the PM data collection in ONAP
...
- Support 5G slice creation by intent based network,
Use intent based network to create 5G slice.
Support Intent instance LCM operations,provide functions for intent instance create, terminate
- Support User intent idendify
Support User Intent Translation
- Support User Intent Decision
...
- It simplifies the complexity for users to activate 5G slices
- Improves the efficiency of service activation
- Improves the user experience of the system
...
Development of Building Blocks in SO to support PNF Plug and Play Flow.
Migration of BPMN Workflow to Building Blocks (BB). These include the "AssignPnfBB", "WaitForPnfReadyBB", "ConfigAssignPnfBB" and "ConfigDeployPnfBB", "ActivatePnfBB". Note: that in R8 will see the development of the VID work to compliment the SO BB work completed in R7.
Modeling analysis of Geolocation and Place objects driven from RFC6225 and MEF TM GB922 standards. Model contributions have been approved.
...
Internal SO development to streamline execution of PNF Plug and Play.
Migration of BPMN Workflow to Building Blocks allows for much more streamlined management of SO workflow execution.
...
Enhanced entire package security
Aligned now with ETSI SOL004 standrads.
...
Deployment and orchestration of new services over CNFs, VNFs and PNFs in a model and software driven way simplifies the network management. Enables operators and service providers to manage the Life Cycle of a Network Service. Assuring continuity of operation of services is crucial for production and carrier grade environments. The actualization or upgrades of software and in consequence required changes in the service model is a natural part of service instance life cycle. Without the support of ONAP service update with schema change, service life cycle management by ONAP can be very difficult which can impact the quality and continuity of services.
...
5G | OOF SON (PCI) | First steps towards realizing Machine Learning (ML) based SON. Offline trained ML model used to provide additional inputs for PCI optimization. Provides interface for fetching PM data to determine additional inputs for optimization related to SON. | Benefits of OOF SON use case: A modular and generic control-loop based framework to realize various SON functions. The interfaces and network models are aligned with 3GPP and O-RAN. Increment in Guilin Enables onboarding ML models to realize ML-based SON use cases. This facilitates use of ML to determine the optimization model to be used, and to provide additional inputs for the optimization engine. |
Service Modeling & Definition | This use case incorporated the 5G RAN Wireless Network Resource Model (NRM) into ONAP. The 5G NRM is defined from the 3GPP standards 3GPP TS28.540 & 3GPP TS28.541 which builds upon the FNIM, UIM specified in 3GPP TS28.620 and TS28.622 The 5G NRM is a common vendor agnostic network model inspired from the standards which provides a common basis for all wireless vendors to have a set of parameters that are in common across the vendor so that service providers have a more uniform set of objects, parameters and models to represent a wireless network. | Allows for RAN Wireless vendors to use standardized 3GPP support TS28.540/TS28.541 5G NRM parameters | |
Standards Alignment: StndDefined VES Event | Development of support for Standard Defined (stndDefined) VES Event. This new domain of a VES event would allow ONAP to support many more standards based & standards defined messages. It opens the possibility for ONAP to support a wide variety of messaging from Optical, Wireless, Core and Transport standards. "stndDefined" is a new VES domain. And it is described in the VES 7.2 specification VES 7.2 and also in the readthedocs. It also introduces a new field "namespace" to be published onto the DMaaP bus which allows for internal routing of the information coming from xNFs. For example 3GPP_Configuration would indicate a CM type information coming from an xNF. | Allows for Standards Bodies such as 3GPP (RAN Wireless) alignment and support of messaging from xNF messages defined by standards to be compatible with ONAP | |
Standards Alignment: A1 |
| CCSDK/SDNC now supports managing A1 Policies, multiple A1 targets in the RAN, multi-version support for different A1 targets, converged DMaaP & REST interfaces, and secure communication (to/from RAN and to/from ONAP functions. Functionality is now available for use in further use cases in ONAP H+. Functionality available for standalone use, or in a larger ONAP deployment. Available for use in O-RAN OSC. | |
5G NRM (CM) | (No Updates in R7) | ||
E2E Network Slicing |
|
| |
Bulk PM: PM Control | 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 6 (5G / Bulk PM / PM Control - REQ-129). Planned enhancements for Rel 7 intend to further increase the capability and the dynamicity of this feature. | PM control is a critical business function because it is vital to enable the PM data collection in ONAP | |
Intent Based Network |
|
| |
PNF | PNF Plug-and-Play | Development of Building Blocks in SO to support PNF Plug and Play Flow. Migration of BPMN Workflow to Building Blocks (BB). These include the "AssignPnfBB", "WaitForPnfReadyBB", "ConfigAssignPnfBB" and "ConfigDeployPnfBB", "ActivatePnfBB". Note: that in R8 will see the development of the VID work to compliment the SO BB work completed in R7. Modeling analysis of Geolocation and Place objects driven from RFC6225 and MEF TM GB922 standards. Model contributions have been approved. | Internal SO development to streamline execution of PNF Plug and Play. Migration of BPMN Workflow to Building Blocks allows for much more streamlined management of SO workflow execution. |
Onboarding/Pre-onboarding | Enhanced package security ETSI SOL004 option 2 security implemented | Enhanced entire package security Aligned now with ETSI SOL004 standrads. | |
PNF software upgrade | 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. | Deployment and orchestration of new services over CNFs, VNFs and PNFs in a model and software driven way simplifies the network management. Enables operators and service providers to manage the Life Cycle of a Network Service. Assuring continuity of operation of services is crucial for production and carrier grade environments. The actualization or upgrades of software and in consequence required changes in the service model is a natural part of service instance life cycle. Without the support of ONAP service update with schema change, service life cycle management by ONAP can be very difficult which can impact the quality and continuity of services. | |
Configuration Persistence Service (CPS) | (Note this has been renamed to Configuration Persistence Service) CPS PROOF OF CONCEPT Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS. The PoC has:
CPS STAND ALONE PROJECT (in R8) Presented Project proposal at architecture sub-committee and TSC: Configuration Persistence Service Project in R7 timeframe. Is has been approved to be a stand-alone project in R8 (Honolulu Release) STATE MANAGEMENT POC State Management PoC was created to store the current state of the network elements in a network. | BENEFITS OF CPS CPS introduces a data layer into ONAP to store and manage Network Element Data. CPS provides a centralized, single, persistent data across all vendors. It allows for the data to be exposed such that different upper level applications (e.g. SON, orchestration, LCM functions) can use CPS data. The CPS is real-time and up-to-date. It facilitates the push & pull of configuration data that is policy driven. CPS is an embodiment of "Golden configurations" which is a solution for an up-to-date unified configuration database sending configuration changes. Before CPS existed, service providers have to struggle with many disparate databases which begs to be harmonized and integrated. BENEFITS OF CPS PROOF OF CONCEPT Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS. BENEFITS OF CPS AS STAND ALONE PROJECT CPS as a stand-alone project in R8 Honolulu will allow CPS to have its own stand-alone repository and facilitate component interaction to CPS. BENEFITS OF STATE MANAGEMENT POC State information facilitates the recovery of failed assets and tracking the states of elements in a service provider's network. | |
CMPv2 | CMPv2 is a standardized certificate based exchange protocol to introduced enhanced security in ONAP. It allows for intra-component security and affect many components. CMP is a protocol for X.509 digital certificate management in a PKI described in RFC4210. And is one of the protocols used for Certificate Request Message Format (CRMF) described in RFC4211. | CMPv2 introduced standardized certificate exchange security into ONAP. | |
xNF License Management | xNF Licensing Management enhancements allows for ONAP to work with an external licensing service. Link to high level description of the solution. Integrated flow into Plug and Play Use Case. 5G - PNF Plug and Play | Possibility to use external licensing service allows for greater interoperability between service providers & vendors, and enables various types of xNF commercial licensing models: simpler, more complex, vendor specific and operator specific models. | |
MDONS Extension | Improvements on MDONS use-case with additional features
| MDONS blueprint is enhanced with additional functionality that enables policy-driven automated service operations. The optimization framework facilitates improved service lifecycle management across cross-carrier optical domains enabling vendor interoperability. | |
ETSI Alignment | The following ETSI-Alignment enhancements are made:
| ONAP supports SOL007 NS design which enables hierarchical orchestration by conforming ETSI NS and VNF standards. ONAP NS and NsVirtualLink are now conforming to ETSI standards. SO NFVO enables plugin-based extension of NFVO functions on top of default NFVO functions. |
Here is a list of a few subcommittees (use-case, architecture, security), OVP, and other activities.
Subcommittee | Key Updates | Benefits |
Arch | ||
Cloud Native | For Guilin release there are introduced key changes that deployment of CNFs with ONAP more operational and they enable Day-0/1 CNF operations. The changes include:
| The introduced changes bring the following benefits:
|
Control Loop | The Control Loop sub committee led the functional requirement to add a new Filter Guard Policy Type. In addition, the subcommittee ensured that the Native Policy Type work developed in Frankfurt was fully tested through the CLAMP interface. The sub committee continues to support the DCAE Project Self-Serve control loop enhancements Proof-of-Concept. The PoC made improvements to MOD (NiFi) and configuration for dynamic topic support. A new Proof-of-Concept was started by the subcommittee to define TOSCA-Based Control Loops. This work was demonstrated at the fall LFN Technical Conference. | The new Filter Guard Policy Type is another guard policy available for ONAP users to use in addition to the others that have been available since Dublin. This allows filters to build more flexible constraints to both whitelist and/or blacklist vnf types, specific vnf id's, services, etc. In defining a TOSCA specification for Control loops, users can now encapsulate all the details of a control loop within one specification. These specifications are re-usable. CLAMP will eventually be able to be fed a TOSCA specification, and with minimal effort be able to configure and deploy a control loop into the runtime environment. |
Modeling | The modeling subcommittee updates the ONAP VNFD model to align with ETSI NFV IFA011 v2.7.1, supporting key features like virtual ip, VNF exposed interface, etc. The subcommittee also adds a new model for location information. Taking consideration of multiple existing standards, including ETSI NFV SOL001, RFC4776 and RFC6225, the new model enables an entity to provide its geographical location information. | Update of the VNFD model to the latest ETSI NFV spec allows ONAP to incooperate new features defined in standards. The new locations model enables entity such as PNF to provide its geographical information, allowing further scheduling and optimization procedures. |
ONAP Security Coordination | The subcommittee continued efforts on upgrading packages to the SECCOM recommended versions as well as upgrading the java (v8 → v11) and python (v2.7 → 3.8) versions. CII Badging information: 1) https://wiki.onap.org/display/Meetings/PTL+2020-11-16?preview=%2F92998580%2F93000904%2FCelebrate-CII-Badging.pdf | Progress with package and Java, Python upgrades Progress with decrease of pods running as root Migration towards https and default use of https |
Open Lab | N/A | |
Requirements | The existing use cases and requirements were significantly extended and functionality was added. The major additions include PNF support extensions, cloud native support extensions, network slicing support extensions, and ETSI SOL1, SOL3, SOL5, SOL5 and SOL7 enrichment | Network slicing would be able to deploy in 5G by using ONAP, with internal nd external NSSMFs, CSMF and NSMF; any combination of PNF, VNF, CNF would be applicable for any use case deployment will be enabled by standardized ETSI SOL functionalities |
VNF Validation Subcommittee and OVP | ||
Other Activities | ||
Controller Design Studio (CDS) |
|
|
K8s Plugin |
|
|
(Note this has been renamed to Configuration Persistence Service)
CPS PROOF OF CONCEPT
Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS.
The PoC has:
- Demonstrated write/read operations for YANG data fragments using CPS and store them in a generic DB with a very simple generic schema
- Demonstrated ability to deploy / upgrade YANG models at run-time
- Demonstrated CPS behavior driven by YANG models
- Provided an architecture vision and roadmap for a target architecture, supported use cases, non-functional requirements towards an ONAP Project
- Got early performance indication for querying the generic schema
- Architectural decisions and issues were resolved through regular team meetings: Issues decisions and assumptions
CPS STAND ALONE PROJECT (in R8)
Presented Project proposal at architecture sub-committee and TSC: Configuration Persistence Service Project in R7 timeframe. Is has been approved to be a stand-alone project in R8 (Honolulu Release)
STATE MANAGEMENT POC
State Management PoC was created to store the current state of the network elements in a network.
BENEFITS OF CPS
CPS introduces a data layer into ONAP to store and manage Network Element Data. CPS provides a centralized, single, persistent data across all vendors. It allows for the data to be exposed such that different upper level applications (e.g. SON, orchestration, LCM functions) can use CPS data. The CPS is real-time and up-to-date. It facilitates the push & pull of configuration data that is policy driven. CPS is an embodiment of "Golden configurations" which is a solution for an up-to-date unified configuration database sending configuration changes. Before CPS existed, service providers have to struggle with many disparate databases which begs to be harmonized and integrated.
BENEFITS OF CPS PROOF OF CONCEPT
Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS.
BENEFITS OF CPS AS STAND ALONE PROJECT
CPS as a stand-alone project in R8 Honolulu will allow CPS to have its own stand-alone repository and facilitate component interaction to CPS.
BENEFITS OF STATE MANAGEMENT POC
State information facilitates the recovery of failed assets and tracking the states of elements in a service provider's network.
...
CMPv2 is a standardized certificate based exchange protocol to introduced enhanced security in ONAP. It allows for intra-component security and affect many components.
CMP is a protocol for X.509 digital certificate management in a PKI described in RFC4210. And is one of the protocols used for Certificate Request Message Format (CRMF) described in RFC4211.
...
xNF Licensing Management enhancements allows for ONAP to work with an external licensing service. Link to high level description of the solution.
Integrated flow into Plug and Play Use Case. 5G - PNF Plug and Play
...
Possibility to use external licensing service allows for greater interoperability between service providers & vendors, and enables various types of xNF commercial licensing models: simpler, more complex, vendor specific and operator specific models.
...
Improvements on MDONS use-case with additional features
- Support for Inter Domain Link (IDL)/Path Optimization for OTN links across multiple optical domains
- Added support for asynchronous response handling to enable OpenROADM based OTN service creation
- Incorporated support for closed loop operations
...
MDONS blueprint is enhanced with additional functionality that enables policy-driven automated service operations. The optimization framework facilitates improved service lifecycle management across cross-carrier optical domains enabling vendor interoperability.
...
The following ETSI-Alignment enhancements are made:
- ETSI SOL 2.5.1/2.7.1 support
- SDC enhancements
- SOL007 NS package design
- SOL004 VNF/PNF package onboarding validation
- SOL001 NSD mapping to SDC AID DM
- Addition of SO NFVO for hierarchical orchestration, as one of the NFVO options
- Support SOL005 NBI and SOL003 SBI
- NS LCM orchestration support
- SOL003 Adapter enhancements for SO NFVO
- ETSI Catalog Manager enhancements for direct interface between SDC and ETSI Catalog Manager
...
ONAP supports SOL007 NS design which enables hierarchical orchestration by conforming ETSI NS and VNF standards.
ONAP NS and NsVirtualLink are now conforming to ETSI standards.
SO NFVO enables plugin-based extension of NFVO functions on top of default NFVO functions.
Here is a list of a few subcommittees (use-case, architecture, security), OVP, and other activities.
...
For Guilin release there are introduced key changes that deployment of CNFs with ONAP more operational and they enable Day-0/1 CNF operations. The changes include:
- Native distribution of Helm package from SDC
- Native support for Helm package enrichment in Controller Design Studio.
- Native orchestration of Helm package in the SO
- Exposure of APIs for monitoring of resources deployed on K8s cluster
...
The introduced changes bring following benefits:
- Native distribution of Helm package in SDC enabled native orchestration of CNF in SO and allows addition of Helm validation or Helm properties recognition in the future
- Native support for Helm package enrichment in CDS allows flexible generation of Helm override parameters and enables easy modification of on-boarded Helm package for each service instance. It is very important for deployment of complex 5G Core CNFs that require heavy customization for each deployed service instance.
- Native orchestration of Helm package in the SO enables further synchronization of ONAP inventory with information from k8s cluster or easier execution of Day-2 operations on CNFs
- Exposure of APIs for monitoring of resources deployed on K8s cluster enables verification of status of k8s resources deployed in k8s cluster. Currently such API can be easily integrated with CNF blueprint created for Controller Design Studio.
...
The Control Loop sub committee led the functional requirement to add a new Filter Guard Policy Type. In addition, the subcommittee ensured that the Native Policy Type work developed in Frankfurt was fully tested through the CLAMP interface.
The sub committee continues to support the DCAE Project Self-Serve control loop enhancements Proof-of-Concept. The PoC made improvements to MOD (NiFi) and configuration for dynamic topic support.
A new Proof-of-Concept was started by the subcommittee to define TOSCA-Based Control Loops. This work was demonstrated at the fall LFN Technical Conference.
...
The new Filter Guard Policy Type is another guard policy available for ONAP users to use in addition to the others that have been available since Dublin. This allows filters to build more flexible constraints to both whitelist and/or blacklist vnf types, specific vnf id's, services, etc.
In defining a TOSCA specification for Control loops, users can now encapsulate all the details of a control loop within one specification. These specifications are re-usable. CLAMP will eventually be able to be fed a TOSCA specification, and with minimal effort be able to configure and deploy a control loop into the runtime environment.
...
The modeling subcommittee updates the ONAP VNFD model to align with ETSI NFV IFA011 v2.7.1, supporting key features like virtual ip, VNF exposed interface, etc.
The subcommittee also adds a new model for location information. Taking consideration of multiple existing standards, including ETSI NFV SOL001, RFC4776 and RFC6225, the new model enables an entity to provide its geographical location information.
...
Update of the VNFD model to the latest ETSI NFV spec allows ONAP to incooperate new features defined in standards.
The new locations model enables entity such as PNF to provide its geographical information, allowing further scheduling and optimization procedures.
...
Open Lab
...
Controller Design Studio (CDS)
...
Finally, here is a list of S3P activities (security, documentation covered above)
S3P Activity | Key Updates | Benefits | Stability | Scalability | Performance | Manageability | Benefits | |
Stability | N/A - See Guilin Release Platform Maturity | |||||||
Scalability | N/A - See Guilin Release Platform Maturity | |||||||
Performance | N/A - See Guilin Release Platform Maturity | |||||||
Manageability | N/A - See Guilin Release Platform Maturity | |||||||
Resilience | N/A - See Guilin Release Platform Maturity | |||||||
Usability | N/A - See Guilin Release Platform Maturity | |||||||
Code Footprint Reduction | N/A - See Guilin Release Platform Maturity | Resilience | Usability | Code Footprint Reduction |