Icehouse, the 9th release of OpenStack, is out! Thanks to the 1200+ contributors.    OpenStack Icehouse

Individual Member Profile

markmc

 

Mark McLoughlin


Date Joined
July 19, 2012

Affiliations
Red Hat From 2013-10-05 (Current)
Statement of Interest

I'm a member of the Technical Committee, Foundation Board of Directors and the Nova and Oslo core teams.


Twitter
LinkedIn
IRC
markmc

 

Bio

Mark McLoughlin is a consulting engineer at Red Hat and has spent over a decade contributing to and leading open source projects like GNOME, Fedora, KVM, qemu, libvirt, oVirt and, of course, OpenStack.

Mark is a member of OpenStack's technical committee and the OpenStack Foundation board of directors. He contributes mostly to Oslo, Nova and TripleO but will happily dive in to any project.

Mark is responsible for Red Hat's OpenStack technical direction from the CTO office.

To find out more about Mark, see his keynote from the Icehouse Summit: http://www.youtube.com/watch?v=m6A2AQFnqH8


 


Projects

I'm involved in the following OpenStack projects: Nova,Glance,Keystone,Horizon,Quantum,Cinder,Ceilometer,Heat,Ironic,Oslo,Openstack-ci,QA,Deployment,DevStack,Release

 

Mark is a candidate in the 2014 Board Election.


Q

What is your relationship to OpenStack, and why is its success important to you? What would you say is your biggest contribution to OpenStack's success to date?

A

I've been involved with OpenStack for over two years now. I started out packaging OpenStack for Fedora, but have concentrated mostly on contributing to the several projects in various ways since then.

I was PTL of the Oslo project for most of the past year, kickstarting this effort to resolve some serious technical debt in OpenStack where projects have failed to share code as libraries resulting in inefficiencies and inconsistencies. I'm proud of the work I've done to create the oslo.config and oslo.messaging libraries and hope it will serve as an example for future cross-project collaboration within OpenStack.

Along with Monty Taylor, I'm in the interesting position of occupying elected seats on the Technical Committee and Foundation Board of Directors.

I'm also a member of the Nova core review team and have recently been contributing to the TripleO program.

It's thanks to Red Hat that I have time to make these contributions to the project and I am the technical lead of Red Hat's OpenStack team, reporting to our CTO.

Red Hat's mission statement is all about being a catalyst in communities and, while credit must go to others for initially catalysing the OpenStack community, we recognize the massive strength of OpenStack's diverse community. This strength is the foundation that will ensure that OpenStack continues to grow, continues to improve and will be around for a long time to win. Red Hat is doing everything it can to help make that happen.

Q

Describe your experience with other non profits or serving as a board member. How does your experience prepare you for the role of a board member?

A

I've been a member of the Foundation Board of Directors for this past year, so I think I have a good understanding of what the role requires.

Indeed, perhaps the thing I've most come to appreciate over the past year is that we have a very large board with a very diverse membership so the key to making an impact on this board is to identify your own particular interests and skills and focus your contributions around those.

Outside of this experience, I've been heavily involved in various open-source projects for over a decade now. Observing and pondering the role of non-profit organizations in open-source projects has prepared me well to participate in the OpenStack Foundation and its efforts to determine its own particular role.

Indeed, I participated significantly in the early discussions leading up to the formation of the Foundation and even proposed a strawman Foundation structure (http://wiki.openstack.org/StrawmanFoundationStructure) based on my experiences with other similar organizations.

Q

What do you see as the Board's role in OpenStack's success?

A

More importantly, I think, is the role the Foundation will play in OpenStack's success. I'm a big fan of the Foundation's simple mission statement - to "protect, empower and promote" OpenStack. It perfectly encapsulates the role of the Foundation.

The "protecting" and "promoting" elements of the mission are hugely important, but what I find myself wondering most about is how the Foundation can "empower" the project. In this past year, I think we've been effective at re-inforcing the understanding that the project's future and direction lies in the hand of its meritocractic community of contributors (in the broadest possible sense) and not the Foundation itself. I'd like to see that continue.

I think that if the Board delivers on the promise of a Foundation which "protects, empowers and promotes", we will find ourselves in the enviable situation of a project with a large and diverse community of contributors supported by a well-financed organization acting at all times in the interests of that community.

Q

What do you think the top priority of the Board should be in 2014?

A

For me, the top priority is delivering on the promise of a marketplace of compatible OpenStack clouds. The board's efforts to define criteria for certifying OpenStack implementations is just beginning and I hope we can make rapid progress.

I wrote more about it here: http://blogs.gnome.org/markmc/2013/10/30/openstack-core-and-interoperability/


Mark has already been nominated by:

  • Matt Wagner
  • Troy Toman
  • Tristan Goode
  • Russell Bryant
  • Tim Bell
  • Julie Pichon
  • Jonathan Bryce
  • Mark Collier
  • Sean Dague
  • Joe Gordon