A confession first: I never ran [OpenStack](https://www.openstack.org). Not once. Not at work, not at home, not in a lab, not out of curiosity. I refused it - fiercely, the way some people refuse a religion - and I want to explain why, because the reason turns out to be the same reason I was late to [Kubernetes](https://kubernetes.io), years later, and that's when the name of this blog stops being a joke. By the time I finished my masters, the private-cloud wars were in full swing, and they were fought the way wars of that era were fought: every vendor had a distribution, every distribution was the only supported way, and every slide deck promised you a private Amazon. But the war I was actually watching had a specific shape, and it was two projects going at each other, and I had already picked a side. The side I picked was called [Eucalyptus](https://github.com/eucalyptus/eucalyptus). AWS-compatible. Open source. The pitch was simple and, to my mind, correct: if you're going to run your own cloud, it should speak the same API as the real cloud, so you're never locked in and never locked out - the same skills, the same tools, the same muscle memory, on hardware you own. OpenStack was the other camp. The story everyone told at the time - and I can't verify it, but everyone told it - was that OpenStack began as a Python fork of Eucalyptus, started by people who simply didn't want to use Java. Whether or not that's the full history, it tells you everything about the era: a big chunk of the "next generation of cloud" was born as a language preference with a marketing budget. I picked Eucalyptus for the philosophy. What I didn't know was that it would pick me back. They hired me as support before I'd finished my masters. I want you to sit with that for a second, because I certainly didn't: I was still a student, and a company whose product I ran in my own studio rack looked at my, let's say, *enthusiastic* forum presence and my weird little homelab and decided I was employable. Then they moved me to the UK. And then - within the first few weeks - they made me TAM for Nokia. Their biggest customer. By a landslide. My onboarding period could be measured in weeks; the customer I was made responsible for was larger than some of the vendors we competed against. I don't recommend this to anyone, and I'd do it again tomorrow. There is no better way to learn a product than to have it be the beating heart of a contract worth more than your future salary, and to be the person whose phone rings when its heart skips. Nokia meant Finland, and I'll put it on the record: the warmest, most competent people I've ever had the luck to work with. I landed there knowing nobody, and I was adopted within the hour - the welcome never once wore off across the whole engagement. And underneath the hospitality sits a level of competence that raised my own game: they knew their estate down to the last VLAN, they'd read everything before the call started, and their questions were sharper than half the war rooms I've sat in since. One thing that struck people at the time - and this comes up again and again in my career, so let me get it on the record now - was my age. Everyone put me in my mid-30s. Not only because I looked older, though I did. Because I *kept up*. I could hold my end of a network conversation, a systems conversation, an architecture conversation, with seniors who had been in the trenches for fifteen years longer than I had, and I could hold it without flinching, because I'd already hit every one of their war stories in miniature, at home, alone, at 1am, in a studio where a rack lived where the wardrobe should have been. The homelab wasn't a hobby. It was a compressed apprenticeship. It just took a while for the industry to price it correctly. And those were the vendor wars from the inside, for the record: I wasn't in the crowd watching distributions fight. I was in the arena. I knew exactly which competitor features were real and which were roadmap. I knew how the same slide deck was rewritten for three different audiences. None of it made me cynical, exactly. But it did teach me to read vendor announcements the way you read weather reports: with an umbrella in the bag regardless. Then HP bought us, and the shape of the war changed. I want to be precise about why, because it was one of the strangest strategic moves I've ever been adjacent to. HP had enterprise customers. Those customers wanted to go to AWS. HP's problem was obvious: if the customers left, HP lost them. So the play was to keep them on-prem by *giving them AWS* - the same APIs, the same features, the same tooling - via Eucalyptus, so that moving to the real cloud later would be a migration, not a conversion. We weren't the product; we were the bridge. Bare metal couldn't do elastic, and Eucalyptus could, and suddenly the little AWS-compatible cloud nobody had heard of was a retention strategy for one of the biggest hardware companies on earth. Which meant that while every cloud conference was a contest of investment announcements - who's pouring how many millions into OpenStack this year, as if dollars were a benchmark - we were the very little guys. We had no armada of integrators. We had no roadshow budget. Our name recognition was a rounding error, and I won't pretend it wasn't the single biggest wall we faced: half the objections we hit weren't about the product at all, they were about the logo on the slide. But here's the part I've carried with me ever since. Wherever we could get through the front door - wherever we actually got a technical evaluation instead of a procurement-level dismissal - we won. Not sometimes. Consistently. Because the moment an engineer put both clouds side by side and tested what mattered - the API compatibility, the actual behavior, the operational reality - the marketing evaporated and we were still standing. Every single one of those wins was earned against the grain of a market that had already decided, before the first test, that the little Java project with the tree name couldn't possibly beat the one everyone was investing in. It taught me a lesson I've relearned in every fight since: name recognition decides who gets *evaluated*. It almost never decides who gets *kept*. So why does this end with a refusal of OpenStack rather than a grudging adoption? Because everything I'd lived through - the all-inclusive socket, the gutted rig, the Nokia TAM phone, and now the little cloud that won every fair fight and still lost every budget - pointed at one belief I couldn't shake: the private cloud as a product category was a machine for organizations, not for people. And Eucalyptus was the last private cloud I believed in, because it was the only one that admitted what it actually was: an API boundary, not a lifestyle. You can guess what happened to it. You can also guess what the industry did instead. And you can probably guess what I said, for years, when people told me Kubernetes was the obvious next step - the exact same thing I'd said about OpenStack.