>>Hello, brilliant humans and welcome back to Las Vegas, Nevada, where we are live from the AWS Reinvent Show floor here with the cube. My name is Savannah Peterson, joined with Dave Valante, and we have a very exciting conversation with you. Two, two companies you may have heard of. We've got AWS and Red Hat in the house. Manu and Joel, thank you so much for being here. Love this little fist bump. Started off, that's right. Before we even got rolling, Manu, you said that you wanted this to be the best segment of, of the cubes airing. We we're doing over a hundred segments, so you're gonna have to bring the heat. >>We're ready. We're did go. Are we ready? Yeah, go. We're ready. Let's bring it on. >>We're ready. All right. I'm, I'm ready. Dave's ready. Let's do it. How's the show going for you guys real quick before we dig in? >>Yeah, I think after Covid, it's really nice to see that we're back into the 2019 level and, you know, people just want to get out, meet people, have that human touch with each other, and I think a lot of trust gets built as a functional that, so it's super amazing to see our partners and customers here at Reedman. Yeah, >>And you've got a few in the house. That's true. Just a few maybe, maybe a couple >>Very few shows can say that, by the way. Yeah, it's maybe a handful. >>I think one of the things we were saying, it's almost like the entire Silicon Valley descended in the expo hall area, so >>Yeah, it's >>For a few different reasons. There's a few different silicon defined. Yeah, yeah, yeah. Don't have strong on for you. So far >>It's, it's, it is amazing. It's the 10th year, right? It's decade, I think I've been to five and it's, it grows every single year. It's the, you have to be here. It's as simple as that. And customers from every single industry are here too. You don't get, a lot of shows have every single industry and almost every single location around the globe. So it's, it's a must, must be >>Here. Well, and the personas evolved, right? I was at reinvent number two. That was my first, and it was all developers, not all, but a lot of developers. And today it's a business mix, really is >>Totally, is a business mix. And I just, I've talked about it a little bit down the show, but the diversity on the show floor, it's the first time I've had to wait in line for the ladies' room at a tech conference. Almost a two decade career. It is, yeah. And it was really refreshing. I'm so impressed. So clearly there's a commitment to community, but also a commitment to diversity. Yeah. And, and it's brilliant to see on the show floor. This is a partnership that is robust and has been around for a little while. Money. Why don't you tell us a little bit about the partnership here? >>Yes. So Red Hand and AWS are best friends, you know, forever together. >>Aw, no wonder we got the fist bumps and all the good vibes coming out. I know, it's great. I love that >>We have a decade of working together. I think the relationship in the first phase was around running rail bundled with E two. Sure. We have about 70,000 customers that are running rail, which are running mission critical workloads such as sap, Oracle databases, bespoke applications across the state of verticals. Now, as more and more enterprise customers are finally, you know, endorsing and adopting public cloud, I think that business is just gonna continue to grow. So a, a lot of progress there. The second titration has been around, you know, developers tearing Red Hat and aws, Hey, listen, we wanna, it's getting competitive. We wanna deliver new features faster, quicker, we want scale and we want resilience. So just entire push towards devs containers. So that's the second chapter with, you know, red Hat OpenShift on aws, which launched as a, a joint manage service in 2021 last year. And I think the third phase, which you're super excited about, is just bringing the ease of consumption, one click deployment, and then having our customers, you know, benefit from the joint committed spend programs together. So, you know, making sure that re and Ansible and JBoss, the entire portfolio of Red Hat products are available on AWS marketplace. So that's the 1, 2, 3, it of our relationship. It's a decade of working together and, you know, best friends are super committed to making sure our customers and partners continue successful. >>Yeah, that he said it, he said it perfectly. 2008, I know you don't like that, but we started with Rel on demand just in 2008 before E two even had a console. So the partnership has been there, like Manu says, for a long time, we got the partnership, we got the products up there now, and we just gotta finalize that, go to market and get that gas on the fire. >>Yeah. So Graviton Outpost, local zones, you lead it into all the new stuff. So that portends, I mean, 2008, we're talking two years after the launch of s3. >>That's right. >>Right. So, and now look, so is this a harbinger of things to come with these new innovations? >>Yeah, I, I would say, you know, the innovation is a key tenant of our partnership, our relationship. So if you look at from a product standpoint, red Hat or Rel was one of the first platforms that made a support for graviton, which is basically 40% better price performance than any other distribution. Then that translated into making sure that Rel is available on all of our regions globally. So this year we launched Switzerland, Spain, India, and Red Hat was available on launch there, support for Nitro support for Outpost Rosa support on Outpost as well. So I think that relationship, that innovation on the product side, that's pretty visible. I think that innovation again then translates into what we are doing on marketplace with one click deployments we spoke about. I think the third aspect of the know innovation is around making sure that we are making our partners and our customers successful. So one of the things that we've done so far is Joe leads a, you know, a black belt team that really goes into each customer opportunity, making sure how can we help you be successful. We launched and you know, we should be able to share that on a link. After this, we launched like a big playlist, which talks about every single use case on how do you get successful and running OpenShift on aws. So that innovation on behalf of our customers partners to make them successful, that's been a key tenant for us together as >>Well. That's right. And that team that Manu is talking about, we're gonna, gonna 10 x that team this year going into January. Our fiscal yield starts in January. Love that. So yeah, we're gonna have a lot of no hiring freeze over here. Nope. No ma'am. No. Yeah, that's right. Yeah. And you know what I love about working with aws and, and, and Manu just said it very, all of that's customer driven. Every single event that we, that he just talked about in that timeline, it's customer driven, right? Customers wanted rail on demand, customers want JBoss up in the cloud, Ansible this week, you know, everything's up there now. So it's just getting that go to market tight and we're gonna, we're gonna get that done. >>So what's the algorithm for customer driven in terms of taking the input? Because if every customers saying, Hey, I this a >>Really similar >>Question right up, right? I, that's what I want. And if you know, 95% of the customers say it, Jay, maybe that's a good idea. >>Yeah, that's right. Trends. But >>Yeah. You know, 30% you might be like, mm, you know, 20%, you know, how do you guys decide when to put gas on the fire? >>No, that, I think, as I mentioned, there are about 70,000 large customers that are running rail on Easy Two, many of these customers are informing our product strategy. So we have, you know, close to about couple of thousand power users. We have customer advisory booths, and these are the, you know, customers are informing us, Hey, let's get all of the Red Hat portfolio and marketplace support for graviton, support for Outpost. Why don't we, why are we not able to dip into the consumption committed spend programs for both Red Hat and aws? That's right. So it's these power users both at the developer level as well as the guys who are actually doing large commercial consumption. They are the ones who are informing the roadmap for both Red Hat and aws. >>But do, do you codify the the feedback? >>Yeah, I'm like, I wanna see the database, >>The, I think it was, I don't know, it was maybe Chasy, maybe it was Besos, that that data beats intuition. So do you take that information and somehow, I mean, it's global, 70,000 customers, right? And they have different weights, different spending patterns, different levels of maturity. Yeah. Do you, how do you codify that and then ultimately make the decision? Yeah, I >>If, I mean, well you, you've got the strategic advisory boards, which are made up of customers and partners and you know, you get, you get a good, you gotta get a good slice of your customer base to get, and you gotta take their feedback and you gotta do something with it, right? That's the, that's the way we do it and codify it at the product level, I'm sure open source. That's, that's basically how we work at the product level, right? The most elegant solution in open source wins. And that's, that's pretty much how we do that at the, >>I would just add, I think it's also just the implicit trust that the two companies had built with each other, working in the trenches, making our customers and partners successful over the last decade. And Alex, give an example. So that manifests itself in context of like, you know, Amazon and Red Hat just published the entire roadmap for OpenShift. What are the new features that are becoming over the next six to nine to 12 months? It's open source available on GitHub. Customers can see, and then they can basically come back and give feedback like, Hey, you know, we want hip compliance. We just launched. That was a big request that was coming from our >>Customers. That is not any process >>Also for Graviton or Nvidia instances. So I I I think it's a, >>Here's the thing, the reason I'm pounding on this is because you guys have a pretty high hit rate, and I think as a >>Customer, mildly successful company >>As, as a customer advocate, the better, you know, if, if you guys make bets that pay off, it's gonna pay off for customers. Right. And because there's a lot of failures in it. Yeah. I mean, let's face it. That's >>Right. And I think, I think you said the key word bets. You place a lot of small bets. Do you have the, the innovation engine to do that? AWS is the perfect place to place those small bets. And then you, you know, pour gas on the fire when, when they take off. >>Yeah, it's a good point. I mean, it's not expensive to experiment. Yeah. >>Especially in the managed service world. Right? >>And I know you love taking things to market and you're a go to market guy. Let's talk gtm, what's got your snow pumped about GTM for 2023? >>We, we are gonna, you know, 10 x the teams that's gonna be focused on these products, right? So we're gonna also come out with a hybrid committed spend program for our customers that meet them where they want to go. So they're coming outta the data center going into a cloud. We're gonna have a nice financial model for them to do that. And that's gonna take a lot of the friction out. >>Yeah. I mean, you've nailed it. I, I think the, the fact that now entire Red Hat portfolio is available on marketplace, you can do it on one click deployment. It's deeply integrated with Amazon services and the most important part that Joel was making now customers can double dip. They can drive benefit from the consumption committed spend programs, both from Red Hat and from aws, which is amazing. Which is a game changer That's right. For many of our large >>Customers. That's right. And that, so we're gonna, we're gonna really go to town on that next year. That's, and all the, all the resources that I have, which are the technology sellers and the sas, you know, the engineers we're growing this team the most out that team. So it's, >>When you say 10 x, how many are you at now? I'm >>Curious to see where you're headed. Tell you, okay. There's not right? Oh no, there's not one. It's triple digit. Yeah, yeah. >>Today. Oh, sweet. Awesome. >>So, and it's a very sizable team. They're actually making sure that each of our customers are successful and then really making sure that, you know, no customer left behind policy. >>And it's a great point that customers love when Amazonians and Red Hats show up, they love it and it's, they want to get more of it, and we're gonna, we're gonna give it to 'em. >>Must feel great to be loved like that. >>Yeah, that's right. Yeah. Yeah. I would say yes. >>Seems like it's safe to say that there's another decade of partnership between your two companies. >>Hope so. That's right. That's the plan. >>Yeah. And I would say also, you know, just the IBM coming into the mix here. Yeah. I, you know, red Hat has informed the way we have turned around our partnership with ibm, essentially we, we signed the strategic collaboration agreement with the company. All of IBM software now runs on Rosa. So that is now also providing a lot of tailwinds both to our rail customers and as well as Rosa customers. And I think it's a very net creative, very positive for our partnership. >>That's right. It's been very positive. Yep. Yeah. >>You see the >>Billboards positive. Yeah, right. Also that, that's great. Great point, Dave. Yep. We have a, we have a new challenge, a new tradition on the cube here at Reinvent where we're, well, it's actually kind of a glamor moment for you, depending on how you leverage it. We're looking for your 32nd hot take your Instagram reel, your sizzle thought leadership, biggest takeaway, most important theme from this year's show. I know you want, right, Joel? I mean, you TM boy, I feel like you can spit the time. >>Yeah. It is all about Rosa for us. It is all in on that, that's the native OpenShift offering on aws and that's, that's the soundbite we're going go to town with. Now, I don't wanna forget all the other products that are in there, but Rosa is a, is a very key push for us this year. >>Fantastic. All right. Manu. >>I think our customers, it's getting super competitive. Our customers want to innovate just a >>Little bit. >>The enterprise customers see the cloud native companies. I wanna do what these guys are doing. I wanna develop features at a fast clip. I wanna scale, I wanna be resilient. And I think that's really the spirit that's coming out. So to Joel's point, you know, move to worlds containers, serverless, DevOps, which was like, you know, aha, something that's happening on the side of an enterprise is not becoming mainstream. The business is demanding it. The, it is becoming the centerpiece in the business strategy. So that's been really like the aha. Big thing that's happening here. >>Yeah. And those architectures are coming together, aren't they? That's correct. Right. You know, VMs and containers, it used to be one architecture and then at the other end of the spectrum is serverless. People thought of those as different things and now it's a single architecture and, and it's kind of right approach for the right job. >>And, and a compliments say to Red Hat, they do an incredible job of hiding that complexity. Yeah. Yes. And making sure that, you know, for example, just like, make it easier for the developers to create value and then, and you know, >>Yeah, that's right. Those, they were previously siloed architectures and >>That's right. OpenShift wanna be place where you wanna run containers or virtual machines. We want that to be this Yeah. Single place. Not, not go bolt on another piece of architecture to just do one or the other. Yeah. >>And hey, the hybrid cloud vision is working for ibm. No question. You know, and it's achievable. Yeah. I mean, I just, I've said unlike, you know, some of the previous, you know, visions on fixing the world with ai, hybrid cloud is actually a real problem that you're attacking and it's showing the results. Agreed. Oh yeah. >>Great. Alright. Last question for you guys. Cause it might be kind of fun, 10 years from now, oh, we're at another, we're sitting here, we all look the same. Time has passed, but we are not aging, which is a part of the new technology that's come out in skincare. That's my, I'm just throwing that out there. Why not? What do you guys hope that you can say about the partnership and, and your continued commitment to community? >>Oh, that's a good question. You go first this time. Yeah. >>I think, you know, the, you know, for looking into the future, you need to look into the past. And Amazon has always been driven by working back from our customers. That's like our key tenant, principle number 1 0 1. >>Couple people have said that on this stage this week. Yeah. >>Yeah. And I think our partnership, I hope over the next decade continues to keep that tenant as a centerpiece. And then whatever comes out of that, I think we, we are gonna be, you know, working through that. >>Yeah. I, I would say this, I think you said that, well, the customer innovation is gonna lead us to wherever that is. And it's, it's, it's gonna be in the cloud for sure. I think we can say that in 10 years. But yeah, anything from, from AI to the quant quantum computing that IBM's really pushing behind that, you know, those are, those are gonna be things that hopefully we show up on a, on a partnership with Manu in 10 years, maybe sooner. >>Well, whatever happens next, we'll certainly be covering it here on the cube. That's right. Thank you both for being here. Joel Manu, fantastic interview. Thanks to see you guys. Yeah, good to see you brought the energy. I think you're definitely ranking high on the top interviews. We >>Love that for >>The day. >>Thank >>My pleasure >>Job, guys. Now that you're competitive at all, and thank you all for tuning in to our live coverage here from AWS Reinvent in Las Vegas, Nevada, with Dave Valante. I'm Savannah Peterson. You're watching The Cube, the leading source for high tech coverage.

>>Hello everyone and welcome back to Motor City, Michigan. We're live from the Cube and my name is Savannah Peterson. Joined this afternoon with my co-host John Ferer. John, how you doing? Doing >>Great. This next segment's gonna be awesome about application modernization, scaling pluses. This is what's gonna, how are the next generation software revolution? It's gonna be >>Fun. You know, it's kind of been a theme of our day today is scale. And when we think about the complex orchestration platform that is Kubernetes, everyone wants to scale faster, quicker, more efficiently, and our guests are here to tell us all about that. Please welcome to Char and Andy, thank you so much for being here with us. You were on the Red Hat OpenShift team. Yeah. I suspect most of our audience is familiar, but just in case, let's give 'em a quick one-liner pitch so everyone's on the same page. Tell us about OpenShift. >>I, I'll take that one. OpenShift is our ES platform is our ES distribution. You can consume it as a self-managed platform or you can consume it as a managed service on on public clouds. And so we just call it all OpenShift. So it's basically Kubernetes, but you know, with a CNCF ecosystem around it to make things more easier. So maybe there's two >>Lights. So what does being at coupon mean for you? How does it feel to be here? What's your initial takes? >>Exciting. I'm having a fantastic time. I haven't been to coupon since San Diego, so it's great to be back in person and see old friends, make new friends, have hallway conversations. It's, it's great as an engineer trying to work in this ecosystem, just being able to, to be in the same place with these folks. >>And you gotta ask, before we came on camera, you're like, this is like my sixth co con. We were like, we're seven, you know, But that's a lot of co coupons. It >>Is, yes. I mean, so what, >>Yes. >>Take us status >>For sure. Where we are now. Compare and contrast co. Your first co con, just scope it out. What's the magnitude of change? If you had to put a pin on that, because there's a lot of new people coming in, they might not have seen where it's come from and how we got here is maybe not how we're gonna get to the next >>Level. I've seen it grow tremendously since the first one I went to, which I think was Austin several years ago. And what's great is seeing lots of new people interested in contributing and also seeing end users who are trying to figure out the best way to take advantage of this great ecosystem that we have. >>Awesome. And the project management side, you get the keys to the Kingdom with Red Hat OpenShift, which has been successful. Congratulations by the way. Thank you. We watched that grow and really position right on the wave. It's going great. What's the update on on the product? Kind of, you're in a good, good position right now. Yeah, >>No, we we're feeling good about it. It's all about our customers. Obviously the fact that, you know, we have thousands of customers using OpenShift as the cloud native platform, the container platform. We're very excited. The great thing about them is that, I mean you can go to like OpenShift Commons is kind of a user group that we run on the first day, like on Tuesday we ran. I mean you should see the number of just case studies that our customers went through there, you know? And it is fantastic to see that. I mean it's across so many different industries, across so many different use cases, which is very exciting. >>One of the things we've been reporting here in the Qla scene before, but here more important is just that if you take digital transformation to the, to its conclusion, the IT department and developers, they're not a department to serve the business. They are the business. Yes. That means that the developers are deciding things. Yeah. And running the business. Prove their code. Yeah. Okay. If that's, if that takes place, you gonna have scale. And we also said on many cubes, certainly at Red Hat Summit and other ones, the clouds are distributed computer, it's distributed computing. So you guys are focusing on this project, Andy, that you're working on kcp. >>Yes. >>Which is, I won't platform Kubernetes platform for >>Control >>Planes. Control planes. Yes. Take us through, what's the focus on why is that important and why is that relate to the mission of developers being in charge and large scale? >>Sure. So a lot of times when people are interested in developing on Kubernetes and running workloads, they need a cluster of course. And those are not cheap. It takes time, it takes money, it takes resources to get them. And so we're trying to make that faster and easier for, for end users and everybody involved. So with kcp, we've been able to take what looks like one normal Kubernetes and partition it. And so everybody gets a slice of it. You're an administrator in your little slice and you don't have to ask for permission to install new APIs and they don't conflict with anybody else's APIs. So we're really just trying to make it super fast and make it super flexible. So everybody is their own admin. >>So the developer basically looks at it as a resource blob. They can do whatever they want, but it's shared and provisioned. >>Yes. One option. It's like, it's like they have their own cluster, but you don't have to go through the process of actually provisioning a full >>Cluster. And what's the alternative? What's the what's, what's the, what's the benefit and what was the alternative to >>This? So the alternative, you spin up a full cluster, which you know, maybe that's three control plane nodes, you've got multiple workers, you've got a bunch of virtual machines or bare metal, or maybe you take, >>How much time does that take? Just ballpark. >>Anywhere from five minutes to an hour you can use cloud services. Yeah. Gke, E Ks and so on. >>Keep banging away. You're configuring. Yeah. >>Those are faster. Yeah. But it's still like, you still have to wait for that to happen and it costs money to do all of that too. >>Absolutely. And it's complex. Why do something that's been done, if there's a tool that can get you a couple steps down the path, which makes a ton of sense. Something that we think a lot when we're talking about scale. You mentioned earlier, Tohar, when we were chatting before the cams were alive, scale means a lot of different things. Can you dig in there a little bit? >>Yeah, I >>Mean, so when, when >>We talk about scale, >>We are talking about from a user perspective, we are talking about, you know, there are more users, there are more applications, there are more workloads, there are more services being run on Kubernetes now, right? So, and OpenShift. So, so that's one dimension of this scale. The other dimension of the scale is how do you manage all the underlying infrastructure, the clusters, the name spaces, and all the observability data, et cetera. So that's at least two levels of scale. And then obviously there's a third level of scale, which is, you know, there is scale across not just different clouds, but also from cloud to the edge. So there is that dimension of scale. So there are several dimensions of this scale. And the one that again, we are focused on here really is about, you know, this, the first one that I talk about is a user. And when I say user, it could be a developer, it could be an application architect, or it could be an application owner who wants to develop Kubernetes applications for Kubernetes and wants to publish those APIs, if you will, and make it discoverable and then somebody consumes it. So that's the scale we are talking about >>Here. What are some of the enterprise, you guys have a lot of customers, we've talked to you guys before many, many times and other subjects, Red Hat, I mean you guys have all the customers. Yeah. Enterprise, they've been there, done that. And you know, they're, they're savvy. Yeah. But the cloud is a whole nother ballgame. What are they thinking about? What's the psychology of the customer right now? Because now they have a lot of choices. Okay, we get it, we're gonna re-platform refactor apps, we'll keep some legacy on premises for whatever reasons. But cloud pretty much is gonna be the game. What's the mindset right now of the customer base? Where are they in their, in their psych? Not the executive, but more of the the operators or the developers? >>Yeah, so I mean, first of all, different customers are at different levels of maturity, I would say in this. They're all on a journey how I like to describe it. And in this journey, I mean, I see a customers who are really tip of the sphere. You know, they have containerized everything. They're cloud native, you know, they use best of tools, I mean automation, you know, complete automation, you know, quick deployment of applications and all, and life cycle of applications, et cetera. So that, that's kind of one end of this spectrum >>Advanced. Then >>The advances, you know, and, and I, you know, I don't, I don't have any specific numbers here, but I'd say there are quite a few of them. And we see that. And then there is kind of the middle who are, I would say, who are familiar with containers. They know what app modernization, what a cloud application means. They might have tried a few. So they are in the journey. They are kind of, they want to get there. They have some other kind of other issues, organizational or talent and so, so on and so forth. Kinds of issues to get there. And then there are definitely the quota, what I would call the lag arts still. And there's lots of them. But I think, you know, Covid has certainly accelerated a lot of that. I hear that. And there is definitely, you know, more, the psychology is definitely more towards what I would say public cloud. But I think where we are early also in the other trend that I see is kind of okay, public cloud great, right? So people are going there, but then there is the so-called edge also. Yeah. That is for various regions. You, you gotta have a kind of a regional presence, a edge presence. And that's kind of the next kind of thing taking off here. And we can talk more >>About it. Yeah, let's talk about that a little bit because I, as you know, as we know, we're very excited about Edge here at the Cube. Yeah. What types of trends are you seeing? Is that space emerges a little bit more firmly? >>Yeah, so I mean it's, I mean, so we, when we talk about Edge, you're talking about, you could talk about Edge as a, as a retail, I mean locations, right? >>Could be so many things edges everywhere. Everywhere, right? It's all around us. Quite literally. Even on the >>Scale. Exactly. In space too. You could, I mean, in fact you mentioned space. I was, I was going to >>Kinda, it's this world, >>My space actually Kubernetes and OpenShift running in space, believe it or not, you know, So, so that's the edge, right? So we have Industrial Edge, we have Telco Edge, we have a 5g, then we have, you know, automotive edge now and, and, and retail edge and, and more, right? So, and space, you know, So it's very exciting there. So the reason I tag back to that question that you asked earlier is that that's where customers are. So cloud is one thing, but now they gotta also think about how do I, whatever I do in the cloud, how do I bring it to the edge? Because that's where my end users are, my customers are, and my data is, right? So that's the, >>And I think Kubernetes has brought that attention to the laggards. We had the Laed Martin on yesterday, which is an incredible real example of Kubernetes at the edge. It's just incredible story. We covered it also wrote a story about it. So compelling. Cuz it makes it real. Yes. And Kubernetes is real. So then the question is developer productivity, okay, Things are starting to settle in. We've got KCP scaling clusters, things are happening. What about the tool chains? And how do I develop now I got scale of development, more code coming in. I mean, we are speculating that in the future there's so much code in open source that no one has to write code anymore. Yeah. At some point it's like this gluing things together. So the developers need to be productive. How are we gonna scale the developer equation and eliminate the, the complexity of tool chains and environments. Web assembly is super hyped up at this show. I don't know why, but sounds good. No one, no one can tell me why, but I can kind of connect the dots. But this is a big thing. >>Yeah. And it's fitting that you ask about like no code. So we've been working with our friends at Cross Plain and have integrated with kcp the ability to no code, take a whole bunch of configuration and say, I want a database. I want to be a, a provider of databases. I'm in an IT department, there's a bunch of developers, they don't wanna have to write code to create databases. So I can just take, take my configuration and make it available to them. And through some super cool new easy to use tools that we have as a developer, you can just say, please give me a database and you don't have to write any code. I don't have to write any code to maintain that database. I'm actually using community tooling out there to get that spun up. So there's a lot of opportunities out there. So >>That's ease of use check. What about a large enterprise that's got multiple tool chains and you start having security issues. Does that disrupt the tool chain capability? Like there's all those now weird examples emerging, not weird, but like real plumbing challenges. How do you guys see that evolving with Red >>Hat and Yeah, I mean, I mean, talking about that, right? The software, secure software supply chain is a huge concern for everyone after, especially some of the things that have happened in the past few >>Years. Massive team here at the show. Yeah. And just within the community, we're all a little more aware, I think, even than we were before. >>Before. Yeah. Yeah. And, and I think the, so to step back, I mean from, so, so it's not just even about, you know, run time vulnerability scanning, Oh, that's important, but that's not enough, right? So we are talking about, okay, how did that container, or how did that workload get there? What is that workload? What's the prominence of this workload? How did it get created? What is in it? You know, and what, what are, how do I make, make sure that there are no unsafe attack s there. And so that's the software supply chain. And where Red Hat is very heavily invested. And as you know, with re we kind of have roots in secure operating system. And rel one of the reasons why Rel, which is the foundation of everything we do at Red Hat, is because of security. So an OpenShift has always been secure out of the box with things like scc, rollbacks access control, we, which we added very early in the product. >>And now if you kind of bring that forward, you know, now we are talking about the complete software supply chain security. And this is really about right how from the moment the, the, the developer rights code and checks it into a gateway repository from there on, how do you build it? How do you secure it at each step of the process, how do you sign it? And we are investing and contributing to the community with things like cosign and six store, which is six store project. And so that secures the supply chain. And then you can use things like algo cd and then finally we can do it, deploy it onto the cluster itself. And then we have things like acs, which can do vulnerability scanning, which is a container security platform. >>I wanna thank you guys for coming on. I know Savannah's probably got a last question, but my last question is, could you guys each take a minute to answer why has Kubernetes been so successful today? What, what was the magic of Kubernetes that made it successful? Was it because no one forced it? Yes. Was it lightweight? Was it good timing, right place at the right time community? What's the main reason that Kubernetes is enabling all this, all this shift and goodness that's coming together, kind of defacto unifies people, the stacks, almost middleware markets coming around. Again, not to use that term middleware, but it feels like it's just about to explode. Yeah. Why is this so successful? I, >>I think, I mean, the shortest answer that I can give there really is, you know, as you heard the term, I think Satya Nala from Microsoft has used it. I don't know if he was the original person who pointed, but every company wants to be a software company or is a software company now. And that means that they want to develop stuff fast. They want to develop stuff at scale and develop at, in a cloud native way, right? You know, with the cloud. So that's, and, and Kubernetes came at the right time to address the cloud problem, especially across not just one public cloud or two public clouds, but across a whole bunch of public clouds and infrastructure as, and what we call the hybrid clouds. I think the ES is really exploded because of hybrid cloud, the need for hybrid cloud. >>And what's your take on the, the magic Kubernetes? What made it, what's making it so successful? >>I would agree also that it came about at the right time, but I would add that it has great extensibility and as developers we take it advantage of that every single day. And I think that the, the patterns that we use for developing are very consistent. And I think that consistency that came with Kubernetes, just, you have so many people who are familiar with it and so they can follow the same patterns, implement things similarly, and it's just a good fit for the way that we want to get our software out there and have, and have things operate. >>Keep it simple, stupid almost is that acronym, but the consistency and the de facto alignment Yes. Behind it just created a community. So, so then the question is, are the developers now setting the standards? That seems like that's the new way, right? I mean, >>I'd like to think so. >>So I mean hybrid, you, you're touching everything at scale and you also have mini shift as well, right? Which is taking a super macro micro shift. You ma micro shift. Oh yeah, yeah, exactly. It is a micro shift. That is, that is fantastic. There isn't a base you don't cover. You've spoken a lot about community and both of you have, and serving the community as well as your engagement with them from a, I mean, it's given that you're both leaders stepping back, how, how Community First is Red Hat and OpenShift as an organization when it comes to building the next products and, and developing. >>I'll take and, and I'm sure Andy is actually the community, so I'm sure he'll want to a lot of it. But I mean, right from the start, we have roots in open source. I'll keep it, you know, and, and, and certainly with es we were one of the original contributors to Kubernetes other than Google. So in some ways we think about as co-creators of es, they love that. And then, yeah, then we have added a lot of things in conjunction with the, I I talk about like SCC for Secure, which has become part security right now, which the community, we added things like our back and other what we thought were enterprise features needed because we actually wanted to build a product out of it and sell it to customers where our customers are enterprises. So we have worked with the community. Sometimes we have been ahead of the community and we have convinced the community. Sometimes the community has been ahead of us for other reasons. So it's been a great collaboration, which is I think the right thing to do. But Andy, as I said, >>Is the community well set too? Are well said. >>Yes, I agree with all of that. I spend most of my days thinking about how to interact with the community and engage with them. So the work that we're doing on kcp, we want it to be a community project and we want to involve as many people as we can. So it is a heavy focus for me and my team. And yeah, we we do >>It all the time. How's it going? How's the project going? You feel good >>About it? I do. It is, it started as an experiment or set of prototypes and has grown leaps and bounds from it's roots and it's, it's fantastic. Yeah. >>Controlled planes are hot data planes control planes. >>I >>Know, I love it. Making things work together horizontally scalable. Yeah. Sounds like cloud cloud native. >>Yeah. I mean, just to add to it, there are a couple of talks that on KCP at Con that our colleagues s Stephan Schemanski has, and I, I, I would urge people who have listening, if they have, just Google it, if you will, and you'll get them. And those are really awesome talks to get more about >>It. Oh yeah, no, and you can tell on GitHub that KCP really is a community project and how many people are participating. It's always fun to watch the action live to. Sure. Andy, thank you so much for being here with us, John. Wonderful questions this afternoon. And thank all of you for tuning in and listening to us here on the Cube Live from Detroit. I'm Savannah Peterson. Look forward to seeing you again very soon.

