Deployment
What it takes to install it, what has to be in place first, and where the setup gets awkward.
AnyStack Lab
I use the lab to test hardware and software before I write about it. I care about setup, day two operation, failure behavior, and recovery. If a test doesn't help answer one of those questions, I usually don't run it.
Most tests start with a question I ran into while working on infrastructure. The gear doesn't need to be expensive or enterprise scale. The test needs to tell me something useful about design, operations, or recovery.
What it takes to install it, what has to be in place first, and where the setup gets awkward.
Monitoring, maintenance, upgrades, automation, and whatever still needs an owner after the install is done.
What happens when a dependency disappears, a service stops, a node is lost, or the normal path is gone.
Can I restore the data, configuration, and service state? What has to exist before that restore actually works?
The bench
I don't have a warehouse full of vendor racks. I use local hardware, nested virtualization, test environments built for a specific question, community tools, and vendor loaners when I need hardware I do not own.
I'll run benchmarks when they answer a design question. Otherwise I care more about behavior, limits, failure modes, and recovery than chasing a score.
Posts tagged Lab show up here automatically. When a test produces useful scripts, configs, or tools, I'll publish those on GitHub too.
Vendor loaners and review access
Vendors and community projects can loan hardware, provide review units, evaluation licenses, or temporary access. I'll say what was provided and what I actually tested.
A loan doesn't include editorial approval, a positive review, or control over the result. If it works, I'll say so. If it fails, I'll show that too.