 using OpenShift Origin, they're using S2 on AWS and in a few months they're actually going to port all of their big clients and run OpenShift 3 on Azure and that's going to be a lot of good learning that they're going to do and contribute back so that when we want to, as OpenShift at Red Hat, want to do the same thing, we won't be the first ones there. So there's some really good things. So there's hosts and operators, there's everybody who's ever built a cartridge for their service, everyone who's created Docker image like the Elastic folks like MongoDB, all of these other companies out there that are providing services that run or integrate into OpenShift. I consider them part of my community because there's all the hooks that they need to know. We don't want to be reinventing that wheel every single time. So what I'm really trying to do is start to create a bigger idea about what community is from an OpenShift point of view. The other piece of the puzzle is that OpenShift upstreams as you've heard in the last talk, Kubernetes and upstreams Docker. So we're very dependent on those communities as well. So instead of like trying to steal resources from the Kubernetes group, what we've done is sort of flipped it all on its head. We embed our engineering resources like Clayton and Vincent Bats and other people into those projects so that we get the features that we need in those projects. So our community isn't just the people working on OpenShift itself and contributing code to the slash origin GitHub repo. It is a very big or vibrant community. So when I talk about OpenShift Commons, you notice I'm not using the word foundation or some other metaphor for a group of people working together on the single project. It's a new community model in the sense that instead of focusing in on just code contributors, we're trying to open and extend the umbrella so that everyone that is working and contributing to that is part of that process. And the reason we started doing this is you've all heard about how we shifted from v2 to v3. When v3 started coming out, we had to have these conversations, we were repeating ourselves and you may have met some of the evangelists for the OpenShift team. There were, at the time, four of us or five of us. We couldn't scale ourselves. It wasn't about scaling containers, it was we couldn't get enough people and product managers to talk at all those one-on-one conversations. We needed to figure out a way to change the communication model because we needed everybody to be talking to each other, not just talking to Red Hat and we had a fire hose. You know what a fire hose is? You open the hydrant and it just blows up? Everything changed. Containers changed. The language underneath was go. The architecture was using Kubernetes. Anyone who had a cartridge was going to have to create a Docker image. There was a lot of learning that had to go on and we couldn't do it ourselves. So we had to get away to get all the peers talking to each other back and forth. What we've done is try and create a virtual hub at commons.openshift.org. We have mailing lists and SIGs, special interest groups. There's lots of different ways that tiers interact with each other. Operators talk to operators. Some of the folks who are working on best practices around DevOps have conversations with you. I host a lot of podcasts and video conference calls and it's pretty amazing the number of people. Who's in there today? All of the enterprise customers should be in there. If you're an enterprise customer using OpenShift Enterprise, it's time to get your feet wet and become a little open sourcing and start talking to your peers. Sometimes we have a little difficulty with getting permission from large government agencies. So we make amends for that. But this is one of the key tenets of this group is we really like people to identify who they are. So in some mailing lists everybody will be a Gmail address or it will be some sort of anonymous thing. We are really trying to push people to join and identify who they are so they can find their family and their SIGs and they know each other. So there will be some people, some US government agents because I'm an American living in Canada here in the Czech. But some of them like NASA joined OpenShift Commons but others have to remain nameless. But you'll see if you're on the mailing list they are allowed to use their actual corporate or government email. So we've been pretty good. There's a lot of service providers, people who were doing cartridges before, people providing integrations and APIs that work with OpenShift, folks who are running their own clouds like Cisco or Dell or GetUp Cloud, I want to mention. The wonderful thing about working in OpenSource is every conference you go to you meet someone else who's downloaded your OpenSource code and deploy that you didn't know about. And a few months ago I was in Tokyo at the OpenStack summit and I was really frustrated because I only got one talk accepted. Usually they have room and they had like 3,000 people in the call for papers so they really had to call out and anyone who'd ever really talked a lot before didn't get a speaking slot. So I got one very short one and then at the same time as my talk was going on, unbeknownst to me was a small company called Symantec gave a talk and they were going through reviewing all of the platforms of the services that are out there and I was a little worried because I didn't know these people. I didn't know who they were and I wasn't going to get to go and sit in the talk because I was giving my talk at the same time. And I came out of it and everybody came to the booth afterwards and said, I had, you should have been there. Where were you? They were just raving about OpenShift and they had downloaded OpenShift 1 Origin totally anonymously. I had no idea and deployed it and they were using it in production. So that's kind of why I wanted that sort of bent about people identifying who they are so that we can connect. IRC tends to be kind of anonymous and the mailing lists tend to be kind of non, so we're trying to bring people out of their shells so that different groups can do it and all of the enterprise customers are there. So at the moment we have 175 different organizations that are part of the OpenShift Commons. That's actually huge. You know, 35 contributing companies is nice. But for us, when you look at what companies will stand up and say and give feedback and participate in design and the processes around building out something like OpenShift, to have 175 organizations is huge. So how does that sort of break out? There's 175 organizations of that. Any time an organization joins, as many people from that company that want to can come in and be part of the OpenShift. So if you're a company XYZ and you have 20 subsidiaries, just join once and all of those folks can come. So we have a rather active mailing list where people are talking to each other and coming to the briefings. And these briefings, I'm going to talk a little bit more about in a minute, but like a couple of the companies that just joined this week is Threescale and ImpoSys and Weaveworks. So on average we have about two or three new companies popping up, identifying that they're using or integrating with OpenShift and joining the Commons. It's a pretty huge community that we're part of. So when I come to a conference like this and I say, I should know every one of you. It's next to impossible. But what I really want is for every one of you to know each other, not just me, not just Red Hat so we can sell you stuff. We want you talking to each other across the community. And we do talk a lot. I know I do talk a lot. So there's the 35 there. So how do we get that kind of engagement going? And that's really the big chore that I have. It's actually what I really like doing. The mailing list is really the key way that people can find each other. We also on our website have a list of participating organizations. I tend to be myself as a community manager. If someone wants an introduction to someone else at another company, I tend to be the lynchpin for that, probably the blocker for that. So we haven't quite figured out a way to automate that. So if someone says, X, Y, Z, I don't want to reinvent it. We are starting special interest groups. So if you're an operator or an educator or a government person, Telco, and I think there's going to be a networking one, or not a network one, an open stack one coming soon. You can get on a mailing list for that and talk amongst yourselves and we'll host a weekly IRC meeting every Thursday that people can come in and ask questions. And in those IRC sessions, we give updates from the different upstream projects. So maybe one week we'll get an update on Kubernetes, what's going on there, where the roadblocks are there, on Docker, where the roadblocks are there, what's going on, what the new features are or some new features. So that happens in the IRC channels. And then there's the commons briefings. And what that is, is an opportunity for members, non red hat ones, people with services to showcase their beta integrations. So some people have new tools that they want feedback on. So they'll give a presentation and demonstration or something they're passionate about or something that doesn't work. So we end up with trying to do one of those every week is sort of my goal. I do travel a lot. So it ends up being about every other week. So if there's something, there's a topic that you want to hear more about, like Mike Barrett just did that great, what the future is, but there's one chunk of that that someone's interested in. There's a whole slew of briefings that have been recorded from last year that are great. They're on the commons.openship.org site under the briefings page. And if you go to the bottom of that, there's a ton of them that are actually really good. It's not all me talking. I just introduce people, make them talk about their passionate thing or the feature that they're working on. And then there's a Q&A session afterwards. So if you're watching it, listen through or slide the YouTube slide to the end of it, near the end, and you'll hear the questions. And yesterday we did one, Mark Lamarine did a talk about running OpenShift on OpenStack using some of the OpenStack resources rather than just running OpenShift on top and ignoring the fact that there's Cinder and other things that you can use directly. It was actually really good. And the conversation afterwards was probably even more interesting than the presentation. The presentation was really good, too. So the things we're doing with the upstream community, I mentioned, Microsoft Azure, Get Up Cloud is going to launch supposedly in early June. They're already moving their first big clients over to that and doing some testing. We're working with Azure to get support for running .NET containers. That's coming out sometime in the future, too. So you'll probably see a common briefing on that when it gets ready. And we're making sure that we have the interoperability with Azure. We want to make sure that we run on any platform. The OpenShift dedicated but managed hosted version of OpenShift online that is running on using OpenShift 3 will be running on GCP. And OpenShift Online v2, the stuff that you're using now, is running on AWS. You can run it on bare metal, too, and on VMware and lots of other things. But we're really trying hard to make sure that the interoperability is pretty seamless between the different infrastructures that you can run on. Kubernetes, I like to say that OpenShift 3 is the best route to having an enterprise production-ready deployment of Kubernetes. Because when you deploy OpenShift, you get OpenShift 3 and you also get Kubernetes. So depending on which way you want to get it, you can still use Kubernetes directly or you can use the OpenShift on them. So I think they've done a very good job of making those hands-full playbooks and working with heat to make it very simple to deploy anywhere and even on OpenStack. So as I mentioned earlier, we have embedded resources into the Kubernetes project. They've done work on ours. If you remember, a side piece of GearD actually ended up moving over from OpenShift and reincarnating over in Kubernetes. We will be at in force at the Kubicon events that are coming in March. There's Kubicon in London, the EU one in North America. There'll also be another one there. And you will see lots of red hats and lots of OpenShift people there because we really are working in tandem with Google and making that work. So there are tons of atomic presentations here. I'm not going to go too deep dive or talk too much about there, but basically we upstream atomic into OpenShift. So we do a lot of, we make sure everything, all the pieces and parts are there that we need and we're really trying to embrace atomic and help other people understand it better. So you'll see in the Commons briefing, I think four atomic related talks that are recorded and there'll be a number more coming up. In Docker, we've also, Vincent Batz is running around here at the conference. He sources from Red Hat Engineering and put it into the Docker project. Dan Walsh has done a ton of work around securing Docker containers. And we're working on getting some of the patches that we've requested merged into Docker as well. So there's a lot of conversation that goes on between all of these communities. Let's see. So I talked a lot about Commons briefing, some of the upcoming things. Let's see, we just did the OpenShift 3 on OpenStack. We're here at DevCon. There's a service linking and service catalogs thing that's coming up. And then the Identity Management one that's coming up in February 25th is actually quite interesting. Open Unison is a recently open source project from Tremelo Securities. Is that a security? Yeah, Tremelo Security. That helps. They're going to present their integration and then it's used in a lot of large U.S. government agencies to do identity management. So that's sort of what I'm trying to do this year is to get at least 50% of the talks given by non-Red Hat community people. So if you are not a Red Adder and there's something that you're passionate about or there's a side project that you want to talk about or get feedback on, because one of the wonderful things about these talks is that it's a great feedback mechanism. I had a fellow come on mid-year, last year and he had written just this alpha version of a monitoring tool for Docker containers inside of Kubernetes and the whole conversation after his presentation in his brief demo helped him really figure out what was necessary to go to the next level. So this is the kind of interaction that we're really trying to get is to have those conversations about use cases and best practices for open ship and not necessarily just about open ship. And then sometime in April, the Get Up Cloud guys are going to come and talk about running and deploy. Give us an update on their work getting open ship running on Azure and that should be really very interesting and very cool bunch of folks from down in Brazil. So I mentioned Kubicon. Any of you guys going to Kubicon? One. Okay, well you're with Red Hat. Good, I'll make you work in the booth. Tei. So they're supposedly going, they're tentatively saying the North American one will be in Seattle. At each of those events, we will have an open ship commons meetup where what we're going to do is every one of the commons members who are there, it's kind of a social thing. Kind of like we'll drink some beer, we'll talk about the beer, then we'll talk about what they're doing with open ship, where their roadblocks are, what sidecar things that they need us to do and it's more of a push to get the conversation going. There'll be a panel on how to contribute to Kubernetes and Origin on the main stage at Kubicon. So it won't just be me talking, it'll be other folks too. At Red Hat Summit, there's going to be commons panels, there'll be meetups, and we're going to have a whole track, a virtual track of following all the different people and partners from the commons throughout the Red Hat event. The calendar events, which I will show you in a minute too, which is on the readings, will always keep you up to date. But if you join the commons mailing list, which is on the main homepage for commons.openship.org, you can stay up to date. And anyone from Red Hat is welcome too. So if you're not already on it, just put it in there and it's semi-automated. You have to wait for my time zone to catch up, and I will add you into the mailing list and get you on the announce list for that. And we are going to host a CFP. We're going to host something called the OpenShift Gathering. We do everything virtually, because as you all know, OpenShift is pretty global. You saw from the winter of code, there was France and Japan, and the other was Slovakia one. So it was like this huge range of people, and I live in Vancouver and Canada, so I'm on the West Coast, so trying to keep up with all of these things would have to be virtual. But we are committing to having an actual, physical get-together sometime, and it's going to be on the, either right after the Kubecon in August is what we're pushing for. So we'll have two days, and what we're going to do is have Ted Talks from people in different Commons user groups and different parts of the project. And then for the first day, I'm going to have good beer. Did I mention beer? I did mention good beer, because it's in Seattle and we're going to bring microglores in. We're going to do a session there, a workshop on contributor training, because I think it's how to set up your environment so that you can do testing locally and contribute. I think that's one of the things, because OpenShift becomes such a complex application, that it's really good. So if you need to justify to your company why you're coming, that's going to be a number of hands-on workshops. A lot of you might have heard of the roadshows that we did over the past year to get people up to speed on OpenShift-free. It's going to be kind of like that, but more hands-on, mostly hands-on Milino slide projector showing things like what you're seeing right now. So that's really what we're trying to do is keep it as virtual as possible, keep all those peer-to-peer connections connecting, try and get red hat out of the way. So a lot of times, because I seem to be the connector point for a lot of introducing people, but also we're trying to make it so that we're not the only ones talking. So I've been talking for a bit, but that's really the Collins Gatherings 216. You will see a website come up. I encourage you to join the mailing list. You'll see Twitter tweets out from me from the OpenShift Commons and the OpenShift Twitter accounts. You'll see it posted probably up in the IRC when the CFP comes out through the gathering. And we would love to have you all attend. If red hat pays for all of you to come, that would be awesome to Seattle's a wonderful place. But we haven't gotten an official date yet because Kubicon hasn't even given an official date for North America. But that will be, there'll be a call for paper and submissions and hopefully we'll find some funds to subsidize some of the trail travel. But all right, this is how you're going to get notification of all of this. Please go in and join and end up on the mailing list. I will not stalk you. I will not try and sell you anything. I am on the open source side of things. I'm on the origin. I'm not going to try it up to you to OpenShift Enterprise or Dedicated. But you will get the announcement when your developer preview comes out. I will let you guys in on whenever that date is and where the form is to sign up. And we'll get you on board and you'll hear all of the new release announcements coming out through this mailing list. So that's what I had to share. And I'm going to have to give this a lightning talk later so I'm going to do the same thing even faster in a little bit. But so the real crux of it is this OpenShift Commons is really about you meeting each other in a virtual second language place and sharing your information with each other rather than waiting for Red Hat to give it to you and spoon feed it to you. There are a lot of Red Hat presentations there on the briefing site. I'll pull that up for a minute. But while I'm doing that, oops, and that's the other thing. How many of you use Slack? Yeah, how many of you love Slack? No, yeah. So I was going to do a Slack channel but I'm not feeling the love here. I really like IRC, so I'm kind of doing that. So I'm thinking, I see. So the Commons site is right here. And let's see if you want to join the mailing list. But the one thing that I'd really like you to do today is go in, and I'm not going to star me, I'm going to star this repo and pay attention to this repo and like it for me. And I'm hoping that by the time this conference is over we will have over 40 more and we'll break our 1,000 likes and that will make all of the developers very happy. It's not on the screen now. If you refresh it. Oh, I'll refresh it. All right, all right, all right. All right, very good. Oh, look at that, a jump. Okay, who hasn't liked it yet? You don't have your computer with you, okay. All right, well get there soon. So please join us. Thank you all for working on OpenShift, using OpenShift. It's an awesome project to be associated with and I really appreciate all of your time. Thank you. All right, then I'll let you do that and I'll talk. Okay. Just a quick question. Do you have a plan to have some community activity in Shanghai? I would love to come to China. You know, like we have 20% more population. I know. I've been to Beijing and Shanghai many times, but not on behalf of Red Hat. So, give me an excuse and an event. Wow. Yeah. Send me an email. All right, and let me know. And I worked with the sales team that's there, because they're the ones that put the... I don't know their names. Yeah, and we can get that done. Yeah, because we are all, like, open-stack, talkers, clowns, especially, like, clowns. We have been, like, fighting against the clown community. Yeah. Well, I used to work on Cloud Foundry. Yeah, I worked for ActiveState before I came. I worked on Staccato. So I know all the Cloud Foundry stuff. I know where the skeletons are. Yeah, so it's... And they have... What's wonderful about Cloud Foundry is they have really good services on, right? The labs that they do, they're more about providing consulting services than they are about software and teaching people how to be agile and all that. And we're more about software, making sure the software scales and works and stuff. Sometimes it's apples and oranges. So... Well, because they're... If you're going to have a consultancy, you have to have a lot of people, because it's the only way it scales. And so they're all over the place, and they must be in your face quite a bit. Yeah, exactly. We can work on that. We can work on that. All right, so make sure you email me and remind me. Because I'm in Vancouver, B.C., West Coast, China. It's not that bad. Yeah, and now I've been to Bangalore and over there a couple of times, so it's... We could do a tour. What I'd like to do is find the comments members who are there and have them come and present, rather than me talk, and have a community meet up. Yeah, we need to make at least some noise there before we actually get some comment. Yeah, no, we can do that. I can help you with that. I've noticed quite some, like, questions or enthusiastic in the EICChannel OpenShift in China time zone, but it's probably... We're all asleep, yeah. So what we need to do is start figuring out who those people are and inviting them into the comments, getting them to join so that they identify themselves and their companies so that we can connect, so that our companies is really about connect them to each other and to Red Hat and hopefully we can grow a community there. Yeah. And because, as I said, we don't have the budget for... and we can't clone ourselves, you know. And we're not about being a consulting services group. We're engineers. Right, totally. So what did you call me? I was with Red Hat. I thought so. Where did you go? I studied my own stuff. I was taking training for Docker. Oh, cool. I was in the book last time, you remember. I was in the book on Docker. Did you... All right, good. I knew I'd seen your face and I thought you were with Red Hat. I left him two months back. Actually, I was there and I was there with the promise to Red Hat. I kind of just forgot about that. I registered with my Gmail or whatever. Cool. All right, now we'll get you in and you can give a presentation and teach Docker stuff. Yeah, sure. I might become something in the process of the project. So I just saw the name. So basically, from what happened I think this is war-slogging that I learned. Well, I can connect with those people. Yeah. Because basically, they don't... they just... they don't... Yeah. And atomic and Kubernetes is a good combination. Yeah, of course. But I think the way that I try and describe OpenShift today is you deploy OpenShift so it's... It doesn't really cost me anymore but I think it's the same subscription. It's pretty cool. I just want to say hi. Yeah, I need an excuse to come back to Bangla. I haven't been in like 10 years. I'm sure everything has changed. Because everything has changed every time you go there. It's totally like the town. We got this new place there in Bangla, yeah. This company. I mean, Red Hat. Yeah, so... I think cluster 3 cluster 3 cluster 3 has been bought by the government. So, cluster and Kubernetes border and other issues are really kind of frightening. I don't think that... I don't think so. Yeah. That's a hard question. Oh, OK. OK. We have a center to stay. It's common. So, at least we got out. We're really excited to see a nice one in China. We have to get out. What? A whole bunch of companies are in the same center. And it might be a better place for you to stay if you want to share it. Well, so the... I guess the... You know, that's... We're wanting to get... Yeah, I'm sure you have that. Yeah. And I think we just have all of that. So, all of the centers are of course... You could like... Yes. And it's always a... Because I think folks that are just... From our perspective, we really appreciate that. We are happy to have this. And it's just really nice to be here. And really, from our perspective, yeah. We want to help... ... We're trying to help them to... ... ... ... ... .. ... I think that if you look at their pool of milk, so access to that has three specifics. You would love to test it in the air for additional use. That's what I'm asking about. What difference does that have with that? Short and long hours. Short and long hours. You can do all kinds of things. Who's right? Who's wrong? Who's right? Who's right? Who's right? Who's right? Who's right? Who's right? Who's left? Who's right? Who's left? Who's right? Who's left? Who's right? No, what are you talking about? What are you talking about? I have a question. What's the difference between the two? What do you think of this? I think I'm gonna go back. No, that's good. You have it. I'm gonna go back. You're still very interesting. No, no. I'm just gonna go back. I'm just gonna go back. I'm just gonna go back. I'm just gonna go back. I'm just gonna go back. That's good. Take care. It's good to see you. No. No, they had it on the ground. And they got it, so it was... No, they had it on the ground. No, they had it on the ground. They had it on the ground. I bought it 15 years ago, 20 years ago. No, they had it on the ground. No, they had it on the ground. They had it on the ground. Well done. It's done. It's done. And it's done. No, they had it on the ground. It was interesting to hear from this person that it was going to get worse. And he recognized the result, because in Monday morning we started at Vastro. So on Sunday, as the concert was going to be, I had to look out for it, and I was looking at it. But while I was looking at those buttons, it looks like it holds everything together. And that's the first one, and the first one here was quite big. Yes. Well, I guess it holds everything together. Yes. No, no, no, no, no. But he's here, because he has everything. I think he has something. I think that he will be able to have some kind of middle-aged blazer in D-105C. So I don't know if he will be there, because there will be some kind of... Yes, I remember. And in the back, it's free. Yes. I see. I'll teach him a lesson.