History | View | Annotate | Download (73.2 kB)
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