{"id":9927,"date":"2026-04-01T17:47:41","date_gmt":"2026-04-01T22:47:41","guid":{"rendered":"https:\/\/www.openstack.org\/blog\/?p=9927"},"modified":"2026-04-01T17:47:41","modified_gmt":"2026-04-01T22:47:41","slug":"openstack-gazpacho-built-by-a-global-community-designed-for-real-world-infrastructure","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-gazpacho-built-by-a-global-community-designed-for-real-world-infrastructure\/","title":{"rendered":"OpenStack Gazpacho: Built by a Global Community, Designed for Real-World Infrastructure"},"content":{"rendered":"\n<h1><\/h1>\n\n\n\n<p class=\"lead\">Today, the OpenStack community is proud to announce the release of <a href=\"https:\/\/www.openstack.org\/software\/openstack-gazpacho\/\">OpenStack 2026.1 Gazpacho<\/a>, the 33rd release of the world\u2019s most widely deployed open source cloud infrastructure software. But beyond the features and improvements, Gazpacho tells a deeper story: one of a global community continuing to come together to solve real infrastructure challenges through open collaboration.<\/p>\n\n\n\n<p>Every OpenStack release is the result of thousands of contributions, countless hours of collaboration, and a shared commitment to building open infrastructure that works in production. Gazpacho is no exception.<\/p>\n\n\n\n<h2>A Community Driving Momentum<\/h2>\n\n\n\n<p>The Gazpacho cycle reflects growing momentum across the OpenStack ecosystem. Over the past six months, around 500 contributors from 100 organizations worked together to deliver more than 9,000 code changes across OpenStack services, an increase in activity compared to the recent OpenStack 2025.1 Flamingo release. <\/p>\n\n\n\n<p>Behind those numbers are developers, operators, users, and organizations from across the globe collaborating in the open to build software that powers private clouds, edge environments, and increasingly, AI infrastructure.<\/p>\n\n\n\n<p>The scale of collaboration doesn\u2019t stop at code. OpenDev\u2019s <a href=\"http:\/\/zuulci.org\">Zuul CI system<\/a> continues to run more than one million jobs per release cycle, ensuring that every contribution is tested, validated, and production-ready before it reaches users.<\/p>\n\n\n\n<p>This level of rigor and transparency is what makes OpenStack unique. It\u2019s not just about shipping features, it\u2019s about building trust.<\/p>\n\n\n\n<h2>Open Collaboration, Global Impact<\/h2>\n\n\n\n<p>One of the most powerful aspects of the OpenStack community is its global nature. Contributors span hundreds of organizations and nearly every region of the world, bringing diverse perspectives and real-world requirements into the project.<\/p>\n\n\n\n<p>In the Gazpacho release, 40% of contributions came from European contributors highlighting how regional priorities like digital sovereignty are shaping the future of open infrastructure.<\/p>\n\n\n\n<p>This is the strength of open source: the ability to reflect the needs of different industries, geographies, and use cases, all within a shared codebase. Whether it\u2019s telecom operators optimizing for performance, enterprises migrating off proprietary platforms, or governments building sovereign cloud infrastructure, those needs show up directly in the software.<\/p>\n\n\n\n<h2>Solving Operator Challenges Together<\/h2>\n\n\n\n<p>At its core, OpenStack has always been driven by operators and Gazpacho continues that tradition.<\/p>\n\n\n\n<p>This release focuses heavily on simplifying operations, improving workload mobility, and enabling infrastructure to run consistently across increasingly complex environments. These priorities don\u2019t emerge in isolation; they come directly from community feedback, real-world deployments, and ongoing collaboration between users and contributors.<\/p>\n\n\n\n<p>For example, enhancements in Ironic introduce more intelligent automation, reducing the need for manual configuration and making it easier to manage bare metal infrastructure at scale. Features like autodetect deployment interfaces and automatic protocol detection reflect a broader goal: letting operators focus less on configuration and more on outcomes.<\/p>\n\n\n\n<p>Similarly, improvements in workload migration, such as enhanced cross-zone strategies and live migration support for sensitive workloads, address one of the most urgent challenges facing infrastructure teams today. As organizations accelerate migration from proprietary platforms, seamless mobility across environments is no longer optional; it\u2019s essential.<\/p>\n\n\n\n<h2>Performance and Flexibility for Modern Workloads<\/h2>\n\n\n\n<p>The Gazpacho release also brings significant improvements in performance and responsiveness, shaped by the needs of operators running at scale.<\/p>\n\n\n\n<p>Enhancements like parallel live migrations, asynchronous APIs, and better I\/O handling in Nova are direct responses to real-world demands for faster, more efficient infrastructure. At the same time, expanded hardware support, from GPUs to FPGAs and beyond, ensures OpenStack can support the growing diversity of modern workloads, including AI and data-intensive applications.<\/p>\n\n\n\n<p>These improvements are not built in isolation. They are the result of collaboration across projects\u2014Nova, Neutron, Ironic, Manila, Cyborg\u2014and across contributors who understand that infrastructure is a system, not a set of silos.<\/p>\n\n\n\n<h2>A Platform That Evolves with Its Community<\/h2>\n\n\n\n<p>Thirty-three releases in, OpenStack continues to evolve, not by chasing trends, but by responding to the needs of the operators running the software in production. As of October 2025, the global OpenStack footprint exceeds 55 million compute cores. <\/p>\n\n\n\n<p>The introduction of the SLURP (Skip Level Upgrade Release Process) model is a perfect example. Designed with operators in mind, SLURP allows for annual upgrades instead of every six months, reducing operational burden while maintaining a predictable release cadence.<\/p>\n\n\n\n<p>It\u2019s a reminder that innovation in OpenStack isn\u2019t just about features; it\u2019s also about how the software is delivered, maintained, and operated over time.<\/p>\n\n\n\n<h2>Looking Ahead<\/h2>\n\n\n\n<p>Gazpacho represents more than a release. It\u2019s a snapshot of a community in motion, growing, adapting, and continuing to build infrastructure that meets the needs of today while preparing for what comes next.<\/p>\n\n\n\n<p>From enabling workload migration at scale to supporting AI-driven infrastructure and advancing digital sovereignty, the direction of OpenStack is clear: open collaboration remains the foundation.<\/p>\n\n\n\n<p>And that foundation is only as strong as the people behind it.<\/p>\n\n\n\n<p>To everyone who contributed to the Gazpacho release\u2014code, documentation, testing, feedback, and beyond\u2014thank you. This is your release.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Today, the OpenStack community is proud to announce the release of OpenStack 2026.1 Gazpacho, the 33rd release of the world\u2019s most widely deployed open source cloud infrastructure software. But beyond the features and improvements, Gazpacho tells a deeper story: one of a global community continuing to come together to solve real infrastructure challenges through open&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-gazpacho-built-by-a-global-community-designed-for-real-world-infrastructure\/\" class=\"more-link\" title=\"Read OpenStack Gazpacho: Built by a Global Community, Designed for Real-World Infrastructure\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":68,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/9927"}],"collection":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/users\/68"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=9927"}],"version-history":[{"count":1,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/9927\/revisions"}],"predecessor-version":[{"id":9928,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/9927\/revisions\/9928"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=9927"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=9927"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=9927"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}