 Good morning OpenStack. Welcome to Barcelona. Good morning OpenStack. Welcome to Barcelona. Please welcome Mark Collier. Barcelona. Good morning. It's so amazing to be here. This summit I've been really expecting and anticipating for a long time. Barcelona is an incredible city and I know we have a lot of new people who have probably never been to a summit. So we want to make sure that we help you all have a great week. So to start with, just raise your hand if this is your first OpenStack summit that you've ever been to. Wow. All right. So we are all here to help. If you didn't raise your hand, then your job is to go find everyone who did after the keynotes this morning and help them have a great time with OpenStack this week. One of the things that you'll find since you've never been to a summit before and you may not be as familiar with OpenStack and the communities that we do things a little different. One of the things I'm going to be talking about today is how OpenStack is different. The community, the way we do things, we like to have a lot of fun. We also work really hard and we do a lot of work that matters to a lot of people. But it's not a big stuffy conference. This is about as dressed up as I ever get. So please have a good time while you're here and get to know the community. We are here to help. So the first thing we're going to do to help you show you a map. I really like maps. I get lost easily, so I need them. This is where you are now. You're in this giant triangle in the keynote room. You probably know where the convention center is. If you've been looking around, you might have even come here from there where we have registration and the marketplace and most of the breakout sessions. The AC hotel that's adjacent is actually where we have the design summit sessions and a few other sessions. And the Hilton that's also quite close. This is where we have OpenStack Academy. This is where we really put together a lot of different content for you to learn about OpenStack. Hands-on workshops. We've got all kinds of training. And there's a lot you can learn if you spend some time over in the Hilton. Another way you can get plugged in while you're here and have a great time and a productive time is to meet the OpenStack Foundation staff. For the first time, we have a foundation lounge. And if you go over there and you can meet all the different staff members from the OpenStack Foundation, we have a small but very dedicated team. And I'm extremely proud of the team we built at the foundation. It's the smartest, most dedicated people I've ever worked with. So you get a chance to meet them. They'll be, of course, all over the summit participating, but at different times, different members of the foundation staff will be there in the foundation lounge. Lastly, if you need to get ahold of anybody about anything at the summit, the best place to start is to email summit at OpenStack.org. That will reach the foundation team, the event management team. And if you have any questions or problems, we'll get right on top of it. Another thing that we've been working really hard on as a community this year is with the certified OpenStack administrator exam. And we're really excited in just five months. More than 500 people have already taken the exam. But what's exciting to me, actually, is that we've had people from 50 countries take the exam. So one of the things we'll be talking about a lot today is just how global of a movement OpenStack is and how that's the big part of the strength of the community and the strength of how we approach building the software and supporting each other and making each other successful with OpenStack. When it comes to the ecosystem, I want to give a quick shout out to Rackspace, who is actually the company that got the most people certified under the COA exam leading into the summit. So thank you to Rackspace. We also have great support from a lot of other companies that are involved in the COA including SUSA and the Linux Foundation and in particular in China, 99 Cloud is a company there that's really leading the charge in China. There's a lot of exciting OpenStack adoption in that region. The next thing I want to just mention is that we have mobile apps. Hopefully most of you have already downloaded these. So there's Android and iOS apps. But one of the things we really made a big improvement on from the previous summit is the reviews. So it's a lot easier to find the reviews and actually give feedback to the speakers. The only word of caution is all of your feedback is public. So be kind but fair. Everyone will see what you write on there. Of course, I want to have your feedback, especially if it's five stars. So the last piece of Foundation business that I want to do here in terms of giving you some late-breaking news is that yesterday we had a board meeting and we approved four new Gold members to the OpenStack Foundation. These are the companies that put a lot of time and resources into making the Foundation possible. And unfortunately, we weren't able to spend time to look at all the companies that were interested because it was really incredible the amount of interest we've had the last few weeks. But the four that we did talk about and approve were China Mobile, City Network, 99 Cloud, who I mentioned earlier, and Deutsche Telecom, aka T-System. So thank you so much to those companies for contributing to the Foundation. So with all that business out of the way, I want to talk about something called OpenStack. Hopefully you're here to hear about it. One thing that you may notice this week is we've given it a little bit of a different look. So we've actually updated the OpenStack logo. It's been six years. And at the time, you know, it's like when you look back at photos and you see your haircut and you're like, thinking, you know, the 3D look was pretty cool for a while. But these days, that's not in fashion anymore, so according to our designers. So they've gone and redesigned the logo. And this is the new OpenStack logo. You'll see it throughout this week, but it will take a few months to fully roll out on the OpenStack website and for all the different members of the community. So we're happy to help everybody get the latest, greatest and spend the next few weeks and months kind of getting all the different websites and collateral updated. But ultimately, OpenStack is more than a logo. It's actually software that people do, things with that matters. And one of the things I hope some of you had a chance to see when you were walking in and sitting down this morning was an animation that our amazing design team put together called The World Runs on OpenStack. And really the theme there is that there are so many different use cases, different versatile application workloads that people run on OpenStack all over the world, whether it's power grids or mobile phone networks, digital media and entertainment. And we're also going to be using this hashtag a lot this week, Runs on OpenStack. So when you're on social media, if you're running OpenStack, feel free to tag it with Runs on OpenStack and expect we'll have a lot of the Twitter's out there. Now, when it comes to OpenStack users, we have a lot of great insight from meeting users at summits. We do user surveys. But we've commissioned a third-party independent report. And we just got access, early access to some of the numbers this week. And those are from the 451 group. And they really give us an independent look into who's using OpenStack, what they're using it for, gives us a better sense for what type of workloads and industries are adopting OpenStack. One of the things that jumped out at me, looking through the data in the last couple of days, is that it's a very diverse set of industries that are adopting OpenStack. And we know we have a lot of energy companies, transportation, healthcare, insurance, media and entertainment. We're going to hear from a lot of those today. But really the key takeaway for me is that 80% of these companies are not in the technology industry, per se. And so I think that's a really good sign of OpenStack's maturity, that it's now being used for work that matters across all kinds of industries. And different, you know, companies of different sizes. I think sometimes we get really excited about telling you that Walmart's running OpenStack, biggest company in the world, which is amazing. They have a huge cloud, and they run Black Friday and all this kind of stuff. But the reality is that there are lots of companies of different sizes running OpenStack. Another key metric that really jumped out at me was how big these clouds are. So if you look at the number of cores, people are really doing serious work. I mean, they're not messing around when it comes to their OpenStack clouds. Based on the survey, and by the way, they talked to 500 different enterprises running OpenStack. And so, you know, 75% of them are running more than 1,000 cores. And in fact, they talk to a number of users running over 100,000 cores on OpenStack. So people are running it in production. They're doing stuff that really makes their business tick. And the workloads themselves, you know, really run the gamut from Big Data, which we're going to have a great user talk about their Big Data use case in just a few minutes. You know, of course, we have web service, e-commerce, business applications. But people do a lot of things with their OpenStack cloud. It's a general-purpose technology. We also know that people are interested in containers, and we've started to see more and more users bring containers into their organization inside of their OpenStack environments. And one of the really interesting stats that we just uncovered from 4.5.1 Group is that according to their data, people are adopting containers three times faster if they're OpenStack users than if they're not. And so, this really speaks to the way OpenStack has an integration engine bringing new technologies to bear in different organizations. And so, this morning, we're going to actually run through examples of some of these workloads and some of these industries. You know, we've got Enterprise and Big Data. We've got Media and Broadcasting. We've got a really cool telecom NFV demo. And we might use some of this equipment over here. And we've also got an awesome scientific research use case. And, you know, when it comes to work that matters, everything is a little, you know, depends on who you ask, what work actually matters to them. But I think that when you see what's happening in science and research, you're going to be blown away by how much these communities are relying on OpenStack to help them solve the biggest problems in the world. And the reason is that these days, you know, building software is synonymous with solving problems. I think we'll all agree that there are a lot of problems in the world. We haven't solved them all yet. But increasingly, when you build software, that's the way you actually approach solving problems. And I think you'll see that trend throughout all of the users today. And so, when I talk about OpenStack being a little bit different, I want to spend a little bit of time, especially for people that are newer to OpenStack to understand, you know, how we build OpenStack. Because the way we build software is essentially the way we solve problems. It's the way we choose to approach solving problems. And the fact is this can be scary to people, but don't be scared. It's going to be okay. We actually do OpenStack different by design. It's actually a lot different than how a lot of other software is built, even other open source software. It's definitely open source. But, you know, that's really not news these days. Everybody does open source these days. Microsoft does open source. If you look at Facebook and Google, they're competing for who can open source their machine learning or AI algorithms faster, or frameworks faster. So that's super healthy. It's amazing. Love open source. But one of the things about OpenStack that we really believe in is what we call the four opens. So some of you who've been around OpenStack for a while, probably know all about this. But for other people, maybe it's kind of getting into the weeds a little bit on how we make the chorizo. But the fact is open source is just one piece of it. Open community means everybody's involved. Everyone has a seat at the table, especially users. It means we have meetings in the open. If you miss a meeting, you can go back and read. Read the notes in the archives. You know, open design means that later on today, we'll start having the OpenStack Design Summit where discussions will happen in the open about how we should implement or design new features, new functionality, new improvements to the next version of OpenStack, which happens to be Okada. So that development is just kicking off on that. And open development means that we don't wait until the product's done and throw it over the wall, so to speak, and say, okay, now it's open source. That's a very common model. But in my opinion, this model's better. We do it because it's better. And you can have access as much as you can handle to the development process. Every line of code that comes in. You can look at it. You can keep an eye on it. You can monitor it. And you may not put it into production until you're ready, but it's all there. It's all available. And one of the number one reasons why I believe this model is better fundamentally at solving problems is that it brings a much broader set of contributors from all over the world. And the smartest people in the world aren't all in one country, are all in one company, in one organization. They're all over the world. And the more open your process is, the more likely you are to be able to attract and integrate smart people who are passionate about making great software-solving big problems from all over the world. So to take a quick case in point, we just released Newton. This is our 14th release of OpenStack in just six years. So that rapid pace of innovation enabled by this awesome model and the four opens philosophy. And this is a release that we can all be really proud of. And to that end, I would like to take just a moment and say, if you contributed to Newton, please stand up. Amazing. Thank you. That is what a development team looks like under the four opens philosophy. And it's really incredible. And if you think about the diversity of contributors, we had over 2,000 contributors from 300 different organizations. And, you know, we don't just build our software in a small room in Seattle or Silicon Valley. We have people all over the world. That's a different way to build software. I don't think it's as good. And the fact is, yes, we have amazing contributors in Seattle and Silicon Valley. So we love you guys too. But we have people all over the world. We have people from over 50 countries that contributed just to the Newton release. It's a six month release of software. And we're really bringing the best and brightest people to work on work that matters, to work on building software that solves big problems. And when it comes to diversity, I'm extremely proud of how this community has grown and been inclusive when it comes to geographic diversity. But I do have to say that there's always more work to be done. And there is one area that clearly is a glaring example in the tech industry where we've got to do a lot more work when it comes to diversity in that, of course, is gender diversity. Hopefully this is not news to anyone. Unfortunately, gender diversity is nowhere near where it needs to be in tech. And OpenStack's no exception. But we do have some incredible people that have come together and put time and money into helping to address this issue within OpenStack. There's a women of OpenStack group and I definitely encourage you to meet all the leaders within that organization. They have recently launched a mentor program. So you can be a mentor or mentee. You can attend speakers here to this summit. And it's incredible work they're doing. There's a lot of work left to be done. And it's something that we really have to keep investing in. All right. So speaking of investments, Intel is going to love that setup. They recently donated $100,000 to the OpenStack Foundation to promote diversity, help us hire more interns. And so they've really done a lot to step up, put their money where their mouth is when it comes to diversity. And if anybody else out there has $100,000 laying around, just call me. We'll put it to good use. So those are some notes about how we build OpenStack and why I think it's a better method. And now I just want to tell you a quick story about a feature and how it came to be in OpenStack Newton. Of course, there are hundreds of features in every new release. You can't possibly cover them all. Ironic introduced multi-tenant networking. Ironic adoption is growing unbelievably right now. It's the bare metal service. And OpenStack in having multi-tenant networking support in Newton really gives it a much broader use case for different people. You know, pass through VLANs and Courier. You're going to hear a lot more about containers because Nathan Brice has got an awesome setup. Throughout the day of different technologies he's going to be talking about in terms of multi-cloud and public cloud and containers and Courier is a project you're going to want to get to know. Mutable configs in Nova. This is a really great end user or operator really, I should say, benefit because it allows you to make certain configuration changes without having to restart the node. GetMeA Network is both as simple as it sounds and very complicated under the hood. This is something people have wanted for a really long time, which is simply I've got a compute resource, GetMeA Network, it should get you a network. Seems pretty reasonable, but a lot of work went into making that simple, sometimes simple is the hardest technology to deliver. So that's the exciting part of Newton. And the feature in particular I want to talk a little bit more about today is VLAN-Aware VMs. So I mentioned earlier that the four opens philosophy that it brings people from countries all over the world together helps us make sure users have a seat at the table. And we have a set of very vocal users many in the telecom world who've been asking for this for a long time about two years actually. They have a lot of VLANs. Carriers have a lot of networks as it turns out. I'm going to try to break this one in a few minutes. But this particular feature took the effort of people all over the world and to put it in perspective of course we had 2,500 people contribute to Newton. I'm talking about 50 people here but this was an incredible amount of work. And by the way, this group of more than 50 people who developed and reviewed the code that delivered this feature in Newton for these users this includes people who did reviews. And if your company is getting started in OpenStack, wants to make a difference in the community, please do reviews. Reviews really matter. Don't just come in with your wish list and your features. It means so much to the community when you review other people's code. It's a big part of what makes the whole thing work. And so this feature was delivered by more than 50 people from 20 organizations in 15 countries. Since I love maps this is another way you can look at it. And that's really the way we do work that matters when it comes to OpenStack. To OpenStack. And if you want to do work that matters and you want to use OpenStack, there's three steps. This is very high level and then we're going to show it to you in real life. But you're going to deploy the OpenStack services on a set of control nodes. You're going to add your resources that your end users are going to end up connecting to. And then all they really care about is deploying apps. So they're going to deploy their app whether it's a single VM or maybe a distributed application that's in containers or a whole dedicated rack that's for bare metal using the ironic service. So that's kind of OpenStack at a 100,000 foot view. But to show us what it looks like in real life live on stage, I'm excited to bring out the interop engineer from the OpenStack Foundation, Chris Hodge. All right. Hey, Mark. Welcome, Chris. All right, so you obviously, you've got some servers over there. We've deployed OpenStack and got some capacity online. So what's in the cloud over here? So we have 12 servers right here that we assembled this weekend and then we used standalone OpenStack Ironic installed with Bifrost to put down the operating system that we created with OpenStack the skimmage builder. And then once that was done, we packaged and installed a complete OpenStack system with OpenStack COLA. COLA? Okay. That's another container thing you might hear about more tomorrow. Let's take a look at it. So you've got it up and running. We've got our own little mini data center here. All right. So you've got some capacity here. You've got some control nodes. It's all in this fancy little box, which I probably shouldn't touch. But we want to do some work that matters. So to kick things off, why don't you just give me, I'll give you something simple. Why don't you just give me a VM? Mark, it's so easy to use OpenStack I think that you should do it yourself. Oh boy. Okay. So I know we were looking at your admin view here and you very wisely set me up as an end user. So Horizon is going to look a little different. I won't be able to break quite as many things hopefully because I'm just in the end user view. But I'm going to go ahead and create my own VM here. All right. So this is going to be my VM. We've got a nice little wizard here. I'm going to launch it from an image. I'm going to go with the Cirrus image. I don't want to tax your server too much here. Let's do something simple. We'll give it a small size and we're almost done with our wizard here. I just need to connect a network. All right. So I'm going to launch that instance. So I guess this isn't as hard as I thought it would be. But, you know, ultimately we're just doing one VM here. I mean, one VM is pretty cool. You could probably do like a cat versus dog app or something like a voting app. But if you want to really do something serious, you're probably going to want to do more than one VM. No offense to that VM, which is in here. So we've got it up and running now. So I've heard, I've done a little bit of research and it turns out the LAMP stack is powering like half the web or something now. So why don't you give me a LAMP stack and that way we can have like a database server, like a multiple VMs networked. That's something I'm going to need your help with. Well, actually I think with heat orchestration you can probably do it yourself. Wow. Okay. I think I'm seeing a pattern here. All right. So I'm going to go over here in the, excuse me, the end user view. Orchestration is the tab for the heat project or heat service. And I'm going to go ahead and launch a stack. So let's see here. I bet you've gone ahead and put a heat template on my laptop. I knew it. We think it had some time. Okay. Let's see. Let's call it a LAMP. Okay. I'm not going to tell you my password. Don't try to trick me. All right. So, there it is. It creates in progress. So how can we take a look and see what's going on here? Well, the orchestration view gives you, if you click on the stack, it'll give you a nice view of the resources as they're being built. And you can also kind of get a higher and looking at the network topology. All right. Well, things are green. That's usually good. So you say I should look at the network topology. All right. Let's see if we've actually created some networks. Awesome. So we've got networks. We've got a web server, a database server. Somehow you've done it. You've tricked me into doing it myself, like a good IT person. Okay. So look, we've done a couple of things here. We've got a basic VM up and running. As I said, other than voting on cats and dogs, I don't know what else we're going to do with that. So we've got a lamp stack. It's multiple VMs. So I can run like half the web now, but that's not very trendy, right? I mean, running things in production is so last year. So like, I want to do something just crazy. It'll make me one of the cool kids. So give me like Kubernetes and the kitchen sink and all the buzzword dockery things. Well, one of the exciting things about OpenStack is you can now launch your own Kubernetes clusters right from Horizon. OpenStack Magnum. Well, when you say you, you mean you? I mean, you. You should do it. We can have you do it now, Mark. Okay. So I'm going to guess that Magnum must be this container infra tab here because I want some container infrastructure, don't I? All right. Looks like you've already got a Kubernetes cluster template set up here. So let's see what happens when I do my old point and click here. So we're going to give it one master and two nodes. Am I doing okay so far, Chris? Looks good to me. All right. So it says the cluster was successfully created or it's in progress here. So how do we keep an eye on this and see if we're making progress? Well, since Magnum is built on top of heat orchestration, you can just look at the resource view like we did with the other heat template. Okay. So heat, again, is here under orchestration. I'm going to look and see what we've done. I'm going to go back to our stack earlier. This is our new cluster. Wow, look at that. We have deployed Kubernetes or in progress here. It's in progress right now. It's bringing up the Kubernetes master. It'll bring up a couple of workers. In a few minutes, we're going to have Kubernetes running on top of OpenStack. Wow. Okay. Well, thank you so much, Chris. You've helped me be one of the cool kids. Thanks to OpenStack Newton and all of your hard work for this project. Thank you.