Aarna Networks Multi Cluster Orchestration Platform (AMCOP)
(A distribution of OpenNESS 20.12 EMCO)
Overview of Aarna Networks, Inc.
5G and edge computing are once-in-a-generation technology trends that will change the way we live and work. Moreover, a move to an all-software environment with cloud native network functions (CNF) and cloud native applications (CNA) across a very large number of edge sites will make application management 1,000,000x more complex that today. This requires a new solution that is being provided by Aarna Networks.
The Aarna Networks Multi Cluster Orchestration Platform (AMCOP) is a commercial platform for orchestration, lifecycle management, and real-time policy-driven closed loop automation of 5G network services and edge computing applications. The core component of our distribution is the OpenNESS EMCO component.
OpenNESS Building Blocks
OpenNESS EMCO (Edge Multi-Cluster Orchestration) Building Block
Virtual machine(s) or bare metal server(s) with the following minimum hardware resources: 16 vCPUs, 32 GB RAM, 500GB SSD, 300GB HDD for Boot disk. The server also requires Kubernetes based OpenNESS 12.20 or later cluster.
Problem Statement or Business Requirements
To fully automate 5G and edge computing, three levels or orchestration are required: infrastructure, resource, and application/service. Infrastructure orchestration takes care of setting up operating systems and a Kubernetes (K8s) environment on bare metal servers and managing a large number of such clusters. The resource orchestration layer is K8s that spreads pods across a number of compute nodes and manages the health and replica factors of these pods. The application or service orchestration layer is a particularly difficult problem as the combination of number of edge sites (could be in 100,000s), application instances (could be in 10,000s with network slicing), and the amount of change through DevOps means that existing mechanisms of managing applications or network services will simply not work. (Note: The term orchestration includes lifecycle management, day 1 and 2 configuration, and real-time policy-driven closed loop automation functionality as well.)
AMCOP Value Proposition/Benefits
AMCOP includes intent based orchestration, ongoing lifecycle management, day 1 and 2 configuration, and real-time policy driven closed loop automation for network services and composite applications built using cloud native network functions (CNF) and cloud native applications (CNA). AMCOP has been integrated with a number of K8s implementations such as open source K8s with OpenNESS, Red Hat OpenShift, AWS EKS, Azure AKS, and Google GKE. AMCOP has also been tested with several CNFs (specifically 5G core, 5G RAN) and CNAs in the OpenNESS marketplace. The below diagram shows the key components of AMCOP.
The benefits of AMCOP are:
• Zero touch management of network services and edge computing applications • Comprehensive 5G support • Access to a large pool of applications through the OpenNESS marketplace • Support for public and private networks • Lightweight, easy-to-use, standards aligned platform
Deployment Diagram of AMCOP with OpenNESS Clusters at the Edge
This diagram shows an example deployment of AMCOP with OpenNESS clusters at the edge.
The diagram shows two clusters. One cluster is hosting all of the Free5GC 5G core services. The second cluster is hosting a UPF and an edge computing application through local breakout. The two clusters are connected through a provider network. AMCOP’s EMCO component is responsible for the orchestration of the two 5G network services, the edge computing application, and overlay networks. This same concept can be extended to 10,000s or more edge clusters with 1,000s of application instances.
Installation and Usage
AMCOP installation involves 3 basic steps:
• Prepare a Deployment host, from where the installation will be done. This host (or VM) should have access to the host(s) where OpenNESS K8s cluster is running. • Extract AMCOP Installation bundle. • Run the Ansible script which installs the necessary components and deploys AMCOP on the OpenNESS K8s cluster.
Please see the detailed Deployment Guide .
Once AMCOP is installed, it can be used to orchestrate network services and composite applications. The below figure shows the various steps required for orchestration. Please see the detailed Users Guide to try out applications such as vFW and Free5GC 5G core.
Additional Use Cases
AMCOP can be used for the following use cases:
• 5G Core orchestration • O-RAN orchestration — AMCOP interoperates with Intel FlexRAN • IoT orchestration • PNF management • Facilitates MEC roaming • Facilitates interoperability/peering with ONAP • OSS/BSS interoperability