Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

(RM Chapter 3 new section on Edge Computing w/o OpenStack specifics)

Alt: RM Chapter08 PR #2118  | Please make your comments on the PR and not here.

X.1 Introduction

Chapter 3(https://github.com/cntt-n/CNTT/blob/master/doc/ref_model/chapters/chapter01.md) of this document focuses on cloud infrastructure abstractions. While these are generic abstractions they and the associated capabilities are specified for data center or a colocation center cloud infrastructure. The environmental conditions, facility and other constraints, and the variability of deployments on the edge are significantly different and, thus, requires separate consideration.

...

A generic Telco cloud is an hybrid multi-cloud or a Federated cloud that has deployments in large data centers, central offices or colocation facilities, and the edge. In this chapter we will discuss the characteristics of Telco Edge and hybrid multi-cloud.

X.2 Telco Edge Cloud

This section presents the characteristics and capabilities of different Edge cloud deployment locations, infrastructure, footprint, etc.

X.2.1 Telco Edge Cloud Deployment Environment Characteristics

Telco Edge Cloud (TEC) deployment locations can be environmentally friendly such as indoors (offices, buildings, etc.) or environmentally challenged such as outdoors (near network radios, curbside, etc.) or environmentally harsh environments (factories, noise, chemical, heat and electromagnetic exposure, etc). Some of the more salient characteristics are captured in Table X.1.

...


Facility Type

Environmental

Characteristics

Capabilities

Physical

Security

ImplicationsDeployment LocationsComments
Environmentally friendlyIndoors: typical commercial or residential structures

Protected

Safe for common infrastructure

Easy access to continuous electric power

High/Medium bandwidth Fixed and/or wireless network access


Controlled Access

Commodotised infrastructure with no or minimal need for hardening/ruggedisation

Operational benefits for installation and maintenance

Indoor venues: homes, shops, offices, stationary and secure cabinets

Data centers, central offices, co-location facilities, Vendor premises, Customer premises


Environmentally challengedOutdoors and/or exposed to environmentally harsh conditions

maybe unprotected

Exposure to abnormal levels of noise, vibration, heat, chemical, electromagnetic pollution

May only have battery power

Low/Medium bandwidth Fixed and/or mobile network access

No or minimal access control

Expensive ruggedisation

Operationally complex

Example locations: curbside, near cellular radios,


X.2.2 Telco Edge Cloud Infrastructure Characteristics

Commodity hardware is only suited for environmentally friendly environments. Commodity hardware have standardised designs and form factors. Cloud deployments in data centers typically use such commodity hardware with standardised configurations resulting in operational benefits for procurement, installation and ongoing operations.

...

At the edge, the infrastructure may further include ruggedised hardware for harsh environments and hardware with different form factors.

X.2.3 Telco Edge Cloud Infrastructure Profiles

The Reference Model (https://github.com/cntt-n/CNTT/blob/master/doc/ref_model/chapters/chapter04.md#4.2.4) specifies two infrastructure profiles:

...

Table X.2. Characteristics of Infrastructure nodes

ReferenceFeatureDescriptionAs Specified in RM Chapter 05Exception for Edge



Basic TypeNetwork IntensiveBasic TypeNetwork Intensive
infra.stg.cfg.003Storage with replication
NYNOptional
infra.stg.cfg.004Storage with encryption
YYNOptional
infra.hw.cpu.cfg.001Minimum Number of CPU socketsThis determines the minimum number of CPU sockets within each host2211
infra.hw.cpu.cfg.002Minimum Number of cores per CPUThis determines the number of cores needed per CPU.202022
infra.hw.cpu.cfg.003NUMA alignmentNUMA alignment support and BIOS configured to enable NUMANYNOptional

X.2.3 Telco Edge Cloud Infrastructure Characteristics

This section characterises the hardware capabilities for different edge deployments and the Platform services that run on the infrastructure. Please note, that the Platform services are containerised to save resources, and benefit from intrinsic availability and auto-scaling capabilities.

Table X.3. Characteristics of Infrastructure nodes


Platform ServicesStorageNetwork Interfaces

IdentityImagePlacementComputeNetworkingMessage QueueDB ServerEphemeralPersistent BlockPersistent ObjectManagementUnderlay (Provider)Overlay
Control Nodes

Image Modified

Image Modified

Image Modified

Image Modified

Image Modified

Image Modified

Image Modified


Image Modified


Image Modified

Image Modified

Image Modified

Workload Nodes

(Compute)




Image Modified

Image Modified



Image Modified

Image Modified

Image Modified

Image Modified

Image Modified

Image Modified

Storage Nodes







Image Modified

Image Modified

Image Modified

Image Modified

Image Modified

Depending on the facility capabilities, deployments at the edge may be similar to one of the following:

...

HA at edge (at least 2 edge servers): Multiple Controller and multiple workloads


X.2.4. Comparison of Edge terms from various Open Source Efforts


Characteristics
Other Terms
CNTT Term?ComputeStorageNetworking

RTT*

SecurityScalabilityElasticityResiliency

Preferred Workload

Architecture

Upgrades
OpenStackOPNFV EdgeEdge GlossaryGSMA

Regional Data Center (DC)


Fixed

1000's

Standardised

>1 CPU

>20 cores/CPU


10's EB

Standardised

HDD and NVMe

Permanence


>100 Gbps

Standardised

~100 msHighly SecureHorizontal and unlimited scalingRapid spin up and down

Infrastructure architected for resiliency

Redundancy for FT and HA

Microservices based

Stateless

Hosted on Containers

HW Refresh: ?

Firmware: When required

Platform SW: CD


Central Data Center


Metro Data Centers


Fixed

10's to 100's

Standardised

>1 CPU

>20 cores/CPU

100's PB

Standardised

NVMe on PCIe

Permanence

> 100 Gbps

Standardised

~10 msHighly SecureHorizontal but limited scalingRapid spin up and down

Infrastructure architected for some level of resiliency

Redundancy for limited FT and HA

Microservices based

Stateless

Hosted on Containers

HW Refresh: ?

Firmware: When required

Platform SW: CD


Edge SiteLarge EdgeAggregation Edge

Edge


Fixed / Mobile

10's

Some Variability

>=1 CPU

>10 cores/CPU

100 TB

Standardised

NVMe on PCIe

Permanence / Ephemeral

50 Gbps

Standardised

~5 msLow Level of TrustHorizontal but highly constrained scaling, if anyRapid spin up (when possible) and down

Applications designed for resiliency against infra failures

No or highly limited  redundancy

Microservices based

Stateless

Hosted on Containers

HW Refresh: ?

Firmware: When required

Platform SW: CD


Far Edge SiteMedium EdgeAccess Edge / Aggregation Edge

Mini-/Micro-Edge


Mobile / Fixed

1's

High Variability

Harsh Environments

1 CPU

>2 cores/CPU

10's GB

NVMe

Ephemeral

Caching

10 Gbps

Connectivity not Guaranteed

<2 ms

Located in network proximity of EUD/IoT

UntrustedLimited Vertical Scaling (resizing)Constrained

Applications designed for resiliency against infra failures

No or highly limited  redundancy

Microservices based or monolithic

Stateless or Stateful

Hosted on Containers or VMs

Subject to QoS, adaptive to resource availability, viz. reduce resource consumption as they saturate

HW Refresh: ?

Firmware: ?

Platform SW: ?


Fog Computing (Mostly deprecated terminology)

Extreme Edge 

Far Edge

Small EdgeAccess Edge
*RTT: Round Trip Times
 EUD: End User Devices
 IoT: Internet of Things

...

+++++++++++++++++++++++++++++++++++++++++++++++++++++

Edge deployment scenarios

Cloud Infrastructure (CI) deployment environment for different edge deployments:

...

External (curb-side, proximity to radio site, etc.)


SDN Networking support on Edge



Comparison of Edge terms from various Open Source Efforts


Characteristics
Other Terms
CNTT Term?ComputeStorageNetworking

RTT*

SecurityScalabilityElasticityResiliency

Preferred Workload

Architecture

Upgrades
OpenStackOPNFV EdgeEdge GlossaryGSMA

Regional Data Center (DC)


Fixed

1000's

Standardised

>1 CPU

>20 cores/CPU


10's EB

Standardised

HDD and NVMe

Permanence


>100 Gbps

Standardised

~100 msHighly SecureHorizontal and unlimited scalingRapid spin up and down

Infrastructure architected for resiliency

Redundancy for FT and HA

Microservices based

Stateless

Hosted on Containers

HW Refresh: ?

Firmware: When required

Platform SW: CD


Central Data Center


Metro Data Centers


Fixed

10's to 100's

Standardised

>1 CPU

>20 cores/CPU

100's PB

Standardised

NVMe on PCIe

Permanence

> 100 Gbps

Standardised

~10 msHighly SecureHorizontal but limited scalingRapid spin up and down

Infrastructure architected for some level of resiliency

Redundancy for limited FT and HA

Microservices based

Stateless

Hosted on Containers

HW Refresh: ?

Firmware: When required

Platform SW: CD


Edge SiteLarge EdgeAggregation Edge

Edge


Fixed / Mobile

10's

Some Variability

>=1 CPU

>10 cores/CPU

100 TB

Standardised

NVMe on PCIe

Permanence / Ephemeral

50 Gbps

Standardised

~5 msLow Level of TrustHorizontal but highly constrained scaling, if anyRapid spin up (when possible) and down

Applications designed for resiliency against infra failures

No or highly limited  redundancy

Microservices based

Stateless

Hosted on Containers

HW Refresh: ?

Firmware: When required

Platform SW: CD


Far Edge SiteMedium EdgeAccess Edge / Aggregation Edge

Mini-/Micro-Edge


Mobile / Fixed

1's

High Variability

Harsh Environments

1 CPU

>2 cores/CPU

10's GB

NVMe

Ephemeral

Caching

10 Gbps

Connectivity not Guaranteed

<2 ms

Located in network proximity of EUD/IoT

UntrustedLimited Vertical Scaling (resizing)Constrained

Applications designed for resiliency against infra failures

No or highly limited  redundancy

Microservices based or monolithic

Stateless or Stateful

Hosted on Containers or VMs

Subject to QoS, adaptive to resource availability, viz. reduce resource consumption as they saturate

HW Refresh: ?

Firmware: ?

Platform SW: ?


Fog Computing (Mostly deprecated terminology)

Extreme Edge 

Far Edge

Small EdgeAccess Edge
*RTT: Round Trip Times
 EUD: End User Devices
 IoT: Internet of Things

Glossary