Azure / cyclecloud-slurm

Azure CycleCloud project to enable users to create, configure, and use Slurm HPC clusters.
MIT License
58 stars 43 forks source link

Allow node features that match standard_*, as to not conflict with customer environments #152

Closed ryanhamel closed 1 year ago

ryanhamel commented 1 year ago

Allow standard_* features to be set so that we do not conflict with customer environments

ryanhamel commented 1 year ago

Testing

1) set vm_sizes to Standard_F2s_v2,Standard_D2_v5 for the dynamic partition in the CC UI (in that order)

2) start the cluster

3) create 3 sets of nodes

directly maps to F2s

scontrol create nodename=dyn-[1-10] state=CLOUD feature=dyn,standard_f2s_v2,a

directly maps to D2_v5

scontrol create nodename=dyn2-[1-10] state=CLOUD feature=dyn,standard_d2_v5,b

does not map to anything, but does have standard_test which should reveal additional logging

2023-08-10 19:32:08,170 WARNING: Found potential vm_size standard_test - however none match approved vm sizes standard_f2s_v2,standard_d2_v5. Is this a typo?

scontrol create nodename=dyn3-[1-10] state=CLOUD feature=dyn,standard_test,c

4) create the nodes oen at a time, and then 3 more all at once azslurm resume --no-wait --node-list dyn-1 azslurm resume --no-wait --node-list dyn2-1 azslurm resume --no-wait --node-list dyn3-1

azslurm resume --no-wait --node-list dyn-2,dyn2-2,dyn3-2

confirm that the appropriate nodes are created

azslurm nodes -o name,vm_size