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...
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
Refs: #3732
Update changelog, unittests for upload_from_string
Refs: #3608
Functional test and debug for upload_from_string
Implement upload_from_string
Implemented with threads
Optimize download_to_string by using threads
Implement download_to_string in pithos client
The download_to_string method downloads a remote object from pithos into astring, which is then returned.
Also, implemented unit and functional tests. Changelog is updated
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
Restore 2nd level command sysntax in shell
Refs: #3736
Cache container info request per upload session
Refs: #3735
Adjust pithos livetest to use container_info_cache
Refs: #3707
Update unitest to include container_info_cache
Refs: 3707
Add a container_infor_cache param to upload_object
Each upload involves a request that retrieves block size and hash information.In higher level applications, this request is redudant after the first upload.This feature allows higher level operations to cache retrieved container info...
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
Update livetest for upload return modification
Refs: #3656
Modify upload methods to return created obj info
Methods affected: upload_object upload_object_unchunked upload_object_by_manifestation
unittests modified accordingly
Implement purging a non-empty container
kamaki file purge <container> -F
will automatically empty a container before purging it
Refs: #3662
Implement livetest for image unregister
Refs: #3728
Expose image-unregister to cli and unittest it
Implement image unregister in kamaki.clients
Allow runtime args when invoking interactive shell
Refs: #3716
Behavior After This:kamaki -XXX -YY ... parses -XXX -YYIf not recognized: syntax errorIf recognized, group them into shell args (e.g. -h) and command args (e.g. -d)Whenever a command is run in this shell instance, apply the command args...
Raise a descriptive error for misconfigured cmds
Refs: #3663
A command group that is declared in the config file is not supportedby valid command specification code or the specification code is notpointed at by <command>.cli configure variable
Log initial call arguments in first log
Merge branch 'feature-logging' into develop
Move logger module to kamaki.cli
Make kamaki.clients unware of kamaki.logger
use logging for getting the loggers
Stop shell from destroying config instance
This caused warnings about preset variables
Update Changelog to reflect #3715 changes
Allow activation/deactivation of specific loggers
refs: #3715Logger settings are not aborted and will be restored at deactivation
Also, remove all logger creation functionality from kamaki.clientsA file or stream logger should be created an the kamaki.clients caller side...
Remove log redaduncy when logging in a file
Use < and > in stream logger for send/recv resp.
Globalize logger usage
Unsolved bug: redudant info in logfile
Wipe logger add_file_logger
Fix typo in _create_or_get_missing_hashes call
Honour if_(none_)match even if all blocks are up
Refs: bug #3708
Expand logger to support stream logging, simplify
Adjust expected values in fanctional client tests
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"
Move addproperty from image to image compute
Fix typo with --config and --property args (#3658)
Connect request-response threads in logs
The connection between kamaki request attempt and httplib response waslogged, but the connection between httplib response and kamaki responsemanagment was not logged.
Remove extra logging options
One default: ~/.kamaki.logUser can use a custom: kamaki config set log_file <custom log file>
Fix mispeled import cyclades_cli --> cyclades
Set ~/.kamaki.log with mode 0600 as default
Refs: #3610
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
Merge branch 'feature-store' into develop
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
Update docs to use the term Synnefo where needed
In some cases, the term 'GRNET development team' was replaced with 'Synnefo' or'Synnefo development team'
Add some parameters to storage.list_object
:param limit: (int) The amount of results requested
:param marker: (str) Return containers with name lexicographically after marker
:param prefix: (str) Return objects starting with prefix
:param format: (str) reply format can be json or xml (default:json)...
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.
Set a default network type when creating nets
Default type is MAX_FILTERED
Support #3514
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....
Fix astakos client functional test
Use 'user.token' instead of 'astakos.token'
Remove quotaholder from kamaki
This affects the cli:- remove the quotaholder commands set- remove the commissioning system (automatic command retrieval)
This affevts the clients:- remove the quotaholder client- remove the clients commissioning system...
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
Rename store command group to file
Rename command group astakos to user
The client is still called 'astakos', but the command group is now 'user'
Add if-etag-match to pithos client upload
Add option to fail upload if remote file exists
The if-none-match header option with '*' is used in that case.This is exposed as 'if_not_exist' in PithosClient.upload_object
Feature #3574
Update documentation for logger changes
Pametrize log file, make it globaly available
Kamaki logger module is now available to both cli and clients packagesUsers may set the log_file option in configuration file kamaki config set log_file ...
Support #3441
Return image details as headers, in image register
Feature #3512
Increase timeout in upload thread canceling
Make download canceling more responsive
This does not make download canceling faster, if anything, it makes it slowerbut probably more gracefull for end users. Instead of just waiting the threadsto finish, users now see messages that descibe the attempts made by kamaki to...
Make --public and --sharing to work in upload
Bug #3509
Fix typo in commands.errors (self-->this)
This typo caused undesired behavior when deleting a deleted network
Bug #3547
Allow users to set maximum thread limit
This is implemented as a configuration option in cliDevelopers may set it as kamaki.clients.Client.MAX_THREADS = <limit>
Adjust documentation acoordingly
Feature #3546
Stop create_server from crushing by a faulty image
If the image is missing the (os, users) metadata, the create_server methodused to crush anexpectingly
Add a NL to logs to make them more readable
Fix typo in using download progress bar
Minimize requeests whn dnlding same block
If a file has multiple same blocks, download one of them and copy it to localfile locations
fixbug 3555: blcks missing if same to other blcks
Create a livetest that catches bug #3555
A boring file is a file with at least two same blocksKamaki fails to download more than 1 same blocks, therefore the downloadedfile is corruptedThis test fixes the bug
DISABLE config log options in interactive shell
to avoid kamaki failures due to logging problems
Allow config to switch some options on or off
- 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
Fix typos in logging mechanism
Move http response logging to ResponseManager
Move http request logging to RequestManager
Wip kamaki.clients.test.py
Unittest ResponseManager
Unittest kamaki.clients.RequestManager
Redesign http connection module
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...