Cloud-native network function
 | This article may be too technical for most readers to understand. (August 2020) |
A Cloud-Native Network Function (CNF) is a software-implementation of a network function, which runs inside a linux container (typically orchestrated by Kubernetes), which would traditionally be performed by a physical device.[1][2][3] In some industry fora, the distinctive feature of CNFs from VNFs is the approach taken for their orchestration. The CNFs are orchestrated using cloud native solutions, typically the ones available in the Cloud Native Computing Foundation project. In ETSI NFV standards, the Cloud-Native Network Functions are a particular type of Virtualized Network Functions, one of the components of Network Function Virtualization[4] and they are orchestrated as VNFs, i.e. using the ETSI NFV MANO architecture and technology agnostic descriptors (e.g. TOSCA, YANG). In that case, the upper layers of the ETSI NFV MANO architecture (i.e. the NFVO and VNFM) cooperate with a Container Infrastructure Service Management (CISM) function [5] that is typically implemented using cloud-native orchestration solutions (e.g. Kubernetes).
The characteristics of Cloud-Native Functions are:[6][7]
- Containerized micro-services that communicate with each-other via standardized RESTful APIs
- Small performance footprint, with the ability to scale horizontally
- Independence of guest operating system, since CNFs operate as containers
- Lifecycle manageable by Kubernetes, using container images registries such as OCI Docker, and OS container runtime.
Relation to Network Function Virtualization
These characteristics address many of the common issues found with the first generation of VNFs, by incorporating many of the innovations deployed commonly in the internet infrastructure. These include auto-scaling,[2] supporting a continuous delivery/DevOps deployment model, and efficiency gains by sharing common services across platforms. Through service discovery and orchestration, a system based on CNFs will be more resilient to node failure.[2][6] A specification of criteria to classify and characterize Cloud Native VNF implementations can be found in ETSI GS NFV-EVE 011.[8]
Cloud Native Computing Foundation
The Linux Foundation backed Cloud Native Computing Foundation project is actively supporting companies in contributing to open-source projects like Kubernetes or Prometheus, upon which Cloud Native Network Functions can be based on.[9] The CNCF project also created a CNF Testbed, in order to facilitate a common test-ground for various cloud-native network functions.[10] Custom Cloud-Native Network Functions are developed by several companies, such as Cisco, Ericsson, or Red Hat.[11]
References
- ^ "Cloud Native Network Functions (CNF)". Ligato.io.
{{cite web}}: CS1 maint: url-status (link) - ^ a b c "What is a CNF?". CDNF.io.
{{cite web}}: CS1 maint: url-status (link) - ^ cloud-native-principles/cloud-native-principles, cloud-native-principles, 2020-07-21, retrieved 2020-07-22
- ^ "NFV FAQ". nfvwiki.etsi.org. Retrieved 2022-04-27.
- ^ "ETSI GS NFV-IFA 040" (PDF). www.etsi.org. Retrieved 2022-07-20.
- ^ a b "Cloud-Native Network Functions". Cisco.
{{cite web}}: CS1 maint: url-status (link) - ^ cncf/cnf-testbed, Cloud Native Computing Foundation (CNCF), 2020-07-20, retrieved 2020-07-22
- ^ "ETSI GS NFV-EVE 011" (PDF). www.etsi.org. Retrieved 2022-04-27.
- ^ "FAQ". Cloud Native Computing Foundation. Retrieved 2020-07-22.
- ^ cncf (2019-02-25). "CNCF Launches Cloud Native Network Functions (CNF) Testbed". Cloud Native Computing Foundation. Retrieved 2020-07-22.
- ^ "Running cloud-native network functions with confidence on Red Hat OpenShift". www.redhat.com. Retrieved 2020-07-22.
11. Cloud Native Computing Foundation, (http//www.cncf.io)