Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The code has been reformated in a way that it should work with a well know package management tool (ANT). The main benifit of ant is that you need not to compile a class and set the path once you have edited the class. The package management tool handes it all. The build.xml file has been written to set the paths of classes once the code gets compiled. It would require following steps to compile and run.

Code Block
   ant -f build.xml

This command would compile the code and create a directory build in the same folder with all the .class files. To run the code you need to run following command from build directory is needed.

...

 Running code for List of hosts

...

There are different command line  options available for running the code. Running the code without any options would yield basic test for list of host in Initial.txt available at tulip directory. The output would be entries in Result.txt which is in $tulip with best three nodes and RTT's.  The format of Result.txt is Target node followed by first best node its RTT then second and third best in the same manner.

Code Block

Run following command from /afs/slac/package/netmon/tulip/build if Class path is not set 
 java tulip.core.AutomateTest

...

Running Code for specific Target

...

The second option available for TULIP command line is running the code for specified target we are trying to locate. The result would be the last line in Result.txt file with the above mentioned format. Following command is required to run the code to locate your specified target.

Code Block

java
Code Block

 java tulip.core.AutomateAutomateTest target 128.2.115.21 startNewTest

Selection of Planet Lab Sites

...

 This script is deployed in crontab which generate a all the available PlanetLab sites. The list is gather through the following link

Code Block
 http http://www.scriptroute.org:3967/

...