Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

To ensure optimal setup of Infrastructure Optimizer, please make a note of the following information that will be used during installation and integration:

Slurm Installation

  • SLURM_CONF_DIR : directory where slurm.conf is located

  • SLURM_BIN_DIR : directory where slurm’s binaries are located, usually on users' PATH

Exostellar Management Server Information

  • MGMT_SERVER_IP : The internal or private IP Address can be found in the CloudFormation Outputs tab.

Facilitating Commands

Variables can be export’d to facilitate copy/paste commands in the next sections of this guide, or source an arbitrary file, for example : . /root/facilitate or source /root/facilitate.

  • export MGMT_SERVER_IP=173.31.23.23
export SLURM_CONF_DIR=/opt/slurm/etc

Compute Environment

An AMI will be needed. The steps below give an example of how an AMI could be created in the AWS Console leveraging the existing slurm cluster and its resources and configuration. Or if the compute resources in the slurm cluster are based on an existing AMI, that can be used as well.

The key concepts to keep in mind about getting a good AMI is that it should boot fast and do little to no work, for example in bootstrapping or user_data. Also, it should have everything required to run the workflows and authenticate users.

To create an AMI from a slurm compute node:

  • Allocate a compute node: 

    • salloc -N 1 -J ami-creation --no-shell --exclusive --nodelist=<NodeNanme>

  • When the job is allocated, gather some information on the node running the job:

    • The salloc command above should have output a JOB_ID.

    • The squeue command should show the JOB_ID running on particular node.

    • Issue the following command to capture information about that node:

      • scontrol show node <NODENAME>

      • Look for the NodeAddr= field in the output to find the Private IPv4 Address of the node running the ami-creation job.

    • Navigate to AWS console EC2 Instances page and search for the Private IPv4 Address.

    • Select that instance and click “Create an image” from the Actions button in the upper right corner.

    • AMI Creation requires a variable amount of time to complete: it may take 15 minutes or longer in some regions at certain times of day. Information requested from the AWS Console to fulfill this request is fairly intuitive: Name the AMI in a memorable way and generally accept the default values provided by the prompts.

    • NOTE : this action will reboot the node and kill our job, which is expected.

  • No labels