Page History

Functionality

Native Deployment Mode

Infrastructure Deployment Mode

Usage Scenarios

On-Premises Edge

Network Edge

Infrastructure

Virtualization base: docker/libvirt

Orchestration: OpenNESS controller

Network: docker network (container) + NTS (through new added KNI interface)

Orchestration: Kubernetes

Network: kube-ovn CNI

Micro-Services in OpenNESS Controller

Web UI: controller UI

Edge Node/Edge application lifecycle management

Core Network Configuration

Telemetry

Core Network Configuration: Configure the access network (e.g., LTE/CUPS, 5G) control plane

Telemetry

Micro-Services in OpenNESS Node

EAA: application/service registration, authentication etc.

ELA/EVA/EDA: used by controller to configure host interfaces, network policy (used by NTS), create/destroy application etc.

DNS: for client to access MS in edge node

NTS: traffic steering

EAA: application/service registration, authentication etc.

EIS(Edge Interface Service), looks to be similar with providernet implemented in ovs4nfv k8s CNI

DNS: for client to access MS in edge node

Application on-boarding

OpenNESS Controller Web UI or Restful API

Kubernetes (e.g. Kubectl apply -f application.yaml)

Note: unlike 19.09, No UI used to on-board application

Edge node interface configuration

ELA (Edge LifeCycle Agent, Implemented by OpenNESS) – Configurated by OpenNESS controller

EIS (Edge Interface Service, which is an kubectl extension to configurate edge node host network adapter), use

e.g. kubectl interfaceservice attach $NODE_NAME $PCI_ADDRESS

Traffic Policy configuration

EDA (Edge Dataplane Agent, Implemented by OpenNESS) – Configurated by OpenNESS controller

Kubenetes Network Policy CRD

e.g. kubectl apply -f network_policy.yml

Note: unlike 19.09, No UI used to configure policy

DataPlane Service

NTS (Implemented based on DPDK in OpenNESS) to provide additional KNI interface for container

kube-ovn + Network policy