Open mrocklin opened 7 years ago
@mrocklin I think that keeping the job template attributes inside python makes more sense since the python drmaa library does a lot of C-drmaa wrapping. If for some reason, the drmaa session dies and has to be reinitialized, the drmaa job templates might be lost (speculation).
Yeah, in #10 we now generate a new job template every time we launch new workers.
Currently we create a single job template to create all workers.
This job template is easily accessible and so provides a nice and familiar release valve for expert users of python-drmaa who want to customize their setup.
However as we submit slightly different kinds of worker jobs we'll want to modify this template a bit, by specifying extra native specifications and by adding extra keywords to the
dask-worker
command.I'm unable to find a way to copy-and-append an existing job template, which leads me to instead consider storing all of the job template attributes (args, native spec, command, error path, etc.) bare, instead of within a job template object. Then we'll create a new job template for each call to
start_workers
.Does anyone see a better way?
cc @davidr