Use CachedAstakosClient in kamaki wrapper
Extend the allowed cloud name characters Allow the characters that kamaki allows
Remove all referencies to words like ~okeanos In the documentation and the printed messages, remove all references to ~okeanos, pithos or cyclades.
Comply with kamaki 0.9 * Change the authentication everywhere to use clouds (authentication URL and token pairs) * Add menu entries to manage clouds * Add an extra -a option in snf-image-creator to allow the user to specify authentication URLs
Code Cleanup * Prefix all private methods with _ * Write missing docstrings * Move all public methods above the private ones * Add module docstrings where missing * Define source code encodings on all modules
Share the md5sum and meta file if image is public If the image gets registered as public allow anyone to read the metadata and the md5sum file.
Check if remote files exist before uploading Before uploading to pithos, check if any remote file gets overwritten.
Support kamaki 0.8 In kamaki 0.8 `store' command is replaced with `file' and `astakos' is replaced with `user'.
Add missing docstrings
Clean-up the code using flake8
Support private images Support images that can only be deployed by the user that registers the image to cyclades
Use only the token to authenticate to synnefo You don't need the account name. You can fetch it from astakos using the authentication token.
Fix the import path for kamaki config module It has changed after the last major revision and was not updated.
Make snf-image-creator compatible with kamaki 0.6
Change kamaki account & token retrieval interface
Read ~okeanos account/token from kamaki If present in the kamaki configuration file, the user will read the ~okeanos credentials using the kamaki config interface. Whenever the user changes the ~okeanos credentians, the changes are pushed back to kamaki.
Fix pep8 errors Fixed many `E127 continuation line over-indented for visual indent' errors
In kamaki.register convert all metadata to strings Otherwise the registration may fail.
Don't handle kamaki exceptions in kamaki_wrapper Let the application decide what to do with them. If image-creator receives an error from kamaki it will terminate. But this may not be the proper thing to do for an interactive application like image-creator-dialog
Create a new output subpackage