SUPPORT FOR IPv4/IPv6 DUAL STACK DEPLOYMENTS IN R8 (REQ-432)

R8 PRESENTATION:

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