About MAAS 3.0 And LXD

With the release of MAAS 3.0, we moved LXD virtual machines out of Beta. Several articles in the MAAS documentation address LXD. Since no document ties all these features together, though, it’s time for a topical blog about LXD.

Table of Contents

About LXD

LXD, pronounced “lex-DEE,” is a container manager (and a lot more). LXD offers a user experience that is very similar to virtual machines, but using containers. MAAS is gradually shifting away from libvirt — and toward LXD — as the default VM host. It’s shifting mainly because LXD is a Canonical product. Canonical has better control over the code and better coordination between development teams for in-house products.

About using LXD as a VM host

When you create a KVM with MAAS 3.0, the MAAS UI pre-selects LXD as the default KVM host type:

The MAAS 3.0 Add KVM UI panel

Notice that the “Beta” designation has disappeared. You must enter a name for the KVM host, and an LXD address (more on that in a minute). When you’ve done so, and you click “Authenticate,” you’ll see the projects screen:

The second MAAS UI Add KVM panel, allowing selection of a project

You can choose an existing project (in this case, “default”). You can also create a new project in real time, using the Add new project box:

You can now create new projects while adding an lxd kvm

Clicking Next brings you to the detail screen for your new, LXD KVM host:

The maas lxd kvm host detail screen

Any VMs you create for this LXD KVM host will be assigned to the project my-lxd-project-1. You can compose a new VM within this KVM by simply selecting the + Compose VM button:

When you use lxc list to view your LXD inventory, you probably won’t see your newly-minted VM by default:

About addressing LXD

We’ll round out this blog with a note about LXD networking and MAAS. When you initialize LXD after installation, via lxd init, you have the option to create a bridge. If you choose the defaults while doing so, you should be able to communicate with LXD containers from MAAS. Here’s a cheat-sheet:

Would you like to use LXD clustering? (yes/no) [default=no]: no
Do you want to configure a new storage pool? (yes/no) [default=yes]: yes
Name of the new storage pool [default=default]:  
Name of the storage back-end to use (btrfs, dir, lvm, zfs, ceph) [default=zfs]: dir
Would you like to connect to a MAAS server? (yes/no) [default=no]: no
Would you like to create a new local network bridge? (yes/no) [default=yes]: no
Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: yes
Name of the existing bridge or host interface: br0
Would you like LXD to be available over the network? (yes/no) [default=no]: yes
pAddress to bind LXD to (not including port) [default=all]:
Port to bind LXD to [default=8443]:
Trust password for new clients:
Again:
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]
Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: no

Note a couple of key points here:

Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: yes
Name of the existing bridge or host interface: br0
Would you like LXD to be available over the network? (yes/no) [default=no]: yes
pAddress to bind LXD to (not including port) [default=all]:
Port to bind LXD to [default=8443]:
Trust password for new clients:
Again:

It doesn’t matter whether you let LXD create the bridge for you (most common) or use a bridge that you’ve created (what’s done here). When creating the LXD address, you’ll formulate it like this:

Pausing for experiments

There’s quite a bit more to say about MAAS 3.0 and LXD KVMs / VMs. We’ll cover that in later blogs. For now, try experimenting with MAAS 3.0 and LXD.