>>Hey guys. Welcome back to the Cubes coverage of Ansible Fast 2022. This is day two of our wall to wall coverage. Lisa Martin here with John Ferer. John, we're seeing this world where companies are saying if we can't automate it, we need to, The automation market is transforming. There's been a lot of buzz about that. A lot of technical chops here at Ansible Fest. >>Yeah, I mean, we've got a great guest here coming on Cuba alumni, Dean Newman, future room. He travels every event he's got. He's got his nose to the grindstone ear to the ground. Great analysis. I mean, we're gonna get into why it's important. How does Ansible fit into the big picture? It's really gonna be a great segment. The >>Board do it well, John just did my job for me about, I'll introduce him again. Daniel Newman, one of our alumni is Back Principal Analyst at Future and Research. Great to have you back on the cube. >>Yeah, it's good to join you. Excited to be back in Chicago. I don't know if you guys knew this, but for 40 years, this was my hometown. Now I don't necessarily brag about that anymore. I'm, I live in Austin now. I'm a proud Texan, but I did grow up here actually out in the west suburbs. I got off the plane, I felt the cold air, and I almost turned around and said, Does this thing go back? Yeah. Cause I'm, I've, I've grown thin skin. It did not take me long. I, I like the warm, Come on, >>I'm the saying, I'm from California and I got off the plane Monday. I went, Whoa, I need a coat. And I was in Miami a week ago and it was 85. >>Oh goodness. >>Crazy. So you just flew in. Talk about what's going on, your take on, on Ansible. We've talked a lot with the community, with partners, with customers, a lot of momentum. The flywheel of the community is going around and round and round. What are some of your perspectives that you see? >>Yeah, absolutely. Well, let's you know, I'm gonna take a quick step back. We're entering an era where companies are gonna have to figure out how to do more with less. Okay? We've got exponential data growth, we've got more architectural complexity than ever before. Companies are trying to discern how to deal with many different environments. And just at a macro level, Red Hat is one of the companies that is almost certainly gonna be part of this multi-cloud hybrid cloud era. So that should initially give a lot of confidence to the buying group that are looking at how to automate their environments. You're automating workflows, but really with, with Ansible, we're focused on automating it, automating the network. So as companies are kind of dig out, we're entering this recessionary period, Okay, we're gonna call it what it is. The first thing that they're gonna look at is how do we tech our way out of it? >>I had a wonderful one-on-one conversation with ServiceNow ceo, Bill McDermott, and we saw ServiceNow was in focus this morning in the initial opening session. This is the integration, right? Ansible integrating with ServiceNow. What we need to see is infrastructure automation, layers and applications working in concert to basically enable enterprises to be up and running all the time. Let's first fix the problems that are most common. Let's, let's automate 'em, let's script them. And then at some point, let's have them self resolving, which we saw at the end with Project Wisdom. So as I see it, automation is that layer that enterprises, boards, technologists, all can agree upon are basically here's something that can make our business more efficient, more profitable, and it's gonna deal with this short term downturn in a way that tech is actually gonna be the answer. Just like Bill and I said, let's tech our way out of it. >>If you look at the Red Hat being bought by ibm, you see Project Wisdom Project, not a product, it's a project. Project Wisdom is the confluence of research and practitioners kind of coming together with ai. So bringing AI power to the Ansible is interesting. Red Hat, Linux, Rel OpenShift, I mean, Red Hat's kind of position, isn't it? Kind of be in that right spot where a puck might be coming maybe. I mean, what do you think? >>Yeah, as analysts, we're really good at predicting the, the recent past. It's a joke I always like to make, but Red Hat's been building toward the future. I think for some time. Project Wisdom, first of all, I was very encouraged with it. One of the things that many people in the market probably have commented on is how close is IBM in Red Hat? Now, again, it's a $34 billion acquisition that was made, but boy, the cultures of these two companies couldn't be more different. And of course, Red Hat kind of carries this, this sort of middle ground layer where they provide a lot of value in services to companies that maybe don't use IBM at, at, for the public cloud especially. This was a great indication of how you can take the power of IBM's research, which of course has some of the world's most prolific data scientists, engineers, building things for the future. >>You know, you see things like yesterday they launched a, you know, an AI solution. You know, they're building chips, semiconductors, and technologies that are gonna power the future. They're building quantum. Long story short, they have these really brilliant technologists here that could be adding value to Red Hat. And I don't know that the, the world has fully been able to appreciate that. So when, when they got on stage and they kind of say, Here's how IBM is gonna help power the next generation, I was immediately very encouraged by the fact that the two companies are starting to show signs of how they can collaborate to offer value to their customers. Because of course, as John kind of started off with, his question is, they've kind of been where the puck is going. Open source, Linux hybrid cloud, This is the future. In the future. Every company's multi-cloud. And I said in a one-on-one meeting this morning, every company is going to probably have workloads on every cloud, especially large enterprises. >>Yeah. And I think that the secret's gonna be how do you make that evolve? And one of the things that's coming out of the industry over the years, and looking back as historians, we would say, gotta have standards. Well, with cloud, now people standards might slow things down. So you're gonna start to figure out how does the community and the developers are thinking it'll be the canary in the coal mine. And I'd love to get your reaction on that, because we got Cuban next week. You're seeing people kind of align and try to win the developers, which, you know, I always laugh cuz like, you don't wanna win, you want, you want them on your team, but you don't wanna win them. It's like a, it's like, so developers will decide, >>Well, I, I think what's happening is there are multiple forces that are driving product adoption. And John, getting the developers to support the utilization and adoption of any sort of stack goes a long way. We've seen how sticky it can be, how sticky it is with many of the public cloud pro providers, how sticky it is with certain applications. And it's gonna be sticky here in these interim layers like open source automation. And Red Hat does have a very compelling developer ecosystem. I mean, if you sat in the keynote this morning, I said, you know, if you're not a developer, some of this stuff would've been fairly difficult to understand. But as a developer you saw them laughing at jokes because, you know, what was it the whole part about, you know, it didn't actually, the ping wasn't a success, right? And everybody started laughing and you know, I, I was sitting next to someone who wasn't technical and, and you know, she kinda goes, What, what was so funny? >>I'm like, well, he said it worked. Do you see that? It said zero data trans or whatever that was. So, but if I may just really quickly, one, one other thing I did wanna say about Project Wisdom, John, that the low code and no code to the full stack developer is a continuum that every technology company is gonna have to think deeply about as we go to the future. Because the people that tend to know the process that needs to be automated tend to not be able to code it. And so we've seen every automation company on the planet sort of figuring out and how to address this low code, no code environment. I think the power of this partnership between IBM Research and Red Hat is that they have an incredibly deep bench of capabilities to do things like, like self-training. Okay, you've got so much data, such significant size models and accuracy is a problem, but we need systems that can self teach. They need to be able self-teach, self learn, self-heal so that we can actually get to the crux of what automation is supposed to do for us. And that's supposed to take the mundane out and enable those humans that know how to code to work on the really difficult and hard stuff because the automation's not gonna replace any of that stuff anytime soon. >>So where do you think looking at, at the partnership and the evolution of it between IBM research and Red Hat, and you're saying, you know, they're, they're, they're finally getting this synergy together. How is it gonna affect the future of automation and how is it poised to give them a competitive advantage in the market? >>Yeah, I think the future or the, the competitive space is that, that is, is ecosystems and integration. So yesterday you heard, you know, Red Hat Ansible focusing on a partnership with aws. You know, this week I was at Oracle Cloud world and they're talking about running their database in aws. And, and so I'm kind of going around to get to the answer to your question, but I think collaboration is sort of the future of growth and innovation. You need multiple companies working towards the same goal to put gobs of resources, that's the technical term, gobs of resources towards doing really hard things. And so Ansible has been very successful in automating and securing and focusing on very certain specific workloads that need to be automated, but we need more and there's gonna be more data created. The proliferation, especially the edge. So you saw all this stuff about Rockwell, How do you really automate the edge at scale? You need large models that are able to look and consume a ton of data that are gonna be continuously learning, and then eventually they're gonna be able to deliver value to these companies at scale. IBM plus Red Hat have really great resources to drive this kind of automation. Having said that, I see those partnerships with aws, with Microsoft, with ibm, with ServiceNow. It's not one player coming to the table. It's a lot of players. They >>Gotta be Switzerland. I mean they have the Switzerland. I mean, but the thing about the Amazon deal is like that marketplace integration essentially puts Ansible once a client's in on, on marketplace and you get the central on the same bill. I mean, that's gonna be a money maker for Ansible. I >>Couldn't agree more, John. I think being part of these public cloud marketplaces is gonna be so critical and having Ansible land and of course AWS largest public cloud by volume, largest marketplace today. And my opinion is that partnership will be extensible to the other public clouds over time. That just makes sense. And so you start, you know, I think we've learned this, John, you've done enough of these interviews that, you know, you start with the biggest, with the highest distribution and probability rates, which in this case right now is aws, but it'll land on in Azure, it'll land in Google and it'll continue to, to grow. And that kind of adoption, streamlining make it consumption more consumable. That's >>Always, I think, Red Hat and Ansible, you nailed it on that whole point about multicloud, because what happens then is why would I want to alienate a marketplace audience to use my product when it could span multiple environments, right? So you saw, you heard that Stephanie yesterday talk about they, they didn't say multiple clouds, multiple environments. And I think that is where I think I see this layer coming in because some companies just have to work on all clouds. That's the way it has to be. Why wouldn't you? >>Yeah. Well every, every company will probably end up with some workloads in every cloud. I just think that is the fate. Whether it's how we consume our SaaS, which a lot of people don't think about, but it always tends to be running on another hyperscale public cloud. Most companies tend to be consuming some workloads from every cloud. It's not always direct. So they might have a single control plane that they tend to lead the way with, but that is only gonna continue to change. And every public cloud company seems to be working on figuring out what their niche is. What is the one thing that sort of drives whether, you know, it is, you know, traditional, we know the commoditization of traditional storage network compute. So now you're seeing things like ai, things like automation, things like the edge collaboration tools, software being put into the, to the forefront because it's a different consumption model, it's a different margin and economic model. And then of course it gives competitive advantages. And we've seen that, you know, I came back from Google Cloud next and at Google Cloud next, you know, you can see they're leaning into the data AI cloud. I mean, that is their focus, like data ai. This is how we get people to come in and start using Google, who in most cases, they're probably using AWS or Microsoft today. >>It's a great specialty cloud right there. That's a big use case. I can run data on Google and run something on aws. >>And then of course you've got all kinds of, and this is a little off topic, but you got sovereignty, compliance, regulatory that tends to drive different clouds over, you know, global clouds like Tencent and Alibaba. You know, if your workloads are in China, >>Well, this comes back down at least to the whole complexity issue. I mean, it has to get complex before it gets easier. And I think that's what we're seeing companies opportunities like Ansible to be like, Okay, tame, tame the complexity. >>Yeah. Yeah, I totally agree with you. I mean, look, when I was watching the demonstrations today, my take is there's so many kind of simple, repeatable and mundane tasks in everyday life that enterprises need to, to automate. Do that first, you know? Then the second thing is working on how do you create self-healing, self-teaching, self-learning, You know, and, and I realize I'm a little broken of a broken record at this, but these are those first things to fix. You know, I know we want to jump to the future where we automate every task and we have multi-term conversational AI that is booking our calendars and driving our cars for us. But in the first place, we just need to say, Hey, the network's down. Like, let's make sure that we can quickly get access back to that network again. Let's make sure that we're able to reach our different zones and locations. Let's make sure that robotic arm is continually doing the thing it's supposed to be doing on the schedule that it's been committed to. That's first. And then we can get to some of these really intensive deep metaverse state of automation that we talk about. Self-learning, data replication, synthetic data. I'm just gonna throw terms around. So I sound super smart. >>In your customer conversations though, from an looking at the automation journey, are you finding most of them, or some percentage is, is wanting to go directly into those really complex projects rather than starting with the basics? >>I don't know that you're, you're finding that the customers want to do that? I think it's the architecture that often ends up being a problem is we as, as the vendor side, will tend to talk about the most complex problems that they're able to solve before companies have really started solving the, the immediate problems that are before them. You know, it's, we talk about, you know, the metaphor of the cloud is a great one, but we talk about the cloud, like it's ubiquitous. Yeah. But less than 30% of our workloads are in the public cloud. Automation is still in very early days and in many industries it's fairly nascent. And doing things like self-healing networks is still something that hasn't even been able to be deployed on an enterprise-wide basis, let alone at the industrial layer. Maybe at the company's on manufacturing PLAs or in oil fields. Like these are places that have difficult to reach infrastructure that needs to be running all the time. We need to build systems and leverage the power of automation to keep that stuff up and running. That's, that's just business value, which by the way is what makes the world go running. Yeah. Awesome. >>A lot of customers and users are struggling to find what's the value in automating certain process, What's the ROI in it? How do you help them get there so that they understand how to start, but truly to make it a journey that is a success. >>ROI tends to be a little bit nebulous. It's one of those things I think a lot of analysts do. Things like TCO analysis Yeah. Is an ROI analysis. I think the businesses actually tend to know what the ROI is gonna be because they can basically look at something like, you know, when you have an msa, here's the downtime, right? Business can typically tell you, you know, I guarantee you Amazon could say, Look for every second of downtime, this is how much commerce it costs us. Yeah. A company can generally say, if it was, you know, we had the energy, the windmills company, like they could say every minute that windmill isn't running, we're creating, you know, X amount less energy. So there's a, there's a time value proposition that companies can determine. Now the question is, is about the deployment. You know, we, I've seen it more nascent, like cybersecurity can tend to be nascent. >>Like what does a breach cost us? Well there's, you know, specific costs of actually getting the breach cured or paying for the cybersecurity services. And then there's the actual, you know, ephemeral costs of brand damage and of risks and customer, you know, negative customer sentiment that potentially comes out of it. With automation, I think it's actually pretty well understood. They can look at, hey, if we can do this many more cycles, if we can keep our uptime at this rate, if we can reduce specific workforce, and I'm always very careful about this because I don't believe automation is about replacement or displacement, but I do think it is about up-leveling and it is about helping people work on things that are complex problems that machines can't solve. I mean, said that if you don't need to put as many bodies on something that can be immediately returned to the organization's bottom line, or those resources can be used for something more innovative. So all those things are pretty well understood. Getting the automation to full deployment at scale, though, I think what often, it's not that roi, it's the timeline that gets misunderstood. Like all it projects, they tend to take longer. And even when things are made really easy, like with what Project Wisdom is trying to do, semantically enable through low code, no code and the ability to get more accuracy, it just never tends to happen quite as fast. So, but that's not an automation problem, That's just the crux of it. >>Okay. What are some of the, the next things on your plate? You're quite a, a busy guy. We, you, you were at Google, you were at Oracle, you're here today. What are some of the next things that we can expect from Daniel Newman? >>Oh boy, I moved Really, I do move really quickly and thank you for that. Well, I'm very excited. I'm taking a couple of work personal days. I don't know if you're a fan, but F1 is this weekend. I'm the US Grand Prix. Oh, you're gonna Austin. So I will be, I live in Austin. Oh. So I will be in Austin. I will be at the Grand Prix. It is work because it, you know, I'm going with a number of our clients that have, have sponsorships there. So I'll be spending time figuring out how the data that comes off of these really fun cars is meaningfully gonna change the world. I'll actually be talking to Splunk CEO at the, at the race on Saturday morning. But yeah, I got a lot of great things. I got a, a conversation coming up with the CEO of Twilio next week. We got a huge week of earnings ahead and so I do a lot of work on that. So I'll be on Bloomberg next week with Emily Chang talking about Microsoft and Google. Love talking to Emily, but just as much love being here on, on the queue with you >>Guys. Well we like to hear that. Who you're rooting for F one's your favorite driver. I, >>I, I like Lando. Do you? I'm Norris. I know it's not necessarily a fan favorite, but I'm a bit of a McLaren guy. I mean obviously I have clients with Oracle and Red Bull with Ball Common Ferrari. I've got Cly Splunk and so I have clients in all. So I'm cheering for all of 'em. And on Sunday I'm actually gonna be in the Williams Paddock. So I don't, I don't know if that's gonna gimme me a chance to really root for anything, but I'm always, always a big fan of the underdog. So maybe Latifi. >>There you go. And the data that comes off the how many central unbeliev, the car, it's crazy's. Such a scientific sport. Believable. >>We could have Christian, I was with Christian Horner yesterday, the team principal from Reside. Oh yeah, yeah. He was at the Oracle event and we did a q and a with him and with the CMO of, it's so much fun. F1 has been unbelievable to watch the momentum and what a great, you know, transitional conversation to to, to CX and automation of experiences for fans as the fan has grown by hundreds of percent. But just to circle back full way, I was very encouraged with what I saw today. Red Hat, Ansible, IBM Strong partnership. I like what they're doing in their expanded ecosystem. And automation, by the way, is gonna be one of the most robust investment areas over the next few years, even as other parts of tech continue to struggle that in cyber security. >>You heard it here. First guys, investment in automation and cyber security straight from two analysts. I got to sit between. For our guests and John Furrier, I'm Lisa Martin, you're watching The Cube Live from Chicago, Ansible Fest 22. John and I will be back after a short break. SO'S stick around.

>> Announcer: theCube presents HPE Discover 2022, brought to you by HPE. >> Hey, everyone. Welcome back to Las Vegas. This is Lisa Martin with Dave Vellante live at HPE Discover '22. Dave, it's great to be here. This is the first Discover in three years and we're here with about 7,000 of our closest friends. >> Yeah. You know, I tweeted out this, I think I've been to 14 Discovers between the U.S. and Europe, and I've never seen a Discover with so much energy. People are not only psyched to get back together, that's for sure, but I think HPE's got a little spring in its step and it's feeling more confident than maybe some of the past Discovers that I've been to. >> I think so, too. I think there's definitely a spring in the step and we're going to be unpacking some of that spring next with one of our alumni who joins us, Keith White's here, the executive vice president and general manager of GreenLake Cloud Services. Welcome back. >> Great. You all thanks for having me. It's fantastic that you're here and you're right, the energy is crazy at this show. It's been a lot of pent up demand, but I think what you heard from Antonio today is our strategy's changing dramatically and it's really embracing our customers and our partners. So it's great. >> Embracing the customers and the partners, the ecosystem expansion is so critical, especially the last couple of years with the acceleration of digital transformation. So much challenge in every industry, but lots of momentum on the GreenLake side, I was looking at the Q2 numbers, triple digit growth in orders, 65,000 customers over 70 services, eight new services announced just this morning. Talk to us about the momentum of GreenLake. >> The momentum's been fantastic. I mean, I'll tell you, the fact that customers are really now reaccelerating their digital transformation, you probably heard a lot, but there was a delay as we went through the pandemic. So now it's reaccelerating, but everyone's going to a hybrid, multi-cloud environment. Data is the new currency. And obviously, everyone's trying to push out to the Edge and GreenLake is that edge to cloud platform. So we're just seeing tons of momentum, not just from the customers, but partners, we've enabled the platform so partners can plug into it and offer their solutions to our customers as well. So it's exciting and it's been fun to see the momentum from an order standpoint, but one of the big numbers that you may not be aware of is we have over a 96% retention rate. So once a customer's on GreenLake, they stay on it because they're seeing the value, which has been fantastic. >> The value is absolutely critically important. We saw three great big name customers. The Home Depot was on stage this morning, Oak Ridge National Laboratory was as well, Evil Geniuses. So the momentum in the enterprise is clearly present. >> Yeah. It is. And we're hearing it from a lot of customers. And I think you guys talk a lot about, hey, there's the cloud, data and Edge, these big mega trends that are happening out there. And you look at a company like Barclays, they're actually reinventing their entire private cloud infrastructure, running over a hundred thousand workloads on HPE GreenLake. Or you look at a company like Zenseact, who's basically they do autonomous driving software. So they're doing massive parallel computing capabilities. They're pulling in hundreds of petabytes of data to then make driving safer and so you're seeing it on the data front. And then on the Edge, you look at anyone like a Patrick Terminal, for example. They run a whole terminal shipyard. They're getting data in from exporters, importers, regulators, the works and they have to real-time, analyze that data and say, where should this thing go? Especially with today's supply chain challenges, they have to be so efficient, that it's just fantastic. >> It was interesting to hear Fidelma, Keith, this morning on stage. It was the first time I'd really seen real clarity on the platform itself and that it's obviously her job is, okay, here's the platform, now, you guys got to go build on top of it. Both inside of HPE, but also externally, so your ecosystem partners. So, you mentioned the financial services companies like Barclays. We see those companies moving into the digital world by offering some of their services in building their own clouds. >> Keith: That's right. >> What's your vision for GreenLake in terms of being that platform, to assist them in doing that and the data component there? >> I think that was one of the most exciting things about not just showcasing the platform, but also the announcement of our private cloud enterprise, Cloud Service. Because in essence, what you're doing is you're creating that framework for what most companies are doing, which is they're becoming cloud service providers for their internal business units. And they're having to do showback type scenarios, chargeback type scenarios, deliver cloud services and solutions inside the organization so that open platform, you're spot on. For our ecosystem, it's fantastic, but for our customers, they get to leverage it as well for their own internal IT work that's happening. >> So you talk about hybrid cloud, you talk about private cloud, what's your vision? You know, we use this term Supercloud. This in a layer that goes across clouds. What's your thought about that? Because you have an advantage at the Edge with Aruba. Everybody talks about the Edge, but they talk about it more in the context of near Edge. >> That's right. >> We talked to Verizon and they're going far Edge, you guys are participating in that, as well as some of your partners in Red Hat and others. What's your vision for that? What I call Supercloud, is that part of the strategy? Is that more longer term or you think that's pipe dream by Dave? >> No, I think it's really thoughtful, Dave, 'cause it has to be part of the strategy. What I hear, so for example, Ford's a great example. They run Azure, AWS, and then they made a big deal with Google cloud for their internal cars and they run HPE GreenLake. So they're saying, hey, we got four clouds. How do we sort of disaggregate the usage of that? And Chris Lund, who is the VP of information technology at Liberty Mutual Insurance, he talked about it today, where he said, hey, I can deliver these services to my business unit. And they don't know, am I running on the public cloud? Am I running on our HPE GreenLake cloud? Like it doesn't matter to the end user, we've simplified that so much. So I think your Supercloud idea is super thoughtful, not to use the super term too much, that I'm super excited about because it's really clear of what our customers are trying to accomplish, which it's not about the cloud, it's about the solution and the business outcome that gets to work. >> Well, and I think it is different. I mean, it's not like the last 10 years where it was like, hey, I got my stuff to work on the different clouds and I'm replicating as much as I can, the cloud experience on-prem. I think you guys are there now and then to us, the next layer is that ecosystem enablement. So how do you see the ecosystem evolving and what role does Green Lake play there? >> Yeah. This has been really exciting. We had Tarkan Maner who runs Nutanix and Karl Strohmeyer from Equinix on stage with us as well. And what's happening with the ecosystem is, I used to say, one plus one has to equal three for our customers. So when you bring these together, it has to be that scenario, but we are joking that one plus one plus one equals five now because everything has a partner component to it. It's not about the platform, it's not about the specific cloud service, it's actually about the solution that gets delivered. And that's done with an ISV, it's done with a Colo, it's done even with the Hyperscalers. We have Azure Stack HCI as a fully integrated solution. It happens with managed service providers, delivering managed services out to their folks as well. So that platform being fully partner enabled and that ecosystem being able to take advantage of that, and so we have to jointly go to market to our customers for their business needs, their business outcomes. >> Some of the expansion of the ecosystem. we just had Red Hat on in the last hour talking about- >> We're so excited to partner with them. >> Right, what's going on there with OpenShift and Ansible and Rel, but talk about the customer influence in terms of the expansion of the ecosystem. We know we've got to meet customers where they are, they're driving it, but we know that HPE has a big presence in the enterprise and some pretty big customer names. How are they from a demand perspective? >> Well, this is where I think the uniqueness of GreenLake has really changed HPE's approach with our customers. Like in all fairness, we used to be a vendor that provided hardware components for, and we talked a lot about hardware costs and blah, blah, blah. Now, we're actually a partner with those customers. What's the business outcome you're requiring? What's the SLA that we offer you for what you're trying to accomplish? And to do that, we have to have it done with partners. And so even on the storage front, Qumulo or Cohesity. On the backup and recovery disaster recovery, yes, we have our own products, but we also partner with great companies like Veeam because it's customer choice, it's an open platform. And the Red Hat announcement is just fantastic. Because, hey, from a container platform standpoint, OpenShift provides 5,000 plus customers, 90% of the fortune 500 that they engage with, with that opportunity to take GreenLake with OpenShift and implement that container capabilities on-prem. So it's fantastic. >> We were talking after the keynote, Keith Townsend came on, myself and Lisa. And he was like, okay, what about startups? 'Cause that's kind of a hallmark of cloud. And we felt like, okay, startups are not the ideal customer profile necessarily for HPE. Although we saw Evil Geniuses up on stage, but I threw out and I'd love to get your thoughts on this that within companies, incumbents, you have entrepreneurs, they're trying to build their own clouds or Superclouds as I use the term, is that really the target for the developer audience? We've talked a lot about OpenShift with their other platforms, who says as a partner- >> We just announced another extension with Rancher and- >> Yeah. I saw that. And you have to have optionality for developers. Is that the way we should think about the target audience from a developer standpoint? >> I think it will be as we go forward. And so what Fidelma presented on stage was the new developer platform, because we have come to realize, we have to engage with the developers. They're the ones building the apps. They're the ones that are delivering the solutions for the most part. So yeah, I think at the enterprise space, we have a really strong capability. I think when you get into the sort of mid-market SMB standpoint, what we're doing is we're going directly to the managed service and cloud service providers and directly to our Disty and VARS to have them build solutions on top of GreenLake, powered by GreenLake, to then deliver to their customers because that's what the customer wants. I think on the developer side of the house, we have to speak their language, we have to provide their capabilities because they're going to start articulating apps that are going to use both the public cloud and our on-prem capabilities with GreenLake. And so that's got to work very well. And so you've heard us talk about API based and all of that sort of scenario. So it's an exciting time for us, again, moving HPE strategy into something very different than where we were before. >> Well, Keith, that speaks to ecosystem. So I don't know if you were at Microsoft, when the sweaty Steve Ballmer was working with the developers, developers. That's about ecosystem, ecosystem, ecosystem. I don't expect we're going to see Antonio replicating that. But that really is the sort of what you just described is the ecosystem developing on top of GreenLake. That's critical. >> Yeah. And this is one of the things I learned. So, being at Microsoft for as long as I was and leading the Azure business from a commercial standpoint, it was all about the partner and I mean, in all fairness, almost every solution that gets delivered has some sort of partner component to it. Might be an ISV app, might be a managed service, might be in a Colo, might be with our hybrid cloud, with our Hyperscalers, but everything has a partner component to it. And so one of the things I learned with Azure is, you have to sell through and with your ecosystem and go to that customer with a joint solution. And that's where it becomes so impactful and so powerful for what our customers are trying to accomplish. >> When we think about the data gravity and the value of data that put massive potential that it has, even Antonio talked about it this morning, being data rich but insights poor for a long time. >> Yeah. >> Every company in today's day and age has to be a data company to be competitive, there's no more option for that. How does GreenLake empower companies? GreenLake and its ecosystem empower companies to really live being data companies so that they can meet their customers where they are. >> I think it's a really great point because like we said, data's the new currency. Data's the new gold that's out there and people have to get their arms around their data estate. So then they can make these business decisions, these business insights and garner that. And Dave, you mentioned earlier, the Edge is bringing a ton of new data in, and my Zenseact example is a good one. But with GreenLake, you now have a platform that can do data and data management and really sort of establish and secure the data for you. There's no data latency, there's no data egress charges. And which is what we typically run into with the public cloud. But we also support a wide range of databases, open source, as well as the commercial ones, the sequels and those types of scenarios. But what really comes to life is when you have to do analytics on that and you're doing AI and machine learning. And this is one of the benefits I think that people don't realize with HPE is, the investments we've made with Cray, for example, we have and you saw on stage today, the largest supercomputer in the world. That depth that we have as a company, that then comes down into AI and analytics for what we can do with high performance compute, data simulations, data modeling, analytics, like that is something that we, as a company, have really deep, deep capabilities on. So it's exciting to see what we can bring to customers all for that spectrum of data. >> I was excited to see Frontier, they actually achieve, we hosted an event, co-produced event with HPE during the pandemic, Exascale day. >> Yeah. >> But we weren't quite at Exascale, we were like right on the cusp. So to see it actually break through was awesome. So HPC is clearly a differentiator for Hewlett Packard Enterprise. And you talk about the egress. What are some of the other differentiators? Why should people choose GreenLake? >> Well, I think the biggest thing is, that it's truly is a edge to cloud platform. And so you talk about Aruba and our capabilities with a network attached and network as a service capabilities, like that's fairly unique. You don't see that with the other companies. You mentioned earlier to me that compute capabilities that we've had as a company and the storage capabilities. But what's interesting now is that we're sort of taking all of that expertise and we're actually starting to deliver these cloud services that you saw on stage, private cloud, AI and machine learning, high performance computing, VDI, SAP. And now we're actually getting into these industry solutions. So we talked last year about electronic medical records, this year, we've talked about 5g. Now, we're talking about customer loyalty applications. So we're really trying to move from these sort of baseline capabilities and yes, containers and VMs and bare metal, all that stuff is important, but what's really important is the services that you run on top of that, 'cause that's the outcomes that our customers are looking at. >> Should we expect you to be accelerating? I mean, look at what you did with Azure. You look at what AWS does in terms of the feature acceleration. Should we expect HPE to replicate? Maybe not to that scale, but in a similar cadence, we're starting to see that. Should we expect that actually to go faster? >> I think you couched it really well because it's not as much about the quantity, but the quality and the uses. And so what we've been trying to do is say, hey, what is our swim lane? What is our sweet spot? Where do we have a superpower? And where are the areas that we have that superpower and how can we bring those solutions to our customers? 'Cause I think, sometimes, you get over your skis a bit, trying to do too much, or people get caught up in the big numbers, versus the, hey, what's the real meat behind it. What's the tangible outcome that we can deliver to customers? And we see just a massive TAM. I want to say my last analysis was around $42 billion in the next three years, TAM and the Azure service on-prem space. And so we think that there's nothing but upside with the core set of workloads, the core set of solutions and the cloud services that we bring. So yeah, we'll continue to innovate, absolutely, amen, but we're not in a, hey we got to get to 250 this and 300 that, we want to keep it as focused as we can. >> Well, the vast majority of the revenue in the public cloud is still compute. I mean, not withstanding, Microsoft obviously does a lot in SaaS, but I'm talking about the infrastructure and service. Still, well, I would say over 50%. And so there's a lot of the services that don't make any revenue and there's that long tail, if I hear your strategy, you're not necessarily going after that. You're focusing on the quality of those high value services and let the ecosystem sort of bring in the rest. >> This is where I think the, I mean, I love that you guys are asking me about the ecosystem because this is where their sweet spot is. They're the experts on hyper-converged or databases, a service or VDI, or even with SAP, like they're the experts on that piece of it. So we're enabling that together to our customers. And so I don't want to give you the impression that we're not going to innovate. Amen. We absolutely are, but we want to keep it within that, that again, our swim lane, where we can really add true value based on our expertise and our capabilities so that we can confidently go to customers and say, hey, this is a solution that's going to deliver this business value or this capability for you. >> The partners might be more comfortable with that than, we only have one eye sleep with one eye open in the public cloud, like, okay, what are they going to, which value of mine are they grab next? >> You're spot on. And again, this is where I think, the power of what an Edge to cloud platform like HPE GreenLake can do for our customers, because it is that sort of, I mentioned it, one plus one equals three kind of scenario for our customers so. >> So we can leave your customers, last question, Keith. I know we're only on day one of the main summit, the partner growth summit was yesterday. What's the feedback been from the customers and the ecosystem in terms of validating the direction that HPE is going? >> Well, I think the fantastic thing has been to hear from our customers. So I mentioned in my keynote recently, we had Liberty Mutual and we had Texas Children's Hospital, and they're implementing HPE GreenLake in a variety of different ways, from a private cloud standpoint to a data center consolidation. They're seeing sustainability goals happen on top of that. They're seeing us take on management for them so they can take their limited resources and go focus them on innovation and value added scenarios. So the flexibility and cost that we're providing, and it's just fantastic to hear this come to life in a real customer scenario because what Texas Children is trying to do is improve patient care for women and children like who can argue with that. >> Nobody. >> So, yeah. It's great. >> Awesome. Keith, thank you so much for joining Dave and me on the program, talking about all of the momentum with HPE Greenlake. >> Always. >> You can't walk in here without feeling the momentum. We appreciate your insights and your time. >> Always. Thank you you for the time. Yeah. Great to see you as well. >> Likewise. >> Thanks. >> For Keith White and Dave Vellante, I'm Lisa Martin. You're watching theCube live, day one coverage from the show floor at HPE Discover '22. We'll be right back with our next guest. (gentle music)

