>> Announcer: From around the globe, it's theCUBE, with digital coverage of Mirantis Launchpad 2020, brought to you by Mirantis. >> Welcome back I'm Stu Miniman, and this is theCUBE's coverage of Mirantis Launchpad 2020. Big event, multiple tracks powered by theCUBE365. Happy to welcome you to the program. We have a first time guest, Willem du Plessis. He's the Director of Customer Success and Operations with Mirantis. Willem, thanks so much for joining us. >> Hi Stu, thanks for having me. >> So customer success, of course, a big topic in the industry last few years. CX a is so important. Employee success and enabling that, but what, give us a little bit, your background and the purview that you and your team cover. >> Exactly, yeah, so everything under my umbrella would be basically post-sales. The whole customer experience after the point of a sale's been made so the whole account management, thereafter, the success of the accounts, as well as the health of the account, thereafter, that will be anything basically post-sales would be under my umbrella. >> Wonderful, well, the big piece is the shift. As we know, software went from shrink wrapped, and hardware talking about CapX to the cloud really ushered in OpX we're touching more subscription managed services and the like, so Mirantis has a subscription offering. Why don't you lay out for us the new pieces of this and how Mirantis puts together its offerings? >> Yeah, absolutely. So with the launch of our new product, Docker Enterprise Container Cloud, we're making two subscriptions available as well, named ProdCare, which is a 24/7 mission critical support offering and OpsCare, being a fully managed platform as a service subscription. Now, these offerings have been available on the Mirantis Cloud platform side of our business for quite some time, we've been very successful with them, so it's really excited making them available to our Docker Enterprise customers. So what we're trying to achieve with these accounts or with these subscriptions, rather, you know, 30% of the Fortune 100 companies are Mirantis customers, so we work on a day to day basis with their container and Kubernetes initiatives. So when we speak to these customers, there are really two trends that are becoming very clear, the first being the requirements of service providers or vendors being able to provide a true 24/7 experience. What I mean by that is not the ability to just react to an incident on a 24/7 basis. That's what I mean, what I mean is all of these companies would have operation centers spread across the globe. So it is at every hour of the day, it would be business as usual. And what these companies require is a, a partner or a service provider that can match that level, that way of operating. That is the first trend that we're noting. The second piece is really the, the evolution of the dev environment. The dev environment is no longer really seen as a secondary or a lower class citizen, if you want to call it, it's really become part of the whole DevOps pipeline, so it is really part of a mission critical process so that what customers, what we hear from our customers is that they require a real enterprise-grade subscription that they can cover this whole pipeline under and, you know, have the same quality of service from whether that is a dev or a production environment. So if you have a failure on your dev environment and your developer cannot push code, that is, is the same level of criticality than there would then they would be on if the failure was on the production environment. So this whole pipeline is decidedly seen as a mission critical component. And that's a great, that's really where ProdCare comes in. It is really this 24/7 mission critical follow the sun, enterprise-grade subscription that provides our customers with enhanced SLAs that, like I said, we've been running on the Mirantis Cloud platform side for quite some time, we've had some significant success with some really large companies. The second offering that we're making available with, like I said, is OpsCare. Now OpsCare is an ITIL-based managed service subscription, where we provide a platform as a service experience to a customer on their infrastructure of choice. So it is really irrelevant for us what your infrastructure is, whether that is on-prem or in the public cloud, as long as the product can support the infrastructure, you know, the subscription would be available for you and the experience would be very much the same. So what OpsCare, like I said, entails is, is this whole ITIL framework that would include, you know, the monitoring and managing of your alerts, the incident management process, the problem management process, as well as change management that would include the lifecycle management of the whole environment. And that would just enable our customers to run on the latest and greatest offer of our product at all times. And same as with ProdCare that's been available for our brass cloud platform customers for quite a while, and have seen some significant success with that, as well. >> Well, we definitely have seen that growth of the managed care offerings like you're talking about with OpsCare, you know, shift left is so important for companies to be able to focus on what's critically important. As you said, developers need to be enabled, it can't just be waiting for things or be, you know, relegated to, you know, have to wait in line or use something that's not optimal. What are some of those outcomes? What can companies do that they weren't able before? What are some of those successes that you're seeing with the managed care OpsCare solution? >> Yeah, so the real way we OpsCare really comes to its own is allowing the customer ability to focus on what is important to their business and spend less time on what we call, keep the lights on. What I mean by that is they're solely focused on developing the application, developing the workload and spend basically no time on managing the infrastructure and, you know, maintaining it, or, you know, providing, do whatever to, to keep the platform stable, because that is done by Mirantis, already. So for example, if we take 2020 year to date, all the platforms running under OpsCare has an availability number of above four nines, and that is a significant number. So that really just sets such a strong foundation for a customer to just have that sole focus on, on what is important to them and, you know, just sets that foundation for them to develop their workload, to develop their business, and achieve their goals. >> Well, what about when it comes to the managing and monitoring of the environment? What kind of metrics are your customers having? Help us understand what the customer still does themselves or the reporting they're getting and what Mirantis, I'm assuming there's probably a Tam involved for at least some of the larger accounts there. Help us understand that shared responsibility, if you would for these type of environments. >> Yeah, exactly. So the whole ITIL framework, as I explained earlier, incident management, problem management, change, all of that, this is wrapped around why a customer success manager that is, you know, brings a single level of ownership on an accountability, and just have a customer direct for a single point of contact as a business partner. So all this is all our customers, their primary KPI or metric that we look at is just the availability of the platform. That is the primary SLA and thereafter, all of the other things happening, you know, the success of the workload and so on, because there's a lot of things that makes the result of the workload, not just the platform or the infrastructure, it's the quality of the workload, and so on, and so forth. But the main metric our customer would be looking at is that availability number, you know, how available and how stable and accessible is the environment, and, you know, like I said, just removing that requirement for them to spend, basically, no time on the platform or the infrastructure, and just focusing on the workload. >> Yeah, when it comes to in the field, your field, your partners, that line between ProdCare and OpsCare, obviously, the trend is going towards, you know, the fully managed option, but what guidance do you have out there, or what trends do you seeing? Is it a certain size company, that tends to be trending that way? Are there certain verticals that may be are further ahead? What's the reality, today? What do you expect to see over the next kind of six, 12 months? >> Yeah, so most of the companies that we see that as, that is engaging with us on an OpsCare, or managed service engagement, you know, they have the ambitions to go down the block model and build, operate, transfer, you know, to take the operations over themselves, at some point, and we have that option available to them, if they wish to choose it further along the line. What we do find is, is that they, that they don't really, you know, exercise that later on. It is, we do find it is such a smooth integration with our customers, that they tend to stay on OpsCare and see the value. This is actually a money saver for them, if they could, just focus their efforts on building, you know, focusing their time on the workload on top of the platform. From a vertical perspective, it's really anything and everything. We have customers in the science and research, we have TELCOs, large manufacturing, manufacturing, a lot of large organizations. There's really the breadth of the verticals that we see that are utilizing OpsCare and not even to mention ProdCare, that's really everything in there, as well. So it is not a really a subscription that is, that is custom for one vertical. It is basically something that we, that any vertical can actually utilize and find a significant amount of value in. >> All right, well, what final words do you have that you want to leave everyone with today? >> Yeah, so over the last six to nine months, you know, we've invested a significant amount of resources in the Docker Enterprise support business and we just with one focus, and that is just to take the support business to the next level and improve or give the customers an optimal customer experience. So with the availability of all these new subscriptions, I'm really excited to engage with our Docker Enterprise customers with these new, enhanced SLAs and just be able to work with them on these, like I said, enhanced subscriptions and just see, just give them a better customer experience. So, I'm really looking forward to working with them on the subscriptions. >> Willem, thank you so much for all the updates and want to welcome everyone to be sure to check out all the rest of the tracks on the Launchpad 2020 event. I'm Stu Miniman and thank you for watching theCUBE. (soft electronic music)

