To give the org credit, they found and fixed the problem – a typo in a script, apparently – but as a result, the sequencing of the demos was disrupted and the result was a little confusing.

I’m gonna quote this, the next time my boss asks why we need a thorough testing culture.

Edit: Also: language servers and static code checkers safe money, so don’t hassle me about why I need to config neovim while clocked in.

This is the best summary I could come up with:

Canonical hosted an amusingly failure-filled demo of its new easy-to-install, Ubuntu-powered tool for building small-to-medium scale, on-premises high-availability clusters, Microcloud, at an event in London yesterday.

The presentation was as buzzword-heavy as one might expect, and it’s also extensively based on Canonical’s in-house tech, such as the LXD containervisor, Snap packaging, and, optionally, the Ubuntu Core snap-based immutable distro.

Microcloud combines several existing bits of off-the-shelf FOSS tech in order to make it easy to link from three to 50 Ubuntu machines into an in-house, private high-availability cluster, with live migration and automatic failover.

Multiple vendors have tools for easily building Kubernetes clusters; for instance, in a prior role, this vulture wrote the original installation guide for SUSE’s CaaSP, now discontinued and replaced by its Rancher acquisition.

Even so, Flatpak remains poor at handling command-line tools and can’t be used to build a distro, for which you need to tackle OStree head-on.

Snap works by keeping each app in a single, compressed file, making transactionality easy without COW or anything resembling Git.

The original article contains 1,564 words, the summary contains 171 words. Saved 89%. I’m a bot and I’m open source!