-
Notifications
You must be signed in to change notification settings - Fork 34
Update appliance for stackhpc.openhpc nodegroup/partition changes #666
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
base: main
Are you sure you want to change the base?
Conversation
TODO: test this with adding |
Testing in .stackhpc env with adding "extra" nodes:
Ok.
OK.
OK |
a7b5cc1
to
32fb617
Compare
WIP: testing on azimuth as slurm-v21 - running, but need to redeploy slurm after last force-push |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sensible to me. Just need to wait for the openhpc role changes to merge so that we can update requirements.yml.
Now fully tested on CaaS. |
Converted to draft because #668 must merge first. |
TODO: Update description below once below PR merges
Changes to cope with stackhpc/ansible-role-openhpc#183 which changed
openhpc_slurm_partitions
toopenhpc_nodegroups
andopenhpc_partitions
:Note that:
cluster_compute_groups
variable templated into theinventory/hosts.yml
file.openhpc_nodegroups
is calculated inenvironments/common/inventory/group_vars/all/openhpc.yml
. This creates a node group per key in the OpenTofucompute
variable. This is usually what is required, but this variable will overriding if custom Node-level Slurm parameters/configuration is required (e.g. for GRES).openhpc_partitions
is calculated. This includes one partition per node group, plus a rebuild partition if therebuild
group is active. This should not generally be overriden. Instead normal (non-rebuild) partitions should be modified usingopenhpc_user_partitions
, which is the same format.#665 is replaced by this.