I am lucky to sit in front of Julien Danjou at work and as the sole Emacs users on the side of our office it was come to our attention that we needed as emacsian to unite ourselves to preach the good parole of the church of Emacs and sexy mens. It was quite obvious that the only way to convince those in the unkown was to find an excuse for drinks good food between good people and set-up a meetup. ...

My day to day being work or personal is to create OpenSource code. As an habit I have taken lately I am adding licenses to all new files I am creating. I have historically used the `auto-insert-mode with a default template. For example for my newly created python files I would have this for configration : ;AutoInsert (auto-insert-mode 't) (setq auto-insert-alist '((python-mode . "python.py"))) and in my `auto-insert-directory directory there would be a python.py template with my license files. ...

We have all been there, we are committing a two character change in a project and send our review all happy and dandy with the review tool full of hope that our change is rock solid : You now that a two character change cannot fail. This is a tiny change in some arcane part of the Swift code that can never get passed by the tests launched in Jenkins and should just be a straightforward commit. ...

I spent too much time trying to figure out how to use the latest swiftclient/novaclient with Rackspace Cloud that I thought I would have to document it somewhere to avoid the pain for others. Assuming you don’t want to use pyrax and no OS_AUTH_SYSTEM plugin but just pure OpenStack python-novaclient/swiftclient on Rackspace cloud then you just need to export those variables in your shell : export OS_REGION_NAME=ORD export OS_USERNAME=username export OS_TENANT_NAME=" " export OS_PASSWORD=password export OS_AUTH_URL=https://identity.api.rackspacecloud.com/v2.0/ so now the region is ORD here (Chicago) but this can be SYD/IAD/DFW or whatever new datacenter/region from Rackspace. If you wanted to use the UK region you would need another username/password which is tighted to the LON datacenter (yes that’s an another legacy weirdness). ...

curl is obviously an extremely popular way to experiment a REST API. Unfortunately one of its shortcoming is not able to remove a custom header but just to modify or add it. In swift if you prefix your Meta header with X-remove it would then just do that and remove the header. For example when I wanted to remove the account quota header from an account with a reseller admin token I had just to do that : ...

It is easy to launch the swift functional tests with v2 auth (Keystone). Assuming you have a recent version of python-swiftclient, python-keystoneclient and swift you need to first add a few users which is easily done with this script : Assuming you have already your OS_* variables configured with an admin, you can just launch it and it will : add a tenant/user named test/tester. add a tenant/user name test2/tester2. add a user tester3 belonging to test2 but not operator on that tenant. and it will create a /etc/swift/swift.conf for testing. You can adjust the keystone host in auth_host there (default to 127.0.0.1) ...

PKI tokens has been implemented in keystone by [Adam Young][1] and others and was shipped for the OpenStack grizlly release. It is available since the version 2.0 API of keystone. PKI is a beautiful acronym to [Public-key infrastructure][2] which according to wikipedia defines it like this : Public-key cryptography is a cryptographic technique that enables users to securely communicate on an insecure public network, and reliably verify the identity of a user via digital signatures. ...

This is something I have been asked and I was at first under impression it was only available in v3, digging a bit more into the code there is actually a way to do that in v2 when you are using PKI tokens. Since I could not find much documentation online here is a description of the steps how to do it. Let first get a PKI token, you can do it the hard way by sending a json blob to the keystone url and parse the json results like this : ...

How I feel when I try to address all pylint warning/errors: Adapted from http://devopsreactions.tumblr.com/post/47690154351/trying-to-code-to-w3c-standards

There is two new nifty middlewares for doing quotas in upcoming Swift release 1.8.0 called container_quotas and account_quotas. Those are two different middlewares because they are actually addressing different use cases. container_quotas is typically used by end users the use case here is to let user to specify a limit on one of their container. Why would you want to restrict yourself you may ask ? This is because when you allow a public upload to a container for example with tempurl or/and formpost you want to make sure people are not uploading a unlimited amount of datas. ...