From a3e7e4e35055bbbd908a4c0195c8b8c9ca97c71e Mon Sep 17 00:00:00 2001 From: Mira Limbeck Date: Tue, 25 Jun 2019 11:36:33 +0200 Subject: [PATCH] add cloudinit dump and snippets documentation Adds documentation for the cloudinit snippets support and how 'qm cloudinit dump' can be used to get a base config file. Signed-off-by: Mira Limbeck --- qm-cloud-init.adoc | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/qm-cloud-init.adoc b/qm-cloud-init.adoc index 23750da..9795479 100644 --- a/qm-cloud-init.adoc +++ b/qm-cloud-init.adoc @@ -131,6 +131,42 @@ commands for reducing the line length. Also make sure to adopt the IP setup for your specific environment. +Custom Cloud-Init Configuration +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Cloud-Init integration also allows custom config files to be used instead +of the automatically generated configs. This is done via the `cicustom` +option on the command line: + +---- +qm set 9000 --cicustom "user=,network=,meta=" +---- + +The custom config files have to be on a storage that supports snippets and have +to be available on all nodes the VM is going to be migrated to. Otherwise the +VM won't be able to start. +For example: + +---- +qm set 9000 --cicustom "user=local:snippets/userconfig.yaml" +---- + +There are three kinds of configs for Cloud-Init. The first one is the `user` +config as seen in the example above. The second is the `network` config and +the third the `meta` config. They can all be specified together or mixed +and matched however needed. +The automatically generated config will be used for any that don't have a +custom config file specified. + +The generated config can be dumped to serve as a base for custom configs: + +---- +qm cloudinit dump 9000 user +---- + +The same command exists for `network` and `meta`. + + Cloud-Init specific Options ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.39.2