Project Teams Gathering or Magic The Gathering?


Unless you’re familiar with the OpenStack way of getting things done, an event called “The Project Teams Gathering” or PTG will probably remind you of something else that may have been misunderstood, “Magic The Gathering” or MTG.

Magic The Gathering

One of these events promote collaboration, community and cross-project creativity, the other is a tradable card game that allows you to battle against friends in imaginary conflicts. I’ll let you guess which one I attended last week (if you know me, it might be hard to guess.)

Typically, this type of event was held in conjunction with the bi-annual OpenStack Summit held in an adjacent building or section of summit conference facility. It used to be called the Developer Summit and seemed to work well at the time, but as the projects grew, as well as the number of attendees, not so much.

As a response to this growing challenge the OpenStack Foundation and more specifically Theirry Carrez sent an email after the Tokyo summit that announced the plans for the concept of a PTG. He explained that this change, to a separate but equal (or better) event, would occur immediately after the Ocata release and be focused on Pike. So, with one extremely long sentence, Theirry explained that the new event would “restore the productivity and focus of the face-to-face contributors gathering, reduce the need to have midcycle events for social bonding and team building, keep the cost of getting all contributors together once per cycle under control, maintain the feedback loops with all the constituents of the OpenStack community at the main event, and better align the timing of each event with the reality of the release cycles.” 

End of Day 2 Tired Selfie

In my experience, this PTG did exactly what it was designed to do. Based on what I observed at this first event, the PTG was magical. The way that everyone comes together for a week and makes it a priority to only work on OpenStack projects is the real magic at the PTG (and you didn’t even have to bring trading cards.) I’ve been to quite a few of the Dev Summits but the PTG really provided me with the time to get to know some of the others on my project teams and to have the ability to collaboratively dive deep without interruption. Sure, we all had our laptops, and sometimes, myself included, had to step away for obligations to our employers, but for the most part, I was able to throw myself into my OpenStack projects. Normally at the summit, this wouldn’t have been possible with all of the customer meetings, strategy sessions, dinners, vendor parties, etc.

The PTG also helped enable in-person cross-project collaboration and communication avoiding the oft misunderstood email thread that sends everyone down a rabbit hole. Need someone from Neutron? He’s over there. Need someone from Designate? He’s sitting two chairs away from you on the left, his name is Graham. Awesome sauce. Normally I’d have to run from room to room looking for these folks based on the session that was happening, but at the PTG, most everyone was in organized conference rooms that had plenty of space and you could find pretty much anyone within a few minutes. Groups were welcoming, plenty of places to sit. Coffee, tea and water was in good supply and even the lunches weren’t all that bad.

What does the DOCS say?

As far as the Docs Team, we got A LOT done, which is a blessing and a curse since we’ve decided to do a lot this cycle but without the PTG this year it would have taken, at least for me, a lot longer to get my ideas socialized and turned into plans on etherpad.

I think we’ve all agreed, at least in the guides that we need to make sure the “what” and the “why” is completely represented before we dive any deeper into the “how.” Some guides, like the install guides for example are an exception to this rule, however, even those guides need somewhere to point when there needs to be a deeper discussion around why a topic exists and where it fits into the larger picture versus all of the available options. Look for great things in Pike from the Docs team and as usual, if you’re interested in helping, come see us at #openstack-docs or send a message to asettle, bsilverman, darrenc or anyone else on the docs team you may know. We would appreciate the help.

Overall, I think the PTG really brings us back to where this whole thing started, reminds us of what OpenStack really is, it’s the people, not the technology. It’s people with ideas who aren’t afraid to share, others who believe in those ideas, and the community of people who are willing to put everything aside, if just for a little while, to make this amazing project happen.

I’d like to thank the unsung Heros of the PTG for all of their work, especially Erin Disney and the rest of the Foundation Staff for putting this all together at the Atlanta Sheraton Downtown.


Press Release – “OpenStack for Architects”



 The definitive book on OpenStack architecture, published by Packt Publishing, is now available from leading booksellers.

 The 214-page book, “OpenStack for Architects” explains how to implement successful private clouds using OpenStack, the extremely popular free open source cloud operating system. “OpenStack for Architects” leads the reader through each of the major decision points that the reader will face while architecting an OpenStack private cloud. At each point, we offer the reader advice based on the experience we have gained from designing and leading successful OpenStack projects in a wide range of industries. Each chapter also includes lab material that gives the reader a chance to install and configure the technologies used to build production-quality OpenStack clouds. Most importantly, we focus on ensuring that the reader’s OpenStack project meets the needs of their organization to guarantee a successful rollout.

 The book is targeted at a broad spectrum of readers, including IT architects, engineers and programmers seeking more knowledge about private cloud platforms as well as seasoned OpenStack operators who are looking for guidance around operational topics such as monitoring, capacity planning and security.

It is now available (list price $39.99) from Amazon, O’reilly and Packt Publishing and books will be available at a discount at upcoming Red Hat and OpenStack Summits.

About OpenStack

OpenStack, an Infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS) platform is transforming the way infrastructure and workloads are provisioned and managed through self-service and on-demand tools. OpenStack enables IT departments to meter and manage infrastructure in a private cloud, much like public clouds like Amazon’s Web Services.

The book provides a step-by-step process and guidance to planning and running an OpenStack cloud in production. It also helps readers through the components of OpenStack and lab construction as well as deploying, integrating and configuring OpenStack in existing enterprises.

 About the Authors

Ben Silverman, as the Principal Cloud Architect for OnX Enterprise Solutions, is responsible for providing strategic and tactical cloud leadership to OnX’s customers. Previously, Ben was a Senior Cloud Architect at Mirantis, where he developed cloud solutions for many Fortune 100 companies. Ben has been involved with OpenStack since the Havana release and is an active technical contributor. Prior to working for Mirantis, Ben was the Lead Technical Architect at American Express, where he built one of the largest financial services OpenStack clouds at that time. Ben is an exuberant OpenStack evangelist who is often seen speaking at industry events and conventions about OpenStack adoption, scale challenges, and cloud operations. In his limited spare time, Ben and a few others have taken on the task of re-writing all of the OpenStack architecture and operations guides that are currently available on the OpenStack Foundation website. Ben has a Master’s degree in Information Management from Arizona State University and lives in Phoenix, AZ.

Michael Solberg, as a chief architect, is responsible for helping Red Hat customers achieve their key business transformation initiatives through open source architectures and technologies. He regularly advises a range of Fortune 100 companies in financial services, healthcare, retail, and transportation verticals on topics such as cloud computing, big data, high-performance computing, and enterprise middleware. At Red Hat since 2008, Michael has led a number of successful initiatives to assist strategic customers adopt new virtualization, systems management, and engineering practices. His previous experience includes building web hosting infrastructure. He is also an avid supporter of the OpenStack project. Michael holds a Bachelor’s degree from the University of Georgia and is a regular speaker at industry events.