>>The cube presents HPE discover 2022 brought to you by HPE. >>Hey everyone. Welcome back to the Cube's day one coverage of HPE. Discover 22 live from Las Vegas. Lisa Martin, here with Dave Velante of a couple of guests from red hat. You may have seen some news yesterday. We're gonna be talking about that. Please. Welcome Ryan King, the senior director of hardware partner ecosystem, and Lori Fontine joins us as well. The senior director of global commercial partner ecosystem. Welcome to the program guys. >>Thanks for having us. Yeah, >>Thank you so great to be back in person and nobody word has summit was just last month or so. That's right. Ryan. Talk about hybrid cloud. It's all the buzz. We've been talking a lot about it in the last hour and a half alone. What are some of the trends that, that red hat is seen with respect to hybrid cloud? >>Well, I, I mean, hybrid cloud of red hat has been a trend for quite some time. In fact, we were very early in setting our course towards hybrid cloud with our products and platforms. And that's been a key part of our strategy in terms of the number of transformations have been happening in the enterprise. And with HPE, we're super excited about, you know, we're hitting our stride with OpenShift. I've been working with OpenShift for the better part of my 10 years here at 12 years at red hat, 10 years with OpenShift. And we're very excited about seeing the pattern of going where customers want to build their cloud. It's very important that where, where the market is going. So we're seeing trends from the public cloud now go into edge and telco and 5g and really exceed, see them expanding their infrastructure footprint out to those use cases. And again, we see REL everywhere. So re has continued to expand as well. And then Ansible automation platform has also been a great means of kind of bringing together community for that last mile of automating your entire infrastructure. >>Well, the Lin, the functionality of Linux continues to improve OpenShift is everywhere. I mean, I remember at the red hat summit, I mean, well, we, we, we coined this term super cloud, which is this layer that floats, you know, on-prem took across clouds out to the edge we had Verizon on. They were talking about, you know, 5g developers and how they're developing using, you know, a combination of, of, of OpenShift. So guys have been really crushing it with, with OpenShift. I remember, gosh, I mean, we've been covering, you know, red hat summits for a long time now. And just to see that evolution is actually quite amazing. >>Yeah. It's actually really neat to see our CEOs align too. Right. So the messaging that we've had around hybrid cloud from red hat, like you said, we were kind of the pioneers, honestly, this we've been talking about hybrid cloud from the very beginning. We always knew that it wasn't gonna be public cloud or private cloud. We had to have, you know, hybrid. And, and it's interesting to see that Antonio, you know, took that on and wanted to say, we're gonna do everything as a service right. A few years ago. And, and the whole theme was around hybrid cloud and giving customers that choice. Right? So it's exciting for us to see all of that come together. And I actually worked for HP for like 17 and a half years. So it's really fun for me to be on this side now with red hat and see the messaging come together, the vision come together and just really being able to align and move forward on >>This tremendous amount of transformation in the last few years >>Alone. Oh my gosh, we >>Talk about, you know, customers need choice. They want choice, but you also talked about, we have to meet customers where they are. That seems the last few years to have accelerated, there is no more option for companies. You've gotta meet the customers where they are. >>Exactly. Yeah. And it's all about choice, like you said, and it, everybody's got, you know, their own way to do everything as far as consumption goes and we have to be available and spot on with it, you know, and be able to move quickly with these trends that we're seeing. And so it's great to be aligned. And >>From a partnership standpoint, I mean, you, you mentioned H HP 17 years. I mean, it was, it was a hard to follow company. You had, you had PCs over here, you had services, the kind of the old EDS business. Now there's such a focus absolutely. On this mission, absolutely. Of as a service. And, you know, obviously a key part of that is having optionality and bringing open source tooling into that. I mean, we heard about this in, in spades, at, at red hat summit, which is really interesting this year. It was a smaller VIP event in Boston. And I, and I loved it, you know, cuz it was really manageable. We had all the execs on and customers and partners. It was awesome. What's new since red hat summit. >>Well, I mean, I would say that obviously GreenLake and what we've announced this week is a big new thing for us, but really like we're just continuing on our pattern. We are. Now, if you look at the Q1 report from IBM, you'll see that the growth of the customer base for OpenShift that they reported just continues to go up into the right. You'll see that now, like AMIA is saying that we're like 47.8% of the containers market for the enterprise. You'll see that like we're now in 65% of the fortune 500 with OpenShift, 90% with red hat in general. So we've established our footprint. And when you establish your footprint and customers start taking you out to the edge, we're going into these 5g use cases, we're, we've got an incredible amount happening in the AI space, all these emerging areas of where people are building their cloud, like we're now going to that next level of saying, how do they want to consume it? >>So what's really important to me about that is, is so Omni data around 50% of the market is, is open shift. A people may not realize a lot of people use, you know, do Kubernetes for free, you know, Hey, we're doing Kubernetes, but they don't have that application development framework and all the recovery and all the, the tooling around it. And the reason why I think that's so important, Laurie is ecosystems wanna monetize. So people are paying for things that becomes more interesting and it actually starts to attract people just naturally. >>Yeah, absolutely. And speaking of ecosystem, I mean, that's the beauty of what we're doing with GreenLake too. We're taking on a building block approach. So we're really, it's kind of ISV as a service if you will. And you know, personally, I, this was my baby for the past couple years, trying to make sure that we took into consideration every partner use case, every customer use case. So we created an agreement that would make sense to be able to scale, but also to meet all the demands of our customers. And so the, the what's really exciting about this is now we have a chance to take this building block approach, scale it out to all types of partner types, right throughout the entire ecosystem and build offerings together. That is really exciting for us. And that's where we see the real potential here with GreenLake and with red hat, >>What's actually available inside a GreenLake. >>So we are starting with OpenShift. So OpenShift will be available in Q3 that will follow in Q4 with re and then after that Ansible. So we're, we're moving very quickly to bring our platforms into it and it's really our strategic platforms, but it's all based on customer demand. We know we're seeing amazing transformation of customers moving to Kubernetes. You said, you know, OpenShift is Kubernetes with useful additions to it and an ecosystem around it, right? So that transformation is also happening at the bare metal layer. So we're seeing people move into Kubernetes bare metal, which is an amazing growth market for us. >>Explain those useful additions if you would. So why shouldn't I just go out and, and get the free version of Kubernete? Why should I engage red hat and, and OpenShift? What do I get? >>So you get all the day, two management stuff, you get, we have a whole set of additional stuff you can purchase around it, OpenShift platform. Plus you can get our ACM, our advanced cluster management. So you wanna manage multiple clusters, right? You get the ACS, the security side of it. You can also get ODF. So you get storage built into it as well. And we've done all these integrations. You can manage the whole thing as a cluster or as multiple clusters with the whole enterprise support and the long term support that we provide for these things up to 10 years. So >>When you look at the early days lease of, of Kubernetes, it was really, the focus was on simplicity. You had other platforms that were actually doing more sophisticated cluster management. And the, the committers that in Kubernetes said, you know, we're not gonna do that. We're gonna keep it simple. And so that leave some holes and gaps and you know, they're starting to fill those, but what if, if correct me if I'm wrong, but what red hat has done is said, okay, we're gonna accelerate, you know, the, the, the closing of those gaps and stay ahead and actually offer incremental value. And that's why you're winning in the marketplace. >>Well, we're an open company, so we're still doing everything upstream and open source as we do, of course, sticking with, you know, the APIs and APIs to make this all work, both, you know, in terms of what the community's trying to drive, what we're trying to drive for our customers on their behalf. And then just where things are going from a technology basis, make it a lot of investment, >>But you have to, you have to make a red hat, has to make a choice as to where it puts its commitments. You can't spread yourself too thin, so you gotta pick your spots. And you've, you've proven that you're pretty adept at doing that. >>That just comes back to customer centricity, right. And just knowing where our customers need to take the platform. That's, >>That's easy to say, but it's, it's an art form. And a little bit of science. >>Remember these customers have experts that are deep in this space. So it's like, you know, those experts trust us with where they needed to go. And they trust us to help shepherd that and deliver that as a platform to them. So it's not like anybody tell us what you want, right? Like it's really about like, knowing what's the best way to do it. And working with the people that can help you understand how to apply that to their use case >>And within the customer environment, who are you working with? Who is that key constituent or constituents that are guiding red hat in this direction? >>Well, it's certainly infrastructure folks. So it's your, it's your standard folks that are looking at the, how do we lay down our infrastructure? How do we manage it? How do we grow it? It goes out to the application developers. They're trying to deliver this in a cloud native way. And we have new personas, you know, coming in with the AI practitioners, right? So we've announced at before summit at Invidia's event, their new offering called Invidia AI enterprise. And so that's them bringing in enterprise support for GPU, for Kuda and for a software stack above that to start offering some more support there. So they're certifying OpenShift, we're both certifying the servers that run underneath it, and then they're offering support for their stuff on top of it. And that's a whole new use case for us. >>And, you know, I should also mention that even though this paper use with the GreenLake is new for us, and we just had this big announcement, we have done GreenLake deals though. We've done numerous GreenLake deals with our annual subs, right? So I, so even though this is new to us, as far as, you know, monthly utilization and being able to do this cloud consumption this isn't new to us as two companies coming together, we've been doing GreenLake deals for the past couple years. It's just, now we have this cloud consumption availability, which is really gonna make this thing launch. So, >>So what have been some of the customer benefits so far, you've been doing it for a couple years. The announcement was yesterday, but there's obviously feed on the street going on. What are some of the, the big outcomes that you're seeing customers actually bring to reality? >>I think speed and agility, right? That's the biggest thing with, with our products, being able to have it everything predictable and being able to have it consumed one way, instead of having this fragmented customer experience, which is, you know, what we've seen in the past. So I think that's the biggest thing is speed agility and just, you know, a really good customer experience at this point. >>Go get it, please. >>I would say the customer experience is critical. Yes. That's one of the things that we know that in terms of, of patients wearing thin the last couple of years, people expect to have a really strong consumer experience regardless of what you're doing, regardless of what industry and so attention and mind on that is a differentiator in my opinion. >>Absolutely. Yeah. And we've gotta constantly keep our eye on that. I mean, that's, that's our north star, if you will. Right. So, and Lori, >>I know you've saying you're, you've done GreenLake deals in the past, but what feels different to me now in that it's actually coalescing some of the things that Alma Russo announced this morning, the platform on which, you know, ISV is a service. I think you, you called it. Yeah. You, it, it now seems like, you know, look a couple years ago, HP said, okay, this is the direction that we're going. Yeah. They weren't there at that time. And they're still not there. There's a lot of work to be, to be done. But now it's starting to form. You're seeing, you know, the pieces come together, the puzzle pieces that sort of substrate being laid out. And now you're hoping that we see the steep part of the S-curve and that's what customers I think are expecting. >>Right. And it's bringing that operating model to move to a monthly model so they can do pay as you go. Right. And that pairs up nicely with like the cloud native capabilities we're bringing to OpenShift and hybrid cloud in general. So it's, it just shows like we're already getting demand from customers. It's saying like, this is part of our model. Like we know a certain amount of infrastructure we wanna own, and we just wanna own it outright, but there's a lot that they want to have flexibility on. And so being able to add that portion to it is just, you know, gonna help us both. >>And you think about the critical aspects of, of the cloud operating model. It's obviously pay as you go it's, you know, massive scale it's ecosystem enablement, and also automation. I mean, that is, that is a key, what's your point of view on that? You guys with Ansible, you, you, you know, you go back to a couple years ago and it was, you know, there was this, there were a lot of other tooling, but now, I mean, Ansible is really taken off. Yeah. >>It's just, you know, Cinderella story, right? Like it really an amazing community driven thing where we just knew, we all know this, right. You have, when you get to the very last mile of doing infrastructure management, there's a variety of devices, there's variety, a variety of vendors. And then you have like the variety of skills of the people that have to figure out how to do automate all of this. And what Ansible did is it provided a common language across all of that. And so what we do with automation, our, an ible automation platform is we make it. So now teams can manage all of this together and they can share their playbooks and they can host that privately for all their enterprise stuff that they need to do. So it's just, you know, it fits our DNA so well to have something so community driven now with a really nice enterprise message wrapped around it. And it's playing out very well for where, you know, hybrid cloud. Right. Cause there's some more additional variety. You need to be able to manage, you know, across all of your different footprints, because really it's like, it's not just about flexibility and scale up scale down it's where do you need it to run at what time? Right. And that, that last leg Ansible plays a key role in that. >>And we actually, Ansible will be coming further down the, you know, the patch. I know we're gonna talk a little bit about what's available today versus what's available down the road, but yeah, we have that on the radar. So right outta the gate, we're working on OpenShift, obviously bare metal. And we see that happening in Q3 and then behind that as well in Q4 and then Ansible is gonna be right behind that. So that's kind of the order that, and there's other pieces, right? So our whole portfolio is basically available to HP right now. It's just making sure that we can operationalize everything and have the best experience >>All inside of GreenLake, >>All inside a GreenLake. Yeah. Pretty neat. Lori >>Question for you. You've been, you were with HP for a very long time. This is obviously the first discover in three years in person. Exactly. You know, three years ago, Antonio near stood on stage and said, we are going to buy 20, 22. And here we are deliver everything as a service, as a partner and as a former HP, what are you seeing at this discover 22? >>It's it's so interesting. I it's such a sea change if you will. Right. And having come from HPE, I actually led the software as a service organization for a while on the software side of things. And we thought that was like state of the art and cutting edge that was 10, 11, 12 years ago. Right. So to actually see this come to life, because we were all thinking really, everything is a service. How are you gonna do that? Like your entire portfolio is gonna be available. Like that is lofty. Right. And having worked at HP, I thought, wow, I don't, you know, I know things take time. And, but actually just even being around the showcase here and watching everything come to life is amazing. Cause I, I, you know, I, I was very positive about it, but at the same time, it's like that, that was a big goal three years. Right. And it's, I'm seeing it happen >>A big goal in two of those years during a pandemic. Right. So right. Talk about lofty. Oh my gosh. Quite a bit of accomplishments guys. Thank you so much for joining David me on the program talking about actually guys, this is great. What red hat and HPE are doing your power partnership, power ship. Is that a word? It is now your power. >>I like >>That with GreenLake. We appreciate that. We'll look forward to having you guys back on. >>Thank you so much, guys. >>All right. For our guests. I'm Lisa Martin. He's Dave ante. We are at HPE discover 22 live from the show floor in Las Vegas. This is just day one of our cupboards stick around. We'll be right back with our next guest.

[Music] thecube's coverage of red hat summit 2022 thecube has been covering red hat summit for a number of years of course the last two years were virtual coverage now the red hat summit is one of the industry's most premier events and and typically red hat summits are many thousands of people i think the last one i went to was eight or nine thousand people very heavy developer conference this year red hat has taken a different approach it's a hybrid event it's kind of a vip event at the westin in boston with a lot more executives here than we would normally expect versus developers but a huge virtual audience my name is dave vellante i'm here with my co-host paul gillin paul this is a location that you and i have broadcast from many times and um of course 2019 the summer of 2019 ibm acquired red hat and um we of course we did red hat summit that year but now we're seeing a completely new red hat and a new ibm and you wouldn't know ibm owned red hat for what they've been talking about at this conference we just came out of the keynote where uh in the in the hour-long keynote ibm was not mentioned once and only appeared the logo only appeared once on the screen in fact so this is uh very much red hat being red hat not being a subsidiary at ibm and perhaps that's justified given that ibm's track record with acquisitions is that they gradually envelop the acquired company and and it becomes part of the ibm board yeah they blue wash the whole thing right it's ironic because ibm think is going on right across the street arvin krishna is here but no presence here and i think that's by design i mean it reminds me of when you know emc owned vmware you know the vmware team didn't want to publicize that they had an ecosystem of partners that they wanted to cater to and they wanted to treat everybody equally even though perhaps behind the scenes they were forced to do certain things that they might not have necessarily wanted to because they were owned by another company and i think that you know certainly ibm's done a good job of leaving the brand separate but when they talk about the con the conference calls ibm's earnings calls you certainly get a heavy dose of red hat when red hat was acquired by ibm it was just north of three billion dollars in revenue obviously ibm paid 34 billion dollars for the company actually by today's valuations probably a bargain you know despite the market sell-off in the last several months uh but now we've heard public statements from arvind kushner that that red hat is a 5 billion plus revenue company it's a little unclear what's in there of course when you listen to ibm earnings you know consulting is their big business red hat's growing at 21 but when i remember paul when red hat was acquired stu miniman and i did a session and i said this is not about cloud this is about consulting and modernizing applications and sure there's some cloud in there with openshift but from a financial standpoint ibm was able to take red hat and jam it right into its application modernization initiatives so it's hard to tell how much of that 5 billion is actually you know legacy red hat but i guess it doesn't matter anymore it's working ibm mathematics is notoriously opaque they if the business isn't going well it'll tend to be absorbed into another number in the in the earnings report that that does show some growth so we've heard uh certainly ibm talks a lot about red hat on its earnings calls it's very clear that red hat is the growth engine within ibm i'd say it's a bit of the tail wagging the dog right now where red hat really is dictating where ibm goes with its hypercloud strategy which is the foundation not only of its technology portfolio but of its consulting business and so red hat is really in the driver's seat of of hybrid cloud and that's the future for ibm and you see that very much at this conference where uh red hat is putting out its uh series of announcements today about improvements to his hybrid cloud the new release of route 9 red hat enterprise linux 9 improvements to its hybrid cloud portfolio it very much is going its own way with that and i sense that ibm is going to go along with wherever red hat chooses to go yeah i think you're absolutely right if by the way if you go to siliconangle.com paul just published a piece on red hat reds hats their roll out of their parade which of course is as you pointed out led by enterprise linux but to your point about hybrid cloud it is the linchpin of of certainly ibm strategy but many companies hybrid cloud strategies if you think about it openshift in particular it's it's the modern application development environment for kubernetes you can get kubernetes you can buy eks you can get that for free in a lot of places but you have to do dozens and dozens of things and acquire dozens of services to do what openshift does to get the reliability the recoverability the security and that's really red hat's play and they're the the thing about red hat combining with linux their linux heritage they're doing that everywhere it's going to open shift everywhere red hat everywhere whether it's on-prem in aws azure google out to the edge you heard paul cormier today saying he expects that in the next several years hardware is going to become one of the most important you know factors i agree i think we're going to enter a hardware renaissance you've seen the work that we've done on arm i think 2017 was when red hat and arm announced kind of their initial collaboration could have even been before that today we're hearing a lot about intel and nvidia and so affinity with all of these alternative processes i think they did throw in today in the keynote power and so i think i heard that that was the other ibm branding they sort of tucked that in there but the point is red hat runs everywhere so it's fundamental to building out hybrid cloud and that is fundamental to a lot of company strategies and red hat has been all over kubernetes with openshift it's i mean it's a drum beat here uh the openshift strategy is what really makes hybrid cloud possible because kubernetes is what makes it possible to shift workloads seamlessly from platform to platform you make an interesting point about hardware we have seen kind of a renaissance in hardware these last couple of years as these specific chipsets and uh and even full-scale processors have come to market we're seeing several in the ai area right now where startups are developing full-blown chipsets and and systems uh just for ai processing and nvidia of course that's that's really kind of their stock and trade these days so uh a a company that can run across all of those different platforms a platform like like rel which can run all across those different platforms is going to have a leg up on on anybody else and the implications for application development are considerable when you when you think about we talk about a lot about these alternative processes when flash replaced the spinning disk that had a huge impact on how applications are developed developers now didn't have to wait for that that disc to spin even though it's spinning very fast it's mechanical compared to electrons forget it and and the second big piece here is how memory is actually utilized the x86 you know traditional x86 you know memory everything goes through that core processor intel for years grabbed more and more function and you're seeing now that function become dispersed in fact a lot of people think we're moving from a processor-centric world to a connect centric world meaning connecting all these piece parts alternative processors memory controllers you know storage controllers io network interface cards smartnics and things like that where the communication across those resources is now where a lot of the innovation is going you see you're seeing a lot of that and now of course applications can take advantage of that especially now at the edge which is just a whole new frontier the edge certainly is part of that equation when you look at machine learning at training machine learning models the cpu actually does relatively little work most of it is happening in gpus in these parallel processes that are going on and the cpu is kind of acting as a traffic cop and you see that in the edge as well it's the same model at the edge where more of the intelligence is going to be out in discrete devices spread across the network and the cpu is going to be less of a uh you know less of a engine of intelligence at the same time though we've got cpus with we've got 100 core cpus are on the horizon and there are even 200 and 300 core cpus that we may see in the next uh in the next couple of years so cpus aren't standing still they are evolving to become really kind of super traffic cops for all of these other processors out in the network and on the edge so it's a very exciting time to be in hardware because so much innovation is happening really at the microprocessor level well we saw this you and i lived through the pc era and we saw a whole raft of applications come about as a result of the microprocessor the shift of the microprocessor-based economy we're going to see so we are seeing something similar with mobile and the edge you know just think about some of the numbers if you think about the traditional moore's law doubling a number of transistors every let's call it two years 18 to 24 months pat gelsinger at intel promises that intel is on that pace still but if you look at the apple m1 ultra they increased the transistor density 6x in the last 15 months okay so where is this another data point is the historical moore's law curve is 40 that's moderating to somewhere down you know down in the low 30s if you look at the apple a series i mean that thing is on average increasing performance at 110 a year when you add up into the combinatorial factors of the cpu the neural processing unit the gpu all the accelerators so we are seeing a new era the thing i i i wanted to bring up paul is you mentioned ai much of the ai work that's done today is modeling that's done in the cloud and when we talk about edge we think that the future of ai is ai inferencing in real time at the edge so you may not even be persisting that data but you're going to create a lot of data you're going to be operating on that data in streams and it's going to require a whole new new architectural thinking of hardware very low cost very low power very high performance to drive all that intelligence at the edge and a lot of that data is going to stay at the edge and and that's we're going to talk about some of that today with some of the ev innovations and the vehicle innovations and the intelligence in these vehicles yeah and in talking in its edge strategy which it outlined today and the announcements that are made today red hat very much uh playing to the importance of being able to run red hat enterprise linux at the edge the idea is you do these big machine learning models centrally and then you you take the you take what results from that and you move it out to smaller processors it's the only way we can cope with it with the explosion of data that will be uh that these sensors and other devices will be generating so some of the themes we're hearing in the uh announcements today that you wrote about paul obviously rel9 is huge uh red hat enterprise linux version nine uh new capabilities a lot of edge a lot of security uh new cross portfolio capabilities for the edge security in the software supply chain that's a big conversation especially post solar winds managed ansible when you think about red hat you really i think anyway about three things rel which is such as linux it powers the internet powers everything uh you think of openshift which is application development you think about ansible which is automation so itops so that's one of the announcements ansible on azure and then a lot of hybrid cloud talk and you're gonna hear a lot of talk this week about red hat's cloud services portfolio packaging red hat as services as managed services that's you know a much more popular delivery mechanism with clients because they're trying to make it easy and this is complicated stuff and it gets more complicated the more features they add and the more the more components of the red hat portfolio are are available it's it's gonna be complex to build these hybrid clouds so like many of these so thecube started doing physical events last summer by the way and so this is this is new to a lot of people uh they're here for the first time people are really excited we've definitely noticed a trend people are excited to be back together paul cormier talked about that he talked about the new normal you can define the new normal any way you want so paul cormier gave the uh the the intro keynote bidani interviewed amex stephanie cheris interviewed accenture both those firms are coming out stephanie's coming on with the in accenture as well matt hicks talked about product innovation i loved his reference to ada lovelace that was very cool he talked about uh serena uh ramyanajan a famous mathematician who nobody knew about when he was just a kid these were ignored individuals in the 1800s for years and years and years in the case of ada lovelace for a century even he asked the question what if we had discovered them earlier and acted on them and been able to iterate on them earlier and his point tied that to open source very brilliantly i thought and um keynotes which i appreciate are much shorter much shorter intimate they did a keynote in the round this time uh which i haven't seen before there's maybe a thousand people in there so a much smaller group much more intimate setting not a lot of back and forth but uh but there is there is a feeling of a more personal feel to this event than i've seen it past red hat summits yeah and i think that's a trend that we're going to see more of where the live audience is kind of the on the ground it's going to the vip audience but still catering to the virtual audience you don't want to lose them so that's why the keynotes are a lot tighter okay paul thank you for setting up red hat summit 2022 you're watching the cube's coverage we'll be right back wall-to-wall coverage for two days right after this short break [Music] you

