Skip to end of metadata
Go to start of metadata

Blueprint overview/Introduction

The Provider Access Edge blueprint is part of Akraino's Kubernetes-Native Infrastructure family of blueprints. As such, it leverages the best-practices and tools from the Kubernetes community to declaratively manage edge computing stacks at scale and with a consistent, uniform user experience from the infrastructure up to the services and from developer environments to production environments on bare metal or on public cloud.

This blueprint targets small footprint deployments able to host NFV (in particular vRAN) and MEC (e.g. AR/VR, machine learning, etc.) workloads. Its key features are:

  • Lightweight, self-managing clusters based on CoreOS and Kubernetes (OKD distro).
  • Support for VMs (via KubeVirt) and containers on a common infrastructure.
  • Application lifecycle management using the Operator Framework.
  • Support for multiple networks using Multus.
  • Support for real-time workloads using CentOS-rt*.

Documentation

Architecture

KNI PAE Installation Guide

KNI Blueprint User Documentation.

KNI PAE Test document

Project Team

PTL Self Nomination is open until noon, 10 June 2020 (Pacific Time)

Member

Company

Contact

RolePhoto & Bio PTL Self Nomination (y/n)
Andrew BaysRed HatCommitter

Frank Zdarsky

Red Hat

CommitterSenior Principal Software Engineer, Red Hat Office of the CTO; Edge Computing and 
Ricardo NoriegaRed HatRicardo NoriegaCommitterRed Hat NFVPE - CTO office - NetworkingY

Sukhdedv Kapur

Juniper

CommitterDistinguished Engineer; Contrail Software - CTO Org
Yolanda RoblaRed HatYolanda Robla MotaCommitterRed Hat NFVPE - Edge, baremetal provisioning
Arm
Contributor

Abhinivesh JainWiproabhinivesh.jain@wipro.comCommitter

SheetalRed HatSheetal Chetan SingalaCommitter

Use Case Template

Attributes

Description

Informational

Type

New


Industry Sector

Telco and carrier networks


Business Driver

The need for deploying mobile application on the edge is growing in latest times. Providing a platform that is capable of supporting deployment of mobile applications, using Kubernetes, and based on kubernetes tooling and declarative configuration from end to end is needed.


Business Use Cases

Edge deployments for 5G, mobile edge applications, vRAN


Business Cost - Initial Build Cost Target Objective

It can be deployed on libvirt, amazon and baremetal. Deployment on baremetal requires a small footprint POD with just 5 servers (1 bootstrap, 3 masters, 1 worker)


Business Cost – Target Operational Objective

The POD footprint starts being the same (5 servers), depending on the use case. Typically the cost will be less than $100k


Security Need

Kubernetes security monitoring and patching capabilities will be required, they are part of the deployment itself


Regulations

It will depend on the use case, and the workloads applied on top


Other Restrictions

-


Additional Details

-


Blueprint Template

Attributes

Description

Informational

Type

New


Blueprint Family - Proposed Name

Kubernetes-Native Infrastructure for Edge (KNI-Edge)


Use Case

Provider Access Edge (PAE)


Blueprint - Proposed Name

Provider Access Edge (PAE)


Initial POD Cost (CAPEX)

less than $150k (TBC)


Scale & Type

3 to 7 x86 servers (Xeon class)


Applications

vRAN (RIC), MEC apps (CDN, AI/ML, …)


Power Restrictions

less than 10kW (TBC)


Infrastructure orchestration

App Lifecycle Management: Kubernetes Operators
Cluster Lifecycle Management: Kubernetes Cluster API/Controller
Cluster Monitoring: Prometheus
Container Platform: Kubernetes (OKD 4.0)
Container Runtime: CRI-O
VM Runtime: KubeVirt
OS: CentOS/CentOS-rt 7.6


SDN

OpenShift SDN (w/ SR-IOV, DPDK, and multi-i/f)


SDSCeph

Workload Type

containers, VMs


Additional Details

-


  • No labels