condor_glidein

add a Globus resource to a Condor pool

Synopsis

condor_glidein [- -help] [- -basedir basedir] [- -archdir dir] [- -localdir dir] [- -setuponly] [- -runonly] [- -scheduler name] [- -queue name] [- -project name] [- -memory MBytes] [- -count CPU count] [- -vms VM count] [- -idletime minutes] [- -runtime minutes] [- -anybody] [- -admin address] [- -genconfig] [- -useconfig filename] {- -contactfile filename } | Globus contact string

   

Description

condor_glidein allows the temporary addition of a Globus resource to a local Condor pool. The addition is accomplished by installing and executing some of the Condor daemons on the Globus resource. A condor_shadow.globus job appears in the queue of the local Condor pool for each glidein request. To remove the Globus resource from the local Condor pool, use condor_rm to remove the condor_shadow.globus job from the job queue.

You must have an X.509 certificate and access to the Globus resource to use condor_glidein. The Globus software must also be installed.

Globus is a software system that provides uniform access to different high-performance computing resources. When specifying a machine to use with Globus, you provide a Globus contact string. Often, the contact string can be just the hostname of the machine. Sometimes, a more complicated contact string is required. For example, if a machine has multiple schedulers (ways to run a job), the contact string may need to specify which to use. See the Globus home page, www.globus.org for more information about Globus.

condor_glidein works in two steps: set up and execution. During set up, a configuration file and the Condor daemons master, startd and starter are installed on the Globus resource. Binaries for the correct architecture are copied from a central server. To obtain access to the server, send e-mail to condor-admin@cs.wisc.edu with your X.509 certificate name. Globus software version 1.1.3 does not yet include the Globus program gsincftp, the Globus secure version of ftp. condor_glidein needs this program. Install gsincftp, obtained from http://www.globus.org/datagrid/deliverables/gsiftp-tools.html. Set up need only be done once per machine and version of Condor. The execution step starts the Condor daemons running through the resource's Globus interface.

By default, all files placed on the remote machine are placed in $(HOME)/Condor_glidein. Each use of condor_glidein will generate spool and log files on the Globus resource. These files should be occasionally removed.

Options

Supported options are as follows:

- -help

Display brief usage information and exit

- -basedir basedir

Specifies the base directory on the Globus resource used for placing files. The default file is $(HOME)/Condor_glidein on the Globus resource.

- -archdir dir

Specifies the directory on the Globus resource for placement of the executables. The default value for - -archdir , given according to version information on the Globus resource, is basedir/<condor-version>-<Globus canonicalsystemname> An example of the directory (without the base directory on the Globus resource) for Condor version 6.1.13 running on a Sun Sparc machine with Solaris 2.6 is 6.1.13-sparc-sun-solaris-2.6

- -localdir dir

Specifies the directory on the Globus resource in which to create log and execution subdirectories needed by Condor. If limited disk quota in the home or base directory on the Globus resource is a problem, set - -localdir to a large temporary space, such as /tmp or /scratch

- -contactfile filename

Allows the use of a file of Globus contact strings, rather than the single Globus contact string given in the command line. For each of the contacts listed in the file, the Globus resource is added to the local Condor pool.

- -setuponly

Performs only the placement of files on the Globus resource. This option cannot be run simultaneously with - -runonly

- -runonly

Starts execution of the Condor daemons on the Globus resource. If any of the files are missing, exits with an error code. This option cannot be run simultaneously with - -setuponly

- -scheduler name

Selects the Globus job scheduler type. Defaults to fork. NOTE: Contact strings which already contain the scheduler type will not be overridden by this option.

- -queue name

The argument name is a string which specifies which job queue is to be used for submission on the Globus resource.

- -project name

The argument name is a string which specifies which project is to be used for submission on the Globus resource.

- -memory MBytes

The maximum memory size to request from the Globus resource (in megabytes).

- -count CPU count

Number of CPUs to request, default is 1.

- -vms VM count

Number of of virtual machines to split up the allocated resources into, default is 1.

- -idletime minutes

How long the Condor daemons on the Globus resource can remain idle before the resource reverts back to its former state of not being part of the local Condor pool. If the value is 0 (zero), the resource will not revert back to its former state. In this case, the Condor daemons will run until the runtime time expires, or they are killed by the resource or with condor_rm. The default value is 20 minutes.

- -runtime minutes

How long the Condor daemons on the Globus resource will run before shutting themselves down. This option is useful for resources with enforced maximum run times. Setting runtime to be a few minutes shorter than the allowable limit gives the daemons time to perform a graceful shutdown.

- -anybody

Sets the Condor START expression to TRUE to allow any user job which meets the job's requirements to run on the Globus resource added to the local Condor pool. Without this option, only jobs owned by the user executing condor_glidein can execute on the Globus resource. WARNING: Using this option may violate the usage policies of many institutions.

- -admin address

Where to send e-mail with problems. The defaults is the login of the user running condor_glidein at UID domain of the local Condor pool.

- -genconfig

This option creates a local copy of the configuration file used on the Globus resource. The file is called condor_config.glidein.

- -useconfig filename

Install filename as the configuration file on the Globus resource instead of the default configuration file during the set up phase.

Exit Status

condor_glidein will exit with a status value of 0 (zero) upon complete success. The script exits with non-zero values upon failure. The status value will be 1 (one) if condor_glidein encountered an error making a directory, was unable to copy a tar file, encountered an error in parsing the command line, or was not able to gather required information. The status value will be 2 (two) if there was an error in the remote set up. The status value will be 3 (three) if there was an error in remote submission. The status value will be -1 (negative one) if no resource was specified in the command line.

Author

Condor Team, University of Wisconsin-Madison

Copyright

Copyright © 1990-2001 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. No use of the Condor Software Program is authorized without the express consent of the Condor Team. For more information contact: Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu. U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

See the Condor Version 6.2.2 Manual for additional notices.