Add clients to a WEKA cluster on GCP

WEKA supports client instances with at least two NICs, one for management and one for the frontend data. It is possible to add more NICs for redundancy and higher performance.

A client with the same VPC networks and subnets as the cluster can connect without additional configuration. If a client is on another VPC network, peering is required between the VPC networks.

The client instance must be in the same region as the WEKA cluster on GCP.

Mount the filesystem

1. Create a mount point (only once):

mkdir /mnt/weka

1. Install the WEKA agent (only once):

curl <backend server http address>:14000/dist/v1/install | sh

Example:

curl http://10.20.0.2:14000/dist/v1/install | sh

1. Mount a stateless client on the filesystem. In the mount command, specify all the NICs of the client.

The mgmt_ip option identifies management processes on the data plane network. It does not identify external management interfaces such as the CLI or REST API.

• DPDK mount with four NICs:

mount -t wekafs -o net=eth1/IP/NETMASK/GATEWAY -o net=eth2/IP/NETMASK/GATEWAY -o net=eth3/IP/NETMASK/GATEWAY -o mgmt_ip=<management IP (eth0)> -o num_cores=4 -o dpdk_base_memory_mb=32 <backend server IP address>/<filesystem name> /mnt/weka

Example:

mount -t wekafs -o net=eth1/10.20.30.101/24/10.20.30.1 -o net=eth2/10.20.31.102/24/10.20.31.1 -o net=eth3/10.20.32.103/24/10.20.32.1 -o mgmt_ip=10.20.33.100 -o num_cores=4 -o dpdk_base_memory_mb=32 10.20.30.40/fs1 /mnt/weka

• UDP mount:

mount -t wekafs -o net=udp -o num_cores=0 -o mgmt_ip=<management IP (eth0)> <backend server IP address>/<filesystem name> /mnt/weka

Example:

mount -t wekafs -o net=udp -o num_cores=2 -o mgmt_ip=10.20.30.100 10.20.30.40/fs1 /mnt/weka

Related topics

Mount filesystems