WEKA installation on GCP
This section aims at a system engineer who is familiar with the GCP concepts and experienced with using Terraform to deploy a system on GCP.
Last updated
This section aims at a system engineer who is familiar with the GCP concepts and experienced with using Terraform to deploy a system on GCP.
Last updated
Leveraging the GCP advantages, WEKA provides a ready-to-deploy GCP-Terraform package that you can customize for installing the WEKA cluster on GCP.
Within GCP, WEKA runs on instances. Each instance can use up to eight partitions of drives on the connected physical server (WEKA does not use the drives directly). The drives can be shared with other clients' partitions in the same physical server.
WEKA requires a minimum of four VPC networks, and each is associated with each of the instances. The reason for using four VPC networks is that a basic WEKA configuration consists of four processes: Compute, Drive, Frontend, and Management. Each of these processes requires a dedicated network interface as follows:
eth0: Management VPC
eth1: Compute VPC
eth2: Frontend VPC
eth3: Drive VPC
VPC peering is used for communication between the WEKA processes. A project in GCP is limited to a maximum of 32 VPC peers.