History | View | Annotate | Download (78.1 kB)
Show user names in /file sharers
Refs: #4203
Correct error message if file does not exist
Fix typos, decale kamai.cli.argument as package
Guess mimetype and use it in uploads
Refs: #4196
Ignore subdir section in file_list
Refs: Bug #4134
Fully test argument.Argument
Refs: #4058
Update the copyright dates everywhere
Fix deprecated terms in documentation
Prepare special local paths (like .) for pithos
Fix all minor typos and modifications in tests
Change term "remote" to "cloud" when proper
Refs: #3934
Merge branch 'feature-endpoints' into develop
Adjust help messages to configuration changes
Refs:#3934
Use os-specific path seperators in up/down-load -R
Refs: #3954
Adjust all command specs to multicloud/singleauth
A. Hardcode the new kamaki config file
Breaks compatibility, implements a remotes-based config file
Backwards compatibility for configuraiton file
Compatible with kamaki config files v2
user.url, file.url, compute.url and image.urlare now valid and of higher priority toastakos.url, pithos.url, cyclades.url, plankton.urlwhich are also valid
All these are ignored iff [global].auth_url is given
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....
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...
Merge branch 'feature-json-output' into develop
Conflicts: Changelog kamaki/cli/commands/image.py
Also, take care of pep8 issues
Fix typo in pithos upload output
Implement an optional json output 4 outputing cmds
Refs: #3732
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...
Apply optional output to kamaki file commands
Apply the feature wherever is applicableGeneralize the feature by moving the corresponding code to _command_init
Update file operations and their output
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...
Add output to file copy/move
Also, kamaki.clients.pithos.copy/move_object returns response headers
Add output support to create methods
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 json formated output for file list
- 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
Allow copy of deleted objects by refering to older
Also disallow moving deleted objects by version The later was implemented byaccident, due to the symetry between move and copy
Refs: #3737
Fix typo dst_path instead of ds_path
Refs: 3737
Add enumeration as optional for all list cmds
Refs: #3739
Cache container info request per upload session
Refs: #3735
Add a -l option to upload: list uploaded details
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
Implement purging a non-empty container
kamaki file purge <container> -F
will automatically empty a container before purging it
Refs: #3662
Globalize logger usage
Unsolved bug: redudant info in logfile
Make containerlimit set/get aware of 0==unlimited
containerlimit set -h will tell users to use 0 for unlimitedcontainerlimit get will print "unlimited" if received a 0 value
Alow uploading to container with limit 0
Container limit 0 means "unlimited"
Make recursive upload non-default, rearange checks
Alloow recursive upload with RRearange pre-upload checks as shown bellow: check first if it is recursive & direcory- check if object exists or forced to overwrite- check container limit and used size...
Take into account container used bytes in upload
Before uploading, check if there is enough remaining space on containerremaning space = container limit - container used bytes
Prevent upload if uploads exceed container limit
Feature #3536
Implement a recursive upload
kamaki file upload <directory> <container>[:remote-dir]
where remote-dir either is a dir or does not exist
Split file-quota semantics for account and contner
kamaki file quota --> only for accountkamaki file quota <container> --> kamaki file containerlimit get [container]
Support #3541
Rename file setquota to file containerlimit set
Also, do not allow user to set account quota
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