SUPPORT FOR IPv4/IPv6 DUAL STACK DEPLOYMENTS IN R8
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.
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:
- 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. - Alternatively, certain components of ONAP, which are deployed using non-Helm methods could be placed on a dedicated K8S platform with IPv4/IPv6 support
- 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.
Additionally, K8S 1.17+ upgrade will offer as well additional functionality on the platform side, which can be used for other purposes.
Business Impact - Improves ONAP integration capabilities, mainly in 5G use-cases and E2E Network Slicing. Future-proofs ONAP for years to come.
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - None. RKE is already supporting K8S 1.17 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