Skip to main content
  1. Blog
  2. Article

Canonical
on 11 March 2015

Architecting OpenStack for enterprise reality



With OpenStack becoming more and more popular as a cloud-building technology for enterprises, companies are asking themselves several important questions. How viable is OpenStack as an enterprise platform? Is it possible (and feasible) to integrate it with existing virtualisation infrastructure, e.g. vSphere from VMware? Is there a business case for such integration, and what are the risks and challenges associated with it? Finally, how do they best utilise OpenStack: is the “vanilla” architecture always the best approach, or is there a case for swapping out certain components for third-party tools?

Gigaom analyst Paul Miller looks at these questions and more in this report sponsored by Canonical. For a more in-depth look at integrating vSphere and OpenStack, you may also want to read this whitepaper.

Download eBook

Related posts


Massimiliano Gori
27 March 2026

Modern Linux identity management: from local auth to the cloud with Ubuntu

Cloud and server Article

The modern enterprise operates in a hybrid world where on-premises infrastructure coexists with cloud services, and security threats evolve daily. IT administrators are tasked with a difficult balancing act: maintaining traditional local workflows while managing the inevitable shift toward cloud-native architectures. Identity has emerged ...


Abdelrahman Hosny
24 March 2026

Canonical welcomes NVIDIA’s donation of the GPU DRA driver to CNCF

Partners Article

At KubeCon Europe in Amsterdam, NVIDIA announced that it will donate the GPU Dynamic Resource Allocation (DRA) Driver to the Cloud Native Computing Foundation (CNCF). This marks an important milestone for the Kubernetes ecosystem and for the future of AI infrastructure. For years, GPUs have been central to modern machine learning and high ...


ijlal-loutfi
23 March 2026

Hot code burns: the supply chain case for letting your containers cool before you ship

Ubuntu Article

Zero CVEs doesn’t mean secure. It means unexamined. New code has zero CVEs because no one has studied it yet, and if you’re rebuilding nightly from upstream, you’re signing first and asking questions later. In software supply chain security, the freshest code isn’t always the safest. Sometimes the most secure component in your pipeline is ...