I run the OpenStack Development Infrastructure
I currently work full-time on OpenStack for IBM. I lead a team that works on running the Developer Infrastructure systems for the project, as well as other pure-upstream development efforts. I am PTL Emeritus of the OpenStack Infra Program and set up the original project gating infrastructure. I currently sit on the Technical Committee. Previously, I was a core developer on Drizzle and was a Senior Consultant for MySQL, Inc. I've been a Python hacker by choice since 2000, and am currently a member of the Python Software Foundation.
I have a degree in Theatre Directing and went to grad school at CalArts in lighting design. The intersection of fields has led me to start more than one business around developing technology for and related to live performance. I continue to work in the theatre, and regularly light shows in New York, Seattle and Austin.
I'm involved in the following OpenStack projects: Keystone,Openstack-ci
I have worked on OpenStack since the very beginning. By working on Infra, I've been in the midst of all of the cross-project interactions and have a first hand experience of how things are difficult. Infra also runs its services across multiple OpenStack clouds, so I have direct knowledge of the interop wins and challenges. I have a team working on meta scale OpenStack public cloud, so I've got ever growing insight into the world of the deployer. OpenStack is what I do from the time I wake up until the time I go to bed.
I work that hard on OpenStack because I believe in freedom. It is important for our industry that people not be locked in to proprietary platforms. We won that battle so well with Linux that even Microsoft embraces it now, but the tables have been turned in Cloud, and we're back to the drawing board. OpenStack being able to provide multiple real Public Clouds, as well as continuing to be suitable for private clouds is essential. Remember that 15 years ago people thought there was no way Linux could target both scale up and scale down and needed to pick.
My biggest contributoin to date has been using my influence and position to ensure that Infra was staffed with people who don't give up and who put the project first. It's not simple to convince companies to invest in what sounds like altrusim because it doesn't deliver a feature in their next product release - but that's the kind of important challenge I like.
I'm a member of a leaderless experimental theatre collective in Seattle. If you think collaborating with hundreds of companies is hard, trying getting 12 experimental theatre artists on the same page.
My experience serving on the OpenStack Board since its useful in setting expectations. Things don't happen quickly in a 24-person Board, not sohuld they. One does not sit on the board to _do_ things - one sits on the board to make sure that bad things don't happen, and to enable the groups who are doing the work, whether that be the Technical Community, the Foundation Staff or key committees like DefCore.
The OpenStack Board must clearly communicate with our business community what the ground rules are. Most specifically, we need to be a place where competing interests from the associated product lines can get in a room, talk and reach compromise so that everyone comes out the other side a winner. The pie is REALLY big here and there is plenty for everyone.
Interoperability and a focus on the end users. That may sound like two priorities, but it's really the same thing. When we focus on what is good for the end user vs. what is good for the vendor, interoperability is easy. The Board can be useful here by providing clear communication about goals and criteria for brand usage, and by providing ground cover for the TC when serving the users puts them into a sticky or unpopular position.
Monty has already been nominated by: