-
Notifications
You must be signed in to change notification settings - Fork 4
Setup
This was set up on OpenSuse. It should work on other OS as well.
Link to Peter Gottesman's work. You can use his documentation and the scripts to help through set up as well: https://github.com/open-mpi/aws-pmix-scale-testing
Clone Peter Gottesman's work. The aws-pmix-scale-testing repository from github into an appropriate folder. I will be assuming you clone aws-pmix-scale-testing into your home directory
git clone https://github.com/open-mpi/aws-pmix-scale-testing
Next, you'll need to install CfnCluster and the AWS Command Line Interface. The docs: https://cfncluster.readthedocs.io/en/latest/getting_started.html#configuring-cfncluster https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html
sudo pip install cfncluster //You may have to install pip as well
sudo pip install awscli --upgrade --user
Unsure how I originally handled this. But this is how I'll handle it now.
Head to AWS and under Services find "VPC". Select "Your VPCs" on the left. "Create VPC" and name it what you'd like. For the "IPv4 CIDR block", give it "10.0.0.0/16" and then create it.
Next, on the left side, click "Subnets". Then "Create subnet". Give it a name and in the VPC drop down, select the VPC you just created. Selected the Availability Zone you are in (Or leave No Preference). For "IPv4 CIDR block", put "10.0.0.0/24".
aws configure
This is where you'll need your AWS Access Key ID and Secret Access Key. Here, at the bottom of the page, are some instructions on getting your Security Credentials. You'll download a csv file and you'll be able to take those values and plug them in. Next is Default region name, select the region you are going to use (Google will tell you the different regions). For example, I've been using "uw-west-2" for everything (sometimes "uw-west-2b" depending on the resource). Then select the default for the last option.
cd ~/.aws
ls //In this folder you should see a config and credentials file
Next, you'll need to configure CfnCluster:
cfncluster configure
ctrl + z
ls -l //In the home directory, there should now be a .cfncluster folder
cd .cfncluster
Make sure to talk about changing the path of files in the config file for pre and post install
In S3, in Services, find the S3 console. Once in the console, "Create bucket". Give it a name and make sure it will be in the region the rest of your resources are in. Then click next and accept defaults for everything. Create three buckets. One for builds, logs, and tests.
Next, in the aws-pmix-scale-testing folder, create a new file from buckets.sh.template called buckets.sh, then copy the names of the S3 buckets into the file.
cp buckets.sh.template buckets.sh
vim buckets.sh
after editing, buckets.sh will look something like this:
backend="ompitestsnmc" //Your bucket names will be different as ALL bucket names
builds="ompibuildsnmc" // are unique
logs="ompilogsnmc"
Next, you'll need to simlink buckets.sh into aws-pmix-scale-testing/backend/shared so buckets.sh can be access from the backend/shared folder
ln -s /full/path/to/home/aws-pmix-scale-testing/buckets.sh /full/path/to/home/aws-pmix-scale-testing/backend/shared/buckets.sh
cd backend/shared
ls -Al //Check to make sure there is a correctly setup simlink
This is a similar process to Buckets. Create the database, cp mysqlauth.sh.template to mysqlauth.sh and file in info. Make sure to symlink as well. I didn't do this so I'm not aware of the exact process. Just the general process.
Updated: 6-29-2018