 What they're doing over there. So in a few minutes, we're going to hear from Mark McLaughlin, who's another amazing leader in the OpenStack community. And before he comes out, we're going to have a short video from Red Hat. It was only a few years ago, OpenStack was just an idea between Rackspace and NASA to build clouds that are massively scalable and simple to implement. Now, that idea is empowering a community to change an industry. But technology alone is just technology. Technology alone does not ignite change. Technology alone does not push society forward. People do. And by developing technology openly, more people can participate. Our cloud company is profitable at just height. We don't see OpenStack having a basis in reality check. OpenStack is not the most likely. There are thousands of engineers and hundreds of companies working together to help our collective customers move forward, to help solve the unsolvable at a rate of innovation that could never be accomplished by one organization alone. Together, we press forward. Together, we change the game. Please welcome OpenStack technical director Red Hat, Mark McLaughlin. My goodness, this is a lot of people. OK, good morning, everybody. The last time I was up here in Hong Kong, I used my keynote to talk about my personal belief in the promise of open source. The strength that a diverse community brings to a project and how we could expect OpenStack to evolve in the years ahead to an expansive umbrella of innovation in cloud infrastructure. More recently, and with some mixed emotions, I've completely changed my role at Red Hat. These days, I've moved my focus away from the upstream project, and instead, I'm helping to manage our OpenStack engineering team, working closely with our partners, and really helping our customers be successful with OpenStack. In some ways, I think my own change and role kind of mirrors Red Hat's approach to creating technology the open source way. I remember back in 2011, at one of our early OpenStack engineering team meetings, laying out for the rest of the team how we could all expect our focus to change over the years as we got more into OpenStack. And I really see our approach to new projects as kind of being a three-phase thing, where each phase builds on the previous one. So, the first phase, participation. Our initial goal is always to participate, and by that, I mean we look for ways to make meaningful contributions, but also to build a really close affinity with the community standing behind the code. This is kind of where we play a Jedi mind trick on ourselves and start to talk about the community as us rather than them. And it's where we learn to kind of put aside our Red Hat and really truly represent the interests of the project as community insiders. So, moving on from that, next we kind of, we build out our ability to deliver a high quality OpenStack distribution. And we've taken a dual approach here with OpenStack. With RDO, we've created an open community of people interested in running OpenStack on Red Hat distributions. This is where users can take a packaged version of OpenStack that stays close to the upstream code base and allows these users to really engage closely with the upstream project. With RELL OpenStack platform, we take what RDO has produced, spend a lot of time validating the many possible configurations that our customers use, and working closely with our partners to certify their technologies and really kind of preparing this whole organization to be ready to make customers successful with the new release right out of the gate. And the final stage, then, is with the product in our customers' hands, we aim to work closely with our customers to ensure that they succeed with their goals for their OpenStack deployments. And so we support our customers in the broadest possible sense of the word. And we're now deep in this latter phase with hundreds of customers of the RELL OpenStack platform depending on its daily. And all of this has a much broader meaning for me on a very personal level. I've chosen to dedicate my time to really proving that open collaboration is a great way of building technology, that from a community of diverse interests spring some fantastic innovation, that an open system, an open ecosystem really delivers great freedom, value, and choice for users of the project, and that it's perfectly possible for successful businesses to both compete and collaborate within such an open ecosystem. For me, central to all of this is demonstrating the commercial value that a pure play open source vendor like Red Hat can deliver to users. And so I've been at Red Hat over 11 years now, so I think I've some pretty good insight into why customers choose to work with us. Sometimes it's because of our real commitment to the projects that we're shipping and our ability to represent customer needs in those communities. Other times it's because of our emphasis on long-term stability and security. Other times it's the reassurance of our certified partner ecosystem. A lot of the times it's actually about our subscription model and the way that model empowers our users and really requires us to deliver continuous value to our customers. Sometimes when I'm asked the very simplistic question, if the software is free, what do people pay Red Hat for? And if I have to quickly answer that, I lean on the most easy to explain answer. And that's Red Hat customers rely on Red Hat for our deep expertise and our technical support. Because modern software is incredibly complex. And if your business depends on a particular technology, you inevitably look to lean on a vendor for their expertise so that you can get the most out of the technology and also so that vendor is there ready to be available to you at a moment's notice if something goes wrong. And so with this change of role, it's really only in recent months that I see on a daily basis this aspect of Red Hat's business. I've always had a particular curiosity for what happens when a customer experiences an outage and how we rally a diverse group of experts to get a customer back up and running. There are many ways to explain the concept of technical support, but for me what brings real meaning to the term is the people behind the support commitment. We're talking here about technical experts. We're looking to use their deep expertise and knowledge to really get a customer back on track. We're talking about engineers with genuine empathy for customers' needs. Our support model is not one of deflection. We really aim to engage our customers with our expertise, whether that be arming you with whatever you need to handle the latest security vulnerability, whether that be Heartbleed or Shellshock or like last week, Phenom, or on those occasions that you do need to pick up the phone, that you quickly get through to a specialized engineer who has access to and a deep familiarity with the code and question. So at Red Hat, we don't see our support team as overhead. We really see them as an extension of our engineering team because it's really through the feedback we get from supporting our customers that we gain the ability to really improve the software. And so I want to take a couple of minutes now to show a short video, which should give some insight into the human side of what providing technical support means at Red Hat because we have a support model, but to me it's really the humans behind that model that make the difference in the end. And so we're going to hear quickly from some support engineers and product engineers about how we all work together to really help get a customer back on track. So, play the video. We want to engage with our customers. Working with our customers is the best way that we know that we're doing a good job. It's also the best way that we know to shape the future direction of the product. I think the level of expertise you'll find in our support organization is above and beyond a lot of other companies. I mean, I look at our support organization as being an extension of engineering. Our mentality is we want to be a partner with the customer and really work through the problems with them. With OpenStack, it's critically important to have that relationship with our customers because the complexity of the software. We understand that OpenStack is not a one size fits all solution. We can't just develop an OpenStack product and have the exact thing delivered to every customer. Support is often a very one dimensional process where you have a problem and you pick up the phone. At Red Hat, support is a much more dynamic collaborative process. It's very much aligned with the open source philosophy of letting that really good idea come to the top. Talk about it, get that feedback, but then make it happen. When OpenStack customers call or open a ticket, they're going to be immediately engaged with somebody who has been trained, who has been certified and who has experienced working with OpenStack and working with our customers. We all feel very personally committed to solving customer issues. There's also the aspect of it's our code, we help to write it and so we want it to be the best code it possibly can be. I think there's a passion in the people that work at Red Hat that comes out in the way that we support our customers because we're all very thankful that we get to work for a company that values open source and open development. OpenStack really pulls together all of these different pieces into this really fun amalgam of people trying new things, people breaking old models and no one's telling us no. We have this ability, if someone has an idea, if someone wants to do some new as a service, go, write it, submit it, share it. It's very inclusive, it's very fun, you know. So you've had a brief glimpse into what providing support means for us at Red Hat. And the reason I wanted to talk about this today was just because I think we're in a really unique position with OpenStack. We, all of us here together, have built an incredibly powerful set of technologies and OpenStack in turn brings together a whole myriad of other technologies. And yet again on top of that, we're seeing many technologies building on OpenStack, integrating with it and really using it as a platform. But if you're a user of OpenStack and you want to build a cloud to run your business on, you know, there's a lot of expertise there required. And supporting that cloud into the long term is an even greater challenge. And what I really wanted to get across today is Red Hat takes that part of the challenge incredibly seriously. And we want to be there for you as you embark on your OpenStack adventure. Thank you very much. Thank you Mark, really appreciate your help. And I want to thank actually all of our headline sponsors for making this all possible today. And...