does not define control. There is a comment in the above PR that this might be ok with appropriate overrides.
However I think we're assuming the cookiecutter should give us "everything + terraform". Are we actually happy with that? I am TBH. If so, maybe we should use the TF from the nrel-workshop branch (which is significantly more flexible in terms of allowing for image changes, multiple types of compute nodes, and auto-creating partition groups based those compute node types). That creates a separate control/login node which is probably a better "production-ready" example.
Not sure PR #19 was really ready to merge
https://github.com/stackhpc/ansible-slurm-appliance/blob/main/environments/skeleton/%7B%7Bcookiecutter.environment%7D%7D/terraform/inventory.tpl
does not define
control
. There is a comment in the above PR that this might be ok with appropriate overrides.However I think we're assuming the cookiecutter should give us "
everything
+ terraform". Are we actually happy with that? I am TBH. If so, maybe we should use the TF from thenrel-workshop
branch (which is significantly more flexible in terms of allowing for image changes, multiple types of compute nodes, and auto-creating partition groups based those compute node types). That creates a separate control/login node which is probably a better "production-ready" example.