>>from around the globe. It's the Cube with digital coverage of Miranda's launchpad 2020 brought to you by more antis. >>Hi, I'm stupid man. And this is the cubes coverage of Miran Tous Launchpad 2020. Happy to welcome to the program First time guest William Do places. He's the head of customer success in operations with Miran Tous William. Thanks so much for joining us, >>Steve. Thanks for two. Thanks for having me. >>Yeah, why don't we start with a little bit? You know, customer success operations. Tell us what that's entail, What's what's under your purview, Right? >>So is everything basically, you know, post sales, right? So after a customer has portions, their their subscription, we basically take it from there Going forward, you know, looking after the relationship with the customer, ensure they you know, the whole, you know, subscription fulfillment element off it. Whether that is just bored with that is to cut the relationship management from a post sales perspective and so on, so forth. So that is basically into end from the point off purchase to the renewal face. Would would would fall with any supporting operations. >>Well, that's such an important piece of the whole cloud conversation. Of course, people, you know, we talked for such a long time cap ex op X. We talk about descriptions and manage services. Of course, has been a riel. You know, growth segment of the market place. Love to hear a little bit, you know, What are you hearing from your customers? And, you know, give us the lay of the land As to the various options that that that Miranda is offering today and we'll get into any of the new pieces also. >>Yeah. So the the the options that we're making available for our customers primary called Prod Care, which is a 24 7 mission critical support subscription. Andi Ops Care, which is a fully managed service offering. Um, what we hear from our customers is is, you know, the the the notion of having a development environment and a production environment with different, you know, sls and entitlements and so on. You know that that that notion is disappearing because your divots chain or pipeline is all connected. So you could just think for yourself. If you have a group of developers like 50 or 100 or 1000 developers that are basically standing there still, because they cannot push code because there's a problem or a new issue on the development cloud. But the development cloud is not. Beings is not seen or is treated as a mission critical platform. You know, those developers are standing date stole, so that is a very expensive problem for a customer at that point in time, so that the whole chain, the whole pipeline that makes part off your your develop cycle, should be seen as one entity. And that's what we've seen in the market at the moment that we're realizing with a large customers that are really embracing the kind of the approach to modern applications. Andi. This is why we're making these options available. Thio, our Doctor Enterprise customers We've been running with them for quite a while on the on the Miranda's cloud platform, which is our Infrastructures service offering on. We've had some great success with that, and we now in a position to make that available to our customers. So it's really providing a customer that true enterprise mission critical regardless of time off they the day of the week availability off support whether that is a my question or whether that is really an outage or a failure. You know, you know, you've got that safety net that is that is online and available for you. Thio to sort Whatever problem you have about, you know, that is from the support perspective, you know. And if we go over into the manage service offering we have for on up Skate that is a really hardened Eitel based, um infrastructure or platform as a service offering that we provide eso. We've had some great success. Like I said on the on the Miranda's cloud platform Peace. And we're now making that available for Doc Enterprise customers as well. So that is taking the whole the whole chain through. We look after the the whole platform for the customer and allow the customer to get on with what is important to them. You know, how do they develop their applications? You know, optimize that for their business instead, off spending their times and keep spending their time on keeping the lights on, so to speak, you know? So we take care of all of that. They have that responsibility over to us on DWI. We manage that as our own and we basically could become an extension of their business. So we have a fully integrated into the environment, the whole logging and not monitoring piece we take over the whole life cycle. Management off the environment. We take over, we do the whole change Management piece Incident Management Incident Management piece on. This whole process is truly transparent to the customer. At no point are they, you know, in the dark what's going on where we're going and we have the and the whole pieces wrapped around Bio customer success Manager which is bringing this whole sense off ownership Onda priority. That customer, you've got a single point of contact that is your business partner and that the only piece, the only metric that that individuals measured on is the success off that customer with our our product. So that in a nutshell, at a very high level what these are. But these offerings are all about >>well, we all know these days how important it is toe, you know, make your developers productive. It's funny listening to you, I think back to the Times where you talked about making sure that it's mission critical environment You know, years ago it was like, Oh, well, the developer just gets whatever old hardware we have, and they do it on their own. Now, of course, you know you want Dev in production toe have a very similar environment. And as you said, those manage services offering and be, you know, so important because we want to be able to shift left, let my platform let my vendors take care of some of the things that's gonna be able to enable me to build my new applications toe, respond to the business and do. In fact, I don't want my developers getting bogged down. So do you have any, You know, what are some of the successes there? How do your customers measure that? They Hey, I'm getting great value for going to manage service. Obviously, you know, you talked about that, That technical manager that helps them there. Anybody that's used, you know, enterprise offerings. There's certain times where it's like, Hey, I use it a lot. Other times it's it's just nice to be there, but, you know, why do you bring us in a little bit? Some of the customers, obviously anonymous. You need Teoh you know, how do they say, You know, this is phenomenal value for my business. >>Yes, it's all. It's all about the focus, right? So you're the customer. 100% focus on what is like I said, important to them, they are not being distracted at any point for, you know, on spending time on infrastructure related or platform related issues they purely focused on. Like I said, that is, that is important to their business. Andi, The successes that we see from that it is, is that we have this integration into into our customers like a seamless approach. We work with them is a true, transparent approach to work with our customers. There's a there's an active dialogue off what they developers want to see from the environment, what the customers want to see from from from the environment, what is working well, what we need to optimize. And that is really seeing ah, really good a approach from from from us and we're seeing some some great successes in it. But it all comes down to the customer is focusing on one thing, and that is on what is important to them on. But is there business instead off. You know, like you said, focusing on the stuff that shoot me, that that should be shift left. >>Yeah. And will, um, is there anything that really stands out when you talk about that? The monitoring that you in the reporting that you give the customers Is it all self serve? You know, how did they set that up and make sure that I'm getting valuable data. That's what what my company needs. >>Yes. So that is where your custom success manager comes in is really how to customize that approach to what fit for the customers. So we've got it in the background, very much automated, but we do the tweaks Thio customize it for for the customer that makes sense for them. Some customers want to see very granular details. Other customers just want a glance over it and look at the the high level metrics what they find important. So it is finding that balance and and understanding what your customer find important, and then put that in a way that makes sense for them Now. That might sound might sound kind of obvious, but it's more difficult than you think to put data from the customer That makes sense to them, uh, in their in their context. And then, you know, be in a position where you can take the information that you receive and give your customer the the runway to plan their the application. You know, where are they trending? So be able. Dutilleux. Look. 3452 quarters 345 months to quarters ahead to say this is where you're going to be. If you continue down this path, we might need to look at shifting direction or shift workload around or at Resource is or or, you know, depending on the situation. But it's all about having that insight going forward, looking forward. Rather, um, instead off, you know, playing things by year end, looking, looking at the year. And now because then that ISS that is done and dusted, really. So it's all about what is coming down the line for us and then be able to to plan for it and have an educated conversation of with with with your customer where they want to go. >>You mentioned that part of this offering is making this available for the Docker Enterprise base. Uh, maybe, if you could explain a little bit as to you know, what's gonna be compelling for for those customers. You know what Laurentis is has built specifically for that base? >>Yeah. So, like I said, this is an offering we have available on our Miranda's cloud platform for quite a while. You've seen some great success from it. Um, we're making it now available for the Doctor Enterprise customers. So it is really a true platform as a service offering, um, on your infrastructure of choice, whether that is on prim or whether that is on public cloud, we don't really care. We'll work with customers whichever way it is. And yeah, Like I said, just give that true platform as a service experience for our customers, Onda allow them to to focus on what's important to them. >>Alright, let me let you have the final word. Will tell us what you want your customers to understand about Iran tous when they leave launchpad this year. >>Yeah, So the main thing the main theme that I want to leave with is is that you know, the the we've made significant progress over the last 62 229 months on the doc enterprise side on. We're now in a position where we're taking the next step in making these offerings available for our customers, and we're really for the customers. That's the handful of custom that we have already. My greater to these offerings with getting some really good feedback from them on it is really helping them just thio thio just to expedite. They they, you know, wherever they're gonna go, whatever they want to want to achieve the, you know, expedite, think goals on bond. It is really there to ensure that we provide a customer or customers a true, um, you know, mission critical feeling, uh, giving them the support they need when they needed at the priority or the severity or the intensity that they need as well as they provide them. The ability to to focus on what is important to them on board. Let us look after the infrastructure and platform for them. >>Well, well, okay. Congratulations on Although the work that the team's done and definitely look forward to hearing more in the future. >>Excellent. Thank you very much for your time. >>Be sure to check out all the tracks for Miranda's launchpad 2020 of course. Powered by Cuba 3. 65. Got the infrastructure. The developers Lots of good content. Both live and on demand. And I'm still minimum. Thank you for watching. Thank you.

>> 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)