>>To the Seaport in Boston, Massachusetts, everybody's buzzing. The Bruins are playing tonight. They tied it up. The Celtics tied it up last night. We're excited. We don't talk about the red Sox. Red Sox are getting struggles, but you know, we have good distractions. Paul goer is here. He's the president and chief executive officer at red hat and also a Boston fan of great to see, of course, you too. >>Nice to see you guys, you know, it's been a, it's been a while. >><laugh> yeah, we saw you, you know, online and virtually for a couple of years there, but, uh, you know, we've been doing red hat summit for a long, long time. Yeah, of course we were talking earlier. It's just much more intimate, kind of a VIP event, a few more suit jackets here. You know, I got my tie on, so I don't get too much grief. I usually get grief when I wear a tie of red hat summit, but it's a different format this year. Compressed keynotes. Your keynote was great. The new normal, sometimes we call it the new abnormal <laugh>, uh, but you know, how do you feel? >>I, I, I, I feel great. First of all, you know, combination today, virtual audience in, in house audience here today. I think we're gonna see a lot of that in the future. I mean, we designed the event around that and I, I think it, I think it played pretty well. Kudos, kudos to our team. You're right. It's, it's, it's a bit more intimate even the way it was set up, but those are the conversations we like having with our customers and our partners, much more partner centric, uh, as well right now, as well. >>You know, we were talking about, you know, hybrid cloud. It was kind of, you know, it was a good marketing term. And, but now it's, it's, it's become the real thing. I've said many times the, the definition of cloud is changing. It's expanding it's no, the cloud is no longer this remote set of services, you know, somewhere up in the cloud, it's on prem connecting to a cloud across clouds, out to the edge and you need capabilities that work everywhere. And that's what red hat did. The market's just swimming toward you. >>Yeah. I mean, you look at it, you know, I was, uh, you know, if you look at it, you know, the clouds are powerful unto themselves, right? The clouds are powerful unto themselves. They're all different. Right? And that that's, I mean, hardware vendors were, were similar, but different, same thing. You need that connective tissue across, across the whole thing. I mean, as I said, in my keynote today, I remember talking to some of our CIOs and customers 10 years ago and they said, we're going 90% of our apps tomorrow to one cloud. And we knew that wasn't practical because of course the clouds are built from Linux. So we knew it was underneath the hood and, and what's happened. It's taken some time, but as they started to get into that, they started to see, well, maybe one cloud's more suited for one application than the other, these apps. You may have to keep on premise, but you know, what really exploded at the, the, the hybrid thing, the edge. Now they're putting things at the edge, the GM announcement tell you, I know you're gonna talk to Francis. Yeah, yeah. Later. I mean, that's, that's a mini data center in, in every cloud, but that's still under the purview of the CIO, you know? So, so, so that's what hybrid's all about is tying all those pieces together, cuz it got more powerful, but it also more complex. >>You mentioned being the connective tissue, but we don't hear as much talk about multi-cloud seems to me, as we used to this conference has been all about hybrid cloud. You don't really talk about multi-cloud. How important is that to the red hat strategy, being that consistent layer? >>It's probably my mistake or our mistake because multi's more prevalent and more important than just hybrid alone. I mean, hybrid hybrid started from on-premise to one part to any one particular cloud. That was the, the first thought of hybrid. But as I said, as, as, as um, some of the cloud providers became so big, um, every, every CIO I talked to, whether they know whether they know it or not most do are in a multi environment for a whole bunch of reasons, right. You know, one cloud provider might be better in a different part of the world. And another one cloud provider might have a better service than another. Some just don't like to be stuck to one it's it's really hybrid multi. We should, we should train ourselves to every time we say hybrid, say multi, because that's really, that's really what it is. It, I think that happened overnight with, with Microsoft, you know, with Microsoft they've, they've, they've really grown over the last few years, so has Amazon for that matter. But Microsoft really coming up is what really made it a, a high, a multi world. >>Microsoft's remarkable what, what they're doing. But I, I, I have a different thinking on this. I, I heard Chuck Whitten last week at, at the Dell conference he used, he said used the phrase a multicloud, uh, by default versus multi-cloud by design. And I thought that was pretty interesting because I've said that multi-cloud is largely multi-vendor, you know? And so hybrid has implications, right? We, we bring and a shesh came up with a new term today. Metacloud I use Supercloud I like Metacloud better because something's happening, Paul. It feels like there's this layer abstraction layer that the underlying complexity is hidden. Think about OpenShift. Yeah. I could buy, I could get OpenShift for free. Yeah. I mean, I could, and I could cobble together and stitch together at 13, 15 dozens of different services and replicate, but I don't, I don't want that complexity. I want you to hide that complexity. I want, I'd rather spend money on your R and D than my engineering. So something's changing. It feels like >>You buy that. I totally buy that. I mean, you know, I, I, I'm gonna try to not make this sound like a marketing thing because it's not, not fair enough. Right. I mean, I'm engineer at heart, you know that, so, >>Okay. >>I really look to what we're trying to do is we're building a hybrid multi cloud. I mean that we, I look at us as a cloud provider spanning the hybrid multi all the way out to the edge world, but we don't have the data centers in the back. Like the cloud providers do in and by that is you're seeing our products being consumed more like cloud services because that's what our customers are demanding. Our, our products now can be bought out of the various marketplaces, et cetera. You're seeing different business models from us. So, uh, you're seeing, uh, committed spend, for example, like the cloud providers where a customer will buy so much up front and sort of just work it down. You're seeing different models on how they're consumed, consumption, based pricing. These, these are all things that came from the cloud providers and customers buying like that. >>They now want that across their entire environment. They don't wanna buy differently on premise or in one cloud and they don't wanna develop differently. They don't wanna operate differently. They don't wanna have to secure it differently. Security's the biggest thing with, with our, with our customers, because hybrid's powerful, but you no longer have the, you know, your security per perimeter, no longer the walls of your data center. You know, you're, you're responsible as a CIO. You're responsible for every app. Yeah. No matter where it's running, if that's the break in point, you're responsible for that. So that's why we've done things like, you know, we cried stack rocks. We've, we've built it into the container Kubernetes platform that spans those various footprints because you no longer can just do perimeter security because the perimeter is, is very, very, very large right now >>Diffuse. One of the thing on the multi-cloud hyper skills, I, I, red hat's never been defensive about public cloud. You, I think you look at the a hundred billion dollars a year in CapEx spend that's a gift to the industry. Not only the entire it industry, but, but the financial services companies and healthcare companies, they can build their own hybrid clouds. Metacloud super clouds taking advantage of that, but they still need that connective tissue. And that's where >>We products come in. We welcome our customers to go to, to the public cloud. Um, uh, look, it's it's. I said a long time ago, we said a long time it was gonna be a hybrid. Well, I should have said multi anybody said hybrid, then it's gonna be a hybrid world. It is. And it doesn't matter if it's a 20, 80, 80, 20, 40, 60, 60, 40. It's not gonna be a hundred percent anywhere. Yeah. And, and so in that, in that definition, it's a hybrid multi world. >>I wanna change the tune a little bit because I've been covering IBM for 40 years and seen a lot of acquisitions and see how they work. And usually it follows the same path. There's a commitment to leaving the acquire company alone. And then over time that fades, the company just becomes absorbed. Same thing with red hat. It seems like they're very much committed to, to, to leaving you alone. At least they said that upon the acquisition, have they followed through on that promise? >>I have to tell you IBM has followed through on every commitment they've made, made to us. I mean, I, I owe it, I owe a lot of it to Arvin. Um, he was the architect of the deal, right. Um, we've known each other for a long time. Um, he's a great guy. Um, he, uh, he, he believes in it. It's not, he's not just doing it that way because he thinks, um, something bad will happen if he doesn't, he's doing it that way. Cuz he believes in that our ecosystem is what made us. I mean, I mean, even here it's about the partners in the ecosystem. If you look at what made REL people think what made red hat as a company was support, right. Support's really important. Small piece of the value proposition life cycle supports certainly their life cycle a 10 year life cycle just came out of a, a, a customer conference asking about the life cycle and could we extend it to 15 years? You know? Um, the ecosystem is probably the most important part of, of, of, of the, of the overall value proposition. And Arvin knows in IBM knows that, you know, we have to be neutral to be able to do everything the same for all of our ecosystem partners. Some that are IBM's competitors, even. So, >>So we were noticing this morning, I mean, aside from a brief mention of power PC and the IBM logo during, at one point, there was no mention of IBM during the keynote sessions this morning. Is that intentional? Or is that just >>No, no, it it's, it's not intentional. I mean, I think that's part of, we have our strategy to drive and we're, we're driving our, our strategy. We, we, we IBM great partner. We look at them as a partner just as we do our, our many other partners and we won't, you know, we wouldn't, we wouldn't do something with our products, um, for I with IBM that we wouldn't offer to our, our entire ecosystem. >>But there is a difference now, right? I don't know these numbers. Exactly. You would know though, but, but pre 2019 acquisition red hat was just, I think north of 3 billion in revenue growing at maybe 12% a year. Something like that, AR I mean, we hear on the earnings calls, 21% growth. I think he's publicly said you're north of 5 billion or now I don't know how much of that consulting gets thrown in. IBM likes to, you know, IBM math, but still it's a much bigger business. And, and I wonder if you could share with us, obviously you can't dig into the numbers, but have you hired more people? I would imagine. I mean, sure. Like what's been different from that standpoint in terms of the accelerant to your >>Business. Yeah. We've been on the same hiring cycle percentage wise as, as we, we always were. I mean, I think the best way to characterize the relationship and where they've helped is, um, Arvin, Arvin will say, IBM can be opinionated on red hat, but not the other way around <laugh>. So, so what that, what that means is they had a lot of, they had, they had a container based Linux platform. Yeah, right, right. They, they had all their, they were their way of moving to the cloud was that when we came in, they actually stopped that. And they standardized on OpenShift across all of their products. We're now the vehicle that brings the blue software products to the hybrid cloud. We are that vehicle that does it. So I think that's, that's how, that's how they, they look about it. I mean, I know, I mean in IBM consulting, I know, I know they have a great relationship with Microsoft of course. >>Right. And so, so that's, that's how to really look at it. They they're opinionated on us where we not the other way around, but that, but they're a great partner. And even if we're at two separate companies, we'd do be doing all the same things we're doing with them. Now, what they do do for us can do for us is they open a lot of doors in many cases. I mean, IBM's been around for over a hundred years. So in many cases, they're in, in, in the C-suite, we, we may be in the C suite, but we may be one layer down, one, two layers down or something. They, they can, they help us get access. And I think that's been a, a part of the growth as well as is them talking into their, into, into their >>Constituents. Their consulting's one of the FA if not the fastest growing part of their business. So that's kind of the tip of the spear for application modernization, but enough on IBM you said something in your keynote. That was really interesting to me. You said, you, you, you didn't use the word hardware Renaissance, but that my interpretation was you're expecting the next, you know, several years to be a hardware Renaissance. We, we certainly have done relationships with arm. You mentioned Nvidia and Intel. Of course, you've had relationships with Intel for a long time. And we're seeing just the spate of new hardware developments, you know, does hardware matter? I'll ask you, >>Oh, oh, I mean the edge, as I said, you're gonna see hardware innovation out in the edge, software innovation as well. You know, the interesting part about the edge is that, you know, obviously remade red hat. What we did with REL was we did a lot of engineering work to make every hardware architecture when, when it was, when, when the world was just standalone servers, we made every hardware architecture just work out of the box. Right? And we did that in such, because with an open source development model. So embedded in our psyche, in our development processes is working upstream, bringing it downstream 10 years, support all of that kind of thing. So we lit up all that hardware. Now we go out to the edge, it's a whole new, different set of hardware innovation out at the edge. We know how to do that. >>We know how to, we know how to make hardware, innovation safe for the customer. And so we're bringing full circle and you have containers embedded in, in Linux and REL right now as well. So we're actually with the edge, bringing it all full circle back to what we've been doing for 20 plus years. Um, on, on the hardware side, even as a big part of the world, goes to containers and hybrid in, in multi-cloud. So that's why we're so excited about, about, about the edge, you know, opportunity here. That's, that's a big part of where hybrid's going. >>And when you guys talk about edge, I mean, I, I know a lot of companies will talk about edge in the context of your retail location. Okay. That's fine. That's cool. That's edge or telco that that's edge. But when you talk about, um, an in vehicle operating system, right. You know, that's to me the far edge, and that's where it gets really interesting, massive volumes, different architectures, both hardware and software. And a lot of the data may stay. Maybe it doesn't even get persisted. May maybe some comes back to the club, but that's a new >>Ballgame. Well, think about it, right? I mean, you, if you listen, I think you, right. My talk this morning, how many changes are made in the Linux kernel? Right? You're running in a car now, right? From a safety perspective. You wanna update that? I mean, look, Francis talked about it. You'll talk to Francis later as well. I mean, you know, how many, how many in, in your iPhone world Francis talked about this this morning, you know, they can, they can bring you a whole new world with software updates, the same in the car, but you have to do it in such a way that you still stay with the safety protocols. You're able to back things out, things like that. So it's open source, but getting raw upstream, open source and managing itself yourself, I just, I'm sorry. It takes a lot of experience to be able to be able to do those kinds of things. So it's secure, that's insecure. And that's what that's, what's exciting about it. You look at E the telco world look where the telco world came from in the telco world. It was a hardware stack from the hardware firmware operating system, every service, whether it was 9 1, 1 or 4, 1, 1 was its own stack. Yep. In the 4g, 3g, >>4g >>Virtualized. Now, now it's all software. Yeah. Now it's all software all the way out to the cell tower. So now, so, so now you see vendors out there, right? As an application, as a container based application, running out, running in the base of a cell tower, >>Cell tower is gonna be a little mini data >>Center. Yeah, exactly. Because we're in our time here asking quickly, because you've been at red hat a long time. You, you, you, uh, architected a lot of the reason they're successful is, is your responsibility. A lot of companies have tried to duplicate the red hat model, the, the service and support model. Nobody has succeeded. Do you think anybody ever will or will red hat continue to be a unicorn in that respect? >>No, I, I, I think, I think it will. I think open source is making it into all different parts of technology. Now I have to tell you the, the reason why we were able to do it is we stayed. We stayed true to our roots. We made a decision a long time ago that we weren't gonna put a line, say everything below the line was open and above the line was closed. Sometimes it's hard sometimes to get a differentiation with the competition, it can be hard, but we've stayed true to that. And I, to this day, I think that's the thing that's made us is never a confusion on if it's open or not. So that forces us to build our business models around that as well. But >>Do you have a differentiated strategy? Talk about that. What's your what's your differentiation >>Are, are, well, I mean, with the cloud, a differentiation is that common cloud platform across I differentiate strategy from an open source perspective is to, to sort make open source consumable. And, and it's even more important now because as Linux Linux is the base of everything, there's not enough skills out there. So even, even a container platform like open source op like OpenShift, could you build your own? Certainly. Could you keep it updated? Could you keep it updated without breaking all the applications on top? Do you have an ecosystem around it? It's all of those things. It was, it was the support, the, the, the hardening the 10 year to predictability the ecosystem. That was, that was, that is the secret. I mean, we even put the secret out as open. >>Yeah, <laugh> right. Free, like a puppy, as they say. All right, Paul, thanks so much for coming back in the cubes. Great to see you face to face. Nice to see you guys get it. All right. Keep it right there. Dave Valante for Paul Gill, you're watching the cubes coverage of red hat summit, 2022 from Boston. Be right back.

welcome back to the seaport in boston massachusetts with cities crazy with bruins and celtics talk but we're here we're talking red hat linux open shift ansible and ashesh badani is here he's the senior vice president and the head of products at red hat fresh off the keynotes had amex up in the state of great to see you face to face amazing that we're here now after two years of of the isolation economy welcome back thank you great to see you again as well and you as well paul yeah so no shortage of announcements uh from red hat this week paul wrote a piece on siliconangle.com i got my yellow highlights i've been through all the announcements which is your favorite baby hard for me to choose hard for me to choose um i'll talk about real nine right well nine's exciting um and in a weird way it's exciting because it's boring right because it's consistent three years ago we committed to releasing a major well uh every three years right so customers partners users can plan for it so we released the latest version of rel in between we've been delivering releases every six months as well minor releases a lot of capabilities that are bundled in around security automation edge management and then rel is also the foundation of the work we announced with gm with the in-vehicle operating system so you know that's extremely exciting news for us as well and the collaboration that we're doing with them and then a whole host of other announcements around you know cloud services work around devsecops and so on so yeah a lot of news a lot of announcements i would say rel nine and the work with gm probably you know comes right up to the top i wanted to get to one aspect of the rail 9 announcement that is the the rose centos streams in that development now in december i think it was red hat discontinued development or support for for centos and moved to central streams i'm still not clear what the difference is between the two can you clarify that i think we go into a situation especially with with many customers many partners as well that you know didn't sort of quite exactly uh get a sense of you know where centos was from a life cycle perspective so was it upstream to rel was it downstream to rel what's the life cycle for itself as well and then there became some sort of you know implied notions around what that looked like and so what we decided was to say well we'll make a really clean break and we'll say centos stream is the upstream for enterprise linux from day one itself partners uh you know software partners hardware partners can collaborate with us to develop rel and then take it all the way through life cycle right so now it becomes a true upstream a true place for development for us and then rel essentially comes uh out as a series of releases based on the work that we do in a fast-moving center-os environment but wasn't centos essentially that upstream uh development environment to begin with what's the difference between centos stream yeah it wasn't wasn't um it wasn't quite upstream it was actually a little bit downstream yeah it was kind of bi-directional yeah and yeah and so then you know that sort of became an implied life cycle to it when there really wasn't one but it was just became one because of some usage and adoption and so now this really clarifies the relationship between the two we've heard feedback for example from software partners users saying hey what do i do for development because i used you know centervis in the past we're like yup we have real for developers available we have rel for small teams available we have rel available for non-profit organizations up and so we've made rail now available in various form factors for the needs that folks had and they were perhaps using centos for because there was no such alternative or rel history so language so now it's this clarity so that's really the key point there so language matters a lot in the technology business we've seen it over the years the industry coalesces around you know terminology whether it was the pc era everything was pc this pc that the internet era and and certainly the cloud we we learned a lot of language from the likes of you know aws two pizza teams and working backwards and things like that became common commonplace hybrid and multi-cloud are kind of the the parlance of the day you guys use hybrid you and i have talked about this i feel like there's something new coming i don't think my term of super cloud is the right necessary terminology but it signifies something different and i feel like your announcements point to that within your hybrid umbrella point being so much talk about the edge and it's we heard paul cormier talk about new hardware architectures and you're seeing that at the edge you know what you're doing with the in-vehicle operating system these are new the cloud isn't just a a bunch of remote services in the cloud anymore it's on-prem it's a cloud it's cross-clouds it's now going out to the edge it's something new and different i think hybrid is your sort of term for that but it feels like it's transcending hybrid are your thoughts you know really really great question actually since you and i talked dave i've been spending some time you know sort of noodling just over that right and you're right right there's probably some terminology something sort of you know that will get developed you know either by us or you know in collaboration with the industry you know where we sort of almost have the connection almost like a meta cloud right that we're sort of working our way towards because there's if you will you know the cloud right so you know on premise you know virtualized uh bare metal by the way you know increasingly interesting and important you know we do a lot of work with nvidia folks want to run specific workloads there we announced support for arm right another now popular architecture especially as we go out to the edge so obviously there's private cloud public cloud then the edge becomes a continuum now you know on that process we actually have a major uh uh shipping company so uh a cruise lines that's talking about using openshift on cruise lines right so you know that's the edge right last year we had verizon talking about you know 5g and you know ran in the next generation there to then that's the edge when we talk to retail the store front's the edge right you talk to a bank you know the bank environments here so everyone's got a different kind of definition of edge we're working with them and then when we you know announce this collaboration with gm right now the edge there becomes the automobile so if you think of this as a continuum right you know bare metal private cloud public cloud take it out to the edge now we're sort of almost you know living in a world of you know a little bit of abstractions and making sure that we are focused on where uh data is being generated and then how can we help ensure that we're providing a consistent experience regardless of you know where meta meta cloud because i can work in nfts i can work a little bit we're going to get through this whole thing without saying metaverse i was hoping i do want to ask you about about the edge and the proliferation of hardware platforms paul comey mentioned this during the keynote today hardware is becoming important yeah there's a lot of people building hardware it's in development now for areas like uh like intelligent devices and ai how does this influence your development priorities you have all these different platforms that you need to support yeah so um we think about that a lot mostly because we have engagements with so many partners hardware right so obviously there's more traditional partners i'd say like the dell and the hpes that we work with we've historically worked with them also working with them in in newer areas uh with regard to appliances that are being developed um and then the work that we do with partners like nvidia or new architectures like arm and so our perspective is this will be uh use case driven more than anything else right so there are certain environments right where you have arm-based devices other environments where you've got specific workloads that can take advantage of being built on gpus that we'll see increasingly being used especially to address that problem and then provide a solution towards that so our belief has always been look we're going to give you a consistent platform a consistent abstraction across all these you know pieces of hardware um and so you mr miss customer make the best choice for yourself a couple other areas we have to hit on i want to talk about cloud services we've got to talk about security leave time to get there but why the push to cloud services what's driving that it's actually customers they're driving right so we have um customers consistently been asking us say you know love what you give us right want to make sure that's available to us when we consume in the cloud so we've made rel available for example on demand right you can consume this directly via public cloud consoles we are now making available via marketplaces uh talked about ansible available as a managed service on azure openshift of course available as a managed service in multiple clouds um all of this also is because you know we've got customers who've got these uh committed spends that they have you know with cloud providers they want to make sure that the environments that they're using are also counting towards that at the same time give them flexibility give them the choice right if in certain situations they want to run in the data center great we have that solution for them other cases they want to procure from the cloud and run it there we're happy to support them there as well let's talk about security because you have a lot of announcements like security everywhere yeah um and then some specific announcements as well i i always think about these days in the context of the solar wind supply chain hack would this have you know how would this have affected it but tell us about what's going on in security your philosophy there and the announcements that you guys made so our secure announcements actually span our entire portfolio yeah right and and that's not an accident right that's by design because you know we've really uh been thinking and emphasizing you know how we ensure that security profile is raised for users both from a malicious perspective and also helping accidental issues right so so both matters so one huge amounts of open source software you know out of the world you know and then estimates are you know one in ten right has some kind of security vulnerability um in place a massive amount of change in where software is being developed right so rate of change for example in kubernetes is dramatic right much more than even than linux right entire parts of kubernetes get rewritten over over a three-year period of time so as you introduce all that right being able to think for example about you know what's known as shift left security or devsec ops right how do we make sure we move security closer to where development is actually done how do we ensure we give you a pattern so you know we introduced a software supply chain pattern uh via openshift delivers complete stack of code that you know you can go off and run that follows best practices uh including for example for developers you know with git ops and support on the pipelines front a whole bunch of security capabilities in rel um a new image integrity measurement architecture which allows for a better ability to see in a post install environment what the integrity of the packages are signing technology they're incorporating open shift as well as an ansible so it's it's a long long list of cables and features and then also more and more defaults that we're putting in place that make it easier for example for someone not to hurt themselves accidentally on security front i noticed that uh this today's batch of announcements included support within openshift pipelines for sigstor which is an open source project that was birthed actually at red hat right uh we haven't heard a whole lot about it how important is zig store to to you know your future product direction yeah so look i i think of that you know as you know work that's you know being done out of our cto's office and obviously security is a big focus area for them um six store's great example of saying look how can we verify content that's in uh containers make sure it's you know digitally signed that's appropriate uh to be deployed across a bunch of environments but that thinking isn't maybe unique uh for us uh in the container side mostly because we have you know two decades or more of thinking about that on the rel side and so fundamentally containers are being built on linux right so a lot of the lessons that we've learned a lot of the expertise that we've built over the years in linux now we're starting to you know use that same expertise trying to apply it to containers and i'm my guess is increasingly we're going to see more of the need for that you know into the edge as well i i i picked up on that too let me ask a follow-up question on sigstor so if i'm a developer and i and i use that capability it it ensures the provenance of that code is it immutable the the signature uh and the reason i ask is because again i think of everything in the context of the solar winds where they were putting code into the the supply chain and then removing it to see what happened and see how people reacted and it's just a really scary environment yeah the hardest part you know in in these environments is actually the behavior change so what's an example of that um packages built verified you know by red hat when it went from red hat to the actual user have we been able to make sure we verify the integrity of all of those when they were put into use um and unless we have behavior that you know make sure that we do that then we find ourselves in trouble in the earliest days of open shift uh we used to get knocked a lot by by developers because i said hey this platform's really hard to use we investigate hey look why is that happening so by default we didn't allow for root access you know and so someone's using you know the openshift platform they're like oh my gosh i can't use it right i'm so used to having root access we're like no that's actually sealed by default because that's not a good security best practice now over a period of time when we you know randomly enough times explained that enough times now behavior changes like yeah that makes sense now right so even just kind of you know there's behaviors the more that we can do for example in in you know the shift left which is one of the reasons by the way why we bought uh sac rocks a year right right for declarative security contain native security so threat detection network segmentation uh watching intrusions you know malicious behavior is something that now we can you know essentially make native into uh development itself all right escape key talk futures a little bit so i went downstairs to the expert you know asked the experts and there was this awesome demo i don't know if you've seen it of um it's like a design thinking booth with what happened how you build an application i think they were using the who one of their apps um during covet and it's you know shows the the granularity of the the stack and the development pipeline and all the steps that have to take place and it strikes me of something we've talked about so you've got this application development stack if you will and the database is there to support that and then over here you've got this analytics stack and it's separate and we always talk about injecting more ai into apps more data into apps but there's separate stacks do you see a day where those two stacks can come together and if not how do we inject more data and ai into apps what are your thoughts on that so great that's another area we've talked about dave in the past right um so we definitely agree with that right and and what final shape it takes you know i think we've got some ideas around that what we started doing is starting to pick up specific areas where we can start saying let's go and see what kind of usage we get from customers around it so for example we have openshift data science which is basically a way for us to talk about ml ops right and you know how can we have a platform that allows for different models that you can use we can uh test and train data different frameworks that you can then deploy in an environment of your choice right and we run that uh for you up and assist you in in uh making sure that you're able to take the next steps you want with with your machine learning algorithms um there's work that we've uh introduced at summit around databases service so essentially our uh a cloud service that allows for deep as an easy way for customers to access either mongodb or or cockroach in a cloud native fashion and all of these things that we're sort of you know experimenting with is to be able to say look how do we sort of bring the world's closer together right off database of data of analytics with a core platform and a core stack because again right this will become part of you know one continuum that we're going to work with it's not i'd like your continuum that's that's i think really instructive it's not a technical barrier is what i'm hearing it's maybe organizational mindset i can i should be able to insert a column into my my my application you know development pipeline and insert the data i mean kafka tensorflow in there there's no technical reason i can't can't do that it's just we've created these sort of separate stovepipe organizations 100 right right so they're different teams right you've got the platform team or the ops team and you're a separate dev team there's a separate data team there's a separate storage team and each of them will work you know slightly differently independently right so the question then is i mean that's sort of how devops came along then you're like oh wait a minute yeah don't forget security and now we're at devsecops right so the more of that that we can kind of bring together i think the more convergence that we'll see when i think about the in-vehicle os i see the the that is a great use case for real-time ai inferencing streaming data i wanted to ask you that about that real quickly because at the very you know just before the conference began we got an announcement about gm but your partnership with gm it seems like this came together very quickly why is it so important for red hat this is a whole new category of application that you're going to be working on yeah so we've been working with gm not publicly for a while now um and it was very clear that look you know gm believes this is the future right you know electric vehicles into autonomous driving and we're very keen to say we believe that a lot of attributes that we've got in rel that we can bring to bear in a different form factor to assist with the different needs that exist in this industry so one it's interesting for us because we believe that's a use case that you know we can add value to um but it's also the future of automotive right so the opportunity to be able to say look we can get open source technology we can collaborate out with the community to fundamentally help transform that industry uh towards where it wants to go you know that that's just the passion that we have that you know is what wakes us up every morning you're opening into that yeah thank you for coming on the cube really appreciate your time and your insights and uh have a great rest of rest of the event thank you for having me metacloud it's a thing it's a thing right it's it's it's kind of there we're gonna we're gonna see it emerge over the next decade all right you're watching the cube's coverage of red hat summit 2022 from boston keep it right there be right back you

