Reuse SbatchStep
and QsubSteps
functions when creating DragonBatchSteps
#595
Labels
area: Dragon
area: job
Issues related to job management
type: feature
Issues that include feature request or feature idea
Description
DragonBatchStep
should convert the step to aSbatchStep
or to aQsubStep
and directly use the correspondingwrite_script
methods, instead of re-implementing them.Justification
The
DragonBatchStep
has to create either a Sbatch or a Qsub script to be run through the corresponding scheduler. Currently, the functions to create such scripts are implemented inDragonBatchStep
, but they are only slight variations of theSbatchStep
andQsubStep
counterparts. It would be better to convert the step internally to the appropriate batch step, and by doing so, being able to re-use its methods.Implementation Strategy
The
DragonBatchStep
needs to create the request file, which is not created by Slurm or PBS batch steps, usually. This needs to happen before the step is converted. Moreover, the internal step (which would usually be aSrunStep
on Slurm and one of the equivalent types on PBS), will need to be aLocalStep
, used to start thedragon_client.py
entrypoint as we currently do. But thisLocalStep
will have to be proxied - noindirect.py
entrypoint should be invoked, as the job will still be managed through Dragon.The text was updated successfully, but these errors were encountered: