Skip to content

README.md

Latest commit

 

History

History
68 lines (48 loc) · 2.72 KB

README.md

File metadata and controls

68 lines (48 loc) · 2.72 KB
Raw

GKE H4D Blueprint

This blueprint uses GKE to provision a Kubernetes cluster and a H4D node pool, along with networks and service accounts. Information about H4D machines can be found here.

NOTE: The required GKE version for H4D support is >= 1.32.3-gke.1170000.

Steps to deploy the H4D blueprint

  1. Install Cluster Toolkit

    1. Install dependencies.
    2. Set up Cluster Toolkit.

  2. Switch to the Cluster Toolkit directory

    cd cluster-toolkit

  3. Get the IP address for your host machine

    curl ifconfig.me

  4. Update the vars block of the gke-h4d-deployment.yaml file.

    1. project_id: ID of the project where you are deploying the cluster.
    2. deployment_name: Name of the deployment.
    3. region: Compute region used for the deployment.
    4. zone: Compute zone used for the deployment.
    5. static_node_count: Number of nodes to create.
    6. authorized_cidr: update the IP address in <your-ip-address>/32.
    7. reservation: The name of the compute engine reservation in the form of . To target a BLOCK_NAME, the name of the extended reservation can be inputted as /reservationBlocks/.

  5. Build the Cluster Toolkit binary

    make

  6. Provision the GKE cluster

    ./gcluster deploy -d examples/gke-h4d/gke-h4d-deployment.yaml examples/gke-h4d/gke-h4d.yaml

    These four options are displayed:

    (D)isplay full proposed changes,
(A)pply proposed changes,
(S)top and exit,
(C)ontinue without applying

    Type a and hit enter to create the cluster.

  7. Additionally, this example blueprint provisions a filestore and connects it to the GKE Cluster via Persistent Volume (PV). An example job template is included in the blueprint which runs a parallel job that reads and writes data to this shared storage. A command similar to kubectl create -f <file-path> is displayed in the deployment outputs which can be used to trigger the sample job.

Run a test using the MPI Operator

The MPI Operator is installed on the cluster during the deployment. To run a test using the MPI Operator on the GKE H4D cluster, refer to https://github.com/GoogleCloudPlatform/kubernetes-engine-samples/tree/main/hpc/mpi.

Clean Up

To destroy all resources associated with creating the GKE cluster, run the following command:

./gcluster destroy CLUSTER-NAME

Replace CLUSTER-NAME with the deployment_name used in the blueprint vars block.