Launching Cluster

Right now we are using a branch of the aws-pmix-scale-testing repo. Check it out here: https://github.com/dylanchristopherson/aws-pmix-scale-testing/tree/jenkins_customization

Now that everything is set up. You should be able to launch Cfncluster using scripts.

./launch.sh {clusterName}  // cluster name is optional. Script will create a name if no name is included 

List all clusters and gives status on the creation, or completion, of cluster

cfncluster list
cfncluster status {clusterName} 

It will take approximately 20 mins to create the cluster, so the status command might not give you the following output immediately. After it is created, the output of status will look something like this:

Output:"MasterPublicIP"="MasterPublicIP"
Output:"MasterPrivateIP"="MasterPrivateIP"
Output:"GangliaPublicURL"="http://54.203.96.159/ganglia/"
Output:"GangliaPrivateURL"="http://10.0.0.19/ganglia/"

Use the connect.sh script in aws-pmix-scale-testing repo to connect to the cfncluster instance.

./connect.sh <path-to-key-pair-file>

Example:

./connect.sh ../MyAWSKeyPair.pem

Your existing clusters will populate and you can choose the one you'd like to connect to.

To connect to the instance manually:

To SSH into the cluster you've just created, you'll need the MasterPublicIP from the cfncluster status command from above. Then:

ssh -i <path-to-key-pair-file> ec2-user@MasterIPAddress

Example:

ssh -i ../MyAWSKeyPair.pem ec2-user@54.213.99.222

After these commands are ran, head onto the AWS EC2 console and check your EC2 instances! You should see a master node and there may be a number of compute nodes as well. Don't see any? In the upper right corner next to the support button, there should be a drop down of regions. Make sure you are in the correct region.

To shutdown the clusters manually, head back onto your terminal:

cfncluster delete {clusterName}

General instructions for launching a cluster https://d1.awsstatic.com/Projects/P4114756/deploy-elastic-hpc-cluster_project.pdf