Skip to content
clalancette edited this page Nov 24, 2012 · 3 revisions

Table of Contents

NAME

oz-generate-icicle - tool to generate an ICICLE (package manifest) of a disk image

SYNOPSIS

oz-generate-icicle [OPTIONS] <tdl-file> <libvirt-xml-file>

DESCRIPTION

This is a tool to generate a package manifest (also called ICICLE) from a disk image. This program can be used as a counterpart to oz-install, though it does not have to be used in conjunction.

Note that oz-generate-icicle does the actual work using a combination of KVM and libvirt, so both of these must be available (and working) for oz-generate-icicle to have a chance to succeed.

OPTIONS

-c <config> Get the configuration from config file config, instead of the default /etc/oz/oz.cfg. If neither one exists, Oz will use sensible defaults. The config file is in standard ini format; for an explanation of the sections and keys, see the CONFIGURATION FILE section.

-d <loglevel> The log levels are:

  • 0 - errors only (this is the default)
  • 1 - errors and warnings
  • 2 - errors, warnings, and information
  • 3 - all messages
  • 4 - all messages, prepended with the level and classname
-h Print a short help message

-i <icicle> oz-generate-icicle will normally write the ICICLE XML to stdout. To have oz-generate-icicle write the ICICLE to a file instead, use the -i option.

CONFIGURATION FILE

The Oz configuration file is in standard INI format with several sections. If any section or configuration key is missing, Oz will use a sensible default. For true/false configuration keys, the values of true, True, Yes, or Yes can be used to turn the option on, and false, False, no, or No can be used to turn the behavior off. The configuration file should have the following form:

[paths]
output_dir = /var/lib/libvirt/images
data_dir = /var/lib/oz
screenshot_dir = .

[libvirt]
uri = qemu:///system
type = kvm
bridge_name = virbr0
cpus = 1
memory = 1024

[cache]
original_media = yes
modified_media = no
jeos = no

The paths section defines the paths that Oz will use for storing data. The output_dir key describes where to store the images after they are built, and the data_dir key describes where to cache install media and use temporary storage. Both locations must have a decent amount of free disk space in order for Oz to work properly. The screenshot_dir key describes where to store screenshots of failed installs.

The libvirt section allows some manipulation of how Oz uses libvirt. The uri key describes the libvirt URI to use to do the guest installation. The type key defines what type of virtualization to use. The bridge_name key defines which bridge Oz should place the guests that it launches on. The cpus key defines how many CPUs should be used inside the virtual machine. The memory key defines how much memory should be used inside the virtual machine.

The cache section allows some manipulation of how Oz caches data. The caching of data in Oz is a tradeoff between installation time and storage space. The original_media key tells Oz to cache the original installation media so that it does not have to download it the next time an install for the same operating system is requested. The modified_media key tells Oz to cache the oz-modified installation media so that it does not have to download and modify it the next time an install for the same operating system is requested. The jeos key tells Oz to cache the installed operating system after installation. This can significantly speed up subsequent installation of the same operating system, with the additional downside of the operating system getting out-of-date with respect to security updates. Use with care.

SEE ALSO

oz-install, oz-customize, oz-cleanup-cache

AUTHOR

Chris Lalancette <[email protected]>