
What Actually Makes Private Cloud Operationally Difficult?
What makes private cloud difficult to operate? Explore Day 2 operations, upgrades, automation, capacity, skills, and managed cloud options.
Read field noteField notes / Latest
Engineering notes from operating open infrastructure: the failures, design decisions, and upstream work that make open infrastructure better.
Browse all field notes
What makes private cloud difficult to operate? Explore Day 2 operations, upgrades, automation, capacity, skills, and managed cloud options.
Read field note
Learn which infrastructure decisions are hardest to undo, from storage and networking to identity, integrations, data location, and APIs.
Read field note
Learn how to safely upgrade production GPU infrastructure across NVIDIA drivers, CUDA, Kubernetes, firmware, containers, and AI workloads.
Read field noteTrends, best practices, and technical deep dives on open source cloud infrastructure.

These releases showcase ongoing efforts to boost performance, reliability, and functionality. With iSCSI LUN enhancements, critical Cert-Manager fixes, and improved networking configurations, users can expect a more seamless and efficient experience. Stay tuned for more updates as capabilities continue to evolve and expand.

Discover the latest Atmosphere updates with releases 2.3.0, 3.4.0, and 3.4.1, featuring enhanced performance, improved control plane resiliency, and advanced monitoring for load balancers.
Learn how Atmosphere flips the traditional cloud stack by running OpenStack inside Kubernetes and provisioning Kubernetes clusters via OpenStack.
This post takes a closer look at the real-world failure points in OpenStack, how to design around them using practical strategies, and how Atmosphere simplifies some of this work.
AI workloads demand scale, speed, and control. See how Atmosphere helps teams ditch vendor lock-in and run GPU-hungry models on their own terms.
OpenStack gets noisy fast. Atmosphere cuts through it with real metrics, real logs, and real alerts, so teams can fix issues before users notice.
Not every workload belongs on Kubernetes. See where VMs still shine, how OpenStack supports both, and why Atmosphere simplifies multi-modal ops.
Cloud sprawl on OpenStack slows teams and inflates costs. From oversized VMs to abandoned volumes, here’s how Atmosphere brings control, cleanup, and cost efficiency back to OpenStack.
Experience enhanced reliability in load balancing — in the latest Atmosphere release Octavia Amphora V2 is now supported and seamlessly integrated by default, resolving long hanging issues with load balancer provisioning interruptions due to service or network failures.
Updating OpenStack can be complex due to its intricate architecture, interdependencies, customisation, data migration challenges, the need for minimal downtime, extensive testing requirements, sometimes outdated documentation, resource demands, the necessity for skilled personnel, and frequent release cycles.