34 | | Finally, using the '''Node Handler''' (via a dedicated experiment called ''imageNodes'', which will be described [wiki:Tutorial/HowToImage later]), the user can quickly load hard disk images onto the nodes of his/her experiment. This ''imaging process'' allows different groups of nodes to run different OS images. It relies on a scalable multicast protocol and the operation of a disk-loading ''Frisbee'' server from M. Hibler et al. ([http://www.cs.utah.edu/flux/papers/frisbee-usenix03-base.html link]). |
| 34 | Finally, using the '''Node Handler''' (via a dedicated ''image nodes''experiment, which will be described [wiki:Tutorial/HowToImage later]), the user can quickly load hard disk images onto the nodes of his/her experiment. This ''imaging process'' allows different groups of nodes to run different OS images. It relies on a scalable multicast protocol and the operation of a disk-loading ''Frisbee'' server from M. Hibler et al. ([http://www.cs.utah.edu/flux/papers/frisbee-usenix03-base.html link]). Similarly, the user can also use the '''Node Handler''' save the image of a node's disk into an archive file. |
| 35 | |
| 36 | The user can perform all these actions on the testbed(s) via the generic command '''orbit''', which is the access point to control the '''Node Handler''', his/her experiment, and the nodes on the testbed(s). |
| 37 | {{{ |
| 38 | # To see a list of available commands |
| 39 | orbit help |
| 40 | |
| 41 | # To see the usage and more help about a particular command, e.g. "load" |
| 42 | orbit help load |
| 43 | }}} |