The base class is named Output. Having a method with the same makes
the code confusing.

This can be used to define scripts to run on the guest media after
mounting it under a directory in the host.

This resolves #13, resolves #14 and resolves #15

This option can be used to display the detected metadata of an image.

Order the arguments alphabetically.

Use qemu-nbd to export a QEMU image as raw where needed

This used to be a class in the util module, but since this is only used
on the Image, it suits better there.

This can be used to act on the original media instead of a device-mapper
snapshot.

This resolves #10

There is no need to associate a loop device with the input media if we
are not snapshotting the input media. The loop device is only needed in
order to use the media with the device-mapper.

Don't treat shrink as a seperated task. Add it in the syspreps menu.

If this is enabled, the program will try to install the specified VirtIO
drivers to the image.

Fix a bug where "$s" instead of "%s" was used in a string as a
placeholder.

This fixes #17

This attribute hosts the block device associated with this Disk
instance. This can be the original media if the source media is a block
device, a loop device of the original media if the original media is a
regular file or a loop device of a temporary object if the original
media is a directory.

Rewrite the mechanism to have better control on the system preparation
parameters. Also change the way the parameters are updated in the UI.

According to the decision of the GRNET Board of Directors,
switch license to GPLv3.

This commit will be propagated to the release
and master branches based on git flow, and the next
release will be licensed as GPLv3.

Remove the warning about having swapped the names of the snf-mkimage and
snf-image-creator executables. Keeping this warning for one major release
was enough.

Make snf-image-creator be the dialog-based program and snf-mkimage be
the command line one.

This can be used to perform various tests to determine if the media
is supported.

Add a new "Unsupported" os_type class. Images that get created from
unsupported media have the EXCLUDE_ALL_TASKS property enabled.

--print-sysprep should be --print-syspreps

The user may define parameters needed by the os_type classes to perform
the system preparation tasks.

A new needed_sysprep_params method is added to os_type.OSBase that
returns a list with parameters that should be defined by the user.

In the documentation and the printed messages, remove all references
to ~okeanos, pithos or cyclades.

When registring an image, use the information returned by the
kamaki register method to construct the metadata file.

When dumping the image to the local filesystem, store the image
properties and the disk-format info in the metadata file.

This options can be used to get the authentication URL and token
from a saved cloud section in the kamaki configuration file

 * Change the authentication everywhere to use clouds
   (authentication URL and token pairs)
 * Add menu entries to manage clouds
 * Add an extra -a option in snf-image-creator to allow the user to
   specify authentication URLs

 * Prefix all private methods with _
 * Write missing docstrings
 * Move all public methods above the private ones
 * Add module docstrings where missing
 * Define source code encodings on all modules

If the image gets registered as public allow anyone to read the
metadata and the md5sum file.

Before uploading to pithos, check if any remote file gets
overwritten.

Check if the filesystem is mounted read-write before you execute
the do_sysprep function

Rename DiskDevice class to Image and move it to a seperate module.
Also, don't let the user access the os_type/* modules directly. In
Image class create the `os' member variable that will host an
appropriate instance of one of the OSBase classes.

Support images that can only be deployed by the user that registers
the image to cyclades