I agree to Bruno and Andre that the advantages are worth it. Performance considerations should be done in the language bindings and / or the implementations, the root spec is the wrong place for that. I therefore vote for the simple addition all job templates attributes to the JobInfo structure.
An interesting side aspect are implementation-specific job template attributes. I would prefer to leave it to the implementors if they want to support them also in the JobInfo structure. If Daniel agrees to all of this, especially from his implementation viewpoint in Grid Engine 8.2, then I would update the root spec and the C binding accordingly. Best regards, Peter. Am 12.09.2014 um 22:18 schrieb Andre Merzky <[email protected]>: > I think the job template information are easy to add, and make app > writing easier (I don't need to keep the old submitted job template > around...). Only drawback I see is increase in memory footprint when > used to report on many jobs -- but when used as a filtering > instruction, this should not matter. > > > My $0,02, Andre. > > On Wed, Sep 10, 2014 at 7:48 PM, Peter Tröger <[email protected]> wrote: >> Dear all, >> >> at OGF-42, we stumbled over the issue that „JobInfo“ does not contain the >> original job name being used in the template: >> >> http://redmine.ogf.org/issues/102 >> >> This leads to the situation that you cannot filter for it when doing >> monitoring. >> >> Although we quickly decided to add it, I meanwhile figured out that this is >> a deeper problem. JobInfo intentionally contains nothing from the job >> template at the moment, which makes perfectly sense if you see it as a pure >> reporting data structure. You don’t need to fetch information that you >> handed in by yourself as the calling application. >> >> For filtering, however, you obviously want to have all of the template >> attributes being usable. This is not possible at the moment. >> >> Another case is the „change job template after submission“ magic in Grid >> Engine, which could lead to the fact that your job has different attributes >> from what you originally specified. You may also want to see that in the >> JobInfo structure. >> >> All in all, it seems like that „JobInfo“ needs all of attributes from >> „JobTemplate“ too, not only the job name. >> >> What do you think ? >> >> Best regards, >> Peter. >> >> >> >> >> >> -- >> drmaa-wg mailing list >> [email protected] >> https://www.ogf.org/mailman/listinfo/drmaa-wg > > > > -- > It was a sad and disappointing day when I discovered that my Universal > Remote Control did not, in fact, control the Universe. (Not even > remotely.)
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- drmaa-wg mailing list [email protected] https://www.ogf.org/mailman/listinfo/drmaa-wg
