Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 is controlled at the Edge and how much is controlled at the core.  Many parameters to take into consideration.   Anyone that worked on Distributed Processing in the 1980's would recall that the nodes were considered from 3 limitations: Processing, storage, bandwidth. These now apply to edge nodes.  Terminology is difficult, 3 years in and we still don't have a shared definition of the edge.  The problem is that Edge is a super set of Cloud computing.   Telco Edge is both latency and network efficiency concerns.  Trevor:  What are we trying to solve for the CNTT workstream?  Important question.  We cannot boil the ocean.  

Review of the chart that covers who owns what in the Edge.  Workload distribution, hybrid model of HW and SW.  How can you deliver an SLA in this model?  Public and private cloud SLAs are very different.  Telco SLAs need to be much higher per customer expectations.  Cloud has the illusion of infinite resources, but when you scale you can use outside locations.  There is always a cost for flexibility.  

Single boxes 

Topic Areas

Cloud Infrastructure (CI) deployment environment

...