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:
Hypervisor
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