Spack in a Multi-User HPC Environment on Azure
Spack is a package management tool designed for HPC environments. In this article we will demonstrate how to install and configure Spack in a multi-user HPC environment on Azure with shared and user repositories. An environment could be easily created with Azure HPC On-demand Platform (Az-HOP) or Azure CycleCloud. This allows the system administrator to provide a collection of shared packages to all users and individual users can build packages on top of this in their own repository without rebuilding or interfering with one another.
Initial setup
Create a user to store shared packages, for example spackuser. Log on as spackuser. Download spack from GitHub:
Use the development branch as it contains latest Intel packages. To load the environment:
Changing the number of processors to build with:
Fixes for Azure
Spack detects the CPU using CPUID flags. Azure platform exposes subset of the flags supported by underlying CPUs, in some cases causing spack to detect architecture incorrectly. In particular, “clzero” flag is not exposed in Azure HB VM and “pku” flag is not exposed in Azure HBv3. These flags are used to detect “zen” and “zen3” platforms. To correct spack detection on Azure, these flags need to be removed from the microarchitecture definition:
Installing Compilers
Using System Compilers
At the time of writing, gcc-9.2.0 is included in the CentOS HPC image, and the following command will register it with spack:
However, when initially installing it will find a compiler in the path. You can check installed compilers using:
Installing latest GCC
First command will download sources for GCC and dependencies, and build them. Second command will set up environment variables, and the last command registers the newly built compiler. Parameter “--scope site” tells spack to store the compiler configuration in $SPACK_ROOT/etc/spack/ directory. It will be local to this instance of spack and shared between all users using it. Default is “--scope user” and it stores the settings in $HOME/.spack.
To check what versions of GCC are available to download from spack repositories, run the following command:
The output will show the preferred version that will be used by default. However, you can select a version using the @ syntax:
To use the specific compiler when installing other packages, for example to install intel-mpi-benchmarks compiled with gcc-12.1.0, the syntax is:
Installing MPI
MPI libraries can be installed from spack repository using spack install. Alternatively, existing MPI packages already installed on the system can also be configured. In this example we install Intel OneAPI MPI using spack, and set up preinstalled Mellanox HPC-X MPI.
Intel MPI
The latest Intel MPI can be installed from SPACK and it will correctly use InfiniBand. For example:
HPCX MPI
HPC-X MPI with other components (UCX, HCOLL) is preinstalled in the HPC image in /opt/hpcx-<version>. To add it to spack, add the following lines (note: version may be different depending on the Azure HPC image version) to the packages section of $SPACK_ROOT/etc/spack/packages.yaml:
The following code may be used to find and install all installed versions of hpcx on an Azure HPC image:
After the change to the packages.yaml is done, you need to install (register) HPCX in spack:
Install and run Intel MPI Benchmarks (IMB)
The Intel MPI benchmarks package can be used to benchmark the cluster and test the communications are working. Use spack install command to build the package with the different compilers and MPI versions, for example:
Load the package and run:
Chaining Spack Installation for Users
For users to be able to use shared packages provided by the system administrators and to create/install their own packages, one of the ways is to create a chained spack installation. To do that, individual users will need to install a private copy of spack in their home directory and connect it with the shared (“upstream”).
Install local copy of spack
Log on to the cluster as normal user and clone the repository:
Load the local environment and set your preferred “make -j” value:
Note the location of the shared install (make sure the directory is readable by users):
Copy Azure CPU definition file from the shared install:
Copy compiler configuration:
Create file spack/etc/spack/upstreams.yaml with following contents:
The chained spack is now ready to use. You can check that all upstream compilers and packages are available:
Creating a new package
Create a new package:
The initial setup will be guessed by spack. Here are updates to build:
The example we are using here does not have any build scripts associated with it and uses the base Package class with spack. The spack package install is creating the bin directory and running the mpicc command directly to build the executable. Spack has support for many different build systems available and should be autodetected from the source code. The documentation is available here.
The package can be installed, loaded and run as follows:
Published on:
Learn moreRelated posts
Code AI apps on Azure - Python, Prompty & Visual Studio
Build your own custom applications with Azure AI right from your code. With Azure AI, leverage over 1,700 models, seamlessly integrating them ...
Network Connectivity for RISE with SAP S/4HANA Cloud Private Edition on Azure
In this article, we will explore different ways to connect to RISE with SAP S/4HANA Cloud Private Edition deployment on Azure, guiding yo...
Azure Landing Zones - Policy Refresh Q1 FY25
ALZ - Policy Refresh Q1 FY25 is here! As you may be aware, the ALZ team release cadence is now on quarterly basis to help customers and partne...
Debug Queries More Efficiently with the Improved Error Messaging in Azure Cosmos DB Data Explorer
Azure Cosmos DB Data Explorer is a web-based tool available in the Azure Portal that allows you to manage data, as well as track and fix issue...
Meet the Winners | Microsoft Developers Azure AI & Azure Cosmos DB Learning Hackathon
Azure Cosmos DB powers some of the world’s most popular intelligent apps like ChatGPT. In a recent hackathon, Over 9,500 developers engaged wi...
Introducing RBAC Authentication and more for the Azure Cosmos DB Integrated Cache
We’re excited to announce new features for the Azure Cosmos DB! The integrated cache is built into the dedicated gateway, and now there’s new ...
Microsoft DiskANN in Azure Cosmos DB Whitepaper
We are excited to publish a new whitepaper titled, Microsoft DiskANN in Azure Cosmos DB, where we examine the impressive capabilities of Micro...
Announcing Private Preview: VS Code Extension of vCore-based Azure Cosmos DB for MongoDB
Overview We’re excited to introduce a new VS Code extension for vCore-based Azure Cosmos DB for MongoDB ! This tool allows users to conn...
Azure Communication Services September 2024 Feature Updates
The Azure Communication Services team is excited to share several new product and feature updates released in August 2024. (You can view previ...