Compute Canada provides HPC infrastructure and support to every academic research institution in Canada. Compute Canada uses CVMFS, a software distribution system developed at CERN, to make the Compute Canada research software stack available on its HPC clusters, and anywhere else with internet access. This enables replication of the Compute Canada experience outside of its physical infrastructure.
From these new possibilities emerged an open-source software project named Magic Castle, which aims to recreate the Compute Canada user experience in public clouds. Magic Castle uses the open-source software Terraform and HashiCorp Language (HCL) to define the virtual machines, volumes, and networks that are required to replicate a virtual HPC infrastructure. The infrastructure definition is packaged as a Terraform module that users can customize as they require. After deployment, the user is provided with a complete HPC cluster software environment including a Slurm scheduler, a Globus Endpoint, JupyterHub, LDAP, DNS, and over 3000 research software applications compiled by experts with EasyBuild. Magic Castle is compatible with AWS, Microsoft Azure, Google Cloud, OpenStack, and OVH.
- Install Terraform (>= 0.14.2)
- Download the latest release of Magic Castle for the cloud provider you wish to use.
- Uncompress the release
- Follow the instructions
- For more details, refer to Magic Castle Documentation
This software project integrates multiple parts that come into play at different steps of spawning the cluster. The following list enumerates the steps involved in order for users to better grasp what is happening when they create clusters.
We will refer to the user of Magic Castle as the operator.
- After downloading the latest release of the cloud provider of choice and adapting the main configuration file, the operator launches Terraform and accepts the proposed plan.
- Terraform communicates with the cloud provider REST API and requests the creation of the virtual machines.
- For each virtual machine creation request, Magic Castle
provides a cloud-init file. This
file is used to initialize the virtual machine base configuration and installs
puppet agent. The cloud-init file of the
puppettagged virtual machine installs and configures a Puppet primary server. - Terraform uploads on the Puppet primary server instance a YAML file containing information about the roles of each instances specified as tags.
- The Puppet agents communicate with the Puppet primary server to retrieve and apply their configuration based on the tags defined in the preceding YAML file.
- FOSDEM 2020 - Magic Castle: Terraforming the Cloud for HPC (2020-02-02)
- Campus Research Computing Consortium - Clusters in the Sky: How Canada is Building Beyond Iaas Cloud with Magic Castle (2021-05-20)
- AWS ParallelCluster [AWS]
- Cluster in the cloud [AWS, GCP, Oracle]
- Elasticluster [AWS, GCP, OpenStack]
- Slurm on Google Platform [GCP]
- illume-v2 [OpenStack]
- NVIDIA DeepOps [Ansible playbooks only]
- StackHPC Ansible Role OpenHPC [Ansible Role for OpenStack]
When I think about the DevOps landscape, we have so many people just like chefs in a restaurant that are experimenting with different ways of doing things. Once they get it, then they create those recipes. Those recipes in our world is source code. [...] That's why we will always have duplicates and similar projects, because there's going to be one ingredient that's going to be slightly different to make you preferred over something else
Kelsey Hightower, Sourcegraph Podcast, Episode 16, 2020
Refer to the reference design and the developer documentation.