TakTuk: Difference between revisions
Xdelaruelle (talk | contribs) m (Tip of the month TakTuk moved to Using TakTuk) |
Xdelaruelle (talk | contribs) m (add intro: the one available on 2007-03 Newsletter) |
||
Line 1: | Line 1: | ||
{{Type|Tip}} | {{Type|Tip}} | ||
{{Maintainer|Pierre Lemoine}} | {{Maintainer|Pierre Lemoine}} | ||
During an experience on G5k, you often want to run programs or scripts on all his nodes simultaneously, to get the data to the reserved nodes for example. This could be done sequentially with a loop function, but this method doesn't scale well. That's why a parallel launcher named TakTuk has been installed on each G5k site. | |||
= Short Explanation about how it work = | = Short Explanation about how it work = | ||
To speed up the execution of a command on a large number of nodes, TakTuk | To speed up the execution of a command on a large number of nodes, TakTuk |
Revision as of 16:12, 29 March 2007
During an experience on G5k, you often want to run programs or scripts on all his nodes simultaneously, to get the data to the reserved nodes for example. This could be done sequentially with a loop function, but this method doesn't scale well. That's why a parallel launcher named TakTuk has been installed on each G5k site.
Short Explanation about how it work
To speed up the execution of a command on a large number of nodes, TakTuk
- uses a tree to launch programs on all reserved nodes.
- initiates a few connections in parallel (the deployment window) and distributes the remaining deployment work to already
deployed peers using an adaptive work-stealing algorithm (Extract of A guide of TakTuk use by Guillaume Huard).
Therefore, for taktuk to operate correctly, peers should be able to connect to each other. By default, TakTuk use ssh connections. So to check if Taktuk execution will work, follow instructions on this page: Test key authentication
Using TakTuk with the base environment
Prerequisites
You have a reservation:
Therefore you're on the reserved node:
Connections from this node and between nodes with your account are possible
Using Taktuk to launch scripts
To launch scripts simultaneously on each node:
users@node-15.site.grid5000.fr :
|
taktuk -f $OAR_FILE_NODES broadcast exec [/home/site/user/testScript.sh] |
Note: do not forget to type the characters [
and ]
By default, Taktuk displays a lot of informations but it might not be necessary. So you can add some options on command line to modify correctly the output [c'est pas trés clair pour l'utilité des options connector et status]:
-o connector -o status -o output='"$host: $line\n"'
Example:
To know if time clock are synchronised on each node (Result formated correctly)
users@node-15.site.grid5000.fr :
|
taktuk -o connector -o status -o output='"$host: $line\n"' -f $OAR_FILE_NODES broadcast exec [date] |
Output
node-101.bordeaux.grid5000.fr: Fri Mar 23 09:38:46 CET 2007 node-23.bordeaux.grid5000.fr: Fri Mar 23 09:38:46 CET 2007 node-24.bordeaux.grid5000.fr: Fri Mar 23 09:38:46 CET 2007 node-67.bordeaux.grid5000.fr: Fri Mar 23 09:38:46 CET 2007 node-97.bordeaux.grid5000.fr: Fri Mar 23 09:38:46 CET 2007
To know cpu's installed on nodes:
plemoine@node-101:$ taktuk -o connector -o status -o output='"$host: $line\n"' -f $OAR_FILE_NODES broadcast exec ["cat /proc/cpuinfo | grep 'model name'"] | uniq
Output
node-101.bordeaux.grid5000.fr: model name : Intel(R) Xeon(TM) CPU 3.00GHz node-23.bordeaux.grid5000.fr: model name : AMD Opteron(tm) Processor 248 node-24.bordeaux.grid5000.fr: model name : AMD Opteron(tm) Processor 248 node-67.bordeaux.grid5000.fr: model name : Intel(R) Xeon(TM) CPU 3.00GHz node-97.bordeaux.grid5000.fr: model name : Intel(R) Xeon(TM) CPU 3.00GHz
Using TakTuk with your own environment and no taktuk installation on it
Prerequisites
Starting to make a reservation:
Deploy environment:
Using Taktuk to launch programs
[Ca ne me dit pas ce qu'il faut faire pour executer sans taktuk, mais seulement comment executer en tant que root : à mon avis, il manque une étape] To execute command as root for update , you have to use the following option: "-l root" as the first one used on the command line: