Pegasus has a few dependencies:
-
Java 1.6 or higher. Check with:
$ java -version java version "1.6.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0_07-164) Java HotSpot(TM) Client VM (build 1.6.0_07-87, mixed mode, sharing) -
Python 2.4 or higher. Check with:
$ python -v Python 2.6.2 Condor 7.4 or higher. See http://www.cs.wisc.edu/condor/ for more information. You should be able to run
condor_qandcondor_status.
-
Globus 4.0 or higher. Globus is only needed if you want to run against grid sites or use GridFTP for data transfers. See http://www.globus.org/ for more information. Check Globus Installation
$ echo $GLOBUS_LOCATION /path/to/globus/installMake sure you source the Globus environment
$ GLOBUS_LOCATION/etc/globus-user-env.shCheck the setup by running:
$ globus-version 5.0.1
To use Pegasus, add the bin/ directory to your PATH.
Example for bourne shells:
$ export PATH=/some/install/pegasus-3.0.0/bin:$PATH
Note
Pegasus 3.0 is different from previous versions of Pegasus in that it does not require PEGASUS_HOME to be set or sourcing of any environtment setup scripts.
The preferred way to install Pegasus is with native (RPM/DEB)
packages. Using this package, Pegasus is installed into
/opt/pegasus/{major_version}.{minor_version}, and the
packages have {major_version}.{minor_version} in the package name. This
allows for multiple installed Pegasus versions installed. For example, if
you installed Pegasus 2.4.3 and 3.0.0, you will have: with:
/opt/pegasus/2.4/ /opt/pegasus/3.0/ /opt/pegasus/3.1/
Add the Pegasus repository to yum by creating a file named
/etc/yum.repos.d/pegasus.repo with the
content:
# Pegasus 3.1 [Pegasus31] name=Pegasus31 baseurl=http://pegasus.isi.edu/wms/download/3.1/yum/rhel/$releasever/$basearch/ gpgcheck=0 enabled=1
Search for, and install Pegasus:
# yum search pegasus pegasus-3.1 : Pegasus Workflow Management System # yum install pegasus-3.1 Running Transaction Installing : pegasus-3.1 Installed: pegasus-3.1 :3.1.0-1 Complete!
To be able to install and upgrade from the Pegasus APT repository, you will have to trust the repository key. You only need to add the repository key once.
# gpg --keyserver keyring.debian.org --recv-keys 81C2A4AC # gpg -a --export 81C2A4AC | apt-key add -
Add the Pegasus apt repository to your
/etc/apt/sources.list file, replacing [DEBVERSION]
with either lenny or squeeze:
deb http://pegasus.isi.edu/wms/download/3.1/apt/debian [DEBVERSION] main
Install Pegasus with apt-get :
# apt-get update ... # apt-get install pegasus-3.1
The Pegaus prebuild tarballs can be downloaded from the Pegasus Download Page.
Use these tarballs if you already have Condor installed or prefer to keep the Condor installation separate from the Pegasus installation.
-
Untar the tarball
$ tar zxf pegasus-*.tar.gz
-
include the Pegasus bin directory in your PATH
$ export PATH=/path/to/pegasus-3.0.0:$PATH
For convenience, there is Pegasus WMS tarballs which has Condor included. This way you can install Pegasus and Condor at the same time, with just minor configuration to get up and running.
-
Untar the tarball
$ tar zxf pegasus-wms-*.tar.gz
-
Edit the Condor Configuration file. The configuration file is currently configured to run only as a submit side (Runs schedd) supporting schedule, local and grid universe. If you want to use it for gt4, lsf, pbs or condor-c additional configuration changes may be required. Please check the Condor Manual for appropriate parameters.
2 parameters need to change at this point. Change !!PEGASUS_HOME!! to the actual path where PEGASUS_WMS is installed and CHANGE !!USER!! to the user who will receive email in case of error. (This can be just your username )
$ vim $PEGASUS_HOME/etc/condor_config RELEASE_DIR = !!PEGASUS_HOME!! # CHANGE THIS TO PATH OF PEGASUS_WMS INSTALLATION WILL GET EMAIL IN CASE OF ERROR.
-
Set up the environment:
$ export PATH=PEGASUS_HOME/bin:PEGASUS_HOME/condor/bin:$PATH $ export CONDOR_CONFIG=PEGASUS_HOME/etc/condor_config
-
Start Condor by running ./sbin/condor_master
$ ./sbin/condor_master
-
Verify that Condor is up by running the condor-q command
$ condor_q -- Submitter: gmehta@smarty.isi.edu : <128.9.72.26:60126> : smarty.isi.edu ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD 0 jobs; 0 idle, 0 running, 0 held
Basic system configuration is controlled through the properties settings selected for Pegasus Planner, Pegasus Home, and Catalogs.
Note
Values rely on proper capitalization, unless explicitly noted otherwise.Some default property values depend on the value of other properties.
Curly braces refer to the value of the named property. For instance,${pegasus.home} means that the value depends on the value of the pegasus.home property plus any noted additions. You can use this notation to refer to other properties, though the extent of the subsitutions are limited. Usually, you want to refer to a set of the standard system properties.
Nesting is not allowed.
Substitutions shall only be done once.
There is a priority to the order of reading and evaluating properties. Usually there is no need to worry about the priorities. However, it is good to know the details of when which property applies, and how one property is able to overwrite another.
Property definitions in the system property file, usually found in ${pegasus.home.sysconfdir}/properties , have the lowest priority. These properties are expected to be set up by the submit host's administrator.
The properties defined in the user property file ${user.home}/.pegasusrc have higher priority. These can overwrite settings found in the system's properties.
Commandline properties have the highest priority. Each commandline property is introduced by a -D argument.
Note
These arguments are parsed by the shell wrapper, and thus the -D arguments must be the first arguments to any command. Commandline properties are useful for debugging purposes.For more details see the Basic Properties section of the Running Workflows chapter
