Week in OpenStack I

This week marks my inaugural ‘Week in OpenStack’ blog series. Every week, I’ll review the things that I’m working on inside the OpenStack community, as mentioned in my previous post. With that, here are the activities for the week:


As I mentioned in my goals for Mitaka post, I’d like to contribute to the SaltStack effort to produce modules for deploying OpenStack. After talking with Nitin Madhok regarding the progress of the work completed thus far, I decided to simply ‘dive-in’ and help out. I don’t know much about Salt to date, but understanding configuration management in a general sense helps me to pick up the concepts in Salt fairly quickly. The first ‘win’ was getting a ridiculously simple commit merged into the saltopenstack project- adding vagrant to the .gitignore. I’ve learned that using vagrant is quite valuable in developing automation code, so my plan is to get the saltopenstack project locally deployable. That way, we have a way to test things out locally prior to submitting PRs for inclusion.

Continuing my work with SaltStack, I took it upon myself to be proactive and create the #openstack-salt IRC channel. I think that communicating with other SaltStackers is a problem we want to solve early- especially when it comes to hacking on Salt on behalf of the OpenStack community. It’s empty at the moment, but it’s worth camping out there to await the calvary.

##Puppetizing Zaqar

Caught up with the zaqarians (a term of endearment used to refer to fellow zaqar teammembers) this week. I hadn’t the chance to speak with them since the summit in Tokyo. I informed them that I’m in the process of finishing up the puppetization of the zaqar module. Right now, I’m working on getting the module to deploy the zaqar service atop Debian. I’m able to use vagrant to my advantage here as well, ensuring clean installs with each new inclusion of puppet code.

##OpenStack Mobile iOS

For the OpenStack Mobile iOS project, I’m continuing to brainstorm (along with others) around the idea of reviving this project. There was some conversation about leveraging Apache Cordova in hopes of having one codebase that supports multiple mobile platforms, but that entails writing the app using webdev (HTML, CSS, JS) technologies. It remains to be seen which way we go on this, but I think I’ll have to eventually make a strong case on why we should go with a native iOS app. I certainly reside in the camp that sees value in a native app, however, if the collective is stronger on doing this the Cordova way, then majority rules.


This week (like many others) was busy. There’s more to accomplish, such as continuing to read through the Horizon documentation to further familiarize myself with the code, continuing to add to the feature list for the OpenStack Mobile iOS project (not to mention the continuation of learning Swift), and pumping out more puppet code. Well, did you find this useful? Boring? Exciting? Comments are welcome.

Jason T Clark

Jason T Clark

Father. Musician. Gamer. Coder.

comments powered by Disqus
rss facebook twitter github youtube mail spotify instagram linkedin