- jsdl-wg - lists.ogf.org

jsdl:FileSystem
by Michel Drescher 09 Mar '05

09 Mar '05

Folks, while messing around with the schema, I just found a possible glitch: Last week, we defined the new attribute "sid" in the element jsdl:FileSystem. This attribute refers to a symbolic name for a filesystem to be made available (mounted) to the environment of the application. This implies 2 issues: a) If the mount point is site configurable (aka unknown to the JSDL document creator) then it is useless to specify a jsdl:MountPoint element. Therefore, jsdl:MountPoint should be optional, instead of mandatory (as it is now) b) We need to define the symbols that are allowed for this new attribute. I propose the following list for a starter: "jsdl:HOME" = The home directory of the jsdl:ExecutionUserID "jsdl:TMP" = A directory for temporary file storage (for the time of the execution) "jsdl:SPOOL" = A spool directory JSDL should allow creators to use their own symbols as long as they are defined in a different namespace. The base set of symbols defined in JSDL MUST be supported by all implementors. Comments, ideas, rants? :-) Cheers, Michel

2 1

Tracker renaming and new tracker
by Andreas Savva 08 Mar '05

08 Mar '05

I've created a new tracker for issues that fall out-of-scope of version 1: "JSDL-post-v1" https://forge.gridforum.org/tracker/index.php?func=browse&group_id=122&atid… and I renamed the JSDL specification tracker to "JSDL version 1" Andreas

1 0

Meeting minutes
by Darren Pulsipher 08 Mar '05

08 Mar '05

%PDF-1.4 %àáâã 3 0 obj << /Filter /FlateDecode /Length 624 >> stream xVQoÚ0~^~Åí-h!$ C]§¶£©šLd{âÅxMìÔ1 û÷;;¡µ©hPÀŸ|÷Ýå»ó''Êù|Ý®ßÜéeŠý^cÂEæ,öØA?hìzeÁªWûÃyrn¢%Þ¡Ñv8Ô»Î]a¢ãÎIBGÐ~;nš¿Û 2Ðž6úë&°YP¯°ýä©Æéðü`ú#Ç¹NaèA7úµ[óèÈàZ)ÊcJKðÃw"%å°tÅÀýýí²euºÎ3cëfv*KJìyÞ°ÌN¶Ø®Ž¿²àä.óë`ÞF&Ûreéëá²!n] enSÂ *¥°@SN`#€ÙâÂÚ`¬ñnSÏÿhº~Iz¶,§ëãÉZáòàseÁ¯ve<*d<¹ìNáð}ÿŒ:ÿûv¶0¿š,àìûuTÝOPáAJ2E@!E!Já1x@ ÓÉcŠô¡iÚ³Ø*HY#t#±b*€]$`ápÌwVMÅbäÝröCu|ÙG°yÑ\èyPQØZíšÖBØÔñ}XL!ŠÆi ª³R1ŸVU`#xàV€DwÁ!<[ ZtqìÓÅ9ObQ(Ü®þüŠcø€äÁXÂ q0QcIî#c=y0±fy07õãPÐ¿±û"FM <2$fK÷£Îkï9«)µŠMÓQÝjZr3ŠÔoë¡q þßa& endstream endobj 4 0 obj << /MediaBox [0 0 612 792] /Contents 3 0 R /Type /Page /Resources << /Font << /F1 2 0 R >> /ProcSet [/PDF /Text] >> /Parent 1 0 R >> endobj 6 0 obj << /Filter /FlateDecode /Length 503 >> stream x¥TÁn0œó£=D°vÙFJ«Ti#UÔfzhªÊgÁÁmÊöÒo¯ Þ(«Fâèyxóæyló$Ðg+HÓh M°Ì=ä.žÌ|ÈlÜ|¹ðqfš9î·à1x_xÙuŽÊ LÖnL I¡Øó¯€Âs8-îyêÞ¡g./Žùî±p(< "Ôn[ÃGêŸ¿@\»Ue3n@56pOÉîæUM€±Õ£Á»ÓQÏç<>šÔÆÈó8îû>ºvñ_ŸkâkÅh|{~¿;ÕWáX*Jh¯é(L.KÃD«§háÓ5ÅüÂ¬?!tÎôÌÔ0#ªêlÍÖi)Ìºí#v[ªègòËQŒ¬I[¡ xNßgRµ.\Tf¯owÓ44âÎ-)G3(Â¹up/¶@QÉ¡Ñ°ê/VbXèõŠ|¬Ò;ñO«Ï 6ð;£Hù ÞÂh'»í¶€¶{Òz®0ªìFŽšk";œRÌZûHÖòÝ®kËœÆJNþbô"IÓb,È×ÙQ¹4É¢ìÂ4U ÉêøXý÷6QKøyúüá(ìÏâ_4 endstream endobj 7 0 obj << /MediaBox [0 0 612 792] /Contents 6 0 R /Type /Page /Resources << /Font << /F1 2 0 R /F2 5 0 R >> /ProcSet [/PDF /Text] >> /Parent 1 0 R >> endobj 8 0 obj << /Type /Outlines /First 9 0 R /Count 1 /Last 9 0 R >> endobj 9 0 obj << /Dest [7 0 R /Fit] /Parent 8 0 R /Title (þÿ[ Text Slide A ]) >> endobj 5 0 obj << /Encoding /WinAnsiEncoding /Subtype /Type1 /BaseFont /Helvetica-Bold /Type /Font >> endobj 2 0 obj << /Encoding /WinAnsiEncoding /Subtype /Type1 /BaseFont /Helvetica /Type /Font >> endobj 1 0 obj << /Type /Pages /Count 2 /Kids [4 0 R 7 0 R] >> endobj 10 0 obj << /Pages 1 0 R /Outlines 8 0 R /Type /Catalog /PageMode /UseOutlines >> endobj 11 0 obj << /CreationDate (D:20050308065421-08'00') /Producer (þÿiText by lowagie.com $r0.80 based on paulo build 87$) >> endobj xref 0 12 0000000000 65535 f 0000001960 00000 n 0000001863 00000 n 0000000015 00000 n 0000000711 00000 n 0000001761 00000 n 0000000859 00000 n 0000001434 00000 n 0000001592 00000 n 0000001663 00000 n 0000002023 00000 n 0000002112 00000 n trailer << /Info 11 0 R /Size 12 /Root 10 0 R >> startxref 2295 %%EOF

