Developer, and current lead for Cinder project
John Griffith, Senior Software Engineer at SolidFire, helped to create the Cinder project in OpenStack. His primary responsibility at SolidFire is technical contributor to OpenStack, and he currently aslo serves as elected Project Lead for Cinder and holds an elected seat on the OpenStack Technical Committee.
John has over fifteen years of engineering experience in both hardware and software engineering. He’s been an active user and contributor to open source for close to a decade, and has been focused on OpenStack since January of 2011.
In addition to his technical contributions, John also spends a lot of his time talking to people who are interested in learning about OpenStack as well as gathering feedback from current users.
I'm involved in the following OpenStack projects: Nova,Cinder,DevStack
I actually started looking at OpenStack in my “free-time” outside of work. I stumbled across OpenStack and decided it was something I wanted to work on full time. In October of 2011 I was hired in to fill an OpenStack development role.
The success of OpenStack is of course important to me for all of the reasons most people give; open source cloud platform, technical strengths and capabilities etc. But really one of the things that the success of OpenStack means to me is that it shows how open source can actually work and in some cases work better than the alternatives. OpenStack is the only project of it’s kind, where competing vendors actually all freely and openly collaborate to make something better for everyone. The success of OpenStack not only has the potential to change cloud computing but it also has the potential to do much more than that.
Contribution success can become a very big topic... I would say from a technical perspective my help in driving and launching the Cinder project was certainly a highlight. In addition to technical/code contributions I’m also extremely proud of my contributions in other areas, including bringing new vendors in to the project and helping them get started as well as public speaking events promoting OpenStack and educating newcomers who are interested. I really enjoy being an evangelist, and I think that is a very significant contribution even if it’s difficult to measure success.
I’ve volunteered for a number of nonprofits over the years. While I haven’t served in a role as board member, I have been very active in organization, management and day to day operations for a ranch that helps kids with disabilities. While the mission statements and purpose of other non profits I’ve been involved with is significantly different, all non profits I’ve been involved with seem to have the same challenges. It seems regardless of your goal funding, community involvement and long term vision are all key. My background in open source software, as well as experience in other community driven projects has given me valuable experience in working together with people of diverse and differing opinions but still working together to achieve a common goal.
I believe the Board has an enormous responsibility. Investment and funding from such a diverse number of organizations is fantastic however I believe that ultimately the board is responsible for long term strategy and direction of the project. This means ensuring it’s not overtaken by a single interest and that it remains an open and level playing field for everyone. At the same time I think there should also be some consideration to keep it from becoming an free for all, or an umbrella for any software project that seems interesting. Along with that of course and just as important are continuing to manage how investments are spent and marketing OpenStack to continue growth and adoption.
There are a number of key topics that are currently being worked on including interoperability/compatibility and core definition. I believe that both of these are critical to the future success of OpenStack and am glad that efforts have already begun in both of these areas. I’d like to participate and contribute to both of these efforts. I’m a firm believer in consistency in OpenStack deployments regardless of backend devices, distributions etc. There are plenty of methods available to extend functionality but there should be a base set of requirements that are met regardless of other variables.
John has already been nominated by: