This package can be used for configuring existing virtual machine images. Virtual machine images can be either downloaded straight from a distribution provider (see cloud_init_images) or generated via tools such as the gen-vm-image.
The following dependencies are required to be installed on the system to use the configure-vm-image command:
How to install each of these for a given distribution can be found at pkgs.org.
Dependency install scripts for various distributions can be found in the dep root directory of this package.
The tool itself can be installed either via pip:
pip install configure-vm-image
or by cloning the repository and running the following command in the root directory:
make install
If no argument is given to the make install command, the package will be installed inside a virtual environment called venv in the root directory of the package.
The VENV_NAME argument can be used to specify a different name for the virtual environment inwhich the package is installed.
Upon installation, the configure-vm-image command is installed and can be used to configure an existing virtual machine image.
To generate such an image, the gen-vm-image tool is available.
To configure the existing image itself, configure-vm-image uses the cloud-init tool to customize the image.
cloud-init itself achives this by running a set of scripts upon image boot that utilises a set of preset configuration files.
These configuration files includes:
- user-data - meta-data - vendor-data - network-config
Therefore, the configure-vm-image tool attempts to load each of these files when launched from the given parameter set paths for each of them.
The parameter names for these can be discovered by running the command with the --help flag:
usage: configure_image.py [-h]
[--version]
[--image-format CONFIGURE_ARGUMENT_IMAGE_FORMAT]
[--config-user-data-path CONFIGURE_ARGUMENT_USER_DATA_PATH]
[--config-meta-data-path CONFIGURE_ARGUMENT_META_DATA_PATH]
[--config-vendor-data-path CONFIGURE_ARGUMENT_VENDOR_DATA_PATH]
[--config-network-config-path CONFIGURE_ARGUMENT_NETWORK_CONFIG_PATH]
[--configure-vm-orchestrator CONFIGURE_ARGUMENT_CONFIGURE_VM_ORCHESTRATOR]
[--configure-vm-name CONFIGURE_ARGUMENT_CONFIGURE_VM_NAME]
[--cloud-init-iso-output-path CONFIGURE_ARGUMENT_CLOUD_INIT_ISO_OUTPUT_PATH]
[--configure-vm-log-path CONFIGURE_ARGUMENT_CONFIGURE_VM_LOG_PATH]
[--configure-vm-template-path CONFIGURE_ARGUMENT_CONFIGURE_VM_TEMPLATE_PATH]
[--configure-vm-template-values KEY=VALUE]
[--reset-operations CONFIGURE_ARGUMENT_RESET_OPERATIONS]
[--verbose]
[--verbose-reset]
image_path
options:
-h, --help show this help message and exit
--version, -V Print the version of the program
Configure Virtual Machine Image:
image_path The path to the image that is to be configured.
--image-format CONFIGURE_ARGUMENT_IMAGE_FORMAT
The format of the image that is to be configured. The tool tries to automatically discover this if not set.
(default: None)
--config-user-data-path CONFIGURE_ARGUMENT_USER_DATA_PATH
The path to the cloud-init user-data configuration file.
(default: cloud-init/user-data)
--config-meta-data-path CONFIGURE_ARGUMENT_META_DATA_PATH
The path to the cloud-init meta-data configuration file.
(default: cloud-init/meta-data)
--config-vendor-data-path CONFIGURE_ARGUMENT_VENDOR_DATA_PATH
The path to the cloud-init vendor-data configuration file.
(default: cloud-init/vendor-data)
--config-network-config-path CONFIGURE_ARGUMENT_NETWORK_CONFIG_PATH
The path to the cloud-init network-config configuration file that is used to configure the network settings of the image.
(default: cloud-init/network-config)
--configure-vm-orchestrator CONFIGURE_ARGUMENT_CONFIGURE_VM_ORCHESTRATOR, -cv-orch CONFIGURE_ARGUMENT_CONFIGURE_VM_ORCHESTRATOR
The orchestrator to use when provisioning the virtual machine that is used to configure a particular virtual machine image.
(default: libvirt-provider)
--configure-vm-name CONFIGURE_ARGUMENT_CONFIGURE_VM_NAME, -cv-name CONFIGURE_ARGUMENT_CONFIGURE_VM_NAME
The name of the VM that is used to configure the image.
(default: configure-vm-image)
--cloud-init-iso-output-path CONFIGURE_ARGUMENT_CLOUD_INIT_ISO_OUTPUT_PATH, -ci-output CONFIGURE_ARGUMENT_CLOUD_INIT_ISO_OUTPUT_PATH
The path to the cloud-init output iso image file that is generated based on the data defined in the user-data, meta-data, vendor-data, and network-config files. This seed iso file is then subsequently used to configure the defined input image.
(default: cloud-init/cidata.iso)
--configure-vm-log-path CONFIGURE_ARGUMENT_CONFIGURE_VM_LOG_PATH, -cv-log CONFIGURE_ARGUMENT_CONFIGURE_VM_LOG_PATH
The path to the log file that is used to log the output of the configuring VM.
(default: tmp/configure-vm.log)
--configure-vm-template-path CONFIGURE_ARGUMENT_CONFIGURE_VM_TEMPLATE_PATH, -cv-tp CONFIGURE_ARGUMENT_CONFIGURE_VM_TEMPLATE_PATH
The path to the template file that is used to configure the VM.
(default: res/configure-vm-template.xml.j2)
--configure-vm-template-values KEY=VALUE, -cv-tv KEY=VALUE
An additional set of comma seperated key=value pair arguments that should be passed to the --configure-vm-template-path. If a value contains spaces, you should define it with quotes.
(default: [])
--reset-operations CONFIGURE_ARGUMENT_RESET_OPERATIONS, -ro CONFIGURE_ARGUMENT_RESET_OPERATIONS
The operations to perform during the reset operation.
(default: defaults,-ssh-userdir)
--verbose, -v Flag to enable verbose output. (default: False)
--verbose-reset, -vr Flag to enable verbose output during the reset. (default: False)
As can be gathered from the help output, configure-vm-image expects that each of these cloud-init configuration files are present in a cloud-init directory in the current path when configure-vm-image is executed.
If any of these configuration files are not present, the tool will skip that particular configuration file and continue on even if none are given.
This means that the tool can be used to configure an image with only a subset of the configuration files or none at all.
Most distributions have a publically available cloud-init image that can be downloaded. A subset highlight of these can be found below.
In this example, we will configure an existing virtual machine image with a basic cloud-init configuration.
This includes creating a default_user with sudo capabilities that can authenticate via the console with a password.
An example of such configuration can be found in the examples/basic-cloud-init directory of this package.
To use this, we can create a symlink of it in the root directory of the repo:
ln -s examples/basic-cloud-init cloud-init
Subsequently, you can adjust the configuration files to your liking and in accordance with the cloud-init documentation.
After this has been prepared, But, before we can begin, we need to install the dependencies for the tool:
./dep/<distro>/install-dep.sh
With this in place, we can now configure the image by running the following command:
configure-vm-image <path_to_image>
This will both generate a cloud-init ISO image and launch a virtual machine that mounts said ISO and the disk image to be configured.
Upon launch, the output of the configuring VM will be logged to the log file specified with the --configure-vm-log-path parameter,
which default can be seen in the help output above in help_output. Additional output from the configure-vm-image tool can also be produced with the --verbose flag
as also highlighted in the help output.
Beyond the simple example, where a single disk image is configured, configure-vm-image can also be used to partition and format additional disks beyond the primary vm image disk.
This can be achived by using the cloud-init feature of disk_setup and fs_setup.
An example of such a cloud-init configuration can be found in the examples/disk-setup-cloud-init directory of this package.
In the example, three additional disks are expected to be present in the VM at the specified device paths, namely:
- /dev/vdb
- /dev/vdc
- /dev/vdd
To ensure this, the VM template file (as specified with --configure-vm-template) should be adjusted to include these disks:
<devices>
...
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='{{disk2_path}}'/>
<target dev='vdb' bus='virtio'/>
</disk>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='{{disk3_path}}'/>
<target dev='vdc' bus='virtio'/>
</disk>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='{{disk4_path}}'/>
<target dev='vdd' bus='virtio'/>
</disk>
...
</devices>
Here it is important to match the target device names with the device paths specified in the cloud-init configuration file. After this has been prepared, the cloud-init configuration files can be symlinked to the root directory of the repo:
ln -s examples/disk-setup-cloud-init cloud-init
Once this is complete, the configure-vm-image tool can be run with the nessesary template values that specify the paths to the additional disk images:
configure-vm-image <path_to_image> --configure-vm-template-values disk2_path=<path_to_disk2> disk3_path=<path_to_disk3> disk4_path=<path_to_disk4>
This will configure the image with the additional disks as specified in the cloud-init configuration file.