Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 27 Next »

Overview



The family’s Provider Access Edge blueprint targets vRAN and MEC (e.g. AR/VR, machine learning, etc.) use cases. 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 real-time workloads using CentOS-rt*.


Architecture


Resource Requirements



Documentation


Release Notes


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 Noriega De SotoCommitterRed 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

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