OpenStack maturity and Adoption
Ken is a Business Development Manager, focused on helping his team to build out EMC’s OpenStack Solutions strategy. HIs passion is to help IT deliver value to their customers through collaboration, automation, and cloud computing. Ken is an OpenStack Ambassador and a VMware vExpert. He blogs about cloud computing, OpenStack, and the EMC Federation at http://cloudarchitectmusings.com.
My relationship to OpenStack is multifaceted; I am at once a supporter, an ambassador, a critic, an architect, and a strategist. Fundamentally, I believe in the ability of a community of technologists to innovate rapidly and to create a platform that can help users and vendors succeed. Although OpenStack also has the potential to fail if the community is not able to stay cohesive in working together to build a sustaining project, I believe in it enough to stake my career on its success. The past few years, I've devoted 100% of my working life to the success of OpenStack, rather it be a Rackspace and in my current position driving the development of OpenStack solutions at EMC.
My biggest contribution to the success of the OpenStack project has been in the areas of technology evangelism and community building. I've spoken at numerous conferences, educating users and vendors on the OpenStack technology, including 15 talks over the last 3 OpenStack Summits. I've been able to blaze some new trails with tech blogs on topics such as SDS in Cinder and VMware vSphere with OpenStack. The blogs on those topics are still being referenced today by community members. I've also been able to help numerous VMware administrators with the transition the OpenStack community through my blogs, talks, and personal tutelage.
As a community advocate, I've been able to assist in jump starting and co-organizing 3 OpenStack user groups in the east coast. As an official OpenStack Ambassador, I've helped other user groups throughout the country as a speaker, as a resource to help with scheduling other speakers, and advising on organizational issues. I was a co-organizer for the new OpenStack Design Guide book sprint and helped to recruit writers from the community.
I've worked at 1 non-profit organization and served as an advisor for another, both outside the tech arena. In the former case, I was director of a program to equip organizations to teach job training skills to the clients they serve. The organizations we equipped included homeless shelters, drug rehab centers, and neighborhood churches. In the latter case, I advised an organization in Harlem that provided, free of charge, early childhood development classes and resources to families in low-income neighborhoods.
The key lessons I learned that would make me a valuable OpenStack Foundation board member is the importance of education, collaboration, and providing strong direction and vision. Any organization and community as diverse as the organizations I worked with and as constituted by the OpenStack community requires constant education of our values and charter. It requires a willingness to listen to everyone and to include as many community members as possible. It also requires the ability and willingness to set a direction for the community even when there is disagreement from some quarters.
The OpenStack Board is the shepherd of the community but not the benevolent dictator. The Board needs to set the direction of the project, with input from as many members as feasible, but needs to do it primarily through persuasion and education. The Board needs to be able to evaluate what is required, not only for the short-term success of the project, but what must be done to ensure ongoing long-term success.
I see several priorities for 2015. They include:
1) Enabling a product management function to ensure that the growing number of OpenStack projects integrate together to create a cohesive platform.
2) Finalize the Defcore initiative to bring clarity to what constitutes OpenStack.
3) Continue to focus on Operators and their requirements for a usable and sustainable cloud platform.
4) Create new avenues for contributions from non-developers. This includes a mechanism for hearing the voice of the end-user.
Kenneth has already been nominated by: