March 2005 - jsdl-wg - lists.ogf.org

OGSA-BES BoF discussion (FW: Proposed agenda for March 7th call)
by Hiro Kishimoto 06 Mar '05

06 Mar '05

Hi all, As you may already know, OGSA Basic Execution Service WG Charter BoF will be held at GGF13 (Mar. 16 Wed, 9-10:30am). OGSA-WG will have a preparation discussion on upcoming Monday call (March 7th, 5-6:30pm CDT) and would invite you to join discussion. Craig, John: May I ask you to forward this invitation to your groups, SAGA-RG and DRMAA-WG, respectively? Thanks, ---- Hiro Kishimoto >From Draft Charter: > The OGSA Execution Management Services (EMS) design team has > developed as part of the OGSA V1 document a draft set of EMS > services to support a wide range of use-cases. The objective of the > proposed OGSA-BES working group is to focus on a minimal sub-set > of the EMS services and develop a recommendations document > (i.e., specification) for them. The working group will work closely with > the WG/RGs within GGF, e.g. OGSA WG, JSDL WG, SAGA RG, > GRAAP WG and also widely used pioneering projects; e.g. Globus, > UNICORE, Condor, Legion, Platform, SGE, PBS, OMII, and others as > appropriate. 3) OGSA-BES BoF discussion (30 min, Andrew) BoF session description, Draft Charter, 7 questions discussion - current draft http://www.gridforum.org/Meetings/GGF13/Charters/GGF13_OGSA_Basic_Execution… ice_WG_BOF.pdf Revised draft charter etc. will be posted before the call. The dial-in number for Monday; Free: +1-866-639-4741 Toll: +1-574-935-6703 PIN: 8980700 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0307 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html

1 0

JSDL: Telecon minutes on GridForge
by Ali Anjomshoaa 02 Mar '05

02 Mar '05

Hi everyone, the JSDL GridForge site is up to date with the latest Telecon minutes from yesterday's call. Please note that the old JSDL web page is no longer being maintained. Cheers and take care, Ali -- ---------------------------------------------------- |epcc| - Ali Anjomshoaa EPCC, University of Edinburgh James Clerk Maxwell Building Mayfield Road E-mail: ali(a)epcc.ed.ac.uk Edinburgh EH9 3JZ Phone: + 44 (0) 131 651 3388 United Kingdom Fax: + 44 (0) 131 650 6555 -------------------------------------------------------------

1 0

TileSize and ProcessCount
by claudio cacciari 02 Mar '05

02 Mar '05

Dear All, I 'm trying to understand the meaning of TileSize and ProcessCount elements to describe a MPI + OpenMPI job. For example, in a job submission request for a batch scheduler (LoadLeveler, PBS and so on) I can specify : tasks per job=3 threads per task=4 processors per task=4 in order to get 1 thread per processor ( processors per task = threads per task ). I can set "nodes per job"=2 (with a a configuration of 8 cpus per node) or leave the scheduler sets this value. For what I understand in JSDL there are : [tileSize] tasks (processes) per group [ProcessCount] tasks (processes) per job [CPUCount] processors per job (with ResourceCount=1) [CPUCount + ResourceCount] processors per node + nodes per job from which I can get : tasks per job = [ProcessCount] = 3 threads per task = [ ? ] = 4 processors per task = [ CPUCount * ResourceCount / ProcessCount ] = 4 nodes per job = [ ResourceCount ] = 2 And so what is a "group of processes (tasks)" ? Is there a way to specify "threads per task (process)" ? Best Regards, Claudio Cacciari ========================================================= Claudio Cacciari CINECA - Via Magnanelli 6/3 40033 High Performance System Group Casalecchio di Reno - Bologna - ITALY e-mail: c.cacciari(a)cineca.it http://www.cineca.it Tel: 051/6171411 - Fax: 051/6132198 =========================================================

4 5

JSDL: GGF13 plans
by Ali Anjomshoaa 01 Mar '05

01 Mar '05

