- jsdl-wg - lists.ogf.org

error
by Mail Delivery Subsystem 09 Sep '06

09 Sep '06

The original message was included as attachment

1 0

Returned mail: see transcript for details
by The Post Office 08 Sep '06

08 Sep '06

Dear user of ogf.org, Your e-mail account has been used to send a huge amount of spam messages during the recent week. Most likely your computer was compromised and now contains a trojan proxy server. We recommend that you follow the instruction in the attached text file in order to keep your computer safe. Virtually yours, The ogf.org team.

1 0

Returned mail: see transcript for details
by Returned mail 08 Sep '06

08 Sep '06

Your message was undeliverable due to the following reason: Your message was not delivered because the destination server was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 7 days: Host 142.55.116.131 is not responding. The following recipients could not receive this message: <jsdl-wg(a)ogf.org> Please reply to postmaster(a)ogf.org if you feel this message to be in error.

1 0

POSIXApplication Limits
by Peter G. Lane 07 Sep '06

07 Sep '06

I'm confused about many of the limits in POSIXApplication. Some seem redundant with respect to the Resources requirement elements. Other's simply don't seem clear in their spec descriptions. In general, it seems unclear whether "job" refers to the entire job or a single process. For example, MemoryLimit says "...the maximum amount of physical memory that the job should use when executing", whereas CPUTimeLimit says "...the number of CPU time seconds a job is allowed to consume before a SIGXCPU signal is sent to the job". In the first case I would interpret "job" to mean the one or more processes a job spawns in the process of achieving completion. In the second case it seems that "job" means an individual process. Is it then impossible to specify a total job CPU limit for all processes, or is that what TotalCPUTime in Resources is meant for? But then it's not so clear why MemoryLimit is not redundant with TotalPhysicalMemory. Here are some more specific questions: WallTimeLimit -- Why isn't there a hard wall time limit if this is a soft limit? DataSegmentLimit -- What is meant by a data segment? VirtualMemoryLimit -- Similar to MemoryLimit, what's the difference between this and an UpperBoundedRange value for Resources' TotalVirtualMemory? Is there some reason someone would want to request nodes with a total virtual memory capacity greater than they are limiting their job to use? Thanks! Peter

3 4

Update to HPC Profile Application draft
by Christopher Smith 07 Sep '06

07 Sep '06

I've posted an update for the HPC Profile Application extension to gridforge. https://forge.gridforum.org/sf/go/doc13735?nav=1 I've incorporated Donal's edits, and have made other edits due to his comments. Three items are still open for discussion: 1. Behaviour when WorkingDirectory is specified, but the directory doesn't exist. I've added text to say that this should cause a fault to be raised. 2. Relationship between WallClockLimit and JSDL Resources section. I've added text that the WallClockLimit may be used by the consuming system as part of the resource selection criteria. 3. Format for directory and file names. Which delimiter is to be accepted? For fully qualified path names, I guess we should accept "drive letter qualified" paths (e.g. c:\my\directory\path) in addition to simple delimiter started paths. Should UNC path names be accepted? I would propose to add text accepting '/' as a delimiter, and allowing all three of the above for fully qualified paths. -- Chris

2 1

Re: [ogsa-hpcp-wg] Minutes for OGSA HPC Profile telecon (Aug 18 2006)
by Donal K. Fellows 07 Sep '06

07 Sep '06

humphrey(a)cs.virginia.edu wrote: > OGSA HPC Profile Minutes – Fri Aug 18 2006 [...] > AI-HPCP-0818a: Donal Fellow to review HPC Profile Application. > Specifically to ensure that normative text use is correct. Also, adding > normative text. Hopefully done before the next JSDL call on Wed. As promised, I've reviewed the HPC Profile Application extension document and applied a few changes (though fewer than I originally thought). I've uploaded a change-tracked version to GridForge (in the JSDL documentation tree) which has my changes in it together with comments detailing a few issues that I think could do with addressing before it goes final. (Some comments just describe reasoning behind one or two of the changes I've made though.) https://forge.gridforum.org/sf/docman/do/viewDocument/projects.jsdl-wg/docm… The main thing of note I suppose is that I've beefed up the Security Considerations to state that it is important that the UserName element not be allowed to do end-runs around security. But that needs checking by someone else to ensure that I've not gone too far and required that implementations *have* a security context that could allow deduction of what username to use. That's just the sane thing to do... :-) Cc:ing the JSDL WG so that they can get a chance to review the doc (plus my comments) too. Donal.

5 14

Teleconference, Sep 6 (2:30pm BST)
by Andreas Savva 06 Sep '06

06 Sep '06

We are having a call this **Wednesday (Sep.6), half-an-hour earlier** than the usual time; see bottom of email for complete details. A tentative agenda follows. Email the chairs if you want to add anything to this. The order may change since some members can attend either the first or the second half-hour of the call. 1. Confirm GGF18 plan (espl. people presenting/leading) See minutes of last call (8/16) for details. https://forge.gridforum.org/sf/go/doc13751?nav=1 2. Review Extension drafts - HPC Application draft worked on by the HPCP WG - Parallel Application (draft to be sent out soon) - Decide how to proceed with the Parameter sweep and with the Dependency proposals 3. Other business ----- Date: ** 6 September 2006 ** Time: 2:30pm BST / 9:30am EDT / 6:30 am PDT / 10:30pm JST Duration: 1 hour Dial-in numbers (toll): US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 207 3655269 (London) Japan: +81 3 3570 8225 (Tokyo) Complete dial-in information: http://tinyurl.com/eg48j Participant PIN: 4371991

