With a team of colleagues from enovance we are going to be this week-end (2/3 Feb 2013) in Brussels for Fosdem. Feel free to catch me if you want to have a chat about Swift or OpenStack in general. I will be wearing a enovance woodie/t-shirt. See you there!
Sometime you just need a long trans atlantic flight and a stupidly long stop-over in a random city to do some of those task that can improve your day to day but you never take some time to do it. When using emacs I wanted a simple way to launch a nosetests on the current function my cursor is in Emacs. The syntax on nosetests is a bit tricky and I actually always have to look at my shell history to know the proper syntax (nosetests directory/filename....
With the modular auth plugin system merged into python-novaclient it is now very easy to use nova CLI against the Rackspace Public Cloud powered by OpenStack. we even have a metapackage that would install all the needed bits. This should be easy as doing this : and all dependencies and extensions will be installed. To actually use the CLI you just need to specify the right arguments (or via env variable see nova –help) like this :...
Historically if you wanted to write software in python against OpenStack swift, people would have use the python-cloudfiles library or swift.common.client shipped with Swift. python-cloudfiles was made mostly for Rackspace CloudFiles before even Swift existed and does a lot of extra stuff not needed for OpenStack Swift (i.e: CDN). swift.common.client was designed for OpenStack Swift from the ground up but is included with Swift which made people having to download the full Swift repository if they wanted to use or tests against it....
A little note about swift3 the S3 emulation layer to OpenStack Swift As from this review we have removed it from Swift since the decision1 was made that only the official OpenStack API would be supported in Swift. The development will be continued in fujita’s repository on github at this URL : https://github.com/fujita/swift3 Feel free to grab the middle-ware or report issue from fujita’s repository. 1 Globally for OpenStack not just for Swift....
During the development for OpenStack Essex a lot of work has been done to make Swift working well with the other OpenStack components, this is a list of the work that has been done. MIDDLEWARE To make Swift behaving well in the ‘stack’ we had to get a rock solid keystone middleware and make sure most of the features provided by Swift would be supported by the middleware. The middleware is currently located in the keystone essex repository and was entirely rewritten from the Diablo release to allow support these Swift features :...
I have been trying lately to get a better understanding of the Swift code base, and I found the best way to know it was to read it from top to bottom and document it along the way. Here is some of my notes, hopefully more will come. I am starting with an object PUT when the request is coming from the proxy server. The request in the log-file will look like this :...
Swift integrity tools. There is quite a bit of tools shipped with Swift to ensure you have the right object on your cluster. At first there is the basic : swift-object-info It will take a swift object stored on the filesystem and print some infos about it, like this : swift@storage01:0/016/0b221bab535ac1b8f0d91e394f225016$ swift-object-info 1327991417.01411.data Path: /AUTH_root/foobar/file.txt Account: AUTH_root Container: foobar Object: file.txt Object hash: 0b221bab535ac1b8f0d91e394f225016 Ring locations: 192.168.254.12:6000 - /srv/node/sdb1/objects/0/016/0b221bab535ac1b8f0d91e394f225016/1327991417.01411.data Content-Type: text/plain...
[NB: Much things has changed since I have written this article but keeping it here for info] It seems that integrating Swift and Keystone together present some challenges to people and this is absolutely normal as there is a lot of changes going on. This is my attempt to document how everything is plugged together. I am not going to explain how a middleware is supposed to work as this is nicely documented on Wikipedia :...
I have done lately quite a bit of work with python-novaclient the (nova/keystone) openstack client. I often experiment it with ipython in the console. There is a nice debugging facility in novaclient which you can see while using –debug argument on the command line and if you wanted to use it with ipython you could have that at the beginning of your session : This would give you the details of the session showing you the REST requests and responses including the headers....