>> Narrator: From Copenhagen, Denmark, it's theCUBE, covering KubeCon, and CloudNativeCon Europe 2018. Brought to you by the Cloud Native Computing Foundation, and its ecosystem partners. >> Okay, welcome back, everyone, live coverage here in theCUBE, in Europe, at Copenhagen, Denmark for KubeCon Europe 2018. This is theCUBE. We have the CNCF, at the Cloud Native Computing Foundation, part of the Linux Foundation. I'm John Furrier, co-host of theCUBE, with Lauren Cooney, the founder of SparkLabs, new venture around open source and innovation. Our analysts here, today with theCUBE, and our two guests are Michael Hausenblas, who's the direct developer advocate at Red Hat. Diane Meuller's the director of community development at Red Hat, talking about OpenShift, Red Hat, and just the rise and success of OpenShift. It's been really well-documented here on theCUBE, but certainly, in the industry, everyone's taking notice. Great to see you again, welcome to theCUBE, good to see you. >> Thank you. >> And wonderful to be here again. >> So, first of all, a lot of big news going on. CoreOS is now part of Red Hat, so that's exciting. I haven't had a chance to talk to you guys about that yet here on theCUBE, but great, great puzzle piece from the industry there for you guys, congratulations. >> Yeah, it's been a wonderful collaboration, having the CoreOS team as part of the Red Hat, and the OpenShift team, it's just a perfect fit. And the team from CoreOS, they've always been my favorite people. Alright, and Brandon Philips and the team over there are just awesome. And to have the expertise from Tectonics, the operator framework, which you'll hear more about here at KubeCon EU this week, to have Quay under the wings of Red Hat now, and Quay is a registry with OpenShift or with any other Kubernetes, you know, the stuff that they brought to the table, and the expertise, as well as the wonderful culture that they had, it was such a perfect fit with OpenShift. >> And you know, you guys bring a lot to the table, too. And I was, I mean, I've been kind of critical of CoreOS in the past, in a good way, 'cause I love those guys. I had good chats with them over the years, but they were so pure open-source guys, like Red Hat. >> Diane: Well, there's nothing wrong with being pure open-source. (laughing) >> No, no, I'm cool with that, but you guys have perfected the business more, you have great customers. So one of the things that they were always strong at was the open-source piece but when you start to monetize, and you start to get into the commercialization, it's hard for a start-up to be both, pure open-source and to monetize. You guys now have it together, >> Yeah. >> Great fit. >> So, it's a wonderful thing. We, on the OpenShift side, we have the OpenShift Commons, which is our open-source community, and we've sort of flipped the model of community development and that's at Red Hat. And one of the things is, they've been really strong, CoreOS, with their open-source projects, whether etcd, or you know, a whole myriad of other things. >> Well, let's double down on that. I want to get your thoughts. What is this OpenShift Commons? Take a minute to talk about what you guys had. You had an event Monday. It was the word on the streets, here in the hallways, is very positive. Take a minute to explain what happened, what's going on with that program? >> So OpenShift Commons is the open-source community around OpenShift Origin, but it also includes all the upstream projects that we collaborate with, with everybody from the Kubernetes world, from the Promytheus, all the CNCF project leads, all kinds of people from the upstream projects that are part of the OpenShift Ecosystem, as well as all the service providers and partners, who are doing wonderful things, and all the hosts, like Google, and you know, Microsoft Azure folks are in there. But, we've kind of flipped the model of community development on its head. In the past, if you were a community manager, which is what I started out as, you were trying to get people to contribute to your own code base. And here, because there's so much cross-community collaboration going on, we've got people working on Kubernetes. We got Kubernetes people making commits to Origin. We work on the OCI Foundation, trying to get the container stuff all figured out. >> So when you say you flipped the model, you mean there's now multiple-project contributions going on, or? >> Yeah, we've got our fingers in lots of pies now, and we have to, the collaboration has to be open, and there has to be a lot of communication. So the OpenShift Commons is really about creating those peer-to-peer networks. We do a lot of stuff virtual. I host my own OpenShift Commons briefings twice a week, and I could probably go to three or four days a week, and do it, because there's so much information. There's a fire hose of new stuff, new features, new releases, and stuff. Michael just did one on FAS. You did one before for the machine-learning Saigon OpenShift on Callum. >> Hold on, I want to just get your thoughts, Michael, on this, because what came up yesterday on theCUBE, was integration glue layers are really important. So I can see the connection here. Having this Commons model allows people to kind of cross-pollenate, one. Two, talk about integration, because we've got Promytheus, I might use KubeFlow. So there's new things happening. What does this mean for the integration piece? Good for it, or accelerating it? What's your thoughts? >> Right, right, right. So, I mainly work upstream which means when it is KubeFlow and other projects. And for me, these kind of areas where you can bring together both, the developers, and the end users, which is super important for us to get the feedback to see where we really are struggling. We hear a lot from those people that meet there, what their pinpoints are. And that is the best way to essentially shape the agenda, to say, well, maybe let's prioritize this over this other feature. And as you mention, integration being one big part, and Functions and Service being, could be considered as the visual basics of applications for Cloud Native Computing. It can act as this kind of glue between different things there. And I'm super excited about Commons. That's for me a great place to actually meet these people, and talk with them. >> So the Commons is almost a cross-pollination of folks that are actually using the code, building the code, and they see other projects that makes sense to contribute to, and so it's an alignment where you allow for that cross-pollination. >> It's a huge series of conversations, and one of the things that is really important to all of the projects is, as Michael said, is getting that feedback from production deployments. People who are working on stuff. So we have, I think we're at around 375 organizational members, so there's... >> John: What percentage of end-user organizations, do you think? >> It's probably about 50/50. You know, you can go to Commons.OpenShift.org, and look up the participants list. I'm behind a little bit in getting everybody in there, but-- >> John: So it's a good healthy dose of end-users? >> It's a good healthy dose of end-users. There's some special interest groups. Our special interest groups are more around used cases. So, we just hosted a machine-learning reception two nights ago, and we had about 200 people in the room. I'd say 50% of them were from the KubeFlow community, and the other 50% were users, or people who are building frameworks for our people to run on OpenShift. And so our goal, as always, is to make OpenShift the optimal, the best place to run your, in this case, machine-learning workloads, or-- >> And I think that's super critical, because one of the things that I've been following a little bit, and you know, I have your blog entry in front of me, is the operator framework, and really what you're trying to do with that framework, and how it's progressing, and where it's going, and really, if you can talk a little bit about what you're doing there, I think that would be great for our viewers. >> So what I'm going to do is I'm going to make sure you get Brandon Philips here, on your KubeFlow, sometime this week, 'cause I don't want to steal the thunder from his keynote tomorrow morning-- >> Lauren: Well, drop a couple hints. (laughs) >> John: Share a little bit, come on. >> So the operator stuff that CoreOS, and they brought it to the table, so it's really their baby. They had done a lot of work to make sure that they had first-class access to be able to inject things into Kubernetes itself, and make it run. And they're going to do a better technical talk on it than I am, and make things run. And so that what they've done is they've opened up and created an STK for operators, so other people can build more. And we think, this is a tipping point for Kubernetes, and I really don't want to steal any thunder here, or get in over my head, is the other part of it, too. >> I think Brandon is the right person to talk about that. >> Brandon, we'll drag Brandon over here. >> I'm super excited about it, but let's-- >> Yeah, let's talk about why you're super excited about it. Is there anything you can kind of tell us in terms of what? >> Enables people to run any kind of workload in communities, in a reliable automated fashion. So you bring the experience that human operators have into software. So you automate that application, which makes it even more suitable to run your enterprise application that so far might have not been the best place to run. >> Lauren: That's great, yeah. >> And yeah, I'm also looking forward to Brandon explaining the details there. >> So I think it's great hearing about that, and we talk a lot about how it's great for users. It's great, you know, operators, developers, how they're building things out, and things along those lines. But one of the things that we are not hearing a ton about here, and we want to hear more about, is security. Security is increasingly important. You know, we're hearing bits and pieces but nothing's really kind of coming together here and what're your thoughts on that? >> Security, I was recently, when I blogged about it, and people on Twitter said, well, is that really true that, you know, couldn't this secure body fall? It's like, well, all the pieces are there. You need to be aware of it. You need to know what you're doing. But it is there, right? All the defaults might not be as you would expect it, but you can enable it. And I think we did a lot of innovations there, as well. With our back, and security context, and so on. And, actually, Liz Rice and myself are working on putting the security cookbook, and for a variety that will come out later this year. We're trying to document the best practice, because it is early days, and it's quite a range of things. From building container images in a secure way, to excess control, and so on, so there's a lot of stuff (mumbles). >> What're some of the end-user feedback sessions, or feedback data that you're getting from these sessions? What is some of the things you guys are hearing? What's the patterns? What's the things that are boiling up to the top? >> Well, there's so many. I mean, this conference is one of those ones where it's a cornucopia of talks, and trying to, I just wrote a little blog post called, The Hitchhiker's Guide to KubeCon. It's on blog.openshift.com. And because, you could spend all of your time here in a different track, and never leave it, like Security 1, or in Operations 1, or-- >> John: There's a lot of great content. >> I think the Istio stuff is probably the hottest thing I'm hearing people going to. There was a great deep-dive training session, hands-on on Monday, here, that got incredible feedback. IBM and Google did that one. We had a lot of customer talks and hands-on training sessions on Monday. Here, there are pretty much, there's a great talk coming up this afternoon, on Kube Controllers that Magic... I think that's at 11:45-ish. There are a lot of the stuff around Service Fish, and service brokers, is really kind of the hot thing that people are looking for to get implemented. And we've got a lot of people from Red Hat working on that. There's, oh man, there's etcd updtes, there's a bazillion things going-- >> John: It's exploding big time here. >> Yeah. >> No doubt about it. >> The number one thing that I'm seeing last couple of months, being onsite with customers, and also here, is that given that Kubernetes is now the defective standard of container authorization, people are much more willing to go all-in, you know? >> Yeah. >> A lot of folks were on the fence, for a couple of years, going like, which one's going to make it? Now, it's kind of like, this is a given. You couldn't, you know, just as Linux is everywhere on the servers, that's the same with Kubernetes, and people are now happy to really invest, to like, okay, let's do it now, let's go all in. >> Yeah, and, what we're hearing, too, just stepping back and looking at the big picture is we see the trend, kind of hearing and connecting the dots, as the number of nodes is going to expand significantly. I mean, Sterring was on stage yesterday, and we heard their, and still small, not a lot of huge, not a lot on a large scale. So, we think that the scale question is coming quickly. >> Well, I think it already came, alright? In the machine-learning reception that we had at night, one of the gentleman, Willem Bookwalter, from Microsoft, and Diane Feddema, from Red Hat, and a whole lot of people are talking about how do we get, because machine-learning workloads, have such huge work, you know, GPU, and Google has their TPU requirements to get to scale, to run these things, that people are already pushing the envelope on Kubernetes. Jeremy Eater from Red Hat has done some incredible performance management work. And on the CNCF blog, they've posted all of that. To get the optimal performance, and to get the scale, is now, I think, one of the next big things, and there's a lot of talks that are on that. >> Yeah, and that's Istio's kind of big service mesh opportunity there, is to bring that to the next level. >> To the next level, you know, there's going to be a lot of things that people are going to experience trying to get the most out of their clusters, but also, I think we're still at the edge of that. I mean, someone said something about getting to 2,500 nodes. And I'm like, thinking, that's just the beginning, baby. >> Yeah, it's going to be more, add a couple zeroes. I got to ask you guys, I got to put you both on the spot here, because it's what we do on theCUBE. You guys are great supporters of theCUBE. We appreciate that, but we've had many conversations over the years with OpenShift, going back to OpenStacks, I don't know what year it was, maybe 2012, or I don't know. I forget what year it was. Now, the success of OpenShift was really interesting. You guys took this to a whole 'nother level. What's the reaction? Are you, as you look back now on where you were with OpenShift and where you are today, do you pinch yourself and say, damn? Or what's your view? >> Red Hat made a big bet on Kubernetes three years ago, three and a half years ago, when people thought we were crazy. You know, they hadn't seen it. They didn't understand what Google was trying to open-source, and some of the engineers inside of Red Hat, Clayton Coleman, Matt Hicks, a lot of great people, saw what was coming, reached out, worked with Google. And the rest of us were like, well, what about Ruby and Rails, and Mongo DB, and you know, doing all this stuff? And like, we invested so much in gears and cartridges. And then, once they explained it, and once Google really open-sourced the whole thing, making that bet as a company, and pivoting on that dime, and making version 3.0 of OpenShift and OpenShift Origin, as a Kubernetes-based platform, as a service, and then, switching over to being a container platform, that was a huge thing. And if you had talked to me back then, three years ago, it was kind of like, is this the right way to go? But, then, you know, okay. >> Well, it's important to history to document that point, because I remember we talked about it. And one of the things, you guys made a good bet, and people were scratching their head, at that time. >> Oh yeah. >> Big time. But also, you've got to give credit to the community, because the leaders in the community recognized the importance of Kubernetes early on. We've been in those conversations, and said, hey, you know, we can't screw this up, because it was an opportunity. People saw the vision, and saw it as a great opportunity. >> I think, as much as I like the technical bits, as an engineer, the API being written and go, and so on, I really think the community, that is what really makes the difference. >> Yeah, absolutely does. >> If you compare it with others, they're also successful. But here with CNCF, all the projects, all the people coming together, and I love the community, I really-- >> It's a case study of how to execute, in my opinion. You guys did a great job in your role, and the people didn't get in the way and try to mess it up. Great smart people understood it, shepherded it through, let it grow. >> And it really is kudos to the Kubernetes community, and the CNCF, for incubating all of this wonderful cross-community collaboration. They do a great job with their ambassadors program. The Kubernetes community does amazing stuff around their SIGs, and making sure that projects get correctly incubated. You know, they're not afraid to rejig the processes. They've just done a wonderful thing, changing the way that new projects come into the Kubernetes, and I think that willingness to learn, learn from mistakes, to evolve, is something that's really kind of unique to the whole new way of thinking about open-source now, and that's the change that we've seen. >> And open-source, open movements, always have a defining moment. You know, the OSI model, remember? That stack never got fully standardized but it stopped at a really important point. PCPIP, IP became really important. The crazy improbability world, CISCO, as we know, and others. This is that kind of moment where there's going to be a massive wealth creation, value creation opportunity because you have people getting behind something, as a de facto standard. And then, there's a lot of edge work around it that can be innovated on. I think, to me, this is going to be one of those moments we look back on. >> Yeah, and I think it's that willingness to adjust the processes, to work with the community, and you know, that Kubernetes, the ethos that's around this project, we've learned from a lot of other foundations' mistakes. You know, not that they're better or worse, but we've learned that you could see the way we're bringing in new projects, and adding them on. We took a step back as a community, and said okay, this is, we're getting too many, too soon, too fast. And maybe, this is not quite the right way to go. And rather than doing the big tent umbrella approach, we've actually starting doing some really re-thinking of our processes, and the governing board and the TOC of the CNCF, have done an awesome job getting that done. >> When you got lightning in a bottle, you stop and you package it up, and you run with it, so congratulations. Red Hat Summit next week, we'll be there, theCUBE. >> Oh yeah. >> Looking forward to going deep on this. >> Well, the OpenShift Commons Gathering is the day before Red Hat Summit. We've completely sold out, so sorry, there's a waitlist. We've gone from being, our first one, I think we had 150 people come. There's over 700 people now coming to the Gathering one, and 25 customers with production deployments speaking. This is the day before Red Hat Summit. And I lost count of how many OpenShift stories are being told at Red Hat Summit. It's going to be a crazy, jetlag-y week, next week, so-- >> Congratulations, you guys got a spring in your step, well done. OpenShift going to the next level, certainly the industry and Kubernetes, a service mesh as Istio. Lot of great coverage here in theCUBE, here in Europe for KubeCon 2018 in Copenhagen, Denmark. I'm John Furrier, and Lauren Cooney, the founder of SparkLabs. I'm with theCUBE, we'll be back with more live coverage. Stay with us! Day Two, here at KubeCon, we'll be right back. (upbeat techno music)