Simulation and emulation experiments are widely used for verifying new approaches as well as existing theories in communication networks. In this report, we present a tool for performing automated experiments in distributed testbeds such as Emulab or PlanetLab. Using an intuitive configuration file syntax, large sets of complex command sequences can be executed with minimal user interaction. As a result, repeated execution of experiments and the generation of controlled, documented, and reproducible results is greatly facilitated.
Metadata
Release files for sshlauncher 2.1
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 | Actions |
|---|---|---|---|---|
| sshlauncher-2.1.tar.gz | 8.7 kB | Without provenance | Details for sshlauncher-2.1.tar.gz |
Release files / sshlauncher-2.1.tar.gz
| Download URL | sshlauncher-2.1.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c30f8a26e67c7ec5f80f7fefae9af9e62198f3c1223d1a8198e97f500bcc3a8
|
|
BLAKE2b-256 checksum How to use checksums |
40bf4beb0e491567b43fb1ffea6aa6a5d980630b886cb14a183f9d6d88c8843e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sshlauncher 2.1
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.