MayaNAS on GCP Marketplace

Deploy a MayaNAS HA NAS cluster directly from the GCP Marketplace using Google Cloud’s Infrastructure Manager (Terraform).

Prerequisites

• A GCP project with billing enabled
• Compute Engine API enabled
• Cloud Storage API enabled
• IAM permissions: Compute Admin, Storage Admin, Network Admin, Service Account User

Step 1: Find MayaNAS in GCP Marketplace

1. Go to GCP Marketplace
2. Search for MayaNAS HA Storage
3. Click Deploy

Step 2: Configure Deployment

The marketplace wizard presents the following sections:

Deployment Configuration

Field	Description	Default
Deployment Name	Unique name for the cluster (used for all resource naming)	—
Deployment Type	Active-Active HA or Active-Passive HA	Active-Active HA

Compute Configuration

Field	Description	Default
Primary Zone	GCE zone for the primary node	—
Machine Type	VM instance type	n2-standard-4

Boot Disk

Field	Description	Default
Boot disk type	Disk type for OS	pd-balanced
Boot disk size	Size in GB	20

Metadata Disk

Field	Description	Default
Metadata disk type	SSD type for metadata caching	pd-ssd
Metadata Disk Size (GB)	Size of each metadata disk (50 GB suits 1-10 TB pools — ZFS metadata is roughly 0.3-0.5% of pool size)	50

Cloud Storage

Field	Description	Default
Cloud Storage Size	Logical storage size (e.g., 1T, 500G, 2T)	1T

Valid range: 100G–999G or 1T–1000T. Charges are based on actual GCS usage.

Networking

Field	Description	Default
Allow Web UI Access (Port 2020)	Opens firewall for Web UI	true
Source IP ranges for Web UI	Restrict access to specific IPs	0.0.0.0/0

Caution

For production deployments, restrict Web UI access to your IP range or disable it and use SSH port forwarding instead:

gcloud compute ssh mayanas@INSTANCE --zone=ZONE -- -L 2020:localhost:2020

Then access http://localhost:2020.

Step 3: Deploy

Click Deploy and wait for Infrastructure Manager to provision all resources. This typically takes 3–5 minutes for VM, disk, and bucket provisioning. After provisioning completes, the cluster auto-configures itself in under 2 minutes — one OpenZFS pool, one ZFS dataset, exported to your VPC subnet. No admin guide required, no manual setup.

Post-Deployment

Retrieve Access Credentials

The Web UI password is auto-generated. Retrieve it from the deployment outputs or from within the instance:

curl -H "Metadata-Flavor: Google" \
  http://metadata.google.internal/computeMetadata/v1/instance/attributes/mayanas-cloud_user_password

Access the Web UI

# Option 1: Direct access (if port 2020 is open)
http://<EXTERNAL_IP>:2020

# Option 2: SSH tunnel (recommended for production)
gcloud compute ssh INSTANCE_NAME --zone=ZONE --project=PROJECT -- -L 2020:localhost:2020
# Then open http://localhost:2020

Login: admin / password from deployment output.

SSH Access

gcloud compute ssh mayanas@INSTANCE_NAME --zone=ZONE --project=PROJECT_ID

Mount NFS Shares

After creating a share in the Web UI:

# Active-Passive (single VIP)
sudo mount -t nfs <VIP_ADDRESS>:/<CLUSTER>-pool/<SHARE_NAME> /mnt/data

# Active-Active (each node has its own VIP)
sudo mount -t nfs <VIP1>:/<CLUSTER>-pool-node1/<SHARE> /mnt/node1
sudo mount -t nfs <VIP2>:/<CLUSTER>-pool-node2/<SHARE> /mnt/node2

VIP Address

The VIP is automatically assigned from the 10.100.x.0/24 range using a deterministic region-based algorithm. The VIP address is shown in the deployment outputs.

What Gets Deployed

• 1–2 Compute Engine instances (depending on deployment type)
• GCS bucket(s) for data storage
• SSD persistent disk(s) for metadata
• Service account with Compute/Storage/Network Admin roles
• Firewall rules (SSH, NFS 2049, optional Web UI 2020)
• VIP alias IP range for HA failover

Troubleshooting

# Check startup logs
tail -f /opt/mayastor/logs/mayanas-terraform-startup.log

# Check service status
systemctl status mayastor

# Check cluster status
mayacli cluster status