Fwding bounced mail... -- ---------------------------------------------------- |epcc| - Ali Anjomshoaa EPCC, University of Edinburgh James Clerk Maxwell Building Mayfield Road E-mail: ali@epcc.ed.ac.uk Edinburgh EH9 3JZ Phone: + 44 (0) 131 651 3388 United Kingdom Fax: + 44 (0) 131 650 6555 ------------------------------------------------------------- ---------- Forwarded message ---------- Date: Thu, 25 Nov 2004 12:15:10 +0300 From: "Lukichev, Alexander S" <alexander.s.lukichev@intel.com> To: jsdl-wg@gridforum.org Cc: "Ratering, Ralf" <ralf.ratering@intel.com>, "Kentemich, Thomas" <thomas.kentemich@intel.com>, "Petrov, Dmitry N" <dmitry.n.petrov@intel.com>, "Odintsov, Igor O" <igor.o.odintsov@intel.com> Subject: application abstraction in JSDL Hi, Our team is currently develops an application that will use JSDL documents as input to invoke jobs in a distributed system. I'd like to comment if possible some aspects of the latest JSDL schema. Currently to describe the job to run you can specify: a) executable name b) arguments c) environment variables This could be not enough configurable because executables can reside at different places on the different systems, arguments can be passed in different ways to close applications on different systems, etc. Thus JSDL contains pretty enough information for locating the suitable server, the located server could fail to run the requested application because of lack of configuration information. We can look at the UNICORE experience and try to configure the particular applications using the following entities: a) fields (i.e. partucular file names, argument values, e.g. "source=a.c", "size=1234") b) options (i.e. names for common modes of application work; though setting this mode could differ from system to system, e.g. "debug=on" results in passing "-g" to some compilers) c) contexts (modes for application invocations, e.g. "profiliration") d) variations (variations of expected results, e.g. "overwrite" for file operations) It would be nice if some kind of such specification (probably with another entities but with the idea of abstraction of application) is described in the JSDL spec. Thanks. Alexander