WEKA installation on GCP
This section aims at a system engineer familiar with the GCP concepts and experienced in using Terraform to deploy a system on GCP.
Last updated
This section aims at a system engineer familiar with the GCP concepts and experienced in using Terraform to deploy a system on GCP.
Last updated
Leveraging GCP's advantages, WEKA offers a customizable terraform-gcp-weka module for deploying the WEKA cluster on GCP. In GCP, WEKA operates on instances, each capable of using up to eight partitions of drives on the connected physical server (without direct drive usage). These drives can be shared among partitions for other clients on the same server.
WEKA requires a minimum of four VPC networks, each associated with one of the instances. This configuration aligns with the four key WEKA processes: Compute, Drive, Frontend, and Management, with each process requiring a dedicated network interface as follows:
eth0: Management VPC
eth1: Compute VPC
eth2: Frontend VPC
eth3: Drive VPC
VPC peering facilitates communication between the WEKA processes, each using its NIC. The maximum allowable number of peers within a VPC is limited to 25 by GCP (you can try to increase the quota, but it depends on the GCP resources availability).