Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


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

R8 PRESENTATION:

ITEMDETAILS
R8 Presentation
Recording mp4
Audio only

Key Contacts - Damian Nowak Martin Skorupski

...

There is also a requirement to register the NetConf network devices in SDN-R controller, using IPv6 networking.

It is mainly about a Kubernetes platform, hosting ONAP application containers. An enabler for IPv4/IPv6 networking would be an upgrade of ONAP OOM Helm charts to K8S 1.16+ APIs.
The support for IPv4/IPv6 dual stack networking is planned to be executed in (at least) two steps:

  1. Migrate ONAP OOM Helm charts to support Kubernetes 1.17+ interfaces.
    Currently (June 2020), the newest K8S platform available as RKE distribution is 1.17. Newest K8S open-source GA distro is 1.18.
  2. Alternatively, certain components of ONAP, which are deployed using non-Helm methods could be placed on a dedicated K8S platform with IPv4/IPv6 support
  3. Review alternative K8S platforms, which can get an "ONAP recommended" stamp, and which support IPv4/IPv6 dual stack networking.

The 1st step described is considered as an enabler to execute the 2nd step. In ONAP/Guiin release, it is planned to implement the 1st step.
Initial tests targeting ONAP Frankfurt on RKE-K8S 1.17 have been executed, and impact is already understood.

...

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.17 18 as one of recommended K8S solutions, thus no additional costs here.

...