Blog

The solar-powered lab that simulates a data center

People ask why I keep a full server rack at home when I've spent my career working on enterprise systems for a living. The honest answer: a home lab is the only place you get to break things on purpose. Production is where you learn to be careful. The lab is where you learn what happens when careful isn't enough, and it costs you a Saturday instead of a customer.

What's in it

  • A full-size rack with a 40GbE fibre backbone bridged to 10GbE copper, so the network itself is a real networking problem, not a toy one.
  • Dell PowerEdge servers on VMware ESXi, running the workloads: VMs, containers, and a Kubernetes cluster.
  • Network-attached storage for the data layer, with the backup and restore discipline that production deserves (restore-drill exists because of this).
  • A Cisco rack for the switching and routing fundamentals.
  • Tailscale mesh with a VPS interlink, so I can reach the lab from anywhere on the planet, the same way distributed teams reach their infrastructure.

It's not just a basement rack

The lab is solar-supported, and it extends into every room of the house. Whole-home automation handles lighting, climate, security, and media through Home Assistant with Z-Wave and Zigbee devices on a mesh Wi-Fi network. That part matters more than it sounds: running a facility, any facility, means managing power, environmental conditions, and a fleet of devices that weren't designed to talk to each other. It's the same muscle as managing a server room, just with better coffee nearby.

What it's for

  • Skills that stay sharp. ESXi, Docker, Kubernetes, VLANs, VPNs, storage, monitoring. Every one of these is a line on my resume because I run them at home, not because I read about them.
  • Breaking things safely. The monitoring tools I open-source (rackpulse, pinggrid, endpointwatch) were built to solve problems this lab actually had.
  • Interview prep. When a hiring manager asks how I'd handle a failing host, a noisy network, or an alert that won't stop, I don't answer from theory. I answer from the last time it happened to me at 11pm on a Tuesday.

The lessons

  • Simulate the hard parts. A lab that only does the easy things teaches you nothing. Put real switching, real storage, and real failure modes in it.
  • Power is infrastructure. Solar support isn't a gimmick, it's an availability story. Same lesson as a UPS in a server room: the grid is a dependency, not a guarantee.
  • Automation compounds. The whole-home layer runs the same pattern as my ops stack: collect, decide, act. The house is just another environment to operate.
  • Run what you claim. Everything on my resume that can run at home, runs at home. It keeps claims honest, which is the whole point.