Skip to main content
  1. Blog
  2. Article

nickbarcet
on 3 February 2011

Canonical joins the OpenStack community


OpenStack today have made a number of announcements about the Bexar release of their cloud stack and we were delighted to be able to confirm its inclusion in the repositories for Ubuntu 11.04 as well as officially joining the community. We have been engaged with the OpenStack community informally for some time. Some Canonical alumni have been key to driving the OpenStack initiative over in Rackspace and there has been a very healthy dialogue between the two projects with strong attendance at UDS and at the OpenStack conferences by engineers in both camps.

In fact it is noteworthy that the OpenStack project has taken a lot of the methodology of the Ubuntu project and applied to how they self-organise and release. They have the same twice-yearly open conference to drive the definition of the project and a similar but three-monthly release cycle. It’s easy to forget that this now ‘standard’, time based, approach to open source development and release was pioneered by Ubuntu and it is gratifying to see it permeate.

But as to OpenStack technology, I know that there are many users very keen to get their hands on a more fully integrated version that Bexar on Ubuntu Server 11.04 will offer. It has always been the goal of Ubuntu with regards to cloud to offer the best integrated experience for open source cloud development and deployment. We did it with Eucalyptus for Ubuntu Enterprise Cloud for the past two years and the next release of this in April will continue on offering a great fully-supported option for businesses looking to bring cloud technology within the firewall. In fact only yesterday saw the official launch of UEC on Dell servers (www.dell.com/canonical) which offers businesses the opportunity to buy hardware from Dell with UEC baked in and fully supported by both companies.

Our aim with OpenStack over time is to make Ubuntu the best OS for clouds built on this stack, both at the infrastructure and guest levels. There is real energy and momentum building around this technology and we congratulate the guys and girls in that project for their success so far. It looks a terrific base for building out open-source based public clouds and its embracing on not just its own APIs but also the EC2 APIs. This offers great options for users and customers to remain flexible as we move towards industry-wide open standards for these types of architectures. In 11.04 (Natty Narwhal), OpenStack 2011.1 (Bexar) will be delivered as a technology preview, and Canonical will not yet be able to provide full support for it. We first want to allow our users to test it and provide us feedback before providing it as a production ready environment. Comments, feedback and reactions are welcome on the Ubuntu-Cloud mailing list, forum and irc channels (http://cloud.ubuntu.com/community/interact/).

Related posts


Canonical
16 March 2026

Meet Canonical at NVIDIA GTC 2026: NVIDIA CUDA and NVIDIA Vera Rubin NVL72 support in Ubuntu 26.04 LTS

Ubuntu Article

Previewing at NVIDIA GTC 2026: NVIDIA CUDA support in Ubuntu 26.04 LTS, NVIDIA Vera Rubin NVL72 architecture support in Ubuntu 26.04, Canonical’s official Ubuntu image for NVIDIA Jetson Thor, upcoming support for NVIDIA DGX Station and NVIDIA DOCA-OFED, and NVIDIA RTX PRO 4500 support. NVIDIA GTC 2026 is here, bringing together the techno ...


Luci Stanescu
12 March 2026

AppArmor vulnerability fixes available

Ubuntu Article

Qualys discovered several vulnerabilities in the AppArmor code of the Linux kernel. These are being referred to as CrackArmor, while CVE IDs have not been assigned yet. All of the vulnerabilities require unprivileged local user access. The impact of these vulnerabilities ranges from denial of service to kernel memory information leak, rem ...


David Beamonte
11 March 2026

The bare metal problem in AI Factories

MAAS MAAS

As AI platforms grow into large-scale “AI Factories,” the real bottleneck shifts from model design to operational complexity. With expensive GPU accelerators, hardware failures and inconsistent configurations lead directly to lost throughput and reduced return on investment. While Kubernetes orchestrates workloads, it cannot fix broken ph ...