GitLab

Refs: #4058

Refs: #4114

E.g. the cyclades spec package contains the non-optional group "server" and
the optional group "floatingip". Now kamaki can load only the "server"
group, except if the user requests the loading of "floatingip" group too.

Refs: 3632

Refs: #3632

Refs: #3867

- configuration section, with clouds
- Simple listing
- Pithos advanced listing

Refs: #3978

Refs: #3979

Refs: #3934 #3979

Refs: #3934

This commit server as a backup mostly, since the adjustments are not yet
applied to docs/commands and all docs/developers kamaki guides.

Refs: #3934

config set remote.smth.option value
  inserts option=value in remote smth
config get remote.smth
  lists the contents (key=val) of remote smth
config delete remote.smth.option
  deletes this specific option from the remote smth
config delete remote.smth
  completely erased the remote smth

Refs: #3934

Refs: #3934

In Config:

Simplify guess_version heuristics (check if the following exist:
    global.url/token, remote-defaults)
Trasnlate files 'remote "name"' to 3-level dict and back
Implement rescue_old_file to convert config files to v3.0

In kamaki.cli:

Implement method _check_config_version

Refs: #3934

rescue_old_file: mines info from old config file to use them in new file
translates:
  remote "smth" --> 'remote': {'smth': ...
  global.{url, token} --> remote.default.{url, token}
  <command>.cli --> global.command_cli
  some commands are maped to other names, e.g. pithos --> file
  <command>.url --> remote.defailt.<command>_url

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: #3913

Config file can (optionaly) contain:

[remotes]
 example = https://www.example.org/astakos/identity/v2.0/
 old_version = https://www.example.org/astakos/identity/v1.0/
 ...

Now, user can explicitely request for a remote cloud authentication URI:

kamaki --cloud=<remote>

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: #3663

A command group that is declared in the config file is not supported
by valid command specification code or the specification code is not
pointed at by <command>.cli configure variable

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

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