 Jonathan Bryce. Without much hair, that mustache, and I don't play tennis. But rather than fixing it, they gave me a tennis racket. So good morning, Boston. It's great to be back here. Some of you may know that this was the place that we did one of our original summits about five and a half years ago, October of 2011. We had about 600 people here then. And it was very early on in the development of the project. And here we are, back here, thousands of people from all over the world. We have 63 countries represented, a lot of people from China, Japan, the UK, all over, even New Zealand. And it is something that is so cool every time we come to the summit and we get to bring the community together, and we get to also add new people to the community. How many of you are here for the first time? Great. Well, welcome. We are very glad to have you joining us. So the best way to find your way around the summit is with our mobile app. And you can go to openstack.org slash mobile to download that. And that is, it has all of the schedules, the agenda. It has maps. You can rate sessions. So a lot of information in there. If you do not like technology, there's an analog version that is in your badge insert, a piece of paper that will work. It never runs out of batteries. It's pretty convenient. And it has a map. It also has an overall summary of the schedule. Just to orient you a little bit, because we are in several locations across the week. Right now, we are in the keynote room in the Heinz Convention Center. Directly behind us is the marketplace and also a primary lunch location. If you continue past that, there is a walkway to the Sheraton. And that is where OpenStack Academy, the hands-on workshops and training are, as well as the open source days. And I know we have a lot of people here for this open source days component that we're doing for the first time at this summit. So these buildings and the primary floors here in the Heinz, this is where everything is happening. The map kind of explains how that works. I mentioned that I love getting our community together. And it truly is a community. One of the things that we've had for several summits now is a travel support program to help individual contributors or diverse contributors who might not be able to make it to the summit, be able to attend. And on the suggestion of one of our community members, we actually opened this up for individual contributions. And I just wanted to briefly recognize the individuals who contributed to the travel support program to help other communities be here this week. So thank you to all of you who contributed. And speaking about getting our community together, we are going to bring back the Stack City party that we started in Austin. Tomorrow night we will be going to Finway Park. That's just down the street here, a really awesome historic baseball stadium. And thank you to the sponsors that are sponsoring this party. You might have noticed that the weather here is a little chilly, so you probably want to bring a jacket because most of Finway Park is outside. Your badge insert, again, it has walking directions and transportation info on how to get there, which gate to go to. And you're going to need your badge to get drink tickets and food tickets there. So join us tomorrow. 7 PM, it's going to be an awesome time. So I want to talk about a few different things today. We've got a great program. We've got some users, some different companies that we're going to be hearing from. But first of all, I want to talk a little bit about OpenStack in the news. If you follow OpenStack at all, you know that we are in the news a lot. And there is a whole wide variety of viewpoints and opinions out there. Obviously, I have a fairly strong opinion about OpenStack and a positive one. But I'm not oblivious to the variety of other opinions that are out there. In fact, I pay a lot of attention to them because ultimately what I care about is the success of OpenStack and our community. But you might have seen things like a tweet like this. OpenStack is as good as dead. That was actually from 2013. So it's kind of a hobby. People love to make these comments and make these predictions, and they do it year after year after year. But those are kind of opinions. And what I really like to base my plans and my decisions on our facts and data. So I wanted to start out with a couple of updates to some of the data that we track at the foundation. We do an OpenStack user survey every six months. And we just recently completed the latest one. And it had some amazing data in there. And a lot of it was really positive, and there were things that we can learn from as well. But one of the biggest stats was that we saw a 44% year over year growth in the number of deployments that we were tracking. And that is a huge jump over every other user survey that we've done. And the other thing that's interesting to think about is we are seven years into this project, and we're seeing accelerating growth and accelerating adoption. And that kind of makes sense when you think about how technology, especially open technology, gets developed. There's a period where communities form, and we had a big community that formed up quickly. And then they start building the technology, and then it crosses the chasm to where it can be adopted and used for a massive amount of use cases. And that's where we are now. Our technology has matured, it's been put into production, and we're seeing a huge user spike in this adoption phase now. Of those deployments, what's held steady year over year is that two-thirds of them are cataloged as being in production. So we're seeing growth in overall deployments and a continuation of the number of them that are in production. This is a stat that we mentioned last year, 50% of the Fortune 100 running OpenStack. A new one that we have that I'm really excited about is we have now cataloged over 5 million cores of compute power that OpenStack is managing around the world. And so think about what that represents. As a global footprint, this is in over 80 countries that these deployments are running. 5 million cores of compute power. It's a lot of work that's getting done out there on OpenStack every single day. And so this is another quote that I kind of identify with. We've scaled, we've accelerated, we've matured, and we're seeing a lot of growth and a lot of workloads moving into production now. But at the same time, that's not the only thing that I care about. Obviously I think that OpenStack has a very important role to play in Cloud today and also into the future. But there are always things that we can improve and ways that we need to look at what we're doing and how we're doing it and what we should change. And recently we had a leadership summit with about 40 leaders from the board, the technical committee, the user committee. And what we did is we got together and we looked at what's happening in OpenStack and what are the areas that we need to focus on improving. And we came up with five areas that we prioritized. And to talk us through that and tell us kind of what we're thinking about so we can get feedback from everybody, I want to invite up a couple of our community leaders. So help me welcome Laurence Sell and Terry Perez. Good morning. Hello. So as Jonathan said, there are about 40 of us who got together actually here in Boston in March for this leadership session, which was very productive. We're thinking about the future of OpenStack, what the opportunity is, but also being honest about what are our challenges and what do we need to do to work on those. So today Terry and I just want to walk you through what those five areas were and what some of the things are that we're working on in the community. So you can take those hopefully into the sessions this week and get involved. So the first area of the five is clearly communicating what is OpenStack. And we've definitely gotten a lot of feedback over the last year with the introduction of the Big Tent concept, also with the deprecation of StackForge, if you're familiar with that, which were kind of the repos of emerging projects on the edge of OpenStack, that it caused some confusion about what is OpenStack, what is actually inside an official OpenStack project and what is not. And to address this, we've more clearly defined the list of official projects. We also published a new version of our project navigator. But going forward, we want to produce a set of maps to more clearly clarify how everything fits together and see, for example, this project map, which is a prototype obviously, but which is a lot less intimidating than a list of 60 projects. Oops, sorry, can we go back one? So the second area that we're working on is improving the feedback loop. And I think this is a pretty common challenge for most open source projects. How do you translate these user requirements into upstream development? As a first step to solve this, this week at the summit, we are introducing a new format for community discussion called The Farm. We used to have up sessions and dev sessions on separate days at the design summit. And with everything that was going on during the summit, we ended up only attending one side or the other. And with this new format, everyone comes to the same table to discuss the same topics. So the third area we talked about is addressing complexity. An open stack is almost seven years old this year. It's a very robust set of capabilities. It's probably the largest support for backends in the industry. But we also continue to get dinged on the complexity of operating open stack. And this is something really taking too hard. Shortly after the workshop, we started to more actively identify areas where we can address this complexity in projects by removing unused features or printing extraneous configuration options or cutting projects that we are not going anywhere. Another perception concern that we identify is this view that open stack is an all or nothing monolith that you have like to install all the open stack projects or that you can't really plug any other technology in an open stack deployment, which if you think about it, a bit weird because open stack was always an open stack. Like we always integrated lots of different technologies that were not produced within the open stack community. So the reality is that open stack is building blocks for open infrastructure. And you can use those together. You can use them standalone. Or you can combine them with other technologies. And as a little teaser, we're actually going to see some demos along those lines tomorrow. In Mark's keynote, we're going to see Ironic and Neutron and Cinder standalone, which should be a pretty cool experience and something that the community has been focused on and talking about this week. But we're also really working to collaborate with these adjacent communities. So this week, for the first time at the Boston Summit, we're going to have open source days. So we've invited these adjacent communities to come and have sessions, collaborate with the open stack community, educate our users on how they can make use of their technology and get involved as well. But it's important that we're not just inviting people into our community. We have to go into these other important communities and work upstream and collaborate. So one great example of that is the open stack SIG and the Kubernetes community, which there's a lot of interest there with open stack users right now. And if that's something that you'd like to get involved in, I would encourage you to check it out. The last area was growing new community leaders. Over the last six years, our community grew immensely. And our focus was mostly on scaling our processes to cope with that explosive growth. Now we need to focus on providing a clear path for new contributors to rise up. We need to evolve our processes to be more friendly to part-time contributors, like contributors coming from direct users of open stack. But also evolve our processes to be more friendly to contributors in different time zones or different cultures, like our contributors from China. So the open stack community is broad and diverse. And we're in this for the long term. We're listening, and we're evolving. It's very important to us. So we want to thank you all for being here this week. The good news is this is open source, which means that everyone in this room can get involved and influence the future of open stack. So we encourage you to take these ideas into the sessions you're going into and to the conversations that you're having and help drive open stack forward. So thank you. Thank you. Thank you, Lauren and Teri. So I just want to reiterate that point there that Lauren made at the end. This is an open source community, and things get done by participation and involvement. So this is a summary of a lot of work that's going on in these five different areas. Love to hear what you think about it. And if you care about any of those, get involved with the groups working on it and help us make these really important improvements that we're working on together as teams. So I want to move on and look beyond just kind of what's happening in open stack and a little bit more at the industry. And I think that we are at a major inflection point in cloud. And this is really across the industry overall. If you look at what we're seeing, obviously we see big growth in public cloud. I just put some stats up about open stack. We see big growth in private cloud. We're seeing hybrid and multi-cloud use cases actually move into the real world and become something that people are putting production workloads on. And so we see growth everywhere. And I said 44% for open stack, AWS growing at about a similar rate. Some of our ecosystem companies that are here, I've been talking with them, they're seeing 40%, 45% growth in their businesses. So that seems to be kind of what we're seeing across all aspects of cloud. And as we look at that, I think that some people, they might be surprised by that growth in private cloud. And I've been thinking about that and kind of trying to understand what's going on there. Thankfully, I get to talk to a lot of users every day. And when I hear what they are doing with private cloud, I think that we've actually entered a second generation of private cloud based off of what people are doing and how they're doing it now. And so second generation, what was the first generation? I think the first generation was really around the time that we launched OpenStack. And that had a focus on kind of hyperscale cloud workloads. Rackspace was running at one of the largest public clouds at the time. Early OpenStack users that were doing private clouds were like Yahoo, eBay, PayPal that were also running at massive scale. And the focus there was really on very large environments. What was interesting, though, and what demonstrates kind of the power of open communities is as the community grew and people started to join the movement and contribute to OpenStack, OpenStack went into an entirely new set of arenas that public cloud couldn't or wouldn't handle at that time. And so in a way, by opening it up and allowing everyone to participate, what we've actually done is we've broaden the addressable market for cloud overall. And I think we're starting to see the payoff with that. But if you go back through and you look at some of the things that the community brought to the table, very early on in OpenStack, we had IPv6 support because we had users that needed it and they came and they did the work and they implemented that in OpenStack well before it was available in public clouds. Geographical needs for data sovereignty, for regulations, for performance, for local laws. This is something that has driven a lot of private cloud usage, but also we have about 30 public clouds around the world that run on OpenStack. Different hardware configurations that people need for various workloads. NFV, this is one of the fastest growing use cases for OpenStack. We have telecoms all over the world that are building their networks powered by OpenStack. And Edge is a use case that we see emerging in a big way right now and there's going to be a lot of talk about that this week. In fact, we're going to hear from Verizon in just a little while about NFV and Edge computing and what they're doing with OpenStack. And so these are things that the community has done and that this open environment has enabled us to do together and to innovate in. And as I look at that, I really do think that we've kind of passed this point of a generational shift in clouds and it affects the technology, the adoption, and also the challenges that people face. If you look at the technology, the first generation was very focused on compute virtualization only. And now we see that everything is virtualized, the compute, the network, the storage. We're pulling in bare metal and we're pulling in a lot of other technologies like OpenShift and Cloud Foundry and Kubernetes. And our user survey data backs this up. This is from our most recent user survey. We said, what PAS tools, what container tools are you running on your OpenStack environment today? And this is the responses that we saw. This is not what are you interested in or kind of what's out there in the future. This is what are you doing today? And so people are combining these tools in ways that if you go back a couple of years, we certainly weren't seeing. On the adoption side, what we've seen is we've seen a change in the technology where it's matured but we've also seen a change in the user profile and the customer profile. And some of that is driven by it being easier to deploy, easier to run at smaller scale and to achieve cost savings. Some of that is also driven by an ecosystem that has matured and companies who have found market fit for their products and brought along new users and new customers. And again, we look at our survey data and what we see is a pretty even distribution across all organizations. Is it for big companies? Sometimes that's what people say OpenSex is for big companies. It's absolutely for big companies. It's also for medium-sized companies and it's also for small companies. And this is, again, something that we've seen shift over the years. And a big area that we have a lot of content about at our summits is around the challenges that people face as they adopt cloud. Initially, it was a lot about technology, talent. How do you find the people to run a maturing technology? And now what we see are a lot of the challenges that you face with any shift in technology and that's around culture and processes and how do you absorb new capabilities? And we've got a lot of people who are covering those topics in their different businesses and we're gonna hear from some great users today that are gonna share their stories about how they are approaching this. One of the things that I think is a challenge is our environments continue to become more diverse. A few years ago, what I would hear a lot of companies say is they would say, well, I'm always going to be in my data center. I can't go to the public cloud. Or they would say, I'm cloud first and I'm gonna put everything in public cloud. And those same companies now are moving beyond that kind of single focus and realizing that they actually need a range of options. This is from a Forrester research report from the end of last year and there's a pretty even distribution between this. What's interesting here is you see internal private and hosted private makes up about 68% there. And in the OpenStack community that's been something that we've had a lot of offerings and a lot of deployments around that kind of fall along those lines. But one of those shifts that we've seen with the second generation is actually a new consumption model that has emerged in the market and that has been gaining traction and that is remotely managed private cloud. So it's private cloud that is dedicated to you but it's delivered as a service and it can be on your premises or in a provider premises. So you can get the power, the long term cost savings, the customization of a private cloud but without necessarily being fully responsible for the operational model around it. And that's something that one of our users in just a few minutes, GE is gonna speak about doing. So we have launched a new category in our marketplace today, openstack.org slash marketplace to capture the remotely managed private cloud offerings that are already out there. And I think we're gonna see more of these over the coming year as well. When you're in that kind of environment though, what I think IT leaders are gonna be thinking about over the next few years is if I have a fleet of clouds and they're in these different locations, where do I put my workloads? And as we've talked with users, we've kind of seen this framework that we call the three C's that gives you a few different attributes to look at to think about where should a workload run. And those are compliance, cost and capabilities. When you look at these, you might have kind of an initial take of, oh, well, this is gonna be public cloud, private cloud, whatever. What I think is really interesting is as I've talked with different users, you see that these have variations within them by workload. Compliance, a lot of people think, okay, well that's an easy decision to go to private cloud. But again, we have openstack public clouds like city network in Europe that has built a cloud that is compliant with European financial regulations. They have a pretty big customer, Folxham, which is an insurance company that runs on their public cloud and meets those compliance requirements. So it's not always just a clear break like that. Cost, for public clouds, they offer a great way to get started, to scale quickly, but over the long term, we've seen a number of users who want to move their long running workloads onto an environment that they can recognize long term cost benefits on. And we've had openstack users like Adobe Tube Mogul, Pubmatic, Tapjoy, most recently Snapdeal, talk about this. Snapdeal moved most of their workloads off of a public cloud onto a private cloud they built, and they achieved a 75% cost savings on their infrastructure. Think about if you could save 75% in any major line item in your business and invest that elsewhere. That's a huge deal. And capabilities, again, public clouds, they are moving really quickly with a lot of great features, especially focused at the developer experience. But sometimes there are other capabilities that are required by projects. In Barcelona, we heard from the Square Kilometer Array, which is a massive multi-government science project creating a software-defined distributed radio telescope in South Africa and Western Australia. When it goes online, it's gonna generate 5,000 petabytes a day of data. Think about that. They can't just ship that to a central public cloud. And so what we see is that companies, they have these different workloads, and what they wanna do is they want to develop strategies and develop tools to be able to use multi-cloud as an advantage for their business so that long-term they can build sustainable operating models and also enable rapid innovation and agility in their development processes. And that's what I'm seeing, and what I wanted to share with you this morning. Thankfully, we also have a number of users who are here, and they're going to take this even further. They're gonna share their journeys in these different environments, and they're gonna be able to help us gain some insight into how companies are making these decisions today. And first up, we're gonna be hearing from GE. So let's hear from GE.