...

A key feature of virtualization technology is taking snapshots and cloning. With traditional file systems, this is expensive in terms of storage and speed. Next generation The next generation volume manager and file system ZFS solves many of theses problems and it is recommended by Ubuntu to install and use with LXD,

sudo apt-get install bridge-utils zfsutils-linux # must be using Ubuntu 16.04 or higher.

The other key feature to use with LXD is network bridging. By it's nature, the containers created by LXD exist in their own network. The network bridge utils allow you to expose your container to the rest of the network,

sudo apt-get install lxd

...

bridge-utils

Finally install LXD,

sudo lxd init

Pretty much first set are defaults. Will add notes about ZFS. Should explain loop device here too. Note Roderick using Azure Ubuntu 16.10 has simpler following screens,

apt-get install lxd

Initial Configuration

Before using LXD you need to to do an initial configuration.

The configuration is evolving and you will notice differences between versions of Ubuntu. Because the material is rather tough, we'll archive the older Ubuntu lxd init and keep the most current release here,

LXD Init for LTS

Name# ofshow theversion storageof backend to use (dir or zfs) [default=zfs]: zfs
Create a new ZFS pool (yes/no) [default=yes]? yes
Name of the new ZFS pool [default=lxd]: lxd
Would you like to use an existing block device (yes/no) [default=no]? no
Size in GB of the new loop device (1GB minimum) [default=15]: 15
Would you like LXD to be available over the network (yes/no) [default=no]? no
Would you like stale cached images to be updated automatically (yes/no) [default=yes]? yes
Would you like to create a new network bridgeUbuntu,
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.2 LTS
Release:    16.04
Codename:   xenial
 
# initialize LXD
sudo lxd init

For the most part you will be able to hit Enter and accept defaults. Some options you may go back and change but others will require lots of work so take your time.

I'll go over some of the more confusing options,

Name of the storage backend to use (dir or zfs) [default=zfs]: 
Create a new ZFS pool (yes/no) [default=yes]? yes
What should the new bridge be called [default=lxdbr0]? lxdbr0
What IPv4 subnet should be used (CIDR notation, "auto" or "none") [default=auto]? auto
What IPv6 subnet should be used (CIDR notation, "auto" or "none") [default=auto]? auto
LXD has been successfully configured.

Tin using Ubuntu 16.04.1

Name of the new ZFS pool [default=lxd]: lxd
Would you like to use an existing block device (yes/no) [default=no]? no
Size in GB of the new loop device (1GB minimum) [default=1518]: 15

LXD allows management over the network. This is useful in an environment with multiple host LXDs and you want the ability to centrally manage. In this article, I am choosing yes because we'll later use Virtual Machine Manager to show GUI management,

