Skip to end of metadata
Go to start of metadata

Topic Areas:

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.

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

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

Commodity/Standard: COTS, standard hardware designs and form factors. Deployed only in Controlled environments. Reduced operational complexity.

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:

CNTT Basic: General Purpose CPU; Standard Design.

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

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.

CNTT Network Intensive++ : CNTT Network Intensive + required hardware acceleration; Custom Design.

Server capabilities for different edge deployments and the OpenStack services that run on these servers; the OpenStack services are containerised to save resources, intrinsic availability and autoscaling:

Control nodes host the OpenStack control plane components (subset of Cloud Controller Services), and needs certain capabilities:

OpenStack services: Identity (keystone), Image (glance), Placement, Compute (nova), Networking (neutron) with ML2 plug-in

Message Queue, Database server

Network Interfaces: management, provider and overlay

Compute nodes host a subset of the Compute Node Services:


OpenStack Compute nova-compute (creating/deleting instances)

OpenStack Networking neutron-l2-agent, VXLAN, metadata agent, and any dependencies

Network Interfaces: management, provider and overlay

Local Ephemeral Storage

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

Block storage cinder-volume

Storage devices specific cinder volume drivers

Cloud partitioning: Host Aggregates, Availability Zones

Edge Deployments:

Small footprint edge device: only networking agents

Single server: deploy multiple (one or more) Compute nodes

Single server: single Controller and multiple (one or more) Compute nodes

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

SDN Networking support on Edge

Multi-Cloud Edge Architecture

  • An enterprise may own and/or have partnerships and network connections to utilize multiple Clouds - together An Enterprise's Clouds (EnCloud)
  • Each EnCloud consists of multiple interconnected Regions
  • An EnCloud Region may connect to multiple regions of another EnCloud (large capacity networks)
  • An EnCloud also consists of interconnected local sites (multiple hierarchies are possible)
  • An EnCloud's local site may connect to multiple Regions within that EnCloud or another EnCloud
  • An EnCloud also consists of a large number of interconnected edge nodes
  • Edge nodes are impermanent
  • An EnCloud's Edge node may connect to multiple local sites within that EnCloud or another EnCloud; an Edge node may rarely connect to an EnCloud Region

  • No labels


  1. Notes from Sept 8 discussion.  We need to capture the outline here, then move it into the Github docs repository.

    CI Deployment environment for edge.  Difference between between controlled environments (Data centers with conditioning) and uncontrolled environment where they might or be outside or in otherwise extreme conditions.  Aspects to consider could be lack of physical security, extreme temperatures, electro-magnetic interference (hospitals, etc.)  The term for exposed is harsh environments.  Need to change the doc above.

     Cloud Infrastructure (CI) hardware design – Edge hardware is more important than in Core HW.  More dependent on HW.  Intel FlexRAN for Edge.  Other companies have "edge" equipment – Dell, Lenovo, SuperMicro.  What makes the Edge equipment special?  Is that needed to deploy and Edge infrastructure.  Much of it is ruggetized for harsh environments.

    Server section - Add storage node for Edge.  More important than we originally thought.  Typically the OS deployment has a small footprint.  What is the minimum number of components you need to run OS at the edge?  Can we run it without network?  How about storage?  Need compute at the very least.  Looking at edge requirements within RA1- Chap 3-4.  2 or 3 servers at edge for HA.  3 is ideal.  Two for failover is the minimum.  Single server, with multiple compute nodes.  All the Edge OS implementations are containerized to safe resources on the edge HW. OpenShift, ADVA has a single server OS management tool.  StarlingX supports that approach as well. 

    Cyberg can be extended to the Edge, Ussurn (OS release after Train) supports FPGA from the beginning.  Nova does not support FPGA natively.  Cisco supports it, but they add proprietary secret sauce to make it work.  Need to address the need for OS native support for FPGA.  China Mobile is also using it, but they wrote extensions to do it.