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.

If an exception that we don't know how to handle gets thrown, make sure
the traceback is always printed in the command line. If the output of
the program is also saved in a log file, then make sure the traceback
gets printed there too.

If a dialog widget exits in an abnormal way, we may end up having a
messed up terminal. Make sure that the terminal attributes are always
restored before the dialog-based version on snf-image-creator
terminates.

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.

Works better this way in OpenSUSE

 * 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.

If the ostype returned by libguestfs is valid and distro in unknown,
don't print the distro at all.

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.

The cow file when creating images or the temporary image file when
bundling the host system may be large. Allow the user to overwrite
the directory under which those files get created.

Make sure the user cannot select a directory as input media

This can be used to create an image out of a live system. This
functionality is not yet implemented.

This reverts commit 883e57b0.
Drop the greenlet support.

Needed by new kamaki, otherwise it throughs an exception at the end.

Create a new dialog_menu module to host all the "expert mode" code.
Check the code with a new version of pep8

Fix various typos in messages, add .gitignore file for
automatically produced intermediate files.

Every time you tried to reupload an image, the dialog displayed the
pithos url instead of the image filename as initial value.

The account info was saved in the token field in .kamakirc

Fix some typos and overwrite the yes/no labels of the wizard/expert
mode yesno dialog

Also move it to a separate module.

Logging can be enabled using the -l input option

A user can now create and upload an image using the wizard

The system does not perform anything yet when in wizard mode.

Create the new python module to host the aforementioned code.

If present in the kamaki configuration file, the user will read
the ~okeanos credentials using the kamaki config interface.
Whenever the user changes the ~okeanos credentians, the changes are
pushed back to kamaki.

Not fully implemented yet

Fixed many `E127 continuation line over-indented for visual indent'
errors

Before extracting an image or registring it with cyclades, the image
properties are populated with metadata concerning excluded deployment
tasks.