aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md85
1 files changed, 63 insertions, 22 deletions
diff --git a/README.md b/README.md
index d6e0839..25d79fd 100644
--- a/README.md
+++ b/README.md
@@ -3,17 +3,20 @@
Rumba is part of ARCFIRE 2020, Work Package 3. It is a framework in
Python which allows user to write a Python script to define a RINA
network. The physical graph needed for this RINA network is then
-calculated and realised on one of the supported testbeds. Next, one of
-the supported RINA prototypes is installed. After installation, the
-network is bootstrapped. For an example of such a Python script, have
-a look at the examples/ folder.
+calculated and realised on one of the supported testbeds. Next, if the
+user requests this, one of the supported RINA prototypes is
+installed. The network is then bootstrapped on the available
+nodes. Finally, the experiment can be swapped out of the testbed. For
+an example of such a Python script, have a look at the examples/
+folder.
## Workflow, both external and internal:
1. User defines the network graph, creating instances of model.Node
- and model.DIF classes
+ and model.DIF classes
- 2. User creates an instance of a Testbed class
+ 2. User creates an instance of a Testbed class. See below for
+ testbed specific configuration
3. User creates an instance of prototype.Experiment class, passing
the testbed instance and a list of Node instances
@@ -23,26 +26,35 @@ a look at the examples/ folder.
per-node IPCPs, registrations and enrollment, ready to be
used by the plugins
- 4. User calls run() on the prototype.Experiment instance:
+ 4. User calls methods on the prototype.Experiment instance:
- 1. run() calls Testbed.swap_in(), passing the Experiment, and
- filling in the missing information
+ 1. swap_in() swaps the experiment in on the testbed, and fills in
+ the missing information in the model.
- 2. run() calls a prototype-specific setup function, to create the
- required IPCPs, perform registrations, enrollments, etc.
+ 2. install_prototype() installs the chosen prototype on the
+ testbed. Currently an Ubuntu image is assumed.
- 3. Perform tests (TODO)
+ 3. bootstrap_prototype() calls a prototype-specific setup function,
+ to create the required IPCPs, perform registrations,
+ enrollments, etc.
- 4. run() calls Testbed.swap_out()
+ 4. swap_out() swaps the experiment out of the testbed.
## Installation
+ For Debian and Ubuntu, the following command will ensure that the
+ required dependencies are installed (replace python-dev with python3-dev
+ if using Python 3):
+
+ # apt-get install build-essential libssl-dev libffi-dev python-dev
+
Rumba can be found on the
[PyPi](https://pypi.python.org/pypi/Rumba) and can thus be
installed through pip, by using `pip install rumba`. However, to
install the latest version, after cloning the repository, a user
can also issue `python setup.py install`.
+
## Supported prototypes
* [IRATI](https://github.com/IRATI/stack) is an open source
@@ -62,10 +74,30 @@ a look at the examples/ folder.
* [QEMU](http://wiki.qemu-project.org/Main_Page) is a generic and
open source machine emulator and virtualizer.
+ A minimal QEMU testbed is defined as follows:
+
+ tb = qemu.Testbed(exp_name = "twolayers",
+ username = "root",
+ password = "root")
+
+ A user can optionally also specify the path to a bzImage and to an
+ initramfs. If they are not specified, the latest buildroot image
+ for the specific prototype will be downloaded. (Around 40 MB in
+ size) The login to those images is root/root.
+
* [Emulab](https://www.emulab.net/) is a network testbed, giving
researchers a wide range of environments in which to develop,
debug, and evaluate their systems.
+ An emulab testbed instance is defined as follows:
+
+ tb = emulab.Testbed(exp_name = "rochefort10",
+ username = "ricksanchez")
+
+ A password can also be provided but is not necessary when an SSH
+ key has been added. Optionally, a project name, a different testbed
+ URL and a custom image can be specified.
+
* [jFed](http://jfed.iminds.be/) is a Java-based framework for
testbed federation.
@@ -82,16 +114,25 @@ a look at the examples/ folder.
Here the experiment name is rochefort10, the user's name is
ricksanchez, and the certificate can be found in
- /home/morty/cert.pem. Please use an absolute path for cert_file for
- now.
+ /home/morty/cert.pem. An absolute path must be used for
+ cert_file. Optionally a custom image can be selected.
- Before running the experiment it is wise to use an SSH agent to
- avoid having to enter the passphrase for every login to a node by
- the framework if you are not on an IPv6 enabled network. (Apart
- from asking for the passphrase to login to the nodes, the framework
+ Before running the rumba you must run an SSH agent in same terminal.
+ This will also avoid you having to enter the passphrase for every
+ login to a node by the framework if you are not on an IPv6 enabled network.
+ (Apart from asking for the passphrase to login to the nodes, the framework
will always ask for the passphrase since it is needed by the jFed
CLI as well.) In order to start an SSH agent and to add the
- certificate, simply perform the following commands:
+ certificate, type the following commands:
+
+ $ eval `ssh-agent`
+ $ ssh-add /home/morty/cert.pem
+
+## Accessing nodes after swap-in
+
+ To access a node once the experiment swapped in, use the following
+ command (in the same terminal where ssh-agent was run in case of jFed):
+
+ $ rumba-access $NODE_NAME
- eval `ssh-agent`
- ssh-add /home/morty/cert.pem
+ Where $NODE_NAME is the name of the node to access. \ No newline at end of file