Blogs

Since my prior post on Contributing to OpenStack, I liked the idea of using some automated tests to validate functionality and specifically, the corner cases that could arise when playing with the code. Most of the errors fixed so far on stampy, were related with some pieces of the code not properly handling UTF or some information returned, etc and still it has improved, the idea of ensuring that prior errors were not put back into the code when some other changes were performed, started to arise to be a priority. ...

Contributing to an OpenSource project might take some time at the beginning, the good thing with OpenStack is that there are lot of guides on how to start and collaborate. What I did is to look for a bug in the project tagged as low-hanging-fruit, this allows to browse a large list of bugs that are classified as easy, so they are the best place for new starters to get familiar with the workflow. ...

As always, I don’t usually find myself keen to write about things I do, until I later realize they might be helpful for others, and that’s why in the past I decided to switch the place I was putting the information about why did to Github and also, take benefit of practicing markdown for writing the entries. At that time, I moved my old blog posts to markdown to be used in conjunction with Jekyll and to use OctoPress as the engine rendering the contents into a static website. The setup and migration was not difficult, but still require to use some ruby, while I was more familiar with Python. ...

Since some time ago, email filter management was not scaling for me as I was using server-side filtering, I had to deal with the web-based interface which was missing some elements like drag&drop reordering of rules, cloning, etc. As I was already using offlineimap to sync from the remote mail server to my system into a maildir folder, I had almost all the elements I needed. After searching for several options imapfilter seemed to be a perfect fit, so I started with a small set of rules and start integration with my email process. ...

Since some time ago, I’ve been mostly dealing with OpenStack, requiring different releases to test for different tests, etc. Virtualization, as provided by KVM requires some CPU flags to get accelerated operations, vmx and svm depending on your processor architecture, but, of course, this is only provided on bare-metal. In order to get more flexibility at the expense of performance, nestedvt allows to expose those flags to the VM’s running at the hypervisor so you can run another level of VM’s inside those VM’s (this starts to sound like the movie Inception). ...