Page History

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

...

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 partitioning: Host Aggregates, Availability Zones

OpenStack Edge Reference Architecture provides more depth and details

Edge Deployments:

Small footprint edge device: only networking agents

...

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

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 An enterprise may own and/or have partnerships and network connections to utilize multiple Clouds - together An Enterprise's Clouds (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)

• Each Telco Cloud Each EnCloud consists of multiple interconnected Regions
• An EnCloud 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 EnCloudTelco Cloud
• A Telco Cloud An EnCloud 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