Changes between Version 2 and Version 3 of Tutorial/HowToTopology
- Timestamp:
- Nov 19, 2007, 6:59:03 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorial/HowToTopology
v2 v3 6 6 This feature is only available in NodeHandler v4 and above. 7 7 8 If you have not done so yet:8 Before going through this tutorial, you should know [wiki:Tutorial/HowToImage how to install a disk image]. 9 9 10 * [http://www.orbit-lab.org/wiki/Registration Register] for an account 11 * [https://www.orbit-lab.org/schedule/ Make a reservation] on the Schedular for a given tesbed 12 * [wiki:Tutorial/HowToImage Image] the nodes of this given testbed with a baseline image that contains nodeAgent v4 (e.g. "baseline-2.2.ndz" or "baseline-2.3.ndz") 10 You should also have installed a disk image with Node Agent v4 on the nodes of the testbed you are using (e.g. "baseline-7.11.ndz"). 13 11 14 As explained [wiki:Tutorial/HowToImage here], at the end of the imaging process 3 files are generated, each containing a topology definition. Assuming you are on the 'grid' testbed, one of this generated file is called 'topo_grid_active.rb' (see attached [attachment:topo_grid_active.rb example]). This file defines a topology which includes all the nodes that were correctly imaged. In other words, this file contains a list of all nodes on the testbed that are currently working and with the correct disk image. 12 === Goal === 15 13 16 You can directly use the topology from this generated 'topo_grid_active.rb' file as a base to build the various node sets within your experiment script.14 In this tutorial, you will learn a simple way to define and use topology in your experiments. 17 15 18 For example, using this topology allows you to define a group of 4 nodes running a given application, without having to explicitly specify the identity of these 4 nodes in you experiment script. Thus the selected nodes for this group is no longer hard coded in the script, but may be for example drawn randomly from the "active" topology at each run of the experiment.16 As explained [wiki:Tutorial/HowToImage here], after installing an image on all the nodes of a testbed, 3 default topologies will be generated. One of them (system:topo:active) defines all the nodes that were correctly imaged. In other words, it contains a list of all nodes on the testbed that are currently working and with the correct disk image. 19 17 20 === Example === 18 In this tutorial, you will use this default active topology to create your own topologies to use in your experiments. 21 19 22 Th e attached script [attachment:tut_topo_1.rb tut_topo_1.rb] presents an example of the user-defined topologies within an experiment script.20 This tutorial's experiment is given in the attached script [attachment:tut_topo_1.rb tut_topo_1.rb]. 23 21 24 22 This file contains extensive comments that should help you understand the different steps involved in defining and using topologies. For more information on the basics of writing and using an experiment script, please refer to the previous tutorials, [wiki:Tutorial/HowtoWriteScripts here] and [wiki:Tutorial/HelloWorld here]. … … 36 34 The experiment screen output should then look like [attachment:grid_2007_08_27_20_45_37-Output.txt this]. And the experiment log file should look like [attachment:grid_2007_08_27_20_45_37.log this]. 37 35 38 You can also access the results of this particular experiment example in the MySQL database, using the experiment ID: "grid_2007_08_27_20_45_37" (please refer to [wiki:Tutorial/AnalyzeResults this page] for more information on accessing the results). 36 You can also access the results of this particular experiment example in the MySQL database, using the experiment ID: "grid_2007_08_27_20_45_37" (please refer to [wiki:Tutorial/AnalyzeResults this page] for more information on accessing the results). 37 38 === More... === 39 40 This other script [attachment:tut_topo_1_more.rb tut_topo_1_more.rb] contains a version of the above script with more optional features.