MicroCloud
Platform:
26.04
24.04
22.04
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 105 | 09 Oct 2025 | |
| latest/edge | 103 | 09 Oct 2025 | |
| latest/edge | 104 | 09 Oct 2025 | |
| latest/edge | 102 | 09 Oct 2025 | |
| latest/edge | 101 | 09 Oct 2025 | |
| 3/stable | 173 | 19 Oct 2026 | |
| 3/stable | 175 | 19 Oct 2026 | |
| 3/stable | 174 | 19 Oct 2026 | |
| 3/stable | 176 | 19 Oct 2026 | |
| 3/candidate | 173 | 16 Oct 2026 | |
| 3/candidate | 175 | 16 Oct 2026 | |
| 3/candidate | 176 | 16 Oct 2026 | |
| 3/candidate | 174 | 16 Oct 2026 | |
| 3/edge | 176 | 16 Oct 2026 | |
| 3/edge | 175 | 16 Oct 2026 | |
| 3/edge | 174 | 16 Oct 2026 | |
| 3/edge | 173 | 16 Oct 2026 |
juju deploy microcloud --channel 3/stable
Manage observability for an externally deployed MicroCloud cluster.
The MicroCloud charm does not deploy or bootstrap a MicroCloud cluster. MicroCloud (LXD, MicroCeph, MicroOVN) must already be deployed out-of-band, with each MicroCloud member added to Juju via "juju add-machine".
On each unit the charm requires MicroCloud to already be initialized. It validates that this unit's own hostname is a MicroCloud member and blocks if it is not. The charm never installs the MicroCloud component snaps but it may install the ovn-exporter snap.