Honolulu release - non-functional requirements proposed list
- Alla.Goldner
- Olivier Phenix
- damian.nowak
- 1 SUPPORT FOR IPv4/IPv6 DUAL STACK DEPLOYMENTS IN R8 (REQ-432)
- 2 CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES (REQ-439)
- 3 COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) (REQ-438)
- 4 COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) (REQ-437)
- 5 LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA (REQ-441)
- 6 COMPLETION OF HELM MIGRATION (v2 → v3) (REQ-442)
- 7 CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL (REQ-443)
- 8 Support for the Multi Tenancy in ONAP (REQ-463)
- 9 Identification of events that compromise the ONAP system (REQ-464)
SUPPORT FOR IPv4/IPv6 DUAL STACK DEPLOYMENTS IN R8 (REQ-432)
R8 PRESENTATION:
ITEM | DETAILS |
R8 Presentation | |
Recording mp4 | |
Audio only |
Key Contacts - @damian.nowak @Martin Skorupski
Executive Summary - Majority of LTE and 5G RAN networks today are running exclusively on IPv6. IPv4/IPv6 dual stack solution for ONAP is needed to enable integration.
There is also a requirement to register the NetConf network devices in SDN-R controller, using IPv6 networking.
The target for Honolulu is to update all ONAP components, which do not install/execute properly in IPv4/IPv6 dual stack environment.
As of today (B10/2020), the following components are affected:
SDN-R Elastic Search module
Portal MariaDB database
SDC/AAI Cassandra database
DCAE - CFY Plugin - support exposing services using IPv6
This might not be a full, comprehensive list.
Additionally, we`d like to make sure, that ONAP CI/Gating environment is running RKE-Kubernetes 1.18.x (at least).
Business Impact - Improves ONAP integration capabilities, mainly in 5G use-cases and E2E Network Slicing. Future-proofs ONAP for years to come. Allows to use AKS/EKS/GKS (* managed Kubernetes Service) to deploy ONAP in public clouds.
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - None. RKE is already supporting K8S 1.18 as one of recommended K8S solutions, thus no additional costs here.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider
CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES (REQ-439)
R8 PRESENTATION:
ITEM | DETAILS |
R8 Presentation | |
Recording mp4 | |
Audio only |
Key Contacts - @Paweł Pawlak @Amy Zwarico
Executive Summary - All ONAP projects shall continue their efforts to reduce the risks associated with software vulnerabilities in the ONAP code base by upgrading all outdated, vulnerable direct dependencies in their code bases following the recommendations of SECCOM. The project and repo specific recommendations are provided in the Security Vulnerability space for Honolulu release.
Business Impact - Improves the security posture of ONAP.
Business Markets - All operators and service providers can leverage the of fewer vulnerabilities in the open source dependencies in ONAP
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) (REQ-438)
R8 PRESENTATION:
ITEM | DETAILS |
R8 Presentation | |
Recording mp4 | |
Audio only |
Key Contacts - @Amy Zwarico @Paweł Pawlak
Executive Summary - All remaining ONAP projects using java shall reduce the risks associated with no regular support for java v8 software as it causes increase of usage risk, as recommended by SECCOM. Continuation of REQ-351.
Business Impact - Improves the security posture of ONAP.
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) (REQ-437)
R8 PRESENTATION:
ITEM | DETAILS |
R8 Presentation | |
Recording mp4 | |
Audio only |
Key Contacts - @Amy Zwarico @Paweł Pawlak
Executive Summary - All remaining ONAP projects using Python shall reduce the risks associated with no community support for Python 2.7 software as it causes increase of usage risk, as recommended by SECCOM. Continuation of REQ-373.
Business Impact - Improves the security posture of ONAP.
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA (REQ-441)
R8 PRESENTATION:
ITEM | DETAILS |
R8 Presentation | |
Recording mp4 | |
Audio only |
Key Contacts - @rouzaut @Amy Zwarico @Paweł Pawlak
Executive Summary - All ONAP applications should generate logs that can be collected by Kubernetes.
Business Impact - Improves the security posture of ONAP.
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
COMPLETION OF HELM MIGRATION (v2 → v3) (REQ-442)
R8 PRESENTATION:
ITEM | DETAILS |
R8 Presentation | |
Recording mp4 | |
Audio only |
Key Contacts - @Amy Zwarico @Paweł Pawlak
Executive Summary - All ONAP projects using HELMv2 must migrate during the Honolulu release to HELMv3.
Business Impact - Improves the security posture of ONAP.
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL (REQ-443)
Key Contacts - @Tony Hansen @Amy Zwarico @Paweł Pawlak
Executive Summary - ONAP project will provide their feedback for the Application Security questions:
Crypto Credentials Agility – ½ od apps in met and almost half not yet answered
Implement Secure Design – 1/3 of projects did not answer
Crypto Weaknesses – tests to be applied (3 including Morgan)
Projects that have already answered this question positively, should verify that the answer is still correct.
Continuation of REQ-350.
Business Impact - Improves the security posture of ONAP by lessening the risk.
Business Markets - All operators and service provider.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Support for the Multi Tenancy in ONAP (REQ-463)
Key Contacts - @Olivier Phenix @Seshu Kumar Mudiganti @Mike Elliott @rodrigo lima
Executive Summary - Allow ONAP to run in a multi-tenant environment, where each tenant can manage access to his service designs, instances, and namespace-specific component
Business Impact - Make ONAP more appealing for operators and service providers, which often require different user groups to have different access level to resources.
Business Markets - All operators and service providers can leverage the multi-tenancy functionality of ONAP
Funding/Financial Impacts - Reduction in operations expense from using industry standard Interfaces.
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Identification of events that compromise the ONAP system (REQ-464)
Key Contacts - @rouzaut @Amy Zwarico @Paweł Pawlak
Executive Summary -
Implementation is done to identify events that compromise the system.
This information feedback is done because only an intervention can stop this risk.
The events are logged and according to rules have intervened according to the risks.
External system must be use to save and display the log
Secure protocol must be use to transfert the log between ONAP and external system
Business Impact - Improves the security posture of ONAP by lessening the risk.
Business Markets - All operators and service provider.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.