Setting up a custom Amazon ParallelCluster node package - Amazon ParallelCluster
Steps
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Setting up a custom Amazon ParallelCluster node package

Warning

The following are instructions for using a custom version of the Amazon ParallelCluster node package. This is an advanced method of customizing Amazon ParallelCluster, with potential issues that can be hard to debug. The Amazon ParallelCluster team highly recommends using the scripts in Custom Bootstrap Actions for customization, because post-install hooks are generally easier to debug and more portable across releases of Amazon ParallelCluster.

Steps

  1. Identify the Amazon ParallelCluster node working directory where you have cloned the Amazon ParallelCluster node code.

    _nodeDir=<path to node package>

  2. Detect the current version of the Amazon ParallelCluster node.

    _version=$(grep "version = \"" ${_nodeDir}/setup.py |awk '{print $3}' | tr -d \")

  3. Create an archive of the Amazon ParallelCluster Node.

    cd "${_nodeDir}"
_stashName=$(git stash create)
git archive --format tar --prefix="aws-parallelcluster-node-${_version}/" "${_stashName:-HEAD}" | gzip > "aws-parallelcluster-node-${_version}.tgz"

  4. Create an Amazon S3 bucket and upload the archive into the bucket. Give public readable permission through a public-read ACL.

    _bucket=<the bucket name>
aws s3 cp --acl public-read aws-parallelcluster-node-${_version}.tgz s3://${_bucket}/node/aws-parallelcluster-node-${_version}.tgz

  5. Add the following variable to the Amazon ParallelCluster configuration file, under the [cluster] section.

    extra_json = { "cluster" : { "custom_node_package" : "https://${_bucket}.s3.<the bucket region>.amazonaws.com/node/aws-parallelcluster-node-${_version}.tgz", "skip_install_recipes" : "no" } }
    Note

    Starting with Amazon ParallelCluster version 2.6.1, most of the install recipes are skipped by default when launching nodes to improve startup times. To skip most of the install recipes for better startup times at the expense of backwards compatibility, remove "skip_install_recipes" : "no" from the cluster key in the extra_json setting.