Update A3 mega blueprint to use Slurm-GCP 6.5.12 #2763
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the A3 Mega slurm image building solution in 2 ways:
The first change aids alignment of Terraform code with the Python autoscaling code added during image building. We previously (#2746) re-enabled
enable_devel: true
which should avoid any problems, but alignment is good.The second change is critical to address problems introduced by GoogleCloudPlatform/guest-agent#401, which perfectly describes the A3 Mega solution: an ethernet device naming problem stemming from building an image on a Packer VM without local SSD and then provisioning A3 Mega VMs (with local SSD) using the image. The resulting compute nodes that cannot join the network or the cluster.
Before the PR, we observe <10% of nodes joining initially and rarely managing to succeed after every ~1000s retry cycle. After the PR, we see 100% of nodes joining on the first try.
Future work can be done to update the base debian-12 image (from April 2024) to one that includes the fix to GoogleCloudPlatform/guest-agent#401.
Submission Checklist
Please take the following actions before submitting this pull request.