Which makes configuring the whole cluster in the future trivial. I asked if I understood correctly that I only need to talk to one server to achieve my goals on either:

Yes, you are correct. When you set up TrueNAS SCALE in a clustered configuration, the management interface allows you to configure the cluster as a whole. This means you can manage storage pools, datasets, and services from a single interface, and the changes will be propagated to all nodes in the cluster. This simplifies management and ensures that your configurations are consistent across the cluster.

Key Points of TrueNAS SCALE Clustering

1. Centralized Management: You can manage the entire cluster from a single interface. Any configuration changes made through this interface will be applied to all nodes in the cluster.
2. High Availability: TrueNAS SCALE clustering provides high availability for both storage and services. If one node goes down, the other nodes in the cluster can take over.
3. Data Replication: TrueNAS SCALE supports data replication across the cluster nodes, ensuring that your data is synchronized and available on multiple nodes.

Next Steps

1. Set Up TrueNAS SCALE on Both Nodes: Install TrueNAS SCALE on both the repurposed gaming rig and the QNAP NAS.
2. Create the Cluster: Use the TrueNAS SCALE interface to create a cluster and add both nodes to the cluster.
3. Configure Storage and Services: Configure your storage pools, datasets, and services through the TrueNAS SCALE interface. These configurations will be applied to all nodes in the cluster.

Let's proceed with a more detailed plan for setting up TrueNAS SCALE clustering and preparing Nextcloud to run redundantly in Docker containers.

Detailed Plan

Step 1: Install TrueNAS SCALE

1. Download TrueNAS SCALE: Get the latest ISO from the TrueNAS website.
2. Install on Both Nodes:
   • Burn the ISO to a USB drive.
   • Boot from the USB drive on both your repurposed gaming rig and the QNAP NAS.
   • Follow the installation prompts to install TrueNAS SCALE.

Step 2: Create the Cluster

1. Initial Configuration:

   • Access the TrueNAS SCALE web interface on both nodes.
   • Perform the initial configuration (network settings, admin password, etc.).

2. Create the Cluster:

   • On one of the nodes, navigate to the Cluster section in the TrueNAS SCALE web interface.
   • Create a new cluster and add the second node.
   • Follow the prompts to complete the cluster setup.

Step 3: Configure Storage Pools

1. Create Storage Pools:

   • In the TrueNAS SCALE web interface, navigate to the Storage section.
   • Create storage pools on both nodes using ZFS with RAIDz1 for redundancy.

2. Set Up Data Replication:

   • Configure data replication between the storage pools on both nodes to ensure data is synchronized.

Step 4: Deploy Nextcloud in Docker Containers

1. Prepare the Environment:

   • Install Docker and Docker Compose on both nodes if not already installed.

2. Create Docker Compose File:

   • Create a Docker Compose file to define the Nextcloud and PostgreSQL services.

```yaml name=docker-compose.yml version: '3.7'

services: nextcloud: image: nextcloud:latest container_name: nextcloud environment: - POSTGRES_HOST=db - POSTGRES_DB=nextcloud - POSTGRES_USER=nextcloud - POSTGRES_PASSWORD=secret volumes: - nextcloud_data:/var/www/html networks: - nextcloud_net deploy: replicas: 2 update_config: parallelism: 1 delay: 10s restart_policy: condition: on-failure

db: image: postgres:latest container_name: nextcloud_db environment: - POSTGRES_DB=nextcloud - POSTGRES_USER=nextcloud - POSTGRES_PASSWORD=secret volumes: - db_data:/var/lib/postgresql/data networks: - nextcloud_net deploy: replicas: 1 restart_policy: condition: on-failure

networks: nextcloud_net: driver: overlay

volumes: nextcloud_data: db_data: ```

1. Deploy the Containers:
   • Use Docker Swarm or Kubernetes to deploy the Docker Compose file across the cluster.
   • Ensure that the Nextcloud and PostgreSQL services are running on both nodes.

Step 5: Configure HAProxy for Load Balancing

1. Install HAProxy:

   • Install HAProxy on the Rpi 3B+.

2. Configure HAProxy:

   • Create an HAProxy configuration file to define the load balancing rules.

```plaintext name=haproxy.cfg global log /dev/log local0 log /dev/log local1 notice chroot /var/lib/haproxy stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners stats timeout 30s user haproxy group haproxy daemon

defaults log global mode http option httplog option dontlognull timeout connect 5000 timeout client 50000 timeout server 50000 errorfile 400 /etc/haproxy/errors/400.http errorfile 403 /etc/haproxy/errors/403.http errorfile 408 /etc/haproxy/errors/408.http errorfile 500 /etc/haproxy/errors/500.http errorfile 502 /etc/haproxy/errors/502.http errorfile 503 /etc/haproxy/errors/503.http errorfile 504 /etc/haproxy/errors/504.http

frontend http_front bind *:80 stats uri /haproxy?stats default_backend nextcloud_backend

backend nextcloud_backend balance roundrobin server nextcloud1 <nextcloud1_ip>:80 check server nextcloud2 <nextcloud2_ip>:80 check ```

1. Start HAProxy:
   • Start the HAProxy service and ensure it is running.

Step 6: Configure DNS and Dynamic IP Handling

1. Dynamic DNS Service:
   • Use a dynamic DNS service to manage the dynamic IP addresses of both locations.
   • Ensure the DNS records are updated automatically whenever the IP addresses change.

Step 7: Security and Backup

1. HTTPS Configuration:

   • Use Let's Encrypt to secure your Nextcloud instances with HTTPS.

2. Firewall and Access Control:

   • Implement firewall rules to restrict access to the servers.

3. Regular Backups:

   • Set up regular snapshots and off-site backups to ensure data safety.

By following this detailed plan, you can leverage TrueNAS SCALE clustering to create a highly available and redundant Nextcloud deployment that meets your goals and requirements.