Difference between revisions of "OpenStack Edge Discussions Dublin PTG"
| Line 9: | Line 9: | ||
=== Edge use cases === | === 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 <ref name="OpenStack Edge Computing Whitepaper">[https://www.openstack.org/assets/edge/OpenStack-EdgeWhitepaper-v3-online.pdf]</ref> also describes there are unlimited use cases possible. The most prominents are: | + | 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 <ref name="OpenStack Edge Computing Whitepaper">[https://www.openstack.org/assets/edge/OpenStack-EdgeWhitepaper-v3-online.pdf]</ref>, which is available from the Edge section of openstack.org <ref name="openstack.org edge section">[https://www.openstack.org/edge-computing/]</ref> 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. | * 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 == | == Links == | ||
<references /> | <references /> | ||
Revision as of 13:59, 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:
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
