Learn MicroCloud - History, Background & Why You Need It

#Introduction

With our environment ready from episode 0, it's now time to understand why MicroCloud exists. Every major technology is born from a real problem, and MicroCloud is no exception: building a simple small private cloud has always meant assembling many components by hand — hypervisor, distributed storage, and networking. In episode 1 we trace its history from Canonical's announcement in November 2023, the philosophy behind it, and the concrete reasons why this LXD-based lightweight cloud is needed.

The questions we'll answer: what problem is MicroCloud trying to solve? Why is "3 nodes" its magic number? And why choose snap as the distribution mechanism? These answers matter because they determine when you should choose MicroCloud in production.

#History and Background

#Born from the Need for Lightweight Edge Clouds

MicroCloud was announced by Canonical in November 2023. The context at the time: the world was moving toward edge computing — bringing the cloud closer to the data source — yet existing solutions were too heavy. OpenStack offers full features but needs many nodes and controllers; Kubernetes is great for containers, but VM workloads and distributed storage still have to be assembled separately. MicroCloud answered with a bold proposition: a complete cloud inside 3 nodes, enough for the edge, retail stores, campuses, or homelabs.

Its design philosophy is simple: simple, open source, and low-touch. Instead of writing a complex new orchestrator, Canonical unified three mature technologies — LXD, Ceph (via MicroCeph), and OVN (via MicroOVN) — and automated the setup. The result is a platform that a single admin can install and configure in minutes, not weeks.

#Release Timeline

• 2.1.0 LTS (15 November 2024): the first LTS release, marking MicroCloud as production-ready. Supports single-node and 3-node HA, and introduces proactive trust when joining.
• 3.1 (March 2026): integration of the MicroCloud Cluster Manager (experimental) and experimental MicroOVN 26.03 — this version isn't yet recommended for production.
• 3.2 (24 April 2026): the latest feature release, compatible with LXD 6.8.
• 2.1.3 LTS (24 April 2026): the fourth LTS release on the 2.x track — the stable choice for production.

snap list microcloud
microcloud version

This "two versions at once" pattern mirrors the Ubuntu ecosystem itself: an LTS track that's maintained for a long time for production, and a feature track that brings innovation faster. We compare the two in detail in episode 17.

#Why You Need MicroCloud

#One Command: microcloud init

MicroCloud's main strength is total setup automation. With a single microcloud init command on the first node (followed by microcloud join on the others), you get three things at once that previously required hours of manual configuration:

• LXD cluster — container & VM instances with automatic scheduling.
• Ceph storage — a block pool for instance disks, with built-in replication.
• OVN network — an overlay network automatically connected across all nodes.

3x Ubuntu kosong
      │  microcloud init + microcloud join
      ▼
┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│ LXD + Ceph  │  │ LXD + Ceph  │  │ LXD + Ceph  │
│ + OVN       │◄►│ + OVN       │◄►│ + OVN       │
└─────────────┘  └─────────────┘  └─────────────┘
         satu cluster, satu cloud

Without MicroCloud, you'd have to build an LXD cluster with lxd cluster add, configure Ceph pools and Ceph network manually, and then arrange OVN — each step prone to configuration errors. MicroCloud removes that work and ensures the configuration across all three layers is always consistent.

#Built-in HA

Because it runs on top of an LXD cluster and Ceph, high availability is baked in from the start. If one node dies, instances running on other nodes aren't disrupted (their data is replicated in Ceph), and the LXD cluster marks the down node. We test this scenario hands-on in episode 9.

#Edge and Lightweight Clouds Without Heavy Controllers

OpenStack needs controller nodes, network nodes, and many services. MicroCloud has no separate controller — all nodes are equal peers, and the LXD cluster handles consistency through quorum. This makes it a great fit for:

• Edge: small clouds at branches, stores, or factories with 1-2 local admins.
• Homelab: home infrastructure that wants HA without OpenStack complexity.
• Small-to-medium clusters: 3-50 nodes with VM/container workloads.

#Delivered via Snap: Transactional Updates

MicroCloud and all its components are distributed as snaps. This isn't a minor technical detail — it defines the operational experience:

• Transactional updates: the snap is downloaded, installed, then switched atomically; if it fails, the system automatically rolls back to the previous version.
• One release source: LXD, Ceph, OVN, and the orchestrator versions are released together and tested as a single unit.
• Strict confinement: every component is isolated; we cover the security in episode 13.

#Position in the Lightweight Cloud Ecosystem

To position MicroCloud, remember the private cloud solution landscape:

• OpenStack: large clouds, many tenants, full flexibility — but heavy and complex.
• Kubernetes (K3s/K8s): container-native orchestration — powerful, yet not a distributed storage/VM provider by default.
• Proxmox VE: a VM/CT hypervisor with optional Ceph — good, but not a "cloud" solution with automated overlay networking.
• MicroCloud: a lightweight LXD-based private/edge cloud with HA storage & networking in a single command.

We do a thorough comparison in episode 22. What matters now: MicroCloud fills the "truly simple small cloud" space that has long been empty between single hypervisors and large clouds.

#Closing

Key takeaways:

• MicroCloud was announced by Canonical in November 2023 with a simple, open source, and low-touch philosophy.
• The 2.1.0 LTS release (Nov 2024) marked production readiness; 3.2 (Apr 2026) is the latest feature release.
• A single microcloud init command forms the LXD cluster, Ceph storage, and OVN network all at once.
• Built-in HA from the LXD cluster + Ceph replication, without a separate controller.
• Snap distribution provides transactional updates and automatic rollback.

In the next episode, we'll dissect MicroCloud's core concepts and main architecture — how LXD, MicroCeph, and MicroOVN work together under the MicroCloud snap orchestration, the components that get installed, and the roles of the microcloud CLI (init, join, status, cluster) and the LXD API. This is the anatomy that will explain every command we run in the coming episodes.