1. First proposal for a modification of the GIS schema
Massimo Sgaravatto
INFN Padova

2. Introduction
The Grid Scheduler chooses the resources where to submit jobs
What is this resource, for our Globus-based M9 prototype ?
A queue of an underlying resource management system (LSF, PBS, …)
A queue represents a set of “homogeneous” resources
When a job is submitted to a specific queue, it doesn’t matter in which node of this queue the job is dispatched
What is the set of local resource management systems that we have to take into account ?
A “single” node

3. Resources
For this brokering functionality, the Grid Scheduler needs info on resources (characteristics, status, forecasting information)
The current Globus schema is not enough
Some useless attributes (at least for our needs)
Some attributes not calculated (always defined as 0)
Some attributes not properly calculated by Globus shell scripts (i.e. totalnodes and freenodes for LSF)
Some important information describing the resources missing
 Necessary to modify the default schema
First proposal about list of attributes that we would like to have already discussed within WP 1

4. List of attributes Name of the resource (i.e. name of the queue)
Architecture
Operating System
Total CPUs
Free CPUs
Number of running jobs
Number of idle (pending) jobs
Maximum number of running jobs allowed for this resource
Maximum number of jobs (running and idle) allowed for this resource
Status (ready or not ready to dispatch jobs to the executing machines)
Run windows (when the resource is active)
Priority
Maximum CPU time for a job submitted to this resource
Maximum wall clock time for a job submitted to this resource

5. List of attributes Job start estimate / Queue traversal time
Minimum local disk footprint
Minimum available physical memory
Computing power
Which benchmark ?
Authorization policy
Which format ? Gridmap file for the M9 release ?
Internet accessibility / Address of an IP gateway
Number of SMP processors
Installed application environments
“Attached” storage element(s)

6. Some of these attributes should be easily obtainable by the underlying resource management system
For other attributes it is necessary to implement specific “information producers”