[nul_byte]

You missed Red Hat, who seem to be the only company having major success with OpenStack [1]

Most of IBM, Intel, HPE etc have thrown in the towel and now offer their own services on top of Red Hat OpenStack.

OpenStack has now found itself beyond enterprise, and now being the de-facto platform for NFV running mobile networks, and I guess Red Hat are becoming the winner here as they are so used to supporting an OpenStack 'type of' infrastructure for large bodies such as banking, telco, health etc. When you consider Red Hat are already large well established contributors to all of the layers of the OpenStack 'stack' such as KVM/QEMU , libvirt, the kernel itself, + overlay networking tech such as OVS, and now DPDK, you can see why they are well positioned to support and run OpenStack clouds.

[1] https://www.theregister.co.uk/2017/03/28/red_hat_cloud_quart...

[lathiat]

Canonical also have a strongly growing OpenStack business with no signs of pulling out from it.

[houseofzeus]

SUSE folks on twitter have also been highlighting that they are still hiring, even in the wake of the addition of the HPE OpenStack team (or what was left of it).

Given all of the inter-dependencies between OpenStack services and lower level Linux constructs and software (OVS, Ceph, QEMU, etc.) those who were already used to distributing and managing these already turned out to be the ones who were best able to make the combination work.

That said at least some folks who were working on OpenStack and related technologies at Canonical are among those now looking for new gigs:

https://twitter.com/zulcss/status/852542117566189568

Thus while cloud remains on their priority list it is not immediately clear how big a part OpenStack will play in that going forward for Canonical versus solutions that run on the reigning public clouds.

[fred_is_fred]

They just had a massive round of layoffs that hit cloud as well. That doesn't mean they are pulling out ,but its also not a wild success.

[bonzini]

(Disclaimer: I work on Red Hat in the virtualization team).

Canonical seriously lacks expertise in KVM (+QEMU+libvirt), and you cannot take that for granted when you have a customer with VMs crashing that is asking for a fix.

[kashyapc]

Those who have down-voted the above almost certainly do not know the situation on the ground.

FWIW, I recently had to explicitly inform the Canonical Virt maintainers (of which there seem to be very few) about which patches that ought to be backported to fix a bug in one of their libvirt packages that was seriously affecting (i.e. preventing from patches being merged) OpenStack upstream CI environment.

The said bug had fixes already available upstream, and are straight backports with no conflicts. No one bothered to do the "unsexy" work of backporting & cutting a quick stable build.

Only after pointing out the commits (with help from one of the lead upstream libvirt maintainers), and posting them on a LaunchPad bug, did the Ubuntu maintainers stepped in to backport the said fixes.