Icehouse, the 9th release of OpenStack, is out! Thanks to the 1200+ contributors. OpenStack Icehouse
I lead VMware's efforts on OpenStack (formerly I was PTL for Neutron)
I head up VMware's OpenStack efforts across compute, network, storage. I came to VMware via Nicira, the company behind Open vSwitch and as part of that effort I help start and was the PTL of the OpenStack Networking Project (Neutron). During that time, I was a core developer on OpenStack Neutron and also made significant contributions to Nova, Docs, and Devstack.
During this time, I've spent countless hours not only developing and troubleshooting OpenStack deployments (both in-house and at customers) but also educating customers about how they can deploy OpenStack to help solve their cloud challenges.
I also served on the OpenStack Technical Committee during this time, and have a lot of experience working closely with the folks who "keep the lights on" from a technical + infrastructure perspective.
Outside of work, I enjoy trail running, and brewing/drinking beer.
I'm involved in the following OpenStack projects: Nova,Glance,Quantum,Cinder,Oslo,Openstack-ci,Openstack-manuals,DevStack
At VMware, I have been instrumental is driving the company to embrace OpenStack and assign resources to contribute to OpenStack VMware's motivations within OpenStack are simple: our customers are interested in deploying OpenStack, and so we want to make it easy for our customers to realize the vision of cloud using OpenStack with whatever pieces of VMware technology they see as valuable.
Many people are surprised to learn how much VMware already contributes to OpenStack. We have already made major contributions across Neutron, Nova, and Cinder, and while rankings + metrics give only a partial picture, in Havana we had 17 different developers contribute, making us the #7 contributor and the #5 most frequent code reviewer for OpenStack core projects (according to http://www.stackalytics.com). I'm particularly proud of the reviewer number, as it indicates how VMware is contributing to help improve the overall quality of the OpenStack codebase.
And as a side note, we run a 150+ physical node OpenStack cluster with mix of hypervisors, Neutron networking, and multiple sites. All of my work is done on VMs on this infrastructure, so that is a vested interest as well :)
I do not have any prior non-profit board experience, but I have phoned in and listed to many of the OpenStack board meetings over the past year, so I am well versed in the fast-paced world of OpenStack board meetings :)
The board is responsible for envisioning and creating an environment that fosters the long-term growth of OpenStack. This means thinking about all of its constituents: users, developers, ecosystem vendors, etc. and making sure that these different parties all can achieve their own success in a way that facilitates the overall success of OpenStack. To do this effectively, you need to both know how the OpenStack technical community really operations on a day-to-day basis, and have a good understanding of the end-user environment where customers, often in conjunction with vendors, are using OpenStack to solve real business problems. As someone with both the technical community experience and significant customer-facing experience, I think I'm a good fit for that role
I'm going to cheat an mention two quick priorities:
1) Focusing on getting OpenStack into the mainstream enterprise in terms of real production deployments. This is close to my heart, as I think VMware can play a big role facilitating this.
2) Defining "what defines" OpenStack. In the user community, there is significant confusion around API interoperability (i.e., is OpenStack an API standard?). Is OpenStack just an ever-growing toolbox of services that may or may not be running in a particular deployment, or it is a core set of services providing real interoperability? I'd really like to be involved in efforts that seek to clarify what it means to be OpenStack.