You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 38 Next »

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

Hardware

KNI Blueprint User Documentation.

Project Team

Member

Company

Contact

RolePhoto & Bio 
Andrew BaysRed HatCommitter

Frank Zdarsky

Red Hat

CommitterSenior Principal Software Engineer, Red Hat Office of the CTO; Edge Computing and 

Jennifer Koerv

Intel

Committer
Manjari AsawaWiproManjari Asawa <manjari.asawa@wipro.com>Committer
Mikko YlinenIntelCommitter
Ned SmithIntelCommitter
Ricardo NoriegaRed HatRicardo NoriegaCommitterRed Hat NFVPE - CTO office - Networking

Sukhdedv Kapur

Juniper

CommitterDistinguished Engineer; Contrail Software - CTO Org
Yolanda RoblaRed HatYolanda Robla MotaPTL, CommitterRed Hat NFVPE - Edge, baremetal provisioning
Pragash VijayaragavanJuniperpvijayaragav@juniper.netCommitter
Tina TsouArm
Contributor

Use Case Template

Attributes

Description

Informational

Type

New


Industry Sector

Telco and carrier networks


Business Driver



Business Use Cases



Business Cost - Initial Build Cost Target Objective



Business Cost – Target Operational Objective



Security Need



Regulations



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

End-to-end Service Orchestration: ONAP
Middlewares: Kubeflow (AI/ML), NEV SDK (TBC)
App Lifecycle Management: Kubernetes Operators (mix of Helm and native)
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

Tungsten Fabric (w/ SR-IOV, DPDK, and multi-i/f); leaf-and-spine fabric mgmt.


SDSCeph

Workload Type

containers, VMs


Additional Details



  • No labels