[upbeat electronic music] >> Hi everyone, welcome back to theCUBE's coverage of AnsibleFest 2021. I'm John Furrier, your host of theCUBE. We're here with Eric Pennington, Director of Solutions Engineering, and Mike Todaro, Senior Epic Cache Consultant at Sapphire Health. Gentlemen, thank you for coming on theCUBE and chatting about the wave of Cloud, cloud-native, Sapphire Health and Ansible. Thanks for coming on. >> Thanks for having us. >> Thank you. >> So, let's get started. Can you guys just briefly describe Sapphire Health and what you guys are doing there. The consulting services, the trends that you're seeing. Just take a step, a minute to describe the environment at Sapphire Health and what you guys are doing. >> For sure, yeah. So, Sapphire Health was a consultancy that was founded by the CEO back in 2016, Austin Park, who also serves as a CTO for some healthcare organizations, because he was having difficulty finding an organization that really specialized in Epic infrastructure. So you might be familiar with some of the large players in Epic consultancies, but they are typically focused more on the application side, so configuring like the ambulatory clinical system or something like that. And there really wasn't a solution that he could find in the market for an organization that was focused on Epic infrastructure and some of the more technical components of managing an Epic technical ecosystem. So, Austin founded a team. Mike was one of the early folks to join. I joined a little bit later. But he put a team together to, again, really focus on the technical components of an Epic implementation. And since then, we've been providing managed services for Epic infrastructure for a number of organizations. We've been focusing on platform migrations from, for example, AIX to REL for Epic organizations, and we've been focusing on some growth areas as well in the Cloud. Epic systems is now able to be hosted on the public Cloud, that's a relatively recent occurrence. So, we're working with some organizations in that space as well. Mike, anything you'd add there? >> No, I think that pretty much covers it. We've spent a large fraction of our effort making sure that we're engineering solutions for these clients that move them in the directions towards Cloud readiness, towards containerization, automation, and those sorts of things. I think Eric's description's spot on. >> So, you guys must be busy. I mean, I can only imagine the action happening right now as people realized, with the pandemic specifically, two areas that we've reported aggressive growth on was public sector and healthcare. Both were under massive strains of pressure to get faster. (chuckles) Can you guys just weigh in real quickly on what you guys are seeing and how that's impacted your consulting services, but also the customer. What's going on in their minds? >> Absolutely, we had some customers very early on in the beginning of the pandemic where we were given the cadence of updates coming from Epic, the needs for growth for those customers where both in ICU surge capability as well as just general admittance. There was a flurry of hardware purchasing, provisioning, set up. An increased cadence around patching for various pieces of the Epic environment including Epic code directly. All of those things. The tempo of all of that increased once the pandemic began, and we spent a significant fraction of time trying to find better ways, faster ways to engineer what we were already doing for clients, simply so that we could continue to keep up with the surge in demand without requiring an additional surge in investment in people, where it wasn't necessary. Obviously, some growth was necessary, but we wanted to help our clients get the most out of what they already had so that they could spend that money where it was needed to help patients. >> Yeah, awesome, great stuff. So, we're here at AnsibleFest getting into the action. It's all about automation. So I have to ask you guys, what led you to start exploring automation solutions at Sapphire Health? >> Yeah, so there's quite a few reasons. I would say the most critical is that we've been providing managed services to organizations around infrastructure management for some time. And as you can imagine, infrastructure management has some repetitive tasks, and I'm quoting my colleague, Mike, here, but a good administrator is a lazy administrator. And what we mean when we say that is, if there's a repetitive task that's being performed over and over again, if there's an opportunity to automate it, that's going to save us time. But more importantly, that's going to... Paul, these lights here. Let me move around a little bit, should come back, there we go. But it's going to provide an opportunity for us to focus on more value-add services for the client. It's going to reduce costs for the client in terms of the services that we're providing. And I think most importantly, it's removing the possibility for human error or the possibility for error overall. So it's a natural evolution of us observing the time that we're spending with our client partners, and again, it really provides a lot of value to Sapphire as an organization and our customer partners as well. >> Mike, you want to weigh in on this automation trend. How do you see it evolving? I mean, obviously sounds good when you want to automate things that you do repetitive tasks, but is there more going on that you see in automation that goes beyond just, okay, if you do it three times-automated kind of vibe. >> Sure. Automating repetitive tasks is the kiddie end of the pool. That's how we get... That's how we sell the idea to people who just don't get the concept yet. But there are workflows that really aren't feasible outside of automation. We tend to think of automation, in some cases in this sort of limited way, but automation is really... What we really are targeting with automation is more about workflow. It's less about individual tasks, and it's more about an idea of workflow or a business requirement from its origin all the way through its implementation. So, I've got just the simplest case that jumps immediately to mind, is I have a new hire, I've got to provision them an account. I need to provision it across multiple systems. I've got to do it in our single sign on. They need home directories. They might need access. They need building accesses we need to generate. You got to generate badges for these people. And these are all workflows that are normally disparate. You know, you have to take your sheet to this guy, take your sheet to this guy, here's my new hire form. Really, what you really want is, we got a new hire, everything's checked out, put it in this basket here and let the automation move it through all of these systems all the way across. And that's the sort of thing, like I said, that's a very limited, very simple idea, but that's the kind of thing we really want. We want to get in the door with automation with simple things and then we want to teach... We want clients and ourselves to be challenged, to be creative, to find new ways to apply it that aren't immediately obvious. >> Yeah, I was smiling because I love the example of the kiddie end of the pool because automation is going mainstream, and it used to be kind of, you know, for the geeks who were doing the hardcore stuff who got the whole big picture. Now you're seeing with AI automation moving in and with Cloud, a lot more automation happening. So, I can almost see in my mind mental image of people wearing bubbles in the pool, kind of like going in the deep end, get back over here. Stay in your lane. Yeah, but this is the trend, and I want to get into this because you guys are involved in this Epic migration that's been talked about. So for the folks that aren't in, say the health care space, put a little context around Epic and then I want to get into this whole migration discussion. I think that kind of points to some real value propositions. So, what is Epic for the folks outside healthcare? >> Sure, so Epic is one of the leading EHRs or electronic health records software in the world. It is by far the most deployed in the United States. What's involved in building an Epic, or performing an Epic migration. Epic is hundreds of systems. When you think about Epic as an umbrella concept, it is servers and end-user workstations and all of these things. When we talk about platform migration, what we're usually talking about is the transactional database. They call it the ODB or whichever term I think you feel applies best. When we perform all those migrations, we're usually talking about... When we perform one of those migrations, we're usually talking about an AIX to Red Hat migration, although you can just do hardware to hardware. Involved in that is a number of things. You're building new VMs. You're setting up patch cycles, setting up the patching server. Installing the various administration scripts that Epic provides. Installing the software that runs the DB, which at the moment is either InterSystems Cache or Iris. There's the provisioning of the local security users. There's the configuration of the OS. If you're moving from AIX to Red Hat, you're talking generally about a bit endians conversions, so, big endian to little endian, there's a tool for that. There's a lot of these little stats. And the thing is, is that, they're all very, very well defined and very similar, and so, they look identical in many of these cases from one implementation of Epic to the next. And that's not true for the entire Epic stack necessarily, but at the ODB level, this stuff is all very similar, and this is a very right place to automate. This screams automate, and we do this because, I mean, who wants to make mistakes. If you write and build your script and debug it, the script runs, it doesn't make mistakes. I make mistakes, the script doesn't. So, we do that, and we end up spending less time on these repetitive, unnecessary tasks. We guarantee the correctness of them, or we do a better job of guaranteeing the correctness of them, and all of that ends up saving money in the long run. >> That's awesome, and thanks for the context. I was going to get there on the automation piece. It really sets the table for the automation. Real quick clarification. How much or what kind of software work is involved in a migration? >> Oh, so there's the installation of... You have from the installation of the OS and the configuration of the OS, the building in the patch server, the implementation, testing, and patch cycling. There's those data conversions I talked about. There's environment refreshes where we copy an existing environment on a regular basis to another environment for things like testing, for troubleshooting purposes or for other reasons. There's more than one database for Epic. There's one big production database. You have training databases, and you have playground databases for people to work in so they can learn to use the system better, and then there are, I mean, there's a galaxy. >> Oh man, so it's a huge system. Okay, so I got to ask the security question. >> Sure. >> Is security element as important when selecting automation or how has that factored in? I mean, right now that's super important, obviously, records are key, but honestly, where does that fit into the automation piece of security? >> Yeah, I think that's a very important question, and as you alluded to, security is incredibly important. It's very important in healthcare in particular. And in fact, with healthcare, there's a lot of regulatory requirements. There's a lot of requirements that individual healthcare institutions have that we as a partner to that institution need to follow. So, as we were evaluating automation vendors and automation solutions, a highly secure system was not a nice to have or like a value add, it was something that was absolutely critical and paramount to being able to successfully automate any of the things that we're doing. So I'll turn it over to Mike to talk about some of the specifics, but as we evaluated Ansible, we saw that it really supported robust security. So, Mike, can you comment a little bit more on that? >> Sure. There's a number of ways that we use Ansible to help improve the security posture for clients. One of the ways is Ansible playbooks are written to be runnable against the server and nothing will change unless something is set incorrectly. And this lets us assure that the configuration is where we expect it to be so we don't get drift on these servers. Now, remember I said an Epic environment is a lot of servers. If one or two of these... >> John: Mike, if you don't mind, I need to interrupt. What is, when you say drift, what are you referring to? >> So when I say drift, what I mean is, if there's a bunch of different servers and I as an administrator have to work on one or two of these servers just for little things during the day, I might make a change on one of these servers advertently or inadvertently, and then that server's configuration is now slightly out of phase with the other servers, which could be benign, but it could also be a security hole. Having Ansible able to run nightly and continue to adjust these servers back to the expected baseline, and in the case of things like tower, be able to report that these things were out of position. Let us know, hey, it lets us reduce the attack surface, first of all. It lets us multiply it, like a force multiply our attention across this farm of servers, and it gives us that sort of clarity that we know we're doing what we have to do to make sure these servers continue to be safe. >> That's an awesome service. That right there is, I mean, just going in manually trying to figure all this stuff out, it's just a nightmare. I mean, what a great relief that is. I mean, just the alternative is what, you know, more pain and suffering human wise, that's the labor, and then risk on attack because people go to bed. >> I'm a patient. The thing is, on a personal note, I'm a patient too, all of us are. We all have doctors. We have to go to the hospital for things occasionally. And if we fail when we perform these security audits, if we fail when we perform these security checks, patient data can get lost. It can get sent to people who shouldn't have it. And I'm a patient, I have no desire for my medical information to be available anywhere but in the hands of my doctor or myself. And that's the thought I try to stay with when I'm working on these systems. I'm a patient. It's not that I'm doing this because... I mean, the knock-on effects of reducing liability for the customers cannot be ignored or overstated, and they're critical, but, ultimately, my eyesight is on the patient. >> Yeah and having that stability is huge. Okay, this brings up the whole automation thing as it becomes more mainstream for you guys, specifically, is critical. The system's there, you have to watch farms, all the action happening, it's a huge system. Complex automation is key. How are you guys continuing to push the automation envelope into the Sapphire Health's consulting practice? >> Well, as you mentioned, John, yeah, we're really taking a look at the entire technical infrastructure when we're working with our clients. And we are offering fully outsourced managed services for organizations, not just around the Epic infrastructure but things like networking devices, security and other third party systems. So with that, we're seeing a lot of these things that are going on, and we're always evaluating opportunities for automation. There's actually two areas in particular that we're seeing gain a lot of momentum with our customers, and we're seeing a lot of opportunity for automation. The first is business continuity and disaster recovery, specifically within Epic. So, Epic has very stringent requirements for resiliency, as you can imagine. When the system goes down, a hospital can't really do what it needs to do from a billing standpoint, a clinical standpoint, so very robust disaster recovery and resiliency standards and solutions are very important. However, there's not a lot of automation that's available either from Epic or, as far as I know, other consultancies, so what we did is we built a script that provides failover automation. So some of the tasks that would be very manual in terms of failing over to your DR solution, we've automated that, and that again, removes a lot of the opportunity for human error, really speeds up the failover process. And so with the customers that we work with, that's something that we provide. Another big area that we're seeing is environment refreshes. So within Epic, there are different environments that are, basically, all their data is copied over on a recurring basis from the production environment, and the refreshes can have a lot of manual steps involved, so we found an opportunity and have implemented some automation around environment refreshes for some of our managed services clients. And as we continue to go throughout, you know, building our Cloud practice in some other areas, I'm very confident that we're going to see, you know, infrastructure is code more opportunities for automation around areas like that. >> I mean, you guys got to love the DevOps vibe going on now. Mike, I mean, you guys have seen the movie before in the old legacy going back to the mainframes, so you probably still run into a lot of older systems that still do a purpose. I mean, I have a lot of friends and clients that are working in the big banks, and they still have all the old school that does their job well, but containerization and Cloud kind of give life to these systems because now we're living in this system architecture called distributed computing again with the Cloud. It's the same game, different, different stuff though. >> Absolutely. Years ago, almost every Epic client was running on AIX, and maybe not mainframe but more mini computer. The migration path for almost all of the clients has been to move from those AIX mini computers down to VMs running Red Hat, or running Linux, and the natural evolution of that path is to move at least disaster recovery data centers into the Cloud, and then for some clients, the economics say the whole data center to the Cloud. So, absolutely that path is, it's well forged, it's there. I suspect that we'll see a lot more of clients, even larger hospitals, beginning to move down that road in the near future. >> And for the folks watching who may not have the scar tissue that we have, AIX was IBM's old Unix, a kind of mid-range mini computer. It was kind of client server, it was client server going now again being modernized. So obviously Red Hat is now part of IBM, but it speaks not just to IBM, this is about Ansible, right. So this is like, there is action happening here, so this is a case study of pretty much all migrations. It's not just the fact that it's AIX to Red Hat, it's system to the new thing that has benefits. >> Absolutely. >> What's your take, Mike, on that that kind of paradigm, because a lot of people going through similar situations just change AIX to something else. You have a lot of this migration re-platforming going on with the opportunity to kind of tweak it and add stuff to it. What's your advice and what's your reaction to this big trend? >> My advice for this trend, honestly, my advice is when you're planning these migrations, you know they're coming. Even if you're not in the cycle yet, you know it's coming. My advice is start brainstorming your implementation of the automation now. Get your automation into the system as you platform into your new platform, because it is far easier to build that entire platform with automation as a critical component than it is to bolt it on later, and you will get much more out of your investment and time and effort if you've integrated it from the very beginning. I would say anyone that was looking to perform a platform migration now and hadn't already begun serious consideration of running automation or had no plans for an automation, was setting themselves up for a very long and very difficult road to hell, and I would advise against it at this point. >> Great, great insight, Mike and Eric. Thanks for coming on, appreciate your insight here. You guys want to give a quick plug for the company? What you guys are looking to do, hiring, any update you want to share because great, great content you guys just shared here. Thanks for doing that. Take a minute to put a plug for the company. >> Yeah, I think a quick plug here. Yeah, if you're a talented cache admin, there's not too many Mikes out there, so we're definitely looking for more Mikes. But more broadly, we're really looking to expand into the Cloud space. We're rapidly expanding our managed services opportunities, and what we're seeing is a lot of organizations have like one ODB admin or one client systems ECSA admin. And what they run into is that person will leave, that person will retire, that person needs to get married and go on their honeymoon. It's kind of a problem, so we're working with a lot of organizations to not just fully outsource their environment but to provide a hybrid-managed service to provide overflow, to provide capabilities, to scale up with upgrades and projects like that. So, talk to us, we're pretty darn good at it, as you heard from Mike. We've got a couple of Mikes, again, we could use more, so if you are a Mike, please reach out. >> I think we virtualized him, we just virtualized Mike, you know, virtualization is a huge trend. >> If data writes Mike, we need to do that, yeah. >> Are you a body, are you the real Mike? >> (laughing) As far as I know, my wife would appreciate it if you guys would clone me a few times. >> You know, I've heard horror stories, Eric, around root passwords, like, who has the root password, oh, she left two years ago, kind of situations, this happens. I mean, this is not... it sounds like crazy but people leave. >> Yeah, I mean, nobody works anywhere forever, right? >> Don't be that company where you lose the root password, and never mind the ransomware action. Oh my God, must be brutal. Anyway, we can go another segment on that. Eric, thank you for coming on. Mike, thank you for your insight, really appreciate it, thanks for coming on. Appreciate it. >> Absolutely. >> Absolutely, it was our pleasure. >> Stay right here for continued coverage of AnsibleFest 2021. This is theCUBE, I'm John Furrier. Thanks for watching. (slow tempo electronic music)

>> Announcer: From around the globe, it's theCUBE with coverage of KubeCon and CloudNativeCon Europe 2021-Virtual, brought to you by Red Hat, the Cloud Native Computing Foundation and Ecosystem Partners. >> Hey, welcome back everyone to theCUBE's coverage of KubeCon and CloudNativeCon 2021-Virtual. I'm John Furrier, your host here on theCUBE. We've got Steve Gordon, Director of Product Management, Cloud Platforms at Red Hat. Steve, welcome to theCUBE, good to see you, thanks for coming on. >> Hey John, thanks for having me on, it's great to be back. >> So soon we'll be in real life, I think North America show, this is for the Europe Virtual, I think the North American one might be in person. It's not yet official. We'll hear, but we'll find out, but looking good so far. But thanks for all your collaboration. You guys have been a big part of the CNCF we've been covering on theCUBE, as you know, since the beginning. But, I wanted to get into the Edge conversation that's been going on. And first I want to just get this out there. You guys are sponsoring Edge Day here at KubeCon. I want you to bring that together for us, because this is a big part of what Red Hat's talking about and frankly customers. The Edge is the most explosive growth area. It's got the most complexity, it's crazy. It's got data, it's got everything at the Edge. Everything's happening. How important is Kubernetes to Edge Computing? >> Yeah, it's certainly interesting to be here talking about it now, and having kind of a dedicated Kubernetes Edge Day. I was thinking back earlier, I think it was one of the last in-person KubeCon events I think, if not the last, the San Diego event where there was already kind of a cresting of interest in Edge and kind of topics on the agenda around Edge. And it's just great to see that momentum has continued up to where we are today. And really more and more people not only talking about using Kubernetes for Edge, but actually getting in there and doing it. And I think, when we look at why people are doing that, they're really leaning into some of the things that they saw as strengths of Kubernetes in general, that they're now able to apply to edge computing use cases in terms of what they can actually do in terms of having a common interface to this very powerful platform that you can take to a growing multitude of footprints, be they your public cloud providers, where a lot of people may have started their Kubernetes journey or their own data center, to these edge locations where they're increasingly trying to do processing closer to where they're collecting data, basically. >> You know, when you think about Edge and all the evolution with Cloud Native, what's interesting is Kubernetes is enabling a lot of value. I'd like to get your thoughts. What are you hearing from customers around use cases? I mean, you are doing product management, you've got to document all the features, the wishlist. You have the keys to the kingdom on what's going on over at Red Hat. You know, we're seeing just the amazing connectivity between businesses with hybrid cloud. It's a game changer. Haven't seen this kind of change at this level since the late '80s, early '90s in terms of inflection point impact. This is huge. What are you hearing? >> I think it's really interesting that you use the word connectivity there because one of the first edge computing use cases that I've really been closely involved with and working a lot on, which then grows into the others, is around telecommunications and 5G networking. And the reason we're working with service providers on that adoption of Kubernetes as they build 5G basically as a cloud native platform from the ground up, is they're really leveraging what they've seen with Kubernetes elsewhere and taking that to deliver this connectivity, which is going to be crucial for other use cases. If you think about people whether they're trying to do automotive edge cases, where they're increasingly putting more sensors on the car to make smarter decisions, but also things around the infotainment system using more and more data there as well. If you think about factory edge, all of these use cases build on connectivity as one of the core fundamental things they need. So that's why we've been really zoomed in there with the service providers and our partners, trying to deliver a 5G networking capabilities as fast as we can and the throughput and latency benefits that come with that. >> If you don't mind me asking, I got to just go one step deeper if you don't mind. You mentioned some of these use cases, the connectivity. You know, IoT was the big buzz word, okay IoT. It's an Edge, it's Operational Technology, or it's a dumb endpoint or a node on the network has connectivity. It's got power. It's a purpose built device. It's operating, it's getting surveillance data, whatever the hell it's doing, right. It's got Edge. Now you're bringing in more intelligent, which is an IT kind of thing, state, databases, caching. Is the database too slow? Is it too fast? So again, it brings up more complexity. Can you just talk about how you view that? Because this is what I'm hearing, what do you think? >> Yeah, I agree. I think there's a real spectrum, when we talk about edge computing, both in terms of the footprints and the locations, and the various constraints that each of those imply. And sometimes those strengths can be, as you're talking about as a specially designed board which has a very specific chip on it, has very specific memory and storage constraints or it can be a literal physical constraint in terms of I only have this much space in this location to actually put something, or that space is subject to excess heat or other considerations environmentally. And I think when we look at what we're trying to provide, not just with Kubernetes but also with Linux, is a variety of solutions that can help people no matter where they are along that spectrum of the smallest devices where maybe Red Hat Enterprise Linux, or REL for Edge is suitable to those use cases where maybe there's a little more flexibility in terms of, what are the workloads I might want to run on that in the future? Or how do I want to grow that environment potentially in the future as well? If I want to add nodes, then all of a sudden, the capability that nannies brings can be a more flexible building base for them to start with. >> So with all of these use cases and the changing dynamics and the power dynamics between Operational Technology in IT, which we're kind of riffing on, what should developers take away from that when they're considering their development, whether they just want an app, be app developers, programming the infrastructure or they're tinkering with the underlying, some database work, or if they're under the hood kind of full dev ops? What should developers take into consideration for all these new use cases? >> Yeah, I think one of the key things is that we're trying to minimize the impact to the developer as much as we can. Now of course, with an edge computing use case where you may be designing your application specifically for that board or device, then that's a more challenging proposition. But there's also the case increasingly where that intelligence already exists in the application somewhere, whether it's in the data center or in the cloud, and they're just trying to move it closer to that endpoint, where the actual data is collected. And that's where I think there's a really powerful story in terms of being able to use Kubernetes and OpenShift as that interface that the application developer interacts with but can use that same interface, whether they're running in the cloud maybe for development purposes, but also when they take it to production and it's running somewhere else. >> I got to ask you the AI impact because every conversation I have or everyone I interview that's an expert as a practitioner is usually something along the lines of chief architect of cloud and AI. You're seeing a lot of cloud, SRE, cloud-scale architects meeting and also running the AI piece, especially in industries. So AI as a certain component seems to be resonating from a functional persona standpoint. People who are doing these transformations tend to have cloud and AI responsibility. Is that a fluke or is that just the pattern that's real? >> No, I think that's very real. And I think when you look at AI and machine learning and how it works, it's very data centric in terms of what is the data I'm collecting, sending back to the mothership, maybe in terms of actually training my model. But when I actually go to processing something, I want to make that as close as I can to the actual data collection, so that I can minimize what I'm trying to send back. Particularly, people may not be as cognizant of it, but even today, many times we're talking about sites where that connectivity is actually fairly limited in some of these edge use cases still today. So what you're actually putting over the pipe is something you're still trying to minimize, while trying to advance your business and improve your agility, by making these decisions closer to the edge. >> What's the advantage for Red Hat? Talk about the benefits. What are you guys bringing to the table? Obviously, hybrid cloud is the new shift. Everyone's agreed to that. I mean, pretty much the consensus is public clouds, great, been there, done that. It's out there pumping out as a resource, but now enterprise is goading us to keep stuff on premises, especially when you talk about factories or whatever, on premises, things that they might need, stuff on premise. So it's clear hybrid is happening. Everyone's in agreement. What does Red Hat bring to the table? What's in it for the customer? >> Yeah, I think I would say hybrid is really an evolving at the moment in terms of, I think, Hybrid has kind of gone through this transition where, first of all, it was maybe moving from my data center to public cloud and I'm managing most of those through that transition, and maybe I'm (indistinct) public clouds. And now we're seeing this transition where it's almost that some of that processing is moving back out again closer to the use case of the data. And that's where we really see as an extension of our existing hybrid cloud story, which is simply to say that we're trying to provide a consistent experience and interface for any footprint, any location, basically. And that's where OpenShift is a really powerful platform for doing this. But also, it's got Kubernetes at the heart of it. but it's also worth considering when we look at Kubernetes, is there's this entire Cloud Native ecosystem around it. And that's an increasingly crucial part of why people are making these decisions as well. It's not just Kubernetes itself, but all of those other projects both directly in the CNCF ecosystem itself, but also in that broader CNCF landscape of projects which people can leverage, and even if they don't leverage them today, know they have options out there for when they need to change in the future if they have a new need for their application. >> Yeah, Steve, I totally agree with you. And I want to just get your thoughts on this because I was kind of riffing with Brian Gracely who works at Red Hat on your team. And he was saying that, you know, we were talking about KubeCon + CloudNativeCon as the name of the conference. He's a little bit more CloudNativeCon this year than KubeCon, inferring, implying, and saying that, okay so what about Kubernetes, Kubernetes, Kubernetes? Now it's like, whoa, CloudNative is starting to come to the table, which shows the enablement of Kubernetes. That was our point. The point was, okay, if Kubernetes does its job as creating a lever, some leverage to create value and that's being rendered in CloudNative, and that enterprise is, not the hardcore hyperscalers and/or the early adopters, I call it classic enterprise, are coming in. They're contributing to open source as participants, and they're harvesting the value in creating CloudNative. What's your reaction to that? And can you share your perspective on there's more CloudNative going on than ever before? >> Yeah, I certainly think, you know, we've always thought from the beginning of OpenShift that it was about more than just Linux and Kubernetes and even the container technologies that came before them from the point of view of, to really build a fully operational and useful platform, you need more than just those pieces. That's something that's been core to what we've been trying to build from the beginning. But it's also what you see in the community is people making those decisions as well, as you know, what are these pieces I need, whether it's fairly fundamental infrastructure concerns like logging and monitoring, or whether it's things like trying to enable different applications on top using projects like KubeVert for virtualization, Istio for service mesh and so on. You know, those are all considerations that people have been making gradually. I think what you're seeing now is there's a growing concern in some of these areas within that broad CNCF landscape in terms of, okay, what is the right option for each of these things that I need to build the platform? And certainly, we see our role is to guide customers to those solutions, but it's also great to see that consensus emerging in the communities that we care about, like the CNCF. >> Great stuff. Steve, I got to ask you a final question here. As you guys innovate in the open, I know your roadmaps are all out there in the open. And I got to ask you, product managing is about making decisions about what you what you work on. I know there's a lot of debates. Red Hat has a culture of innovation and engineering, so there's heated arguments, but you guys align at the end of the day. That's kind of the culture. What's top of mind, if someone asks you, "Hey, Steve, bottom line, I'm a Red Hat customer. I'm going full throttle as a hybrid. We're investing. You guys have the cloud platforms, what's in it for me? What's the bottom line?" What do you say? >> Yeah, I think the big thing for us is, you know, I talked about that this is extending the hybrid cloud to the edge. And we're certainly very conscious that we've done a great job at addressing a number of footprints that are core to the way people have done computing today. And now as we move to the edge, that there's a real challenge to go and address more of those footprints. And that's, whether it's delivering OpenShift on a single node of itself, but also working with cloud providers on their edge solutions, as they move further out from the cloud as well. So I think that's really core to the mission is continuing to enable those footprints so that we can be true to that mission of delivering a platform that is consistent across any footprint at any location. And certainly that's core to me. I think the other big trend that we're tracking and really continuing to work on, you know, you talked about AI machine learning, the other other space we really see kind of continuing to develop and certainly relevant in the work with the telecommunications companies I do but also increasingly in the accelerator space where there's really a lot of new and very interesting things happening with hardware and silicon, whether it be kind of FPGAs, EA6, and even the data processing units, lots of things happening in that space that I think are very interesting and going to be key to the next three to five years. >> Yeah, and software needs to run on hardware. Love your tagline there. It sounds like a nice marketing slogan. Any workload, any footprint, any location. (laughs) Hey, DevSecOps, you got to scale it up. So good job. Thank you very much for coming on. Steve Gordon, Director of Product Management, Clout Platforms, Red Hat, Steve, thanks for coming on. >> Thanks, John, really appreciate it. >> Okay, this is theCUBE coverage of KubeCon and CloudNativeCon 2021 Europe Virtual. I'm John Furrier, your host from theCUBE. Thanks for watching. (serene music)

