Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove LSF cluster interface #375

Open
timtroendle opened this issue May 13, 2024 · 4 comments
Open

Remove LSF cluster interface #375

timtroendle opened this issue May 13, 2024 · 4 comments
Labels
bug Something isn't working workflow Related to the design and execution of the workflow.

Comments

@timtroendle
Copy link
Member

timtroendle commented May 13, 2024

What happened?

The LSF cluster interface has been broken in #330. In fact, we want to drop LSF support and should remove all traces of LSF.

Version

1.2.0.dev

Relevant log output

No response

@timtroendle timtroendle added the bug Something isn't working label May 13, 2024
@timtroendle
Copy link
Member Author

@calliope-project/euro-calliope-devs , I fixed this but in fact I cannot test it as LSF has been switched off at ETH in favour of Slurm. Do people require LSF? Otherwise, this can be seen as a non-issue and we could remove the LSF capabilities.

Either way, we should implement #244 to allow for cluster execution on Slurm.

@timtroendle timtroendle added the workflow Related to the design and execution of the workflow. label May 13, 2024
@irm-codebase
Copy link
Contributor

DelftBlue also uses SLURM for scheduling jobs. So on our end it should be perfectly OK to drop the feature.

@timtroendle
Copy link
Member Author

Thanks for letting me know. I'll rename the issue accordingly.

@timtroendle timtroendle changed the title Fix regression in cluster interface Remove LSF cluster interface May 13, 2024
@brynpickering
Copy link
Member

Cambridge HPC also uses SLURM, so removing LSF support is fine by me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working workflow Related to the design and execution of the workflow.
Projects
None yet
Development

No branches or pull requests

3 participants