Split up this package

[andreasnoack]

There is not much shared code between the managers and most of us only use a single workload/cluster manager so it is difficult to review PRs.

Finished:

• Slurm (via srun): Done: JuliaParallel/SlurmClusterManager.jl
• Load Sharing Facility (LSF) (via bsub): Done: JuliaParallel/LSFClusterManager.jl
• ElasticManager: Done: https://github.com/JuliaParallel/ElasticClusterManager.jl

Currently in progress:

• HTCondor (via condor_submit) : In progress here: https://github.com/JuliaParallel/HTCondorClusterManager.jl

Not yet started:

• Scyld (via bpsh): not started yet. Currently still lives in this package. We are looking to recruit a maintainer.
• Sun Grid Engine (SGE) (via qsub and/or qrsh): not started yet. Currently still lives in this package. We are looking to recruit a maintainer.
• Portable Batch System (PBS) (via qsub): not started yet. Currently still lives in this package. We are looking to recruit a maintainer.
• LocalAffinityManager (for pinning local workers to specific cores): not started yet. Currently still lives in this package. We are looking to recruit a maintainer.

[azraq27]

That's a good point. Any code that actually is shared should probably be submitted to Base instead of keeping it here.

[amitmurthy]

Should the split packages be with individual contributors or under JuliaParallel ? The maintainers of the separate cluster managers ought to be users of the specific manager.

[kleinhenz]

I just created SlurmClusterManager.jl if anyone is interested in giving it a try.

[kescobo]

And there's https://github.com/simonbyrne/SlurmTools.jl

[vchuravy]

I just created SlurmClusterManager.jl if anyone is interested in giving it a try.

Requires that SlurmManager be created inside a Slurm allocation created by sbatch/salloc. Specifically SLURM_JOBID and SLURM_NTASKS must be defined in order to construct SlurmManager. This matches typical HPC workflows where resources are requested using sbatch and then used by the application code. In contrast ClusterManagers.jl will dynamically request resources when run outside of an existing Slurm allocation. I found that this was basically never what I wanted since this leaves the manager process running on a login node, and makes the script wait until resources are granted which is better handled by the actual Slurm queueing system.

Oh so much yes! ;)

[juliohm]

We are barely able to maintain a single repository with working versions of the managers. My opinion is that we should unite efforts and collect people with similar skills here to watch out for improvements made to particular managers. Also, from the user's point of view, it is annoying to have a different environment depending on where the script is to be run. Right now we can simply do ]add ClusterManagers and move on.

[bjarthur]

@juliohm i disagree, and so do many others i think. my view is that clustermanagers.jl works as is, and so we should leave it be. if we want to make changes, then i would prefer to split it up instead of unifying the code base as you propose in #145. re-opening this issue.

[juliohm]

You mean you agree that we should split this package into multiple packages for specific managers @bjarthur?

[mashu]

Perhaps a common abstract interface should be put in place such that managers can use it? I was looking for SLURM manager, but it's very confusing which one should I use ?