support invoking lxd init
Bug #1522879 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Unassigned |
Bug Description
'lxd init' initializes lxd for use on a system.
The format might look something like:
#cloud-config
lxd:
init_storage: 5G
That would ensure that lxd package is installed and then initialize storage to it.
The plan is to have lxd-init in the next couple weeks, this bug track cloud-init consumption.
Related branches
lp:~wesley-wiedenmeier/cloud-init/lxd-init
- cloud-init Commiters: Pending requested
-
Diff: 183 lines (+147/-0)5 files modifiedChangeLog (+1/-0)
cloudinit/config/cc_lxd.py (+66/-0)
config/cloud.cfg (+1/-0)
doc/examples/cloud-config-lxd.txt (+21/-0)
tests/unittests/test_handler/test_handler_lxd.py (+58/-0)
Changed in cloud-init: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
lxd init is already implemented and in the archive, it's command line interface will remain identical, it's just a bit buggy in 0.23 but as far as mapping things into cloud-init, it's good to go.
Init options: address ADDRESS backend NAME create- device DEVICE create- loop SIZE password PASSWORD
--auto
Automatic (non-interactive) mode
--network-
Address to bind LXD to (default: none)
--network-port PORT
Port to bind LXD to (default: 8443)
--storage-
Storage backend to use (zfs or dir, default: dir)
--storage-
Setup device based storage using DEVICE
--storage-
Setup loop based storage with SIZE in GB
--storage-pool NAME
Storage pool to use or create
--trust-
Password required to add new clients
Those should probably be exposed as is through cloud-init and then, for those which were set, passed to lxd init along with the --auto flag.