Icehouse, the 9th release of OpenStack, is out! Thanks to the 1200+ contributors. OpenStack Icehouse
I am a contributor to the project and part of a team running OpenStack in the public cloud
I am currently part of the public cloud team at Rackspace. I lead Rackspace's OpenStack strategy and work with teams on our overall open source efforts. Prior to this role, I led the engineering teams responsible for the Rackspace Public Cloud services including those deploying and contributing to OpenStack Nova, Swift, Cinder, Glance and Neutron. I have been at Rackspace since 2006 and served in a number of development and operations functions across the company. I am also a member of the advisory council of the Department of Computer Science and Engineering at Texas A&M University.
I'm involved in the following OpenStack projects: Nova,Swift,Glance,Keystone,Quantum,Cinder,Openstack-ci,Openstack-manuals
I have been involved with OpenStack since early 2010. During the past three years I have been an OpenStack contributor, operator and user. I was an early member of the netstack effort which eventually evolved into Neutron. I serverd as PTL for the incubated IPAM project called Melange which was merged into Neutron. I have served as a member of the OpenStack Foundation Board of Directors since its creation in 2012.
OpenStack is a chance to evolve how open source communities collaborate to rapidly evolve complex solutions. There is great potential power in the model. OpenSTack is not about merely replicating other open source models to produce a cloud operating system. We are trying to leverage the best of past experience to create a new collaborative model that will, in turn, create the next generation platform. The success of OpenStack is crucial to the evolution of open source in broad terms. That is an important cause for me.
My biggest contributions to OpenStack have been to provide mentoring and leadership to a number of OpenStack members and early project formation efforts. I have had the privelege to serve in a managerial role for a large number of OpenStack core developers and contributors. I have been involved in the early evolution of the OpenStack Foundation. I have served in an advisory role with a number of teams launching new projects including Neutron, Marconi, Solum and Barbican. In every one of these situations, I have been able to help teams understand the fundamental founding principles of OpenStack and ensure that new entities embody those ideals from the start.
I am currently on the board of the Alamo Heights School Foundation, a board member of the OpenStack Foundation, an advisor to Literacy San Antonio and a member of the advisory council of the Department of Computer Science and Engineering at Texas A&M university. I have previously served as a board member for the San Antonio Public Library Foundation.
I have now had several years of non-profit experience which has taught me how to walk the line between the ideals of social change and the practicalities of depending on volunteer resources from a variety of backgrounds. It is important to have a strong voice for the founding ideals of an organization. They cannot be taken for granted and must be eplicitly raised as a lens for board decisions. At the same time, there are practical realities about aligning a wide variety of points-of-view and needs. This balance is essental in the evolution of a non-profit. I am now clearer on this role and hope to be able to use these skills in service to the OpenStack Board of Directors in 2014.
The OpenStack Foundation Board of Directors is responsbile for creating an evironment where the our open, collaborative model can thrive. That means overseeing the financial health of the foundation; ensuring the bylaws are followed and also driving modifications where they are necessary; promoting OpenStack within the foundation membership and across the industry; managing the definition/evolution of OpenStack core and the OpenStack trademarks. In most cases, this is not about the Board setting an agenda or driving the direction of OpenStack. It should be removing roadblocks and facilitating dialog that enable the membership to make OpenStack what we want it to be.
Completion of the DefCore process and establishing and efficient mechanism for defining OpenStack Core.
Troy has already been nominated by: