Jump to: navigation, search

Difference between revisions of "OpenStack Edge Discussions Dublin PTG"

Line 19: Line 19:
 
This is a single node deployment with multiple instances contained within it (lives in a coffee shop for instance); there should probably be some external management of the collection of these single nodes that does roll-up.
 
This is a single node deployment with multiple instances contained within it (lives in a coffee shop for instance); there should probably be some external management of the collection of these single nodes that does roll-up.
 
* Hardware specs
 
* Hardware specs
  * Minimum: 1 unit of 4 cores, 8 GB RAM, 225 GB SSD
+
  * Minimum: 1 unit of 4 cores, 8 GB RAM, 225 GB SSD
  * Maximum: 1 unit of ? cores, 64 GB RAM, 1 TB storage
+
  * Maximum: 1 unit of ? cores, 64 GB RAM, 1 TB storage
  
 
== Links ==
 
== Links ==
 
<references />
 
<references />

Revision as of 14:38, 21 March 2018

Intro

This page collects the discussed topics of the Edge Worskhop from the Dublin PTG. If there is any error on this page or some information is missing please just go ahead and correcct it.

The discussions were noted in the following etherpads:

  • PTG schedule [1]
  • Gap analyzis [2]
  • Alans problems [3]

Edge use cases

However it was not noted in the etherpads there were lots of discussions about the use cases for edge clouds. As the OpenStack Edge Computing Whitepaper [4], which is available from the Edge section of openstack.org [5] also describes there are unlimited use cases possible. The most prominents are:

  • IoT data aggregation: In case of IoT a big amount of devices are sending their data towards the central cloud. In an edge application this data can be pre processesed and aggregated, so the amount of data sent to the central cloud is smaller.
  • NFV: Telecom operators would like to run realtime applications on an infrastructure close to the radio heads to provide low latency.
  • Autonomus devices: Autonomus cars and other devices will generate high amount of data a will need low latency handling of this data.

Deployment Scenarios

To support all of the use cases there is a need for different size of edge clouds. During the discussions we recognised the following deployment scenarios:

Small edge

This is a single node deployment with multiple instances contained within it (lives in a coffee shop for instance); there should probably be some external management of the collection of these single nodes that does roll-up.

  • Hardware specs
  * Minimum: 1 unit of 4 cores, 8 GB RAM, 225 GB SSD
  * Maximum: 1 unit of ? cores, 64 GB RAM, 1 TB storage

Links

  1. [1]
  2. [2]
  3. [3]
  4. [4]
  5. [5]