Would you like LXD to be available over the network (yes/no) [default=no]? noyes
WouldAddress youto likebind staleLXD cached images to be(not updated automatically (yes/noincluding port) [default=yesall]?: yes
WouldPort you like to createbind aLXD new network bridge (yes/no) to [default=yes8443]?: yes
WhatTrust shouldpassword thefor new bridgeclients: be
called [default=lxdbr0]? lxdbr0
What IPv4 subnet should be used (CIDR notation, "auto" or "none") [default=auto]? auto
What IPv6 subnet should be used (CIDR notation, "auto" or "none") [default=auto]? auto
LXD has been successfully configured.

...

Again: 

LXD init will configure a bridge. In order to say yes to this you must have the bridge utils installed. In this article we covered that so say yes

WouldDo you likewant to createconfigure athe newLXD network bridge (yes/no) [default=yes]? <yes>
What should the new bridge be called [default=lxdbr0]? <Ok>
Do you want to setup an IPv4 subnet? <yes>

This subnet was selected for your convenience and next questions have been pre-answered accodingly. Please make sure this subnet isn't already in use somewhere on your network, if it is, change it to one which isn't. If you later notice network connectivity issues, re-configure lxd and pick a different subnet.
<Ok>

# resulting IPv4 address will vary in this example using VMWare fusion it is 10.232.27.1
<Ok>
... all sorts of things... need to redo this.

If you need to reconfigure the bridge you can by using this command.

sudo dpkg-reconfigure -p medium lxd

...

 You will be prompted with a "text ui" interface. Use your arrow keys to pick the buttons.

Introduction,

The default bridge name is lxdbr0. It's just a name but suggest you leave as default. To get to the button, use the down arrow key,

Go with IPv4 unless you have some special need to use IPv6,

You will be assigned a random subnet. For the purposes of this article, think of a subnet as a way of naming your postal code. It's the difference between Canada and US postal code. When given time I'll provide more description and write or link to a good article on subnets,

IPv4 address. This prompt is not very clear. Going to go back and check shortly. It is either reserving this IP address or asking you for a sample to determine the subnet.

A valid CIDR mask. (e.g. 24),

Initial IP Address Range does not matter unless you want to use a lot of static IP addresses. I need to think about this a bit more... the idealism behind cloud is not require static, but reality (at least for now), I still find static useful and in some application designs (stateful apps, older PKI's... ect...) absolutely necessary.

Pick default for the last address,

The DHCP leas number should be default unless you went and changed the range. If so you should adjust to match. Yeah I know the numbers do not add up (254 - 2 = 252) but I believe there is some fancy math for that... look up and link to my LXC articles.

For almost all networks this will be Yes. Tin google or to talk to Dickson or Andrew though at some point to put explanations here.

Unless you really need IPv6 say no,

After this you will be taken out of the Text UI. The warning message is due to network bridge setup,

Warning: Stopping lxd.service, but it can still be activated by:
  lxd.socket
LXD has been successfully configured.

I hate doing this in Linux, but let's reboot to make sure the lxd service is ok,

sudo reboot

Add Users to the lxd Group

By default, users cannot yet use LXD until you add them to the reserved group. In this example, I'm adding my account,

sudo usermod -a -G lxd usernametin.pham

Reminder that if you use your own account, you need to log out then log back in.

Verify LXD is Working

Basic test to verify lxd is working and it will also generate your random client certificate (used by LXD to secure calls) on your account,

lxc image list
+-------+-------------+--------+-------------+------+------+-------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE |
+-------+-------------+--------+-------------+------+------+-------------+

At this point we have no LXD images.

Basic LXD Commands

To view your bridge information.

lxc profile edit default

Notice the following,

name: default
config: {}
description: Default LXD profile
devices:
  eth0:
    nictype: bridged
    parent: lxdbr0
    type: nic
name: default

What we see here is that the containers will be handed IPs from the LXD bridge and exist within the LXD network.

Images

...

Cached Images in Image Store

...

...

lxc image list ubuntu: | less
+--------------------+--------------+--------+-------------------------------------------------+---------+----------+-------------------------------+
|       ALIAS        | FINGERPRINT  | PUBLIC |                   DESCRIPTION                   |  ARCH   |   SIZE   |          UPLOAD DATE          |
+--------------------+--------------+--------+-------------------------------------------------+---------+----------+-------------------------------+
| p (5 more)         | 6041c5e200b6 | yes    | ubuntu 12.04 LTS amd64 (release) (20161205)     | x86_64  | 156.47MB | Dec 5, 2016 at 12:00am (UTC)  |
+--------------------+--------------+--------+-------------------------------------------------+---------+----------+-------------------------------+
| p/armhf (2 more)   | c19b1fff3336 | yes    | ubuntu 12.04 LTS armhf (release) (20161205)     | armv7l  | 135.19MB | Dec 5, 2016 at 12:00am (UTC)  |
+--------------------+--------------+--------+-------------------------------------------------+---------+----------+-------------------------------+
| p/i386 (2 more)    | ce5c6821eebb | yes    | ubuntu 12.04 LTS i386 (release) (20161205)      | i686    | 139.28MB | Dec 5, 2016 at 12:00am (UTC)  |
+--------------------+--------------+--------+-------------------------------------------------+---------+----------+-------------------------------+
...
# Reduce the list to your machine architecture, in my case and most it will be amd64
lxc image list ubuntu: amd64

The output table from list is not very clear. I don't understand what to reference to use What you reference when using the "launch" command . Will put explanation here once figured out. Here is what I can tellis the main part of the ALIAS name ignoring anything in brackets. For example to install and launch other distrobusions based off of the images: list which has all Linux distributions,

At this point LXD is all setup and ready to use.

...

There are two key methods. Clone semi-live using snapshots and shutting down first.

Shutdown Approach

Log into myhost02

...

lxc file push sourcefile container/path/to/directory/
lxc file pull container/path/to/file directory

Reconfigure

If you need to reconfigure the bridge you can by using this command.

sudo dpkg-reconfigure -p medium lxd

Reference

Initializing LXD  - https://insights.ubuntu.com/2016/03/16/lxd-2-0-installing-and-configuring-lxd-212/

...

Live Container Migrations - https://bobcares.com/blog/lxc-live-migration-to-minimize-business-downtime/

Mounting a local folder - https://tribaal.io/nicer-mounting-home-in-lxd.html