(upbeat music) >> And, welcome back to theCube's coverage of Red Hat Summit, 2021. I'm John Furrier, host of theCube. We've got a great segment here on how Red Hat is working with telcos and the disruption in the telco cloud. We've got a great guest Cube alumni, Darrell Jordan Smith, senior vice president of industries and global accounts at Red Hat. Darrell, great to see you. Thanks for coming back on theCube. >> Oh, it's been, it's great to be here and I'm really excited about having the opportunity to talk to you today. >> Yeah, we're not in person, in real life's coming back soon. Although I hear Mobile World Congress, might be in person this year, looking like it's good. A lot of people are going to be virtual and activating I know. A lot to talk about. This is probably one of the most important topics in the industry because when you talk about telco industry, you're really talking about the edge. You're talking about 5G, talking about industrial benefits for business, because it's not just edge for connectivity access. We're talking about innovative things from self-driving cars to business benefits. It's not just consumer, it's really bringing that together. You guys are really leading with the cloud-native platform from REL, OpenShift managed services. Everything about the cloud-native underpinnings, you guys have been successful as a company. But now in your area, telco is being disrupted. You're leading the way >> Absolutely. Give us your take on this, this is super exciting. >> Well, it's actually one of the most exciting times. I've been in the industry for 30 years. I'm probably aging myself now, but in the telecommunications industry, this for me, is the most exciting. It's where, you know, technology is actually going to visibly change, the way, that everyone interacts with the network. And with the applications that are being developed out there on, on our platform. and, you know, as you mentioned, IoT, and a number of the other AI and ML innovations, that are occurring in the marketplace. We're going to see a new wave of applications and innovation. >> What's the key delivery workload you're seeing, with 5G environment. Obviously it's not just, you know 5G in the sense of thinking about mobile phones or mobile computers as they are now. It's not just that consumer, "Hey surf the web and check your email and get an app and download and, and communicate". It's bigger than that now. Can you tell us, where you see the workloads coming in on the 5G environment? >> You, you hit the nail on the head. The, the, the, the killer application, isn't the user or the consumer and the way that we traditionally have known it. Because you might be able to download a video and that might take 20 seconds less, but you're not going to pay an awful lot more money for that. The real opportunity around 5G, is the industrial applications. Things like connected car. You know automotive driving, factory floor automation. How you actually interface digitally with your bank. How we're doing all sorts of things, more intelligently at the edge of the network, using artificial intelligence and machine learning. So all of those things are going to deliver a new experience, for everyone that interacts with the network and the telcos are at the heart of it. >> You know, I want to get into the real kind of underpinnings, of what's going on with the innovations happening. You just kind of laid out kind of the implications of the use cases and the target application workloads, but there's kind of two big things going on with the edge and 5G. One is under the hood networking, you know, what's going on with the moving the packets around the workload, throughput, bandwidth, et cetera, and all that, that goes on under the hood. And then there's the domain expertise in the data, where AI and machine learning have to kind of weave in. So let's take the first part, first. OpenShift is out there. Red Hat's got a lot of products, but you have to nail the networking requirements and cloud native with containerization, because at large scales, not just packets, it's all kinds of things going on, security, managing compute at the edge. There's a lot of things under the hood, if you will, from a networking perspective. >> Could you share what Red Hat's doing in that area? >> Yep, so, so that's a very good question, in that we've been building on our experience with OpenStack and the last time I was on theCube, I talked about, you know, people virtualizing network applications and network services. We're taking a lot of that knowledge, that we've learned from OpenStack and we're bringing that into the container based world. So we're looking at how we accelerate packets. We're looking at how we build cloud-native applications, on bare metal, in order to drive that level of performance. We're looking at actually how we do, the certification around these applications and services, because they may be sitting in different applets across the cloud. And in some instances running on multiple clouds, at the same time. So we're building on our experience from OpenStack. We're bringing all of that into OpenShift, our container based environment. With all of the tooling necessary to make that effective. >> It's interesting with all the automation going on and certainly with the edge developing nicely, the way you're describing it, it's certainly disrupting the telco cloud. You have an operator mindset a cloud-native operator thinking, kind of, I mean it's distributed computing. We know that, but it's hybrid. So it's essentially cloud operations. So there's an operator mindset here, that's just different. Could you just share quickly, before we move on to the next segment, what's different about this operating model, for the, these new kinds of operators. As, as you guys have been saying, the CIO is the new cloud operator. That's the skill set they have to be thinking. And certainly IT, to anyone else provisioning and managing infrastructure has to think like an operator, what's your view? >> Exactly. They certainly do need to think like an operator. They need to look at how they automate a lot of these functions, because they're actually deployed in many different places, all at the same time. They have to live independently of each other, that's what cloud-native actually really is. So the whole, the whole notion of five nines and vertically orientated stacks of five nines availability that's kind of going out the window. We're looking at application availability, across a hybrid cloud environment and making sure the application can live and sustain itself. So operators as part of OpenShift is one element of that, operations in terms of management and orchestration and all the tooling that we actually also provide as Red Hat, but also in conjunction with a big partner ecosystem, such as companies like Netcracker, for example, or IBM as another example. Or Ericsson bringing their automation tool sets and their orchestration tool sets, to that whole equation, to address exactly that problem. >> Yeah. You bring up the ecosystem and this is really an interesting point. I want to, just hit on that real quick, because it reminds me of the days, when we had this massive innovation wave in the nineties. During that era, the client server movement, really was about multi-vendor, right? And that, you start to see that now and where this ties into here I think, is and I want to get your reaction to this is that, you know, moving to the cloud was all about to 2015, moved to the cloud, move to the cloud, cloud-native. Now it's all about not only being agile and better performance, but you're going to have smaller footprints, with more security requirements, more net, enterprise requirements. This is now, it's more complicated. So you have to kind of make the complication go away. And now you have more people in the ecosystem, filling in these white spaces. So, you have to be performance and purpose built, if you will. I hate to use that word, but, or, or at least performing and agile, smaller footprint, greater security, enabling other people to participate. That's a requirement. Can you share your reactions to that? >> Well, that's core of what we do at Red Hat. I mean, we take open source community software, into a hardened distribution, fit for the telecommunications marketplace. So we're very adapt to working with communities and third parties. That ecosystem is really important to us. We're investing hundreds of engineers, literally hundreds of engineers, working with our ecosystem partners, to make sure that their application is services certified running on our platform. But also importantly, is certified to be running in conjunction with other cloud-native applications that sit under the same cloud. So that, that is not trivial to achieve, in any stretch of the imagination. And a lot of IT technology skills come to bear. And as you mentioned earlier a lot of networking skills, things that we've learned, and we build with a lot of these traditional vendors as we bring that to the marketplace. >> You know, I've been saying on theCube, I think five years ago, I started talking about this and it was kind of a loose formulation. I want to get your reaction, because you brought up ecosystem. Now saying, you know, you're going to see the big clouds develop obviously Amazon and Microsoft came in after and now Google and others. And then I said, there's going to be a huge wave of, of what I call secondary clouds. And you see companies, like Snowflake building on top of Amazon. And so you start to see the power law, of new cloud service providers emerging, that can either sit and work with, across multiple clouds, either one cloud or others, that's now multi-cloud and hybrid. But this rise of the new, more CSPs, more cloud service providers. This is a huge part of your area right now because some call that telco, telco cloud, edge hits that. What is Red Hat doing in this cloud service provider market specifically? How do you help them? If I'm a cloud service provider, what do I get in working with Red Hat? How do I be successful? Because it's very easy to be a cloud service provider now more than ever. What do I do? How do you help? How do you help me? >> Well, we, we, we offer a, a platform called OpenShift which is our containerized based platform, but it's not just a container. It involves huge amounts of tooling associated with operating it, developing in and around it. So the, the concept that we have, is that you can bring those applications, develop them once, on one, one single platform, and run it on premise. You can run it natively as a service in Microsoft's environment. You can actually run it natively as a service in Amazon's environment. You can run it natively in IBM's environment. You can build an application once and run it in all of them, depending on what you want to achieve and who actually provides you the best zoning, the best terms and conditions, the best, the best tooling in terms of other services, such as an AI, associated with that. So it's all about developing it once, certifying it once, but deploying it in many, many different locations, leveraging the largest possible developer ecosystem, to drive innovation through applications on that common platform. >> So the assumption there, is that's going to drive down costs. Can you tell me about why the benefits, the economics are there? Talk about the economics. >> Well, Yeah, so, so, A, it does drive down costs and that's an important aspect but more importantly, it drives up agility, so time to market advantage is actually attainable for you. So many of the telcos when they deploy a network service, traditionally it would take them literally, maybe a year to roll it all out. They have to do it in days, they have to do updates in real time, in day two operations, in literally minutes. So we were building the fabric necessary, in order to enable those applications and services to occur. And as you move into the edge of the network and you look at things like private 5G networks, service providers or telcos, in this instance, will be able to deliver services all the way out to the edge, into that private 5G environment and operate that, in conjunction with those enterprise clients. >> So OpenShift allows me if I get this right, from the CSP to run, have a horizontally scalable organization. Okay. And from a unification platform standpoint. Okay. Whether it's 5G and other functions, is that correct? >> Darrell: That's correct. >> Okay. So you've got that. Now I want to come in and bring in the top of the stack with the other element that's been been a big conversation here at Red Hat Summit and in the industry. That is AI and the use of data. One of the things that's emerging is the ability to have both the horizontal scale, as well as the specialism of the data and have that domain expertise. You're in the industries for Red Hat. This is important because you're going to have, one industry is going to have different jargon, different language, different data, different KPIs. So you got to have that domain expertise, to enable the ability, to, to write the apps and also enable AI. Can you comment on how that works and what's Red Hat do in there? >> So, so, so, we, we're developing OpenShift and a number of our, other technologies, to be fit for the edge of the network, where a lot of these AI applications will reside, because you want them at the closest to the client or the, or the application itself, where it needs to reside. We're, we're creating that edge fabric, if you like. The next generation of hybrid cloud is really going to be, in my view at the edge. We're enabling a lot of the service providers to go after that, but we're also igniting by industry. You mentioned different industries. So if I look at, for example, manufacturing with MindSphere, we recently announced with Siemens, how they do at the edge of the network, factory automation, collecting telemetry, doing real-time data and analytics, looking at materials going through the factory floor, in order to get a better quality result, with lower, lower levels of imperfections, as they run through that system. It's just one industry and they have, their own private and favorite AI platforms and data sets they want to work with. With their own data scientists who understand that, that, that ecosystem inherently. You can move that to healthcare. And you can imagine, you know, how you actually interface with your healthcare professionals here in North America, but also around the world. How those applications and services and what the AI needs to do, in terms of understanding x-rays and looking at, you know common errors associated with different x-rays, so, so our practitioner can make a more specific diagnosis, faster, saving money and potentially lives as well. So different, different vertical markets in this space, have different AI and ML requirements and needs, different data sciences and different data models. And what we're seeing is an ecosystem of companies, that are starting up there in that space, you know, we have Watson as part of IBM, but you have Perceptor Labs, you have H2O and a number of other, very very important AI based companies in that ecosystem. >> Yeah. And you've got the horizontal scalability of the control plane then in the platform, if you will, that gives us cross-organizational leverage and enable that, that vertical domain expertise. >> Exactly. And you'd want to build an AI application, that might run on a factory floor for certain reasons, it's location and what they're actually physically building. You might want to run that on premise. You might actually want to put it in the IBM cloud, or in Zuora or into AWS. You develop it once to OpenShift, you can deploy it in all of those as a service, sitting natively in those environments. >> Darrell, great chat. You got a lot going on. telco cloud, there is a lot of cloud-native disruption going on. It's a challenge and an opportunity. And some people have to be on the right side of history, on this one, if they're going to get it right. We'll know, and the scoreboard will be very clear, 'cause this is a shift, it's a shift. So again, you hit all the key points that I wanted to get out, but I want to ask you two more areas that are hot here at Red Hat Summit 21, as well, again as well in the industry. I want to get your reaction and thoughts on. And they are DevSecOps and automation. Okay. Two areas everyone's talking about, DevOps, which we know is infrastructure as code, programmability, under the hood, modern application development, all good. You add the second there, security, DevSecOps, it's critical. Automation is continuing to be the benefits of cloud-native. So DevSecOps and automation, what's your take, and how's that impact the telco world and your world? >> You can't, you can't operate a network without having security in place. You're talking about very sensitive data. You're talking about applications that could be real-time critical And this is actually, even lifesaving or life threatening, if you don't get them right. So the acquisition that Red Hat recently made around StackRox, really helps us, make that next level of transition into that space. And we're looking at about how we go about securing containers, in a cloud-native environment. As you can imagine, there'll be many many thousands, tens of thousands of containers running. If one is actually misbehaving for want of a better term, that creates a security risk and a security loophole. We're shoring that up. That's important for the deployment OpenShift in the telco domain and other domains. In terms of automation, if you can't do it at scale and if you look at 5G and you look at the radios at the edge of the network and how you're going to provision those services. You're talking about hundreds of thousands of nodes, hundreds of thousands. So you have to automate a lot of those processes, otherwise you can't scale to meet the opportunity. You can't physically deploy. >> You know, Darrell this is a great conversation, you know as a student of history and Dave Vellante and I always kind of joke about that. And you've been in and around the industry for a long time. Telcos have been balancing this evolution of digital business for many, many decades. And now with cloud-native, it's finally a time where you're startin' to see, that it's just the same game, now, new infrastructure. You know, video, voice, text, data, all now happening, all transformed and going digital, all the way, all aspects of it. In your opinion, how should telcos be thinking about, as they put their plans in place for next generation? Because you know, the world is, is now cloud-native. There's a huge surface here of opportunities, different ecosystem relationships. The power dynamics are shifting. It's, it's really a time where there will be winners and there will be losers. What's your, what's your view on on how the telco industry needs to Cloudify, and how to be positioned for success? >> So, so one of the things I, I truly believe very deeply, that the telcos need to create a platform, horizontal platform that attracts developer and ecosystems to their platform, because innovation is going to sit elsewhere. Then you know, there might be a killer application that one telco might create, but in reality, most of those innovations, the most of those disruptors are going to occur from outside of that telco company. So you want to create an environment, where you're easy to engage and you've got maximum sets of tools and versatility and agility in order to attract that innovation. If you attract the innovation, you're going to ignite the business opportunity that 5G and 6G and beyond is going to actually provide you, or enable your business to drive. And you've really got to unlock that innovation. And you can only unlock it, in our view at Red Hat innovation, if you're open. You know, you follow open standards, you're using open systems and open source, is a method or a tool, that you guys, if you're a telco I would ask, you guys need to leverage and harness. >> Yeah. And there's a lot. And there's a lot of upside there if you get that right. >> Yes. >> There's plenty of upside. A lot of leverage, a lot of assets, take advantage of the whole offline, online, coming back together. We are living in a hybrid world, certainly with the pandemic. We've seen what that means. It's put a spotlight, on critical infrastructure and the critical shifts. If you had to kind of get pinned down Darrell, how would you describe that learnings from the pandemic. As folks start to come out of the pandemic, there is a light at the end of the tunnel. As we come out of this pandemic, companies want a growth strategy. Want to be positioned for success. What's your learning coming out of the pandemic? >> So from, from my perspective, which really kind of in one respect was, was very admirable, but, in another respect is actually deeply, a lot of gratitude, is the fact that the telecommunications companies, because of their carrier grade capabilities and their operational prowess, were able to keep their networks up and running and they had to move significant capacity from major cities to rural areas, because everyone was working from home. And in many different countries around the world, they did that extremely, extremely well. And their networks held up. I don't know, and maybe someone will correct me and email me, but I don't know one telco had a huge network outage, through this pandemic. And that kept us connected. It kept us working. And it also, what I also learned is, that in certain countries, particularly Latam, where they have a very large prepaid market. They were worried that the prepaid market in the pandemic would go down, because they felt that people would have less money to spend. And therefore they wouldn't top up their phones as much. The opposite effect occurred. They saw prepaid grow. And that really taught me, that, that connectivity is critical, in times of stress, that we are also, where everyone's going through. So, I think there were some key learnings there. >> Yeah, I think you're right on the money there. It's like they pulled the curtain back of all the FUD and said, you know, necessity's the mother of invention. And when you look at what happened and what had to happen, to survive in the pandemic and be functional, you're, you nailed it. The network stability, the resilience, but also the new capabilities that were needed, had to be delivered in an agile way. And I think, you know, it's pretty much a forcing function, for all the projects that are on the table, to know which ones to double down on. So, I think you pretty much nailed it. >> Thank you. Darrell Jordan Smith, senior vice president of industries and global accounts for Red Hat, theCube alumni. Thanks for that insight. Thanks for sharing. Great conversation around telcos and telco clouds and all the edge opportunities. Thanks for coming on. >> Thank you, John. >> Okay. It's theCube's coverage of Red Hat Summit 21. I'm John Furrier, your host. Thanks for watching. (upbeat music)

(upbeat music) >> Hello and welcome back to theCUBES coverage of Red Hat summit 21 virtual. I'm John Furry, host of theCUBE. We've two great guests here, returning back CUBE alumni here to give us their perspective. Dave Linquist GM VP of engineering hybrid cloud management at Red Hat. Joe Fitzgerald, general manager VP of the management business unit Red Hat. Guys, welcome back to theCUBE. Congratulations, Red Hat summits, ongoing virtual. Great to see you. >> Thank you, John. >> Thanks John. >> So I'd love to get the low down. A lot going on the productivity this year. Looking back from last year, a lot's been done and we've been in the pandemic now, now circling back a full year. A lot's happened- a lot of productivity, a lot of clear visibility on, on what's working, what's not, you guys got some great news. Let's just jump right into it. What's the big announcement? >> So one of the things that we announced here at Summit, John, is an expansion of our Red Hat insights brand. Basically we announced Red Hat insights for our RHEL platform back in 2015. Over the years, we've increased the amount of data and visibility into those systems. Here at summit, we've now announced Red Hat insights for both OpenShift, and for the Red Hat Ansible platform. So it's a pretty significant increase in the visibility that we have to the platforms. >> Oh, so can you repeat that one more time? So the expansion is through which platform style specifically? >> So Red Hat insights is a way that we connect up to different platforms that Red Hat provides. Historically it was for Red Hat enterprise Linux realm. We've now expanded it to the Red Hat, OpenShift family, the platforms as well as the Red Hat Ansible automation platform as well. >> So a nice broad expansion and people want that data. What's what was the motivation behind it? Was it customer demand? Was it more access to the data? Just, was it on the roadmap? What's the motivation- where where's this going? What's what's the purpose of all this? >> Well, I don't think customers say, Hey, please, you know take more data. I think it's customers say, can you keep me more secure? Can you keep my systems more optimized? Can you help me set more things to automatic? And that requires that you get data from these systems that you can auto tune on, auto- secure, auto optimize. Right? So it's really all those benefits that we get by connecting to these systems, bringing the telemetry data that config different kinds of information, and using that on customer behalf to optimize secure to the systems. >> You know, one of the biggest trends I think now for multiple years has been observability with cloud native, more services are being turned on and off enterprises are are getting a lot of pressure to be modern in their in their application development processes. Why is data more important than ever now? Can you guys take a minute to expand on that? Because this idea of telemetry across the platform is a very interesting announcement because you're turning that data into value, but can you guys expand where's that value coming, turning into? What is the value proposition? Where are people seeing the, the, the key key value points? >> Well, a couple of points, John, as you started out is in a hybrid cloud environment with cloud native applications and a lot of application modernization and the current progressiveness of DevOps and SRE teams, you're seeing a lot of dynamics and workloads and continuous delivery and deployments that are in public environments and private environments, distributed models. And so consequently, there's a lot of change in dynamics in the environment. So to sustain these high levels of service levels to sustain the security and the compliance, the ability to gather data from all these different points, to be able to get visibility into that data. It'd be able the ability to process that with various analytics and understand what when something's gone wrong or when an update is needed or when a configuration has drifted is increasingly critical in that in a hybrid cloud environment. >> So on the telemetry piece is that in open shift as well that that's supporting that as in there has that work. >> It's it's in OpenShift, as Joe mentioned, it's in braille it's in V2 Ansible and the OpenShift space we'd have an offering advanced cluster management that understands fleets of deployments, clusters, wherever they're deployed however they're running infrastructure public private hybrid environments. And it also collects in the context of the workloads that are deployed on those on those clusters to multi-question burn. >> I want to ask you guys a question. I get this all the time on theCUBE. Hey, you know, I need more data. I have multiple systems. I need to pull that data into one kind of control plane but I'm being pushed more and more to keep scaling operations. And this becomes a huge question mark for the enterprises because they, they have to turn up more, more scale. So this is becomes a data problem. Does this solve it here? How do you guys answer that? And what was the, what would be your response to that trend? >> Well, I think the, the thirst for data, right? There's a lot of things you can do with more data. There is a point where you can't ship all the data everywhere, right? If you think about logs and metrics and all the data it's too heavyweight to move everything everywhere. Right? So part of it is, you know, selecting the kind of data that you're going to get from these systems and the purpose you're going to use it for. And in the case of Red Hat, we take data from these different systems, regardless of whether they're deployed bring it in, and then we did predictive analytics against that data. And we use that telemetry that can take that health data right to do everything from optimize for performance or security costs, things like that. But we're not moving, you know, huge quantities of data from every system to Red Hat in order to, you know, pour through it. We are very selectively moving certain kinds of data for very specific purposes. >> Dave, what's your take on that because you know you got to engineer these systems. What's the optimized path for data? Do you keep it in the silo? Do you bring it together? What's the customer's view on, on how to deal with the data? >> Yeah. It is a complex problem. No doubt. You don't want it to be pulling all the data and trying to transmit all that data back into your analytics system. So you ended up curating some data, some of it you afford on often it's done under it will be done under control of policies. So that data that is sensitive, that should stay within the environment that it's in, will stay, but curated or alerts or information that's particularly relevant say to configurations, updates, any any of that type of information will go up into the analytics, into the insights. And then in turn, the alerts will come back down in a manner that are presented to the user. So they understand what actions need to be taken place whether there's automated actions or or they have to get approvals to maybe make an update to a certain environment. >> All right, you got telemetry, data power, the the advanced cluster management ACM. What's the overlap of the visibility and automation here. Can you guys talk about that? >> Well, let's say it's a great question, John what we'd like to do is we'd like to sort of separate the different areas. There's the seeing, right. And what's going on in these environment. Right. So getting the data analyzing it and determining what needs to be done. And then the, you know the recommendation of the automation. As Dave said, in a lot of environments, there's a process of either approvals or checkpoints or, you know evaluation of the changes being made to the system. Right. So separating the data and the analysis from the what do you want to do at this and making that configurable I think is really powerful. >> Yeah. I mean, that's, I mean I think that's the number one thing is like, you know everyone always asks, what do you optimize for do you optimize for the automation or the visibility? And I think, you know, there's always a trade-off and that's always interesting question David- love to get your thoughts. If someone asks you, Hey, I'm a I'm I have a team of people. What do I optimize for? The visibility or the automation or both? Is or is there a rule of thumb or is there a playbook? What w how would you answer that question? >> Well, there's a couple of things. I first, I think the, the ability to pull the data together to get visibility across the environment is critical. And then what becomes often complex is how the different disciplines, how the different parts of the system are able to work together on common understanding of the resources common understanding the applications. That's usually where systems start falling down. And so it's too siloed. So one of the key things we have with with our systems, particularly with OpenShift and row and with ACM and Ansible is the ability to have the common back lane and the ability to have a common understanding of the resources and the applications. And then you can start integrating the data around that common, those common data models and take appropriate actions on that. So that's how you ended up getting the visibility integrated with the automation. >> When you think about this, Joe about the security aspect of it and the edge of the network which has been a big theme this year and going into next year, a lot more discussion just the industrial edge, you know, that's important. You got to take all this into account. How do you, how would you talk about folks who are thinking about embedding security and thinking about now the distributed edge specifically? >> Right. So we thought it was complicated before, right? It goes up a notch here, right? As you have, you know, more and more edge applications I think at the edge, you're going to want automated policies and automated configurations in force so that when a device connects up to a network or is, you know analyzed that there's a set of policies and some configurations and versions that need to be applied to that device, these devices, aren't always connected. There's not always high bandwidth. So you basically want a high degree of automation in that case. And to get back to your early point there are certain things you can set like policies about security or configuration. You say, I always want it to be like this and make it so and there's other things where they're more you know, complicated, right. To, to address or have regulatory requirements or oversight issues. And those things you want to tell somebody I think this should be done. Is this the right thing to do? Is it okay? Do it, but at the edge you're going to have a lot more sort of lights out automation to keep these things secure, to configure. Right. >> It's funny. I was, some of the Ansible guys are talking about, you know code for code, changing code all the time and dynamic nature of some of the emerging tech coming out of the Red Hat teams. It's pretty interesting. You guys have going on there, but you know, you can bring it down to the average enterprise and main street, you know enterprise out there, you know, they're looking at, okay I got some public loud. Now I got hybrid. I'm going a hundred percent hybrid. That's pretty much the general consensus of all the enterprises. Okay. So now you say, okay, if I understand this correctly you got insights on REL, OpenShift and Ansible platform. So I'm, am I set up for an open hybrid cloud? That's the question I want to ask you guys does that give me the foundation to allow me to start the cloud adoption with an, a true distributed open way >> I'll I'll offer to go first. I think there's a couple of things you need in order to run across hybrid clouds. And I think Red Hat from a platform point of view the fact that Red Hat platforms run across all those different environments from the public cloud to on-premise and physical vert to edge devices. Now you have consistency of those platforms whether it's your traditional on REL, your container based workloads on shift or automation that's being turned in by Ansible. Those are consistent across all these different hybrid cloud environments. So reduces the complexity by standardizing those platforms across any and all of those different substrates. Then, when you can take the data from those systems bring them centrally and use it to manage those things to a higher degree of automation. Now you take an, another sort of chunk of complexity out of the problem, right? Consistency of getting data from all those different systems being able to set policies and enforce things across all those distributed environments is huge. >> Yeah. And then, you know, it fills in the gaps when you start thinking about the siloed teams, you know, the, the, I think one of the messages that I've been hearing out of Red Hat Summit in the industry that's consistent is the unification trend that's going on. Unifying development teams in a way that creates more of an exponential value curve rather than just linear progressions in, in traditional IT. Are you guys seeing that as well? I mean, what's your take on this? That's that piece of the story? >> Well, I think the shift that we've seen for the last few years actually quite a few years with DevOps and SRE is started to bring a lot of the disciplines together that you mentioned that are traditionally silos. And you're finding the effectiveness of that is really around many of the areas that we've been discussing here which is open platforms that can run consistently across a hybrid environment, the ability to get data and visibility out of this platform. So you can see across the distributed environment across the hybrid environment and then the ability to take actions in Bourse or update environments through automation is, is is really what's critical to bring things to to bring it all together. >> Yeah. I think that's such an important point, Joe. You know, I was talking with Chris right around and we we've covered this in the past red hats success with academics in the young people coming into in the universities with computer science. It's not just computer science anymore. Now you have engineering degrees kind of cross-disciplinary with SRS is SRE movement because you're looking at cloud operations at scale. That's not an IT problem anymore. It's actually an IT next gen problem. And this is kind of what, there's no real degree. There's no real credential for, you know large scale hybrid cloud environment. You guys have the mass open cloud initiative. I saw that going on. That's some really pretty big things. This is a, a change and, and talent. What's your, what's your view on this? Because I think people want to learn what what do I need to be in the future? What position? >> So John it's a great question. I think Ansible actually addresses a number of the issues you brought up, which is, you know historically there've been different tools for each of the different groups. So, you know, developers had their favorite set of tools and different, IT areas their favorite set of tools and technologies. And it was sort of like a tower of Babel. People did not share the same, you know sort of languages and tools. Ansible crosses both your your development test and operational teams. So creates a common language, now that can be used across different teams. It's easy to understand. So it sort of democratizes automation. You don't have to be deeply skilled in some, you know misspoke language or technology in order to be able to do some level of automation. So I think sort of sharing the same technology and tools I'd like an answer, more democratizing it so that more people can get involved in automating sharing that automation across teams and unifying those worlds is huge, right? So I think that's a game changer as well in terms of getting these teams work holistically integrated. >> Yeah. And there's also a better together panel on the Ansible and advanced cluster management session. Folks watching should check it out on on the virtual event platform on that point while I got you here on that point, let's let's talk about the portfolio updates for advanced cluster management for Kubernetes, what's new since the Ansible Fest, Ansible Fest announcements >> There's quite a bit that's been new since Ansible Fest. Ansible Fest well actually going back to Summit last year we introduced advanced cluster management. For years, we've been seeing the growth of Kubernetes with cloud native and clusters. And what ACM really allows enterprises to do is is scale out their deployments of OpenShift. Well, one of the things we found is that as you're deploying workloads or clusters or trying to take care of the compliance, the importance of integrating that environment with the breadth of capabilities that Ansible has in automation. So that's what we announced that at Ansible Fest following last year's summit what we've done is put a lot more focus on that integration with Ansible. So when you bring up, provision a cluster maybe you need to make some storage or security configurations on behalf of that cluster or if you're taking care of the compliance how do you remediate any issues with Ansible or one of the things that get shown a lot, demonstrate a lot with customers like is when you're deploying applications into production, how do you configure the network? Do the network configurations like a load balancer maybe a ticket into your service management system along with say a threat detection on your security. So a lot of advances with ACM and the integration with a broader ecosystem of IT, in particular with, with Ansible >> What's the ecosystem update for partners? And this has comes up all the time. I want to make sure I get this in there. I want it, I missed it. Last time we chatted, you know, the partner impact to this. You mentioned the ecosystem and you've got native Coobernetti's, non-native what's native to open. You guys have a lot of native things and sometimes it's just support for other clouds. So you start to get into the integration questions. Partners are very interested in what you guys are doing. Can you share the partner update on how they play and what impacts them the most here? >> Yeah. On the events, cluster management ACM front first with this integration with Ansible that actually allows us to integrate with the wealth of partner ecosystem the Ansible apps, which is huge. So that's, that's one, one space. And then the way ACM works, this policy desirous state model is we've been able to integrate with a large number of partners around particularly the security space model the service management space, where they, where we can enforce the use of certain security tools on the on the clusters themselves. So it's really opened up how quickly partner offerings can be integrated into the OpenShift environment at scale across all the clusters that you want, that you need to support it on what the appropriate configurations and policies >> I got to ask you on the insight side you mentioned the expansion across the platform. Now, if you go out and take out to the ecosystem, you know there's guard rails around governance how far can partners push their data in terms of sharing? That's something that might come up when you comment on that. >> Sure. So Red Hat, you know, takes, you know our customer data very seriously. We're a trusted partner to our customers. So the data that we get from systems we make sure that we are following all of the governance and oversight necessary to protect that data. So far, we have basically been collecting that data and using that data at Red Hat. Our plan really is to allow partners with the right degree of governance and control to be able to use some of that data in the future, under the right conditions whether it's anonymized or aggregated, things like that to be able to take that data and to add value to customers if they can enrich customers or or help customers by getting some access to that data without every vendor or partner, having to go out to systems and having to connect and pull data back. That's a pretty tough situation for customers to live with. But I think that fact that we're ahead is trusted. We've been doing this for awhile. We know how to handle the data. We know how to provide the governance. But our plan really is to enable partners to use that data ecosystem. I will say that initially what they had said about ACM and partners, Ansible has been working with partners on the automation side at a very large scale, right? So if you look at the amount of partners that are doing automation, work with us we have some pretty strong, you know, depth there. But in terms of working with partners, our plan is to take the data ecosystem, expand that as well. >> It's really a nice mix between the Ansible OpenShift and then REL, do you guys have great insights across now? I think the open innovation just continues to be every year. I say the same thing. It's almost like a broken record but every year it just gets better and better. You know, innovation out in the open you guys doing a great job and continuing and now certainly as the pandemic looks like it's coming to an end soon, post-pandemic, a lot more projects are being worked on a lot more productivity, as we said at the top. So to end the segment out I'd love to get you guys to weigh in on what happens next. As we come out of the pandemic, the table has been set. The foundation's there, cloud native is continuing to accelerate rapidly in the open OpenSource, going through them on another level. What's next what's, what's going to what's next for customers. Are they going to continue to double down on those? The winds they're going to shut down certain projects. What happens after this pandemic? How do people grow, Dave? We'll start with you. >> Well, I think, yes we all see the light at the end of the tunnel, John. It's great. And I think if a positive, is it really throughout this? We've been accelerated in the digitization and at modernization cross the board across industries. Okay. And that is really teaching all of us a lot about the importance of how do you start managing and running this at scale and securing this at scale. So I think what we'll see coming out of this is just that much more effort, open ecosystems. How you really bring together data across insights? How do you bring in increasing the amount of analytics AI to now do something turn that data into information that you can respond with and that in turn, close it, closing the loop with automation against or against your hybrid cloud environment? We're just going to see acceleration of that occurring. >> Awesome, great insights there. Open data insights, automation, all kind of coming together. AI. You don't have AI in your, your plans. Someone was Wall Street was joking. That's going to be the future stable stakes get listed on Wall Street. You got to have some sort of AI piece. They have great insight, Joe, your take on what's next? What, what what's going to what's going to happen as we come out of the pandemic? >> Yeah. We've definitely seen people, you know advance their digital transformation. And I don't think it's going to stop. Right? So the speed scale and complexity or just put more pressure on teams, right? To be able to support these environments that are evolving at light speed. So I think Red Hat is really well positioned and is a great partner for folks who are trying to get more digital, faster trying to leverage these technologies from the hybrid cloud to the edge. They're going to need lots of help. Red Hat is in a great position. >> Okay. >> You guys doing great work, Dave Linquist, Joe Fitzgerald. Great to have you back on again. Open, always wins. And as end users become much more participants in the open source ecosystem and user contributions and user interactions software at scale, it's now a new come next generation commercial environment, You guys are doing a great job. Thank you for sharing. Appreciate it. >> Thank you John. >> Thanks John. >> Okay. Red Hat Summit 21 CUBE coverage. I'm John Furrier getting all the action from the experts who've been there, done that living through it, being more productive and have bringing benefits to you being open source. Thanks for watching.

