Skip to content

scripts: improve job launcher interface #578

@adammoody

Description

@adammoody

The JobLauncher interface for launch_run() is ambiguous in that some launchers require the list of nodes to run on (like aprun and mpirun) while others take the list of nodes to avoid (like srun and jsrun). For proper polymorphism, we need to settle on one approach so that the interface is consistent across all implementations.

Additionally, let's create a JobLauncherRun class to be returned by launch_run() which will later be passed to wait_run() or kill_run(). This class will represent a launched parallel run, and it will encapsulate the details of the proc and jobid values currently returned by launch_run. It could also provide stdout(), stderr(), and rc() functions so one can query the results of the parallel run.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

To do

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions