If you attended OpenStack Summit Tokyo , then you probably remember the koi pond at the Japanese garden in the middle of the hotels. Everyday of OpenStack Summit Tokyo, as you walked back and forth between the hotels attending various sessions, you’d have to catch a glimpse of the pond. Quite impressive. Much better than the little holes in the ground back home with 6 fish in it. If you didn’t here’s what it looked like:
Plenty of fish, all swimming about, each with its own purpose for the day. See the little one in the back? That’s me. Small fish, in a big pond. That’s how I felt attending my first OpenStack Summit in Tokyo Japan. It was my first OpenStack Summit, and my first trip abroad. Fresh off the plane, here are my thoughts on how a small fish (like me) plans to approach this next OpenStack release cycle:
Continue working on a fully featured version of the puppet-zaqar module
Not only is the zaqar team continuing to iterate on the development of the project, the team is also ‘lobbying’ for the integration of zaqar with other major projects. IMHO, the goal of completing the puppet module for zaqar solidifies the project’s maturity level by offering OS operators a means of automating the deployment of the service.
2) Automate all the things!
Configuration Management and deployment automation is my strong suit. My goal around this is to continue submitting bug fixes, implementing features, supporting releases, and conducting plenty of reviews on all things automation.
+SaltStack - The Tokyo Summit presentation on deploying OpenStack with Salt by Nitin Madhok of Clemson University was intriguing. I’ve yet to use Salt, so I’d like to get my hands dirty and contribute to this effort as well.
3) Revive the OpenStack iOS client project
This goal is by far the most ambitious. First, I think that my lightning talk on was well received. Since chatting with Chris Jones about the effort, he and I have been brainstorming on strategies to reignite the project. Soon, a kickoff email will be sent to the -dev list, and hopefully we’ll get a chance to join forces with others who still think that this is a worthy cause.
One theory that I have is to contribute to the Horizon team (and possibly the API-wg). The mobile client is essentially a dashboard alternative, so I’m thinking that studying the underlying code while making contributions to the Horizon project could help ‘give us a clue’ as to how we design/develop the mobile project.
With that, here goes- I’ve blogged a lot about individual progress in the past, but this time you’ll get a chance to see what it is I do from a professional perspective. Let’s see how a ‘Week in OpenStack’ weekly review blog post goes over.
To the interwebs!