Meteor

Environment

PREPARE THE Meteor.jar FILE BEFORE SETTING UP THE EXPERIMENT

Setup

Tools

• VNC client to connect to a cluster using X-window
• ANT to compile, jar, run, and structure directories
• Jxta 2.2 Libraries to write the application
• Distributed Shell to run peers on a cluster

Scripts

• Obtain the list of cluster nodes (say in a file named clusterNodes)
• Create directories for each peer one each cluster node

  for i in `cat clusterNodes`
    do
  	 mkdir XPERIMENTS/$i
  	 mkdir XPERIMENTS/results # where Squid stores its results
  	 for j in 2 3 4 5      #these are for 4 additional peers per node
  	   do
  	      mkdir XPERIMENTS/$i/$j
  	      mkdir XPERIMENTS/$i/$j/results
  	   done
    done
  

• Link the build.xml files (prepared beforehand) to each directory

  for i in `cat clusterNodes` 
    do 
       ln -s build1.xml XPERIMENTS/$i
       ln -s build2.xml XPERIMENTS/$i/2  #Each of these point to different RVs
       ln -s build3.xml XPERIMENTS/$i/3
       ln -s build4.xml XPERIMENTS/$i/4
       ln -s build5.xml XPERIMENTS/$i/5
    done
  

  $i is the name of the node on the cluster.
  Each buildX.xml might differ from the other by passing different command-line arguments to the peers. In my runs,the differences were essentially, the Rendezvous Peers to connect to, the setting of a peer being a rendezvous as opposed to not being a rendezvous, and the setting of graphics or non-graphics mode.
• You should get a structure similar to the example below for one peer:

  XPERIMENTS/
    |-- celepharn
    |   |-- 2
    |   |   |-- build.xml -> ~METEOR/build2.xml
    |   |-- 3
    |   |   |-- build.xml -> ~METEOR/build3.xml
    |   |-- 4
    |   |   |-- build.xml -> ~METEOR/build4.xml
    |   |-- 5
    |   |   |-- build.xml -> ~METEOR/build5.xml
    |   |   
    |   |-- build.xml -> ~METEOR/build1.xml
  ...
  

• Setup the rendezvous peers
• Write a script (say runNode.sh) to start a node

  xp=`basename $HOSTNAME .rutgers.edu`
  cd XPERIMENTS/$xp; ant run &   # Starts the first peer
  sleep 20; cd XPERIMENTS/$xp/2/; ant run &; # Starts the second peer
  sleep 20; cd XPERIMENTS/$xp/3/; ant run &; # Starts the third peer
  sleep 20; cd XPERIMENTS/$xp/4/; ant run &; # Starts the fourth peer
  sleep 20; cd XPERIMENTS/$xp/5/; ant run &; # Starts the fifth peer
  

• dsh -g $1 -c -d 80 runNode.sh
  

  Here -g is the group file with names of the cluster nodes
  -c is for concurrent starts, -d is the delay in seconds
  
  
• Once experiments are done all processes have to be terminated and the cache diretory for each peer deleted.

  for i in `cat clusterNodes`
    do
       rsh $i killall java  
       rm -rf XPERIMENTS/$i/.jxta/cm
       for j in 2 3 4 5
         do
           rm -rf XPERIMENTS/$i/$j/.jxta/cm
         done
    done
  

Sequence of operations

• Start the Bootstrap node, that should have a shell interface and a graphical configuration
• Start all subsequent Rendezvous peers that are pointed to in the buil[2-5].xml files (to lighten the load on the Main bootstrap node).
• Run the dsh script on as many nodes as needed using an appropriate (for example .dsh/group/clusterNodesH) filename.
• Wait for the peers to stabilize (sending messages, etc...)
• Type commnads at the jxtashell Prompt line (status, sendmessage, querys, etc...)
• Clean up cache directories and kill all running processes

Command-Line arguments

Deployment setup

Meteor Shell Commands

Packaging Meteor using Java Network Launching Protocol (JNLP)

• Have a working Jar version of the application
• Create a .jnlp file for the application
• Transform all parts of the code that need a resource (config file, property etc...) to use the ClassLoader.getResource. This is because JNLP uses Jars only so all additional resources have to be bundled inside the Jar.
• Make sure that the JXTA URLs are created using the IDFactory.jxtaURL and not "new URL"
• Sign every Jar
• Add the JNLP application mime type to the Web server

<?xml version="1.0" encoding="utf-8"?> 
<jnlp spec="1.0+" codebase="file:///c:/mydocu~1/jxtalib/"
     > 
<information> 
	<title>Meteor App</title> 
	<vendor>Sun Microsystems, Inc.</vendor> 
	<description>DHT Application</description> 
	<description kind="short">
	   </description> 
	<offline-allowed/> 
</information> 

<security> 
   <all-permissions/> 
</security> 

<resources> 
	<j2se version="1.4+"/> 
	<jar href="Meteor.jar" download="eager"/> 
	<jar href="cryptix-asn1.jar" download="eager"/>
	<jar href="cryptix32.jar" download="eager"/>
	<jar href="javax.servlet.jar" download="lazy"/>
	<jar href="jaxen.jar" download="eager"/>
	<jar href="jdom.jar" download="eager"/>
	<jar href="jxta.jar" download="eager"/>
	<jar href="jxtaext.jar" download="lazy"/>
	<jar href="jxtaptls.jar" download="eager"/>
	<jar href="jxtasecurity.jar" download="eager"/>
	<jar href="jxtashell.jar" download="eager"/>
	<jar href="log4j.jar" download="eager"/>
	<jar href="org.mortbay.jetty.jar" download="lazy"/>
   <jar href="bcprov-jdk14.jar" download="eager"/>	
	<jar href="saxpath.jar" download="eager"/>
	<jar href="xerces.jar" download="eager"/>
</resources> 

<application-desc main-class="meteor.lookup.Loader"/> 
	
</jnlp> 

InputStream is = this.getClass().getClassLoader().getResourceAsStream("conf.properties");
BufferedReader lr = new BufferedReader(new InputStreamReader(is));

PropertyConfigurator.configure(meteor.lookup.Loader.class.getClassLoader().getResource("log4j.properties"));

 IDFactory.fromURL(IDFactory.jxtaURL(refPeerGroupSpec)));
 

 keytool -genkey -keystore myKeystore -alias myself 

keytool -selfcert -alias myself -keystore myKeystore 

jarsigner -keystore myKeystore test.jar myself