OpenStack Private Cloud
A private cloud built with MicroStack on Ubuntu: virtual networks, a cloud router, compute instances, storage volumes, and remote SSH access.
Infrastructure & CloudContext
Public cloud hides the machinery. To understand what AWS actually does, I built the machinery myself — an OpenStack cloud on my own hardware.
The problem
Cloud skills learned through a console teach you buttons, not systems. The goal was to stand up the entire IaaS layer — the part AWS never shows you — and operate it: networks, routing, images, instances, volumes, and access.
Decisions
MicroStack for a full stack on one host
MicroStack packages OpenStack's core services to run on a single Ubuntu machine — the complete architecture (Neutron networking, Nova compute, Cinder storage) without a datacenter's hardware bill.
Virtual topology before instances
Networks, subnets, and the cloud router were designed first, so every instance launched into a deliberate topology instead of a default flat network — the same discipline as physical network design.
Remote access as the acceptance test
The deployment only counted as done when an instance was reachable over SSH from outside the cloud — floating IP, security rules, and routing all proven in one connection.
Challenges
Resource pressure and opacity: OpenStack's services are heavy for one host, and when instance networking fails, the fault can sit in any of four layers. Debugging meant reading each service's view of the world until they agreed.
Result
A self-hosted private cloud with virtual networks, a router, compute instances, and attached storage volumes — administered remotely over SSH, from bare Ubuntu to running workloads.
Lesson
Cloud is not magic; it is networking, storage, and compute with good APIs. Owning the whole stack once makes every managed service legible forever.
Next case
01Terra Talent Hub