| Summary: | Reservations using GRES | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | tyler.boswick |
| Component: | User Commands | Assignee: | Scott Hilton <scott> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 4 - Minor Issue | ||
| Priority: | --- | ||
| Version: | 19.05.5 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.schedmd.com/show_bug.cgi?id=9462 | ||
| Site: | NOAA | Alineos Sites: | --- |
| Atos/Eviden Sites: | --- | Confidential Site: | --- |
| Coreweave sites: | --- | Cray Sites: | --- |
| DS9 clusters: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | GFDL | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Linux Distro: | --- |
| Machine Name: | CLE Version: | ||
| Version Fixed: | Target Release: | --- | |
| DevPrio: | --- | Emory-Cloud Sites: | --- |
|
Description
tyler.boswick
2020-07-22 12:11:49 MDT
Tyler, I checked gres and there is no option for it. (And the Tres option doesn't support it.) However, I found the documentation of features: Features=<features> Set the reservation's required node features. Multiple values may be "&" separated if all features are required (AND operation) or separated by "|" if any of the specified features are required (OR operation). Parenthesis are also supported for features to be ANDed together with counts of nodes having the specified features. For example "Features=[(knl&a2a&flat)*4&haswell*2]" indicates the advanced reservation should include 4 nodes with ALL of the features "knl", "a2a", and "flat" plus 2 nodes with the feature "haswell". Value may be cleared with blank data value, "Features="." (https://slurm.schedmd.com/scontrol.html#OPT_SPECIFICATIONS-FOR-CREATE,-UPDATE,-AND-DELETE-COMMANDS,-RESERVATIONS) Looking at this documentation I think it should work for your use case. However, when I tried to create a reservation using this feature, nothing changed; everything was allocated as if I didn't use the feature. I think this is a bug. I will look into it and get back to you. In the mean time, let me know if you have any other questions about this. -Scott Tyler, I talked to a colleague and found that I was mistakenly using our pre-release slurm version. I tested it on 20.02 and 19.05 and it works just fine. No need to worry about the bug. I think the feature system should work for your use case. Let me know how it goes and if you have any follow up questions. -Scott Hi Scott, Sorry for the delayed response. I will bring this information back to the person requesting and let you know the results. Thanks! Tyler, I am going to assume it worked as expected and go ahead an close this ticket for now. If you or your customer need more help with this feel free to reopen the ticket. Take care, Scott |