https://backend-engineering-strategy-tools.github.io/site/tags/cluster/Recent content in Cluster on Backend Engineering Strategy ToolsHugo -- gohugo.ioen-usThu, 14 May 2026 00:00:00 +0000https://backend-engineering-strategy-tools.github.io/site/homelab/proxmox-cluster/Thu, 14 May 2026 00:00:00 +0000https://backend-engineering-strategy-tools.github.io/site/homelab/proxmox-cluster/<p>Getting a three-node <a class="link" href="https://backend-engineering-strategy-tools.github.io/site/public-notes/cloud-infrastructure/proxmox/" >Proxmox VE</a> cluster running in the homelab.</p> <p>The goal is a shared virtualization platform for running VMs and LXC containers across the rack. Also, a good excuse to kick the tires on Proxmox itself so, naturally, let&rsquo;s needlessly complicate things with some self-imposed constraints:</p> <ol> <li>run it clustered</li> <li>don&rsquo;t use any hardware already earmarked for other projects</li> </ol> <hr> <h2 id="hardware">Hardware </h2><p>I am going try and use three IBM rack servers from the <a class="link" href="https://backend-engineering-strategy-tools.github.io/site/homelab/inventory/systems/" >inventory</a>.</p> <table> <thead> <tr> <th>Asset ID</th> <th>Hostname</th> <th>Model</th> <th>Form Factor</th> <th>RAM</th> <th>CPU</th> </tr> </thead> <tbody> <tr> <td>SYS-001</td> <td>FREJA</td> <td>IBM System x3550 M1 (7978)</td> <td>1U</td> <td>24GB</td> <td>single</td> </tr> <tr> <td>SYS-002</td> <td>TYR</td> <td>IBM System x3650 M1 (7979)</td> <td>2U</td> <td>64GB</td> <td>dual</td> </tr> <tr> <td>SYS-003</td> <td>TOR</td> <td>IBM System x3650 M1 (7979)</td> <td>2U</td> <td>64GB</td> <td>dual</td> </tr> </tbody> </table> <p>Three nodes satisfies Corosync quorum without needing a <code>qdevice</code> — losing one node still leaves a majority.</p> <hr> <h2 id="installation">Installation </h2><p><em>In progress.</em></p> <hr> <h2 id="cluster-formation">Cluster formation </h2><p><em>In progress.</em></p>