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

Support for OpenPBS #136

Open
xpillons opened this issue Jun 5, 2023 · 5 comments
Open

Support for OpenPBS #136

xpillons opened this issue Jun 5, 2023 · 5 comments
Labels
dev-onboarding? Identifies Issues that might make a good starting point for new devs (quick/simple/self-contained) enhancement help wanted

Comments

@xpillons
Copy link

xpillons commented Jun 5, 2023

OpenPBS and Torque have different outputs and options for qstat.
Please add support for OpenPBS

@mej
Copy link
Owner

mej commented Jun 6, 2023

Well, I'm afraid I am not at all familiar with OpenPBS's command syntax or how it differs from TORQUE or PBS Pro, nor do I have a cluster running OpenPBS to test on. But NHC is fully Open Source, so you might be able to make the customizations yourself -- and if you do, we'd love for you to contribute your work to the project! (But you absolutely are not required to do so.) 😀

@mej mej added enhancement help wanted dev-onboarding? Identifies Issues that might make a good starting point for new devs (quick/simple/self-contained) labels Jun 6, 2023
@jbaksta
Copy link

jbaksta commented Jun 20, 2023

I've started swapping over to NHC from in-house and am looking to do PBS Pro as well. I've started small things, but there is enough difference between the two, might make sense to have NHC_RM=pbspro as the variant. Normally I wouldn't mind openpbs, but openpbs has a weird anthropology(?) in this case.

@mej
Copy link
Owner

mej commented Jul 26, 2023

It's interesting for me to hear that OpenPBS, PBS Pro, and TORQUE have diverged to such a degree -- having done a significant amount of work with TORQUE internals but never having even touched either of the other 2 🤣 -- but it's not really surprising either.

If it's impossible, impractical, or imprudent to try to treat them all as "similar enough," I think that's fine, and I'm perfectly happy having NHC_RM=pbspro and NHC_RM=openpbs be distinct from NHC_RM=pbs. It might be wise, in fact, to move toward NHC_RM=torque for the 1.5 release to avoid ambiguity and/or confusion going forward!

Is this something you'd be interested in contributing? If so, welcome, and feel free to ask questions, share works in progress, etc. along the way! 😁

@jbaksta
Copy link

jbaksta commented Jul 27, 2023

I think we might be willing to push a pbspro variant at some point. We'll probably end up having to still override that as we have another tool that we put on top that does some more automation around that which we were thinking about using for doing the online/offline actions and I'm unsure what that tool will offer me as an API.

That being said, I think it would be valuable to have a pbspro basic integration available and try to minimize the harm that can be inflicted on pbspro server itself too.

@xpillons
Copy link
Author

xpillons commented Jul 31, 2023

I agree that due to the divergence it would make sense to have pbspro and openpbs variant. The more challenging part will be the epilog or prolog scripts as these are not scripts configured from the config file, but rather python hooks that need to be specifically configured and written making the reuse of bash script less useful.

I may be able to contribute but more as a tester rather than a writer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev-onboarding? Identifies Issues that might make a good starting point for new devs (quick/simple/self-contained) enhancement help wanted
Projects
None yet
Development

No branches or pull requests

3 participants