oarsh(1) [debian man page]
oarsh(1) OAR commands oarsh(1) NAME
oarsh - remote shell connector for OAR batch scheduler. oarcp - oarsh compagnon to copy files from a node or to a node. SYNOPSIS
oarsh [OPTIONS] <NODENAME> [COMMAND] oarcp [OPTIONS] [NODENAME:]<PATHNAME> [NODENAME:]<PATHNAME> DESCRIPTION
Connect a node from the submission frontal of the cluster or any node. OPTIONS
oarsh uses OpenSSH client (the ssh command) underneath to perform the connection. Thus any OpenSSH option can be used. ENVIRONMENT
OAR_JOB_ID From the frontal of the cluster or any node, specify the Id of the job oarsh must connect to. OAR_JOB_KEY_FILE Specify a job key oarsh must use, e.g. the one that was used for the submission of the job you want to connect to. This is mandatory when connecting to a node of a job from a host that does not belong to the nodes managed by the OAR server the job was submitted to. The -i option may be used as well. CONFIGURATION
In order to provide the user with the ability to use oarsh to connect both the nodes of his job or other hosts that live out of the scope of his job, oarsh tries to read two configuration files: first ~/.oarsh-host-include then ~/.oarsh-hosts-exclude. If exist, those files must contain one regular expression matching a hostname per line. At execution time, if oarsh finds in ~/.oarsh-host-include a match for the hostname used in the command line, it continues with the execution of oarsh, skipping ~/.oarsh-hosts-exclude file. If not, it tries to find a match in ~/.oarsh-hosts-exclude and if one is found, then executes ssh with the same command line. Finally, it no match is found (or for instance, if none of those files exists), it continues with the execution of oarsh. For instance, if all nodes look like name-XXX.domain, one may place ^[^.]+-[[:digit:]]+ in ~/.oarsh-host-include and .* in ~/.oarsh-hosts-exclude and then can use oarsh to connect any host. The feature finally becomes really sexy when one considers placing a symlink to oarsh named ssh, and then can always use the ssh command to connect any host. EXAMPLES
Connecting from within our job, from one node to another one (node23): > oarsh node-23 Connecting to a node (node23) of our job (Id: 4242) from the frontal of the cluster: > OAR_JOB_ID=4242 oarsh node-23 Connecting to a node (node23) of our job that was submitted using a job key: > OAR_JOB_KEY_FILE=~/my_key oarsh node-23 Same thing but using OpenSSH-like -i option: > oarsh -i ~/my_key node-23 NOTES
All OpenSSH features should be inherited by oarsh, for instance X11 forwarding. However, one feature that oarsh does break is the SSH Agent. None of OpenSSH user configuration files (within ~/.ssh directory) are used by oarsh. SEE ALSO
oarsub(1), oardel(1) oarstat(1), oarnodes(1), oarhold(1), oarresume(1) COPYRIGHTS
Copyright 2008 Laboratoire d'Informatique de Grenoble (http://www.liglab.fr). This software is licensed under the GNU Library General Public License. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. oarsh 2012-05-23 oarsh(1)
Check Out this Related Man Page
ganeti-listrunner(8) Version 2.5.2 ganeti-listrunner(8) NAME
ganeti-listrunner - Run commands in parallel over multiple machines SYNOPSIS
ganeti-listrunner -l logdir {-x executable | -c shell-cmd} {-f hostfile | -h hostlist} [-a aux-file] [-b batch-size] [-u username] [-A] DESCRIPTION
ganeti-listrunner is a tool to run commands in parallel over multiple machines. It differs from dsh or other tools in that it asks for the password once (if not using ssh-agent) and then reuses the password to connect to all machines, thus being easily usable even when public key authentication or Kerberos authentication is not available. It can run either a command or a script (which gets uploaded first and deleted after execution) on a list of hosts provided either via a file (one host per line) or as a comma-separated list on the commandline. The output (stdout and stderr are merged) of the remote execution is written to a logfile. One logfile per host is written. OPTIONS
The options that can be passed to the program are as follows: -l logdir The directory under which the logfiles files should be written. -x executable The executable to copy and run on the target hosts. -c shell-cmd The shell command to run on the remote hosts. -f hostfile The file with the target hosts, one hostname per line. -h hostlist Comma-separated list of target hosts. -a aux-file A file to copy to the target hosts. Can be given multiple times, in which case all files will be copied to the temporary directory. The executable or the shell command will be run from the (temporary) directory where these files have been copied. -b batch-size The host list will be split into batches of batch-size which will be processed in parallel. The default if 15, and should be increased if faster processing is needed. -u username Username to connect as instead of the default root username. -A Use an existing ssh-agent instead of password authentication. --args Arguments to pass to executable (-x). EXIT STATUS
The exist status of the command will be zero, unless it was aborted in some way (e.g. ^C). EXAMPLE
Run a command on a list of hosts: listrunner -l logdir -c "uname -a" -h host1,host2,host3 Upload a script, some auxiliary files and run the script: listrunner -l logdir -x runme.sh -a seed.dat -a golden.dat -h host1,host2,host3 SEE ALSO
dsh(1), cssh(1) REPORTING BUGS
Report bugs to project website (http://code.google.com/p/ganeti/) or contact the developers using the Ganeti mailing list (ganeti@google- groups.com). SEE ALSO
Ganeti overview and specifications: ganeti(7) (general overview), ganeti-os-interface(7) (guest OS definitions). Ganeti commands: gnt-cluster(8) (cluster-wide commands), gnt-job(8) (job-related commands), gnt-node(8) (node-related commands), gnt- instance(8) (instance commands), gnt-os(8) (guest OS commands), gnt-group(8) (node group commands), gnt-backup(8) (instance import/export commands), gnt-debug(8) (debug commands). Ganeti daemons: ganeti-watcher(8) (automatic instance restarter), ganeti-cleaner(8) (job queue cleaner), ganeti-noded(8) (node daemon), ganeti-masterd(8) (master daemon), ganeti-rapi(8) (remote API daemon). Ganeti htools: htools(1) (generic binary), hbal(1) (cluster balancer), hspace(1) (capacity calculation), hail(1) (IAllocator plugin), hscan(1) (data gatherer from remote clusters). COPYRIGHT
Copyright (C) 2006, 2007, 2008, 2009, 2010, 2011 Google Inc. Permission is granted to copy, distribute and/or modify under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. Ganeti ganeti-listrunner(8)