Update A4high blueprints to use pre-built ACI image

[ksaishree]

Replacing the Ubuntu accelerator image with ACI image in A4high blueprint.

Integration tests and NCCL tests passed successfully.

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.

Please take the following actions before submitting this pull request.

• Fork your PR branch from the Toolkit "develop" branch (not main)
• Test all changes with pre-commit in a local branch #
• Confirm that "make tests" passes all tests
• Add or modify unit tests to cover code changes
• Ensure that unit test coverage remains above 80%
• Update all applicable documentation
• Follow Cluster Toolkit Contribution guidelines #

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the A4high blueprints to leverage pre-built Advanced Compute Images (ACI), significantly reducing build complexity. It also introduces Filestore for shared home directories, optimizes GCSFuse mount configurations, and improves the robustness of startup scripts for Enroot and GPU health checks. These changes collectively streamline the deployment process and improve environment stability for A4high clusters.

Highlights

• ACI Image Integration: Updated A4high blueprints to utilize pre-built Advanced Compute Images (ACI) instead of building custom images, simplifying deployment.
• Storage and Networking: Added Filestore support for shared home directories and updated network configuration to include Filestore IP ranges.
• Startup and Environment Fixes: Improved startup scripts for better Enroot environment handling, including AppArmor adjustments and hostname generation, and standardized GCSFuse mount options.
• Resource Optimization: Downsized controller machine types to e2-standard-16 and added metadata configurations for better instance management.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the Slurm blueprints to use pre-built advanced compute images instead of building custom images with Packer, simplifies the startup scripts, and updates GCSfuse mount options to use standard profiles. Feedback on these changes highlights that downloading and installing the CUDA toolkit during node startup is redundant since the selected image already has CUDA 13.0 pre-installed. Additionally, it is recommended to configure the AppArmor unprivileged user namespace restriction permanently using sysctl via /etc/sysctl.d/ rather than writing directly to /proc/sys.

[Neelabh94]

/gcbrun

[Neelabh94]

/gcbrun

[Neelabh94]

LGTM

[Neelabh94]

@ksaishree please wait for the integration test "PR-test-ml-a4-highgpu-onspot-slurm" to pass before merging.