1 0

Re: [jsdl-wg] TileSize and ProcessCount (fwd)
by Ali Anjomshoaa 08 Mar '05

08 Mar '05

Bounced ? -- ---------------------------------------------------- |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 ------------------------------------------------------------- ---------- Forwarded message ---------- Date: Wed, 02 Mar 2005 09:26:56 +0000 From: A S McGough <asm(a)doc.ic.ac.uk> Cc: jsdl-wg(a)gridforum.org Subject: Re: [jsdl-wg] TileSize and ProcessCount OK, Reading this thread (sorry for the use of the term...) it seems as though we have confusion between a number of different terms. Personally in this case I like to think in diagrams. Attached is the example ProcessCount = 12 TileSize = 4 From the document this suggests that we have 12 processes (not processors) in the job and that each set of 4 processes are allocated to a resource. Thus requiring 3 resources. Presumably if we request in the resource section that each resource must have at least 4 processors then each process _could_ be mapped down to a different processor. Is this correct? Are people happy with this? Does it describe all situations? I've attached a figure showing this - sorry it's so naff. steve.. Christopher Smith wrote: >Thanks for the clarification Andreas. I guess I need to do some reading up >on some of the changes. :-) > >-- Chris > > >On 1/3/05 18:41, "Andreas Savva" <andreas.savva(a)jp.fujitsu.com> wrote: > > > >>Hi Chris, >> >>Just to give you some background on why this is the way it is. >> >>At the last F2F after a lengthy discussion on topology and what it >>really means the group reached the conclusion that topology is part of >>the application definition rather than part of the hardware >>requirements. (That is, it is independent of the hardware resources to >>be allocated to the job and should be described separately and in terms >>that are not hardware specific.) >>So the topology tags describe the number of processes and their desired >>grouping/tiling and appear in the Application section rather than the >>Resource section. The Resource section (may) contains tags to describe >>the hardware resources required: CPUCount and ResourceCount. >> >>I have some doubts about the current definition (in particular I think >>we either overloaded the term 'Process' or we defined TileSize the wrong >>way). But I think it is easier to bash this out on a call or f2f (hand >>to hand? :-) at GGF13. >> >>Andreas >> >> >>Christopher Smith wrote: >> >> >>>Perhaps there are naming issues here, or there are too many terms defined >>>here. >>> >>>JSDL is only concerned with specifying the resource requirements for the >>>allocation request, not with how those resources end up being used (i.e. >>>using threads or processes). So the TileSize indicates how many cpus need to >>>be allocated as a unit within one OS image (i.e. a group of cpus), and the >>>CPUCount would tell you how many cpus are needed in total. I don't believe >>>you need any more. If the job chooses to use processes or threads is >>>independent of the allocation. >>> >>>So given this example: >>> >>> >>> >>> >>>>tasks per job=3 >>>>threads per task=4 >>>>processors per task=4 >>>> >>>> >>>> >>>TileSize = 4 >>>CPUCount = 12 >>> >>>This can translate to the PBS syntax "nodes=3:ppn=4" or the LSF syntax "-n >>>12 -R 'span[ptile=4]'", and I'm sure others as well. >>> >>>To the entity making the allocation, processes or threads doesn't matter. >>> >>>-- Chris >>> >>> >>> > > > > -- ------------------------------------------------------------------------ Dr A. Stephen McGough ------------------------------------------------------------------------ Research Associate, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8310 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------ Assistant Warden, West Wing, Beit Hall, Imperial College, Prince Consort Road, London, SW7 2BB tel: +44 (0)207-828-49910 ------------------------------------------------------------------------

