VO-LOGIN(1)               BSD General Commands Manual              VO-LOGIN(1)

NAME
     vo-login - virtual login command for creating a MyCluster session

SYNOPSIS
     vo-login [-d] [-h] [-ec2] [-S] [-n <jobs:size>] [-s] [-H <conf_file>]
              [-W <mins>]
     vo_pool [-d] [-h] [-S] [-n <jobs:size>] [-s] [-H <conf_file>] [-W <mins>]
     ec2_pool [-d] [-h] [-S] [-n <jobs>] [-s]

DESCRIPTION
     The vo-login command provisions compute nodes from remote clusters, or
     Amazon.com EC2, into a private Condor/SGE cluster.  The command creates a
     new login shell session with GNU screen that allows the user to detach
     from the session with the "detach" command, and to re-attach to a running
     session from a different terminal with the "vo-attach" command.

     vo_pool is the non-GNU screen version of the vo-login command that is
     used for provisioning compute nodes from remote clusters. The prerequi‐
     stes are that the user has an account on the remote cluster, and that
     MyCluster is installed in that user account.

     ec2_pool is the non-GNU screen version of the vo-login command that is
     used for provisioning compute nodes from Amazon.com EC2.  The prerequi‐
     stes are that the user has setup the EC2 command line tools on the desk‐
     top, and that the _MYCLUSTER_AMI environment variable is set with the EC2
     AMI to use.

     The options are as follows:

     -d      Prints additional debug messages to standard error.

     -h      Prints a very verbose usage message and exits.

     -ec2    Specifies that compute nodes should be provisioned from Ama‐
             zon.com EC2. Default: remote cluster.

     -S      Specifies that a SGE cluster should be created. Default: Condor.

     -n <jobs:size>
             Specifies the number of job proxies and the size of each job
             proxy that are submitted at each site; e.g. -n 2:16 specifies 2
             starter jobs of size 16 processors each. Default: -n 1:1

     -n <jobs>
             Specifies the number of job proxies that are submitted to EC2.

     -s      Specifies that the desktop home directory should not be mounted
             across clusters

     -H <conf_file>
             Specifies the configuration file listing the cluster gateway
             nodes participating in this session. The configuration file may
             also contain site specific configuration settings for the ses‐
             sion. Default: $HOME/vo.conf

             The vo-login configuration file is an ASCII file listing the
             clusters contributing to a virtual organization. Comments in the
             file are introduced with "#", and the _MYCLUSTER_THROTTLE and
             _MYCLUSTER_JOB_SIZE configuration variables are used to specify
             site specific job proxy submission requirements; e.g. tg-
             login.tacc.utexas.edu%_MYCLUSTER_THROTTLE=2:_MYCLUS‐
             TER_JOB_SIZE=32 specifies 2 job proxies of size 32 processors
             each submitted to the cluster tg-login.tacc.utexas.edu. Note that
             if the _MYCLUSTER_MAX_THROTTLE specification is set at the par‐
             ticipating sites, the starter submission requirements are treated
             as inital "hints" by the system. MyCluster will attempt to move
             pending job proxies between sites, to minimize their queue wait
             times.

     -W <mins>
             Specifies the wall time limit for the job proxies when they are
             submitted to the remote sites. The unit of the wall clock limit
             is in minutes.

AUTHOR
     Edward Walker, ewalker@tacc.utexas.edu, Texas Advanced Computing Center
     (TACC)

HISTORY
     vo-login appeared in v2.0 of MyCluster.

BSD                              June 1, 2005                              BSD