History | View | Annotate | Download (23.7 kB)
Handle url proccessing even if url is unicode
Also, fix typos and default values for service configurations
Apply servce.url options to cross-sercice calls
Refs: #3874
Let cross-service initializations to use explicit service endpoint urls ifthere 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
Use explicitely set services urls if no auth_url
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 attemptsto read the <service>.url option from the configuration file....
Implement --cloud arg to switch between clouds
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:...
Get endpoint urls for all CLI operations
Use kamaki.clients.astakos.AstakosClient as a cached astakos client to getuser information and, most importantly, endpoints. Allow users to authenticatemultiple tokens on the same session. In every session there must be at most...
Rename meta-->metadata and remove values @CLI
Refs: #3633
Add metadata management to image register
- 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...
Merge branch 'feature-json-output' into develop
Conflicts: Changelog kamaki/cli/commands/image.py
Also, take care of pep8 issues
Implement an optional json output 4 outputing cmds
Refs: #3732
Update and enrich error messages in image register
Parse ivalid property file and guide users to correct itGuide users to pass valid container:path parameters
Refs:#3769
Print full and nice response in image register
Make sure registered properties are unique
Refs: #3769
Store image properties after image registration
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...
Optionaly load images properties from file
Update documentation to reflect changes in output
Refs: #3756
Apply option outputs to image commands + renames
- 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 enumeration as optional for all list cmds
Refs: #3739
Expose image-unregister to cli and unittest it
Move addproperty from image to image compute
Fix typo with --config and --property args (#3658)
Fix mispeled import cyclades_cli --> cyclades
Add some client-side filters to image list
--owner=<uuid> : print only images with given owner
--name-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>...
Filter image listing results by owner
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 aclient side filtering, as oposed to the other filters of the command.
Apply uniform descriptions to all client commands
<GRNET name>/<OS name> API <actuall api> commands
e.g. Cyclades/Compute API server commandsor Pithos+/Storage API commands
Commands file names are named after the API they implement, not the command interface....
Update docs, rename kamaki.cli.commands/*
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