[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] r20853 - in gnunet-planetlab: . gnunet_automatic_deployment

From: gnunet
Subject: [GNUnet-SVN] r20853 - in gnunet-planetlab: . gnunet_automatic_deployment
Date: Mon, 2 Apr 2012 15:02:13 +0200

Author: wachs
Date: 2012-04-02 15:02:13 +0200 (Mon, 02 Apr 2012)
New Revision: 20853

- updated scripts and README

Modified: gnunet-planetlab/README.txt
--- gnunet-planetlab/README.txt 2012-04-02 12:46:54 UTC (rev 20852)
+++ gnunet-planetlab/README.txt 2012-04-02 13:02:13 UTC (rev 20853)
@@ -1,32 +1,63 @@
+Automation is done with a set of scripts which let the user enter the 
+planetlab nodes in a list and eventually ends up installing the GNUnet 
+software on these nodes including all the gnunet dependencies.
-To add the nodes to current buildmaster, perform the following steps:
+The latest version of the automation toolset is located in the 
+gnunet_automatic_deployment/ subdirectory and basically provides you 
+this scripts:
-1. svn co  on your 
local machine.
-2. add the nodes in nodes.txt
-3. execute the script 
-. ./
+Installs GNUnet from SVN on all nodes
+Installs all required dependencies from the repository or from source
+Uninstalls outdated packages
-Following are the tasks performed in this automation:
+Starts GNUnet on all nodes
-1. Master configuration file is Generated with respect to the provided nodes 
in nodes.txt
+Stops GNUnet on all nodes
-2. Master configuration file is uploaded at Buildmaster node.
+Updates the GNUnet installation on all nodes
-3. Buildmaster is configured with newly configuration file.
+To use the scripts create a file called nodes.txt which contains the 
+hostnames of the planetlab nodes you want to install GNUnet on. You can 
+use the tools from the planetlab-api/ subdirectory to:
-4. All the required dependencies for the GNUnet is installed at the provided 
planetlab  nodes in nodes.txt.
+Add all nodes in the "booted" state to your slice
+Get all list of all nodes in the "booted" state assigned to your slice
+Before using the using the scripts, have a look at the first lines of 
+the scripts. You have to edit the lines:
-5. All the required dependencies for buildslave is installed at planetlab 
+# Planetlab username
+# Number of ssh parallelism
+# Timeout for ssh operations
+# Destination directory on the nodes
+# File containing nodes
-6. Buildslave is configured at the planetlab nodes with the same credentials 
provided in master configuration file.
+To run the scripts you need a running ssh-agent with your credential to
+your slice.
-7. Buildslave is started.
+Here a short example how to install GNUnet on all nodes of your slice
+and start it:
-Now, User can force build from Buildmaster to each respective planetlab nodes.
+Get a list of all booted nodes
+./ -u -p
+cp nodes_booted ../gnunet_automatic_deployment/nodes.txt
+Start ssh-agent
+ssh-agent bash
+Install GNUnet
+Start GNUnet

Modified: gnunet-planetlab/gnunet_automatic_deployment/
--- gnunet-planetlab/gnunet_automatic_deployment/       
2012-04-02 12:46:54 UTC (rev 20852)
+++ gnunet-planetlab/gnunet_automatic_deployment/       
2012-04-02 13:02:13 UTC (rev 20853)
@@ -1,16 +1,27 @@
+# Change the following lines 
+# Planetlab username
+# Number of ssh parallelism
+# Timeout for ssh operations 
+# Destination directory on the nodes
+# File containing nodes
-cmd_pssh="pssh -O StrictHostKeychecking=no -t $timeout -p $parallelism -v -l 
tum_dht_testing -h $working_nodes_filtered_file -P"
-cmd_pscp="pscp -O StrictHostKeychecking=no -p $parallelism -v -l 
tum_dht_testing -h $working_nodes_filtered_file "
+cmd_pssh="pssh -O StrictHostKeychecking=no -t $timeout -p $parallelism -v -l 
$username -h $working_nodes_filtered_file -P"
+cmd_pscp="pscp -O StrictHostKeychecking=no -p $parallelism -v -l $username -h 
$working_nodes_filtered_file "
 #rm -rf tmp
 echo "Prepare distribution tarball"
 mkdir tmp 2> /dev/null

reply via email to

[Prev in Thread] Current Thread [Next in Thread]