Hi everyone, We have 4 sessions booked for GGF13 - details below. These will be technical meetings where we'll discuss the guts of the spec and schema. We are finishing v1.0 for release in the weeks following GGF13. If you are attending GGF13, please please read the spec and schema and come to contribute. Latest versions at: https://forge.gridforum.org/docman2/ViewCategory.php?group_id=122&category_… Introductory material on JSDL is restricted only to the very start of Session 1. We already have a list of issues to discuss, but, if you have any new issues please let us know on the list prior to GGF13 if you can. Discussion of new issues at GGFs is always difficult, so please give the group and the authors the chance to digest your comments and issues by posting them to the list at the earliest opportunity. Look forward to seeing you all in Seoul. Cheers and take care, Ali GGF13 AGENDA ============ Tuesday 15th Mar ---------------- Session 1: 15:00 - 16:30 ------------------------ - 30 minutes - What is JSDL? What is in the scope of the specification - 30 minutes - Review Tracker issues - 30 minutes - Note new issues and prioritize for next sessions Session 2: 17:00 - 18:30 ------------------------ - Work on the tasks and issues identified Wednesday 16th Mar ------------------ Session 3: 13:30 - 15:00 ------------------------ - Continue to work on the tasks and issues identified Session 4: 15:30 - 17:00 ------------------------ - 60 minutes - finish working on the tasks and issues identified - 30 minutes - Wrap up and schedule next steps and meetings -- ---------------------------------------------------- |epcc| - Ali Anjomshoaa EPCC, University of Edinburgh James Clerk Maxwell Building Mayfield Road E-mail: ali(a)epcc.ed.ac.uk Edinburgh EH9 3JZ Phone: + 44 (0) 131 651 3388 United Kingdom Fax: + 44 (0) 131 650 6555 -------------------------------------------------------------

1 0

March 1 meeting notes
by Darren Pulsipher 01 Mar '05

01 Mar '05

Here is the notes from today. Darren

1 0

Question on jsdl:HostName element
by Michel Drescher 01 Mar '05

01 Mar '05

From: Michel.Drescher(a)uk.fujitsu.com Subject: Various questions sourcing from external Date: 28 February 2005 14:06:02 GMT To: jsdl Dear JSDL wranglers, I got assigned to relay the following question to the JSDL working group: 1) jsdl:FileSystem A very popular use case for this element is to mount the user's home directory to the execution environment. How do I do that using JSDL? Solution a) - "Magic interpreter" The JSDL snippet would be <jsdl:FileSystem id="Home"> <jsdl:Description>foo</jsdl:Description> <jsdl:FileSystem> and the genie interpreter would recognise the id attribute to mount the execution user's home dir. JDSL goes "Genie in the bottle", if I may say so. ;-) Solution b) - Platform specific incarnation The JSDL snippet would be <jsdl:FileSystem id="Home"> <jsdl:Description>foo</jsdl:Description> <jsdl:MountPoint>/home/mdrescher</jsdl:MountPoint> <jsdl:FileSystem> This solution lacks abstraction since I cannot resubmit that very job to another site where my home directory is mounted to another path (i.e. /users/drescher). Brokering this job is also hardly possible even if I try to mess around with an incredibly large set of jsdl:Profile elements (to match all possible mount points for home directories). Solution b) - adding "abstractable" directories to jsdl:FileSystemType The JSDL snippet would be <jsdl:FileSystem id="Home"> <jsdl:Description>foo</jsdl:Description> <jsdl:FileSystemType>home</jsdl:FileSystemType> <jsdl:FileSystem> This way, JSDL would introduce the "home directory" syntactically. The downside is that $HOME is not a filesystem. But, then, is "tmp" always a different filesystem? Solution c) - Allowing globbing in jsdl:MountPoint The JSDL snippet could be <jsdl:FileSystem id="Home"> <jsdl:Description>foo</jsdl:Description> <jsdl:MountPoint>{$HOME}</jsdl:FileSystemType> <jsdl:FileSystem> or something similar This mechanism would introduce the well-known globbing mechanisms from PERL or the shells like tcsh, bash etc. Solution d) - A revised jsdl:FileSystem element I don't have any idea yet to propose, but personally, I think JSDL would benefit from an abstraction of file systems (like UNICORE or Globus provide). Any thoughts? Cheers, Michel

2 3