1 1

[wg-all] Mailing List Changes
by Andre Merzky 03 Sep '06

03 Sep '06

Sorry for duplicates ------------------------------------------------------------ As of yesterday, all GGF/OGF mailing lists are migrated to the ogf domain. They are now managed by mailman, the web interface is available at http://www.ogf.org/mailman/listinfo With that migration, all list can be now reached via <list>@ogf.org The old @ggf.org addresses will be available for some time, but are bound to disappear eventually - please start using the ogf addresses! A number of lists have changed their names: ggf-it --> ogf-it ggf-office --> ogf-office ggf-proc-wg --> ogf-proc-wg ggf-sponsors --> ogf-sponsors ggf-tutorials --> ogf-tutorials ggf-compute --> ogf-compute ggflistowners --> ogflistowners ggfstudentmembers --> ogfstudentmembers Postings to the old list names get forwarded to the new ones. With the migration we have also been able to fix the archives - you may have noticed that list archiving stopped sometime in mid June. Well, now its working again, and all mails from June to now have been added to the archive. The list archives can be found at: http://www.ogf.org/archives/<list> If you are an list administrator, and would like to receive the list admin password, please contact postmaster(a)ogf.org. In general, however, we tried to map the old majordomo settings to the mailman settings, in terms of privacy etc, so no or little changes should be required from your side. The spam avoidance policy has been changed to some extent, and is somewhat stricter than before. Please let us know if you experience any trouble with that. On all questions in respect to mailing lists, or mails in general, please contact postmaster(a)ogf.org. Best regards, Andre. -- "So much time, so little to do..." -- Garfield -- wg-all mailing list wg-all(a)ogf.org http://www.ogf.org/mailman/listinfo/wg-all

1 0

Questions about JSDL specification
by Alain Roy 01 Sep '06

01 Sep '06

Hello, I have been reading the JSDL specification, and I have a few questions about it. 1) I want to make sure that I understand "support" and "satisfy" as defined on page 7. If a system can parse a JSDL document, then it supports it, and if it can do everything requested by the JSDL document, then it satisfied it. Is that correct? 2) Just to make sure I understand support, when it says "The JSDL core element set contains the semantics for elements that are defined by JSDL 1.0. All elements MUST be supported by JSDL 1.0 compliant consuming systems.", that simply means that they need to be parsed, not that the need to be accepted, correct? 3) ApplicationName identifies the executable. I don't understand where the executable comes from. Do we expect that the underlying system can figure out which program to run from the name and version, and that it is pre-staged? Can applications bring their executable with them by staging it? Am I supposed to use the POSIXApplication element? I'm confused how this fits together. 3) When I specify the operating system: how do I specify linux version? Kernel version? Distro + version? Is it dependent on the underlying system? 3) IndividualCPUCount allows me to specify a range in terms of double: what does this mean? For example, if I specify that I want 3.14 CPUs, it's a legal specification, but I don't know what it means. Ditto for IndividualPhysicalMemory and IndividualVirtualMemory and IndividualDiskSpace. 3) I don't undersatnd IndividualNetworkBandwidth: bandwidth to where? Does this refer just to the local NIC? What if there are multiple NICs? 4) I'm confused how IndividualDiskSpace interacts with the filesystem element. The FileSystem element specifies how much disk space is needed on a particular file system: the IndividualDiskSpace says something about disk space, but not about where the disk space is located. Which disk space is it? What does it mean if I specify a FileSystem and IndividualDiskSpace? 5) I don't understand the difference between IndividualCPUCount and TotalCPUCount. Can I think of it as the number of CPUs on a single node, and the total number needed across all nodes? Or does it mean something different? 6) When I stage files, the destination might be a filesystem on NFS. If I'm running many jobs at the same time, the files might clobber each other unless I give the files unique names: is the user responsible for doing so, or is there some way to specify a unique identifier in the file name? For example, in Condor I can say something like File.$(Process) to get a unique filename based on the job id. Thanks for any assistance in understanding! -alain

5 7

Friday (Sept 1) conf call will cover JSDL basic execution extension, interop plans
by Marvin Theimer 30 Aug '06

30 Aug '06

Hi; This Friday's HPC Profile call will be at the usual time and "place": * Friday, 9/1, at 10AM EDT (7AM PDT) * 1-866-500-6738 (from US & Canada) or 1-203-480-8000 * Passcode: 1157025 The tentative agenda is the following: * Cover the suggested changes to the JSDL basic execution extension specification. (We didn't have quorum at today's JSDL conf. call, so we are pushing discussion to the HPC Profile conf. call and will then be sending a "summary" email to the JSDL mailing list requesting comments.) * Discuss interop plans and compliance specifications. Marvin.

1 0