Summary: | Use of single_node_vni in HPE slingshot | ||
---|---|---|---|
Product: | Slurm | Reporter: | Thomas.green |
Component: | HPE Slingshot | Assignee: | Tim McMullan <mcmullan> |
Status: | OPEN --- | QA Contact: | |
Severity: | 4 - Minor Issue | ||
Priority: | --- | ||
Version: | 23.02.6 | ||
Hardware: | Linux | ||
OS: | Linux | ||
Site: | Bristol AI | Alineos Sites: | --- |
Atos/Eviden Sites: | --- | Confidential Site: | --- |
Coreweave sites: | --- | Cray Sites: | --- |
DS9 clusters: | --- | HPCnow Sites: | --- |
HPE Sites: | --- | IBM Sites: | --- |
NOAA SIte: | --- | NoveTech Sites: | --- |
Nvidia HWinf-CS Sites: | --- | OCF Sites: | --- |
Recursion Pharma Sites: | --- | SFW Sites: | --- |
SNIC sites: | --- | Tzag Elita Sites: | --- |
Linux Distro: | --- | Machine Name: | |
CLE Version: | Version Fixed: | ||
Target Release: | --- | DevPrio: | --- |
Emory-Cloud Sites: | --- |
Description
Thomas.green
2025-03-07 04:33:53 MST
Just checked slurmctld.log and see: error: Single-node VNI requested by user, but 'single_node_vni=<all|user>' not set in SwitchParameters What is odd is that setting that will always use it - I would have assumed I could override with the --network. You will probably want to set this in the slurm.conf file:
> SwitchParameters=single_node_vni=user
By default it is set to "none" which is why you are seeing the requested by user but not set in the config error.
single_node_vni=user should only allocate the VNI when a user requests it which sounds like the behavior you are expecting!
Let me know if this helps!
Thanks!
--Tim
Hi, Thanks for the quick reply. I didn't realise that user is what signifies that - I thought it was related to how VNI is configured in Slingshot. Makes perfect sense - will put in a change request locally to add that option. Thanks. (In reply to Thomas.green from comment #3) > Hi, > > Thanks for the quick reply. I didn't realise that user is what signifies > that - I thought it was related to how VNI is configured in Slingshot. > Makes perfect sense - will put in a change request locally to add that > option. > > Thanks. Sure thing, I'm glad I could help! Let me now how the change goes! --Tim |