Page Comparison

This page is now not in use. Instead please refer to and add content to: PR #2118

• CNTT Hybrid Multi-Cloud Architecture (includes Edge)
• CNTT Edge Architecture

Topic Areas:

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

Edge deployment scenarios

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

Controlled: Indoors, Protected, and Restricted environments. Data Centers, Central Offices, Indoor venues. Operational benefits for installation and maintenance, and reduced need for hardening/ruggedized.

Exposed: Outdoors, Exposed, Harsh and Unprotected environments. Expensive rugged equipment

Cloud Infrastructure (CI) hardware type for different edge deployments:

Cloud Infrastructure (CI) - Commodity/Standard: COTS, standard hardware designs and form factors. Deployed only in Controlled environments. Reduced operational complexity.

Cloud Infrastructure (CI) - Custom/Specialised: non-standard hardware designs including specialised components, ruggetised for harsh environments and different form factors. Deployed in Controlled and/or Exposed environments. Operationally complex environment.

Cloud Infrastructure (CI) hardware specifications for different edge deployments:

Cloud Infrastructure (CI) - CNTT Basic: General Purpose CPU; Standard Design.

Cloud Infrastructure (CI) - CNTT Network Intensive: CNTT Basic + high speed user plane (low latency, high throughput); Standard Design.

Cloud Infrastructure (CI) - CNTT Network Intensive+ : CNTT Network Intensive + optional hardware acceleration (compared with software acceleration can result in lower power use and smaller physical size); possible Custom Design.

Cloud Infrastructure (CI) - CNTT Network Intensive++ : CNTT Network Intensive + required hardware acceleration; Custom Design.

...

Network Interfaces: management, provider and overlay

Local Ephemeral Storage

Cloud partitioning: Host Aggregates, Availability Zones

Storage Nodes host the cinder-volume service. Storage nodes are optional and required only for some specific Edge deployments that need large persistent storage:

...

Storage devices specific cinder volume drivers

Cloud partitioning: Host Aggregates, Availability Zones

OpenStack Edge Reference Architecture provides more depth and details

Edge Deployments:

Small footprint edge device: only networking agents

...

SDN Networking support on Edge

(RM Potential Ch 2 as a specialised workoad type)

Network Function as a Service (NFaaS)

Higher level services such as Network Functions (includes composition of Network Functions to form higher level services) offered on Telco and other clouds (HCP, specialised, etc.). While here the discussion is about NFaaS, this is equally applicable to anything as a service (XaaS)

• NFaaS offered on one or more Cloud Services (Telco, HCP, others) including at the Edge
  
  • Network integration and Service Chaining
  • Security Considerations including delegated User Authentication & Authorization
  • Commercial arrangements including User Management

(RM Ch03 as a sub-section of Introduction)

Hybrid Multi-Cloud Enabled Edge Architecture

...

Image Removed

...

Image Added

(PG: In the above diagram, replace "Local" with "Metro")

• The Telco Operator may own and/or have partnerships and network connections to utilize multiple Clouds - together An Enterprise's Clouds (EnCloud)
• Each EnCloud consists of multiple Regions
• Multiple regions of an EnCloud
  
  • for network services, IT workloads, external subscribers
  • On Prem Private
    
    • Open source; Operator or Vendor deployed and managed  | OpenStack or Kubernetes based
    • Vendor developed; Operator or Vendor deployed and managed  | Examples: Azure on Prem, VMWare, Packet, Nokia, Ericsson, etc.
  • On Prem Public: Commercial Cloud service hosted at Operator location but for both Operator and Public use | Example: AWS Wavelength
  • Outsourced Private: hosting outsourced; hosting can be at a Commercial Cloud Service | Examples: Equinix, AWS, etc.
  • (Outsourced) Public: Commercial Cloud Service | Examples: AWS, Azure, VMWare, etc.
  • Multiple different Clouds can be co-located in the same physical location and may share some of the physical infrastructure (for example, racks)

Type	System Developer	System Maintenance	System Operated & Managed by	Location where Deployed	Primary Resource Consumption Models
Private (Internal Users)	Open Source	Self/Vendor	Self/Vendor	On Prem	Reserved, Dedicated
Private	Vendor | HCP	Self/Vendor	Self/Vendor	On Prem	Reserved, Dedicated
Public	Vendor | HCP	Self/Vendor	Self/Vendor	On Prem	Reserved, On Demand
Private	HCP	Vendor	Vendor	Vendor Locations	Reserved, Dedicated
Public (All Users)	HCP	Vendor	Vendor	Vendor Locations	On Demand, Reserved

• Each Telco Cloud consists of multiple interconnected Regions
• A Telco Cloud Region may connect to multiple regions of another EnCloud another Telco Cloud (large capacity networks)
• An EnCloud A Telco Cloud also consists of interconnected local sites (multiple hierarchies are possible scenarios)
• An EnCloudA Telco Cloud's local site may connect to multiple Regions within that EnCloud that Telco Cloud or another EnCloudAn EnCloud Telco Cloud
• A Telco Cloud also consists of a large number of interconnected edge nodes
• Edge nodes are may be impermanent
• An EnCloudA Telco Cloud's Edge node may connect to multiple local sites within that EnCloud that Telco Cloud or another EnCloudTelco Cloud; an Edge node may rarely connect to an EnCloud Regionan Telco Cloud Region

(RM Ch03 the new Edge Section)

Comparison of Edge terms from various Open Source Efforts

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

Glossary

• State of the Edge