| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
fixes #53
|
|
|
|
|
|
|
|
|
| |
The Script class has been made private as the script field
of the Storyboard class. All script-related functions are
now accessible as methods of the storyboard class.
In other news:
Made the script path in script-example.py pwd resilient.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for a testbed based on Docker containers running on
the local host. Bridging the containers can be done using built-in
Linux bridging or using OpenVSwitch bridges.
A new resource 'executor' has been added to abstract away command
execution on nodes on the testbed. Executors have been created for
local command execution, docker exec based command execution and
SSH-based command execution. This has also been changed in the
prototypes to execute using the correct executor.
|
|
|
|
| |
implements #27
|
|
|
|
|
|
|
|
| |
After the refactor of ssh_support to use the native paramiko way to
setup an ssh connection via a proxy, rumba-access stopped working,
since it relied on the exporting of the proxy command to
ssh_info. This commit updates rumba-access to take the refactor into
account.
|
|
|
|
|
|
|
|
|
| |
Temporary files such as ssh_info, the rspecs, logs, ... are now
created in /tmp/rumba to avoid too many files being created and never
removed. The VM images and jFed CLI are kept in ~/.cache/rumba to
avoid redownloading every reboot.
Closes #18, #19
|
|\ |
|
| |
| |
| |
| |
| | |
This reverts the script to its original state since it was not
functioning properly.
|
| |
| |
| |
| | |
This fixes some errors in the rumba access script.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The proxy command was not added to the file generated with ssh
info. This adds it, and changes the access script to use it if it is
there.
|
|/ |
|
| |
|
|
|
|
|
| |
other:
fix to democonf2rumba jfed arguments
|
| |
|
|
|
|
|
| |
This splits experiment.run() into 4 different operations: swap_in,
install_prototype, bootstrap_prototype and swap_out.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
master-tester
Technical merge
|
| |
|
|
|
|
|
|
| |
Deep reworking of the testing tool, it can be provided with a (demo-like)
.conf file, a testbed and a prototype, and it auto-runs the experiment.
Removed generated testing scripts.
|
|
|