 Welcome everybody. I'm totally thrilled to be here in London today doing another OpenShift Commons gathering. This has been one of those very last minute serendipitous kind of events. There were a collision of wonderful conferences that are all happening in Europe that got a number of our engineering team from Red Hat and people who are contributing to OpenShift and Commons members who corralled me at Austin, at the Austin gathering and said, hey, you know, we should do something in London. And the London Red Hat solution architects and other folks said they'd back me up. And so within 30 days I think we pulled this one together and you're all here in the room. So I am totally thrilled that we could do this as a community event. And so thank you for coming this morning on a beautiful day in London, which is, I guess, a rarity. I'm going to talk a little bit about OpenShift, what OpenShift Commons is, and why you're here. I threw this slide in because it came across my desk at the last minute the other day. And what was really amazing to me is we've been doing, or I've been doing cloud stuff for the past five years. If you don't know me, my name is Diane Euler. You will know me by the end of the day. I was one of the members of the OpenShift evangelist team during the early V2 days and did community management and now I'm the director of community development. And I'm totally amazed at how fast this is all happening. And this came across my desk the other day. And Gartner expects 25% of all the application workloads to be in the public cloud by the end of this year. I know a lot of you are in financial services or in government and other entities where you may not be using the public cloud so much. But to me, the thing that was astounding that this was 2018. This wasn't 2020, 2024. This is this year. And this year I feel not just for the OpenShift community but for the cloud native community and all of the other assembled and upstream communities is a real big tipping point. And you may have heard a little bit of news that came across the wires late last night about Red Hat acquiring CoreOS and we'll talk a little bit about that in the next presentation if you hadn't heard about that, surprise. So this is really a matter of that tipping point where the community around Kubernetes around the cloud native tooling that we use in OpenShift and OpenShift itself really has gone to the next level and it's astounding to me. Because now at this juncture I think everybody realizes that digital transformation is just a given. And we talk about it a lot at Red Hat. This slide gets used by everybody in marketing at Red Hat. I'm not going to talk about digital transformation from these three perspectives, the applications platform or process. I'm going to talk about it, what it means when we have to transform our communities to support this kind of change and why we did the change to the OpenShift Commons model. So we all know that OpenShift Origin, and many of you probably did it first, downloaded OpenShift Origin from GitHub and played with it, maybe did the mini shift, maybe did one of the VMs in the early days. All of our stuff is out in the open. Everything is done with open communities, with the Kubernetes community, with the Docker community, with OCI, CNCF, and you'll be hearing from some of those folks today as well. And we are trying very hard to do all of this collaboration in the open. And it is that capabilities that makes us able to do the continuous innovation that is what has made OpenShift the success that it is today. So OpenShift is a repository in GitHub. You can go there, you can download it, but it also pulls in, I like the styrofoam because it pulls in all of these other projects, some of them red hat, some of them not red hat, and we push them out into our three flagship products in our business unit, OpenShift Container Platform, OpenShift Digital and OpenShift Online, and now OpenShift IO. I need to update that slide just a little bit, and I'm sure we'll have another update of it too. But it's really been more of an interesting thing. We're pulling in from lots of different areas. So you'll see some of the sponsors that are here today, and thanks again for your support. And lots of other companies are adding services to our ecosystem, are adding feedback into the OpenShift engineering and the OpenShift contributors so that we make this project the success that it is. So Commons came about for an interesting reason. So typically someone like myself who's a community manager for an open source project, whether it's at Red Hat or elsewhere, my whole job is about trying to coerce you into contributing code to my GitHub repo, so I can show contributions to my project. And when we pivoted at OpenShift and at Red Hat to using Kubernetes, we had gone from V2, a Ruby on Rails application on MongoDB, that was very in-house driven. And we had this fire hose of information that we had to get out to you and to our entire global community very quickly, because that's a big pivot from doing this platform as a service on MongoDB and Ruby on Rails that we knew everything about to something where we were collaborating in the open. So we needed to come up with a new community model and a new communications channels, or channels with an S more likely. And in some ways I've become like a TV channel myself. You'll see me doing OpenShift Commons briefings, sometimes two or three a week, just to get the word out there. There's lots of other events that we do each year, but it's really about trying to bring all of you together in more of a peer-to-peer network to promote peer-to-peer interactions with each other. Because if Red Hat has to be in every single conversation with every single person, it just doesn't work. It doesn't scale. I don't scale. The Evangelist team, some of whom are here today, we don't scale. The PMs don't scale. This has to be a community-driven thing. And so today what I'm going to ask you a lot is we've specifically built this day around having longer breaks or longer lunch and put you at round tables so that you'll connect with each other and talk to each other and coach each other. If you go on our Slack channel now, you'll probably find Greg arguing with Larry or somebody else about what monitoring tool. That was the argument on the Slack channel this morning. What was the best way to monitor OpenShift? And none of those people work at Red Hat. And actually none of them are really what traditionally would be called a contributor to OpenShift. They are just people like yourselves who are using OpenShift in production or adding services or providing services or hosting OpenShift somewhere who all have this common network that they're using to leverage, and it's very virtual, which is kind of why I like to do these gatherings and get you physically in the same room with each other because I think the physical face-to-face stuff is really what binds us together as well. We can do a lot virtually, but we do need to have these connections. So we do the Commons Briefings events like this one, gatherings. We have special interest groups that I encourage you to join. We just launched one for machine learning on OpenShift. The next meeting for that is February 9th. There's lots of mailing lists. I'm not going to say you shouldn't do code contributions because we love that too, but we have a very active Slack channel. So if you aren't on it already, during one of the breaks or at lunchtime, find me and I will add you, and we can talk there. The growth of this community is astounding to me. When I started this almost four and a half, five years ago when I started at OpenShift, it was a much smaller world. It was very posy. Today, in the past 100 days, I did a count and you can look at it. It's all out in the open on GitHub. We add them to the participants list on the commons.openshift.org site. As fast as I can get them in. But many of you, there's one new member here. It was Informatic Matters. There we go. One new one just joined and handed me his sign-up sheet today. So there's tons of folks out there who are in similar companies, tangential companies, service providers that you may use that will really kind of help you on your journey with OpenShift, besides the engineers and the contributors that are working on it. So at the moment we're around 330 plus, give or take a few silent people who couldn't get permission to be public about it. And some of you are in the room today and I won't call you out. But I will make you get on stage at some point. There are over 50 countries. So wherever you are in the world, there is somebody probably doing a meet-up and probably deploying OpenShift in that region. So there's a lot of people everywhere. And I try and keep this slide up to date, but it's the most impossible. For us though, the real crux of the matter is all of this collaboration happens with the upstream. It's very important. We all know that Kubernetes is under the hood of OpenShift and we do a lot of work in the Kubernetes world and in other ancillary upstream projects. I don't really care whether we're number one, number two, number three, and total number of contributions to any of these projects. What it is is we're there and we're trying to support all of the tooling that you need to make your production deployments work and all of the tooling we need to help support that as well. Because we are hosting two clouds, basically. OpenShift Online is on AWS and OpenShift Dedicated is on Google's cloud and we are using it ourselves. So we have a good vested interest in making sure all of these things work. Like we mentioned the other day, or yesterday was the other day, it was so soon, 10 o'clock last night, Dan texts me, guess what, we bought CoreOS. I'm like, oh no, how am I supposed to get to sleep now? But one of the things that that does is it actually brings a whole another group of wonderful engineers into the fold to work on OpenShift and all of the related technologies at Red Hat. And so there's going to be a whole lot more people doing it. A whole lot more of us will be working in the different SIGs on Kubernetes. So there's a lot of leadership in the Kubernetes world. It's, I'm not sure, Gary Brown here yet. There's also a number of other folks in the open tracing world, OCI, lots of other places where we're trying to make sure that we are participating actively, bringing that feedback back into the OpenShift engineering team. This slide, too, gets out of date really ridiculously fast as well because I think we've just added Rook to CNCF. There's always new projects coming into the CNCF when we participate actively there. And in the upstream, this panel this afternoon, Chris Anzick will be with us and he can ask you, you can ask him anything. Because really what we look at this as is the collaboration in the open is what makes us a success across all of the streams with all of your peers. Because really it's not just open source, it's open collaboration. It's the connections you make in the room today and hopefully in the futures. And in the room today, and I apologize if I missed a few, are a lot of folks besides the sponsors. I think we had over 50 different companies who were signed up to come today. Hopefully all of you show up, but that's pretty amazing to me because when you think about where we started in the beginning four and a half years ago, it was a much smaller crew and it was a much more red hat crew. There are a lot of red hatters here today. So if you're a red hatter, raise your hand. One of the things about Commons that I really like and was sort of an extra thing that happened was that a lot of the internal folks started joining the Commons conversations too and that's led to a lot of internal education and education between the different projects as well. So it's really, please do connect with these folks. Because even though my job is not to drive contributions into the code base, we have one of the most active and we're continuing to attract new developers to work on the project, so you may do that. And when I started four and a half years ago, there were five external companies contributing to OpenShift and now there's over 70 companies, organizations contributing to OpenShift. And that's without trying to lasso you or beg you or whatever I have to do, grovel to get you to contribute your codes and your fixes and your patches. That's just organically from having this network and having you talk to each other and give us feedback, make pull requests, log issues, bug fixes, come to SIG meetings. It's really pretty awesome and I'm very grateful for this. So this is really what the future looks like to me. It's very way out there and I apologize if I didn't get your logo on there too. There's a lot of you and it's even though we have OpenShift at the center, that's the center of my universe, really you guys are the center of the universe and hopefully today you'll get to meet a lot of your things. I'm talking a little fast because we have a lot on the agenda today. So this was my 10 minute welcome. Did I do kind of 10 minutes? Close. I'm going to bring Dan Walsh up to the stage right after this and he's going to try and figure out how to message the CoreOS and everything container-related the state of the container ecosystem kind of changed. And then we'll have Diogenes and then what I've asked is all of our wonderful sponsors, I've given them five minutes to give their pitch afterwards just before lunch and so we're going to have them come up on stage and do that and we have a nice long lunch and Paul Moray who some of you will recognize that you will recognize him as soon as he comes into the room. I think he's still sleeping because he flew in from the state and he's the one with the red mohawk. He's been working on the open service broker and the service catalog work and he says a pretty action-packed demo and then we have kind of my favorite thing is the upstream this panel where we're bringing in people from all of the different upstreams projects and you can ask them anything and I'm really going to ask you to ask them anything. We'll have a few pre-programmed questions that Michael's going to ask hand-held microphones will go around the room get you to ask your questions and then we have two panels in the end the financial services one and the one in .gov and we'll bring those to a close as quickly as possible because there's beer afterwards and we'll hopefully get you to come and socialize with us and talk to each other and ask more questions and so that's really what this day is about. It's about on the brakes making those connections with everybody again while you're down there on the brakes all of the wonderful sponsors without whom this would not have happened have tables set up and I've invited the Red Hat Open Innovation Labs they have their tables set up I think the Red Hat mobile folks are going to come as well they haven't shown up from Dublin yet but hopefully they'll get here so there's a lot of people to interact with at the lunch breaks, in the coffee breaks please do so they've got lots to tell you about this evening we're going to try and start around 4.50 if I don't talk too long and we think we have the room until 6.30, 7 o'clock until they kick us out or you finish all the beer that we've bought for you so let's get started our first speaker is Dan Walsh he's going to revel us with everything the big reveal about containers so thanks and we'll hook him up and get you started