Skip to content

Latest commit

 

History

History
40 lines (35 loc) · 1.61 KB

README.md

File metadata and controls

40 lines (35 loc) · 1.61 KB

SageMaker HyperPod with WEKA

The SageMaker HyperPod files here are copied from AWS SageMaker HyperPod samples
The unique files are:

  • set_weka.sh: will set weka on the SageMaker HyperPod cluster nodes setup
  • set_env_vars.sh: will set the required env vars for examples.sh
  • deploy.sh: will create the SageMaker HyperPod cluster with weka installed

The idea here is to have a simple example to create a SageMaker HyperPod cluster with WEKA installed, while our expectation is, that WEKA customers will integrate set_weka.sh into their own SageMaker HyperPod cluster setup.

Pre-requisites

  • Weka cluster is up and running

The following AWS resources (can use AWS official CF):

  • Fsx
  • VPC
  • Subnet
  • SG
  • IAM ROLE
  • S3 Bucket

SageMaker HyperPod Cluster with WEKA

  • set the required aws profile
  • update the parameters in the examples.sh
  • run cd aws/sagemaker-hyperpod
  • run ./set_env_vars.sh <stack_name> && source env_vars if the pre-requisites are created using the CF above
  • For a new cluster
    • run ./deploy.sh <weka backend ip> <FS name>
  • For an existing cluster
    • run ./deploy_weka_into_existing_cluster.sh <weka_backend_ip> <FS name>

Access the nodes

./easy-ssh.sh <cluster_name>
sudo su -l ubuntu
ssh-keygen -t rsa -q -f "$HOME/.ssh/id_rsa" -N ""
cat .ssh/id_rsa.pub >> .ssh/authorized_keys

now you can run sinfo and ssh to one of the worker nodes ssh -i ~/.ssh/id_rsa ubuntu@<worker_ip>