You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@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.
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.
stalebot
added
the
stale
This issue is in danger of being automatically closed
label
Apr 10, 2022
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?
The text was updated successfully, but these errors were encountered: