>> Announcer: Live from Boston, Massachusetts, it's theCUBE, covering Red Hat Summit 2019. Brought to you by Red Hat. >> Welcome back here on theCUBE, joined by Stu Miniman, I'm John Walls, as we wrap up our coverage here of the Red Hat Summit here in 2019. We've been here in Boston all week, three days, Stu, of really fascinating programming on one hand, the keynotes showing quite a diverse ecosystem that Red Hat has certainly built, and we've seen that array of guests reflected as well here, on theCUBE. And you leave with a pretty distinct impression about the vast reach, you might say, of Red Hat, and how they diversified their offerings and their services. >> Yeah, so, John, as we've talked about, this is the sixth year we've had theCUBE here. It's my fifth year doing it and I'll be honest, I've worked with Red Hat for 19 years, but the first year I came, it was like, all right, you know, I know lots of Linux people, I've worked with Linux people, but, you know, I'm not in there in the terminal and doing all this stuff, so it took me a little while to get used to. Today, I know not only a lot more people in Red Hat and the ecosystem, but where the ecosystem is matured and where the portfolio is grown. There's been some acquisitions on the Red Hat side. There's a certain pending acquisition that is kind of a big deal that we talked about this week. But Red Hat's position in this IT marketplace, especially in the hybrid and multi-cloud world, has been fun to watch and really enjoyed digging in it with you this week and, John Walls, I'll turn the camera to you because- >> I don't like this. (laughing) >> It was your first time on the program. Yeah, you know- >> I like asking you the questions. >> But we have to do this, you know, three days of Walls to Miniman coverage. So let's get the Walls perspective. >> John: All right. >> On your take. You've been to many shows. >> John: Yeah, no, I think that what's interesting about what I've seen here at Red Hat is this willingness to adapt to the marketplace, at least that's the impression I got, is that there are a lot of command and control models about this is the way it's going to be, and this is what we're going to give you, and you're gonna have to take it and like it. And Red Hat's just on the other end of that spectrum, right? It's very much a company that's built on an open source philosophy. And it's been more of what has the marketplace wanted? What have you needed? And now how can we work with you to build it and make it functional? And now we're gonna just offer it to a lot of people, and we're gonna make a lot of money doing that. And so, I think to me, that's at least what I got talking to Jim Whitehurst, you know about his philosophy and where he's taken this company, and has made it obviously a very attractive entity, IBM certainly thinks so to the tune of 34 billion. But you see that. >> Yeah, it's, you know, some companies say, oh well, you know, it's the leadership from the top. Well, Jim's philosophy though, it is The Open Organization. Highly recommend the book, it was a great read. We've talked to him about the program, but very much it's 12, 13 thousand people at the company. They're very much opinionated, they go in there, they have discussions. It's not like, well okay, one person pass this down. It's we're gonna debate and argue and fight. Doesn't mean we come to a full consensus, but open source at the core is what they do, and therefore, the community drives a lot of it. They contribute it all back up-stream, but, you know, we know what Red Hat's doing. It's fascinating to talk to Jim about, yeah you know, on the days where I'm thinking half glass empty, it's, you know, wow, we're not yet quite four billion dollars of the company, and look what an impact they had. They did a study with IDC and said, ten trillion dollars of the economy that they touch through RHEL, but on the half empty, on the half full days, they're having a huge impact outside. He said 34 billion dollars that IBM's paying is actually a bargain- >> It's a great deal! (laughing) >> for where they're going. But big announcements. RHEL 8, which had been almost five years in the works there. Some good advancements there. But the highlight for me this week really was OpenShift. We've been watching OpenShift since the early days, really pre-Kubernetes. It had a good vision and gained adoption in the marketplace, and was the open source choice for what we called Paths back then. But, when Kubernetes came around, it really helped solidify where OpenShift was going. It is the delivery mechanism for containerization and that container cluster management and Red Hat has a leadership position in that space. I think that almost every customer that we talked to this week, John, OpenShift was the underpinning. >> John: Absolutely. >> You would expect that RHEL's underneath there, but OpenShift as the lever for digital transformation. And that was something that I really enjoyed talking to. DBS Bank from Singapore, and Delta, and UPS. It was, we talked about their actual transformation journeys, both the technology and the organizational standpoint, and OpenShift really was the lever to give them that push. >> You know, another thing, I know you've been looking at this and watching this for many many years. There's certainly the evolution of open source, but we talked to Chris Wright earlier, and he was talking about the pace of change and how it really is incremental. And yet, if you're on the outside looking in, and you think, gosh, technology is just changing so fast, it's so crazy, it's so disruptive, but to hear it from Chris, not so. You don't go A to Z, you go A to B to C to D to D point one. (laughing) It takes time. And there's a patience almost and a cadence that has this slow revolution that I'm a little surprised at. I sense they, or got a sense of, you know, a much more rapid change of pace and that's not how the people on the inside see it. >> Yeah. Couple of comment back at that. Number one is we know how much rapid change there is going because if you looked at the Linux kernel or what's happening with Kubernetes and the open source, there's so much change going on there. There's the data point thrown out there that, you know, I forget, that 75% or 95% of all the data in the world was created in the last two years. Yet, only 2% of that is really usable and searchable and things like that. That's a lot of change. And the code base of Linux in the last two years, a third of the code is completely overhauled. This is technology that has been around for decades. But if you look at it, if you think about a company, one of the challenges that we had is if they're making those incremental change, and slowly looking at them, a lot of people from the outside would be like, oh, Red Hat, yeah that's that little Linux company, you know, that I'm familiar with and it runs on lots of places there. When we came in six years ago, there was a big push by Red Hat to say, "We're much more than Linux." They have their three pillars that we spent a lot of time through from the infrastructure layer to the cloud native to automation and management. Lots of shows I go to, AnsiballZ all over the place. We talked about OpenShift 4 is something that seems to be resonating. Red Hat takes a leadership position, not just in the communities and the foundations, but working with their customers to be a more trusted and deeper partner in what they're doing with digital transformation. There might have been little changes, but, you know, this is not the Red Hat that people would think of two years or five years ago because a large percentage of Red Hat has changed. One last nugget from Chris Wright there, is, you know, he spent a lot of time talking about AI. And some of these companies go buzzwords in these environments, but, you know, but he hit a nice cogent message with the punchline is machines enhance human intelligence because these are really complex systems, distributed architectures, and we know that the people just can't keep up with all of the change, and the scope, and the scale that they need to handle. So software should be able to be helping me get my arms around it, as well as where it can automate and even take actions, as long as we're careful about how we do it. >> John: Sure. There's another, point at least, I want to pick your brain about, is really the power of presence. The fact that we have the Microsoft CEO on the stage. Everybody thought, well (mumbles) But we heard it from guest after guest after guest this week, saying how cool was that? How impressive was that? How monumental was that? And, you know, it's great to have that kind of opportunity, but the power of Nadella's presence here, it's unmistakable in the message that has sent to this community. >> Yeah, you know, John, you could probably do a case study talking about culture and the power of culture because, I talked about Red Hat's not the Red Hat that you know. Well, the Satya Nadella led Microsoft is a very different Microsoft than before he was on board. Not only are they making great strides in, you know, we talk about SaaS and public cloud and the like, but from a partnership standpoint, Microsoft of old, you know, Linux and Red Hat were the enemy and you know, Windows was the solution and they were gonna bake everything into it. Well, Microsoft partnered with many more companies. Partnerships and ecosystem, a key message this week. We talked about Microsoft with Red Hat, but, you know, announcement today was, surprised me a little bit, but when we think about it, not too much. OpenShift supported on VMware environments, so, you know, VMware has in that family of Dell, there's competitive solutions against OpenShift and, you know, so, and virtualization. You know, Red Hat has, you know, RHV, the Red Hat Virtualization. >> John: Right, right, right. >> The old day of the lines in the swim lanes, as one of our guests talked about, really are there. Customers are living in a heterogeneous, multi-cloud world and the customers are gonna go and say, "You need to work together, before you're not gonna be there." >> Azure. Right, also we have Azure compatibility going on here. >> Stu: Yeah, deep, not just some tested, but deep integration. I can go to Azure and buy OpenShift. I mean that, the, to say it's in the, you know, not just in the marketplace, but a deep integration. And yeah, there was a little poke, if our audience caught it, from Paul Cormier. And said, you know, Microsoft really understands enterprise. That's why they're working tightly with us. Uh, there's a certain other large cloud provider that created Kubernetes, that has their own solution, that maybe doesn't understand enterprise as much and aren't working as closely with Red Hat as they might. So we'll see what response there is from them out there. Always, you know, we always love on theCUBE to, you know, the horse is on the track and where they're racing, but, you know, more and more all of our worlds are cross-pollinating. You know, the AI and AI Ops stuff. The software ecosystems because software does have this unifying factor that the API economy, and having all these things work together, more and more. If you don't, customers will go look for solutions that do provide the full end to end solution stuff they're looking for. >> All right, so we're, I've got a couple in mind as far as guests we've had on the show. And we saw them in action on the keynotes stage too. Anybody that jumps out at you, just like, wow, that was cool, that was, not that we, we love all of our children, right? (laughing) But every once in awhile, there's a story or two that does stand out. >> Yeah, so, it is so tough, you know. I loved, you know, the stories. John, I'm sure I'm going to ask you, you know, Mr. B and what he's doing with the children. >> John: Right, Franklin Middle School. >> And the hospitals with Dr. Ellen and the end of the brains. You know, those tech for good are phenomenal. For me, you know, the CIOs that we had on our first day of program. Delta was great and going through transformation, but, you know, our first guest that we had on, was DBS Bank in Singapore and- >> John: David Gledhill. >> He was so articulate and has such a good story about, I took outsourced environments. I didn't just bring it into my environment, say okay, IT can do it a little bit better, and I'll respond to business. No, no, we're going to total restructure the company. Not we're a software company. We're a technology company, and we're gonna learn from the Googles of the world and the like. And he said, We want to be considered there, you know, what was his term there? It was like, you know, bank less, uh, live more and bank less. I mean, what- >> Joyful banking, that was another of his. >> Joyful banking. You don't think of a financial institution as, you know, we want you to think less of the bank. You know, that's just a powerful statement. Total reorganization and, as we mentioned, of course, OpenShift, one of those levers underneath helping them to do that. >> Yeah, you mentioned Dr. Ellen Grant, Boston Children's Hospital, I think about that. She's in fetal neuroimaging and a Professor of Radiology at Harvard Medical School. The work they're doing in terms of diagnostics through imaging is spectacular. I thought about Robin Goldstone at the Livermore Laboratory, about our nuclear weapon monitoring and efficacy of our monitoring. >> Lawrence Livermore. So good. And John, talk about the diversity of our guests. We had expats from four different countries, phenomenal accents. A wonderful slate of brilliant women on the program. From the customer side, some of the award winners that you interviewed. The executives on the program. You know, Stefanie Chiras, always great, and Denise who were up on the keynotes stage. Denise with her 3D printed, new Red Hat logo earrings. Yeah, it was an, um- >> And a couple of old Yanks (laughing). Well, I enjoyed it, Stu. As always, great working with you, and we thank you for being with us as well. For now, we're gonna say so long. We're gonna see you at the next Red Hat Summit, I'm sure, 2020 in San Francisco. Might be a, I guess a slightly different company, but it might be the same old Red Hat too, but they're going to have 34 billion dollars behind them at that point and probably riding pretty high. That will do it for our CUBE coverage here from Boston. Thanks for much for joining us. For Stu Miniman, and our entire crew, have a good day. (funky music)

>> Voiceover: Live from Boston, Massachusetts, it's the CUBE. Covering your Red Hat Summit 2019. Brought to you by Red Hat. >> And welcome back to our coverage here on the CUBE Red Hat Summit 2019. We're at the BCEC in Beantown, Boston, Massachusetts playing host this week to some 9000 strong attendees, pack keynotes. Just a great three days of programming here and educational sessions. Stu Miniman and I'm John Walls. We're joined by Mike Piech, who's the VP and general manager of Middleware at Red Hat. Mike, good to see you today. >> Great to be back. >> And Mark Little, VP of engineering Middleware at Red Hat. Mark, Good to see you as well, sir. >> You too. >> Yeah. First of, let's just talk about your ideas at the show here. Been here for a few days. As we've seen on the keynote stage, wide variety of first off, announcements and great case studies, great educational sessions. But your impressions of what's going on and some of the announcements we've heard about this week. >> Well, sure. I mean definitely some very big announcements with RHEL 8 and OpenShift 4. So as Middleware we're a little bit more in sort of gorilla mode here while some of the bigger announcements take a lot of the limelight. But nevertheless those announcements and the advances that they represent are very important for us as Middleware. Particularly OpenShift 4 as sort of the next layer up from OpenShift which the developers sort of touch and feel and live and breathe on a daily basis. We are the immediate beneficiaries of much of the advances in OpenShift and so that's something that, we as the Middleware guys sort of make real for the enterprise application developer. >> I'd say, probably for me, building on that in a way, one of the biggest announcements, one of the biggest surprises is gotta be the first keynote where we had Satya from Microsoft on stage with Jim announcing the collaboration that we're doing. I never believed that would ever happen and that's, that's fantastic. Has a benefit for Middleware as well but just for Red Hat as a whole. Who would've thought it? >> John: Who would have thought it, right? Yeah, we actually just had Marco Bill-Peter on and he was talking about, he's like "Look, we've actually had some of our support people up in Redmond now for a couple of years." And we had Chris Wright on earlier and he says "You know, sometimes we got to these shows and you get the big bang announcement. It's like, well, really we're working incrementally along the way and open source you can watch it. Sure sometimes you get the new chipset or there's a new this or that. But you know, it's very very small things." So in the spirit of that, maybe, you know, give us the updates since last time we got together. What's happening in the Middleware space as you said. If we build up the stack, you know, we got RHEL 8, we got OpenShift 4 and you're sitting on top. >> Yeah. Well one aspect that's an event like this makes clear in almost a reverse sort of way. We put a lot of effort particularly in Mark's team in getting to a much more frequent and more incremental release cycle and style, right. So getting away from sort of big bang releases every year, couple of years, to a much more agile incremental again sort of regime of rolling out functionality. Now, one of the downsides of that is that you don't have these big grand product announcements to make a big deal about in the same way as RHEL just did with 8 for example. So we need to rethink how we sort of (Laughs) >> absence the sort of big .0 releases, you know how we sort of batch up interesting news and roll it out at a large event like this. Now one of the things that we have been working on is our application environment narrative. Right now, the whole idea of the story here is that many people talk about Cloud-Native and about having lot's of different capabilities and services in a cloud environment. And as we've sort of gone through the, particularly the last year or so, it's really become apparent from what our customers tell us and from what we really see as the opportunities in the cloud-native world. The value that we bring is engineering all these pieces together, right? So that it's not simply a list of these disparate, disconnected, independent services but rather Middleware in the world of cloud native re-imagined. It is capabilities that when engineered together in the right way they make for this comprehensive, unified, cohesive environment within which our customers can develop applications and run those applications. And for the developer, you get developer productivity and then at runtime, you're getting operational reliability. So there really is a sort of a dual-sided value proposition there. And this notion of Middleware engineered together for the cloud is what the application environment idea is all about. >> Yeah. I'd add kinda one of the things that ties into that which has been big for us at least at summit this year is an effort that we kicked off or we announced two months ago called Quakers and as you all know a lot of what we do within Middleware, within Red Hat is based on Java and Java is still the dominant language in the enterprise but it's been around for 20 years. It developed in a pre-cloud era and that made lots of assumptions on the way in which the Java language and the JVM on which it runs would develop which aren't necessarily that conducive for running, in a cloud environment, a hybrid cloud environment and certainly public cloud environment based on Linux containers and Kubernetes. So, we've been working for a number of years in the upstream open JDK community to try and make Java much more cloud-native itself. And Quakers kind of builds on that. It essentially is what we call a kub-native approach where we optimize all of the Middleware stack upfront to work really really well in Kubernetes and specifically on OpenShift. And it's all Java though, that's the important thing. And now if people look into this they'll find that we're showing performance figures and memory utilization that is on a per with some of the newer languages like Go for instance, very very fast. Typically your boot time has gone from seconds to tens of milliseconds. And people who have seen it demonstrated have literally been blown away cause it allows them to leverage the skills that they've had invested in their employees to learn Java and move to the cloud without telling them "You guys are gonna have to learn a completely new language and start from scratch" >> All right, so Mark, if I get it right cause we've been at the Kubernetes show for a bunch of years but this is, you're looking at kinda the application side of what's happening in those Kubernetes environment >> Mark: Yeah. So many times we've talked about the platforms and the infrastructure down but it's the the art piece on top. Super important. I know down the DevZone people were buzzing around all the Quaker stuff. What else for people that are you know, looking at that kinda cloud-native containerization space? What other areas that they should be looking at when it comes to your space? >> Well, again, tying into the up environment thing, hopefully, you know, you'll have heard of knative and Istio. So knative is, to put it in a quick sentence is essentially an enabler for serverless if you like. It's where we're spinning containers really really quickly based on events. But really any serverless platform lives and dies based on the services in which your business logic can then rely upon. Do I have a messaging service there? Do I have a transaction service or a database service? So, we've been working with, with Google on knative and with Microsoft on knative to ensure that we have a really good story in OpenShift but tying it into our Middleware suite as well. So, many of our Middleware products are now knative enabled if you like. The second thing is, as I mentioned, Istio which is a sidecar approach. I won't go into details on that but again Istio the aim behind that is to remove from the application developer some of the non-functional business logic that they had to put in there like "How do I use a messaging service? How do I secure this endpoint and push it down the infrastructure?" So the security servers, the messaging servers, the cashing servers et cetera. They move out of the business logic and they move into Istio. But from our point of view, it's our security servers that we've been working on for years, it's our transactional servers that we've been working on for years. So, these are bullet-proof implementations that we have just made more cloud-native by embedding them in a way in Istio and like I said, enabling them with knative. >> I think we'd mentioned that Chris Wright was on earlier and one of the things he talked about was, this new data-eccentric focus and how, that's at the core so much of what enterprise is doing these days. The fact that whenever speed is distributed, they are and you've got so many data inputs come in from, so to a unified user trying to get their data the way they wanna see it. You might want it for a totally other reason, right? I'm just curious, how does that influence or how has that influenced your work in terms of making sure that transport goes smoothly? Because you do have so much more to work with in a much more complex environment for multiple uses that are unique, right? >> (Mike) Yeah. >> It's not all the same. >> Huge, huge impact for sure. The whole idea of decomposing an application into a much larger number of much smaller pieces than was done in the past has many benefits probably one of the most significant being the ability to make small changes, small incremental changes and afford a much more trial and error approach to innovation versus more macro-level planning waterfall as they call it. But one of the implications of that is now you have a large number of entities. Whether they be big or small, there's a large number of them running within the estate. And there's the orchestration of them and the interconnection of them for sure but it's a n-squared relationship, right. The more these entities you have, the more potential connections between each of them you have to somehow structure and manage and ensure are being done securely and so on. So that has really driven the need for new ways of tying things together, new ways essentially of integration. It has definitely amplified the need for disciplines, EPI management for example. It has driven a lot of increase demand for an event-driven approach where you're streaming in realtime and distributing events to many receivers and dealing with things asynchronously and not depending on round-trip times for everything to be consistent and so on. So, there's just a myriad of implications there that are very detailed technical-level drive some of the things that we're doing now. >> Yeah, I'll just add that in terms of data itself, you've probably heard this a number of times, data is king. Everything we do is based on data in one way or another, So we as Red Hat as a whole and Middleware specifically, we've had a very strong data strategy for a long time. Just as you've got myriad types of data, you can't assume that one way of storing that data is gonna be right for every type of data that you've got. So, we've worked through the integration efforts on ensuring that no sequel data stores, relational data stores^, in-memory data caching and even the messaging services as a whole is a way of sto^ring data in transit, that allows you to, in some ways it allows you to actually look at it in an event-driven way and make intelligent decisions. So that's a key part of what anybody should do if they are in the enterprise space. That's certainly what we're doing because at the end of the day people are building these apps to use that data. >> Well, gentlemen, I know you have another engagement. We're gonna cut you loose but I do wanna say you're the first guests to get applause. (guests laugh) >> From across all the way there. People at home can't hear but, so congratulations. You've been well received already. >> I think they're clearly tuned in to the renaissance of the job in here. >> Yes. >> Thank you both. >> Thanks for the time. >> Mark: Thanks so much. >> We appreciate that. Back with more, we are watching a Red Hat summer 2019 coverage live on the CUBE. (Upbeat music)

>> Announcer: Live, from Boston, Massachusets, it's theCUBE covering Red Hat Summit, 2019. Brought to you by Red Hat. >> Well, welcome back here in Boston. We're at the BCEC as we are starting to wrap up our coverage here of day two of the Red Hat Summit, 2019. Along with Stu Miniman, I'm John Walls, and we're now joined by Ashesh Badani, who is the senior vice president of Cloud Platforms at Red Hat. Been a big day for you, hasn't it Mr. Badani? >> It sure has, thanks for having me back on! >> You bet! All right, so OpenShift 4, we saw the unveiling, your baby gets introduced to the world. What's the reaction been between this morning and this afternoon in terms of people, what they're asking you about, what they're most curious about, and maybe what their best reaction is. >> Yeah, so it's not necessarily a surprise for the folks who have been following OpenShift closely, we put the beta out for a little while, so that's the good news, but let me roll back just a little. >> John: Sure >> I think another part of the news that was really important for us is our announcement of a milestone that we crossed, which is a thousand customers, right? And it was at this very summit and theCUBE definitely knows this well, right, because they've been talking for a while. At this very Summit in 2015, four years ago, that we launched OpenShift Version 3. Right and so, you know you fast forward four years, right, and now the diversity of cases that we see, you know, spanning, established apps, cloud native apps, we heard Exxon talking about AIML data signs that they're putting on the platform, in a variety of different industries, is amazing. And I think the way OpenShift 4 has come along for us, is us having the opportunity to learn what have all these customers been doing well, and what else do we need to do on the platform to make that experience a better one. How do we reimagine enterprise kubernetes, to take it to the next level. And I think that's what we're introducing to the industry. >> Ashesh I think back four years ago, kubernetes was not something that was on the tip of the tongues of most people here. Congratulations on 1,000. >> Thank you. >> I hear what, 100, 150, new customers every quarter is the current rate there, but what I've really enjoyed, talked to a CIO and they're like okay, we're talking about digital transformation, we're talking about how we're modernizing all of our environments, and OpenShift is the platform that we do it. So, talk a little bit, from a customer's standpoint, the speeds, the feeds, the technical pieces, but that outcome, what is it an enabler of for your customers? >> Yeah, so excellent points Stu, we've seen whole sale complete digital transformations underway with our customers. So whether it's Deutsche Bank, who came and talked about running thousands of containers now, moving a whole bunch of workload onto the platform, which is incredible to see. Whether it's a customer like Volkswagen, who talking yesterday, if you caught that, about building an autonomous, self-driving, sets of technologies on the platform. What we're seeing is not just what we thought we would only see in the beginning which is one built, cloud native apps, and digital apps, and so on. Or, more nice existing apps, and bring them on the platform. But also, technologies that are making a fundamental difference, and I'll call one out. So I'm a judge for The Innovation Awards, we do this every year, I have been for many years, I love it, it's one of my favorite parts of the show. This year, we had one entry, which is one of the winners, which is HCA, which is a healthcare provider, talking about how they've been using the OpenShift platform as a means to make a fundamental difference in patients' lives. And when I say fundamental difference, actually saving lives. And you'll hear more about their story, but what they've done, is be able to say, look how can we detect early warning signals, faster than we have been, take some AI technology, and correlate against that, and see how we can reduce sepsis within patients. It's a very personal story for me, my mother died of sepsis. And the fact that they've been able to do this, and I think they're reporting they've already saved dozens of lives based on this. That's when you know, the things that you're doing are making a real difference, making a real transformation, not just in an actual customers' lives, but in users and people around the world. >> You were saying earlier too, Ashesh, about looking at what customers are doing and then trying to improve upon that experience, and give them a more effective experience, whatever the right adjective might be, in terms of what you're doing with 4. If you had to look at it, and say okay, these are the two or three pillars of this where I think we've made the biggest improvement or the biggest change, what would those be? >> Yes, so, one is to look at the world as it is in some sense, which is what a customer's doing. Customers weren't deployed to hybrid cloud, right? They want choice, they want independence with regard to which environments are rented on, whether it's physical, virtual, private, or any public cloud. Customers want one platform, to say I want to run these next generation, cloud native, market service based applications, along with my established stateful applications. Customers want a platform for innovation, right? So for example, we have customers that say, look, I really need a modern platform because I want to recruit the next generation of developers from colleges, if I don't give them the ability to play with Go, or Python, or new databases, they're gonna go to some Silicon Valley company, and I'm going to deplete my pool of talent that I need to compete, right? 'Cause digital transformation is about taking existing companies, and making them digitally enabled. Going forward, what we're also seeing is the ability for us to say well maybe the experience we've given existing customers can be improved. How do we for example, give them a platform, that's more autonomous in nature, more self-driving in nature, that can heal itself, based on for example, there's a critical update that's required that we can send over the air to them. How can we bring greater automation into the platform? It's all of those ideas that we've got based on how customers are using it today, is what we're bringing to bear, going forward. >> Ashesh, one of the errors we have trying to help customers parse through the language is, everybody's talking about platforms, if you look at the public clouds, everybody's all in on kubernetes, a few weeks ago, we were at the Google Cloud event, talked to Red Hat there, there's Anthos, there's OpenShift, look at Azure, we Satya Nadella up on stage, and you're like, okay they've got their own kubernetes platform, but I've got OpenShift fully integrated there. >> Ashesh: Yeah. >> Can you help is kinda understand how those fit together because it's an interesting and changing dynamic. >> Well it's a very Silicon Valley buzzword, right? Everyone wants a platform, everyone wants to build a platform, Facebook's a platform, Uber's a platform, Airbnb is, everything's seeming a platform, right? What I really want to focus on more is in regard to, we want to be able to give folks literally an abstraction level, an ability for companies to say I want to embrace digital transformation. Before we get there, someone's like what's digital transformation, I don't even understand what that means anymore. My simple definition is basically flipping the table. Typically companies spend 80% on maintenance, 20% innovation, how do we flip that? So they're spending 80% innovation, 20% maintenance. So if we're still thinking in those terms, let me give you a way to develop those applications, spend more time and energy on innovation, and then allow for you to take advantage of what I'll call a pool of resources. Compute, network, and storage. Across the environment that you have in place. Some of which you might own, some of which some third parties might provide for you, and some of which you get from public cloud. And take advantage of innovation that's being done outside. Innovative services that come from either public cloud providers, or ISPs, or separate providers, and then be able to do that innovated rapid fashion, you know, develop, deploy, iterate quickly. So to me that is really fundamentally what we're trying to provide customers, and it takes different forms, internal packaging. >> Maybe you can explain to me, the Azure OpenStack seems different than some of the other partnerships. Two years ago, when we were sitting in this building, we talked to you about AWS with OpenShift in that partnership, so what's differentiated and special about the Azure OpenStack integration. >> Yeah, so the Azure partnership, it's a good question because we've now taken our partnering with the public cloud providers to the next level, if you will. With Azure there's a few things in play, first it's a jointly offered managed service from Red Hat and Microsoft, where we're both supporting it together. So in the case of OpenShift and AWS, that's you know OpenShift directly to the ring of service, in this case, it's right out of Microsoft, working close together to make that happen. It's a native service to Azure, so if you saw in the keynote, you could use a command line to call OpenShift directly integrate into the Azure command line. It's available within the interface of Microsoft-Azure. So it feels like a native service, you can take advantages of other Azure services, and bring those to bear, so obviously increases developer experience from that perspective. We also inherit all the compliances, certifications, that Microsoft-Azure has, as well, for that service, as well as all the availability requirements that they put out there, so it's much more closely integrated together, much better developer experience, native to Azure, and then the ability for the Microsoft sales team to go out and sell it to their customers in conjunction. >> You talk a lot about different partnerships, and bringing this collaborative, open-mindset to each and every relationship, how hard is that to do? Because you have your of way of doing things and it's worked very well, and yet, you go out and you have these new partnerships or extensions of partnerships, and not everybody with whom you work does things the same way, and so, everybody's gotta be malleable to a certain extent, but just in terms of being that flexible all the time, what does that do for you? >> So, we take that for granted sometimes, the way we work. And I don't mean to say that to be boastful, or arrogant, in any fashion. I had an interview earlier today, and the reporter said why don't you put on your page, that you're 100% open source? And I said we never put that on our page because that's just how we work, we assume that, we assume everyone knows that about us, and we're going forward. And he says, well, I don't know, perhaps there's others that don't know. And he's right. The world's changing, we're expanding our opportunities in front of folks. In the same way we've only and always known, we used to collaborate with others in the community, before we fully embraced OpenStack, there were certain projects that Red Hat was investing in that were Red Hat driven, and we say maybe there wasn't as much community around it, we're gonna go down and embrace and fully parse an OpenStack community. Same's the case, for example, in kubernetes too. It's not necessarily a project that we created on our own, in conjunction with Google, and many others in the community. And so that's something that's part of our DNA, I'm not sure we're doing anything different, in engaging with communities, just how we work. >> So, Ashesh, I know your team's busy doing a lot of things. We've been hearing about what sessions are overflowing, down in the expo floor, so why don't you give us some visibility. But there was one specific one I wondered if you could start with. >> Ashesh: Sure. >> So down on the expo floor, it's a containerized environment and it has something to do with puppies, and therefor how does that connect with OpenShift 4 if we can start there. >> That's a tough one, you're gonna have to go and ask the puppies how to make a difference in the world. (laughing) >> John: So we go from kubernetes to canines, (laughing) that's what we're doing here. >> I do believe they're comfort dogs, but there was coding and some of the other stuff, so give us a little bit of the walk around, the expo flow, the breakouts and the like, in some of the hot areas, that your team's working on. >> Fair enough, fair enough. Maybe not puppies, but maybe we're trying to herd cats, close enough, right? >> John: Safer terrain. >> The amount of interest, the number of sessions, with OpenShift, or container based technologies, cloud based technologies, it's tremendous to see that. So regardless if whether you see the breakouts that are in place, the customer sessions, I think we've got over 100 customers, I think. Who are presenting on all aspects of their journey. So to me, that's remarkable. Lots of interest in our road map going forward, which is great to see, standing room only for OpenShift 4 and where we're taking that. Other technology that's interesting, the work, for example, we're doing in serverless. We announced an OpenSource collaboration with Mircrosoft, something called KEDA, the Kubernetes eventually. Our scaling project, so interesting how customers can kind of engage around that as well. And then the partner ecosystem, you can walk around and see just a plethora of ISVs, we're all looking to build operators, or have operators and are certifying operators within our ecosystem. And then it's ways for us to expose that to our joint customers. >> We're gonna cut you loose, and let you go, the floor's gonna be open for a few minutes, those puppies are just down behind Stu, we'll let you go check that out. >> Alright, thanks, I hear you can adopt them if you want to, as well. >> Before we let you go see the comfort dogs, 1,000 customers, where do you see, when we come back a year from now, where you are, where you wanna see it go, show us a little bit looking forward. >> So there's been some news around Red Hat that has probably happened over the last few months, the people are hearing this, I look at that as a great opportunity for us to expand our reach into markets, both in terms of industries perhaps we haven't necessarily gone into, that other companies have been. Perhaps we say it's manufacturing, perhaps this is the opportunity for us to cross the chasm, have a lot more trained consultants who can help get more customers on the journey, so I fully expect our reach increasing over a period time. And then you'll see, if you will, iterations of OpenShift 4 and the progress we've made against that, and hopefully many more success stories on the stage. >> Alright, looking forward to catching up next year, if not sooner. >> Ashesh: Okay, excellent. >> John: And congratulations on today, and best of luck down the road. >> Thanks again for having me. >> And good to see you! >> Ashesh: Yeah, likewise! >> Back with more on theCube, you are watching our coverage live, here from Red Hat Summit, 2019, in Boston, Massachusetts. (upbeat techno music)

>> Announcer: Live from Boston, Massachusetts, it's theCUBE. Covering Red Hat Summit 2019. Brought to you by Red Hat. >> Good to have you back here on theCube we are live in Boston at the Convention Center here. Along with Stu Miniman, I'm John Walls and on theCUBE we're continuing our coverage of Red Hat Summit 2019 in Boston, as I said. Joined now by Reza Shafii, who is the VP of Platform Services at Red Hat. Former CoreOS guy >> That's right. >> Stu actually has his CoreOS socks on, >> He told me. >> Today, yeah, so he came dressed for the occasion. >> Shh, can't see those on camera, John. I can't be wearing vendor here. >> Don't show it to the camera. >> Well I just say they're cool! They're cool. Glad to have you with us, Reza. And first off, your impression, you have a big announcement, right, with OpenShift. OpenShift 4 being launched officially on the keynote stage today. That's some big news, right? >> It's a big deal, it's a big deal. The way I think about it is that it's really a culmination of the efforts that we planned out when we sat down between the CoreOS leadership team and the Red Hat leadership team, when the acquisition was closed. And we planned this out, I remember a meeting we had in the white board room. We planned this out. In terms of bringing the best of OpenShift and CoreOS technology together. And it's really great to see it out there on the keynote, and actually all demoed and working. >> And working, right? Key part. >> Reza, dig in for us a little bit here, because it's one thing to say okay, we got a white board and we put things together. You know, when I looked at both companies, at first both, CoreOS before the acquisition and Red Hat, I mean open source, absolutely as its core. I remember talking to the CoreOS team, I'm like, you guys are gonna build a whole bunch of really cool tools, but what's the business there? Do you guys think you're gonna be the next Red Hat? Come on. Well, now you're part of Red Hat. So, give us a little bit of the insight as to what it took to get from there to the announcements, CoreOS infused in many of the pieces that we heard announced this week. >> Yeah, so the way I like to think about it is that Red Hat's OpenShift's roots, it started with making sure that they create a really nice comfortable surface area for the deaf teams. The deaf teams can go in and start pushing the applications and it just ensures that it's running those applications in the right way. The CoreOS roots came from the operations perspective and the system administrator. We always looked at the world from the system administrator. Yes, you're right, CoreOS had a number of technologies they were working on, etcd, Rocket, clair. I used to joke that there's a constellation of open source services that we're working on, but where is the one product? And, towards the end, right before the acquisition, the one product I think was pretty clear is Tectonic, the Kubernetes software. Now, if you look at Tectonic, the key value difference was automated operations. The core tenants of what Alex Polvi and Brandon Philips said into the mindset of the company was we're outnumbered, the number of machines out there is going to be way more than we can handle, therefore we need to automate all operations. They started that on the operating system itself, with CoreOS, the namesake of the company. And then they brought that to Kubernetes. What you see with OpenShift is, OpenShift 4, you see us bringing that to, not only the Kubernetes core, that's the foundation of OpenShift 4, so all capabilities of running Kubernetes are automated with 20 plus operators now. But you see that apply to all the other value capabilities that are on top of OpenShift as well, and we're bringing that to ISV. I was walking around and a number of ISV's have their operators as the number one thing they're advertising. So you're seeing automated operations really take hold and with OpenShift 4 being a foundation for that. >> You talk about operations or operators, you have Operator Hub that was launched earlier this year, what was the driving force behind that? And then ultimately what are you trying to get out of that in terms of advancement and going forward here? >> Right, I think it means it's worked. Going back a little bit of history on this, the operator pattern was coined at CoreOS as a way to do things on a Kubernetes cluster to automate operations. The right way. You have to expose it as a proper API, you have to use a controller, so on and so forth. Then as the team started doing that we realized well there's a lot of demand for this pattern, we started documenting it, describing it better and so on. But then we realized there's a good case for a framework to help people build these automations. Therefore we announced the operator framework at Cubeacon. I think it was a year and a half ago. What happened then was interesting, suddenly we started seeing hundreds plus operators being built on the operator framework. But, it was hard because you could see five Redis operators, 10 MySQL operators. It was hard for our customers to know where can I find the right set of operators that have the right functionality and how do they compare to each other? OperatorHub.IO is a registry that we launched together with AWS, Google and Microsoft to solve for that problem. Now that we have a way to create operators easily and capture that automated operations, we have sort of created a pattern and a framework around it, where do you go to find the right set of operators. >> It's an interesting point because if you look in the container space, especially Kubernetes, it's like, okay well what's standardized, what works across all of these environments? We always worry, I've probably got some pain from previous projects and foundations as to well what's certified and what's not and how do we do that? So, did I see there's a certification now for operators and how do you balance that we need it to work everywhere, we don't wanna have it's Red Hat's building an open ecosystem not something that's limited to only this? >> Yes. So OperatorHub.IO is a community initiative. And, every operator you find on there should work on any Kubernetes. So in fact as part of the vetting process we make sure that that's the case. And then on the certification we launched today, actually, and you can see a number of, we have already 20 plus operators that are certified. This is where we take it a step further and we work with the vendors to make sure that it works on OpenShift. It's following a number of guidelines that we have, in terms of using, for example, Rail as the basis. They work with us to run the updates through security checks and so on. And that's just to give our enterprise customers more levels of guarantees and validation, if they would like to. >> So what are they getting out of that, out of the certification system? What, I guess, stability and certainty and all those kinds of things that I'm looking for, standardization of some kind, is that what's driving that? >> It's simple, at the end of the day they got three things. They get automated updates that are pushed through the OpenShift update mechanism. So if you are using the Redis one, for example, and it's certified, you're gonna be able to update the Redis operator through the same cluster administration mechanism, then you would apply it to the entire cluster itself. You see updates from Redis come in, you can put it through the same approval work so on, so on. The second is they get support. So they get first line of support from Red Hat. They can call Red Hat, our customers and actually we work with them on that. And the third is that they actually get that security vulnerability scans that we put them through to make sure that they pass certain checks. And actually one last one, they also get Rail as the basis of the operator, so, yup. >> Reza, help bring us into the customer point of view. What does all this mean to them, what are the big challenges, how do they modernize their applications and get more applications moving along this path? >> Yeah, in this case the operator customer is mainly the infrastructure administrators. It's important to point that out. The developers will get some benefit on that in that it's self service, so the provision, but there's other ways to do that as well. You can go to a Helm chart, deploy that Helm chart, you get that level of self service automated provisioning. To go ahead and configure for example, a charted MongoDB database on a Kubernetes cluster, you have to create something like 20 different objects. And then to update that to change the charts, you have to go and modify all those 20 different objects. Let's just stay at that level alone. An operator makes that before different parameters on a yaml file that you change. The operator takes that and applies all these configurations for you. So, it's all about simplifying the life of the infrastructure administrators. I truly believe that operators, human operators, infrastructure administrators are one of the least appreciated personas right now that we have out there. They're not the most important ones, but there is a lot of pain points and challenges that they have we're not really thinking about too much. And I think OpenShift goes a long way and operators go a long way to actually start thinking about their pain point as well. >> So what do you think their reaction was this morning when they're looking, first off, the general announcement, right? And then some of the demonstrations and all those things that are occurring? Is there, do you have or are you talking to customers? Are you getting the sense of relief or of anticipation or expectation? I mean, how would you characterize that? >> Think they're falling into a couple of different buckets. There's the customers we've talked to, for awhile now, that know this stuff, so this is not super new to them, but they're very happy to see it. There's one big automaker that's a customer of us and the main human operator was telling me awhile ago that he does not want any service on the cluster unless it has an operator, this is a year and a half ago. And he kept pushing me well I want a Kafka one and I want an Elasticsearch one, and you know. And we, CoreOS, were too small to try to build that ourselves. Obviously that's not, we can't maintain a Kafka operator and a CoreOS one. Now, he's able to go to our operator APP, he's gonna be able to get a Kafka operator that's maintained by Kafka experts. He's gonna be able to get a Redis operator that's maintained by Redis experts. So that bucket of customers are super happy. And then there's another one that's just starting to understand the power of all this. And I think they're just starting to kick the tires and play around with this. Hopefully they will get to the same point as the first bucket of customers, and be asking for everything to be operator based all the time. >> Convert the tire kickers, you're gonna be okay, right? >> That's right. >> Thank you for the time. >> Thank you. >> We appreciate that and continued success at Red Hat, and, once again, good to see you. >> Thank you, always a pleasure. >> You bet. Live, here on theCUBE, you're watching Red Hat Summit 2019. (upbeat music)