>>From around the globe covering Google cloud next. >>Hi, I'm Stu middleman and this is the cube coverage of Google cloud. Next, happy to welcome back to the program. One of our cube alumni, Clayton Coleman, he's the architect for Kubernetes and OpenShift with red hat Clayton. Thanks for joining us again. Great to see you. Good to see you. All right. So of course, one of the challenges in 2020 is we love to be able to get unity together. And while we can't do it physically, we do get to do it through all of the virtual events and online forum. Of course, you know, we had the cubit red hat summit cube con, uh, for the European show and now Google cloud. So, you know, give us kind of your, your state of the state 2020 Kubernetes. Of course it was Google, uh, taking the technology from Borg, a few people working on it, and, you know, just that this project that has just had massive impact on it. So, you know, where are with the community in Kubernetes today? >>So, uh, you know, 2020 has been a crazy year for a lot of folks. Um, a lot of what I've been spending my time on is, um, you know, taking feedback from people who, you know, in this time of, you know, change and concern and worry and huge shift to the cloud, um, working with them to make sure that we have a really good, um, you know, foundation in Kubernetes and that the ecosystem is healthy and the things are moving forward there. So there's a ton of exciting projects. I will say, you know, the, the pandemics had a, an impact on, um, you know, the community. And so in many places we've reacted by slowing down our schedules or focusing more on the things that people are really worried about, like quality and bugs and making sure that the stuff just works. Uh, I will say this year has been a really interesting one and open source. >>There's been much more focus, I think, on how we start to tie this stuff together. Um, and new use cases and new challenges coming into, um, what maybe, you know, the original Kubernetes was very focused on helping you bring stuff together, bring your applications together and giving you common abstractions for working with them. Um, we went through a phase where we made it easy to extend Kubernetes, which brought a whole bunch of new abstractions. And, and I think now we're starting to see the challenges and the needs of organizations and companies and individuals that are getting out of, um, not just in Kubernetes, but across multiple locations across placement edge has been huge in the last few years. And so the projects in and around Kubernetes are kind of reacting to that. They're starting to, um, bridge, um, many of these, um, you know, disparate locations, different clouds, multicloud hybrid cloud, um, connecting enterprises to data centers are connecting data centers to the cloud, helping workloads be a little bit more portable in of themselves, but helping workloads move. >>And then I think, you know, we're, we're really starting to ask those next big questions about what comes, what comes next for making applications really come alive in the cloud, um, where you're not as focused on the hardware. You're not focused on the details, which are focused on abstractions, like, um, you know, reliability and availability, not just in one cluster, but in multiple. So that's been a really exciting, uh, transition in many of the projects that I've been following. You know, certainly projects like Istio I've been dealing with, um, spanning clusters and connecting existing workloads in and, uh, you know, each step along the way, I see people sort of broaden their scope about what they want, uh, open source to help themselves. >>Yeah, I it's, it's, it's been fascinating to watch just the, the breadth of the projects that can tie in and leverage Kubernetes. Uh, you brought up edge computing and want to get into some of the future pieces, but before we do, you know, let's look at Kubernetes itself. Uh, one dot 19 is kind of where we are at. Uh, um, I already see some, some red stalking about one dot 20. Can you just talk about the, the, the base project itself contributions to it, how the upstream, uh, works and you know, how, how should customers think about, you know, their Kubernetes environment, obviously, you know, red hat with open shifts had a very strong position. You've got thousands of customers now using it, all of the cloud providers have their, uh, Kubernetes flavor, but also you partner with them. So walk us through a little bit about, you know, the open source, the project and those dynamics. >>The project is really healthy. I think we've got through a couple of big transitions over the last few years. We've moved from the original, um, you know, I was on the bootstrap steering committee trying to help the governance model. The full bootstrap committee committee has handed off responsibility to, um, new participants. There's been a lot of growth in the project governance and community governance. Um, I think there's huge credit to the folks on the steering committee today. Folks, part of contributor experience and standardizing and formalizing Kubernetes as its own thing. I think we've really moved into being a community managed project. Um, we've developed a lot of maturity around that and Kubernetes and the folks involved in helping Kubernetes be successful, have actually been able to help others within the CNCF ecosystem and other open source projects outside of CNCF be successful. So that angle is going phenomenally well. >>Uh, contribution is up. I think one of the tension points that we've talked about is, um, Kubernetes is maturing one 19, spent a lot of time on stability. And while there's definitely lots of interesting new things in a few areas like storage, and we have fee to an ingress fee too, coming up on the horizon dual stack, support's been hotly anticipated by a lot of on premise folks looking to make the transition to IPV six. I think we've been a little bit less focused on chasing features and more focused on just making sure that Kubernetes is maturing responsibly. Now that we have a really successful ecosystem of integrators and vendors and, um, you know, unification, the conformance efforts in Kubernetes. Um, there've been some great work. I happened to be involved in the, um, in the architecture conformance definition group, and there's been some amazing participation from, um, uh, from that group of people who've made real strides in growing the testing efforts so that, you know, not only can you look at, um, two different Kubernetes vendors, but you can compare them in meaningful ways. >>That's actually helped us with our test coverage and Kubernetes, there's been a lot of focus on, um, really spending time on making sure that upgrades work well, that we've reduced the flakiness of our test suites and that when a contributor comes into Kubernetes, they're not presented with a confusing, massive instructions, but they have a really clear path to make their first contribution and their next contribution. And then the one after that. So from a project maturity standpoint, I think 2020 has been a great great year for the project. And I want to see that continue. >>Yeah. One of the things we talked quite a bit about, uh, at both red hat summit, as well as, uh, the CubeCon cloud native con Europe, uh, was operators. And, you know, maybe I believe there was some updates also about how operators can work with Google cloud. So can you give us that update? >>Sure. There's been a lot of, um, there's been a lot of growth in both the client tooling and the libraries and the frameworks that make it easy to integrate with Kubernetes. Um, and those integrations are about patterns that, um, make operations teams more productive, but it takes time to develop the domain expertise in, uh, operationalizing large groups of software. So over the last year, um, know the controller runtime project, uh, which is an outgrowth of the Kubernetes Siggy lb machinery. So it's kind of a, an outshoot that's intended to standardize and make it easier to write integrations to Kubernetes that next step of, um, you know, going then pass that red hat's worked, uh, with, um, others in the community around, um, the operator SDK, uh, which unifying that project and trying to get it aligned with others in the ecosystem. Um, almost all of the cloud providers, um, have written operators. >>Google has been an early adopter of the controller and operator pattern, uh, and have continued to put time and effort into helping make the community be successful. And, um, we're really appreciative of everyone who's come together to take some of those ideas from Kubernetes to extend them into, um, whether it's running databases and service on top of Kubernetes or whether it's integrating directly with cloud. Um, most of that work or almost all of that work benefits everybody in the ecosystem. Um, I think there's some future work that we'd like to see around, um, you know, uh, folks, uh, from, um, a number of places have gone even further and tried to boil Kubernetes down into simpler mechanisms, um, that you can integrate with. So a little bit more of a, a beginner's approach or a simplification, a domain specific, uh, operator kind of idea that, um, actually really does accelerate people getting up to speed with, um, you know, building these sorts of integrations, but at the end of the day, um, one of the things that I really see is the increasing integration between the public clouds and their Kubernetes on top of those clouds through capabilities that make everybody better off. >>So whether you're using a managed service, um, you know, on a particular cloud or whether you're running, um, the elements of that managed open source software using an open source operator on top of Kubernetes, um, there's a lot of abstractions that are really productive for admins. You might use the managed service for your production instances, but you want to use, um, throw away, um, database instances for developers. Um, and there's a lot of experimentation going on. So it's almost, it's almost really difficult to say what the most interesting part is. Um, operators is really more of an enabling technology. I'm really excited to see that increasing glue that makes automation and makes, um, you know, dev ops teams, um, more productive just because they can rely increasingly on open source or managed services offerings from, you know, the large cloud providers to work well together. >>Yeah. You had mentioned that we're seeing all the other projects that are tying into Coobernetti's, we're seeing Kubernetes going into broader use cases, things like edge computing, what, from an architectural standpoint, you know, needs to be done to make sure that, uh, Kubernetes can be used, you know, meets the performance, the simplicity, um, in these various use cases. >>That's a, that's a good question. There's a lot of complexity in some areas of what you might do in a large application deployment that don't make sense in edge deployments, but you get advantages from having a reasonably consistent environment. I think one of the challenges everybody is going through is what is that reasonable consistency? What are the tools? You know, one of the challenges obviously is as we have more and more clusters, a lot of the approaches around edge involve, you know, whether it's a single cluster on a single machine and, um, you know, in a fairly beefy, but, uh, remote, uh, computer, uh, that you still need to keep in sync with your application deployment. Um, you might have a different life cycle for, uh, the types of hardware that you're rolling out, you know, whether it's regional or whether it's tied to, whether someone can go out to that particular site that you've been update the software. Sometimes it's connected, sometimes it isn't. So I think a need that is becoming really clear is there's a lot of abstractions missing above Coopernetties. Uh, and everyone's approaching this differently. We've got a get ops and centralized config management. Um, we have, uh, architectures where, you know, you, you boot up and you go check some remote cloud location for what you should be running. Um, I think there's some, some productive obstructions that are >>That, or haven't been, um, >>It haven't been explored sufficiently yet that over the next couple of years, how do you treat a whole bunch of clusters as a pool of compute where you're not really focused on the details of where a cluster is, or how can you define applications that can easily move from your data center out to the edge or back up to the cloud, but get those benefits of Kubernetes, all those places. And >>That >>This is for so early, that what I see in open source and what I see with people deploying this is everyone is approaching this subtly differently, but you can start to see some of those patterns emerge where, um, you need reproducible bundles of applications, things that help can do REL, or you can do with just very simply with Kubernetes. Um, not every edge location needs, um, uh, an ingress controller or a way to move traffic onto that cluster because their job is to generate traffic and send it somewhere else. But then that puts more pressure on, well, you need those where you're feeding that data to your API APIs, whether that's a cloud or something within your something within a private data center, you need, um, enough of commonalities across those clusters and across your applications that you could reason about what's going on. So >>There's a huge amount >>Out of a space here. And I don't think it's just going to be Kubernetes. In fact, I, I want to say, I think we're starting to move to that phase where Kubernetes is just part of the platform that people are building or need to build. And what can we do to build those tools that help you stitch together computer across a lot of footprints, um, parts of applications across a lot of footprints. And there's, there's a bunch of open source projects that are trying to drive to that today. Um, projects like I guess the O and K natives, um, with the work being done with the venting in K native, and obviously the venting is a hugely, um, you know, we talk about edge, we'd almost be remiss, not talk about moving data. And you talk about moving data. Well, you want streams of data and you want to be reacted to data with compute and K native and Istio are both great examples of technologies within the QB ecosystem that are starting to broaden, um, you know, outside of the, well, this is just about one cube cluster to, um, we really need to stitch together a mindset of development, even if we have a reasonably consistent Kubernetes across all those footprints. >>Yeah. Well, Clayton so important. There's so many technologies out there it's becoming about that technology. And it's just a given, it's an underlying piece of it. You know, we don't talk about the internet. We don't talk, you know, as much about Linux anymore. Cause it's just in the fabric of everything we do. And it sounds like we're saying that's where we're getting with Kubernetes. Uh, I'd love to pull on that thread. You mentioned that you're hearing some patterns starting to emerge out there. So when you're talking to enterprises, especially if you're talking 2020, uh, lots of companies, all of a sudden have to really accelerate, uh, you know, those transformational projects that they were doing so that they can move faster and keep up with the pace of change. Uh, so, you know, what should enterprise be, be working on? What feedback are you hearing from customers, but what are some of those themes that you can share and w what, what should everybody else be getting ready for that? >>The most common pattern I think, is that many people still find a need to build, uh, platforms or, um, standardization of how they do application development across fairly large footprints. Um, I think what they're missing, and this is what everyone's kind of building on their own today, that, um, is a real opportunity within the community is, uh, abstract abstractions around a location, not really about clusters or machines, but something broader than that, whether it's, um, folks who need to be resilient across clouds, and whether it's folks who are looking to bring together disparate footprints to accelerate their boot to the cloud, or to modernize their on premise stack. They're looking for abstractions that are, um, productive to say, I don't really want to worry too much about the details of clusters or machines or applications, but I'm talking about services and where they run and that I need to stitch those into. >>Um, I need to stitch those deeply into some environments, but not others. So that pattern, um, has been something that we've been exploring for a long time within the community. So the open service broker project, um, you know, has been a long running effort of trying to genericize one type of interface operators and some of the obstructions and Kubernetes for extending Kubernetes and new dimensions is another. What I'm seeing is that people are building layers on top through continuous deployment, continuous integration, building their own API is building their own services that really hide these details. I think there's a really rich opportunity within open to observe what's going on and to offer some supporting technologies that bridge clouds, bridge locations, what you deal with computed a little bit more of an abstract level, um, and really doubled down on making services run. Well, I think we're kind of ready to make the transition to say officially, it's not just about applications, which is what we've been saying for a long time. >>You know, I've got these applications and I'm moving them, but to flip it around and say, we want to be service focused and services, have a couple of characteristics, the details of where they run are more about the guarantees that you're providing for your customers. Um, we lack a lot of open source tools that make it easier to build and run services, not just to consume as dependencies or run open source software, but what are the things that make our applications more resilient in and of themselves? I think Kubernetes was a good start. Um, I really see organizations struggling with that today. You're going to have multiple locations. You're going to have, um, the need to dramatically move workloads. What are the tools that the whole ecosystem, the open source ecosystem, um, can collaborate on and help accelerate that transition? >>Well, Clayton, you teed up on my last thing. I want to ask you, you know, we're, we're here at the Google cloud show and when you talk about ecosystem, you talk about community, you know, Google and red hat, both very active participants in this community. So, you know, you, you peer you collaborate with a lot of people from Google I'm sure. So give our audience a little bit of insight as to, you know, Google's participation. What, what you've been seeing from them the last couple of years at Google has been a great partner, >>Crazy ecosystem for red hat. Um, we worked really closely with them on Istio and K native and a number of other projects. Um, I, you know, as always, um, I'm continually impressed by the ability of the folks that I've worked with from Google to really take a community focus and to concentrate on actually solving use cases. I think the, you know, there's always the desire to create drama around technology or strategy or business and open source. You know, we're all coming together to work on common goals. I really want to, um, you know, thank the folks that I've worked with at Google over the years. Who've been key participants. They've believed very strongly in enabling users. Um, you know, regardless of, um, you know, business or technology, it's about making sure that we're improving software for everyone. And one of the beauties of working on an open source project like Kubernetes is everyone can get some benefit out of it. And those are really, um, you know, the sum of all of the individual contributions is much larger than what the simple math would apply. And I think that's, um, you know, Kubernetes has been a huge success. I want to see more successes like that. Um, you know, working with Google and others in the open source ecosystem around infrastructure as a service and, you know, this broadening >>Domain of places where we can collaborate to make it easier for developers and operations teams and dev ops and sec ops to just get their jobs done. Um, you know, there's a lot more to do and I think open source is the best way to do that. All right. Well, Clayton Coleman, thank you so much for the update. It's really great to catch up. It was a pleasure. All right. Stay tuned for lots more coverage. The Google cloud next 2020 virtually I'm Stu Miniman. Thank you for watching the cube.

>> Announcer: From theCUBE studios in Palo Alto and Boston, it's theCUBE, covering IBM Think brought to you by IBM. >> Hi, there, this is Dave Vellante. We're back at the IBM Think 2020 Digital Event Experience are socially responsible and distant. I'm here in the studios in Marlborough, our team in Palo Alto. We've been going wall to wall coverage of IBM Think, Kit Chee here is the Vice President, and general manager of Cloud and Enterprise sales at Intel. Kit, thanks for coming on. Good to see you. >> Thank you, Dave. Thank you for having me on. >> You're welcome, and Evaristus Mainsah, Mainsah is here. Mainsah, he is the general manager of the IBM Cloud Pack Ecosystem for the IBM Cloud. Evaristus, it's good to see you again. Thank you very much, I appreciate your time. >> Thank you, Dave. Thank you very much. Thanks for having me. >> You're welcome, so Kit, let me start with you. How are you guys doing? You know, there's this pandemic, never seen it before. How're things where you are? >> Yeah, so we were quite fortunate. Intel's had an epidemic leadership team. For about 15 years now, we have a team consisting of medical safety and operational professionals, and this same team has, who has navigated as across several other health issues like bad flu, Ebola, Zika and each one and one virus then navigating us at this point with this pandemic. Obviously, our top priority as it would be for IBM is protecting the health and well being of employees while keeping the business running for our customers. The company has taken the following measures to take care of it direct and indirect workforce, Dave and to ensure business continuity throughout the developing situation. They're from areas like work from home policies, keeping hourly workers home and reimbursing for daycare, elderly care, helping with WiFi policies. So that's been what we've been up to Intel's manufacturing and supply chain operations around the world world are working hard to meet demand and we are collaborating with supply pains of our customers and partners globally as well. And more recently, we have about $16 Million to support communities, from frontline health care workers and technology initiatives like online education, telemedicine and compute need to research. So that's what we've been up to date. Pretty much, you know, busy. >> You know, every society that come to you, I have to say my entire career have been in the technology business and you know, sometimes you hear negative toward the big tech but, but I got to say, just as Kit was saying, big tech has really stepped up in this crisis. IBM has been no different and, you know, tech for good and I was actually I'm really proud. How are you doing in New York City? >> Evaristus: No, thank you, Dave, for that, you know, we are, we're doing great and, and our focus has been absolutely the same, so obviously, because we provide services to clients. At a time like this, your clients need you even more, but we need to focus on our employees to make sure that their health and their safety and their well being is protected. And so we've taken this really seriously, and actually, we have two ways of doing this. One of them is just on to purpose as a, as a company, on our clients, but the other is trying to activate the ecosystem because problems of this magnitude require you to work across a broad ecosystem to, to bring forth in a solution that are long lasting, for example, we have a call for code, which where we go out and we ask developers to use their skills and open source technologies to help solve some technical problems. This year, the focus was per AVADA initiatives around computing resources, how you track the Coronavirus and other services that are provided free of charge to our clients. Let me give you a bit more color, so, so IBM recently formed the high performance computing consortium made up of the feYderal government industry and academic leaders focus on providing high performance computing to solve the COVID-19 problem. So we're currently we have 33 members, now we have 27 active products, deploying something like 400 teraflops as our petaflop 400 petaflops of compute to solve the problem. >> Well, it certainly is challenging times, but at the same time, you're both in the, in the sweet spot, which is Cloud. I've talked to a number of CIOs who have said, you know, this is really, we had a cloud strategy before but we're really accelerating our cloud strategy now and, and we see this as sort of a permanent effect. I mean, Kit, you guys, big, big on ecosystem, you, you want frankly, a level playing field, the more optionality that you can give to customers, you know, the better and Cloud is really been exploding and you guys are powering, you know, all the world's Clouds. >> We are, Dave and honestly, that's a huge responsibility that we undertake. Before the pandemic, we saw the market through the lens of four key mega trends and the experiences we are all having currently now deepens our belief in the importance of addressing these mega trends, but specifically, we see marketplace needs around key areas of cloudification of everything below point, the amount of online activities that have spiked just in the last 60 days. It's a testimony of that. Pervasive AI is the second big area that we have seen and we are now resolute on investments in that area, 5G network transformation and the edge build out. Applications run the business and we know enterprise IT faces challenges when deploying applications that require data movement between Clouds and Cloud native technologies like containers and Kubernetes will be key enablers in delivering end to end data analytics, AI, machine learning and other critical workloads and Cloud environments at the edge. Pairing Intel's data centric portfolio, including Intel's obtain SSPs with Red Hat, Openshift, and IBM Cloud Paks, enterprise can now break through storage bottlenecks and have unconstrained data availability in the hybrid and multicloud environments, so we're pretty happy with the progress we're making that together with IBM. >> Yeah, Evaristus, I mean, you guys are making some big bets. I've, you know, written and discussed in my breaking analysis, I think a lot of people misunderstand IBM Cloud, Ginni Rometty arm and a bow said, hey, you know, we're after only 20% of the workloads are in cloud, we're going after the really difficult to move workloads and the hybrid workloads, that's really the fourth foundation that Arvin you know, talks about, that you and IBM has built, you know, your mainframes, you have middleware services, and in hybrid Cloud is really that fourth sort of platform that you're building out, but you're making some bets in AI. You got other services in the Cloud like, like blockchain, you know, quantum, we've been having really interesting discussions around quantum, so I wonder if you can talk a little bit about sort of where you're allocating resources, some of the big bets that, that you're making for the next decade. >> Well, thank you very much, Dave, for that. I think what we're seeing with clients is that there's increasing focus on and, and really an acceptance, that the best way to take advantage of the Cloud is through a hybrid cloud strategy, infused with data, so it's not just the Cloud itself, but actually what you need to do to data in order to make sure that you can really, truly transform yourself digitally, to enable you to, to improve your operations, and in use your data to improve the way that you work and improve the way that you serve your clients. And what we see is and you see studies out there that say that if you adopt a hybrid cloud strategy, instead of 2.5 times more effective than a public cloud only strategy, and Why is that? Well, you get thi6ngs such as you know, the opportunity to move your application, the extent to which you move your applications to the Cloud. You get things such as you know, reduction in, in, in risk, you, you get a more flexible architecture, especially if you focus on open certification, reduction and certification reduction, some of the tools that you use, and so we see clients looking at that. The other thing that's really important, especially in this moment is business agility, and resilience. Our business agility says that if my customers used to come in, now, they can't come in anymore, because we need them to stay at home, we still need to figure out a way to serve them and we write our applications quickly enough in order to serve this new client, service client in a new way. And well, if your applications haven't been modernized, even if you've moved to the Cloud, you don't have the opportunity to do that and so many clients that have made that transformation, figure out they're much more agile, they can move more easily in this environment, and we're seeing the whole for clients saying yes, I do need to move to the Cloud, but I need somebody to help improve my business agility, so that I can transform, I can change with the needs of my clients, and with the demands of competition and this leads you then to, you know, what sort of platform do you need to enable you to do this, it's something that's open, so that you can write that application once you can run it anywhere, which is why I think the IBM position with our ecosystem and Red Hat with this open container Kubernetes environment that allows you to write application once and deploy it anywhere, is really important for clients in this environment, especially, and the Cloud Paks which is developed, which I, you know, General Manager of the Cloud Pak Ecosystem, the logic of the Cloud Paks is exactly that you'll want plans and want to modernize one, write the applications that are cloud native so that they can react more quickly to market conditions, they can react more quickly to what the clients need and they, but if they do so, they're not unlocked in a specific infrastructure that keeps them away from some of the technologies that may be available in other Clouds. So we have talked about it blockchain, we've got, you know, Watson AI, AI technologies, which is available on our Cloud. We've got the weather, company assets, those are key asset for, for many, many clients, because weather influences more than we realize, so, but if you are locked in a Cloud that didn't give you access to any of those, because you hadn't written on the same platform, you know, that's not something that you you want to support. So Red Hat's platform, which is our platform, which is open, allows you to write your application once and deploy it anyways, particularly our customers in this particular environment together with the data pieces that come on top of that, so that you can scale, scale, because, you know, you've got six people, but you need 600 of them. How do you scale them or they can use data and AI in it? >> Okay, this must be music to your ears, this whole notion of you know, multicloud because, you know, Intel's pervasive and so, because the more Clouds that are out there, the better for you, better for your customers, as I said before, the more optionality. Can you6 talk a little bit about the rela6tionship today between IBM and Intel because it's obviously evolved over the years, PC, servers, you know, other collaboration, nearly the Cloud is, you know, the latest 6and probably the most rel6evant, you know, part of your, your collaboration, but, but talk more about what that's like you guys are doing together that's, that'6s interesting and relevant. >> You know, IBM and Intel have had a very rich history of collaboration starting with the invention of the PC. So for those of us who may take a PC for granted, that was an invention over 40 years ago, between the two companies, all the way to optimizing leadership, IBM software like BB2 to run the best on Intel's data center products today, right? But what's more germane today is the Red Hat piece of the study and how that plays into a partnership with IBM going forward, Intel was one of Red Hat's earliest investors back in 1998, again, something that most people may not realize that we were in early investment with Red Hat. And we've been a longtime pioneer of open source. In fact, Levin Shenoy, Intel's Executive Vice President of Data Platforms Group was part of COBOL Commies pick up a Red Hat summit just last week, you should definitely go listen to that session, but in summary, together Intel and Red Hat have made commercial open source viable and enterprise and worldwide competing globally. Basically, now we've65 used by nearly every vertical and horizontal industr6y. We are bringing our customers choice, scalability and speed of innovation for key technologies today, such as security, Telco, NFV, and containers, or even at ease and most recently Red Hat Openshift. We're very excited to see IBM Cloud Packs, for example, standardized on top of Openshift as that builds the foundation for IBM chapter two, and allows for Intel's value to scale to the Cloud packs and ultimately IBM customers. Intel began partnering with IBM on what is now called Pax over two years ago and we 6are committed to that success and scaling that, try ecosystem, hardware partners, ISVs and our channel. >> Yeah, so theCUBE by the way, covered Red Hat summit last week, Steve Minima and I did a detailed analysis. It was awesome, like if we do say so ourselves, but awesome in the sense of, it allowed us to really sort of unpack what's going on at Red Hat and what's happening at IBM. Evaristus, so I want to come back to you on this Cloud Pack, you got, it's, it's the kind of brand that you guys have, you got Cloud Packs all over the place, you got Cloud Packs for applications, data, integration, automation, multicloud management, what do we need to know about Cloud pack? What are the relevant components there? >> Evaristus: I think the key components is so this is think of this as you know, software that is designed that is Cloud native is designed for specific core use cases and it's built on Red Hat Enterprise Linux with Red Hat Openshift container Kubernetes environment, and then on top of that, so you get a set of common services that look right across all of them and then on top of that, you've got specific both open source and IBM software that deals with specific plant situations. So if you're dealing with applications, for example, the open source and IBM software would be the run times that you need to write and, and to blow applications to have setups. If you're dealing with data, then you've got Cloud Pack to data. The foundation is still Red Hat Enterprise Linux sitting on top of with Red Hat Openshift container Kubernetes environment sitting on top of that providing you with a set of common services and then you'll get a combination of IBM zone open, so IBM software as well as open source will have third party software that sits on top of that, as well as all of our AI infrastructure that sits on top of that and machine learning, to enable you to do everything that you need to do, data to get insights updates, you've got automation to speed up and to enable us to do work more efficiently, more effectively, to make your smart workers better, to make management easier, to help management manage work and processes, and then you've got multicloud management that allows you to see from a single pane, all of your applications that you've deployed in the different Cloud, because the idea here, of course, is that not all sitting in the same Cloud. Some of it is on prem, some of it is in other Cloud, and you want to be able to see and deploy applications across all of those. And then you've got the Cloud Pack to security, which has a combination of third party offerings, as well as ISV offerings, as well as AI offerings. Again, the structure is the same, REL, Red Hat Openshift and then you've got the software that enables you to manage all aspects of security and to deal with incidents when, when they arise. So that gives you data applications and then there's integration, as every time you start writing an application, you need to integrate, you need to access data security from someplace, you need to bring two pipes together for them to communicate and we use a Cloud Pack for integration to allow us to do that. You can open up API's and expose those API so others writing application and gain access to those API's. And again, this idea of resilience, this idea of agility, so you can make changes and you can adapt data things about it. So that's what the Cloud Pack provides for you and Intel has been an absolutely fantastic partner for us. One of the things that we do with Intel, of course, is to, to work on the reference architectures to help our certification program for our hardware OEMs so that we can scale that process, get many more OEMs adopt and be ready for the Cloud Packs and then we work with them on some of the ISV partners and then right up front. >> Got it, let's talk about the edge. Kity, you mentioned 5G. I mean it's a really exciting time, (laughs) You got windmills, you got autonomous vehicles, you got factories, you got to ship, you know, shipping containers. I mean, everything's getting instrumented, data everywhere and so I'm interested in, let's start with Intel's point of view on the edge, how that's going to evolve, you know what it means to Cloud. >> You know, Dave, it's, its definitely the future and we're excited to partner with IBM here. In addition to enterprise edge, the communication service providers think of the Telcos and take advantage of running standardized open software at the Telco edge, enabling a range of new workloads via scalable services, something that, you know, didn't happen in the past, right? Earlier this year, Intel announced a new C on second generation, scalable, atom based processes targeting the 5G radio access network, so this is a new area for us, in terms of investments going to 5G ran by deploying these new technologies, with Cloud native platforms like Red Hat Openshift and IBM Cloud Packs, comm service providers can now make full use of their network investments and bring new services such as Artificial Intelligence, augmented reality, virtual reality and gaming to the market. We've only touched the surface as it comes to 5G and Telco but IBM Red Hat and Intel compute together that I would say, you know, this space is super, super interesting, as more developed with just getting started. >> Evaristus, what do you think this means for Cloud and how that will evolve? Is this sort of a new Cloud that will form at the edge? Obviously, a lot of data is going to stay at the edge, probably new architectures are going to emerge and again, to me, it's all about data, you can create more data, push more data back to the Cloud, so you can model it. Some of the data is going to have to be done in real time at the edge, but it just really extends the network to new horizons. >> Evaristus: It does exactly that, Dave and we think of it and which is why I thought it will impact the same, right? You wouldn't be surprised to see that the platform is based on open containers and that Kubernetes is container environment provided by Red Hat and so whether your data ends up living at the edge or your data lives in a private data center, or it lives in some public Cloud, and how it flows between all of them. We want to make it easy for our clients to be able to do that. So this is very exciting for us. We just announced IBM Edge Application Manager that allows you to basically deploy and manage applications at endpoints of all these devices. So we're not talking about 2030, we're talking about thousands or hundreds of thousands. And in fact, we're working with, we're getting divided Intel's device onboarding, which will enable us to use that because you can get that and you can onboard devices very, very easily at scale, which if you get that combined with IBM Edge Application Manager, then it helps you onboard the devices and it helps you divide both central devices. So we think this is really important. We see lots of work that moving on the edge devices, many of these devices and endpoints now have sufficient compute to be able to run them, but right now, if they are IoT devices, the data has been transferred to hundreds of miles away to some data center to be processed and enormous pass and then only 1% of that actually is useful, right? 99% of it gets thrown away. Some of that actually has data residency requirements, so you may not be able to move the data to process, so why wouldn't you just process the data where the data is created around your analytics where the data is spread, or you have situations that are disconnected as well. So you can't actually do that. You don't want to stop this still in the supermarket, because there's, you lost connectivity with your data center and so the importance of being able to work offline and IBM Edge Application Manager actually allows you so it's tournament so you can do all of this without using lots of people because it's a process that is all sort or automated, but you can work whether you're connected or you're disconnected, and then you get replication when you get really, really powerful for. >> All right, I think the developer model is going to be really interesting here. There's so many new use cases and applications. Of course, Intel's always had a very strong developer ecosystem. You know, IBM understands the importance of developers. Guys, we've got to wrap up, but I wonder if you could each, maybe start with Kit. Give us your sense as to where you want to see this, this partnership go, what can we expect over the next, you know, two to five years and beyond? >> I think it's just the area of, you know, 5G, and how that plays out in terms of edge build out that we just touched on. I think that's a really interesting space, what Evaristus has said is spot on, you know, the processing, and the analytics at the edge is still fairly nascent today and that's growing. So that's one area, building out the Cloud for the different enterprise applications is the other one and obviously, it's going to be a hybrid world. It's not just a public Cloud world on prem world. So the whole hybrid build out What I call hybrid to DoD zero, it's a policy and so the, the work that both of us need to do IBM and Intel will be critical to ensure that, you know, enterprise IT, it has solutions across the hybrid sector. >> Great. Evaristus, give us the last word, bring us home. >> Evaristus: And I would agree with that as well, Kit. I will say this work that you do around the Intel's market ready solutions, right, where we can bring our ecosystem together to do even more on Edge, some of these use cases, this work that we're doing around blockchain, which I think you know, again, another important piece of work and, and I think what we really need to do is to focus on helping clients because many of them are working through those early cases right now, identify use cases that work and without commitment to open standards, using exactly the same standard across like what you've got on your open retail initiative, which we're going to do, I think is going to be really important to help you out scale, but I wanted to just add one more thing, Dave, if you if you permit me. >> Yeah. >> Evaristus: In this COVID era, one of the things that we've been able to do for customers, which has been really helpful, is providing free technology for 90 days to enable them to work in an offline situation to work away from the office. One example, for example, is the just the ability to transfer files and bandwidth, new bandwidth is an issue because the parents and the kids are all working from home, we have a protocol, IBM Aspera, which will make available customers for 90 days at no cost. You don't need to give us your credit card, just log on and use it to improve the way that you work. So your bandwidth feels as if you are in the office. We have what's an assistant that is now helping clients in more than 18 countries that keep the same thing, basically providing COVID information. So those are all available. There's a slew of offerings that we have. We just want listeners to know that they can go on the IBM website and they can gain those offerings they can deploy and use them now. >> That's huge. I knew about the 90 day program, I didn't realize a sparrow was part of that and that's really important because you're like, Okay, how am I going to get this file there? And so thank you for, for sharing that and guys, great conversation. You know, hopefully next year, we could be face to face even if we still have to be socially distant, but it was really a pleasure having you on. Thanks so much. Stay safe, and good stuff. I appreciate it. >> Evaristus: Thank you very much, Dave. Thank you, Kit. Thank you. >> Thank you, thank you. >> All right, and thank you for watching everybody. This is Dave Volante for theCUBE, our wall to wall coverage of the IBM Think 2020 Digital Event Experience. We'll be right back right after this short break. (upbeat music)

