Revision fcf2a923

View differences:

software.md
26 26
The jFed software is already installed, you can start it by opening a Terminal and typing `jFed-Experimenter`. The only
27 27
step needed is the copy of the certificate and keys related to your [iMinds Auhority](https://authority.ilabt.iminds.be) 
28 28
account and, if you plan on reproducing big topologies, the configuration of your user on the omni_config file. All
29
these steps are detailed in the README.md of the IoF repository, available in `~/src/iof-tools/README.md`.
29
these steps are detailed in the [README.md](https://github.com/internetonfire/iof-tools/#internet-on-fire-scripts-repo) of the IoF repository.
30 30
In short, you should have your public and your **unencrypted** private keys stored inside the virtual machine in `~/.ssh/iminds.pub` and `~/.ssh/iminds.key`, respectively.
31 31

  
32 32
## Reproducing our specific simulations
33 33

  
34 34
**NOTE:** this section refers to the instructions in an appendix of a paper currently under review.
35
As soon as possible, we will publish the paper under the Publications section.
35
The appendix can be downloaded [here](/docs/Reproducibility.pdf).
36
As soon as possible, we will publish the complete paper under the Publications section.
36 37

  
37 38
As detailed in the *Reproducing IoF* appendix, all the configuration files to reproduce the simulations presented in the paper are
38 39
already available in our repository in the `experimentFiles` directory. In the appendix, there are only the commands to
......
41 42

  
42 43
### Fabrikant simulations
43 44
You will find all the Bird configuration directories on `~/src/iof-tools/experimentFiles/fabrikant/bird-config-files`.
44
As already detailed in the `~/src/iof-tools/experimentFiles/README.md` file, the folders names indicate the type of
45
As already detailed in the [README.md](https://github.com/internetonfire/iof-tools/blob/master/experimentFiles/README.md#experiment-files) file inside the `experimentFiles` folder, the folders names indicate the type of
45 46
MRAI setting and the size of the gadget: `0_$MRAISETTING$_f$GADGETSIZE$n-dest`. You can select the topology you want and
46 47
substitute the *copy* command present on the Appendix with the topoogy directory you want to simulate. Depending on the
47 48
size of the gadget, the parameters of the `./run-simulation.sh` script have to be changed:
......
61 62
run more than a single topology on the same deployed physical nodes some steps are needed: after you have finished a simulation
62 63
you must clean the network config and redeploy the new topology.
63 64
You can find the detailed informations on how to do it 
64
on the repository's `README.md`.
65
on the repository's [README.md](https://github.com/internetonfire/iof-tools/#internet-on-fire-scripts-repo).
65 66

  
66 67

  
67 68
If you don't want to use our pre generated Bird config files, you can use all our toolchain to reproduce the same topology
68
graphs and configurations by yourself. A detailed description on how to use the toolchain is available 
69
[here](https://iof.disi.unitn.it/docs/Reproducibility.pdf)
69
graphs and configurations by yourself. A detailed description on how to use the toolchain is available inside the [README.md](https://github.com/internetonfire/iof-tools/#internet-on-fire-scripts-repo).
70 70

  
71 71
### Internet like simulations
72 72
You will find the Bird configuration directories on `~/src/iof-tools/experimentFiles/elmokashfi/bird-config-files.tgz`.
73 73
The deployment phase on the testbed is the same as the Fabrikant topologies, but you will need more physical resources.
74 74
All our simulations have been run with a 4:1 ratio (4 AS on a single core), so you have to reserve at least 1000 cores.
75
To reproduce exactly our simulations, you must generate the network change on the same Autonomous Systems as we did. You 
76
can find a detailed explanation on how to manage this kind of operation on the repo's `README.md`. Below you will find the
77
list of the AS generating the change and some simple scripts to automate the runs:
75
To reproduce exactly our simulations, you must generate the network change on the same Autonomous Systems as we did.
76
Again, for details on how to manage this kind of operation inside the [README.md](https://github.com/internetonfire/iof-tools/#internet-on-fire-scripts-repo).
77
Below you will find the list of the AS generating the change and some simple scripts to automate the runs:
78 78

  
79 79
Autonomous Systems generating the change:
80 80
1. AS1815

Also available in: Unified diff