ether: Edge Topology Synthesizer
Ether is a Python tool to generate plausible edge infrastructure configurations. It arose from the need to evaluate edge computing systems in different infrastructure scenarios where no appropriate testbeds are available.
Use cases
Some of the uses cases for ether include
- Evaluating resource allocation strategies
- Creating topologies for network simulations
- Infrastructure capacity planing
Examples
Code example
Creating a topology for an urban sensing scenario, similar to that of the Array of Things could look like this:
topology = Topology()
aot_node = IoTComputeBox(nodes=[nodes.rpi3, nodes.rpi3])
neighborhood = lambda size: SharedLinkCell(
nodes=[
[aot_node] * size,
IoTComputeBox([nodes.nuc] + ([nodes.tx2] * size * 2))
],
shared_bandwidth=500,
backhaul=MobileConnection('internet_chix'))
city = GeoCell(
5, nodes=[neighborhood], density=lognorm((0.82, 2.02)))
cloudlet = Cloudlet(
5, 2, backhaul=FiberToExchange('internet_chix'))
topology.add(city)
topology.add(cloudlet)
We have pre-parameterized versions of these scenarios that can be readily used:
topology = Topology()
UrbanSensingTopology().materialize(topology)
Example usage
The following example shows how we used generated topology to evaluate the effect on uplink usage of different resource allocation strategies in an edge computing platform. The node-link diagram of the topology is augmented with a topographic attribute map (rpreiner/tam) that the data exchange in log bytes. The left part of the figure shows the baseline resource allocation strategy, the right part shows our improved strategy that takes data-locality into account. The visualization helps to see how much the backhaul network is relieved, and how data transfer is isolated into edge networks.
Related publications
- Rausch, T., Lachner, C., Frangoudis, P. A., Raith, P., & Dustdar, S. (2020). Synthesizing Plausible Infrastructure Configurations for Evaluating Edge Computing Systems. In 3rd USENIX Workshop on Hot Topics in Edge Computing (HotEdge 20). USENIX Association. [Preprint]
Metadata
Release files for edgerun-ether 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| edgerun-ether-0.3.3.tar.gz | 22.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| edgerun_ether-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 87.6 kB
Release files / edgerun-ether-0.3.3.tar.gz
| Download URL | edgerun-ether-0.3.3.tar.gz |
|---|---|
| Size | 22.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f0cce08010fcbe7663224fe73d57fb38002ad482951021dee31d0908fd23737
|
|
BLAKE2b-256 checksum How to use checksums |
95816e3e98db3a362d63d2f5517083f21bb7664facf0cff7bad773533c4e1b30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.23.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.5
|
Release files / edgerun_ether-0.3.3-py3-none-any.whl
| Download URL | edgerun_ether-0.3.3-py3-none-any.whl |
|---|---|
| Size | 64.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd317ebcf69894d148f268c0905021f8b7a85307bf641cc4ea3e4d77e993278f
|
|
BLAKE2b-256 checksum How to use checksums |
b293b4fbac349e9026239a372c720dd16674e258c9d6b9cd5511637e3198c527
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.23.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.5
|
Security for edgerun-ether 0.3.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.