Elastic Slurm Cluster in a Jetstream image


This repo contains scripts and ansible playbooks for creating a virtual cluster in an Openstack environment, specifically aimed at the ACCESS Jetstream2 resource.

The basic structure is to have a single instance act as headnode, with compute nodes managed by SLURM via the openstack API. The current version builds a basic image with all the necessary configuration to act as compute nodes to the main headnode instance. When jobs are submitted, SLURM will trigger instance creation based on this image. The SchedMD documentation on Power Management and Elastic Computing are useful reading.


To build your own Virtual cluster, starting on your localhost:

  1. If you don't already have an openrc file, see the Jetstream Wiki.

  2. Clone the Virtual Cluster repository.

  3. Copy the openrc for the allocation in which you'd like to create a virtual cluster to this repo. A file called clouds.yaml with the following format (replace values in all caps with actual values, similar to your openrc file) will be automatically created during the installation process, based on your openrc.sh.

   auth_url: SAME-AS-OPENRC
   project_name: SAME-AS-OPENRC
   password: SAME-AS-OPENRC
  user_domain_name: SAME-AS-OPENRC
  project_domain_name: SAME-AS-OPENRC
  identity_api_version: 3
  1. If you'd like to modify your cluster, now is a good time! This local copy of the repo will be re-created on the headnode, but if you're going to use this to create multiple different VCs, it may be preferable to make the following modifications in separate files.
  2. The number of nodes can be set in the slurm.conf file, by editing the NodeName and PartitionName line.
  3. If you'd like to change the default node size, the node_size=line in slurm_resume.sh must be changed.
  4. If you'd like to enable any specific software, you should edit compute_build_base_img.yml. The task named "install basic packages" can be easily extended to install anything available from a yum repository. If you need to add a repo, you can copy the task titled "Add OpenHPC 1.3.? Repo". For more detailed configuration, it may be easiest to build your software in /export on the headnode, and only install the necessary libraries via the compute_build_base_img (or ensure that they're available in the shared filesystem).
  5. For other modifications, feel free to get in touch!

  6. Run create_headnode.sh - it will require an ssh key to exist in ${HOME}/.ssh/id_rsa.pub. This will be the key used for your jetstream instance! If you prefer to use a different key, be sure to edit this script accordingly. The expected argument is only the headnode name, and will create an 'm1.small' instance for you.

./create_headnode.sh <headnode-name>

Watch for the ip address of your new instance at the end of the script! If you miss it, openstack server list will display your new headnode. 1. The create_headnode script has copied everything in this directory to your headnode. You should now be able to ssh in as the centos user, with your default ssh key: ```ssh centos@

  1. Now, in the copied directory, on the headnode, run the install.sh script with sudo: sudo ./install.sh. This script handles all the steps necessary to install slurm, with elastic nodes set. It will also build a customized image for your compute nodes, with the compute_build_base_img.yml playbook.

Useage note: Slurm will run the suspend/resume scripts in response to scontrol update nodename=compute-[0-1] state=power_down or scontrol update nodename=compute-[0-1] state=power_up

If compute instances get stuck in a bad state, it's often helpful to cycle through the following: scontrol update nodename=compute-[?] state=down reason=resetting scontrol update nodename=compute-[?] state=idle or to re-run the suspend/resume scripts as above (if the instance power state doesn't match the current state as seen by slurm). Instances in a failed state within Openstack may simply be deleted, as they will be built anew by slurm the next time they are needed.