README for Platform Community Scheduler Framework
March, 2005
=========================
Introduction
=========================
------------------------
1.1 What is the Platform Community Scheduler Framework?
------------------------
The Platform Community Scheduler Framework (CSF) is the industry's
first comprehensive and OGSI-compliant metascheduling framework
built upon the Globus Toolkit(R) 4 (GT4) As part of our commitment
to the future of Grid, we are contributing CSF back to the Globus
Project(TM) to be included in all future versions of the Globus Toolkit.
------------------------
1.2 Platform CSF metascheduling services
------------------------
The Platform CSF consists of the following services:
o Job Service, for submitting, controlling and monitoring jobs
o Reservation Service, for reserving resources on the Grid
o Queuing Service, which provides a basic scheduling capability in CSF.
=========================
Building and Installing
=========================
------------------------
1 Supported Platforms:
------------------------
This release supports the following platforms:
x86 systems running Linux: Kernel 2.4.x, compiled with glibc 2.2
Tested on RedHat Linux 9.0 and RedHat Enterprise 3.0
------------------------
2 Required packages
------------------------
1. Additional tools (required also by GT4)
- JDK 1.5 or higher (http://java.sun.com/j2se) (1.5 is recommended)
- Ant 1.5 or higher (http://ant.apache.org/)
- Globus Toolkit 4.0.0
See the GT4 installation documentation for information about
downloading and installing these tools:
http://www.globus.org/toolkit/downloads
2. CSF packages
- CSF4.0.x source package: csf-src-4.0.x.tar.gz
Newest code from CVS:
http://sourceforge.net/projects/gcsf
Newest release package:
http://sourceforge.net/projects/gcsf
From GT4 package
untar and unzip gt4 package,
CSF package is in 'contrib' directory
------------------------
3 Optional packages
------------------------
1. Platform's LSF 6.0
------------------------
4 System requirements
------------------------
- CPU speed must be 1 GHz processor higher.
- At least 512 MB of RAM and 1 GB of free disk space.
------------------------
5 Installing the CSF4.0.x packages
------------------------
To install the CSF4.0.x packages, complete the following steps.
1. Make sure JAVA_HOME, ANT_HOME are set to the correct
installation location.
Add JAVA_HOME/bin and ANT_HOME/bin to PATH variable.
2. Install the newest Gt4 packages:
please look through the GT4 install guide :
http://www.globus.org/toolkit/docs/4.0/admin/docbook/
3. Set up GT4.0 environment
o Make sure JAVA_HOME, ANT_HOME are set to the correct installation location.
o Add JAVA_HOME/bin and ANT_HOME/bin to PATH variable.
o cd <gt4_install_location>
o export GLOBUS_LOCATION=`pwd`
o source either etc/globus-user-env.csh or etc/globus-user-env.sh
o source either etc/globus-devel-env.csh or etc/globus-devel-env.sh
4. Install LSF for CSF (Optional)
o Login as root
o Uncompress and untar lsf6.0_linux2.4-glibc2.2-x86.tar.Z and follow
the steps in README
o Set up your LSF environment by sourcing either cshrc.lsf or profile.lsf.
5. Install CSF4.0.x :
o If download the CVS:
o Enter into packaging/
run this command:
. ./make-src-package
come into being the file of csf-4.0.x-src.tar.gz
o run this command as globus admin user (the user installed gt4)
gpt-build csf-4.0.x-src.tar.gz
gpt-postinstall
o If download the package: csf-4.0.x-src.tar.gz
o run this command as globus admin user (the user installed gt4)
gpt-build csf-4.0.x-src.tar.gz
gpt-postinstall
6£® Make sure you set up security configuration for GT4.0
You can get certificate from Globus or set up your own CA. Certificates
for every user and the host, which runs GT4.0, are required. We recommend
you getting certificates from Globus as setting up your own CA could
take some time.
For details,
http://www.globus.org/toolkit/docs/4.0/admin/docbook/ch05.html
7. Sanity checking
o Verify your certificate by executing the following commands
% $GLOBUS_LOCATION/bin/grid-proxy-init
220:blu@dev04 /usr/local/bingfeng/gt395> grid-proxy-init
Your identity: /O=Grid/O=Globus/OU=lsf.platform.com/CN=Bingfeng Lu
Enter GRID pass phrase for this identity:
Creating proxy ........................................... Done
Your proxy is valid until: Wed Mar 9 05:02:14 2005
% $GLOBUS_LOCATION/bin/grid-proxy-info
222:blu@dev04 /usr/local/bingfeng/gt395> grid-proxy-info
subject : /O=Grid/O=Globus/OU=lsf.platform.com/CN=Bingfeng Lu/CN=880442514
issuer : /O=Grid/O=Globus/OU=lsf.platform.com/CN=Bingfeng Lu
identity : /O=Grid/O=Globus/OU=lsf.platform.com/CN=Bingfeng Lu
type : Proxy draft compliant impersonation proxy
strength : 512 bits
path : /tmp/x509up_u30107
timeleft : 11:59:36
=========================
Configuring
=========================
following files must be configured:
- $GLOBUS_LOCATION/etc/metascheduler/resourcemanager-config.xml
- $GLOBUS_LOCATION/etc/metascheduler/metascheduler-config.xml
Those files include some example settings for you follow.
------------------------
1. Configuring Resource Manager
------------------------
Edit $GLOBUS_LOCATION/etc/metascheduler/resourcemanager-config.xml :
ResourceManagerService support alternative protocols other than WS GRAM.
Currently, There are two kinds of protocols were supported.
o LSF Web Broker (daemon named gabd)
gabd's configuration locates at $LSF_ENVDIR/ga.conf, in which
port number is specified. The default port number for gabd is 1966.
name = name of LSF cluster, you specified it during the LSF installation.
type = "LSF" (without quotes)
host = host running gabd (may be same as LSF master) or running gatekeeper(the daemon of Pre-WS GRAM)
port = port number specified in gabd configuration (i.e., ga.conf)
for example:
<cluster>
<name> aspen </name>
<type> LSF </type>
<host> grid1.jlu.edu.cn </host>
<port> 1967</port>
<version>6.0</version>
</cluster>
o Pre-WS GRAM (daemon named gatekeeper)
name = a unique name of the cluster
type = "GRAM" (without quotes)
host = host running gatekeeper, jobmanager type should be given if you don't want to use default jobmanager
port = port number of gatekeeper(2119 by default)
for example:
<cluster>
<name> sge-96 </name>
<type> GRAM </type>
<host> rocks-96.sdsc.edu/jobmanager-sge </host>
<port> 2119 </port>
<version>2.4</version>
</cluster>
Note: the example resource manager configuration in the file
is commented out. You need to define one after line "-->".
------------------------
2. Configuring CSF
------------------------
Edit $GLOBUS_LOCATION/etc/metascheduler-config.xml and specify:
1. global configuration
o global:CommunityGISHandle = handle of Default Index Service
NOTE: Do not use localhost or 127.0.0.1 loopback address, change it to actual host IP address.
2. Config job,queue,reservation
o job:pullingInterval : the Interval seconds to get Job data from Local Resource Manager
o job:queueName : default queue name
o queuing:plugin : scheduling policies class name
o queuing:parameter : the parameter for scheduling policies
Tip: You can using default configuration without any change.
=========================
Testing
=========================
------------------------
1. Documentation
------------------------
NOTE: What we did the testing is on the GT4.0.0
CSF documentation can be found in directory $GLOBUS_LOCATION/docs/metascheduler/:
- examples: contains examples for job service and reservation service
- config: configuration template for resource manager and CSF.
- api: Java API documents in Javadoc format:
$GLOBUS_LOCATION/bin/
------------------------
2. Starting LSF (Optional)
-----------------------
o Login as root
o Set up LSF environment by sourcing either cshrc.lsf or
profile.lsf
o lsadmin limstartup
o lsadmin resstartup
o badmin hstartup
o $LSF_SERVERDIR/gabd -d $LSF_ENVDIR
------------------------
3. Starting GT4.0
------------------------
1. Set up GT4.0 environment
- Make sure JAVA_HOME, ANT_HOME are set to corresponding install location.
- Add JAVA_HOME/bin and ANT_HOME/bin to PATH variable.
- cd <gt4_install_location>
- Export GLOBUS_LOCATION=`pwd`
- Source either etc/globus-devel-env.csh or etc/globus-devel-env.sh
2. Start service container
% su - globus
% globus-start-container
NOTE: control will not return to the terminal for "globus-start-container",
so you will need another window for testing CSF.
------------------------
4£® Using the Reservation Service (LSF is needed)
------------------------
Reservation Service requires resource manager supporting advance
reservation. By default only LSF cluster administrator(s) can make
reservations in the cluster. You can allow every user to make
reservation as well by defining advance reservation policies in your
LSF cluster.
See the chapter "Advance Reservation" in "Administering Platform LSF"
for more information.
o Creating a reservation by agreement
o Use template agreement file from
${GLOBUS_LOCATION}/docs/csf/example/agreement.xml,
you must change:
- agreement term values (ResReq or hostTerm, cpuTerm, userTerm,
startTime, endTime)
o csf-rsv-create -agreement|-a
<agreement_file> [-name|-n reservation_name]
o On success, a corresponding reservation is created in the LSF
cluster. Use the "brsvs" command to query existing reservations.
NOTE: On success, this returns a handle to the reservation-name
On failure, this throws a fault
If not specified the reservation_name ,It will return a hach_code,
The hach_code has the same function as the reservation_name.
o Creating a reservation by RSL
o You can use template RSL file from csf/example/rsv.xml, but
must change:
- schema location specified in "schemaLocation" attribute.
- values for hosts, number ... etc
o csf-rsv-create createService -rsl|-r <rsl_file>
[-name|-n reservation_name]
o csf-rsv-submit <reservation_name>
o On success, a corresponding reservation is created in the LSF
cluster. Use the "brsvs" command to query existing reservations.
o Modifying a reservation
o csf-rsv-modify <reservation_name > <-rsl rsl_file>
o Operation that modifies the reservation request. This can only
be performed when reservation is in CREATED status.
o Canceling a reservation
o csf-rsv-cancel <reservation_name >
o Querying Reservation Data
o csf-rsv-data <reservation_name >
You will see XML file. At the top of it, you should see the reservation
information:
<GridReservation
ID="{http://10.60.39.113:8080/wsrf/services/metascheduler/ReservationService}ID_20050310_3" Status="RESERVED" UserID="bingfeng">
This reservation can be used by job. For details, see next section.
o Querying Reservation Status
o csf-rsv-status <reservation_name>
------------------------
5. Using the Job Service
------------------------
For jobs forwarded by the Platform Resource Manager Adapter, you can
verify if job service is working by checking the job status in
your LSF cluster
o Creating a job:
o csf-job-create -rsl|-r <rsl_file> [-name|-n job_name]
RETURN: true or false ,and the job_name
(You should use this job_name to control the job).
NOTE: Users need to call submit or start after the creation
in order for the job to run; otherwise, the job service
will not perform any further action. Users should also
destroy the job after it is finished.
If not specified the job_name,it will return a hach_code,
The hach_code has the same function as the job_name.
createService option "id <ID>" is not supported yet.
o Query Resource Managers available (new feature)
o csf-resource-list
RETURN: All the Resource Managers Information (Include local/remote ResourceManagerLsf, local/remote ResourceManagerGram, local/remote Gram Clusters)
Tip: ResourceManagerGram means GT2 gatekeeper, Gram Cluster means cluster managed by Gram. Gram Cluster can be Fork, LSF, PBS, SGE, Condor, DRMAA.
o Starting a job in a cluster controlled by resource manager:
o csf-job-start <job_name> <-RmfHandle|-Rh ResourceManagerFactoryService_handle> <-cluster|-c cluster_name> <-rsvId|-r reservationID> <-delegate|-d "Full"|"Limited">
RETURN: JobID
o Stopping a job:
o csf-job-stop <job_name>
RETURN: true or false
o Resuming a job:
o csf-job-resume <job_name>
RETURN: true or false
o Canceling a job:
o csf-job-cancel <job_name>
RETURN: true or false
o Checking job information:
o csf-job-data <job_name>
RETURN: job data in xml format
o csf-job-status <job_name>
RETURN: job status in xml format
o Queuing a job:
The queuing service must be configured successfully, as described
in "5.6. Using the Queuing Service"
o csf-job-submit <job_name>
Queuing service will schedule jobs automaticlly (by the scheduling policies configured).
o List all jobs
o csf-job-list
o Creating a job with a grid reservation id (only supports LSF cluster)
o Make a reservation by using Reservation service.
o Get grid reservation id
o Specify a reservation in job's rsl_file like
<metascheduler:gridReservationId>
<rsl:string>
<GridReservation ID="{http://10.60.39.113:8080/wsrf/services/metascheduler/ReservationService}ID_2005030_10"/>
</rsl:string>
</metascheduler:gridReservationId>
Queuing service dispatches the job to the cluster where the reservation is
made if grid reservation id is included. See the next section for details
of queuing service.
If job is started by using job service client, clusterName and
gridReservationId defined in job's rsl file is ignored.
Note: This feature only available for ResourcManagerLsf
o Creating a job with Gram:
For example:
$ csf-job-create -rsl docs/metascheduler/examples/gram_job.xml -name job1
Service location:https://198.202.88.32:8443/wsrf/services/metascheduler/JobService
CreateJob Successfully: job1
o Submit the job to Queue:
For example:
$ csf-job-submit job1
submit() => https://198.202.88.32:8443/wsrf/services/metascheduler/JobService
Checking the job information :
For example:
$ csf-job-status job1
getStatus() => PDone
$ cat /tmp/stdout
abc 34 this is an example_string Globus was here
abc 34 this is an example_string Globus was here
o List all jobs
For example:
$ csf-job-list
getAllJobs() =>
JOBNAME RSL STYLE STATUS
job1 WS GRAM PDone
job2 Pre-WS GRAM Created
------------------------
6. Using the Queuing Service
------------------------
o Configuring queues:
$GLOBUS_LOCATION/etc/metascheduler/metascheduler-config.xml
section queuingConfig
Each queue has its own configuration section, which includes:
- plugin: name of the class which must interface
implement com.platform.metascheduler.impl.schedPlugin
The default plugin is always loaded even without defining plugin.
If the plugin specified does not exist or does not implement the
schedPlugin interface, it will not be loaded.
The optional throttle plugin should be configured.
- scheduleInterval: interval in seconds between different
scheduling session. Its value is an integer between 5 and 600.
This parameter is optional. If not defined, default value (30
seconds) is used.
- throttle: maximal number of jobs can be dispatched in each
scheduling cycle. Its value is an integer greater than 0.
To test this, you must configure throttle to a small value and
scheduleInterval to a bigger value and submit more jobs. You can
check how many jobs are forwarded to LSF cluster(s) as well.
Turn on debug in $GLOBUS_LOCATION/log4j.properties
log4j.category.com.platform.metascheduler.impl.schedThrottle=DEBUG
You should see a message like the following:
[java] 438867 [Thread-60] DEBUG com.platform.metascheduler.impl.schedThrottle
- Keep only the first 3 decisions
By default, there is a queue named "normal" configured.
o Creating a queue - only queues the are configured in the
configuration file can be created. Any user can create queues and
any queue can be used by all users. If you submit a job to a
queue that does not already exist, the queue is created automatically.
Syntax:
o csf-queue-create -q <queue_name>
Return: handle to the created queue if operation is successful.
Tips: A Queue will be created automaticlly when jobs were submitted to it.
o Checking one specific queue:
o Get queue data through queuing service client
Syntax:
o csf-queue-data <queue_name>
Return: queue name and status
o Get queue configuration through queuing service client:
Syntax:
o csf-queue-conf <queue_name>
Return: queue configuration parameters.
TODO: a interface queue-query (Query the jobs pending in the queue) will be added in the recently future.
o Queuing a job
o Jobs specifying a cluster name. The queuing service honors
the ClusterName specified in the job RSL file and dispatches it.
If it is incorrect, the job is not scheduled.
1 - create a job by using job service
2 - submit the job to the queue
o Jobs without specifying any cluster. The queuing service assigns
a cluster for the job and dispatches it.
1 - create a job by using job service
2 - submit the job to the queue
See "Using the Job Service" for job creation and job
submission to queue
o Jobs with reservation. Queuing service dispatches the job
to the cluster where the first reservation is made.
If the job does not specify clusterName or gridReservationId in
its RSL file, the queuing service dispatches the job to the
available Resource Manager Factory Service and Gram factories
in round-robin order.
=========================
CSF Commands & APIs
=========================
In order to make CSF easy for end users to use, the CSF package
includes several sample commands to wrap around clients for Job
Service, Reservation Service, and Queuing Service.
All the commands are located in $GLOBUS_LOCATION/bin. For
command usage, use "help" as an argument.
------------------------
1. Job service commands
------------------------
% csf-job-cancel: cancel a job service instance
% csf-job-create: create a job service instance
% csf-job-data: get detailed job information
% csf-job-resume: resume a suspended job
% csf-job-start: start a job in a specific resource manager
% csf-job-status: get job status
% csf-job-stop: resume a suspended job
% csf-job-submit: submit the job to queuing service
% csf-job-list: list all the jobs, name, rsl style and status
------------------------
2. Reservation service commands
------------------------
% csf-rsv-cancel cancel an existing reservation
% csf-rsv-create create a reservation service instance
% csf-rsv-data get reservation information
% csf-rsv-status get reservation status
% csf-rsv-submit submit a created reservation to start reservation booking
------------------------
3.Queuing service commands
------------------------
% csf-queue-conf get queue configuration
% csf-queue-create create a queuing service instance
% csf-queue-data get queue information
Job service, reservation service and queuing service are Grid
services. Here we list published APIs of those services. For details,
see the WSDL files under directory
$GLOBUS_LOCATION/schema/metascheduler and the Javadoc information
under directory ${GLOBUS_LOCATION}/docs/csf/api.
------------------------
4. Job service APIs
------------------------
- String start(String factoryUri, String clusterName, String rmType, String rmRsvId)
Start a job in a specific cluster
- boolean cancel()
Cancel a job
- boolean resume()
Resume a suspended job
- boolean stop()
Suspend a job
- String getJobData()
Get detailed job information
- String getStatus
Get job status
------------------------
5. Reservation service APIs
------------------------
- String getRsvData()
Get reservation information
- boolean submit()
Submit a reservation request for reservation booking
- boolean modify(String rsl)
Modify a reservation request before the request is submitted
- String getStatus()
Get reservation status
------------------------
6. Queuing Service APIs
------------------------
- QueueDataType getQueueData()
Get queue information
- QueueConfigParamsType getQueueConfigParams()
Get queue configuration
- String submit(QueuingRequestType submitRequest)
Submit a job to current queue
- boolean remove(QueuingRequestType removeRequest)
Remove a job from current queue
=========================
Support for Multiple GT4.0 Hosting Environment
=========================
------------------------
1.The conception of multiple GT4.0 hosting environment
------------------------
The conception of multiple GT4.0 hosting environment means there exist multiple Globus enviroment(The hosting who installed the GT software means one Globus enviroment),they trust the issued CAs mutually, the multiple Globus enviroment is called a "Community" or a "Virtual Organization(OA)".
The multi-hosting collaboration of CSF allows the hostA send it's jobs to the hostB,and the jobs run in the hostB's resourcemanager.
One community need one or more Center Index Server,the Center Index Server storage all "epr" about the RM information of the community. Especially, the Center Index Server isn't necessary to install the CSF4.
------------------------
2.The configure must to do
------------------------
for instance: HostA(IP:10.60.39.3) HostB(IP10.60.39.113) as the hosts computer of a Community, HostC(IP:10.60.39.4) as the Center Index Server of the Community¡£
o config the HostA:
o In the file of $GLOBUS_LOCATION/etc/metascheduler/metaschedulerconfig.xml
(in the title of globalConfig),configure the CommunityGISHandle
For instance:
<global:CommunityGISHandle value=
" https://10.60.39.3:8443/wsrf/services/DefaultIndexService"/>
o In the file of $GLOBUS_LOCATION/etc/globus_wsrf_mds_index/hierarchy.xml
configure the VO Index Service Handle¡£
For instance:
<upstream>https://10.60.39.4:8443/wsrf/services/DefaultIndexService</upstream>
o config the HostB
The configure process is the same as HostA
o In the file of $GLOBUS_LOCATION/etc/globus_wsrf_mds_index/hierarchy.xml, configure the other Host Index Service Handle of the VO¡£
for instance:
<downstream>https://10.60.39.3:8443/wsrf/services/DefaultIndexService</downstream>
<downstream>https://10.60.39.113:8443/wsrf/services/DefaultIndexService</downstream>
------------------------
3.Submit a job in the Multiple GT4.0 Hosting Environment
------------------------
o Config the HostB's $GLOBUS_LOCATION/etc/metascheduler/resourcemanager-config.xml
for instance:
<cluster>
<name> cluster1 </name>
<type> LSF </type>
<host> HostB </host>
<port> 1966</port>
<version> 6.0 </version>
</cluster>
o Config the HostA's $GLOBUS_LOCATION/etc/metascheduler/resourcemanager-config.xml
for instance:
<cluster>
<name> cluster2 </name>
<type> LSF </type>
<host> HostA </host>
<port> 1976</port>
<version> 6.0 </version>
</cluster>
o Create job1 on HostB
[globus@grid5 gt395]$ csf-job-create -rsl job.xml -name job1
Service location:https://10.60.39.113:8443/wsrf/services/metascheduler/JobService
CreateJob Successfully: job1
o submit job1 ,run in the HostA
[globus@grid5 gt395]$ csf-job-submit job1 -q normal -Rh https://10.60.39.3:8443/wsrf/services/metascheduler/ResourceManagerFactoryService -c cluster2
submit(normal) => https://10.60.39.113:8443/wsrf/services/metascheduler/JobService
Notice:The HostB had configed to cluster1, the job1 was appointed to cluster2(the HostA had configed), so when submit the jod which created in HostB ,the job will run in the HostA.
------------------------
4.Starting a job in an LSF cluster through Resource Manager Factory service
------------------------
o Create a job in GT4.0 on hostA environment:
% csf-job-create rsl job.xml job1
o Start the job in an LSF cluster through Resource Manager Factory
service:
% csf-job-start job1 -Rh http://HostIP:8443/wsrf/services/metascheduler/ResourceManagerFactoryService -c clustername
=========================
New features
=========================
-------------------------
1. A new useful utility for Query Resource Manager Information availabe
-------------------------
o csf-resource-list
o csf-job-list
-------------------------
2. Support GT2 gatekeeper
-------------------------
o Config gatekeeper to $GLOBUS_LOCATION/etc/metascheduler/resourcemanager-config.xml
o For example:
<cluster>
<name> gatekeeperA </name>
<type> GRAM </type>
<host> rocks-110.sdsc.edu </host>
<port> 2119 </port>
<version>2.4</version>
</cluster>
o submit a job to gatekeeper
o csf-job-create -rsl docs/metascheduler/test.rsl -n job1
Service location:https://198.202.88.110:8443/wsrf/services/metascheduler/JobService
CreateJob Successfully: job1
o csf-job-submit job1
-------------------------
3. Support full delegate for GT4 WS-Gram/GT2 gatekeeper job
-------------------------
o GT4 WS-Gram client (globusrun-ws) and gatekeeper client (globusrun) didn't support full delegation for some secure issue, however, full delegation proxy is necessary for some application (for example: Gfarm1.1.1).
o Start a job with full delegate
For example:
o csf-job-start job1 -Rh http:///198.202.88.110:8443/wsrf/services/metascheduler/ResourceManagerFactoryService -c gatekeeperA -d Full
=========================
Uninstallation
=========================
To undeploy and uninstall the CSF package:
Run this command in the directory $GLOBUS_LOCATION as globus admin user
ant -f share/globus_wsrf_common/build-packages.xml undeployGar -Dgar.id=metascheduler
rm -rf etc/gpt/packages/setup/csf
rm -rf etc/gpt/packages/csf
=========================
Contact Information
=========================
Please send all questions and comments to support@platform.com
or discuss group of sourceforge.net(http://sourceforge.net/mail/?group_id=103105),
or phone toll-free 1-877-444-4LSF (+1 877 444 4573)
=========================
Copyright
=========================
Copyright 1994-2003 Platform Computing Corporation.
All rights reserved.
Although the information in this document has been carefully
reviewed, Platform Computing Corporation ("Platform") does not
warrant it to be free of errors or omissions. Platform reserves the
right to make corrections, updates, revisions or changes to the
information in this document.
UNLESS OTHERWISE EXPRESSLY STATED BY PLATFORM, THE PROGRAM DESCRIBED
IN THIS DOCUMENT IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. IN NO EVENT WILL PLATFORM COMPUTING BE LIABLE TO
ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, DATA OR
SAVINGS, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PROGRAM.
LSF is a registered trademark of Platform Computing Corporation in
the United States and in other jurisdictions.
ACCELERATING INTELLIGENCE, THE BOTTOM LINE IN DISTRIBUTED COMPUTING,
PLATFORM COMPUTING, and the PLATFORM and LSF logos are trademarks of
Platform Computing Corporation in the United States and in other jurisdictions.
UNIX is a registered trademark of The Open Group.
Other products or services mentioned in this document are the
trademarks of their respective owners.
=========================
Security Considerations
=========================
[the Security_Considerations_Frag.html is embedded below.]
=========================
Troubleshooting
=========================
o If the client server report the error "connect denied" ,you'd
better check out if the LSF is started.
o If you can't create a queue, you'd better check out if you have
configed the queue in the file of
$GLOBUS_LOCATION/etc/metascheduler/metascheduler-config.xml
o When you using csf-resource-list/csf-rsv-create/csf-queue-create utility,
return a error message "DefaultIndexService isn't ready".
The reason is ResourceManager Information won't aggregate to DefaultIndexService as soon as container startup,
so please wait a few seconds and re-run the command.
==============================
END of README
Last update: Tuesday Augest 15th 2006
==============================
Download Latest Version
csf-4.0.5.1-src.tar.gz (380.2 kB)
