GitLab

- validate image metadata format
- read metadata from file
- merge file-loaded metadata with runtimes
- store metadata file on pithos, check existance, overwrite with -f
- raise helpful error messages when there fail

Refs: #3797

Refs: #3732

Parse ivalid property file and guide users to correct it
Guide users to pass valid container:path parameters

Refs:#3769

Refs: #3769

Log of changes:
- Properties are stored in a remote file on Pithos+
- File name is <image-file>.meta
- Feature can be switched off with --no-property-file-upload
- If remote property file exists, registration is aborted
- If remote property file exists, force with -f, --fforce-upload-property-file
- Location is given as container:path
- User id can be aquired internaly with an astakos call

Refs: #3769, #3778

Refs: #3769

Refs: #3756

- Add image.add_member missing content-length header
- Rename image-[add|del]member commands to members-[add|delete]
- Remove update option from image-register
- In image-compute split properties to properties-list and properties-get
- Add optional output to methods
 * image: unregister, members add/delete/set
 * image compute: delete, properties delete
- Transliterate methods to list-get-set-delete command groups:
 * image: members, member
 * image compute: properties

Refs :#3756 #3732

Refs: #3739

--owner=<uuid> :  print only images with given owner

--name-prefix=<prefix>  :  print only images with name starting with <prefix>
--name-suffix=<suffix>  :  print only images with name starting with <suffix>
--name-like=<part>      :  print only images with name containing <part>

Feature #3513

Introduce the --owner parameter to kamaki image list (was: image public)
If given, only images of given owner will be pronted on console. This is a
client side filtering, as oposed to the other filters of the command.

<GRNET name>/<OS name> API <actuall api> commands

e.g.
  Cyclades/Compute API server commands
or
  Pithos+/Storage API commands

Commands file names are named after the API they implement, not the command interface.
It cyclades, astakos, pithos, etc. instead of server, user, file, although the command
names they expose are "server *", "user *", "file *", etc.

Cyclades is a pretty good example: it exposes a set of commands with different prefixes
(server, network, flavor) and they all use the cyclades client.

Documentation updates: reflect the changes in command groups
    astakos --> user, store --> file

File renaming: remove the _cli suffix from modules in kamaki.cli.commands

Feature #3566

Feature #3566

Kamaki logger module is now available to both cli and clients packages
Users may set the log_file option in configuration file
   kamaki config set log_file ...

Support #3441

Feature #3512

This is implemented as a configuration option in cli
Developers may set it as kamaki.clients.Client.MAX_THREADS = <limit>

Adjust documentation acoordingly

Feature #3546

- LOG_TOKEN: whether to log user token in http requests (default: off)
- LOG_DATA: whether to log http body (send or secv - default: off)

config options: log_token=off, log_data=off

- image compute group contains all Compute Image API commands, as oposed to
Plankton API commands.

- definition of a kamaki cli command slightly changed: a command with
subcommands can have a class without being a command itself, as long as it has
subcommands! Thus a subcommand group can be defined with docs and everything.

- image public is not image list (docs not updated yet)

New method: cli.utils.page_hold holds console until user input, usefull for listing
results