1 0

Issues for the teleconference tomorrow
by Michel Drescher 08 Mar '05

08 Mar '05

Co-wranglers, I (again me...) have a list of questions (extracted from the mail of Karl Czajkowski mentioned last week): 1) Argument list handling in jsdl:Application Basically, the modeling of command line arguments in a whole string is ... cumbersome? I know, it works, but it looks ugly. Instead, I'd like to propose the following (in PseudoCode): <Application ... > ... <Arguments> <Arg order:xsd:positiveInteger>xsd:String</Arg> </Arguments>* ... </Application> Every content in the jsdl:Arg element would be converted to quoted strings if it contains whitespaces. Example: Consider an application "print.exe" that sends a file to a named print queue. The default queue is used when no print queue name is given. "print.exe -p dj720c example.txt" (1) "print.exe example.txt" (2) "print.exe 'C:\Program Files\Dummy\help.txt'" (3) The XML snippets could be as follows: ... <Arguments> (1) <Arg order="1">-p</Args> <Arg order="2">dj720c</Arg> <Arg order="3">example.txt</Arg> </Arguments> ... <Arguments> (2) <Arg order="3">example.txt</Arg> </Arguments> ... <Arguments> (3) <Arg order="2">C:\Program Files\Dummy\help.txt</Arg> </Arguments> ... Note: XML itself seem not to impose any order to elements with the same name contained in the same parent element. So we have to invent our own ordering mechanism (as done by the order attribute). 2) Versioning This topic might be slipped, so I would like to raise it again. Call me a nag bag, but is this superfluous information to contain "jsdl-1..1.xsd" in the namespace definitions? As an alternative, I propose the following namespace that also serves as a version identifier: "http://www.ggf.org/jsdl/2005/03/jsdl/" or "http://www.ggf.org/jsdl/2005/03/" where "http://www.ggf.org/" - is the shared domain of all GGF standards "jsdl/" - is the JSDL common domain "2005/03/" - is the version of the specification "jsdl/" (or sth. else) - is the sub-specification (if we want to think of any) 3) Storage/bandwidth units At the moment, we use a mixed set of units. SI defines two distinct sets of units: One based on 10, and one based on 2 (adopted by the IEC), having the 10 based units the normal prefix (like K, M, G, T, P and E) and the 2 based units the prefixes Ki, Mi(!), Gi, Ti, Pi and Ei. I propose to use the SI units. For JSDL2, I propose to switch to an OID based system for these kind of units. 4) Reservations What about the concept of resource reservations? Some initial thoughts: - Use reservation tokens in JSDL to refer to previously made reservations (with means out of scope of JSDL) - Incorporate/emend the job description with means to make reservations, so the reply to such a JSDL document would give the reservation token to put into another JSDL document to actually use the reserved resources 5) JSDL 2.0 issues list I would like to get some topics to be put as research/development candidate for JSDL2. 5.1) more structure for Java applications Quote from Karl's mail: >> -- more structure for java >> -- jar versus bytecode class >> -- native compiled java? >> -- like executable but java-style >> parameterization >> -- class w/ Main() to invoke >> -- language version >> -- external class dependencies? >> -- supported JVMs (java portability 50% myth) Cheers, Michel

6 8

meeting on the 8th sorry for the late reminder
by Bill Harris 08 Mar '05

08 Mar '05

You have been invited to attend a Microsoft Office Live Meeting. At the time of the meeting, click on the following link to attend. URL: http://www.placeware.com/cc/cadence/join?id=RWZ334&role=attend <http://www.placeware.com/cc/cadence/join?id=RWZ334&role=attend> Subject: JSDL Meeting When: Tuesday, Mar 8, 2005 7:00 AM (MST) Scheduled to Occur: Recurring Duration: 1 Hour 30 Minutes Audio Information: 1-800-933-3594 pin: 6444 Alternate Attend Instructions: Go to: http://www.placeware.com/cc/cadence/join <http://www.placeware.com/cc/cadence/join> Your Name: (enter your name) Meeting ID: RWZ334 Meeting Password: >Phone Numbers: >Belgium - 0800-7053 >Bezeq - 1-800-940-1786 >France - 0800-903109 >Germany - 0800-1815765 >Hong Kong - 800-968932 >Italy - 800874509 >Japan - 00531123656 >Korea-Tele - 00798-14-800-0512 >Netherlands - 0800-0225447 >Singapore - 800-1200766 >Sweden - 020-7905043 >Taiwan - 00801-13-8546 >UK - 0800961294 >US - 800-933-3594 William Harris Program Architect 150 West Civic Center Dr. Sandy, Utah 84070 Oryx follow me - 800 281 6462 Inside cadence 88 202 6462 Cell Phone 801 554 0187

1 0

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