GitLab

Also, fix typos and default values for service configurations

Refs: #3874

Kamaki.clients.astakos.AstakosClient is now a high-level client lib that
offers access to token-authenticated astakos-aquired cached information.
Users who need an astakos client should use the snf-astakosclient instead.

Usage:

 astakos_cache = AstakosClient(<astakos/base/url/with/identity/api>)
 astakos_cache.authenticate(<token>)
 user_info = astakos_cache.user_info()
 compute_endpoints = astakos_cache.get_service_endpoints('compute', 'v2')

Major changes:

Modify ReST call from /im/authenticate to /tokens

New methods as AstakosClient instance cache accessors:
 get_services
 get_service_details
 get_service_endpoints

Method renaiming for existing AstakosClient instance cache accessors:
 info --> user_info
 user --> list_users

Refs: #3732

use logging for getting the loggers

refs: #3715
Logger settings are not aborted and will be restored at deactivation

Also, remove all logger creation functionality from kamaki.clients
A file or stream logger should be created an the kamaki.clients caller side
In this case, the caller is kamaki.cli
Kamaki.cli should handle where and how the loggers will output. Kamaki.clients
will log as __name__ and the two extras: kamaki.clients.send/recv

An external app can now import kamaki and create a logger named "kamaki" and
this will log whatever kamaki is logging. The external app will handle loggers
as they wish.

Unsolved bug: redudant info in logfile

The connection between kamaki request attempt and httplib response was
logged, but the connection between httplib response and kamaki response
managment was not logged.

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

- 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

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

Tests are packaged as kamaki.clients.test
As an example, the astakos authenticate method test has been implemented

This bug was produced after changes in path4url, where a trailing / is now
always removed

This bug was produced after changes in path4url, where a trailing / is now
always removed

Conflicts:

	kamaki/clients/utils.py
	version

Replace calls of the form unicode(v) to the equivalent" '%s' % v

Replace calls of the form unicode(v) to the equivalent" '%s' % v

kamaki.clients.connection.HTTPConnection/Response abstract class are renamed
to kamaki.clients.connection.KamakiConnection/Response to avoid confusion w.
httplib.HTTPConnection/Response classes