(upbeat music) >> Narrator: Live from Boston, MA it's theCUBE covering Red Hat Summit 2019. Brought to you by Red Hat. (upbeat music continues) >> It is so good to have you back with us here on theCUBE as we continue our live coverage here at the BCEC at Red Hat Summit 2019. Glad to have you watching wherever you might be, Eastern Time Zone or maybe out West. Stu Miniman, John Walls here. Our coverage continuing; sixth year we've been at this summit. Eric Kern now joins us here. Both from Lenovo, Eric and Steve Brown. Eric is the Executive Distinguished Engineer. And Steve is the Managing Partner in the Software Business Unit and the DevOps practice leader. So gentlemen good to have you with us on theCUBE. Good to see you today! >> Thanks for having us. >> Thank you. >> No surprise, right, that you're here; long term partnership, very successful get together. First off, I want your ideas or your impressions of what you've hear or what you've seen so far here in the day and a half that we've been underway. And whether it's keynote or maybe one of the side sessions, just what's your first impression of what's goin' on here? >> Yeah, I mean it's great. There's a lot of people here, a lot of activity. I mean we can see the Expo behind us. You know the food is great, lunch is great so- (laughter) >> Rub it in. (laughter continues) Rub it in just a little bit. Okay, so a little bit of news this week with regard to what you're up to. And if you would, I'm not gonna ask you to go terribly deep, but just give us an idea of what some of the headlines are you guys were sending out this week. Steve, why don't you take that? >> Yeah, so this week we announced six new reference designs and solutions, engineered solutions. But pretty excited about OpenShift 4 and certainly Rel8 after a five year I guess pause, if you will, on major releases. So that's exciting. >> So, Eric, why don't we start with building on those partnerships, talk about some of the solutions your talking to customers and some of the latest and greatest? There's a lot of interesting things we're doing; one of the things we've been doing recently is around TruScale. So TruScale is our infrastructure as a service on premise. So one of the things we do with it is we build overall solutions. So there's a number of reference architectures that we talked about with Red Hat. These solutions, think about them as having an overall CapEx price and then we convert that into a OpEx price. Probably one of the neat novel things, and this is kind of the area that I really got into, right, is around how do we build a metering system that doesn't require us to install a bunch of software and can be compatible with everything? So with TruScale what we've done is we've leveraged our what's called our xclarity controller, it's the chip basically on the motherboard, and that xclarity controller has the ability to measure power. And measure power both at the overall input consumption, as well measuring power in the CPU, the memory and the eye out. And we built an infrastructure around that. We can actually tell you exactly what percentage the system is being used and consumed based on that. And we can charge for the overall system on a monthly basis. So we have a portal that's set up for that, whether it be our hardware on its own or our hardware with the Red Hat software installed on top of it. >> So how's that effect the customer relationship then? All the sudden your- whether there was a- not I'd say a dispute, but might of been questions about how much usage am I getting? How am I using this? Why am I being billed as I'm being billed? So on and so forth. Now all the sudden you can just deliver the proof's in the pudding, right? You can say this is exactly what you're doing with this, this is exactly how much you're consuming. And I would assume from a pricing standpoint for that modeling standpoint, you give everybody a lot of comfort, I would think; right? >> You do, right. Not only do they see exactly what they're being charged for, they see exactly some of the usage on their own systems. A lot of times they don't know how well-balanced or unbalanced their systems are. And so we're actually providing real usage data. It's different than what you get in public cloud. It's different in what you get in other solutions where it's virtual allocation. So there's a difference in knowing the physical utilization versus the allocated utilization. What a lot of people do, a lot of companies do when they're renting public cloud infrastructure is they spend a lot of time in automation to actually deallocate. Right, so they're doing all this work just to try to save money. Whereas in the TruScale model, you just run it like you normally run it and you save money because you know, if you're not using it, you're not paying for it. >> John: You don't pay for it. >> Exactly, exactly. >> All right, well Steve, a lot of discussion at the show this week about OpenShift, not least this morning, OpenShift 4 was released. We've had a chance to talk to a number of customers, bring us inside, you know, Lenovo's worked with OpenShift for awhile. Oftentimes we think about the application layers like oh, it's totally divorced, I don't need to think of it. Well, we understand there's integration work that happens there and would love your insight into what is happening at he integration, where it's progressed, and any customer stories that you've got along those lines. >> Well, yeah, we've been doing a lot of work with OpenShift. I would say for an upwards of more than two years. We started with Intel and Red Hat and built a number of Intel Select solutions, reference designs, both bare metal and hyper converged. We are on our fifth edition now of the OpenShift design on Cascade Lake. We're the, I wanna say the pioneers in the industry. We have a center of competency in DevOps with software to really promote software development solutions. And we're excited with OpenShift 4 because of the CoreOS integration as well as the auto-provisioning. Key things, it makes it so much easier to adopt and integrate. >> Any customer deployments? When they come to you, what's the kind of a-ha moment that they have? Is it just the agility that it brings them? Is there anything you can share as to the customers that are actually doing this in the field? >> Well, I like to think the customers get the a-ha when they realize that there is an engineered platform that's been purpose built and they're not coddling software and tools together. It helps with the CI/CD pipeline process templating much more effectively. Overall it's, I think, a lot more streamlined than it was in the earlier editions of OpenShift, especially Open Source. So we're pretty excited with comprehensive business support. I think that businesses feel comfortable. >> Kind of a simple question, but what do you, in terms of what TruScale operates now, what is the- what are you allowing people to do now that they didn't do before? In the latest version here, what exactly is- where's, you think, this improvement? Or where's the new efficiency? What are they getting out of it that would make me, as a customer, have that- if I haven't converted yet, or if I'm perhaps ripe for the taking, what would make me jump? >> Part of it is customers don't want to be managing their infrastructure. And so this there's a big push to public cloud. They just wanna be managing their applications. They just wanna focus on what's paying the bills, right? And paying the bills are providing the IT service is all in the application layer for the most part. What TruScale allows them to do is to have that public cloud kind of management platform. So it's Lenovo premium support behind the scenes; so Lenovo is managing the hardware itself, Lenovo maintains the ownership of the hardware, so they're not even owning the hardware, very similar to public cloud. And they can go and use it on FREM. So they don't have to worry about any security issues with the public cloud. They don't have to worry about any kind of network issues, right, it's all in their data center. It's running just exactly the way they'd run CapEx, but they're running in the way that they have really liked with the public cloud infrastructure. >> So confidence, comfort, security and all that stuff right? >> Eric: There ya go. Yeah. >> Yeah, that's just- I'll pay for that! >> Sure! (laughter) So, we've seen software move heavily towards this model whether it be SaaS or various moving CapEx to OpEx. When I look at infrastructure it's been a little bit of a slower move, especially, I've got some background on the storage side, if you look at storage, it's like oh okay. I'm conditioned as a customer to think about my capacity, my performance, and how I'm tuning everything, and I need to make adjustments, and making changes usually takes a little bit longer. Red Hat's got a lot of software products in the storage space. Help us understand how this fits in and are customers gettin' more comfortable moving from the CapEx to the OpEx for their uses? >> Yeah, good segue. So Ceph and Gluster are some really interesting storage products from Red Hat. And they fit right on our servers, and so we install them; we build big solutions around both of them. I'm actually working on big architecture for another company, for another customer out in Germany. So it's huge stuff cluster. The neat thing about it is our TruScale model allows us to actually sell them on OpEx in a storage product. And what we're measuring is the storage, what I call storage in motion versus the storage at rest. So we see all the different usages of the different servers. The servers are acting as controllers, a multi-tenant controller. And there's a lot of information that's being stored and transmitted through the systems. TruScale's just accumulating all the usage of that. And Steve, maybe you want to talk about some of the software side of it from the storage perspective, but it's really, TruScale fits right in real nicely with the storage side of it. >> I'd actually like to talk about it more comprehensively from the Red Hat software side of it. Anywho, let's talk about how they're already no certification needed. We're looking at all Red Hat applications on TruScale; whether it's OpenShift, or Rel8, Gluster, Ceph, Ansible. So we're really excited because we're not limited in the portfolio. >> Exactly. Exactly. >> Yeah. >> So, Steve, it's interesting, you used to think about, okay, what boxes am I buying, what license I'm doing. If you talk about a real true software world it should be a platform that unifies these things together. So it sounds like you're saying we're getting there. I shouldn't have to think about- give us a little bit, kind of the old way and where customers are seeing it today. >> Yeah, well we're not getting there. We're there. What that allows us to do is to take the reference designs that we have and the testing that we've previously validated with Intel and Red Hat and be able to snap pieces together. So it's just a matter of what's different and unique for the client and the client's situation and their growth pattern. What's great about TruScale is that in this model we can predicatively analyze their consumption forward based on the business growth. So for example, if you're using OpenShift and you start with a small cluster for one or two lines of business, as they adopt DevOps methodologies going from either Waterfall or Agile, we can predicatively analyze the consumption forward that they're gonna need. So they can plan years in advance as they progress. And as such, the other snap-ins, say storage, that they're gonna need for data in motion or data at rest. So it's actually smarter. And what that ends up doing is obviously saving them money, but it saves them time. The typical model is going back to IT and saying we need these severs, we need the storage and the software, and bolt it altogether. And the IT guys are hair on fire running around already. So they can, as long as IT approves it, they can sort of bypass that big, heavy lift. >> So from what you've heard of this week, with Rel8, the big launch last night, a lot of fun, right? >> Steve: Yeah. >> And then OpenShift 4 earlier today talked about- >> Yeah. >> What if there are elements to those two, either one of them, that you find most attractive? Or that really kinda jump off the page to you? Is there anything out there that you're seein' or through the demos that we saw today, or last night even that you think wow, that's cool, that's good, that this is gonna be useful for us? >> OpenShift is one of the things that we're seeing in the industry that's just really enabling the whole DevOps practice. So OpenShift is interesting from the perspective of flexibility, automation, the tooling. Rel8, of course, we've all been waiting for it, I guess for a while now probably. >> Host: Right. >> It's just the next level, the next generation. The Red Hat software, see I'm a big fan of Ceph. I mean I just like Ceph, it's just a neat storage product. It's been around for awhile, but it keeps getting better. It's kinda like the old storage product that first came out with some soft-refined storage. But the whole ecosystem around Red Hat is just very appealing. I actually, Cloudforms is one I think is a little under-utilized today. Cloudforms is a real nice cloud management platform as well. So there's a lot of interesting Red Hat software. Steve, we've done all these reference architectures, are there any ones that stick out to you? I've just been kind of rattling off some of the ones that I like. >> Yeah, I really like the CoreOS integration, 'cause we now see that acquisition really taking shape in a true productization sense, in a practical use sense. I think with Red Hat owning that asset and controlling the development, they can build out features as needed. They're not having to wait on the ecosystem or to spin different cycles for growth. So I think that's my highlight. I've been looking for that. And auto-provisioning as well. I think that's a really key benefit to it, just to make things more smooth and simple. >> Well gentlemen, thanks for the time. >> Guest: Sure. >> Nice to meet you. Look forward to seeing you down the road. We were talkin' about Lenovo, Stu and I were there a couple of years ago, Ashton Kutcher out in San Francisco, so now we get the two of you guys. You're right there with Ashton, right? (laughter) >> That's right. >> Same celebrity! Thanks for sharing the time. Good to see you guys. >> Eric: Thank you. >> Steve: You too. >> Back with more live here at Red Hat Summit 2019, we're in Boston, and you're watching theCube. (electronic music)