>> From around the globe, it's theCube with digital coverage of Red Hat Summit 2020, brought to you by Red Hat. >> Welcome back. I'm Stu Miniman, and this is the cubes coverage of Red Hat Summit 2020. Of course, this year's event happening digitally, we're talking to Red Hat executives, partners, customers, where they are around the globe, bringing them remotely into this digital event. And really important topic, of course, has been Automation for a long time, I think back to my career automation is something we've been talking about for decades, but even more important in today's age. Happy to welcome back to the program, Tim Kramer with Red Hat, Vice President of Engineering is that I don't have listed view here. But since we last talked to him at Ansible Fest, has been a little expansion in the scope of what you're working on. First of all, welcome back, and tell us what's new in your world? >> All right, thanks a lot. Yeah, there's been rather substantial change in roles. I'm now in charge actually, of all of the engineering within Red Hat. All the development engineering site includes: the middleware teams, Red Hat Enterprise Linux, of course management and automation, the new team that we just brought over from IBM doing Advanced Container Management. I'm basically running the whole thing and OpenShift of course. >> Excellent. Just a few things to keep you busy. Congratulations on that and love your support in the the Boston "Hello World" rella eight shirt that of course we saw last year at summit. I know one of the things being digital is people do miss some of the t-shirts. I know my family was quite fond of the "May The Fourth Be With You" shirts, that Red Hat did one year at summit. Of course, celebrating Star Wars Day, highly celebrated in in the Miniman household. But Tim, let's talk about Ansible. This brings our audience up to speed, what's happening that some of the latest pieces, and of course, it's been one of the great success stories. Ansible was a lot of adoption before the acquisition, but really accelerated over the last few years? >> At Ansible Fest, we talked a lot about technology to come and showed a few demos of the possibilities. What we have done since then is actually bring all of that technology to life and to expand it. One thing that Red Hat has really done is continue to invest heavily in Ansible, to make sure that we can bring new capabilities and new value to the subscription for everyone. Some of the things that have been happening since summit, which of course we are in, and since Ansible Fest, since we last talked was it, the community continues to scale at a really rapid rate. It's almost hard to keep up. And the number of modules that we have had is grown just tremendously. We have well over 3000 modules now that are available, and as customers and partners and also just casual users are looking through that, it's difficult to figure out: what's really supported? What's really rock solid? What can I count on? And what is, maybe sort of that Wild West community, I'm just trying out some stuff with Ansible and see how it goes. We've been focusing on a lot, is a place that you can come to the Ansible automation platform and the hub where you can now get this content and you can rely on the fact that it's going to be certified by partners, tested by partners, they're always keeping up with the latest updates. A great example of this is, let's just take NetApp or F5, or Cisco as good examples, across the various spaces, we absolutely in the Ansible engineering team are not experts on all of the latest changes, the new hardware coming out, the new software upgrades that they're making. And our ability to keep up with that is pretty difficult. We just can't do it, but they sure can. And their customers, and our customers are both demanding that we give them more content, better content, and we need to be able to do it at the rate that our partners want to be able to provide that kind. As an example, normally we were kind of slowing Ansible down and trying to do one release every six months. But if a new piece of software, a new switch or a new disk array or anything comes out in the meantime, all of our customers had to wait for that next six months release, that was not very convenient. And having an expectation that our partners are going to line up on our schedule is, well, That didn't work out so well for them. We've created the certified content. And we now have the goals to have 50 certified partners. Back at first, I think we had three or four. We're now up to 30, our goal is to hit 50. We had about 100 modules that we showed at fest that were certified, we now have over 1200 modules that are certified content. And these are our partners, creating this content and making it stable and secure for everyone to use. >>So that, I think, by far   >> That was the coolest thing that we've done. >> Yeah, it's great to see that progress. Congratulations on the momentum since Ansible Fest. One of the other things talked about that back at that show, we talked about how analytics and automation, how those are going together, how's adoption been? Is this impossibly met? >> Adoption on the analytic side has been... It's been taking off. It was pretty nascent. I can tell you that, that we've grown by about five X there, but we started a little bit small. We had a few customers that signed up early on to do it. I think probably the more impressive thing is that, we have a couple of customers in markets that you would traditionally think, we're not going to get their data, they're more concerned about what we're sharing, but we have a major bank, we have a major manufacturer that have well over 10,000 systems providing data back into Red Hat that allows us then to analyze and provide a bunch of analytics back on their running estate. And I think that's amazing, seeing the big customers that are coming in from Marcus that you might think, we're probably not going to get a lot of uptake has been really exciting to me. >> All right, you talked a bit about how Ansible fits into the ecosystem, of course being at summit, want to understand a bit more how Ansible the latest of how it's fitting into the rest of the Red Hat portfolio. I've got interviews with Stephanie Shiraz, talking about you, Raul and Joe Fitzgerald, talking about ACM, your group I know is heavily involved working on a lot of those pieces. Help us understand how this is kind of a seamless portfolio. >> I think that's one of the most important things that we do within Red Hat team, is that we have to share the sufficiency across all the product groups and make them better and provide an additional enhanced value there. We've done a lot on the RHEL side, probably one of the maybe lesser known thing is that, we've been working really closely on OpenShift. And actually, we have a lot of customers now that really want the Ansible automation hub available on OpenShift as a first-class application. We're doing things, we're writing operators for those so that we can automate the updates and upgrades and back up and all of that important functionality, so that it's really easy, than to manage your Ansible automation hub, running on OpenShift, that's one big thing. And then we're going to integrate that really well into the advanced container management, that the team from IBM that came over is working towards. I have a really close partnership with ACM team to make sure that we can start to not only gather lists of affected systems, but then take that list and do a bunch of automations against it. >> That's one. On the RHEL side, we've done a lot. We introduced at last summit rally, and we talked about having insights as part of that. Since then, we've been adding more and more capabilities into insights, and to enhance that value of the subscription route. We looked at adding in, well, advisor is now what we used to call insights. It's just something that advises you about problems or issues that may be occurring in your URL instances that are running on prem. We've also added in a drift service, so you can tell if your configurations are sort of drifting apart. We've added in a compliance checker, so you can define some kind of a policy or compliance that you want to enforce on all of your running instances, and we make sure that you're still compliant. We also have a vulnerability detector, which you'd kind of expect, so any nasty security issues that come along, we can pop those up and show you right away. And probably some of the... One of the newer things is, we allow you to do patching. And you can do that patching, right from cloud@redhat.com. We also have another new very exciting feature, which is Subscription Watch, also on cloud@redhat.com. And what this allows you to do is to see and manage all of your subscriptions across your entire hybrid estate. From what you're running on prem, to what you're running in any of the public clouds, we can actually track that for you. You can see what kind of usage you have. And then, make better economic decisions for yourself, and then be able to easily expand that usage if you want to, it used to be a little bit more difficult to do that. We're trying to make subscriptions just like as much in the background as possible to make it easier for our customers. >> Tim, one of one of the big changes customers have to go through is moving from, their environment in their data centers, to the leverage of SaaS and managing things that are outside of their control and the public cloud. You've got an engineering development team, and you've got software that went from, mostly going in customers data centers too, you've got SaaS offerings, you're living in the public cloud. Want to understand, what's changing in your world? What advice would you give to other people as to kind of the learnings that Red Hat has had going through those pieces? >> It's actually a kind of a neat story, because after we change to start making a lot of our services that we had just only shipping products on prem into cloud based services, we had to develop this platform to be able to host all of these services. We started with the insights platform, because we already had that running out in the public cloud. So that was the obvious first thing to base everything on. But we had to build out that platform so that it could support all these services, the ones I just talked about, that are with REL are really good examples. Between a policy, compliance drift, all of these different kinds of services that we're offering, we had to build out that set of capabilities and services in what we're calling sort of the cloud@redhat.com platform. What I'm seeing is that a lot of customers are going through some of these same kinds of thoughts. Like they have a myriad, let's say of applications that are running that they're trying to provide back into their their own company. Different divisions of a company, they have things that are running in the cloud, some things that are running on prem, and they want to start to be able to offer a more cohesive set of services, consolidate some of these, share some of the engineering effort that they have across their various teams. This is exactly the journey that we went through to get to cloud@redhat.com. Finding a surprising number of customers that are actually really interested just in that story, about how we did that. One of the things that we've found is, we've been working with the folks at the open innovation labs within Red Hat. And this is one of the transformation stories that they see constantly as well. We've worked with them and shared this, they're a great resource to help customers kind of think through that problem and get them into a new kind of a platform. But it's quite a journey. We've been really focused on the infrastructure and on prem. Moving to the cloud was a big. But I'll tell you it engineering can move so much faster in a SaaS service than it can with on prem software delivery. It's been remarkable how quickly we could get there. >> Tim, one other thing, if I look at Red Hat, you're a global company, most development organizations are highly distributed to begin with. So many companies today are now having to rapidly figure out how do I manage people that are working from home? How do I live in these environments? From an automation tooling, we'd love to hear any advice you have there, as well as just anything else from your engineering experience in your teams that other people might be able to learn from, as they're dealing with today's landscape. >> To be honest, this is a... We have never seen anything like this in our history, with this kind of pandemic that's happening worldwide. It's shifting everything about business. And it has been challenging just within Red Hat engineering for how we can manage the engineers and their expectations and how difficult it can be to work from home. I have amazing stories from my own engineers. I had an engineer who's in Spain and his wife is a nurse. She's on like 18-hour shifts, the hospital comes back, they have to separate, he's got the kids. And because they don't want them to get infected, it's a really, really difficult working situation for a lot of families out there to try to make it through this. One of the things at Red Hat is, we just have to recognize that it's okay to slow things down a little bit. Let our engineers not feel the pressure that they have to do both childcare and school-at-home and caring for sick relatives or sick family, as well as meet all of your deadlines, it's kind of too much. We've been really... We're trying to be very compassionate with our folks letting them know that we have their back, and it's going to be okay as we try to get ourselves through this ridiculously different time that we've never seen anything like this, like I said. From an engineering perspective, I think work-from-home has been, it's okay for some people. If you have a larger home, I think it's a little easier maybe to find a room that you can go into and do your work. For some, no, if they're in an apartment, or you're sharing with a bunch of friends, it's not your workplace. And it can be really challenging to figure out how to work for eight hours a day with sort of a lot of distractions or just feeling confined and it's just been really difficult for anybody that wants to try to get out, you go a little stir-crazy. The good thing I guess is that engineering is naturally lends itself to being able to be remote and work from home. We have an advantage that way, than other industries, which is great. But it's definitely been really challenging for our teams to be able to cope with this and all we can do is just be really understanding. >> Tim, we appreciate the stories, they're definitely everyone's working through some challenging times. Want to give you the final word as to really takeaways as to what should people be watching? What things should people be going back and looking at from an automation standpoint as they leave Red Hat Summit 2020? >> We're just going to continue to work with the community, work with our partners, get more certified content and continue to scale, the best way that we can for all of our users and our customers. That is the key focus. We want to continue automating and providing all of that flexibility. If you want all 4000 modules and a big download, we certainly are... We're going to continue to give you that option. But if you want to be able to start customizing what you download, maybe only relying on certified content, instead of community content, we're going to give you that option now as well, so that you know what you're running. And with the analytics, we're just scratching the surface here. We're getting some great data. It's helping us to develop new ways of insights into how your systems are running. And that'll get very exciting as we go forward. I know that we've seen like a Forex increase already in the amount of insights attached to REL, which is really great, and for now, at least in the hundreds of customers that are using the AI, I think as we show more value there, you'll get a lot more customers to provide some of their data which will allow us then collectively to come up with some really great analytics to help people become more efficient with your automation. >> Well, Tim Kramer, thank you so much for the updates. And thank you to everything your team's doing. And just a reminder to the audience, of course, these communities not only are important technical resources, but many of them you've made friends with over the years. If you need help, reach out to the community. There are so many good stories that can be found amongst these communities helping each other through these challenging times. Much more coverage from Red Hat Summit 2020. I'm Stu Miniman, and thank you as always for watching theCube. (gentle upbeat music)

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Hi, I'm Stew Minimum And and this is the Cube's coverage of Red Hat Summit 2020 course Digital event This year. We're not together at Mosconi, but we are bringing together many of the speakers thought leaders, customers in this very important ecosystem. Really excited to welcome back to our program. Stephanie Cheers. Who's the vice president and general manager of the Red Hat Enterprise Linux business unit inside of Red Hat. Stephanie. So great to see you have to give you a virtual hug high five year, but you know, always great to see and have you on the program. >>Oh, thank you. So it's great to be here, and this is what together means today. But it's great to be together with you >>again. Here it's limit. >>Yeah, the discussion is you talk on it together apart for for a time we talk in tact. That change is one of the only constants that we have, and there are more changes than ever happening right now. So before we get into kind of your B you talk a little bit about, You know, some of the big changes. There's organizational changes, you know, I know we spoke to you about in 2019 at IBM Think and Red Hat Summit because you've worked for both sides of the equation here, Uh, give us kind of the latest from your standpoint. >>Yes, certainly the leadership changes which have been public now for a couple weeks. Those were a big change >>for for us. I think one of the things that has come through is IBM has really been respecting what red hat is. What? Um, what we do. But also how we do it is very important and valued. And we at red Hat >>believe in it so strongly. We're sticking to what Red Hat does best. Everything is open source. Everything is collaborative. And honestly, I have to say it. It >>feels great as a red Hatter to see Jim in the position he's in at IBM Um, Paul's passion, >>which clearly comes across in his keynotes and >>his passion for how we do have an open source development model. It's great to have them now take over the CEO role for Red hat. So it's it's really exciting times. I think. Last year when we spoke, it was, um it was a bit of a wait and see and see what happens. And I think now the recent announcements really solidify this sort of synergy and partnership that IBM and Red Hat have and what our intentions are in the market. But at Red Hat, we still stay red hat, and we're still driving things the way we always have. And that's great. Feels that >>that that's great. And thank you so much for the update. So when we talk about your business unit that the Red Hat Enterprise, Linux, of course, Rehl, um, you know, I've got a little too much history, you know. I go back when it was, whereas, you know, before well and kind of wash the growth of Linux sto become really, you know, the underlying fabric of so much of what we see out there today for all of businesses, so many companies could not exist if it wasn't for Linux. And in the seven years we've been having the Cube, of course, we've really watched that that moved from Lennox to not only be some of the foundations of what's happening in customer's environments, but also a major piece of cloud and cloud. Native S O. You know, give us that up date as to, you know, here in 2020. You know why? You know Linux has been around for quite a long time, but, you know, it's still is relevant. >>Yeah, so that's it. That's a >>great leader and ties exactly to how we look at well in the red hat sort of entire portfolio. Um, when you look at Lenox of how it evolved, it started out as being a bit of a cheaper alternative to units. But it quickly became, because of the open source way and collaborative way it's developed. It quickly became sort of this springboard for innovation because you have all these incredible innovators collaborating upstream. All of that has fed to a whole different view of what Linux is. Is cloud exists because of Linux is containers are just a different deployment mechanism or Lennox workloads, artificial intelligence. All those APS are built on Linux, so it's become this standardized foundation upon which innovation is done today, And for me, that's the most exciting thing, because it red hat and rail. Our goal is to one. Have it just work right? It has >>to be the standard. And, um well, sometimes that can be misinterpreted. It >>is boring or a commodity. It is anything but a commodity. It's probably one of the most strategic decisions that someone makes. Is which Raoul Distribution? Which Red Hat, which Lennox distribution did they use and that really take real pride that it's built for the enterprise? It's build for security. It's built for resiliency, and all of that build it once deploy anywhere, translates into also using all the innovation, all the container ization capabilities, using it across multiple public clouds. So it's really that combination of having it just work, be the foundation of where you build once and then being able to leverage all the innovation that's coming out of the open source world today. >>Yeah, really interesting points. Stephanie, I think back to when we talked for years about the consumer nation consumers, consumer ization. Excuse me of I t and people thought that therefore, there wouldn't be differentiation, you know, just by white box things and everything will be off the shelf. But if you look at how most companies build things, they really hyper optimize that. I need to build what I need. I need to use the tools that are available, and I need to be able to be agile. You know, I want one of my highlights last year talking to a lot of companies going through their digital transformation and a number of them at Red Hat Summit last year where they talked about both the organization and technology changes that they're making to move faster. And, of course, your portfolio is a big piece of helping them move forward. >>And that's one thing we're seeing that that ability to consume, innovation and get the >>most and extract the most out of what they're running today in their data center. As customers transform and take on this digital transformation, it's not just a technology statement. In most cases, it's an organizational statement as well. And how do you bridge both those and move it forward? It's one thing we focus a lot on right with the open innovation labs, with a lot of customers as well, because it's not just about the technology, it's about the way we work in the way we do things as well. >>Yeah. So, Stephanie, you know, every every year or so I hear it's like, Oh, well, we've got a new way to To the operating system. There was the Jeff just enough operating system for for a while when container ization came out, there was little company named core Os. That was like, Oh, we're going to make a thin version or core OS is now Ah, piece of red hat. Um, so still, with the cloud, there's always, you know, we're going to change the way the operating system it's done. Um, we just love your viewpoint as to, you know, Red Hat has, you know, a few options and kind of a spectrum of offerings. But how do your customers think about the OS these days? And you know, how should we be thinking about rail specifically in that overall spectrum? >>No, it's so that's a great question, too. And we look at >>it as Lennox and Rehl is be one thing that stays the same and helps you get the value out of all the work you've already put in all the development work you've already put in. And make sure that that translates to the future, where everything is changing, how you deploy where you deploy what you deploy. All of that may change, but if you want to get the value out of the work in the development that has been done yesterday, you need something to stay the same. In our view, that's real. We build it with um in mind for the enterprise along lifecycle security support. We build all of that into it so that when you build on a rail monorail kernel, you can take that. If you want to deploy it in a container, you can deploy on Rehl itself. Or if you need orchestration, you can deploy it on open shift. And that's part of the reason why you mentioned Core OS. So we now have a rail core. OS is within open shift 4.0, on beyond, of course. But what we did was we tailor down what is. In reality, it's the same packages. It's the same certification, security, all of that work that we put in. We take the core OS piece of it, what's essential and really optimized for open shift. We build that into an immutable image, and it goes out as part of open shift. It's not available separately because it's really tailored. What we pick the life cycle is all matching open shift, >>and what that does >>is provide you on open shift experience. That's easy to update fully across the board, all the way down to the kernel. But you know, it's the same Lennox that you have in rail, >>and it's that consistency >>of technology that we really strive for. Um, same thing in public Cloud. So when you build an image on Prem on REL, you can take that image up into the public cloud. And no, it's the same level of security and it just will work, you know, part of part of my team. And we take a lot of pride in the fact that it will just work on. And while that >>may not sound super exciting, particularly in days >>like like right now, being dependable and being reliable and knowing that it's secure, all of that is really important when you run your business that those those features or anything but commoditized >>Well, yeah, I think one of the real volumes that customers see with real specifically is there's so much change going on there, and you look at the Linux community, you look at what open shifts doing in the Kubernetes community. There's so much coaches going on red hat packages that make sure that you don't need to think about the almost chaos that's going out there in all of those communities. But you packaged those together. So Stephanie rarely was, of course, one of the highlights of last year's Red Hat Summit. So we'd love to hear you know, if you've got any good customer stories, really, the momentum of relate as you've seen it, you roll out around the world as and then we'll talk about the new updates. You have this. >>Yeah, great. So Rehl eight was a big deal for us last year, as you remember, and partly because not >>only all the features and functions, of course, which we put into it, but also because we really wanted to reposition what the value of an operating system is within a data center and within their innovation future. So we really focus all the features and functions into two buckets. One is about how do we help you with the operating system? Run your business better, more efficiently If the most out of the systems you have in the critical workloads that you run today and how do we use the operating system to help you bridge into the next level of innovation? What's coming down the pipeline? Things like containers. >>And we really wanted to >>make sure that, as we see you know, most customers are looking to how they digitally transform. But of course, no one has the freedom to throw away everything they've done in the past. They want to build upon that and get value out of it. So we really focused on balancing those two things now, as we look at. In fact, one of the commitments we made because we heard it from customers was they wanted a more predictable deployment of our minor releases and our major releases. And we committed, um, at the REHL eight launch that we would be delivery minor releases every six months, major releases every three years, and we have held to that. We delivered 816 months after we delivered eight. And now you saw last week we delivered eight dot too. Um, this is what it means for us to stand by our world and be dependable as an operating system. And the beauty of the subscription with well is that if you're a customer and you're running REL seven, particularly in times right now, it's It's not that easy to get into your data center, perhaps. And so if you don't choose to update to eight now, you can stay on seven until that time works. That's to me. That's part of the beauty and the flexibility of the subscription model. We have course want to continue to bring your new capabilities and new features. But the subscription Our goal is to have a value subscription that you can you can get the most value from No matter when you decide to upgrade or no forward with, uh, with a different releases, we have >>Well, you can go. And congratulations on keeping the releases going on schedule. One of the nice things about open source is we can see the roadmap out there. You've made this Ah, this promise and you're keeping to it. So ah is you said the announcements we made has been talked about in the keynote. So give us a couple of highlights. Says what people to be looking at and looking to learn more when they dig into a thought to >>Yeah, great. So we really wanted to stick with a few key >>messages with it, and they do really tie to How do we help you run your business? And how do we help you grow your business? It's one thing that we announced and what we pivoted to, um, with the eight dot io is we >>really moved to? How do we How do we >>deliver what we called an intelligent OS, which means an OS that helps you bridge the gap and brings more value to you in your data center than you got before? One of the key aspects to this was adding in the capability of red hat insights, and we added insights capability into every single rail subscription that is under current support. So whether or not you moved to relate whether you have real seven, if you have a supported version of real six, all of those had insights added to it, and what insights is is a as a service on cloud at red hat dot com and link up your servers, and >>it will give you insight >>into operational capability. Is it configured correctly is it could be optimized for better performance. Where are you on your C V E updates and what it does is take all that knowledge that Red Hat has from all the support cases and things that we're seeing what's happening in the industry, what we're seeing other customers have, and we can even proactively help customers. The feedback on this capability has been huge. In fact, you'll see in the announcement last week we've added a lot of new capabilities into this specifically For that reason we've had customers, you know, it's like having it's like having more ops people on my team because I'm getting this input in directly from Red Hat for things to look at. And so that, to me, was probably one of the key aspects that, as we look from going to eight into eight dot too, how do we build up that capability? And of course, last week you saw we added a lot to that, and I think now more than ever, we want to make sure that everyone who has a real subscription is getting the most value out of that and I think insights is one of the places where if you have a subscription and, um, you can value or you can get more value from operational help, insights is a place where we want to help you. Um, we everything we had prior we have now bucket sized into a capability and insights called advisor is really about performance, stability and security and doing an analysis for you. We've added a new capabilities around vulnerability, Right. How do you re mediate common vulnerabilities and exposures, compliance aspect, patch aspect policies and drift? Um, kind of all of those we've now bucket it in into that insights capability. So this friends a lot more value to something that we have already seen. Customers say, You know, we didn't expect to get this amount of input and continuous growth because we constantly add new new rules into that engine. And so you know what? What we what we knew yesterday will be what we know tomorrow, and we look forward to sharing with that with everyone >>who has a subscription. So this is >>a place where I think it's ah, it's an important place for folks to look, particularly now because operational efficiency is really key. And security is really we have a lot of capabilities in both. What? Yes, Please, >>please, please, go ahead. Now, >>one other aspect on that that I wanted to mention >>was we also added a capability called subscription watch and subscription Watch helps you get a very simple, clean view of all the subscriptions you have and where they're running. And that was one thing that we saw. Customers say there was friction. And how do I know where my entitlements are? How I'm using them across my entire enterprise Corruption watch can help with that. So, um, this sort of cloud dot red hat dot com capability that we can assist with and is already part of your subscription. These are the kinds of things that we really want to help augment this to make Really intelligent os for the enterprise. >>Yeah. Stuff Stephanie. The comment I was gonna make is there's certain shows that I go to that every year. You go to it, You say Okay, it's a little bit bigger. They announce something. They made some progress on it. What has impressed me most about going to the red Hat show year after year is really the the growth of the of the portfolio, if you will. So when I first started going to it, it was, you know, a lot of the people there were, you know, the hard core Linux people. Um And then, you know, there's some storage people, some networking people is cloud containers really grew. It really blossomed into this really robust ecosystem. Oh, and growth there. So would love just to get your viewpoint on, you know, the skill set because, you know, I'm sure there's plenty of companies out there that are like, Well, you know, I've got some people that are, you know, my limits people, and they do things that aren't there. But, you know, how do you see kind of the skill set and what what Red Hat's doing really permeating more and more of, of companies, day to day activity. >>I think one of the things that I'm >>most proud of is even since last year's all the deeper collaborations we have between the various product lines. Certainly we'll talk with Joe Fitzgerald, and he and I work together very closely. Capabilities like insights. How do we add answerable capabilities directly into real. And what that does is really help. I think in any customer today, skills is probably one of the biggest concerns that they have. How do they grow those skills? How do they help folks grow and learn more and progress into the innovation areas? But clearly they still need their their mission critical applications to run and how do they span that? And I think what we're really trying to do is be able to bring the strength of the portfolio together to help a customer have more flexibility in how they leverage their skills and how they grow their skills. >>Because I think coming back to >>that statement that that you made earlier it's not just about technology. It's about how, if >>you really want to be, have agile, it's about >>how a company has organized. And I think we're hoping that we bring together the strength of the portfolio so that a customer is able todo leverage their organization and leverage their skills and the best way possible. I think another place where we worked hard on eight dot too. Some similar lines of bridging the portfolio was, you know, we announced back in eight dot io. We were putting container ization tools directly in Terrell with build a pod made in scope e 08 dot too. We brought in the newest versions of Scope EO and Build Up. In fact, in tech preview, you get containerized versions of those, and so we're continuing to add. What we are seeing is the container ization is a journey for customers. Many customers just want to deploy a single container on a server. Or they were. They want to deploy a single container in a VM Um, they're not ready for orchestration. We wanted to put the tools in so that a customer could do that on REHL. Get started, get those containers deployed on REHL. Put those tools directly, and we added it to old protocol, which is a tool built for security. It brings that security of SC Lennox and brings that up and adds value at the container level. It's those kinds of things as you see the bridge from well into open shift. How do we help a customer rich? That skill journey as well along that path and I think right now in kubernetes and Containers skills is a is a big, big area of focus, so the more we can help ease that across the portfolio and bring those things together is really important. And I know we're working very closely with the chefs in the, um and the team there in order to help bridge that. >>Excellent. Stephanie, I just want to give you the last word. We talked a lot about the ongoing journey that customers are going through. So give us your final take away as to how customers should be thinking about red hat in general and role specifically as their journey goes forward. >>I think I think one of the things >>we're very proud of here at Red Hat is that we always, particularly in the open source communities with our customers, with our partners, we want to roll up our sleeves and help, and that's we want. So, developer, we wanna work upstream with you. It's one of the things we're very proud of, and now, particularly in this time it's We want to make sure that folks understand we're here to help, and we want to make sure that you're getting the most out of the subscriptions you have, Um, and we help. We help you on that journey both to get the most out of you can out of your data center today. But also be ready for the innovation that you want to consume going forward. And we're collectively working across red Hat in order to make that happen. But it's, um >>even though this is different and it's there the virtual Experience edition of Red Hat Summit. It's >>great to be together and be able to share the whole message. >>Well, Stephanie, the open source community is definitely used to collaborating remotely. So thank you so much for joining us. It's a pleasure to see you. And we would hope to talk again soon. >>Great to see you too. Thank you for the time. >>Alright. You're watching the Cube's coverage of Red Hat Summit 2020 digitally with remote guests from around the globe. Instrument a man and thank you for watching the Cube. >>Yeah, yeah, yeah.