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

Supporting Additional Allocations #115

Open
alexandermichels opened this issue Apr 2, 2024 · 0 comments
Open

Supporting Additional Allocations #115

alexandermichels opened this issue Apr 2, 2024 · 0 comments

Comments

@alexandermichels
Copy link
Member

Currently all jobs are run under our allocation which is often specified in the HPC configurations (https://github.com/cybergis/cybergis-compute-core/blob/v2/configs/hpc.example.json#L75) . However, we would like to add support for end-users to run their own jobs using their own allocations.

A few ideas for implementations:

  1. A textbox to specify the allocation (basically a SLURM option in the manifest that makes a textbox in the SDK), but we need to make sure this overrides any option in the configuration and we need to figure out the logistics of how that would work (e.g. do they need to add our community account to their allocation, is there anything else that needs to be done?).
  2. An allowlist that associates HPC/allocation pairs to users so that only certain users can use certain allocations.
  3. We should be able to ignore the defaultSlurmCeiling if using an external allocation:
    var defaultSlurmCeiling = {
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant