You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Topic Leader(s)


Topic Overview

Detailed Description: Brief update cover CNTT Edge.  After reviewing the Reference Model, it was determined that the Reference Model met the Edge groups criteria in its current state.  Proposals for changes to the CNTT reference architectures, both RA1 (OpenStack) and RA2 (Containers) can be found at  CNTT Edge - RA01 ( OpenStack ) Architecture - Scenario.  This will serve as the basis for the discussion for the planning for the upcoming work that needs to be incorporated into the next (Elbrus) release targeted for January.  

Slides & Recording

CNTT Edge - RA01 ( OpenStack ) Architecture - Scenario

Minutes

Pankaj reviewed his outline and asked for comments.  Beth: there are two types of edge that are quite different.  The far edge has very different characteristics than the data center.  Telco edge is more focused more on low latency than other use cases.  O-RAN is a use case that is latency sensitive use case.  SD WAN is a mixed use case, purpose-built edge or uCPE based software.  The controllers are located in the core cloud.  Time sync is important O-RAN, RAN video processing, UPF - User Plane Fn for packet routing, forwarding inspection, etc. and possibly other use cases.  We have not spent time characterizing all the use cases yet.  Use cases are a good way of mapping the Edge requirements, but we should not get bogged down in the details or create silos.  We should create a set of profiles that abstract the use cases.  We cannot proscribe the HW, but at the far edge is much more dependent on the HW.  From an architecture view, we need to be able to support very distributed profiles.   We can simplify all the use cases with the profiles.  

You need to think in terms of cores, not racks.  HA at the edge at the minimum is two servers.  There are situations where the Edge nodes are impermanent and the HA is achieved by an adjacent node picking up the workload.  IoT is a good use case that fits this scenario.  The control plane is centralized to a certain extent, but the edge nots have to have at least some autonomy to work independent of the control plane.  Ildiko:  Don't try to define the edge, but it is ALWAYS connected to some kind of centralized core.  How much is 

Topic Areas

Cloud Infrastructure (CI) deployment environment

  •  


Cloud Infrastructure (CI) hardware type

  •  Do we need to to have Hardware profile 
    • No , and ODIM is not cover Hardware profile in terms of HW specs


Cloud Infrastructure (CI) hardware specifications

  •  


Server capabilities (including OSTK Services)

  •  


Network Function as a Service (NFaaS)

  •  


Multi-Cloud Enabled Edge Architecture

  •  


Others

  •  

Action Items

  •  
  • No labels