Yes, everything is optional in a JSDL document, but everything is also optional in a DRMAA job template. In both cases, submitting a job from an empty template is result in a failure. I think a JSDL integration for DRMAA would be an elegant solution to this problem. Because JSDL defines an extension mechanism, we could define a JSDL-DRMAA document format. Daniel Peter Troeger wrote:
JSDL is the answer. It defines a well-discussed set of possible attributes and their semantic. But in contrast to DRMAA, there are no mandatory attributes in a JSDL document. Making everything optional is not the DRMAA style, at least for me.
Peter.
Currently, users can specify resource requirements only using native specification or using job categories. This approach is DRMs dependant and not portable. It would be good to add some new optional attributes (e.g. number_cpu, min_memory) to deal with this problem.
The 'lack of portability' is a consequence of not specifying an interface for number_cpu, min_memory, etc.
I don't think the 'approach' for specifying attributes is inherently nonportable.
By the way, In addition to 'native specification' and using 'job categories' DRMAA implementations may introduce implementation-specific job template attributes.
-Roger -- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg
-- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg