GitLab

Refs: #4058

Refs: #4059

Also, adjust corresponding unit and functional tests

Refs: #4059

Refs: #4203

Refs: #4196

Refs: Bug #4134

Refs: #4058

Refs: #3934

Refs:#3934

Refs: #3954

Refs: #3934

Refs: #3934

Breaks compatibility, implements a remotes-based config file

Compatible with kamaki config files v2

user.url, file.url, compute.url and image.url
are now valid and of higher priority to
astakos.url, pithos.url, cyclades.url, plankton.url
which are also valid

All these are ignored iff [global].auth_url is given

Also, fix typos and default values for service configurations

Refs: #3874

Let cross-service initializations to use explicit service endpoint urls if
there is no single authentication url.
- In Image commands, there are calls that use astakos and pithos clients
- In pithos there are calls that use astakos client

Refs: #3874

In current configuration, kamaki checks for auth_url. If that fails,
it raises an error. If it is not set, it prints a warning and attempts
to read the <service>.url option from the configuration file.

Service urls: astakos.url, pithos.url, cyclades.url, plankton.url

Refs: #3874

Use kamaki.clients.astakos.AstakosClient as a cached astakos client to get
user information and, most importantly, endpoints. Allow users to authenticate
multiple tokens on the same session. In every session there must be at most
one authentication per user/token.

Major change: top kamaki.cli.commands class now contains a base_auth field
with the cached authenticating client. All urls are drained from this field.

Refs: #3732

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

Apply the feature wherever is applicable
Generalize the feature by moving the corresponding code to _command_init

Refs: #3756 #3732

 - Add optional output for file methods: mkdir, touch, create, move, create,
    copy, move, append, delete, purge, info, meta, upload
 - Transliterate permissions and metadata methods to apear as get/set/delete
    command subgroups
    e.g. kamaki file metadata set ...
    instead of
    kamaki file setmeta
- Add method create_container to pithos client, add unit and functional tests

Also, kamaki.clients.pithos.copy/move_object returns response headers

Refs: #3756 #3732

Refs: #3756 #3732

In kamaki.clients
-------------------
- storage.create_directory returns response headers
- implement pithos.create_container

In kamaki.cli.pithos
-------------------
- add flag --with_output for optional output
- add (-j, --json) flag for optional json-formated output
- apply these changes to file_mkdir, file_touch, file_create

- Implement a print_json auxiliary method in kamaki.cli.utils
- Add a (-j, --json) flag to file list
- When -j or --json flag is on, only json is printed

Refs: #3732

 Also disallow moving deleted objects by version The later was implemented by
accident, due to the symetry between move and copy

Refs: #3737

Refs: 3737

Refs: #3739

Refs: #3735

If the upload is successfull, if the -l or --details argument is present,
kamaki lists all uploaded objects with all details returned by the server
(e.g. object version, date of creation, etc)

Refs: #3730

kamaki file purge <container> -F

will automatically empty a container before purging it

Refs: #3662

Unsolved bug: redudant info in logfile

containerlimit set -h will tell users to use 0 for unlimited
containerlimit get will print "unlimited" if received a 0 value

Container limit 0 means "unlimited"