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

Automatic queue creation based on node profile/type #747

Closed
renzo-granados opened this issue Jan 25, 2022 · 2 comments
Closed

Automatic queue creation based on node profile/type #747

renzo-granados opened this issue Jan 25, 2022 · 2 comments
Labels
enhancement New feature or request stale This issue is in danger of being automatically closed

Comments

@renzo-granados
Copy link

In order to prevent unnecessary manual intervention of SLURM configuration is it possible to use the current node discovery process to identify the compute node type (i.e. GPU, CPU, Mem_Intensive, etc) and assign it to its type queue?

Describe the solution you'd like
Automatic queue configuration based on node discovery after setup or reconfiguration.

Describe alternatives you've considered
If queue autoselection is not an option is it possible to document how to perform the configuration steps based on the discovery findings?

@renzo-granados renzo-granados added the enhancement New feature or request label Jan 25, 2022
@sujit-jadhav
Copy link
Collaborator

@renzo-granados We will check on this and update you.
In upcoming release may be Omnia.NEXT we will have telemetry insights where we will be suggesting compute nodes based on the hardware health, configuration.

@stale
Copy link

stale bot commented Apr 10, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale This issue is in danger of being automatically closed label Apr 10, 2022
@stale stale bot closed this as completed Apr 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale This issue is in danger of being automatically closed
Projects
None yet
Development

No branches or pull requests

2 participants