GitLab

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 does not make download canceling faster, if anything, it makes it slower
but probably more gracefull for end users. Instead of just waiting the threads
to finish, users now see messages that descibe the attempts made by kamaki to
cancel them. Each cancelation gets a timeout of 0.5 seconds, so that users
will not wait too long (although they might wait more overall)

Bug #3457

Bug #3509

This typo caused undesired behavior when deleting a deleted network

Bug #3547

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

WAS: kamaki set token ....
NOW: kamaki config set token ...

If the image is missing the (os, users) metadata, the create_server method
used to crush anexpectingly

If a file has multiple same blocks, download one of them and copy it to local
file locations

A boring file is a file with at least two same blocks
Kamaki fails to download more than 1 same blocks, therefore the downloaded
file is corrupted
This test fixes the bug

to avoid kamaki failures due to logging problems

- 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

Missing config: at setup, in the first example (Quick Setup) it was
kamaki set ...
while it should have been
kamaki config set

Merge everything to kamaki.clients

Remove multiple hierarchies of connection classes (== abandon support for
    alternative connection methods, e.g. for requests from pypi)

New connection classes are
- RequestManager
- ResponseManager
Semantics:
    RequestManager constructor commits a request without performing it
      but it performs all sanity checks for url, path, method and params
    RequestManager.perform will perform the commited request, if called
    ResponseManager constructor needs a RequestManager instance
    ResponseManager.(various properties)
        request is pooled from a ContextManagerPool (objpool) when needed.
        Results are cached and used as long as the ResponseManager instance
        is alive

Remove KamakiConnection/ResponseErrors, use ClientError wrapers for everything

Remove the connection livetest

TODO: Adjust unittests