Well, this was kind of a little side project for the SOAP interface. To
submit a job to the SOAP interface the client has to build a ClassAd
that represents the job. This would usually be a pretty trivial
operation, but Condor has a few things to say about it in the form of
all sorts of default attributes that are required for things like
condor_q to work properly. So, to combat this annoyance we introduced a
CreateJobTemplate() call, which was very specialize and ugly. It would
take a few things like Cmd/User and make a Job Ad the client could then
submit. The template service is just a generalization of the
CreateJobTemplate() that allows for multiple kinds of templates that
could even be application specific, i.e. a template for a BLAST job
might not need a Cmd since the template knows where blast is installed
in the pool. The need for a more powerful template, i.e. one that can
do some of the things I described in my original message, are needed
for things like DAGMan jobs, which require the Env attribute be setup
properly. Anyway, I'm sure that is more than you wanted to know. 8o)
matt
On Jul 28, 2004, at 11:31 AM, Joe Nelson wrote:
I guess just the desire to implement when I had originally describe,
which was for a template service of sorts.
Cool. :) What part of Condor will the template thing be a part of? I'm
always
happy to hear about parts of Condor evolving to use Classads.
--Joe
Condor Classads Info:
http://www.cs.wisc.edu/condor/classad/
Condor Classads Info:
http://www.cs.wisc.edu/condor/classad/
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}