(upbeat music) >> We are back, approaching the finish line here at Supercomputing 22, our last interview of the day, our last interview of the show. And I have to say Dave Nicholson, my co-host, My name is Paul Gillin. I've been attending trade shows for 40 years Dave, I've never been to one like this. The type of people who are here, the type of problems they're solving, what they talk about, the trade shows are typically, they're so speeds and feeds. They're so financial, they're so ROI, they all sound the same after a while. This is truly a different event. Do you get that sense? >> A hundred percent. Now, I've been attending trade shows for 10 years since I was 19, in other words, so I don't have necessarily your depth. No, but seriously, Paul, totally, completely, completely different than any other conference. First of all, there's the absolute allure of looking at the latest and greatest, coolest stuff. I mean, when you have NASA lecturing on things when you have Lawrence Livermore Labs that we're going to be talking to here in a second it's a completely different story. You have all of the academics you have students who are in competition and also interviewing with organizations. It's phenomenal. I've had chills a lot this week. >> And I guess our last two guests sort of represent that cross section. Armando Acosta, director of HPC Solutions, High Performance Solutions at Dell. And Matt Leininger, who is the HPC Strategist at Lawrence Livermore National Laboratory. Now, there is perhaps, I don't know you can correct me on this, but perhaps no institution in the world that uses more computing cycles than Lawrence Livermore National Laboratory and is always on the leading edge of what's going on in Supercomputing. And so we want to talk to both of you about that. Thank you. Thank you for joining us today. >> Sure, glad to be here. >> For having us. >> Let's start with you, Armando. Well, let's talk about the juxtaposition of the two of you. I would not have thought of LLNL as being a Dell reference account in the past. Tell us about the background of your relationship and what you're providing to the laboratory. >> Yeah, so we're really excited to be working with Lawrence Livermore, working with Matt. But actually this process started about two years ago. So we started looking at essentially what was coming down the pipeline. You know, what were the customer requirements. What did we need in order to make Matt successful. And so the beauty of this project is that we've been talking about this for two years, and now it's finally coming to fruition. And now we're actually delivering systems and delivering racks of systems. But what I really appreciate is Matt coming to us, us working together for two years and really trying to understand what are the requirements, what's the schedule, what do we need to hit in order to make them successful >> At Lawrence Livermore, what drives your computing requirements I guess? You're working on some very, very big problems but a lot of very complex problems. How do you decide what you need to procure to address them? >> Well, that's a difficult challenge. I mean, our mission is a national security mission dealing with making sure that we do our part to provide the high performance computing capabilities to the US Department of Energy's National Nuclear Security Administration. We do that through the Advanced Simulation computing program. Its goal is to provide that computing power to make sure that the US nuclear rep of the stockpile is safe, secure, and effective. So how we go about doing that? There's a lot of work involved. We have multiple platform lines that we accomplish that goal with. One of them is the advanced technology systems. Those are the ones you've heard about a lot, they're pushing towards exit scale, the GPU technologies incorporated into those. We also have a second line, a platform line, called the Commodity Technology Systems. That's where right now we're partnering with Dell on the latest generation of those. Those systems are a little more conservative, they're right now CPU only driven but they're also intended to be the everyday work horses. So those are the first systems our users get on. It's very easy for them to get their applications up and running. They're the first things they use usually on a day to day basis. They run a lot of small to medium size jobs that you need to do to figure out how to most effectively use what workloads you need to move to the even larger systems to accomplish our mission goals. >> The workhorses. >> Yeah. >> What have you seen here these last few days of the show, what excites you? What are the most interesting things you've seen? >> There's all kinds of things that are interesting. Probably most interesting ones I can't talk about in public, unfortunately, 'cause of NDA agreements, of course. But it's always exciting to be here at Supercomputing. It's always exciting to see the products that we've been working with industry and co-designing with them on for, you know, several years before the public actually sees them. That's always an exciting part of the conference as well specifically with CTS-2, it's exciting. As was mentioned before, I've been working with Dell for nearly two years on this, but the systems first started being delivered this past August. And so we're just taking the initial deliveries of those. We've deployed, you know, roughly about 1600 nodes now but that'll ramp up to over 6,000 nodes over the next three or four months. >> So how does this work intersect with Sandia and Los Alamos? Explain to us the relationship there. >> Right, so those three laboratories are the laboratories under the National Nuclear Security Administration. We partner together on CTS. So the architectures, as you were asking, how do we define these things, it's the labs coming together. Those three laboratories we define what we need for that architecture. We have a joint procurement that is run out of Livermore but then the systems are deployed at all three laboratories. And then they serve the programs that I mentioned for each laboratory as well. >> I've worked in this space for a very long time you know I've worked with agencies where the closest I got to anything they were actually doing was the sort of guest suite outside the secure area. And sometimes there are challenges when you're communicating, it's like you have a partner like Dell who has all of these things to offer, all of these ideas. You have requirements, but maybe you can't share 100% of what you need to do. How do you navigate that? Who makes the decision about what can be revealed in these conversations? You talk about NDA in terms of what's been shared with you, you may be limited in terms of what you can share with vendors. Does that cause inefficiency? >> To some degree. I mean, we do a good job within the NSA of understanding what our applications need and then mapping that to technical requirements that we can talk about with vendors. We also have kind of in between that we've done this for many years. A recent example is of course with the exit scale computing program and some things it's doing creating proxy apps or mini apps that are smaller versions of some of the things that we are important to us. Some application areas are important to us, hydrodynamics, material science, things like that. And so we can collaborate with vendors on those proxy apps to co-design systems and tweak the architectures. In fact, we've done a little bit that with CTS-2, not as much in CTS as maybe in the ATS platforms but that kind of general idea of how we collaborate through these proxy applications is something we've used across platforms. >> Now is Dell one of your co-design partners? >> In CTS-2 absolutely, yep. >> And how, what aspects of CTS-2 are you working on with Dell? >> Well, the architecture itself was the first, you know thing we worked with them on, we had a procurement come out, you know they bid an architecture on that. We had worked with them, you know but previously on our requirements, understanding what our requirements are. But that architecture today is based on the fourth generation Intel Xeon that you've heard a lot about at the conference. We are one of the first customers to get those systems in. All the systems are interconnected together with the Cornell Network's Omni-Path Network that we've used before and are very excited about as well. And we build up from there. The systems get integrated in by the operations teams at the laboratory. They get integrated into our production computing environment. Dell is really responsible, you know for designing these systems and delivering to the laboratories. The laboratories then work with Dell. We have a software stack that we provide on top of that called TOSS, for Tri-Lab Operating System. It's based on Redhead Enterprise Linux. But the goal there is that it allows us, a common user environment, a common simulation environment across not only CTS-2, but maybe older systems we have and even the larger systems that we'll be deploying as well. So from a user perspective they see a common user interface, a common environment across all the different platforms that they use at Livermore and the other laboratories. >> And Armando, what does Dell get out of the co-design arrangement with the lab? >> Well, we get to make sure that they're successful. But the other big thing that we want to do, is typically when you think about Dell and HPC, a lot of people don't make that connection together. And so what we're trying to do is make sure that, you know they know that, hey, whether you're a work group customer at the smallest end or a super computer customer at the highest end, Dell wants to make sure that we have the right setup portfolio to match any needs across this. But what we were really excited about this, this is kind of our, you know big CTS-2 first thing we've done together. And so, you know, hopefully this has been successful. We've made Matt happy and we look forward to the future what we can do with bigger and bigger things. >> So will the labs be okay with Dell coming up with a marketing campaign that said something like, "We can't confirm that alien technology is being reverse engineered." >> Yeah, that would fly. >> I mean that would be right, right? And I have to ask you the question directly and the way you can answer it is by smiling like you're thinking, what a stupid question. Are you reverse engineering alien technology at the labs? >> Yeah, you'd have to suck the PR office. >> Okay, okay. (all laughing) >> Good answer. >> No, but it is fascinating because to a degree it's like you could say, yeah, we're working together but if you really want to dig into it, it's like, "Well I kind of can't tell you exactly how some of this stuff is." Do you consider anything that you do from a technology perspective, not what you're doing with it, but the actual stack, do you try to design proprietary things into the stack or do you say, "No, no, no, we're going to go with standards and then what we do with it is proprietary and secret."? >> Yeah, it's more the latter. >> Is the latter? Yeah, yeah, yeah. So you're not going to try to reverse engineer the industry? >> No, no. We want the solutions that we develop to enhance the industry to be able to apply to a broader market so that we can, you know, gain from the volume of that market, the lower cost that they would enable, right? If we go off and develop more and more customized solutions that can be extraordinarily expensive. And so we we're really looking to leverage the wider market, but do what we can to influence that, to develop key technologies that we and others need that can enable us in the high forms computing space. >> We were talking with Satish Iyer from Dell earlier about validated designs, Dell's reference designs for for pharma and for manufacturing, in HPC are you seeing that HPC, Armando, and is coming together traditionally and more of an academic research discipline beginning to come together with commercial applications? And are these two markets beginning to blend? >> Yeah, I mean so here's what's happening, is you have this convergence of HPC, AI and data analytics. And so when you have that combination of those three workloads they're applicable across many vertical markets, right? Whether it's financial services, whether it's life science, government and research. But what's interesting, and Matt won't brag about, but a lot of stuff that happens in the DoE labs trickles down to the enterprise space, trickles down to the commercial space because these guys know how to do it at scale, they know how to do it efficiently and they know how to hit the mark. And so a lot of customers say, "Hey we want what CTS-2 does," right? And so it's very interesting. The way I love it is their process the way they do the RFP process. Matt talked about the benchmarks and helping us understand, hey here's kind of the mark you have to hit. And then at the same time, you know if we make them successful then obviously it's better for all of us, right? You know, I want to secure nuclear stock pile so I hope everybody else does as well. >> The software stack you mentioned, I think Tia? >> TOSS. >> TOSS. >> Yeah. >> How did that come about? Why did you feel the need to develop your own software stack? >> It originated back, you know, even 20 years ago when we first started building Linux clusters when that was a crazy idea. Livermore and other laboratories were really the first to start doing that and then push them to larger and larger scales. And it was key to have Linux running on that at the time. And so we had the. >> So 20 years ago you knew you wanted to run on Linux? >> Was 20 years ago, yeah, yeah. And we started doing that but we needed a way to have a version of Linux that we could partner with someone on that would do, you know, the support, you know, just like you get from an EoS vendor, right? Security support and other things. But then layer on top of that, all the HPC stuff you need either to run the system, to set up the system, to support our user base. And that evolved into to TOSS which is the Tri-Lab Operating System. Now it's based on the latest version of Redhead Enterprise Linux, as I mentioned before, with all the other HPC magic, so to speak and all that HPC magic is open source things. It's not stuff, it may be things that we develop but it's nothing closed source. So all that's there we run it across all these different environments as I mentioned before. And it really originated back in the early days of, you know, Beowulf clusters, Linux clusters, as just needing something that we can use to run on multiple systems and start creating that common environment at Livermore and then eventually the other laboratories. >> How is a company like Dell, able to benefit from the open source work that's coming out of the labs? >> Well, when you look at the open source, I mean open source is good for everybody, right? Because if you make a open source tool available then people start essentially using that tool. And so if we can make that open source tool more robust and get more people using it, it gets more enterprise ready. And so with that, you know, we're all about open source we're all about standards and really about raising all boats 'cause that's what open source is all about. >> And with that, we are out of time. This is our 28th interview of SC22 and you're taking us out on a high note. Armando Acosta, director of HPC Solutions at Dell. Matt Leininger, HPC Strategist, Lawrence Livermore National Laboratories. Great discussion. Hopefully it was a good show for you. Fascinating show for us and thanks for being with us today. >> Thank you very much. >> Thank you for having us >> Dave it's been a pleasure. >> Absolutely. >> Hope we'll be back next year. >> Can't believe, went by fast. Absolutely at SC23. >> We hope you'll be back next year. This is Paul Gillin. That's a wrap, with Dave Nicholson for theCUBE. See here in next time. (soft upbear music)

>>The queue presents Coon and cloud native con Europe, 2022, brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Valencia Spain and Coon cloud native con Europe, 2022. I'm Keith towns, along with Paul Gillon, senior editor, enterprise architecture, Silicon angle. We are going to talk to some amazing folks, especially in today's segment. Paul there's a lot of companies here, like what what's been the, the consistent theme you've heard so far in the show. >>Well, you know, one thing that's different from this show, it seems to me than others I've attended is it's all around open source. We're not seeing a lot of companies bringing new proprietary technology to market. We are seeing them try to piece together, open source components with some kind of, perhaps there's a proprietary element to it, but to create some kind of a, a common management interface or control plane, and that's quite different from what I think we've seen in the past and open source business models have been difficult to make work historically. And these companies are all taking their, their own approaches to it. But I think the, the degree to which this, the people here of coalesced around the importance of open source is building blocks to the future of, of applications is something I've not seen quite this way before. >>Well, with our current segment guests, we're gonna go deep into kind of these challenges and how enterprises are addressing, and their partners are addressing with those challenges we have with us, a flower head of cloud native HCL technologies. We'll get into how a system integrator is helping with this transition to Ramon neon, senior product manager, redhead. Welcome to the show. You're now cute. Alum. Welcome. >>Thanks for having us. >>So we're gonna get right off, off the bat. We're gonna talk about this. What are some of the trends you're seeing when it comes to application migration? You've done, I'm assuming at this point, thousands of them, what are some of the common trends? >>Well, it's a very good question. And clearly a C we've helped thousands of clients move tens of thousands of applications to what we would call a cloud native, you know, environment. I think the overwhelming trend that we're seeing of course is clients realize it's a particularly complex, sophisticated journey. It requires a certain set of skills and capability clients increasingly asking us for anything that we can do to simplify and accelerate the journey, cuz what's really important to clients. If you're on a transformation journey to cloud is you wanna see some value very quickly. So I don't wanna wait three to five years to transform my applications portfolio. If you can do something in three to five days, that would be perfect. Thank you. >>Well, three to five days, that sounds more akin to when we were doing P to V or V to V migrations, I'm sure HCL is at this point done in the millions of those types of migrations. What are some of the challenges or the nuance in doing a traditional migration from a traditional MI monolithic application to a cloud native? >>Well, it's another good question. Of course you notice that there's a general trend in the industry. Clients don't really want to lift and shift anymore. Lift and shift doesn't really bring any transformational value to my, to my company. So clients are looking for increasingly what we could call cloud native modernization. I want my applications to really take advantage of the cloud native environment. They need to be elastic and kind of more robust than maybe before now in particular, I think a lot of clients have realized that this state of Nirvana, which was we're gonna modernize everything to be a cloud native microservices based application. That is a tremendous journey, but no client really has the time patient or resources to fully refactor or rearchitect all of their applications. They're looking for more immediate kind of impact. So a key trend that we've seen of course is clients still want to refactor and modernize applications, but they're focusing those resources on those applications that will bring greater impact to their business. >>What they now see as a better replacement for lift and shift is probably what we would call replatforming, where they want all of the advantages of a cloud native environment, but they haven't necessarily got the time to modernize the code base. They wanna refactor to Kubernetes and re replatform to Kubernetes in particular, and they want us to take them there quickly. And that's why, for example, this week at cuon eight sellers announced a new set of tools called KMP based on conveyor, an open source project supported by red hat. And the key attraction of KMP is it lets me replatform my applications to Kubernetes immediately, right? Within two or three minutes, I can bring an application from a legacy platform directly onto Kubernetes and I can take it straight into production. That's the kind of acceleration that clients are looking for today. Isn't >>That just a form of lift and shift though? >>Well, no lift and shift typically of course, was moving virtual machines from one place to another. You know, the focus of Kubernetes of course is containerization of solutions. And it's not just about containerizing the solution and movement. It it's the DevOps tool chain around the solution as well. And of course, when I take that application into production in a Kubernetes based environment, I'm expecting to operate it in a different way as well. So that's where we see tremendous focus on what we would call cloud native operations clients expecting to use practices like site reliability engineering, to run these replatformed applications in a different way to, >>It sounds like you're saying, I mean, replatforming has been a, a spectrum of options. I think Gartner has seven different types of platforming. Are you seeing clients take more mature attitude now to replatforming? Are they looking more carefully at the characteristics of their legacy applications and, and try to try to make maybe more nuanced choices about what to replatform, what to just leave >>Alone? I think clients and I I'm sure Ramon's got some comments on this too, but clients have a lot more insight now in terms of what works for them. They they've realized that this, this promise of maybe a microservices based applications estate is a good one, but I can't do that for every application. If I am a large enterprise with several thousand applications in my portfolio, I can't refactor everything to become microservices based. So clients see replatforming possibly it's a middle ground. I, I get a lot of the advantages from a cloud native environment. My applications are inherently more efficient, hopefully a lot more performance. >>Yeah. It's, it's a matter of software delivery performance. Yeah. So legacy workloads will definitely benefit from being brought into Kubernetes in the software delivery per performance department. So it's a matter of somehow revamping your, your legacy applications and getting the benefits in, in life's application, life cycle management, a full tolerance and all that stuff. It's about leveraging the, what Kubernetes offers. >>When you say bringing legacy applications into Kubernetes. It's not that simple, right? I mean, what's involved in doing that. >>It, it, isn't, it's just a matter of taking a holistic view at your application portfolio and understanding the nuance sets of each application type within your organization and trying to come up with a suitable migration strategy for each one of these application types. And for that, what we're trying to do is provide a series of standardized tools and methodologies from a community perspective, we created this conveyor community. It, it was kick started by red hat and IBM, but we are trying to bring as many vendors and GSI as possible to try to set up these standards to make these road towards Kubernetes as easy as >>Possible. So we've done a little bit of app modernization in the CTO advisor hybrid infrastructure. And one of the things that we've found is there's plenty of Avan advantages. If I take a monolithic application that has that I've traditionally had to scale off to game performance, I can take selective parts of that, and now I can add autoscaling to it. Exactly. However, as I look at a landscape Allen of thousands of applications, I need to dedicate developer resources to get that done in my traditional environment. But my traditional environment is busy building new. My traditional or my developers are building new applications and new capabilities. I just don't have the resources to do that. How does HCL and red hat team together to kind of fast track that capability? >>Well, I'll comment on two things in particular, actually the, the first thing when it comes to skilling, I think the thing that's really surprised us at HCL is so many of our clients around the world have said, we are desperately short of skills. We cannot hire ourselves out of this problem. We need to get our existing developer community reskilled around platforms like OpenShift, conveyor, and other projects too. So the first thing that's happened to us at eight seal is we've been incredibly busy undertaken, probably what we would call developer workforce modernization, right? Where we have to help the client reskill their entire technical and developer community to give them the skills, right. So we will help the clients develop a community, build the cloud native understanding, help them understand how to modernize tools for example, or applications. But the second thing I mention is, and this comes back to a comment the Ram made around around conveyor. >>It's been really encouraging to see the open source community, start to invest in building the supporting frameworks around my kind of modernization journey, because if I'm a developer that's reskilling and I'm attempting to maybe modernize an application, being able to dip into an opensource project, I mean, a good example would be tackled part of the conveyor project. Exactly. You now have open source based tools that will help you analyze your applications. They will go into the source code and they will give the developer guidance in terms of what would be effective treatments to undertake. So perhaps a development team that are new to this modernization journey, they would benefit from a project like conveyor, for example, exactly because I need to know where can I safely modernize my application now for experience organizations like HCL that comes naturally to us, but for people who are just starting this journey, if I can take an open source tool like tackle or the rest of conveyor, for example, and use that to accelerate my journey, it takes a lot of pressure off, off my organization, but it also accelerates the journey too. And >>It's not just a matter of, of tooling. We we're also, opensourcing the, the modernization methodology that we've been using in red hat consulting for years. So this whole conveyor communities, it's all about knowledge sharing on one hand and building a set of tools together based on that knowledge that we are sharing to make it as easy as possible. >>And what role does red hat play in all that, I mean is your, your, you you've carved out this position for yourself as the, as the true open source company. Is that, does that position you for a leadership role in helping or companies make this >>Transition? I wouldn't say we should be leading the whole thing. We, we kick started it, but we want to get other vendors on board for this thing. One cool thing about the Camra community is that IBM is opensourcing a lot of their IP. So IBM research is on board. In this thing, we have some really crazy stuff related to a AI being applied to application analysis. We have some machine learning in place. We have very cool stuff that has been sitting on a, on a corner in IBM research for quite some years that now it's being open sourced and integrated in a unified user experience to streamline the modernization process as much as possible. >>So let's talk about the elephant of the room. HCL was leading the conversation around cloud Foundry circa five plus years ago. And as customers are thinking about their journey to cloud native, how should they think about that cloud Foundry to cloud native or Kubernetes replatform? >>Well with within the cloud Foundry community, we've, we've been quite staunched supporters of Kubernetes for quite some time, right? It's, it's quite a, a stated intent of the cloud Foundry foundation to, to move across to Kubernetes platform right now that is a significant engineering journey for cloud Foundry to take. Now we're in this position where a lot of large users of cloud Foundry have a certain urgency to their journey. They, they want to consolidate on a single Kubernetes based infrastructure. We, we see a lot of traction around OpenShift, for example, from red hat in terms of its market leadership. So a lot of clients are saying we would like to consolidate all of our platforms around a single kind of Kubernetes vendor, whether that's red hat or anyone else, you know, quite frankly. So what HCL is doing right now with the tools and the solutions we've announced this week is we're simply accelerating that journey for clients. If I've got a large installed base of applications running in my cloud Foundry environment, and I've also started to invest in standardize on Kubernetes place platforms like OpenShift, most clients would see it as quite a sensible choice to now try and consolidate those two environments into one. And that's simply what we're doing at HCL. We're making it very, very easy. In fact, we fully automated the journey so I can move all of my applications from cloud Foundry into for example, OpenShift pretty much immediately, and it just simplifies the entire journey. >>So the, as we start to wrap up the segment, I like to know customer stories. What, what, how customers either surprised or challenged when they get into, even with the help of an ACL in redhead, why are they seeing the most difficult parts of their migrations? >>Well, my, my simple comment would be maybe complexity, right? And the, the associated requirement for skilled people to undertake this modernization work, right? We spoke about this, of course, in terms of clients now are a lot more realistic. They understand that their ambition now needs to be somewhat tempered by their ability to sort of drive modernization quickly. So we see a lot of clients when they look at their very large global portfolios of applications, they're trying to invest their resources in the higher priority applications, the revenue generative applications in particular, but they have to bring everything else with them as well. Now, a common kind of separation point was we see a lot of clients who might say I'm gonna properly modernize and refactor, maybe five to 10% of my portfolio, but the other 90% also needs to come on the journey as well. And that's really where replatforming in particular kicks in. So, so the key trend again, is, is clients send to us, I've gotta take the entire journey. All right, I've got the resources and the skills to really focus on this much of my application base. Can someone simplify the overall journey so I can afford to bring everything on a cloud native journey? >>So the key to success here is having a holistic view at the application portfolio, segmenting the application portfolio in different application types and ordering the, the priorities of these application types and come up with suitable migration strategies for each one of them is >>Really necessary to move everything though. >>Not necessarily, no. Yeah. Or not necessarily. Yeah, absolutely not everything, but it would make sense. As we were saying before, it will definitely move, make sense to move legacy applications towards Kubernetes, to leverage all the software delivery. >>That's, that's a big project, right? >>It is. >>If you're gonna restructure the application around eight API and microservices, >>That it should be taken the way I've seen organizations succeeding the most in these road towards cloud native and Kubernetes in general is trying to address the whole portfolio. Maybe not move everything, but try to have this holistic view and not leave anything behind. Because if you try to do this isolated initiatives of bringing these or that application in, in isolation, you're Def you, you will miss part of the picture and you might be doomed to fail >>There. Yeah. It's been my experience that if you don't have a plan to migrate your applications to a cloud native operating model, then you're doomed to follow lift and shift examples to the public cloud. Yeah. Whether you're going to any other clouds, if you don't make that, that operational transition. Last question on operational transition, we've talked a lot about the replatforming process itself. What about day two at the I've landed to the cloud? What are some of the top considerations for, for compliance op observability? Just making sure my apps stay up in transitioning my workforce to that model. >>I think the over, you know, the overarching trend or theme that, that I see is clients now are, are asking for what I would call cloud native operations. Now in particular, there's a very solid theme around what we would call reliability engineering. So think about site reliability, engineering, SRE platform, reliability engineering, PR E. These are the dominant topics that clients now want to engage HCL on in particular, because the point you make is a valid one. I've modernized my application. Now I need to modernize the way that I operate the application in production. Otherwise I won't see those benefits. So that general theme of SRE is keeping us really busy. We're busy, re-skilling all of those operations teams around the world as well, because they need to know how to run these environments appropriately >>Too. And also being able to measure your progress while your transitioning is important. And that's one of the concerns that we are addressing as well in the community with a called polars to, to measure and to effectively measure the software delivery performance of, of the organization after the transition has been done. >>And this is a really good point by the way, cuz most, most people think it's a bit of a black art. How do I understand how I modernize my application? How do I understand how I've improved my kind of value chain around software creation and many people thought you needed to bring in very expensive consultants to advise you on these, on these black lives? No, >>Definitely >>Not. But in open source projects like conveyor from, from red hat, the availability of these tools available on an open source model means exactly any engineer, any developer can get these tools off the shelf and get that immediate benefit. >>Well, a flower head of creative labs at HCL at Ramon neon, senior product manager, redhead. Thank you for joining the Q you now cube alum. You'll have a nice profile like the profile pictures on here. Awesome. Absolutely. Thank you. From Valencia Spain. I'm Keith towns, along with Paul Gillon and you're watching the cue, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Valencia Spain and Coon cloud native con Europe, 2022. I'm Keith towns, along with Paul Gillon, senior editor, enterprise architecture and Silicon angle. We are going to talk to some amazing folks, especially in today's segment. Paul, uh, there's a lot of companies here, like what what's been the, the consistent theme you've heard so far in the show. >>Well, you know, one thing that's different from this show, it seems to me than others I've attended is it's all around open source. We're not seeing a lot of companies bringing new proprietary technology to market. We are seeing them try to piece together, open source components with some kind of, perhaps there's a proprietary element to it, but to create some kind of a, a common management interface or control plane, and that's quite different from what I think we've seen in the past open source business models have been difficult to make work historically. Uh, and these companies are all taking their, their own approaches to it. But I think the, the degree to which this, the people here of coalesced around the importance of open source is building blocks to the future of, of applications is something I've not seen quite this way before. >>Well, with our current segment, guess we're gonna go deep into kind of these challenges and how enterprises are addressing, and their partners are addressing with those challenges we have with us, a flower head of cloud native HCL technologies. We'll get into how a system integrator is helping with this transition to Ramon neon, senior product manager, redhead. Welcome to the show. You're now cube alum. Welcome. Thanks for having us. So we're gonna get right off, uh, off the bat. We're gonna talk about this. What are some of the trends you're seeing when it comes to application migration? You've done, I'm assuming at this point, thousands of them, what are some of the common trends? >>Well, it's a very good question. And clearly ACL we've helped thousands of clients move tens of thousands of applications to what we would call a cloud native, um, you know, environment. I think the overwhelming trend that we're seeing of course is clients realize it's a particularly complex, sophisticated journey. It requires a certain set of skills and capability clients increasingly us for anything that we can do to simplify and accelerate the journey, cuz what's really important to clients. If you're on a transformation journey to cloud is you wanna see some value very quickly. So I don't wanna wait three to five years to transform my applications portfolio. If you can do something in three to five days, that would be perfect. Thank you. >>Well, three to five days, that sounds more akin to when we were doing, uh, P to V or V to V migrations. I'm sure. Uh, HCL is at this point done in the millions of those types of migrations. What are some of the challenges or the nuance in doing a traditional migration from a traditional MI monolithic application to a cloud native? >>Well, it's another good question. Of course you notice that there's a general trend in the industry. Clients don't really want to lift and shift anymore. Lift and shift doesn't really bring any transformational value to my, to my company. So clients are looking for increasingly what we could recall, cloud native modernization. I want my applications to really take advantage of the cloud native environment. They need to be elastic and kind of more robust than maybe before now in particular, I think a lot of clients have realized that this state of Nirvana, which was we're gonna modernize everything to be a cloud native microservices based application. That is a tremendous journey, but no client really has the time patient or resources to fully refactor or rearchitect all of their applications. They're looking for more immediate kind of impact. So a key trend that we've seen of course is clients still want to refactor and modernize applications, but they're focusing those resources on those applications that will bring greater impact to their business. >>What they now see as a better replacement for lift and shift is probably what we would call replatforming, where they want all of the advantages of a cloud native environment, but they haven't necessarily got the time to modernize the code base. They wanna refactor to Kubernetes in re replatform to Kubernetes in particular, and they want us to take them there quickly. And that's why, for example, this week at cuon eight sellers announced a new set of tools called KMP based on conveyor, an open source project supported by red hat. And the key attraction of KMP is it lets me replatform my applications to Kubernetes immediately, right? Within two or three minutes, I can bring an application from a legacy platform directly onto Kubernetes and I can take it straight into production. That's the kind of acceleration that clients are looking for today. Isn't >>That just a form of lift and shift though? >>Well, no lift and shift typically of course, was moving virtual machines from one place to another. You know, the focus of Kubernetes of course is containerization of solutions. And it's not just about containerizing the solution and moving it. It's the DevOps tool chain around the solution as well. And of course, when I take that application into production in a Kubernetes based environment, I'm expecting to operate it in a different way as well. So that's where we see tremendous focus on what we would call cloud native operations clients expecting to use practices like site reliability engineering, to run these replatformed applications in a different way to, so >>It sounds like you're saying, I, I mean, replatforming has been a, a spectrum of options. I think Gartner has seven different types of re-platforming. Uh, are you seeing clients take more mature attitude now toward replatforming? Are they looking more carefully at the characteristics of their legacy applications and, and trying to try to make maybe more nuanced choices about what to replatform, what to just leave >>Alone? I think clients and I I'm sure Ramon's got some comments on this too, but clients have a lot more insight now in terms of what works for them. They they've realized that this, this promise of maybe a microservices based applications estate is a good one, but I can't do that for every application. If I am a large enterprise with several thousand applications in my portfolio, I can't refactor everything to become microservices based. So clients see replatforming possibly is a middle ground. I, I get a lot of the advantages from a cloud native environment. My applications are inherently more efficient, hopefully a lot more performance. >>Yeah. It's, it's a matter of software delivery performance. Yeah. So, uh, legacy workloads will definitely benefit from, uh, being brought into Kubernetes in the software delivery per performance department. So, uh, it's a matter of, uh, somehow Rebump your, your legacy applications and getting the benefits in, in life's application, life cycle management, a, uh, full tolerance and all that stuff. It's about leveraging the, what Kubernetes offers. >>When you say bringing legacy applications into Kubernetes. It's not that simple, right? I mean, what's involved in doing that. >>It, it, isn't, it's just a matter of taking a holistic view at your application portfolio and understanding the nuances of each application type within your organization and trying to come up with a suitable migration strategy for each one of these application types. And for that, what we're trying to do is provide a series of standardized, um, tools and methodologies, uh, from a community perspective, uh, we created this conveyor community. Uh, it, it was kick started by red hat and IBM, but we are trying to bring as many vendors and GSI, uh, as possible to try to set up these standards to make these, uh, road towards Kubernetes as easy as >>Possible. So we've done a little bit of, uh, app modernization in the CTO advisor hybrid infrastructure. And one of the things that we've found, there's plenty of Avan advantages. If I take a monolithic application that has, uh, that I've traditionally had to scale off to, uh, game performance, I can take selective parts of that, and now I can add auto-scaling to it. Exactly. However, as I look at a landscape Allen of thousands of applications, uh, I need to dedicate developer resources to get that done and my traditional environment, but my traditional environment is busy building new. My traditional or my developers are building new applications and new capabilities. I just don't have the resources to do that. How does HCL and red hat team together to kind of fast track that capability? >>Well, um, I'll comment on two things in particular, actually the, the first thing when it comes to skilling, I think the thing that's really surprised us at HCL is so many of our clients around the world have said, we are desperately short of skills. We cannot hire ourselves out of this problem. We need to get our existing developer community re-skilled around platforms like OpenShift, conveyor, and other projects too. So the first thing that's happened to us at eight still is we've been incredibly busy undertaken, probably what we would call developer workforce modernization, right, where we have to help the client reskill their entire technical and developer community to give them the skills, right. So we will help the clients develop a community, build the cloud native understanding, help them understand how to modernize tools for example, uh, or applications. But the second thing I mention is, and this comes back to a comment that Ramon made around around conveyor. >>It's been really encouraging to see the open source community start to invest in building the supporting frameworks around my kind of modernization journey, because if I'm a developer that's re-skilling and I'm attempting to maybe modernize an application, being able to dip into an open source project, I mean, a good example would be tackled part of the conveyor project. Exactly. You now have open source based tools that will help you analyze your applications. They will go into the source code and they will give the developer guidance in terms of what would be effective treatments to undertake. So perhaps a development team that are new to this modernization journey, they would benefit from a project like conveyor, for example, because I need to know where can I safely modernize my application now for experience organizations like HCL that comes naturally to us, but for people who are just starting this journey, if I can take an open source tool like tackle or the rest of the conveyor, for example, and use that to accelerate my journey, it takes a lot of pressure off, off my organization, but it also accelerates the journey too. >>And it's not just a matter of, of tooling. We we're also opensourcing, uh, the, the modernization methodology that we've been using in red hat consulting for years. So this whole conveyor communities, it's all about knowledge sharing on one hand and building a set of tools together, based on that knowledge that we are sharing to make it as easy as possible. >>And what role does red hat play in all that, I mean, is your you've carved out this position for yourself as the, as the true open source company. Is that, does that position you for a leadership role in helping companies make this >>Transition? I wouldn't say we should be leading the whole thing. Uh, we, we kick started it, but we want to get other vendors on board for this thing. One cool thing about the Camira community is that IBM is, uh, opensourcing a lot of their IP. So IBM research is on board. In this thing, we have some really crazy stuff related to a AI being applied to application analysis. We have some machine learning in place. We have very cool stuff that has been sitting on a, on a corner in IBM research for quite some years that now it's being open sourced and integrated in a, uh, unified user experience to streamline the, uh, modernization process as much as >>Possible. So let's talk about the elephant of the room. Uh, HCL was leading the conversation around cloud Foundry circa five plus years ago. And as customers are thinking about their journey to cloud native, how should they think about that cloud Foundry to cloud native or Kubernetes, uh, replatforming? >>Well within the cloud Foundry community, we've, we've been quite staunched supporters of Kubernetes for quite some time, right? It's, it's quite a, a stated intent of the cloud Foundry foundation to, to move across to Kubernetes platform right now that is a significant engineering journey for cloud Foundry to take. Now we're in this position where a lot of large users of cloud Foundry have a certain urgency to their journey. They, they want to consolidate on a single Kubernetes based, okay. Um, infrastructure. We, we see a lot of traction around OpenShift, for example, from red hat in terms of its market leadership. So a lot of clients are saying we would like to consolidate all of our platforms around a single kind of Kubernetes vendor, whether that's red hat or anyone else, you know, quite frankly. So what ATL is doing right now with the tools and the solutions we've announced this week is we're simply accelerating that journey for clients. If I've got a large installed base of applications running in my cloud Foundry environment, and I've also started to invest in standardize on Kubernetes based platforms like OpenShift, most clients would see it as quite a sensible choice to now try and consolidate those two environments into one. And that's simply what we're doing at HCL. We're making it very, very easy. In fact, we fully automated the journey so I can move all of my applications from cloud Foundry into for example, OpenShift pretty much immediately. And it just simplifies the entire journey. >>So the, as we start to wrap up the segment, I like to know customer stories. What, what, how customers either surprised or challenged when they get into, even with the help of an ACL in redhead, why are they seeing the most difficult parts of their migrations? >>Well, my, my simple comment would be maybe complexity, right? And the, the associated requirement for skilled people to undertake this modernization work, right? We spoke about this, of course, in terms of clients now are a lot more realistic. They understand that their ambition now needs to be somewhat tempered by their ability to sort of drive modernization quickly. So we see a lot of clients when they look at their very large global portfolios of applications, they're trying to invest their resources in the higher priority applications, the revenue generative applications in particular, but they have to bring everything else with them as well. Now, a common kind of separation point was we see a lot of clients who might say I'm gonna properly modernize and refactor, maybe five to 10% of my portfolio, but the other 90% also needs to come on the journey as well. And that's really where replatforming in particular kicks in. So, so the key trend again, is, is clients send to us, I've gotta take the entire journey. All right, I've got the resources and the skills to really focus on this much of my application base. Can someone simplify the overall journey so I can afford to bring everything on a cloud native journey? >>So the key to success here is having a holistic view at the application portfolio, segmenting the application portfolio in different application types and ordering the, the priorities of these application types and come up with suitable migration strategies for each one of them is >>Really necess necessary to move everything though. >>Not necessarily no, or, uh, not necessarily. Yeah, absolutely not everything. But, uh, it would make sense. Uh, as we were saying before, it will definitely move, make sense to move legacy applications towards Kubernetes, to leverage all the, uh, software delivery >>That's >>That's project, right? >>It is. If >>You're gonna restructure the application around APIs and microservices, >>That it should be taken the, the way I've seen, uh, organizations succeeding the most in this, uh, road towards cloud native and Kubernetes in general is trying to address the whole portfolio. Maybe not move everything, but try, try to have this holistic view and not leave anything behind, because if you try to do this isolated, uh, initiatives of bringing this or that applications in a, in isolation, you're Def you, you will miss part of the picture and you might be, uh, doomed to fail >>There. Yeah. It's been my experience that if you don't have a plan to migrate your applications to a cloud native operating model, then you're doomed to follow lift and shift examples to the public cloud. Yeah. Whether you're, uh, going to any other clouds, if you don't make that, that operational transition. Last question on operational transition, we've talked a lot about the replatforming process itself. What about day two, uh, at the I've landed to the cloud? What are some of the top considerations for, for compliance, uh, op op observability, just making sure my apps stay up and transitioning my workforce to that model. >>I, I, I think the over, you know, the overarching trend or theme that, that I see is clients now are, are asking for what I would call cloud native operations. Now in particular, there's a very solid theme around what we would call reliability engineering. So think about site reliability, engineering, SRE platform, reliability engineering, PR E. These are the dominant topics that clients and I want to engage, uh, HCL on in particular, because the point you make is a valid one. I've modernized my application. Now I need to modernize the way that I operate the application in production. Otherwise I won't see those benefits. So that general theme of SRE is keeping us really busy. We're busy, re-skilling all of those operations teams around the world as well, because they need to know how to run these environments appropriately too. >>And also being able to measure your progress while your transitioning is important. And that's one of the concerns that we are addressing as well in the premier community with a tool called polars to, to measure, to effectively measure the software delivery performance of, of the organization after the transition has been done. >>And this is a really good point by the way, cuz most, most people think it's a bit of a black art. How do I understand how I modernize my application? How do I understand how I've improved my kind of value chain around software creation and many people thought you needed to bring in very expensive consultants to advise you on these, on these black lives? No, >>Definitely >>Not. But in open source projects like conveyor from, from red hat, the availability of these tools available on an open source model means exactly any engineer, any developer can get these tools off the shelf and get that immediate benefit. >>Well, a flower head of creative labs at HCL at Ramon neon, senior product manager, redhead. Thank you for joining the QPI. Now Cuba alum, uh, you'll have a nice profile like the profile picture on here. Awesome. >>Absolutely. Thank you. >>From Valencia Spain. I'm Keith towns, along with Paul Gillon and you're watching the cue, the leader in high tech coverage.

>>Mm. Welcome back to the seaports in Boston City is abuzz. Bruins tonight, Celtics Tomorrow night. We're all excited. We're talking open source, which is a very exciting topic. Every company is using open source. I mean, it is the mainspring of innovation. I'm Dave along with my co host, Paul Dillon. And you're watching the cubes. Coverage of Red Hat. Summer 2022. Raj Raj Masinga is here. He's hybrid and emerging Platforms lead at Accenture and Ghetto Greber. Who's red hats? Business group lead eccentric. Gentlemen, welcome to the Cube. Thanks for coming >>on. Thank you. >>Thank you, Raj. We saw in the keynote up there today with Stephanie. She's coming on tomorrow. Rockstar Stephanie. Cheers. Also a Boston sports fan, and I have to work at it, but you can talk about the history with red hat. How long have you guys been at this? And give us a journey update. >>Well, first of all, thanks for having us here. Um, yes, we are big fans of Red Hat and especially Stephanie. I get to I had the pleasure of working with a very closely, um, our relationship with Red Hat goes many, many years, decades I think. And but Paul, come here will tell you that. You know, we've been focused a lot with the formation of our new business unit in Cloud. First around, migrating to the public cloud. But now, as we focus more and more around how our clients begin to operate in the public cloud in the cloud ecosystem hybrid is coming much more into focus. And Red Hat is very much a key client of a key partner of us. So we go way back. But this is all about us doubling down and increasing our partnership and deepening it with them. >>So, uh, you talked today about hybrid Cloud is everything. And it seems like a couple of years ago there was focuses more on moving to the public cloud and getting off of private infrastructure. Has there been a change in the ways in which customers are thinking, are they gonna be hanging onto their private infrastructure longer, perhaps, than was expected a couple of years ago? >>I think the first of all, it's a very different industry by industry. If you look at retail or consumer goods, I think there's a big movement in terms of percentages of workloads that are getting moved onto public cloud. If you look at industries like banking or utilities or government, more regular financial services, more regulated industries. I think we are finding a much larger percentage of their workloads because of regulatory reasons and security reasons, etcetera. Our need to remain either on premise or in private cloud. So I think it very much depends on the industry. But regardless the hype, you know, especially with the movement to edge now hybrid is going to be, you know, permeating everything. So I think by industry depends. But but the edges driving a whole new flywheel. >>You know, we started the Cuban 2010, so the cloud was, you know, modern cloud. Anyway, it was like, say, four years in into it and at the time, to your point Raj Financial Services, there was an evil word. No way we're ever going to the cloud. No, that's changed, obviously. But then, when the financial crisis hit, >>you >>had so initially it was a lot of tyre kicking experimentation. When the financial crisis hit, you had a lot of CFO saying, Okay, let's shift Capex to Apex and so that was sort of a bridge. And then after we came out, it was like this spate of innovation. And then we saw that during the pandemic, where cloud migration was a high priority and or it was the lifeline. And now it sounds like customers are kind of rethinking to your earlier conversation. What is cloud? It's that operating model. So I wonder if you could sort of Can you confirm that's kind of the journey that customers are taking? Where are they today? What does it mean? There? You know the the operating model. What do they consider cloud? >>Um, you actually, you see it? It's like it's really try forward to the cloud. Uh, but where it was in the beginning, If it doesn't hype about Public Cloud, they become more and more aware that it's hybrid because they have to bring the legacy system and process into the cloud as well. And it takes more time that actually they have fought before. So it's like there was a process of learning and also like in the steps moving forward to the operating model because they also understand I cannot operate a cloud like I was operating in the classical way like my old data centre and everything. It needs all the capabilities it needs, all the skills and especially if you go in a hybrid world. And it's a hybrid operation between the classic traditional but also the new ways of how you operate into a cloud. And you really see also the financial services. Now, uh, we had, uh I mean watch presented at keynote. We had a client in Germany. He made a decision, a very traditional financial services clients providing the service to chairman saving banks. And they did this decision and I would say, if you have spoken to them 10 years ago, they will not go into the cloud. But now they went to the cloud via private cloud, and now they got the confidence about how to operate in it. And now they move forward into a public cloud. But from a private cloud into the public cloud. Today, after security, they have up Skilling on skills and people and they understand the process and what's really required and needed in order to have such an environment. >>Generally, what's the strategy with regard to modernisation organisations? More building like an abstraction layer? Uh, with microservices and then connecting to the cloud. Or are they actually rewriting applications to make them cloud native? What are you What are you advising clients from a strategy standpoint, and I know it depends, but, you know, it's >>a It's a great question. I think the genesis to that strategy is how they view infrastructure, Right? So you know, everyone is, has this kind of, I don't know that this is almost mythical opinion out there with cloud. You don't need to worry about your infrastructure. All the providers will worry about it, and you just need to move it there. But the opposite is true. It's really critical what your infrastructure strategy is as you move to the cloud, because depending on what workload you have, you know it can be on any one of the continuum that you described. So the first thing is, where do you want to house your workload? Is the question and that will drive. How what do you want to do with your application? Whether you want to just maintain it the way it is, Do you want to simply modernise it, keeping where it is, or do you want to completely risk in it or even eliminated. So so I think the entire basically the answer to your question around. Do we? What do we do with the application? Is fundamentally driven by what is your infrastructure strategy and what that workload needs to do for you. >>So I know you want to jump in, but I got to follow up. You're saying hardware matters because we heard Paul Corvino today talking about this hardware renaissance. I'm actually I just ran a power panel called. Does hardware still matter? You're saying it matters? >>Yeah. And and it doesn't. And infrastructure doesn't always. I mean, now that you can do infrastructure as code, right? I mean, I was at the Del summit last time and read That is a huge partner of Dell now, right? Which, you know, uh, was much more, uh, partnered with VM ware. But I think the whole ecosystem is opening up, and even the hardware providers are looking at this in a much more nimble way. But yes, it's very much part of the conversation. They haven't gone away. >>During your keynote. You outlined sort of your strategy. Going forward is called cloud first. Yes. What does cloud first mean? >>Well, um, we we want to make sure that when we talk about transformation of business with our clients, So extension always goes with the idea of an industry lens of solving a specific problem for a client. What is the business problem we solve? And increasingly, what we want to message and drive to our clients is if you're thinking about, regardless of what the business is technologies absolutely critical to whatever transformation you're doing and when. When you look at technology, you have to think cloud first because that's where all the innovation is happening. That's where all the, um um, investments are being driven. Whether it's an I mean, it's a software vendor, but it's a hardware vendor with its uh, so you have to think cloud first when you think about transforming your business. >>Uh, what is How does modernisation play into that? You know, a lot of vendors are throwing a lot of resources that the modernisation market VM ware, Tanzania and IBM and such, uh, how interesting our customers really a Modernising legacy applications >>hugely right, because fundamentally, I think everything is now driven by our experiences. What we now are used to in terms of, uh, interfacing with applications are interfacing with function sets or interfacing with technology. So there is a lot of inherent, um, legacy technology that doesn't have that experience. So when you think about transforming, you have to come at it from an experience point of view. And when you think in those terms modernisation or even rebuilding the same, even if it's the same function set, uh, re skinning it and modernisation is critical for the purposes of engagement. >>What's the number one challenge that customers that you're working with face in terms of modernisation? Is it trying to figure out like Rogers sort of laying out the portfolio? What do I do with it? Do I modernise it? Do I retire it? Do I let it just die on the vine? What's their number one challenge? >>Uh, mainly it depends also on the industry, but it's, uh, I would say, for the highly regulated, certainly regulations. They always have an own interpretation of the regulations. Regulation means for them, but normally it's not really what they understand. But I think this is more and more coming to Annie's and more people understand what it really means, but it's also what we see a lot. They think first about technology, but not what kind of business problem they want, Uh, and they want to solve. So it's like, instead of having a technology neutral discussion is really do want to achieve, um, to have really start on this side and then having this discussion away, which, obviously it's one of the key, even because they start to the cloud even without having a strategy without having a vision. If you have a clear vision, if you have a clear strategy, you know where you want to go, and then you can make your business case. You can make you architecture and then you decide on technology. And then, of course, on this journey, all the things about security compliance coming to the plane, Yeah, and I think I think that's the easiest approach. But clients struggle to understand. Of course, I mean, the technology is changing rapidly. Even new products and release cycle new life cycles, the complexity of all the tools hardware we mentioned before network is changing new working coming up. It's really hard to keep pace or keep up with the base of the technology and what's happening even for us. And then you understand the complexity and bring this complexity back to simplicity, but not without losing. We have this also keynote the efficiency and, uh, flexibility for an engineer, because that's what he needs >>to your clients. Have the skill sets to do all that such a self serving question to you guys. But but no, do they? I mean, there's a skills shortage. There's a a battle for talent. So how are they >>dealing? I mean, it's obvious the battle for talent is here. I mean, everybody is looking for the best talent, and if we need, if you need a full stack. Engineer, for example, is very hard to get a full stack engineer on your ground. You call really cloud native. So you have to up skill people to re skilled people. There's also a change coming into it and the changes not to forget. So it's what we say most time. The technology is an easy part, but the change change the organisation, change up skilled organisation. That's the hard part because you need to change from from one mindset to another, and we know from the from the past. What change? People are not open to change in general, so we need to change the mindset. >>I wanna go back to Hybrid Cloud because we have Dani from Red Hat was on earlier and he said, Edges really redefining the definition of hybrid cloud. It's it's more complex architecture, and it's changing the nature of how we think about hybrid Cloud. Are you seeing that with your customers? Are they changing their thinking about what hybrid means in that context? >>Yeah, completely. You know, I was I was We did a bunch of, uh, research recently, and I had I just wanted to make sure I called this. I mean, there's a flexible report that came out that says 80% of all enterprises now are on hybrid 89% multi cloud redheaded. A report that said 80% of our businesses are expected to, um, uh, increase their use of open source. Right, So So, yes, hybrid is everywhere. Edge is driving it, but there's a There's another critical element to that movement. The complexity of our clients. Estates are increasing because whether it's hybrid or whether it's edge or whatever, they are now. You know, given if you're a C i or a C T o. Your estate is really complex now. So one of the things that we now need to do is how do we simplify that? So, you know, we think and we've been talking with red hat about this. We need to come up with a clean, you know, we keep calling it, you know, single pane of glass for a enterprise that allows them to look at their estate in a way that allows them to then simply make some innovative decisions across the entire state. So, yes, edges driving hybrid. But the key thing that we now need to overcome is how do we manage that complexity? >>We have new term. Uh, I call it Super Cloud, but the session is a better word. Medic cloud. That's gonna what I think of that century. I think of deep industry expertise. Of course, we have that, but with the partnership from redhead, it's a very it's horizontal in the sense that it can go anywhere. So how do you guys work in in terms of within Accenture plugging into your deep industry expertise? And how does that horizontal redhead >>fit. That's a really good question. So, you know, one of the things, you know. First of all, we came out with a announcement today about our expanded relationship with Red Hat. One of the key elements in that announcement is how we are looking and bringing in red Hat into our industry business motions. So we actually have decided to pick a certain number of industries. You know, financial services is one. Telco is another. We are thinking about utilities in Europe. Public health is a is another one that we are looking at. And as we come up with our offerings, you heard me and Stephanie talk about joint offerings earlier on the keynote. Um, these offerings are industry offerings, but in those offerings we have embedded and we are, they're powered by redhead technology. Um, that allows these industry solutions to drive innovation through their technology. Um, yes. Red hat can be, for the most part, a horizontal cross industry, you know, technology. But you have to really bring them into specific industrial solutions because of the way we go to market. And I think Red hat brings innovation, uh, in a way that these industries haven't seen before. >>So I mean, how do you stay out of their way? Because they have a services operation that they're trying to grow. And that's your business as well. So where the lines of demarcation >>back to your question? I I don't I don't think there is a limiting opportunity. Read? Had, you know Stephanie Me, Paul, we're all talking about How do we collectively increase both our armies? You know, I I Yes, there might be occasional overlaps in the trenches, but when you look at the bigger picture, it is not a problem at all. >>I wouldn't think so. I mean, the way you're describing Rogers exactly the way it should work. You lead with the business, figure out the business problem, how you're gonna solve that. The technology will take care of itself. Technologies come and they go. And you want to use modern technologies, obviously. But if you don't get the business piece right, forget no technology is gonna save you >>exactly, right. And and the complexities of what the businesses today are facing is getting more and more difficult. And I think actually, technologies like red hat, you know, they're the whole concept of open source, I think is very creative around driving innovations from the market. I >>want to ask you that because Paul Kermie is you know, the storey was sort of an homage to open source. How much do customers really care about open source >>customers care about innovation and and anything that drives innovation to their business, whether it's whether it comes from technology, whether it comes from crowdsourcing, whether it comes from, you know, uh, marketing doesn't matter. I think when you look at the key hunger for innovation and how open source drives innovation, it becomes part of the business conversation. And, uh and I think that's been one of the mantras that Paul has had from day one about how this is such a great platform for innovation. And I think that's >>something customers asked for. They say we must develop this using open source platforms and tool sets. >>Um, it depends. I think I think there are some technology CEO s R c T O s that are much more religious about what? Their technologies that needs to be there are others that are that are much more business oriented. Um, so yes, there are. You know, if it's more in telecom field, I think telecom or some of the more, uh, technology driven fields, they will ask for open source. In others, they we bring, bring it through as part of offering. >>Here's the nuance that I see and you mentioned Paul Cormier. Accenture, especially. I mean, you look at your ascendancy as a company, you for years would take known processes and codify them in software. And you made, you know, a lot of great innovations doing that. And people who made a lot of >>money >>today, this new normal, he calls it. I call it the new abnormal. You don't know what's around the corner. You have to build flexibility into your business, and that is something that open source enables. Uh, so that's sort of this, Really Not really. We don't want to speak about it too much. Business resiliency and flexibility is that that is the new normal. I don't see how you can do it without without open sources expertise. >>I completely agree that I and I think, um, it's actually an asset. So you know, in some ways, selfishly, by having open source in a solution stack some of the innovation gets them much more democratised, right? So? So it can come from a much broader sweet. So the load is not only an extension to come up with all the innovation we can, we can actually come up with a more democratised way of bringing that innovation in. So I think that's that's >>great. And it doesn't always go back to the community. I mean, Amazon built a $70 billion business on open source, but not all right, guys. Thanks so much for coming. Thank you very much for having a pleasure. All right, keep it right there. This is Dave Volonte for Paul Dillon. The Cubes. Continuous coverage of Red Hat Summit 2022 from the seaport in Boston. We'll be right back. >>Mm mm.

[Music] is an open source first company right and we've been around for 20 years and we're pretty amazing at being good at open source giving back to the community building software with people and sharing it back to the community the cubism is an amazing kind of community outreach show and it's really great to be able to communicate and talk to the right people working with the cube has been incredible we do have a couple people that have been on the show a lot and like been able to do that and i think you're very friendly um and yeah just just have a good community around you i've worked for microsoft for a really long time and this is my first reinvent and it's it feels a little odd to be here for a non-microsoft event um and odd and exciting in a way um we are so redhead is partnering with both aws azure as well as gcp ibm and we we are working across different clouds partnering with a lot of cloud providers and i think this is a very interesting new relationship that we have that is new to me compared to being very committed to one single vendor one single line of business like one single operating system and stuff like that being able to partner with different people across the industry and board can build stuff together for the customers one word community

>>mhm Yes. >>Welcome back to the Cube coverage of Red Hat summit 21 2021. I'm john for host of the Cubans virtual this year as we start preparing to come out of Covid a lot of great conversations here happening around technology. This is the emerging technology with Red hat segment. We've got three great guests steve watt manager, distinguished engineer at Red Hat hurl saying senior software engineer Red Hat and luke Hines, who's the senior software engineer as well. We got the engineering team steve, you're the the team leader, emerging tech within red hat. Always something to talk about. You guys have great tech chops that's well known in the industry and I'll see now part of IBM you've got a deep bench um what's your, how do you view emerging tech um how do you apply it? How do you prioritize, give us a quick overview of the emerging tech scene at Redhead? >>Yeah, sure. It's quite a conflated term. The way we define emerging technologies is that it's a technology that's typically 18 months plus out from commercialization and this can sometimes go six months either way. Another thing about it is it's typically not something on any of our product roadmaps within the portfolio. So in some sense, it's often a bit of a surprise that we have to react to. >>So no real agenda. And I mean you have some business unit kind of probably uh but you have to have first principles within red hat, but for this you're looking at kind of the moon shot, so to speak, the big game changing shifts. Quantum, you know, you got now supply chain from everything from new economics, new technology because that kind of getting it right. >>Yeah, I think we we definitely use a couple of different techniques to prioritize and filter what we're doing. And the first is something will pop up and it will be like, is it in our addressable market? So our addressable market is that we're a platform software company that builds enterprise software and so, you know, it's got to be sort of fit into that is a great example if somebody came up came to us with an idea for like a drone command center, which is a military application, it is an emerging technology, but it's something that we would pass on. >>Yeah, I mean I didn't make sense, but he also, what's interesting is that you guys have an open source D N A. So it's you have also a huge commercial impact and again, open sources of one of the 4th, 5th generation of awesomeness. So, you know, the good news is open source is well proven. But as you start getting into this more disruption, you've got the confluence of, you know, core cloud, cloud Native, industrial and IOT edge and data. All this is interesting, right. This is where the action is. How do you guys bring that open source community participation? You got more stakeholders emerging there before the break down, how that you guys manage all that complexity? >>Yeah, sure. So I think that the way I would start is that, you know, we like to act on good ideas, but I don't think good ideas come from any one place. And so we typically organize our teams around sort of horizontal technology sectors. So you've got, you know, luke who's heading up security, but I have an edge team, cloud networking team, a cloud storage team. Cloud application platforms team. So we've got these sort of different areas that we sort of attack work and opportunities, but you know, the good ideas can come from a variety of different places. So we try and leverage co creation with our customers and our partners. So as a good example of something we had to react to a few years ago, it was K Native right? So the sort of a new way of doing service um and eventing on top of kubernetes that was originated from google. Whereas if you look at Quantum right, ibms, the actual driver on quantum science and uh that originated from IBM were parole. We'll talk about exactly how we chose to respond to that. Some things are originated organically within the team. So uh luke talking about six law is a great example of that, but we do have a we sort of use the addressable market as a way to sort of focus what we're doing and then we try and land it within our different emerging technologies teams to go tackle it. Now. You asked about open source communities, which are quite interesting. Um so typically when you look at an open source project, it's it's there to tackle a particular problem or opportunity. Sometimes what you actually need commercial vendors to do is when there's a problem or opportunity that's not tackled by anyone open source project, we have to put them together to create a solution to go tackle that thing. That's also what we do. And so we sort of create this bridge between red hat and our customers and multiple different open source projects. And this is something we have to do because sometimes just that one open source project doesn't really care that much about that particular problem. They're motivated elsewhere. And so we sort of create that bridge. >>We got two great uh cohorts here and colleagues parole on the on the Quantum side and you got luke on the security side. Pro I'll start with you. Quantum is also a huge mentioned IBM great leadership there. Um Quantum on open shift. I mean come on. Just that's not coming together for me in my mind, it's not the first thing I think of. But it really that sounds compelling. Take us through, you know, um how this changes the computing landscape because heterogeneous systems is what we want and that's the world we live in. But now with distributed systems and all kinds of new computing modules out there, how does this makes sense? Take us through this? >>Um yeah john's but before I think I want to explain something which is called Quantum supremacy because it plays very important role in the road map that's been working on. So uh content computers, they are evolving and they have been around. But right now you see that they are going to be the next thing. And we define quantum supremacy as let's say you have any program that you run or any problems that you solve on a classical computer. Quantum computer would be giving you the results faster. So that is uh, that is how we define content supremacy when the same workload are doing better on content computer than they do in a classical computer. So the whole the whole drive is all the applications are all the companies, they're trying to find avenues where Quantum supremacy are going to change how they solve problems or how they run their applications. And even though quantum computers they are there. But uh, it is not as easily accessible for everyone to consume because it's it's a very new area that's being formed. So what, what we were thinking, how we can provide a mechanism that you can you don't connect this deal was you have a classical world, you have a country world and that's where a lot of thought process been. And we said okay, so with open shift we have the best of the classical components. You can take open shift, you can develop, deploy around your application in a country raised platform. What about you provide a mechanism that the world clothes that are running on open shift. They are also consuming quantum resources or they are able to run the competition and content computers take the results and integrate them in their normal classical work clothes. So that is the whole uh that was the whole inception that we have and that's what brought us here. So we took an operator based approach and what we are trying to do is establish the best practices that you can have these heterogeneous applications that can have classical components. Talking to our interacting the results are exchanging data with the quantum components. >>So I gotta ask with the rise of containers now, kubernetes at the center of the cloud native value proposition, what work clothes do you see benefiting from the quantum systems the most? Is there uh you guys have any visibility on some of those workloads? >>Uh So again, it's it's a very new, it's very it's really very early in the time and uh we talk with our customers and every customers, they are trying to identify themselves first where uh these contacts supremacy will be playing the role. What we are trying to do is when they reach their we should have a solution that they that they could uh use the existing in front that they have on open shift and use it to consume the content computers that may or may not be uh, inside their own uh, cloud. >>Well I want to come back and ask you some of the impact on the landscape. I want to get the look real quick because you know, I think security quantum break security, potentially some people have been saying, but you guys are also looking at a bunch of projects around supply chain, which is a huge issue when it comes to the landscape, whether its components on a machine in space to actually handling, you know, data on a corporate database. You guys have sig store. What's this about? >>Sure. Yes. So sick store a good way to frame six store is to think of let's encrypt and what let's encrypt did for website encryption is what we plan to do for software signing and transparency. So six Door itself is an umbrella organization that contains various different open source projects that are developed by the Six door community. Now, six door will be brought forth as a public good nonprofit service. So again, we're very much basing this on the successful model of let's Encrypt Six door will will enable developers to sign software artifacts, building materials, containers, binaries, all of these different artifacts that are part of the software supply chain. These can be signed with six door and then these signing events are recorded into a technology that we call a transparency log, which means that anybody can monitor signing events and a transparency log has this nature of being read only and immutable. It's very similar to a Blockchain allows you to have cryptographic proof auditing of our software supply chain and we've made six stores so that it's easy to adopt because traditional cryptographic signing tools are a challenge for a lot of developers to implement in their open source projects. They have to think about how to store the private keys. Do they need specialist hardware? If they were to lose a key then cleaning up afterwards the blast radius. So the key compromise can be incredibly difficult. So six doors role and purpose essentially is to make signing easy easy to adopt my projects. And then they have the protections around there being a public transparency law that could be monitored. >>See this is all about open. Being more open. Makes it more secure. Is the >>thief? Very much yes. Yes. It's that security principle of the more eyes on the code the better. >>So let me just back up, is this an open, you said it's gonna be a nonprofit? >>That's correct. Yes. Yes. So >>all of the code is developed by the community. It's all open source. anybody can look at this code. And then we plan alongside the Linux Foundation to launch a public good service. So this will make it available for anybody to use if your nonprofit free to use service. >>So luke maybe steve if you can way into on this. I mean, this goes back. If you look back at some of the early cloud days, people were really trashing cloud as there's no security. And cloud turns out it's a more security now with cloud uh, given the complexity and scale of it, does that apply the same here? Because I feel this is a similar kind of concept where it's open, but yet the more open it is, the more secure it is. And then and then might have to be a better fit for saying I. T. Security solution because right now everyone is scrambling on the I. T. Side. Um whether it's zero Trust or Endpoint Protection, everyone's kind of trying everything in sight. This is kind of changing the paradigm a little bit on software security. Could you comment on how you see this playing out in traditional enterprises? Because if this plays out like the cloud, open winds, >>so luke, why don't you take that? And then I'll follow up with another lens on it which is the operate first piece. >>Sure. Yes. So I think in a lot of ways this has to be open this technology because this way we have we have transparency. The code can be audited openly. Okay. Our operational procedures can be audit openly and the community can help to develop not only are code but our operational mechanisms so we look to use technology such as cuba netease, open ship operators and so forth. Uh Six store itself runs completely in a cloud. It is it is cloud native. Okay, so it's very much in the paradigm of cloud and yeah, essentially security, always it operates better when it's open, you know, I found that from looking at all aspects of security over the years that I've worked in this realm. >>Okay, so just just to add to that some some other context around Six Law, that's interesting, which is, you know, software secure supply chain, Sixth floor is a solution to help build more secure software secure supply chains, more secure software supply chain. And um so um there's there's a growing community around that and there's an ecosystem of sort of cloud native kubernetes centric approaches for building more secure software. I think we all caught the solar winds attack. It's sort of enterprise software industry is responding sort of as a whole to go and close out as many of those gaps as possible, reduce the attack surface. So that's one aspect about why 6th was so interesting. Another thing is how we're going about it. So we talked about um you mentioned some of the things that people like about open source, which is one is transparency, so sunlight is the best disinfectant, right? Everybody can see the code, we can kind of make it more secure. Um and then the other is agency where basically if you're waiting on a vendor to go do something, um if it's proprietary software, you you really don't have much agency to get that vendor to go do that thing. Where is the open source? If you don't, if you're tired of waiting around, you can just submit the patch. So, um what we've seen with package software is with open source, we've had all this transparency and agency, but we've lost it with software as a service, right? Where vendors or cloud service providers are taking package software and then they're making it available as a service but that operationalize ng that software that is proprietary and it doesn't get contributed back. And so what Lukes building here as long along with our partners down, Lawrence from google, very active contributor in it. Um, the, is the operational piece to actually run sixth or as a public service is part of the open source project so people can then go and take sixth or maybe run it as a smaller internal service. Maybe they discover a bug, they can fix that bug contributed back to the operational izing piece as well as the traditional package software to basically make it a much more robust and open service. So you bring that transparency and the agency back to the SAS model as well. >>Look if you don't mind before, before uh and this segment proportion of it. The importance of immune ability is huge in the world of data. Can you share more on that? Because you're seeing that as a key part of the Blockchain for instance, having this ability to have immune ability. Because you know, people worry about, you know, how things progress in this distributed world. You know, whether from a hacking standpoint or tracking changes, Mutability becomes super important and how it's going to be preserved in this uh new six doorway. >>Oh yeah, so um mutability essentially means cannot be changed. So the structure of something is set. If it is anyway tampered or changed, then it breaks the cryptographic structure that we have of our public transparency service. So this way anybody can effectively recreate the cryptographic structure that we have of this public transparency service. So this mutability provides trust that there is non repudiation of the data that you're getting. This data is data that you can trust because it's built upon a cryptographic foundation. So it has very much similar parallels to Blockchain. You can trust Blockchain because of the immutable nature of it. And there is some consensus as well. Anybody can effectively download the Blockchain and run it themselves and compute that the integrity of that system can be trusted because of this immutable nature. So that's why we made this an inherent part of Six door is so that anybody can publicly audit these events and data sets to establish that there tamper free. >>That is a huge point. I think one of the things beyond just the security aspect of being hacked and protecting assets um trust is a huge part of our society now, not just on data but everything, anything that's reputable, whether it's videos like this being deep faked or you know, or news or any information, all this ties to security again, fundamentally and amazing concepts. Um I really want to keep an eye on this great work. Um Pearl, I gotta get back to you on Quantum because again, you can't, I mean people love Quantum. It's just it feels like so sci fi and it's like almost right here, right, so close and it's happening. Um And then people get always, what does that mean for security? We go back to look and ask them well quantum, you know, crypto But before we get started I wanted, I'm curious about how that's gonna play out from the project because is it going to be more part of like a C. N. C. F. How do you bring the open source vibe to Quantum? >>Uh so that's a very good question because that was a plan, the whole work that we are going to do related to operators to enable Quantum is managed by the open source community and that project lies in the casket. So casket has their own open source community and all the modification by the way, I should first tell you what excuse did so cute skin is the dedicate that you use to develop circuits that are run on IBM or Honeywell back in. So there are certain Quantum computers back and that support uh, circuits that are created using uh Houston S ticket, which is an open source as well. So there is already a community around this which is the casket. Open source community and we have pushed the code and all the maintenance is taken care of by that community. Do answer your question about if we are going to integrate it with C and C. F. That is not in the picture right now. We are, it has a place in its own community and it is also very niche to people who are working on the Quantum. So right now you have like uh the contributors who who are from IBM as well as other uh communities that are specific specifically working on content. So right now I don't think so, we have the map to integrated the C. N. C. F. But open source is the way to go and we are on that tragic Torri >>you know, we joke here the cube that a cubit is coming around the corner can can help but we've that in you know different with a C. But um look, I want to ask you one of the things that while you're here your security guru. I wanted to ask you about Quantum because a lot of people are scared that Quantum is gonna crack all the keys on on encryption with his power and more hacking. You're just comment on that. What's your what's your reaction to >>that? Yes that's an incredibly good question. This will occur. Okay. And I think it's really about preparation more than anything now. One of the things that we there's a principle that we have within the security world when it comes to coding and designing of software and this aspect of future Cryptography being broken. As we've seen with the likes of MD five and Sha one and so forth. So we call this algorithm agility. So this means that when you write your code and you design your systems you make them conducive to being able to easily swap and pivot the algorithms that use. So the encryption algorithms that you have within your code, you do not become too fixed to those. So that if as computing gets more powerful and the current sets of algorithms are shown to have inherent security weaknesses, you can easily migrate and pivot to a stronger algorithms. So that's imperative. Lee is that when you build code, you practice this principle of algorithm agility so that when shot 256 or shot 5 12 becomes the shar one. You can swap out your systems. You can change the code in a very least disruptive way to allow you to address that floor within your within your code in your software projects. >>You know, luke. This is mind bender right there. Because you start thinking about what this means is when you think about algorithmic agility, you start thinking okay software countermeasures automation. You start thinking about these kinds of new trends where you need to have that kind of signature capability. You mentioned with this this project you're mentioning. So the ability to actually who signs off on these, this comes back down to the paradigm that you guys are talking about here. >>Yes, very much so. There's another analogy from the security world, they call it turtles all the way down, which is effectively you always have to get to the point that a human or a computer establishes that first point of trust to sign something off. And so so it is it's a it's a world that is ever increasing in complexity. So the best that you can do is to be prepared to be as open as you can to make that pivot as and when you need to. >>Pretty impressive, great insight steve. We can talk for hours on this panel, emerging tech with red hat. Just give us a quick summary of what's going on. Obviously you've got a serious brain trust going on over there. Real world impact. You talk about the future of trust, future of software, future of computing, all kind of going on real time right now. This is not so much R and D as it is the front range of tech. Give us a quick overview of >>Yeah, sure, yeah, sure. The first thing I would tell everyone is go check out next that red hat dot com, that's got all of our different projects, who to contact if you're interested in learning more about different areas that we're working on. And it also lists out the different areas that we're working on, but just as an overview. So we're working on software defined storage, cloud storage. Sage. Well, the creator of Cf is the person that leads that group. We've got a team focused on edge computing. They're doing some really cool projects around um very lightweight operating systems that and kubernetes, you know, open shift based deployments that can run on, you know, devices that you screw into the sheet rock, you know, for that's that's really interesting. Um We have a cloud networking team that's looking at over yin and just intersection of E B P F and networking and kubernetes. Um and then uh you know, we've got an application platforms team that's looking at Quantum, but also sort of how to advance kubernetes itself. So that's that's the team where you got the persistent volume framework from in kubernetes and that added block storage and object storage to kubernetes. So there's a lot of really exciting things going on. Our charter is to inform red hats long term technology strategy. We work the way my personal philosophy about how we do that is that Red hat has product engineering focuses on their product roadmap, which is by nature, you know, the 6 to 9 months. And then the longer term strategy is set by both of us. And it's just that they're not focused on it. We're focused on it and we spend a lot of time doing disambiguate nation of the future and that's kind of what we do. We love doing it. I get to work with all these really super smart people. It's a fun job. >>Well, great insights is super exciting, emerging tack within red hat. I'll see the industry. You guys are agile, your open source and now more than ever open sources, uh, product Ization of open source is happening at such an accelerated rate steve. Thanks for coming on parole. Thanks for coming on luke. Great insight all around. Thanks for sharing. Uh, the content here. Thank you. >>Our pleasure. >>Thank you. >>Okay. We were more, more redhead coverage after this. This video. Obviously, emerging tech is huge. Watch some of the game changing action here at Redhead Summit. I'm john ferrier. Thanks for watching. Yeah.

>>mhm Yes. Hello and welcome back to the cubes coverage of red hat summit 2021 virtual. I'm john for your host of the cube and cube coverage here with matt Hicks. Executive vice president of products and technologies at red hat cuba lum I've been on many times, knows the engineering side now running all the process of technologies matt. Great to see you. Thanks for coming on remote. I wish we were in real real life in person. I RL but doing it remote again. Thanks for coming on. >>Hey, thanks thanks for having me today. >>Hey, so what a year you know, um, I was just talking to a friend and another interview with the red hat colleagues. Chef on your team in 2019 I interviewed Arvin at IBM right before he bought red hat and you smile on his face and he wasn't even ceo then um, he is such a big fan of cloud native and you guys have been the engine underneath the hood if you will of IBM this transformation huge push now and with Covid and now with the visibility of the post Covid, you're seeing cloud Native at scale with modern applications just highly accelerated across the board In almost every industry, every vertical. This is a very key trend. You guys at the, at the center of it always have been, we've been covering you for many years, interesting time and so now you guys are really got the, got the formula at red hat, take us through the key transit you see on this wave for enterprises and how is red hat taking that, taking that through? >>Yeah, no, absolutely. It has been, it's been a great ride actually. I remember a couple years ago standing on stage with Arvin prior to the acquisition. So it's been uh, it's been a world one but I think if we look at Really would emerge in 2020, we've seen three trends that we hope we're gonna carry through in 2021 just in a better and better year for that. That the first is open hybrid cloud is really how customers are looking to adapt to change. They have to use what they have um assets they have today. On premise, we're seeing a lot of public cloud adoption that blend of being hybrid is just, it is a reality for how customers are having to deliver a edge computing I think is another area I would say uh the trend is really not going to be a fad or a new, you know, great texture. Um the capabilities of computing at the edge, whether that is automotive vehicles, radio access network capabilities to five G. It's pretty astounding at this point. So I think we're gonna see a lot of pushing edge computing for computing, getting closer to users. Uh but then also the choice aspect we're seeing with Ceos, we often talk about technology is choice, but I think the model of how they want to consume technology has been another really strong trend in 2020. Uh We look at this really is being able to deliver a cloud managed services in addition to technology that ceos around themselves. But those, those will probably be the three that stand out to me at least in 2020 we've seen, >>so matt take us through in your minds and red hats, perspective the workloads that are going to be highlighted in this cloud native surge that's happening. We're seeing it everywhere. You mentioned edge industrial edge to consumer Edge to lightweight, edge, massive new workloads. So take us through how you see kind of the existing workloads evolving and potentially new workloads that emerging. >>Yeah. So I think um you know first when you talk about edge workloads a big umbrella but if you look at data driven workloads, especially in the machine learning artificial intelligence spectrum of that, that's really critical. And a reason that those workloads are important is five G. Aside for now when you're running something at the edge you have to also be able to make decisions pretty well at the edge. And that that is that's where your data is being generated and the ability to act on that closely. Whether that's executing machine learning models or being able to do more than that with A I. That's going to be a really really critical workload. Uh huh. Coupled to that, we will see I think five G. Change that because you're going to see more blending in terms of what can you draw back to uh closer to your data center to augment that. So five G will shift how that's built but data driven workloads are going to be huge then I think another area will see is how you propagate that data through environment. Some Kafka has been a really popular technology will actually be launching a service in relation to that. But being able to get that data at the edge and bring it back to locations where you might do more traditional processing, that's going to be another really key space. Um and then we'll still have to be honest, there is still a tremendous amount of work loads out there that just aren't going to get rebuilt. And So being able to figure out how can you make them a little more cloud native? You know, the things your companies have run on for the last 20 years, being able to step them closer to cloud native, I think it's going to be another critical focus because he can't just rewrite them all in one phase and you can't leave them there as well. So being able to bridge shadow B T to >>what's interesting if folks following red hat, No, no, you guys certainly at the tech chops you guys have great product engineering staff been doing this for a long time. I mean the common Lennox platform that even the new generation probably have to leave it load limits on the server anymore. You guys have been doing this hybrid environment in I T for I T Sloan for decades. Okay. In the open, so, you know, it's servers, virtualization, you know, private, public cloud infrastructures and it's been around, we've been covering it in depth as you know, but that's been, that's a history. But as you go from a common Lennox platform into things with kubernetes as new technologies and this new abstraction layers, new control plane concept comes to the table. This need for a fully open platform seems to be a hot trend this year. >>How do you >>describe that? Can you take a minute to explain what this is, this is all about this new abstraction, this new control plane or this open hybrid cloud as you're calling? What is this about? What does it mean? >>Yeah, no, I'll do a little journey that she talked about. Yeah. This has been our approach for almost a decade at this point. And it started, if you look at our approach with Lennox and this was before public clouds use migrants existed. We still with Lennox tried to span bare metal and virtualized environments and then eventually private and public cloud infrastructure as well. And our goal there was you want to be able to invest in something, um, and in our world that's something that's also open as in Lennox but be able to run it anywhere. That's expanded quite a bit. That was good for a class of applications that really got it started. That's expanded now to kubernetes, for example, kubernetes is taking that from single machines to cluster wide deployments and it's really giving you that secure, flexible, fast innovation backbone for cloud native computing. And the balance there is just not for cloud native, we've got to be able to run traditional emerging workloads and our goal is let those things run wherever rail can. So you're really, you're based on open technologies, you can run them wherever you have resources to run. And then I think the third part of this for us is uh, having that choice and ability to run anywhere but not being able to manage. It can lead to chaos or sprawl and so our investments in our management portfolio and this is from insights the redhead advanced cluster management to our cluster security capabilities or answerable. Our focus has been securing, managing and monitoring those environments so you can have a lot of them, you can run where you want, but she just sort of treat it as one thing. So you are our vision, how we've executed up to this point has really been centered around that. I think going forward where you'll see us um really try to focus is, you know, first you heard paul announced earlier that we're donating more than half a billion dollars to open. I would cloud research and part of this reason is uh running services. Cloud native services is changing. And that research element of open source is incredibly powerful. We want to make sure that's continuing but we're also going to evolve our portfolio to support this same drive a couple areas. I would call out, we're launching redhead open shift platform plus and I talked about that combination from rail to open shift to being able to manage it. We're really putting that in one package. So you have the advanced management. So if you have a huge suites of cloud native real estate there, you can manage that. And it also pushes security earlier into the application, build workflows. This is tied to some of our technology is bolstered by the stack rocks acquisition that we did. Being able to bring that in one product offering I think is really key to address security and management side. Uh we've also expanded Redhead insights beyond Rehl to include open shift and answerable and this is really targeted it. How do we make this easier? How do we let customers lean on our expertise? Not just for Lennox as a service, but expand that to all of the things you'll use in a hybrid cloud. And then of course we're going to keep pushing Lennox innovation, you'll see this with the latest version of red hat enterprise, like so we're gonna push barriers, lower barriers to entry. Uh But we're also going to be the innovation catalyst for new directions include things like edge computing. So hopefully that sort of helps in terms of where, where we started when it was just Lennox and then all the other pieces were bringing to the table and why and some new areas. Uh We're launching our investment going forward. >>Yeah, great, that's great overview. Thanks for taking the time to do that. I think one of the areas I that's jumping out at me is the uh, advanced cluster management work you guys are doing saw that with the security peace and also red hat insights I think is is another key one and you get to read that edge. But on the inside you mentioned at the top of this interview, data workloads pretty much being, I mean that pretty much everything, much more of an emphasis on data. Um, data in general but also, you know, serve abilities a hot area. You know, you guys run operating system so you know, in operating systems you need to have the data, understand what's being instrumented. You gotta know that you've got to have things instrument and now more than ever having the data is critical. So take us through your vision of insights and how that translates. Because he said mentions in answerable you're seeing a lot more innovations because Okay I got provisions everything that's great. Cloud and hybrid clouds. Good. Okay thumbs up everyone check the box and then all of a sudden day too As they call day two operations stuff starts to, you know, Get getting hairy, they start to break. Maybe some things are happening. So day two is essentially the ongoing operational stability of cloud native. You need insights, you need the data. If you don't have the data, you don't even know what's going on. You can't apply machine learning. It's kind of you if you don't get that flywheel going, you could be in trouble. Take me through your vision of data driven insights. >>Yeah. So I think it's it's two aspects. If you go to these traditional traditional sport models, we don't have a lot of insight until there's an issue and I'm always amazed by what our teams can understand fix, get customers through those and I think that's a lot of the success red hats had at the same note, we want to make that better where if you look at real as an example, if we fixed an issue for any customer on the planet of which we fix a lot in the support area, we can know whether you're going to hit that same issue or not in a lot of cases and so that linkage to be able to understand environments better. We can be very proactive of not just hey apply all the updates but without this one update, you risk a kernel panic, we know your environment, we see it, this is going to keep you out of that area. The second challenge with this is when things go do break or um are failing the ability to get that data. We want that to be the cleanest handshake possible. We don't want to. Those are always stressful times anyway for customers being able to get logs, get access so that our engineering knowledge, we can fix it. That's another key part. Uh when you extend this to environments like open shift things are changing faster than humans can respond in it. And so those traditional flows can really start to get strained or broken broken down with it. So when we have connected open shift clusters, our engineering teams can not only proactively monitor those because we know cooper net is really well. We understand operators really well. Uh we can get ahead of those issues and then use our support teams and capabilities to keep things from breaking. That's really our goals. Finding that balance where uh we're using our expertise in building the software to help customers stay stable instead of just being in a response mode when things break >>awesome. I think it's totally right on the money and data is critical in all this. I think the trust of having that partnership to know that this pattern recognition is gonna be applied from the environment and that's been hurting the cybersecurity market people. That's the biggest discussion I had with my friends and cyber is they don't share the data when they do, things are pretty obvious. Um, so that's good stuff there and then obviously notifications proactive before there's a cause or failure. Uh great stuff. This brings up a point that paul come here, said earlier, I want to get your reaction to this. He said every C. I. O. Is now a cloud operator. >>That's a pretty bold >>statement. I mean, that's simply means that it's all cloud all the time. You know? Again, we've been saying this on the queue for many years, cloud first, whatever people want to call it, >>what does that actually >>mean? Cloud operator, does that just mean everything's hybrid? Everything's multiple. Cloud. Take me through an unpacked what that actually means? >>Yeah. So I think for the C I O for a lot of times it was largely a technology choice. So that was sort of a choice available to them. And especially if you look at what public clouds have introduced, it's not just technology choice. You're not just picking Kafka anymore. For example, you really get to make the choice of do I want to differentiate my business by running it myself or is this just technology I want to consume and I'm going to consume a cloud, native service and other challenges come with that. It's an infrastructure, not in your control, but when you think about a ceo of the the axes they're making decisions on, there are more capabilities now and I think this is really crucial to let the C i O hone in on where they want to specialist, what do they want to consume, what do they really want to understand, differentiate and Ron? Um and to support this actually, so we're in this vein, we're going to be launching three new managed cloud services and our our focus is always going to be hybrid in these uh but we understand the importance of having managed cloud services that red hat is running not the customers in this case. So one of those will be red hat open shift streams for Patrick Kafka. We've talked about that, that data connectivity and the importance of it and really being able to connect apps across clouds across data centers using Kafka without having to push developers to really specialize in running. It is critical because that is your hybrid data, it's going to be generated on prim, it's going to be generated the edge, you need to be able to get access to it. The next challenge for us is once you have that data, what do you do with it? And we're launching a red hat open shift data science cloud service and this is going to be optimized for understanding the data that's brought in by streams. This doesn't matter whether it's an Ai service or business intelligence process and in this case you're going to see us leverage our ecosystem quite a bit because that last mile of AI workloads or models will often be completed with partners. But this is a really foundational service for us to get data in and then bring that into a workflow where you can understand it and then the last one for us is that red hat open shift api management and you can think of this is really the overseer of how apps are going to talk to services and these environments are complex, their dynamic and being able to provide that oversight up. How should my apps be consuming all these a. P. S, how should they be talking? How do I want to control? Um and understand that is really critical. So we're launching these, these three and it fits in that cloud operator use, we want to give three options where you might want to use Kafka and three Scale technologies and open data hub, which was the basis of open shift data sides, but you might not want to specialize in running them so we can run those for you and give you as a C. I. O. That choice of where you want to invest in running versus just using it. >>All right, we're here with matt Hicks whose executive vice president prospect technology at red hat, matt, your leader at red hat now part of IBM and continues to operate um in the red hat spirit, uh innovating out in the open, people are wearing their red hat uh hoodies, which has been great to see. Um I ask every executive this question because I really want to get the industry perspective on this. Um you know, necessity is the mother of invention as the saying goes and, you know, this pandemic was a challenge for many In 2020. And then as we're in 2021, some say that even in the fall we're gonna start to see a light at the end of the tunnel and then maybe back to real life in 2022. This has opened up huge visibility for CSOS and leaders and business in the enterprise to say, Hey, what's working, what do we need? We didn't prepare for everyone to be working at home. These were great challenges in 2020. Um, and and these will fuel the next innovations and achievements going forward. Um again necessity is the mother of all invention. Some projects are gonna be renewed and double down on some probably won't be as hybrid clouds and as open source continues to power through this, there's lessons to be learned, share your view on what um leaders in in business can do coming out of the pandemic to have a growth strategy and what can we learn from this pandemic from innovation and and how open source can power through this adversity. >>Yeah. You know, I think For as many challenging events we had in 2020, I think for myself at least, it it also made me realize what companies including ourselves can accomplish if we're really focused on that if we don't constrain our thinking too much, we saw projects that were supposed to take customers 18 months that they were finishing in weeks on it because that was what was required to survive. So I think part of it is um, 2020 broke a lot of complacency for us. We have to innovate to be able to put ourselves in a growth position. I hope that carries into 2021 that drives that urgency. When we look at open source technologies. I think the flexibility that it provides has been something that a lot of companies have needed in this. And that's whether it could be they're having to contract or expand and really having that moment of did the architectural choices, technology choices, will they let me respond in the way I need? Uh, I'm biased. But first I think open models, open source development Is the best basis to build. That gives you that flexibility. Um, and honestly, I am an optimist, but I look at 2021, I'm like, I'm excited to see what customers build on sort of the next wave of open innovation. I think his life sort of gets back to normal and we keep that driving innovation and people are able to collaborate more. I hope we'll see a explosion of innovation that comes out and I hope customers see the benefit of doing that on a open hybrid cloud model. >>No better time now than before. All the things are really kind of teed up and lined up to provide that innovation. Uh, great to have you on the cube. Take a quick second to explain to the folks watching in the community What is red hat 2021 about this year? And red hat someone, I'll see. We're virtual and we're gonna be back in a real life soon for the next event. What's the big takeaway this year for the red hat community and the community at large for red hat in context of the market? >>You know, I think redhead, you'll keep seeing us push open source based innovation. There's some really exciting spaces, whether that is getting closer and closer towards edge, which opens up incredible opportunities or providing that choice, even down to consumption model like cloud managed services. And it's in that drive to let customers have the tools to build the next incredible innovations for him. So, And that's what summit 2021 is going to be about for us, >>awesome And congratulations to, to the entire team for the donation to the academic community, Open cloud initiative. And these things are doing to promote this next generation of SRS and large cloud scale operators and developers. So congratulations on that props. >>Thanks john. >>Okay. Matt Hicks, executive vice president of products and technology. That red hat here on the Cube Cube coverage of red hat 2021 virtual. I'm John Ferrier. Thanks for watching. Yeah.

>>mhm Yes. >>Welcome back to the cubes coverage of red hat summit 2021 virtual. I'm john for a host of the cube we're here in Palo alto. Were remote with our great guest here cube alumni. I've been on many times chris wright, Senior vice president and CTO of red hat chris great to see you. Always a pleasure to have you on the screen here too. But we're not in person but thanks for coming in remote. >>Yeah, you bet. Glad to be here. >>Not only were talking about speeds and feeds, digital transformation going under the hood here we're gonna talk about red hats, expanded collaboration with boston University to help fund education and research for open source projects. So you guys have a huge relationship with boston University. Talk about this continued commitment. What's the news, what's the, what's the story? >>Well, we have a couple different things going on uh and and the relationship we have with the EU is many years in. So this itself isn't brand new. Um one of the things that's important to highlight here is we are giving something north of $550 million dollars worth of software to be you really in pursuit of running uh powering and running scaled infrastructure. That's part of the open hybrid class. Um and that's that's an important piece which we can touch on a little bit as we talk to this conversation. The other one is like I said, this isn't a new relationship with the U. And what we're doing now is really expanding the relationship. So we've we've built a great connection directly with the You were substantially expanding that. Um The original relationship we had was a $5 million relationship spread over five years now. We're talking about a $20 million Relationship spread over five years. So really a significant expansion. And of course that expansion is connected to some of the work that we plan to do together in this open hybrid cloud infrastructure and research space. So a lot of things coming together at once to really really advance the red hat ca laboratory at the U. That combined effort in bringing you know, cloud research and open source and all these things together >>and a lot of actually going on. So basically the boston area lot of universities, but I love the shirt you're wearing with his red hat innovation in the open. This is kind of one of those things you also mentioned out of this huge subscription of software grant that's going to be you just a huge number give value for for the boston University. But you also have another project that's been going on the collaborative research and education agreement called red hat collaborative orI Okay, this was in place. You mentioned that. How's that tying in because that was pre existing. Now. You've got the grant, you got your funding more and more research. Talk about how this connects into the open cloud initiative because this is kind of interesting. You're not bringing hybrid cloud kind of research and practical value in A i ops is hot. You can't you can't go anywhere these days without having great observe ability. Cloud native more and more is more complex and you've got these young students and researchers dying and get their hands on it. Take us through the connection between the CA laboratory and open open cloud. >>So the CA laboratory is a clever name that just talks about collaboration and research laboratory type research. And initially the CA laboratory focus was on the infrastructure running the cloud and some of the application workloads that can run on top of an open cloud infrastructure uh that are that's very data centric. And so this is uh an opportunity for multidisciplinary work looking at modeling for um for health care, for example for how you can improve imaging and we've had a great results in this collaboration. Um We've talked at times about the relationship with the boston Children's Hospital and the chris project not related to me, but just similar acronym that spells chris. Um and these things come together in part through connecting relationships to academia, where academia as research is increasingly built in on and around open source software. So if you think of two parallel worlds, open source software development, just the activity of building open source software, it brings so many people together and it moves so quickly that if you're not directly connected to that as an academic researcher, you risk producing academic research results that aren't relevant because it's hard for them to connect back to these large, fast moving projects, which may have invented a solution to the problem you've been focused on as an academic if you're not directly connected. So we see academia and open source coming together to build really a next generation of understanding of the scientific in depth and he's joining the >>train operations you're talking about here though, this is significant because there's dollars behind it, right? There's real money, it's not >>just the right software, >>it's it's a center, it's a joint operation. >>That's right. And so when you think about just the academic research of producing um ideas that manifest themselves as code and software projects, we want to make sure we're first connecting the software projects to open source communities in with our own engineering experience, bringing code into these open, open source projects to just advance the the feeds and speeds and speeds, the kind of functionality the state of the art of the actual project. We're also taking this to a new level with this expanded relationship and that is software today. When you, when you operate software as a cloud, a critical part of the software is the operationalization of that software. So software just sitting there on the shelf doesn't do anybody any good. Even if the shelf is an open source project, it's a tar ball waiting for you to download. If you don't ever grab it and run it, it's not doing anybody any good. And if the challenge of running it is substantial enough that it stops you from using that software, you've created a barrier to the value that's locked inside that project. The focus here is how can we take that the operations experience of running a cloud, which itself is a big complex distributed system, tie some of those experiences back into the projects that are used to build that infrastructure. So you're taking not just the output of the project, but also the understanding of what it takes to run a project and bringing that understanding and even the automation and code associated with that back into the project. So, your operational izing this open source software and you're building deeper understanding of what it means to operate things that scale, including data and data sets that you can use to build models that show how you can create the remediation and closed loop systems with AI and machine learning, you know, sort of synthesizing all the data that you generate out of a big distributed infrastructure and feed that back into the operations of that same infrastructure. So a lot going on there at the same time operationalization as as an open source initiative but also um really the understanding advancement of A I and data centric operations, so ai ops and closed the remediation. >>Yeah, I mean, devops developer and operations to operationalize it and certainly cloud Native put an emphasis on Day two operations, which leads a lot more research, a lot more uh student work on understanding the coding environment. Um so with that I got to ask um I asked you about this uh massachusetts focused or this open cloud initiative because you guys are talking about this open cloud initiative including this massachusetts. Open Cloud, what is that? What is the massachusetts? Open Cloud sounds like you're offering a kind of open person, not just bu but other um Yeah, institutions. >>That's right. So the the M o C massachusetts open cloud is itself a cross um organizational collaboration bringing together five different academic institutions in New England In massachusetts. It's bu it's Harvard mit, its Northeastern and its U. Mass. Coming together to support a common set of infrastructure which is cloud. It's a cloud that runs in a data center and then um it serves a couple of different purposes. One is research on clouds directly. So what does it mean to run a cloud? What does it look like from a research point of view to understand large scale distributed systems? And then the other is more on top. When you have a cloud you can run workloads and those workloads scaled out to do say data processing, looking at the implications of across different fields which could be natural sciences, could be medicine, could be, even political science or social science is really a multidisciplinary view of what it means to leverage a cloud and run data centric workloads on top. So two different areas that are of a focus for the M. O. C. And this becomes this sort of vehicle for collaboration between Red Hat View and the Red Hot Laboratory. >>So I have to ask only because I'm a big fan of the area and I went to one of those schools, is there like a bean pot for technical hackathons where you get all the schools matched up against each other on the mass open cloud and compete for who gets bragging rights and the text city there. >>It's a great question. Not yet. But I'll jot that down here in hell. Up on that. >>Happy to sponsor. We'll we'll do the play by play coverage, you know. Great. >>I love that. Yeah, kind of twitch tv style. The one thing that there is which is very practical is academic research grants themselves are competitive, right? People are vying for research dollars to put together proposals, Bring those proposals to um the agency that's that's that's giving out grants and winning those grants is certainly prestigious. It's important as part of her research institutes continue to fund the work that they're doing. Uh Now we've been associated uh through the work we've done to date with the U. With Yeah almost $15 million 20 papers. So there's there's a lot of work you can't quite call the play by play. It's a >>scoreboard. I mean their numbers you can put numbers on the board. I mean that's what's one of the things you can measure. But let me ask you on those grants. So you're saying this is just the bu you guys actually have data on um the impact of the relationship in terms of grants and papers and stuff like that academic work. >>That's right. That's right. And so those numbers that I'm giving you are examples of how we've worked together with the u to help their faculty generate grant dollars that then fund some of the research that's happening there together with redhead engineers and on and on the infrastructure like the massachusetts Open cloud. >>That's a good way to look at the scoreboard. It's a good point. We have to research that if you don't mind me asking on this data that you have um are all those projects contributing to open source or do they have to be? That's just generic. Is that all of you all papers around bu is part of the research. In other words, I'm trying to think if I'm in open source, has this contributed to me as an >>open source? Yeah, it's a big and complex question because there's so much research that can happen through a research institution. And those research grants tend to be governed with agreements and some of those agreements have intellectual property rights um front and center and might require things like open source software as a result, the stuff that we're working on clearly isn't that focus area of open source software and and research activities that help kind of propel our understanding forward of what does it mean to do large scale distributed systems creation and then operation. So how do you develop software that does it? How do you how do you run the software that builds these big large distributed systems? So we're focused in that area. Um some of the work that we facilitated through that focus includes integrating non open source software that might be part of um same medical imaging. So for example work we've done with the boston Children's Hospital That isn't 100 doesn't require us to be involved 100 of the open source pieces. All the infrastructure there to support it is. And so we're learning how we can build integrated pipelines for data analysis and image analysis and data sharing across different institutions uh at the open source project level. Well maybe we have a specific imaging program that is not generated from this project. And of course that's okay with >>us. You know chris you bring up a good point with all those conversations. I could see this really connecting the dots. Most computer science programs. Most engineering programs haven't really traditionally focused on it at the scale we're talking about because we look at cloud scale but now scaling with hybrid it's real engineering going on to think about the large scale. We know all the big hyper scale ear's right so it's not just I. T. Provisioning you know network connection and doing some I. T. Work. We're talking about large scale. So I have to ask you as you guys look at these relationships with academics uh academia like like bu and others um how are the students responding to this? Are you guys seeing any specific graduate level advancements? Because you're talking about operational roles that are becoming so important whether it's cyber security and as cloud needed because once more data driven you need to have all this new scale engineered up. That's >>what how >>do you look at that? >>There's two different pieces that I would highlight. One is just the data science itself. So schools still need to produce data scientists. And having data is a big part of being a data scientist and knowing what your what your goals are with that data and then experimenting with different techniques, whether it's algorithms or tools. It's a big part of being a data scientist sort of spelunking through the data. So we're helping produce data. We're looking at data science efforts around data that's used to operationalize infrastructure, which is an interesting data science endeavor by itself. The other piece is really what you highlighted, which is there's an emergence of a skill set in the industry, often referred to as SRE site reliability engineering. Um it is a engineering discipline. And if you back up a little bit and you start thinking about what are the underlying principles behind large scale distributed systems, you get to some information theory and computer science. So this isn't just something that you might think of as um some simple training of a few key tools and knowing how to interpret a dashboard. And you're good to go, this is a much more sophisticated view of what does it mean to really operate large scale infrastructure, which to date, there aren't a lot of these large scale infrastructures available to academics to research because their commercial endeavors >>and their new to me. I was talking to some young folks my son's age and daughters age and I was saying, you know, architect in a building, a skyscraper isn't trivial. You can't just do that overnight. There's a lot of engineering that goes on in that science, but you're bringing kind of operating systems theory, systems thinking to distributed computing. I mean that's combination of a interdisciplinary shift and you got, I won't say civil engineering, but like concept is there, you've got structure, you've got networks, they're changing and then you've got software so again completely new area. >>That's right and there's not a lot of even curriculum that explores this space. So one of the opportunity, there's a great program that really focuses on um that that space of site reliability engineering or operational izing software. Um And then the other piece that I'm I'm really excited about is connecting to open source communities so that as we build software, we have a way to run and operationalize that software that doesn't have to be directly tied to a commercial outlet. So products running in the cloud will have a commercial S. L. A. And commercial agreements between the user and the producer of that service. How do you do that in open source context? How do you leverage a community, bring that community software to a community run service, learn through the running of that service. How to best build architect the service itself and then operationalized with the tooling and automation that service? How do you, how do you bring that into the open source community? And that's something that we've been referring to as the operate first initiative. How do you get the operationalization of software? Really thought of as a primary focal point in the software project where you normally think about the internals of software, the features, the capabilities of functionality, less about the operationalization. So important shift at the open source project level, which is something that I think will really be interesting and we'll see a lot of reaping a lot of rewards. Just an open source communities directly. >>Yeah, speed and durability. Certainly having that reliability is great. You know, I love talking with you guys at red hat because, you know, software, you know, open source and you know, operating systems because as it comes together in this modern era, what a great, great fit, great work you're doing with Boston University's and the mass open cloud initiative. Congratulations on that. I got I got to ask you about this Red Hat Graduate Fellows program you have because this kind of speaks to what you guys are doing, you have this kind of this redhead graduate fellows network and the work that's being done. Does that translate into red hat at all? From an engineering standpoint? How does that, how does that work together? >>Basically, what we do is we support um PhD students, we support post docs. So there's a real direct support to the, you know, that is the Red Jack Graduate Fellow program on our focus there is connecting those um uh academics, the faculty members and the students to our engineers to work together on key research initiatives that we think will help drive open source software agendas forward really broad can be in all different areas from security to virtualization too, the operating systems to cloud distributed systems, uh and one of the things that we've discovered is it creates a great relationship with the university and we find students that will be excited to leave university and come into the the industry workforce and work at Red hat. So there is a direct talent relationship between the work that we do at bu and the talent that we can bring into red hat, which is awesome. Uh We know these people we've worked with well with them, but also we're kind of expanding understanding of open source across, you know, more and more of academia, which I think is really valuable and important for red hat. We just go out to the the industry at large, um, and helping bring a set of skills to the industry that whether they're coming, whether these are students that come into red hat or go elsewhere into the industry, these are important skills to have in the industry. So we look at the, how do you work in open source communities? How to operationalize software at scale? These are important things. They didn't >>expand, expand the territory if you will in terms of systems thinking. We just talked about great collaboration. You guys do a great job chris great to have you on a quick final word from you on this year at red hat summer. I know it's virtual again, which we could be in person, but we're starting to come out of the covid kind of post covid right around the corner. Um, what's the update? How would you describe the current state of red hat? Obviously you guys still got that, that vibe. You still pumping strong a lot going on. What's the current? What's the current, uh, bumper sticker? What's the vibe? >>Well, in many ways, because we're so large and distributed. Um, the last year has been, uh, can't say business as usual because it's been an impact on everybody, but it hasn't required us to fundamentally change. And as we work across open source communities, there's been a lot of continuity that's come through a workforce that's gone completely distributed. People are anxious to get to the next phase, whatever back to normal means. Uh, and people at Red Hat are no different. So we're looking forward to what it can mean to spend time with colleagues in offices, were looking forward to what it means to spend time together with our friends and families and travel and all those things. But from a, from a business point of view, Red Hat's focus on the open hybrid cloud and that distributed view of how we work with open source communities. That's something that's, it's only continued to grow and pick up over the course of the last year. So it's clearly an important area for the industry and we've been busier than ever the last year. So, uh, interesting, interesting times for everybody. >>Well, it's great to see and I love how the culture maintains its its relevance, its coolness intersection between software, Open Source and systems. Great, Great working congratulations chris. Thanks for coming on. >>Thank you. >>All right. I'm John for here with the Cube for Red Hat Summit 2021. Thanks for watching. Mhm.

>>mhm >>Yes, >>everyone welcome back to the cubes coverage of Red Hat summit 2021. I'm john for your host of the cube, 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, uh Darryl, great to see you. Thanks for coming back on the cube. >>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 is coming back soon, although I hear mobile world congress might be in person this year looking like it's good a lot of people gonna be virtual 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 um the edge, talking about five G talking about industrial benefits for business because it's not just Edge for connectivity access. We're talking about internet of 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 rail, open shift men and services. Everything about the cloud native underpinnings you guys have been successful as a company but now in your area, telco is being disrupted. Absolutely. Give us your take on this is super exciting. >>Well, it's actually one of the most exciting times I've been in the industry for 30 years are probably aging myself now. But in the telecommunications industry, this, for me is the most exciting. It's where 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 our platform and as you mentioned IOT and a number of the other ai and Ml innovations that are occurring in the market place. We're going to see a new wave of applications and innovation. >>What's the key delivery workloads you're seeing with Five G environment? Um, obviously it's not just, you know, five G in the sense of thinking about mobile phones or mobile computers as they are now. Um, it's not just that consumer, hey, surf the web and check your email and get an app and download and communicate. It's bigger than that. Now, can you tell us Where you see the workloads coming in on the 5G environment? >>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 in that take 20 seconds less, but you're not going to pay an awful lot more money for that. The real opportunity around five years, the industrial applications, things that I connected car, automotive, driving, um 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 in five G one is under the hood, networking, you know, what's going on with the moving the packets around the workload, throughput, bandwidth etcetera, and all 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 weaving. So let's take the first part first. Um open shift is out there. Red hat's got a lot of products, but you have to nail the networking requirements and cloud Native with container ization because at large scales, not just packaged, it's all kinds of things going on security, managing a 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 hats doing in that area? >>So when we last spoke with the cube, we talked a lot about GMOs and actually people living Darryl, >>can I Cause you really quickly? I'm really sorry. Keep your answer in mind. We're gonna >>go right from that question. >>We're just kidding. Um, are you, is anything that you're >>using or touching running into the desk? We're just getting >>a little bit of shakiness on your camera >>and I don't want to. >>So anyway, >>that is my, my elbows. No worries. So no >>worries. Okay, so take your answer. I'll give you like a little >>321 from behind the scenes >>and and we'll go right as if >>john just ask >>the questions, we're gonna stay running. >>So I think, uh, >>can you ask the question just to get out of my mind? Perfect. Well let's, let's do >>from that. So we'll stay on your shot. So you'll hear john, but it'll be as if >>he just asked the question. So jOHn >>team up. Here we go. I'm just gonna just jimmy and just keep my other question on the okay, here we go. So Darryl, open shift is optimized for networking requirements for cloud native. It's complex into the hood. What is red hat doing under the hood to help in the edge in large complex networks for large scale. >>Yeah. So, so that's a very good question in that we've been building on our experience with open stack and the last time I was on the cube, 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 open stack 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 app lets across the cloud, but in some instances running on multiple clouds at the same time. So we're building on our experience from open stack, we're bringing all of that into open shipping, container based environment with all of the tallinn necessary to make that effective. >>It's interesting with all the automation going on. Certainly with the edge developing nicely the way you're describing it, certainly disrupting the Telco cloud, you have an operator mindset of cloud Native operator thinking, kind of, 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 you guys been saying, the C I O is the new cloud operator, That's the skill set they have to be thinking and certainly to anyone else provisioning and managing infrastructure has to think like an operator, what's your >>view? They certainly do need anything 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 will 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 open shift is one element of that operations in terms of management and orchestration and all the tooling that we actually also providers red hat but also in conjunction with a big partner ecosystem, such as companies like net cracker, for example, or IBM as another example or Erickson bringing their automation tool sets and their orchestration tool sets of that whole equation to address exactly that problem >>you bring up the ecosystem. And this is really an interesting point. I want to just hit on that real quick because 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're starting to see that now and where this ties into here I think is when we get your reaction to this is that, you know, moving to the cloud was all about 2 2015. Move to the cloud moved to the cloud cloud native. Now it's all about not only being agile and better performance, but you're gonna have smaller footprints with more security requires more enterprise requirements. This is now it's more complicated. So you have to kind of make the complications 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 an agile, smaller footprint grade security enabling other people to participate. That's a requirement. Can you share your reaction to that? >>Well, that's the core of what we do. A 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 applications services certified, running on our platform, but but also importantly is certified to be running in conjunction with other cloud native applications that sit over the same cloud. So that that is not trivial to achieve in any stretch of the imagination. And a lot of 80 technology skills come to bear. And as you mentioned earlier, a lot of networking skills, things that we've learned and we've built with a lot of these traditional vendors, we bring that to the marketplace. >>You know, I've been saying on the cube, I think five years ago I started talking about this, it was kind of a loose formulation, I want to get your reaction because you brought up ecosystem, you know, saying, you know, you're gonna see the big clouds develop out. The amazon Microsoft came in after and now google and others and I said there's gonna be a huge wave of of what I call secondary clouds and you see companies like snowflake building on 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 C. S. P. S, 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 platform called open shift which is a containerized based platform, but it's not just a container. It involves huge amounts of tooling associated with operating it, developing and around it. So the concept that we have is that you can bring those applications, developed them once on 11 single platform and run it on premise. You can run it natively as a service in Microsoft environment. You can actually run it natively as a service in amazon's environment. You can running natively on IBM's Environment. You can build an application once and run it in all of them depending on what you want to achieve, who actually provide you the best, owning the best terms and conditions the best, the best tooling in terms of other services such as 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 developing ecosystem to drive innovation through applications on that common platform. >>So assumption there is that's going to drive down costs. Can you why that benefits the economics are there? We talk about the economics. >>Yeah. So it does drive down costs a massive important aspect but more importantly it drives up agility. So time to market advantages actually attainable for you so many of the tell coast but they deploy a network service traditionally 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 data 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 five G networks, service providers or telcos in this instance will be able to deliver services all the way out to the edge into that private five G environment and operate that in conjunction with those enterprise clients. >>So open shit allows me if I get this right on the CSP to run, have a horizontally scalable organization. Okay. From a unification platform standpoint. Okay, well it's 5G and other functions, is that correct? That's correct. Ok. So you've got that now, now I want to come in and bring in the top of the stack or the other element. That's been a big conversation here at Redhead Summit and in the industry that is A I 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 special is um of the data and have that domain expertise. Uh you're in the industries for red hat. This is important because you're gonna have one industry is going to have different jargon, different language, different data, different KPI S. So you've got to have that domain expertise to enable the ability to write the apps and also enable a I can, you know how that works and what were you doing there? >>So we're developing open shift and a number of other of our technologies to be fit for the edge of the network where a lot of these Ai applications will reside because you want them closer to the client or the the application itself where it needs to reside. 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 mind sphere, we recently announced with Seaman's 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 results with lower, lower levels of imperfections as they run through that system and 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 health care and you can imagine how you actually interface with your health care 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 common errors associated with different x rays to. A 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 science is different data models. And what we're seeing is an ecosystem of companies that are starting up there in that space that we have, what service part of IBM. But you have processed the labs of H T H 20 and a number of other very, very important AI based companies in that ecosystem. >>Yeah. And you get the horizontal scalability of the control plane and in the platform if you will, that gives you cross organizational leverage uh and enable that than vertical expertise. >>Exactly. And you want to build an Ai application that might run on a factory floor for for certain reasons to its location and what they're actually physically building. You might want to run their on premise, you might actually want to put it into IBM cloud or in Zur or into AWS, You develop, it wants to open shift, you can deploy it in all of those as a service sitting natively in those environments. >>Darrell, great chat. I got a lot going on telco cloud, There's 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. Well, no, and the scoreboard will be very clear because 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 to more areas that are hot here at red hat summit 21 as well again and as well in the industry and get your reaction and thoughts on uh, and they are def sec ops and automation. Okay. Two areas. Everyone's talking about DEV ops which we know is infrastructure as code programming ability under the hood. Modern application development. All good. Yeah, the second their security to have sex shops. That's critical automation is continuing to be the benefits of cloud native. So Deb see cops and automation. What you're taking has that impact the telco world in 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 chris pickling mrs actually even life saving or life threatening if you don't get them right. So the acquisition that red hat recently made around stack rocks, really helps us make that next level of transition into that space. And we're looking about how we go about securing containers in a cloud native environment. As you can imagine, there will be many, many thousands tens of thousands of containers running if one is actually misbehaving for what one of a better term that creates a security risk in a security loophole. Were assuring that up that's important for the deployment, open shift in the Tokyo domain and other domains in terms of automation. If you can't do it at scale and if you look at five G and you look at the radios at the edge of the network and how you're gonna provision of those services. You're talking about hundreds of thousands of nodes, hundreds of thousands. 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, Darryl, this is a great conversation, you know, as a student of history and um development and I always kind of joke about that and you you've been around the industry for a long time. Telcos have been balancing this um evolution of digital business for many, many decades. Um and now with Cloud Native, it's finally a time where you're starting 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 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 clarify and how they be positioned for success. >>So, so one of the things 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 gonna sit elsewhere, then there might be a killer application that one telco might create. But in reality most of those innovations that 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 60 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 in our view, red hat innovation. If you're open, 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 >>and there's a lot, there's a lot of upside there if you get that right, there's plenty of upside, a lot of leverage, a lot of assets to advantage 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 Darryl, how would you describe that learnings from the pandemic as folks start to come out of the pandemic? There's a light at the end of the tunnel as we come out of this pandemic, companies want a growth strategy, wanna be positioned for success what you're learning coming out of the pandemic. >>So from my perspective, which really kind of 11 respect was was very admirable. But another respect is actually deeply uh a lot of gratitude is the fact that the telecommunications companies because of their carrier, great 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 and with extremely well. Um 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 at a time 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 enough 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're also everyone's going through. So I think there are some key learnings that >>yeah, I think you're right on the money there. It's like they pulled the curtain back of all the fun and said necessity is the mother of invention and when you look at what happened and what had to happen to survive in the pandemic and be functional. Your, 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 the 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. Darrell Jordan smith, senior vice president of industries and global accounts for red hat kibble, unnatural. 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 the cubes coverage of Red Hat summit 21. I'm John for your host. Thanks for watching. Mhm mhm

>>lost myself. >>You know, one of the things that I love about the Cuba being doing it for 11 years now is that everyone that we interviewed years and years ago, they all getting promoted. So much fun to watch everyone grow and and now it's stews over there now so it's fun to get to do something. When >>are you gonna, are you gonna get to interview stew for? Way >>to put them on the hot seat? I think he's afraid actually >>throughout all the talking points. Right. 1st question. The way >>we do miss too. I will say that it is amazing. Okay, I'm ready to go. >>Red >>Hat Summit read. Pat Summitt, we're coming to you in. Hello and welcome back to the Red Hat Summit 2021 virtual coverage I'm john for is the cube coverage of Palo alto with the remote interviews for our virtual conference. You've got two great guests cube alumni's Tom Anderson VP of answerable automation platform and Robyn Bergeron who's the Senior manager and small community community architect and all the great things involved, Robyn great to see you tom. Thanks for coming back on red hat some of this year. Virtual. Good to see you. >>Thanks for having us. >>So since last summit, what's the updates on the answerable community and the automation platform? Tom we'll start with you automation platform. What's the big updates? >>Yeah. So since the last time a lot has happened in the unanswerable land. If you will also last time that we were talking about constant collections have given distribution format or the integrations that ends this close. So a lot of the content. Uh huh. As well as the commercial users we launched last year a fucking program certified contact program with our partners and including partners to certify the content collections today. Create co certify them where we work together to make sure that they're uh developed against and tested against a proper step so that both of us can provide them to our customer basis with confidence that they're going to be working informed broccoli and that we red hat and our partners co support those out in our customers production parts. That was a big deal. The other thing that we announced late last fall was the private automation hub. And that's the idea where our customers obviously appreciate the idea of being able to go to Ansel Galaxy or the answerable automation to go and grab these content collections. This these integrations and bring them down in their environment. They wanted a way that they wanted a methodology where there are a repository where they can curate content from different sources and then manager across the environment. The automation across their environment. Kind of leaning into a little bit of automation content as code if you will. And um, so we launched the automation of the private automation hub where that sits in our customers infrastructure, whether that's in the cloud or on premises with both, and allows them to grab content from Galaxy from the answer automation. Uh, the answer automation hub on cloud got red hat dot com as well as their internally developed content and to be able to manage and provide that across their organization governed by a set of policies. So lots of stuff is going on real advancement in the amount of content that we provide, uh, the amount of collections that we provide them certified up for customers and and the ability to manage that company across the teams. >>I want to do a drill down on some of the unification of teams, which is a big message as well as operating scale because that's the super value proposition you guys have and want to get that. But robert, I want to come back to you on the community so much has gone on, we are now into the pandemic for almost a year and a half now, um it's been a productivity boom. People, developers have been working at home for a long time, so it's not a new workflow for them, but you've seen a lot more productivity. What has changed in the community since last summit? Again, virtual to virtual again between the Windows here, event Windows, you guys have a lot going on. What's new in the community gets an update? >>Yeah, well, I mean if we go back to summit, you know, this time ish, you know, last year we were wrapping up more or less the, it was, you know, we used to have, you know, everything you would install answerable, you would get all the modules, you get everything, you know, it was all all all together, which, you know, is great for new users who don't want to have to figure things out. It helps them to really get up and started running quickly. Um and But, you know, for a from a community perspective, trying to manage that level of complexity turned out to be pretty hard. So the move to collection was actually great for, you know, not just, you know, for a user perspective, but also from a community perspective. Um and we came out with the answerable to 10 that was last fall, I believe, and that was the first real release advance. Well, where we had, you know, collections were fully in stan she hated uh you know, they were available on Galaxy, but you can also get them as part of the animal community distribution. Um, fast forward to now. You know, we just had the answer to all three point oh release here in february and we're looking to answer bill ford auto here in early May. So, you know, there's been a lot of activity, a lot has improved honestly as a result of the changes that we've made, it's made it a lot easier for contributors to get in with a smaller group that's more of their size and you know, be able to get start and identify, you know, who are, they're interested peers in the community. So that's been a boon for us honestly. Um, you know, the pandemic otherwise is, you know, I think taught all of us, you know, certainly you john about the, the amazing things that we can do virtually. So we've had a lot of our meetups pivot to being virtual meetups and, and things like that. And it's been great to see how, how easily the community's been able to pivot around. You know, this sort of event. Um, I hope that we don't have to just keep practicing it for forever, but in the meantime, you know, it's enabled us to continue to get things done. Thank goodness to every video platform on earth. Yeah, >>well we appreciate we're gonna come back and talk more about that in the future, but best practice what we all learned and stories. But I think I want to come back to you on the persona side of answerable because one of the things we talked about last time that seems to be getting a lot of traction is that multiple personas. So I want to just hold off that will come back tom back to back to you were red hat summit. You guys have an apple fest, which is your own event that you guys drill down on this. So users Washington, you know this, your own community, but now part of red hat part of IBM, which IBM thinks also happening soon as well. Red hat some, it still is unique event. How is answerable fitting into the big picture? Because the, the value proposition of unifying teams is really consistent now with red hats overall arching thing, which is operating at scale open shift Robin just mentioned, where is the automation platform going this year? What's the story here at red hat summit for the automation platform? >>Yeah, that's that's a great question. We've seen so kind of timeless, a little bit of dependent and how it has accelerated some existing trends that we already saw and one of those is really around the democratization of the application delivery teams, more people delivering infrastructure and applications independent of each other, which is right, faster and more agile, all of those other. Good, good uh, words that apply to that. But what that does bring up is the opportunity for um >>patient >>of work, replication of effort, uh not reusing necessary things that are in existence already that other things may have maybe not complying with all of the policies if you will, the configuration and compliance policies. And so it's really kind of brought danceable out into focus even more here because of the car comin back plane that provides a common language and common automation back plane across these different teams and across these different personas. The great thing about what we supply for these different personas, whether its application developers, infrastructure owners, network engineers set up teams, get ox teams, There's so many of these options out there now, All want independent access to infrastructure and deploying infrastructure. And Answerable has the kind of levers that each of those communities, whether it's API or Cli s or event based automation or uh web hooks, et cetera et cetera. You know, service catalog. He lies all of those um interfaces if you will or modalities are accessible into hands of water nations. What's really allowed us to be this sort of connective tissue or blue across these different silos or remains of the organization the time of the year? Open ship specifically one of the things that we talked about last fall and are answerable fest was our integration between Answerable to automation platform are advanced cluster management product and are open ship platform that allows native applications running on open ship. Be able to talk to a sensible automation operator that's running on that same platform to do things off platform for it that our customers are already using. Answer before. So connecting their cloud, native platforms with their existing ecosystems and infrastructures. Systems of records, network systems, uh, ticketing systems, you name it. So all of those sort of integrations and school has become the connected blew across all of these different environments time. Traditional, anti biotic native, you name it. So it's really been it's really been fun and it's been an exciting time for us inside the portfolio. And uh, >>that's a great point connective tissue is a great way to describe some of these platform benefits because you have been on this platform for a really long time and the benefits are kind of being seen in the market. Certainly as people have to move faster with the agility robert. I want to come back to you because you brought up this idea of personas. I mean we all know devops infrastructure as code has been our religion for over a decade more, but now the word DEv sec ops is more prevalent in all the conversations the securities now weaved in here. How are you seeing that play out in the community and then tom if you can give some color commentary to on the automation platform, how security fits in. So devops everything's being operationalized at scale, we get that that's one of the value problems You have. But def sec off as a persona, more people want more sex. Deb is great more ops and standardisation. More developers, agile standards and then security def sec ops. What's your? I >>thought it was dev net sec off. >>Okay. I've forgotten that they were putting that in their networks abstracted away, you know, As we say. Yeah. >>Well, you know, from, from my perspective, you know there are people and their jobs all over the place is right. Like they you know the more they can feel like they're efficient and doing great stuff at their work. Like they're happy to bring as many people into the fold as possible, right? And you know normally security has always been this you know it's sort of like networking right? It's always been this sort of isolated this special group over here that's the traditional you know one of the traditional I. T. Bottlenecks that causes us to not be able to get anything done. But you know on a community level we see folks who are interested in security you know all the time. I know we've certainly done quite a bit of work with some folks at IBM around one of their products which I assume tom will get more into here in just a moment, but from, you know, a community perspective, I mean, we've seen people who have been writing, you know, playbooks and roles and you know, now collections for uh you know, all the traditional government testing, you know, is are, you know, missed standards, all of that kind of stuff. Um and you know, it's one of those, it's part of network effects and it's a great place where actually automation hub, I think, you know, for folks who are on prem or you know, any of our customers are really going to start to see lots of value is how it will be able to connect folks inside the organization organically through just the place where I'm doing my answerable things, allows them to find each other really, and build those, you know, take it from being silos of automation everywhere into a really sort of networked, you know, internal network of of answerable friends and uh danceable power users that can work together and collaborate, you know, just the same way that we do an open source >>and tom so I. T. Modernization requires security. What's your take on this? Because, you know, you got cluster a lot of cluster advanced cluster management issues, you've got to deal with the modern apps, they're coming, I. T. S got to evolve. What's your take on all >>this? Yeah, not only does I have to call but it's it's an integration like the rest of the environment and be able to respond the spirit of that song on the areas that we put a lot of effort into advanced in terms of curating and solutions around national security automation. We talked about that in the past, the idea of connecting the SEc ops teams that are doing intrusion detection or threat hunting and then responding in an automated way to those threats protections. Right? So, connecting stepped up to the bike, which is traditionally been styled operations and silo teams. And now it is curated against the security automation uh, solution that we've got a market with our partners. It connects those two teams in a single sort of way. We've done a lot of work with our friends that idea around this area because they are big and that security area, a radar and other products in their portfolio. So we've done a lot of work with them but we don't want to work with lots of our partners for their side. There are Microsoft in those areas. Traditionally Danceable has done a great job on sort of compliance around configuration enforcement, right setting and enforcing configuration. Now we moved into connecting set pops with IT security automation. And now with our acquisition of staff blocks along with our advanced custom management immigration with Danceable were starting to say, what are the things inside that sack office workflow that may require integration or automation packaged? Automate automation with other parts of the environment, bringing all of those pieces together as we move forward to security for us. >>Okay. I gotta ask you guys the number one question that I get all the time and I see in the marketplace is kind of a combo question is how do I accelerate the automation of my cloud native development with my traditional infrastructure? Because as people put in green born the cloud projects, whether it's whether and then integrating able to cloud on premises with nutritional infrastructure, how do I accelerate those two environments? How I automate accelerate the automation? >>Yeah. So it's a great story for us and this is what we're talking about, small and special as we have bringing together of our advanced cluster management product, open ship platform and it's just, you know, widespread use through all the automation of both traditional and cognitive changes. Whether it's cloud infrastructure on premise, start network, you name it, customers are using answerable user, you're using answer to do all kinds of pieces in the system infrastructure. Being able to tie that to their new collaborative initiatives without having to redo all of that work that they've already done to integrate that existing um infrastructure automation with their cognitive accelerate substantial what I call the offer operationalization to say operated operationalization, their cloud native platforms that are existing infrastructure and existing I uh, ecosystem. I believe that that's where the answer the automation and plays a key role in connecting those students is together without having to redo all that work that's been done in investment >>robert. What's your take on this? This is what people are working on the trenches, they realized cloud benefits. They got some cloud native action, and also that they got the on the traditional environment, they got to get them connected and automated. >>Yeah, absolutely. I mean, you know, the beauty of answerable, you know, from an end user perspective is, you know, how easy it is to learn and how easy the languages to learn. And I think, you know, that that portability, you know, it doesn't matter like how much of a rocket scientist you are, you know, everybody appreciates simplicity, everybody appreciates being able to hand something simple to somebody else and letting other people get done and having it be more or less in a it's not quite english, but it's definitely, you know, answer is quite readable, right? Um, and you know, when we looked at, you know, when we started to work on all the answerable operators, you know, one of that, one of the main pieces there was, making sure that that simplicity that we have an answerable is brought over directly into the operators. So just because it's cloud native doesn't mean you suddenly have to learn, you know, a whole set of new languages and peoples just as portable there as it is to any other part of the your mighty organization, infrastructure or whatever it is that you have going on. >>Well, there's a lot of action going on here at red hat summit 2021 things I wanted to bring up in context of the show um is the successor and the importance of you guys having answerable collections. This has come up multiple times. Um as we talked about those personas and you've got these new contributors, you've got people contributing content. Um, as open source continues to grow and be phenomenal value proposition. Touch on this uh, concept of collections. What's the updates? Why is it important? Why should folks pay attention to it and continue to innovate with collection? >>This is from a commercial perspective of food products, questions and down has made a lot of these contributors to create an exploit, distribute content at the end, the problems mentioned earlier, these iterations announced, we'll have all of the documentation, all those collections, all within one. If you call the batteries included back at the time that day. Right. But that, that meant that contributors um, be able to deploy their content with the base, has the distribution. They have to wait for the next version. Events. Alright, that's when that content would get redistributed the next investment. He coupled content from the core engine, putting that into elections that are individual elements of related innovations closes can use at their own pace. So users and customers can get content baby a case that contributors like in public. So, uh, customers don't have to wait for the next evolution shipping products. You get a new version of the immigration is really like, you know, so again, a couple of those things that last into the different faces the engine or the platform itself is the state Department's here. It's going to be a certain website. Content itself, all the different content, the network providers ready platforms, all of those same pace. You girls have their own life cycle quite sweet. It allows us to get more functionality for customers hands like bigger and then launching our Certified can support that. Okay. Certified. Support that content tells me the values that we bring our customers with the subscription. Is that ecosystem and highest partners that we work with Certified and support the stuff that we should and support with possible superb benefits, both on the access to the technology as well as the access to the value of this. In terms of immigration testing and support >>Robin, What's your take on the community? I see custom automation with with the connector, a lot of action going on collections. >>Yeah, absolutely. Um, you know, it's been interesting, you know, tom just mentioned the, you know how everything previously all had to be released all at once. Right. And if you think about, you know sure I have answerable installed but you know, how often do I have to, you know, just even as a regular, I'm not a system administrator these days, type person like how often do I have to, you know, click that button to update, you know, my Mac or my Lennox machine or, you know, my Windows machine or, you know, the operating system on my telephone, right? Every time one of these devices that answerable connects to or a program or whatever it is, connects to something, those things are all operating and, you know, developing themselves at their own pace is right? So when a new version of, you know, uh, uh, well, we'll call Red Hat enterprise Linux when a new version of Red Hat enterprise Lennox comes out, uh, if there are new changes or new features that, you know, we want to be able to connect to it. That's not really helpful when we're not releasing for another six months. Right? So it's really helped us, you know, from a community angle to be able to have each of these collections working in concert with, you know, like for example, in real like the Lennox subsystems that are actually making things that will be turned into collections, right? Like Sc Lennox or System D right? Like those things move at their own pace, we can update those at our own pace in in collections and then people can update those collections without having to wait another six months or eight months or whatever it is for a new version of answerable to come out. It's really made it easier for all of those, you know, developers of content to work on their content and their, you know, answerable relationships almost in sync and make sure that, you know, but not, I'm going to do it over here and then I'm gonna come back over here and fix everything later. It's more of a continuous >>development. So they contribute experience is better than you'd say. >>I'm sorry, >>the contributor experiences better than. Oh, >>absolutely. Yeah, 100%. I mean, it's, >>it's, >>you know, there's something to be said for. I wouldn't say it's like instant satisfaction, but, but certainly the ability to have a little bit more independence and be able to release things as as you see fit and not be gated by the entire rest of the project is amazing for those >>votes. So I put you on the spot, Robin. So if I'm a, I'm a developer bottom line, me, what's in it for me? Why? Why should I pay attention to collections? What's the bottom >>line? Well, you know, answerable as a platform and, and for benefits from network effects. Um, you know, the reason that we've gotten as big as we have sort of like the snowball rolling downhill, right, the more people that latch on to what you're doing, the more people benefit and the more, you know, additional folks want to join in. So, you know, if I, if I was working on any other product that I would consider being able to have automated with answerable, um, you know, the biggest thing that I would look at is, well, you know, what are those people also using or they automating it with an apple and I can guarantee you 99% of the time, everything else that people are using is also being automated with answerable. So you'd be crazy to not, you know, want to participate and make sure that you're providing the best, you know, and experience for your application because for every Application or device that we can connect you, there's probably 20 other competitors that also make similar applications that folks might also consider in lieu of you if you're not using your not providing ample content >>for it. Hey, make things easier, simple to use and you reduce the steps it takes to do things. That's a winning formula. Tom. I mean when you make things that good, then you get the network effect. But this highlights what you mentioned earlier about connective tissue. When you use words like connective tissue, it implies an organizational is not a mechanism. It's not just software, it's people, there's a people experience here in the automation platform. This seems to be the bottom line. What's, what's your take? What's your bottom line of you? I'm a developer. What's in it for me? Why should I pay attention to the automation platform? >>States of the public developer. What excites me is using it? Yeah, I'm just composition department and crossing those domains in silence and sort of can issue across these tools and resolve this means those contributors is developed as a great denomination come embedded in the hands of more people across the organization. Absoluteal more simple. five way by using the explanation. Sometimes they get access right. You see those out the automation of South coast for so long as they get access to existing automation faster. They have to run into the expert on their part requirement a local hotel folks and the real in terms of automation and that kind of a patient. Excellently. When I'm getting on you about the details of what it takes them, you configure the network and figure the storage elements. They rely on those automation developers and contributors that would do that for them. You must really work powers of this Children across those news process of human. Again when I got kidnapped and sent cops, the idea of connecting to the network, being able to do all of these tasks with the same language and the same. In addition, funds had some money faster and get some of the kind of quote responsibilities without worrying. Line >>Robin, you wanted to talk about something uh, in the community. Any updates? I think navigator you mentioned you wanted to mention uh, plug for that. Absolutely. >>So, you know, um, much like any other platform in the universe. You know, if you don't have really great uh, tools for developing content, you're kind of, you know, dead in the water, right? Or you're leaving it to fate. So we've been working on a new project. I'm not part of the product yet, but you know, it's sort of in a community exploratory phrase released early release often or you know, minimum viable project I guess might be the other way to describe it currently. Uh it's a called Animal Navigator, it's a TUI which is like a gooey, but it's got a sort of a terminal user interface look to it that allows you to, you know, develop, its a sort of interface where you can develop content, uh you know, all in one window, have your, you know, documentation accessible to you have, you know, all of your test results available to you in one window, um rather than I'm going to do something here and then I'm gonna go over here and now, I'm not sure. So now I'm gonna go over here and look at docs instead. It's all, you know, it's all in one place, um which we think will actually, but I mean, I know the folks who have seen it have already been like, but you know, it's definitely an early community stages right now. It's, you know, we can give you the link github dot com slash answer slash danceable navigator, but >>versus a gooey versus a command line interface are how do you innovate on the command line? It's a kuwaiti uh it's >>um you know, there there's so many ideas out there and I think tom can probably talk to some of this, you know, how that might relate to V. S. Code or you know, many of the other traditional developer ideas that are out there, but you know, the goal certainly to be able to integrate with some of those other pieces. Um but you know, it's one of those things where, you know, if everybody is using the same tool, we can start to enforce higher levels of quality and standards through that tool. Uh there's benefits for everyone tom, I don't know if you want to add on to that in any way. >>Yeah, it's just kind of one of our focus areas religious making it as easy as possible to create things and a lot of nations. So part of that is essentially a kind of road map in the nesting table and spoke that that's not presented to the security is you don't build test deploy. So people are making a contributor that builders life job. >>Well, thanks for coming on tom and Robyn. Thanks for sharing the insight here. Redhead Summit 21 virtual. I'll see you guys do continue to do a great job with the success of the platform, which has been, you know, consistently growing and having great satisfaction with developers and now ops teams and sec teams and Net teams, you know, unifying these teams is certainly a huge priority for enterprises because the end of the day, cloud scale is all about operating a skill, which means more standards, more operations. That's what you guys are doing. So. Congratulations on the continued success. Thanks for sharing. >>Thanks for having us. >>Okay. I'm John for here in the queue, we are remote with Cube virtual for Reddit Summit 2021. Thanks for watching what?

>>on >>the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS and our community partners. Okay. Welcome back, everyone. That's the cubes. Live coverage here in Palo Alto, California. I'm John for your host with David Lantana in Boston. Massachusetts. Uh, we got a great panel here. Analysts just gonna break it down. Keynote analysis. Day one, we got Ah, longtime Web services expert analyst Diane Hinchcliffe, principal researcher at N V. P. It constantly research, but he goes way back. Dan, I remember, uh, 2000 and one time frame you and I'm >>reading Last time you and I hang out with Michael Arrington's house back in the TechCrunch days >>back when, you know you were on this was Web services. I mean, that's always, uh, serves on the architectures. They called it back then. This was the beginning. This really was the catalyst of cloud. If you think about virtualization and Web services in that era, that really spawned where we are today so great to >>have you on as an Amazon got their start saying that everyone could get whatever they want to on a P. I now right, >>all right? Well, we've been riding this wave. Certainly it's cotton now more clear for the mainstream America. And I quoted you in my story, uh, on Andy Jassy when I had my one on one with them because I saw your talk with star Bit of the weekend and in the way you kicked it off was the Pandemic four was forced upon everybody, which is true, and that caught my attention was very notable because you talked to a lot of C E. O s. Does jazz sees pitch resonate with them? In your opinion, what's your take on on that on that posture? Because we heard, hey, you know, get busy building or you're dying, right? So get busy building. That's what >>I thought that was a good message. But I mean on and certainly I saw tweets and said, Hey, he's just he's just directly talking to the CEO. But if you ask me, he's still talking to the CTO, right? The technology officer who's got a feels all this technology and bend it into the shape that it will serve the business. You talk to a CEO who wants is trying to get on the cloud their biggest challenges. I know I need armies of people who know all these brand new services. You saw the development velocity of all the things that they announced and things they re emphasized there was There was a lot of things that were bringing back again because they have so many things that they're offering to the public. But the developer skills or not, they're the partner skills are not there. So you talked to CEO, says All right, I buy in and and I have had to transform overnight because of the pandemic, my customers have moved, my workers have moved on, and I have to like, you know, redirect all my I t Overnight and Cloud is the best way to do that. Where's my where's all the skills for the training programs, the department programs that allow me to get access to large amounts of talent? Those are the types of things that the CEO is concerned about is from an operational perspective. We didn't hear anything about, like a sales force type trailhead where we're going to democratize cloud skills to the very far end of your organization. >>Yeah, they're just kind of scratching the service. They didn't mention that, you know, far Gates away to get into server list. I mean, this is ultimately the challenge Dave and Deena like, don't get your thoughts on this because I was talking Teoh a big time CTO and a big time see so and that perspectives were interesting. And here's the Here's the Here's what I want you to react Thio the sea level Say everything is gonna be a service. Otherwise we're gonna be extinct. Okay, that's true. I buy that narrative, Okay, Make it as a service. That's why not use it. And then they go to the C t. And they say, implement, They go Well, it's not that easy. So automation becomes a big thing. And then so there's this debate. Automate, automate, automate. And then everything becomes a service. Is it the cart before the horse? So is automation. It's the cart before the horse, for everything is a service. What do you guys think about that? >>We'll see. I mean, CEO is to Diane's point, are highly risk averse and they like services. And those services generally are highly customized. And I think the tell in the bevy of announcements the buffet have announces that we heard today was in the marketplace what you guys thought of this or if you caught this. But there was a discussion about curated professional services that were tied to software, and there were classic PDM services. But they were very, you know, tight eso sort of off the shelf professional services, and that's kind of how Amazon plays it. And they were designed to be either self serve. It's a Diane's point. Skill sets aren't necessarily there or third parties, not directly from Amazon. So that's a gap that Amazon's got too close. I mean, you talk about all the time without post installations, you know, going on Prem. You know who's gonna support and service those things. You know, that's a that's a white space right now. I think >>e think we're still reading the tea leaves on the announcements. But there was one announcement that was, I thought really important. And that was this VM Ware cloud for a W s. It says, Let's take your VM ware skills, which you've honed and and cultivated and built a talent base inside your organization to run VMS and let's make that work for a W s. So I thought the VM Ware cloud for a W s announcement was key. It was a sleeper. It didn't spend a lot of time on it. But the CEO ears are gonna perk up and say, Wait, I can use native born skills. I already have to go out to the cloud So I didn't think that they did have 11 announcement I thought was compelling in that >>in the spending data shows of VM Ware Cloud on AWS is really gaining momentum by the way, As you see in that open shift So you see in that hybrid zone really picking up. And we heard that from AWS today. John, you and I talked about it at the open I produces in >>Yeah, I want to double down on that point you made because I want to get your thoughts on this a Z analyst because you know, the VM ware is also tell. Sign to what I'm seeing as operating and developing Dev ops as they be called back in the day. But you gotta operate, i t. And if Jassy wants to go after this next tier of spend on premise and edge. He's gotta win the global i t posture game. He's gotta win hybrid. He's got to get there faster to your point. You gotta operate. It's not just develop on it. So you have a development environment. You have operational environment. I think the VM Ware thing that's interesting, cause it's a nice clean hand in glove. VM Ware's got operators who operate I t. And they're using Amazon to develop, but they work together. There's no real conflict like everyone predicted. So is that the tell sign is the operational side. The challenge? The Dev, How does Amazon get that global I t formula down? Is it the VM Ware partnership? >>I think part of it is there, finally learning to say that the leverage that the vast pool of operational data they have on their literally watching millions of organizations run all the different services they should know a lot and I say made that point today, he said, Well, people ask us all the time. You must have all these insights about when things were going right or wrong. Can you just tell us? And so I think the announcement around the Dev ops guru was very significant, also saying you don't necessarily have to again teach all your staff every in and out about how to monitor every aspect of all these new services that are much more powerful for your business. But you don't yet know how to manage, especially at scale. So the Dev Ops guru is gonna basically give a dashboard that says, based on everything that we've known in the past, we could give you insights, operational insights you can act on right away. And so I think that is again a tool that could be put in place on the operational side. Right. So b m where for cloud gives you migration ability, uh, of existing skills and workloads. And then the Dev Ops crew, if it turns out to be everything they say it is, could be a really panacea for unlocking the maturity curve that these operators have to climb >>on. AWS is in the business now of solving a lot of the problems that it sort of helped create. So you look at, for instance, you look at the sage maker Data Wrangler trying to simplify data workloads. The data pipeline in the cloud is very very complex and so they could get paid for helping simplify that. So that's a wonderful, virtuous circle. We've seen it before. >>Yeah. I mean, you have a lot of real time contact lens you've got, um, quick site. I mean, they have to kind of match the features. And And I want to get your guys thoughts on on hybrid because I think, you know, I'm still stuck on this, Okay? They won the as path and their innovations Great. The custom chips I buy that machine learning all awesome. So from the classic cloud I as infrastructure and platform as a service business looking good. Now, if you're thinking global, I t I just don't just not connecting the dots there. See Outpost? What's riel today for Amazon? Can you guys share E? I mean, if you were watching this keynote your head explode because you've got so many announcements. What's actually going on if you're looking at this is the CEO. >>So the challenge you have is the CEO. Is that your you have 10, 20 or 30 or more years of legacy hardware, including mainframes, right. Like so big insurance companies don't use mainframe because their claims systems have been developed in their very risk averse about changing them. Do you have to make all of this work together? Like, you know, we see IBM and Redhead are actually, you know, chasing that mainframe. Which angle, which is gonna die out where Amazon, I think is smart is saying, Look, we understand that container is gonna be the model container orchestration is gonna be how I t goes forward. The CEO is now buy into that. Last year, I was still saying, Are we gonna be able to understand? Understand? Kubernetes is the regular average i t person, which are not, you know, Google or Facebook level engineers Are there gonna be able to do do containers? And so we see the open sourcing of of the AWS is, uh, kubernetes, uh, server on. We see plenty of container options. That's how organizations could build cloud native internally. And when they're ready to go outside because we're gonna move, they're gonna move many times slower than a cloud native company to go outside. Everything is ready there. Um, I like what I'm seeing without posts. I like what I'm seeing with the hybrid options. The VM ware for cloud. They're building a pathway that says you can do real cloud. And I think the big announcement that was that. That s a really, uh, spend time on which is that PCs for everywhere. Um, a saying you're gonna be able to put Amazon services are compute services anywhere. You need it, e think that's a smart message. And that allows people to say I could eventually get toe one model to get my arms around this over time >>day. What does that mean for the numbers? I know you do a lot of research on spend customer data. Um, CEO is clearly no. This is gonna be the world's never go back to the same way it was. They certainly will accelerate cloud toe. What level depends upon where they are in their truth, as Jassy says. But >>what does >>the numbers look at? Because you're looking at the data you got Microsoft, You got Amazon. What's the customer spend look like where they're gonna be spending? >>Well, so a couple things one is that when you strip out the the SAS portion of both Google and Azure, you know, as we know, I asked him pass A W S is the leader, but there's no question that Microsoft is catching up. Says that we were talking about earlier. Uh, it's the law of large numbers Just to give you a sense Amazon this year we'll add. Q four is not done yet, but they'll add 10 billion over last year. And Jesse sort of alluded to that. They do that in 12 months. You know, uh, azure will add close to nine billion this year of incremental revenue. Google much, much smaller. And so So that's, you know, just seeing, uh, as you really catch up there for sure, you know, closing that gap. But still Amazon's got the lead. The other thing I would say is die on you and I were talking about this Is that you know Google is starting. Thio do a little bit better. People love their analytics. They love the built in machine learning things like like big query. And you know, even though they're much, much smaller there, another hedge people don't necessarily want to goto Microsoft unless they're Microsoft Shop. Google gives them that alternative, and that's been a bit of a tailwind for Google. Although I would say again, looking at the numbers. If I look back at where Azure and AWS were at this point where Google is with a few billion dollars in cloud the growth rates, I'd like to see Google growing a little faster. Maybe there's a covert factor there. >>Diane. I want to get your thoughts on this transition. Microsoft Oracle competition Um, Jesse knows he's got a deal with the elite Salesforce's out there. Oracle, Microsoft. Microsoft used to be the innovator. They had the they had the phrase embracing extend back in the day. Now Amazon's embracing and extending, but they gotta go through Oracle and Microsoft if they wanna win the enterprise on premise business and everybody else. Um, eso welcome to the party like Amazon. You What's your take on them versus Microsoft? Calling them out on sequel server licensing practices almost thrown him under the bus big time. >>Well, I think that's you know, we saw the evidence today that they're actually taking aim at Microsoft now. So Babel Fish, which allows you to run Microsoft sequel server workloads directly on Aurora. Uh, that that is what I call the escape pod that gives organizations an easy way That isn't Will parliament to redesign and re architect their applications to say, Just come over to AWS, right? We'll give you a better deal. But I think you've got to see Amazon have, um, or comprehensive sales plan to go into the C. E. O s. Go after the big deals and say, You know, we want to say the whole cloud suite, we have a stack that's unbeatable. You see our velocities, you know, best in class. Arguably against Microsoft is the big challenger, but we'll beat you on on a total cost of ownership. You know, your final bill. At the end of the day, we could we commit to being less than our competitors. Things like that will get the attention. But, you know, uh, Amazon is not known for cutting customized deals. Actually, even frankly, I'm hearing from very CEO is a very large, like Fortune 20 companies. They have very little wiggle room with Microsoft's anybody who's willing to go to the big enterprise and create custom deals. So if you build a sales team that could do that, you have a real shot and saying getting into the CEO's office and saying, You know, we want to move all the I t over and I'm seeing Microsoft getting winds like that. I'm not yet seeing Amazon and they're just gonna have to build a specialized sales team that go up against those guys and migration tools like we saw with Babel fish that says, If you want to come, we can get you over here pretty quick. >>I want to chime in on Oracle to John. I do. I think this is a blind spot somewhat for AWS, Oracle and mainframes. Jesse talks that talks like, Oh yeah, these people, they wanna get off there. And there's no question there are a number of folks that are unhappy, certainly with Oracle's licensing practices. But I talked to a lot of Oracle customers that are running the shops on Oracle database, and it's really good technology. It is world class for mission critical transaction workloads. Transaction workloads tend to be much, much smaller data set sizes, and so and Oracle's got, you know, decades built up, and so their their customers air locked in and and they're actually reasonably happy with the service levels they're getting out of Oracle. So yes, licensing is one thing, but there's more to the story and again, CEO or risk averse. To Diane's point, you're not just gonna chuck away your claim system. It's just a lot of custom code. And it's just the business case isn't there to move? >>Well, I mean, I would argue that Well, first of all, I see where you're coming from. But I would also argue that one of the things that Jesse laid out today that I thought was kind of a nuanced point was during the vertical section. I think it was under the manufacturing. He really laid out the case that I saw for startups and or innovation formula, that horizontal integration around the data. But then being vertically focused with the modern app with same machine learning. So what he was saying, and I don't think he did a good job doing it was you could disrupt horizontally in any industry. That's a that's a disruption formula, but you still could have that scale. That's cloud horizontal scalability, cloud. But the data gives you the ability to do both. I think bringing data together across multiple silos is critical, but having that machine learning in the vertical is the way you could different so horizontally. Scalable vertical specialization for the modern app, I think is a killer formula. And I think >>I think that's a I think it's a really strong point, John, and you're seeing that you're seeing in industries like, for instance, Amazon getting into grocery. And that's a data play. But I do like Thio following your point. The Contact Center solutions. I like the solutions play there and some of the stuff they're doing at the edge with i o T. The equipment optimization, the predictive maintenance, those air specialized solutions. I really like the solutions Focus, which several years ago, Amazon really didn't talk solution. So that's a positive sign, >>Diane, what do you think? The context And I think that was just such low hanging fruit for Amazon. Why not do it? You got the cloud scale. You got the Alexa knowledge, you know, got machine learning >>zone, that natural language processing maturity to allow them to actually monitor that. You know that that contact lens real time allows them a lot of supervisors to intervene them conversations before they go completely south, right? So allowing people to get inside decision windows they couldn't before. I think that's a really important capability. And that's a challenge with analytics in general. Is that generates form or insights than people know how to deal with? And it solutions like contact lens Real time? This is Let's make these insights actionable before it's broken. Let's give you the data to go and fix it before it even finishes breaking. And this is the whole predictive model is very powerful. >>Alright, guys, we got four minutes left. I wanted Segway and finish up with what was said in the keynote. That was a tell sign that gives us some direction of where the dots will connect in the future. There's a lot of stuff that was talked about that was, you know, follow on. That was meat on the bone from previous announcements. Where did Jassy layout? What? I would call the directional shift. Did you see anything particular that you said? Okay, that is solid. I mean, the zones was one I could see. What clearly is an edge piece. Where did you guys see? Um, some really good directional signaling from Jassy in terms of where they really go. Deal with start >>e I felt like Jassy basically said, Hey, we invented cloud. Even use these words we invented cloud and we're gonna define what hybrid looks like We're gonna bring our cloud model to the edge. And the data center just happens to be another edge point. And hey, I thought he laid down the gauntlet. E think it's a very powerful message. >>What do you think Jesse has been saying? That he laid out here, That's >>you laid out a very clear path to the edge that the Amazons marching to the edge. That's the next big frontier in the cloud. It isn't well defined. And that just like they defined cloud in the early days that they don't get out there and be the definitive leader in that space. Then they're gonna be the follower. I think so. We saw announcement after announcement around that you know, from the zones Thio the different options for outpost um, the five g announcement wavelength. All of those things says we're gonna go out to the very tippy edge is what I heard right out to your mobile devices. Right after the most obscure field applications imaginable. We're gonna have an appliance So we're gonna have a service that lets you put Amazon everywhere. And so I think the overarching message was This is a W s everywhere it z gonna go after 100% of I t. Eventually on DSO you can move to that. You know, this one stop shop? Um and you know, we saw him or more discussions about multi cloud, but it was interesting how they stand away from that. And this is what I think One area that they're going to continue to avoid. So it was interesting, >>John, I think I think the edges one by developers. And that's good news for Amazon. And good news for Microsoft. >>We'll see the facilities is gonna be good for me. I think guys, the big take away You guys nailed two of them there, but I think the other one was I think he's trying to speak to this new generation in a very professorial way. Talk about Clay Christensen was a professor at his business school at Harvard. We all know the book. Um, but there was this There was this a posture of speaking to the younger generation like hey, the old guy, the old that was running the mainframe. Wherever the old guys there, you could take over and run this. So it's kind of like more of a leadership preach of preaching like, Hey, it's okay to be cool and innovative, right now is the time to get in cloud. And the people who are blocking you are either holding on to what they built or too afraid to shift. Eso I think a Z we've seen through waves of innovation. You always have those people you know who are gonna stop that innovation. So I was very interesting. You mentioned that would service to the next generation. Um, compute. So he had that kind of posture. Interesting point. Yeah, just very, very preachy. >>E think he's talking to a group of people who also went through the through 2020 and they might be very risk averse and not bold anymore. And so, you know, I think that may have helped address that as well. >>All right, gentlemen, great stuff. Final word in the nutshell. Kena, What do you think about it in general? Will take away. >>Yeah, I I think we saw the continued product development intensity that Amazon is going to use to try and thrash the competition? Uh, the big vision. Um, you know, the real focus on developers first? Um and I think I t and C e O's second, I think before you could say they didn't really think about them too much at all. But now it's a close second. You know, I really liked what I saw, and I think it's It's the right move. I'd like to Seymour on on hybrid cloud migration than that, even when we saw them. >>All right, leave it there. Don. Thanks for coming on from this guest analyst segment. Appreciate you jumping in Cuba. Live. Thank you. >>Thanks. Alright. >>With acute virtual. I'm your host John per day Volonte here covering A W s live covering the keynote in real time State more for more coverage after the break

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America. 2020. Virtual Brought to You by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners. Hey, welcome back, everybody. Jeffrey here with the Cube coming to you from our Palo Alto studios with our ongoing coverage of Q. Khan Cloud, Native Con 2020 North America. Of course, it's virtual like everything else is in 2020 but we're excited to be back. It's a terrific show, and we're excited our next guest. So let's introduce him. And we've got Sam Warner, the VP of offering manager and business line executive for storage for IBM. Sam. Great to see you. >>Great to be here. >>And also joining us is Brent Compton. He's a senior director of data services for Redhead. Great. See you, Brent. >>Thank you. >>So let's let's jump into it. Cloud Native. Everything's about cloud native. Everything's about containers. Everything is about kind of container ization and flexibility. But then there's this thing in the back and called storage. We actually have toe keep this stuff and record this stuff and have data protection for this stuff in business resiliency love to jump into it, so lets you know where does storage fit within a container world? And how is the growth of containers and the adoption containers really had you rethink the way that you think about storage and how clients you think about stories saying, Let's start with you >>e mean, it's a great question. And first off, I'm really excited about another cube con. Uh, we did Europe now, uh, doing North America so very excited to be, you know, seeing all the you know, all the news and all the people talking about the advancements around kubernetes. And we're very excited about it now. You asked a very good question. Important question. We're seeing an acceleration of digital transformation, and the people that are going through this digital transformation are using containers to now modernize the rest of their infrastructure. The interesting thing about it, though, is those initiatives are being driven out of the application teams. The business lines in an organization, and a lot of them don't understand that there's a lot of complexity to this storage piece here. So the storage teams I talked to are all of a sudden getting these initiatives thrown on them or a kind of halfway their strategy. And they're scratching their heads, trying to figure out now how they can support these applications with persistent storage. Because that's not where containers started. They started with micro services, and now now they're in a quandary. They have to deliver a certain S L. A to their customers, and they're trying to figure out how they do it in this new environment, which in a lot of cases, has been designed outside of their scope. So they're seeing issues with data protection. Some of the kind of core things that they've been dealing with for years are now. They're now having to solve all over again. So that's what we're working on helping them with reinventing how storage is deployed to help them deliver the same level of security, availability and everything they have in the past. Uh, in these new environments, >>right? So, yeah, e say you've been involved in this for a long time. You know, you've worked in hyper converge. You've worked in big data. You know, the evolution of big data continues to change, as ultimately we want to get people the information to make good decisions, but we've gone through a lot of integrations over the years. So how is it different? You know? Now how is it different with containers? What can we finally do you as a as an architect that we couldn't do before? >>Infrastructure is code. That's, I think, one of the fundamental differences of the storage admin of yesteryear versus storage admin of today today, Azaz Sam mentioned As people are developing and deploying applications, those applications need to dynamically provisioned the infrastructure dynamically provisioned what they need from compute dynamically provisioned what they need from storage dynamically provisioned network paths and so that that that element of infrastructure is code. A dynamically provisioned infrastructure is very different from well from yesterday, when applications or teams needed to. Well, when they needed storage, they would you know, they would file a ticket and typically wait. Now they make an a p A. Now they make an A p. I call and storage is dynamically provisioned and provided to their application. >>But what what I think hard to understand for the layman. And maybe it's just me, right? I It's very easy to understand dynamic infrastructure around, um compute right, I'm Pepsi. I'm running it out for the Super Bowl. I need I know how much people are gonna hit by hit my site and it's kind of easy to understand. Dynamic provisioning around networking again for the same example. What's less easy to understand its dynamic provisioning for storage? It's one thing to say, you know, there's a there's a pool of storage resource is that I'm going to dynamically provisioned for this particular after this particular moment. But one of the whole things about the dynamic is not only is it available when you need it, but I could make it big, and conversely, I could make it smaller go away. I get that for servers, and I kind of get that for networking, supporting an application and that example I just talked about. But we can't It doesn't go away a lot of the time for storage, right? That's important data that's maybe feeding another process. There's all kinds of rules and regulations, So when you talk about dynamic infrastructure for storage, it makes a lot of sense for grabbing some to provision for some new application. But it's >>hard to >>understand in terms of true dynamics in terms of either scaling down or scaling up or turning off when I don't particularly need that much capacity or even that application right now, how does it work within storage versus No, just servers or I'm grabbing them and then I'm putting it back in the pool. >>Let me start on this one, and then I'm gonna hand it off to Brent. Um, you know, let's not forget, by the way, that enterprises have very significant investments in infrastructure and they're able to deliver six nines of availability on their storage. And they have d are worked out in all of their security, encryption, everything. It's already in place, and they're sure that they can deliver on their SLS. So they want to start with that. You have to leverage that investment. So first of all, you have to figure out how to automate that into the environment, that existing sand, and that's where things like uh, a P I s the container storage interface CS I drivers come in. IBM provides that across your entire portfolio, allowing you to integrate your storage into a kubernetes environment into an open shipped environment so that it can be automated, but you have to go beyond that and be able to extend that environment, then into other infrastructure, for example, into a public cloud. So with the IBM flash system, family with our spectrum virtualized software were actually able to deploy that storage layer not only on Prem on our award winning a race, but we can also do it in the cloud. So we allow you to take your existing infrastructure investments and integrate that into your communities environment and using things like danceable, fully automated environment. I'll get into data protection before we're done talking. But I do want Brent to talk a bit about how container native storage comes into that next as well. On how you can start building out new environments for, uh, for your applications. >>Yeah, What the two of you are alluding to is effectively kubernetes services layer, which is not storage. It consumes storage from the infrastructure, Assam said. Just because people deploy Kubernetes cluster doesn't mean that they go out and get an entirely new infrastructure for that. If they're deploying their kubernetes cluster on premises, they have servers. If they're deploying their kubernetes cluster on AWS or an azure on G C P. They have infrastructure there. Uh, what the two of you are alluding to is that services layer, which is independent of storage that can dynamically provisioned, provide data protection services. As I mentioned, we have good stuff to talk about their relative to data protection services for kubernetes clusters. But that's it's the abstraction layer or data services layer that sits on top of storage, which is different. So the basics of storage underneath in the infrastructure, you know, remain the same, Jeff. But the how that storage is provisioned and this abstraction layer of services which sits on top of the storage storage might be IBM flash system array storage, maybe E m c sand storage, maybe a W S E B s. That's the storage infrastructure. But this abstraction layer that sits on top this data services layer is what allows for the dynamic interaction of applications with the underlying storage infrastructure. >>And then again, just for people that aren't completely tuned in, Then what's the benefit to the application developer provider distributor with that type of an infrastructure behind And what can they do that they just couldn't do before? >>Well, I mean Look, we're, uh, e I mean, we're trying to solve the same problem over and over again, right? It's always about helping application developers build applications more quickly helps them be more agile. I t is always trying to keep up with the application developer and always struggles to. In fact, that's where the emergency cloud really came from. Just trying to keep up with the developer eso by giving them that automation. It gives them the ability to provision storage in real time, of course, without having open a ticket like friends said. But really, the Holy Grail here is getting to a developed once and deploy anywhere model. That's what they're trying to get to. So having an automated storage layer allows them to do that and ensure that they have access to storage and data, no matter where their application gets it >>right, Right, that pesky little detail. When I have to develop that up, it does have to sit somewhere and and I don't think storage really has gotten enough of of the bright light, really in kind of this app centric, developer centric world, we talk all the time about having compute available and and software defined networking. But you know, having this software defined storage that lives comfortably in this container world is pretty is pretty interesting. In a great development, I want to shift gears a >>little bit. Just one thing. Go >>ahead, >>plus one to Sam's comments. There all the application developer wants, they want an A P I and they want the same a p I to provision the storage regardless of where their app is running. The rest of the details they usually don't care about. Sure. They wanted to perform what not give him an A p I and make it the same regardless of where they're running the app. >>Because not only do they want to perform, they probably just presume performance, right? I mean, that's the other thing is that the best in class quickly becomes presumed baseline in a very short short period of time. So you've got to just you just got to just deliver the goods, right? They're gonna get frustrated and not be productive. But I wanted to shift gears up a little bit and talk about some of the macro trends. Right? We're here towards the end of 2020. Obviously, Cove It had a huge impact on business and a lot of different ways. And it's really evolved from March, this light switch moment. Everybody work from home, too. Now, this kind of extended time, that's probably gonna go on for a while. I'm just curious some of the things that you've seen with your customers not so much at the beginning, because that was that was a special and short period of time. But mawr, as we've extended and and are looking to, um, probably extended this for a while, you know, What is the impact of this increased work from home increase attack surface? You know, some of these macro things that we're seeing that cove it has caused and any other kind of macro trends beyond just this container ization that you guys were seeing impacting your world. Start with you, Sam. >>You know, I don't think it's actually changed what people were going to do or the strategy. What I've seen it do is accelerate things and maybe changed the way they're getting their, uh and so they're actually a lot of enterprises were running into challenges more quickly than they thought they would. And so they're coming to us and asking us to help them. Saw them, for example, backing up their data and these container environments as you move mission critical applications that maybe we're gonna move more slowly. They're realizing that as they've moved them, they can't get the level of data protection they need. And that's why actually we just announced it at the end of October. Updates to our modern data protection portfolio. It now is containerized. It could be deployed very easily in an automated fashion, but on top of that, it integrates down into the A P. I layer down into CSE drivers and allows you to do container where snapshots of your applications so you could do operational recovery. If there's some sort of an event you can recover from that you can do D R. And you can even use it for data migration. So we're helping them accelerate. So the biggest I think requests I'm getting from our customers, and how can you help us accelerate? And how can you help us fix these problems that we went running into as we tried to accelerate our digital transformation? >>Brent, Anyone that you wanna highlight? >>Mm. Okay. Ironically, one of my team was just speaking with one of the cruise lines, um, two days ago. We all know what's happened them. So if we just use them as an example, I'm clearly our customers need to do things differently now. So plus one to Sam's statement about acceleration on I would add another word to that which is agility, you know, frankly, they're having to do things in ways they never envisioned 10 months ago. So there need to cut cycle times to deploy effectively new ways of how they transact business has resulted in accelerated poll for these types of infrastructure is code technologies. >>That's great. The one that jumped in my mind. Sam, is you were talking. We've we've had a lot of conversations. Obvious security always comes up on baking security and is is a theme. But ransomware as a specific type of security threat and the fact that these guys not only wanna lock up your data, but they want to go in and find the backup copies and and you know and really mess you up so it sounds like that's even more important to have the safe. And we're hearing, you know, all these conversations about air gaps and dynamic air gaps and, you know, can we get air gaps and some of these infrastructure set up so that we can, you know, put put those backups? Um, and recovery data sets in a safe place so that if we have a ransomware issue, getting back online is a really, really important thing, and it seems to just be increasing every day. We're seeing things, you know, if you can actually break the law sometimes if you if you pay the ransom because where these people operate, there's all kind of weird stuff that's coming out of. Ransomware is a very specific, you know, kind of type of security threat that even elevates, you know, kind of business continuity and resiliency on a whole nother level for this one particular risk factor. When if you're seeing some of that as well, >>it's a great point. In fact, it's clearly an industry that was resilient to a pandemic because we've seen it increase things. Is organized crime at this point, right? This isn't the old days of hackers, you know, playing around this is organized crime and it is accelerating. And that's one thing. I'm really glad you brought up. It's an area we've been really focused on across our whole portfolio. Of course, IBM tape offers the best most of the actual riel air gapping, physical air gapping We could take a cartridge offline. But beyond that we offer you the ability to dio you know, different types of logical air gaps, whether it's to a cloud we support. In fact, we just announced Now the spectrum protect. We have support for Google Cloud. We already supported AWS Azure IBM Cloud. So we give you the ability to do logical air gapping off to those different cloud environments. We give you the ability to use worm capability so you can put your backups in a vault that can't be changed. So we give you lots of different ways to do it. In our high end enterprise storage, we offer something called Safeguarded copy where we'll actually take data off line that could be recovered almost instantly. Something very unique to our storage that gives you, for the most mission critical applications. The fastest path recovery. One of things we've seen is some of our customers have done a great job creating a copy. But when the event actually happens, they find is gonna take too long to recover the data and they end up having to pay the ransom anyway. So you really have to think through an Indian strategy on we're able to help customers do a kind of health checks of their environment and figure out the right strategy. We have some offerings to help come in and do that for our customers. >>Shift gears a little bit, uh, were unanswerable fest earlier this year and a lot of talk about automation. Obviously, answer was part of the Red Hat family, which is part of the IBM family. But, you know, we're seeing Mawr and Mawr conversations about automation about, you know, moving the mundane and the air prone and all the things that we shouldn't be doing as people and letting people doom or high value stuff. When if you could talk a little bit about the role of automation, that the kind of development of automation and how you're seeing that, you know, impact your deployments, >>right? You want to take that one first? >>Yeah, sure. Um, s o the first is, um when you think about individual kubernetes clusters. There's a level of automation that's required there. I mean, that's the fundamental. I mean, back to the infrastructure is code that's inherently. That's automation. To effectively declare the state of what you want your application, your cluster to be, and that's the essence of kubernetes. You declare what the state is, and then you pass that declaration to kubernetes, and it makes it so. So there's the kubernetes level automation. But then there's, You know what happens for larger enterprises when you have, you know, tens or hundreds of kubernetes clusters. Eso That's an area of Jeff you mentioned answerable. Now that's an area of with, you know, the work, the red hats doing the community for multi cluster management, actually in the community and together with IBM for automating the management of multiple clusters. And last thing I'll touch on here is that's particularly important as you go to the edge. I mean, this is all well and good when you're talking about, you know, safe raised floor data center environments. But what happens when you're tens or hundreds or even thousands of kubernetes clusters are running in an oil field somewhere? Automation becomes not only nice to have, but it's fundamental to the operation. >>Yeah, but let me just add onto that real quick. You know, it's funny, because actually, in this cove it era, you're starting to see that same requirement in the data center in the core data center. In fact, I would say that because there's less bodies now in the data center, more people working remotely. The automation in need for automation is actually actually accelerating as well. So I think what you said is actually true for the core data center now as well, >>right? So I wanna give you guys the last word before before we close the segment. Um, I'm gonna start with you, Brent. Really, From a perspective of big data and you've been involved again in big data for a long time. As you look back, it kind of the data warehouse era. And then we had kind of this whole rage with the Hadoop era, and, you know, we just continue to get more and more sophisticated with big data processes and applications. But at the end of the day, still about getting the right data to the right person at the right time to do something about it. I wonder if if you can, you know, kind of reflect over that journey and where we are now in terms of this mission of getting, you know, the right data to the right person at the right time so they could make the right decision. >>I think I'll close with accessibility. Um, that Z these days, we you know, the data scientists and data engineers that we work with. The key problem that they have is is accessibility and sharing of data. I mean, this has been wonderfully manifest. In fact, we did some work with the province of Ontario. You could look that stop hashtag house my flattening eso the work with them to get a pool of data. Scientists in the community in the province of Ontario, Canada, toe work together toe understand how to track co vid cases s such so that government could make intelligent responses and policy based on based on the fax so that that need highlights the accessibility that's required from today's, you know, yesteryear. It was maybe, uh, smaller groups of individual data scientists working in silos. Now it's people across industry as manifest by that That need accessibility as well as agility. They need to be able to spin up an environment that will allow them to in this case, um, to develop and deploy inference models using shared data sets without going through years of design. So accessibility on back to the back to the the acceleration and agility that Sam talked about. So I'll close with those words >>That's great. And the consistent with the democratization of two is another word that we're here, you know, over and over again in terms of, you know, getting it out of the hands of the data scientists and getting it into the hands of the people who are making frontline business decisions every day. And Sam for you, for your clothes. I love for you Thio reflect on kind of the changing environment in terms of your requirements for the types of workloads that you now are, you know, looking to support. So it's not just taking care of the data center and relatively straightforward stuff. But you've got hybrid. You've got multi cloud, not to mention all the media, the developments in the media between tape and obviously flash, um, spinning, spinning drives. But you know, really, We've seen this huge thing with flash. But now, with cloud and the increased kind of autumn autonomy ization of of units to be able to apply big batches in small batches to particular workloads across all these different requirements. When if you could just share a little bit about how you guys are thinking about, you know, modernizing storage and moving storage forward. What are some of your what are some of your your priorities? What are you looking forward to, uh, to be able to deliver, You know, basically the stuff underneath all these other applications. I mean, applications basically is data whether you I and some in some computer on top. You guys something underneath the whole package? >>Yeah. Yeah. You know, first of all, you know, back toe what Brent was saying, Uh, data could be the most valuable asset of an enterprise. You could give an enterprising, incredible, uh, competitive advantage as an incumbent if you could take advantage of that data using modern analytics and a I. So it could be your greatest asset. And it can also be the biggest inhibitor to digital transformation. If you don't figure out how to build a new type of modern infrastructure to support access to that data and support these new deployment models of your application. So you have to think that through. And that's not just for your big data, which the big data, of course, is extremely important and growing at incredible pace. All this unstructured data, You also have to think about your mission critical applications. We see a lot of people going through their transformation and modernization of S a p with move toe s four Hana. They have to think about how that fits into a multi cloud environment. They need to think about the life cycle of their data is they go into these new modern environments. And, yes, tape is still a very vibrant part of that deployment. So what we're working on an IBM has always been a leader in software defined storage. We have an incredible portfolio of capabilities. We're working on modernizing that software to help you automate your infrastructure. And sure, you can deliver enterprise class sls. There's no nobody's going to alleviate the requirements of having, you know, near perfect availability. You don't because you're moving into a kubernetes environment. Get a break on your downtime. So we're able to give that riel enterprise class support for doing that. One of the things we just announced that the end of October was we've containerized our spectrum scale client, allowing you now toe automate the deployment of your cluster file system through communities. So you'll see more and more of that. We're offering you leading modern native protection for kubernetes will be the first to integrate with OCP and open ship container storage for data protection. And our flashes from family will continue to be on the leading edge of the curve around answerable automation and C s I integration with who are already so we'll continue to focus on that and ensure that you could take advantage of our world class storage products in your new modern environment. And, of course, giving you that portability between on from in any cloud that you choose to run in >>exciting times. No, no shortage of job security for you, gentlemen, that's for sure. All right, Well, Brent, Sam, thanks for taking a few minutes and, uh, is great to catch up. And again. Congratulations on the success. Thank you. Thank you. Thank you. Alrighty, Sammy's Brent. I'm Jeff, You're watching the cubes. Continuing coverage of Q. Khan Cloud, Native Con North America 2020. Thanks for watching. We'll see you next time.

>>from around the globe. >>It's the Cube with >>coverage of Coop Khan and Cloud Native Con Europe 2020 Virtual brought to you by Red Hat Cloud, >>Native Computing Foundation and >>Ecosystem Partners. Hi. And welcome back. I'm stew Minuteman. And this is the cube coverage of que con cognitive con 2020. The Europe virtual addition Course kubernetes won the container wars as we went from managing a few containers that managing clusters, too many customers managing multiple clusters and that and get more complicated. So to help understand those challenges and how solutions are being put out to solve them, having a welcome back to the from one of our cube alumni do if it Gerald is the vice president and general manager of the management business unit at Red Hat. Joe, good to see you again. Thanks so much for joining us >>two. Thanks for having me back. >>All right, so at Red Hat Summit, one of the interesting conversation do you and I add, was talking about advanced cluster management or a CME course. That was some people and some technology that came over to Red hat from IBM post acquisition. So it was tech preview give us the update. What's the news? And, you know, just level set for the audience. You know what cluster management is? >>Sure, So advanced Cluster manager or a CMS, We actually falling, basically, is a way to manage multiple clusters. Ross, even different environments, right? As people have adopted communities and you know, we have at several 1000 customers running open shift on their starting to push it in some very, very big ways. And so what they run into is a stay scale. They need better ways to manage. It would make those environments, and a CMS is a huge way to help manage those environments. It was early availability back at Summit end of April, and in just a few months now it's generally available. We're super excited about that. >>Well, that that Congratulations on moving that from technical preview to general availability so fast. What can you tell us? How many customers have you had used this? What have you learned in talking to them about this solution? >>So, first of all, we're really pleasantly surprised by the amount of people that were interested in the tech preview. Integrity is not a product that's ready to use in production yet so a lot of times accounts are not interested in. They want to wait for the production version. We had over 100 customers in our tech review across. Not only geography is all over the world Asia, America, Europe, us across all different verticals. There's a tremendous amount of interest in it. I think that just shows you know, how applicable it is to these environments of people trying to manage. So tremendous had update. We got great feedback from that. And in just a few months, we incorporate that feedback into the now generally available product. So great uptick during the tech created >>Excellent Bring assigned side a little bit, you know, When would I use this solution? If I just have a single cluster, Does it make sense for May eyes? Is it only for multi clusters? You know, what's the applicability of the offering? Yes, sir, even for >>single clusters that the things that ACM really does fall into three major areas right allows closer lifecycle management. Of course, that would mean that you have more than one cluster ondas people grow. They do for a number of reasons. Also, policy based management the ability to enforced and fig policies and enforce compliance across even your single cluster to make sure that stays perfect in terms of settings and configuration and things like that. Any other application. Lifecycle management The ability to deploy applications in more advanced way, even if you're on a single cluster, gets even better for multi cluster. But you can deploy your APS to just the clusters that are tagged a certainly, but lots of capabilities, even for application, even a single cluster. So we find even people that are running a single cluster need it askew, deployed more more clusters. You're definitely >>that's great. Any you mentioned you had feedback from customers. What are the things that I guess would be the biggest pain points that this solves for them that they were struggling with in the past? Well, >>first of being able to sort of Federated Management multiple clusters, right, as opposed to having to manage each cluster individually, but the ability to do policy based configuration management to just express the way you want things to stay, have them stay that way to adopt a more of a getups ethnology in terms of how they're managing their your open ships environments. There's lots more feedback, but those were some of the ones that seem to be fairly common, repetitive across the country. >>Yeah, and you know, Joe, you've also gotten automation in the management suite. How do I think about this? How does this fit into the broader management automation that customers were using? Well, >>I think as people in employees environments. And it was a long conversation about platform right? But there's a lot of things that have to go with the platform and red hats actually in very good about that, in terms of providing all the things you necessary that you would find necessary to make the five form successful in your environment. Right? So I was seen by four. We need storage, then development environments management, the automation ability to train on it. We have our open innovation labs. There's lots of things that are beyond the platform that people acquire in order to be successful. In the case of management automation, ACM was a huge advancement. Terms had managed these environments, but we're not done. We're gonna continue to ADM or automation integration with things like answerable mawr, integration with observe ability and analytics so far from done. But we want to make sure that open ship stays the best managed environment that's out there. I also do want to make a call out to the fact that you know, this team has been working on this technology for the past couple of years. And so, you know, it's only been a red hat for five months. This technology is actually very mature, but it is quite an accomplishment for any company to take a new team in a new technology. And in five months, do what Red Hat does to it in terms of making it consumable for the enterprise. So then kudos continue. Really not >>well. And I know a piece of that is, you know, moving that along to be open source. So, you know, where are we with the solution? Now that is be a How does that fit in tow being open? Source. >>Eso supports that are open source Already. When the process of open sourcing the rest of it, as you've seen over time read, it has a perfect record here of acquiring technologies that were either completely closed Source Open core in some cases where part it was open. It was closed. But that was the case with Ansell a few years ago. But basically our strategy is everything has to be open source. That takes time in the process of going through all of the processes necessary to open source parts of ACM on. We think that will find lots of interest in the community around the different projects inside of >>Yeah. How about what? One of the bigger concerns talking to customers in general about kubernetes even Mawr in 2020 is. What about security? How does a CME help customers make sure that their environment to secure? >>Yeah, so you know, configuration policies and forcing you can actually sent with ACM that you want things to be a certain way that somebody changes them that automatically either warn you about them or enforcement would set them back. So it's got some very strong security chops in terms of keeping the configurations just the way you want. That gets harder as you get more and more clusters. Imagine trying to keep everything but the same levels, settings, software, all the parts and pieces so affected you have ACM that can do this across any and all of your clusters really took the burden off people trying to maintain secure environments, >>okay, and so generally available. Now, anything you can share about how this solution is priced, how it fits in tow. The broader open shift offerings, >>Yes. Oh, so it's an add on for open shift is priced very similarly to open shift in terms of the, you know, core pricing. One thing I do want to mention about ACM, which maybe doesn't come out just by a description product is the fact that a scene was built from scratch for communities, environments and optimize for open shift. We're seeing a lot of competition out there that's taking products that were built for other environments, trying to sort of been member coerce them into managing kubernetes environments. We don't think people are going to be successful at that. Haven't been successful to date. So one things that we find as sort of a competitive differentiator for ACM and market is the fact that it was built from scratch designed for communities environments. So it is really well designed for the environment it's trying to manage, and we think that's gonna keep your competitive edge? >>Well, always. Joe. When you have a new architecture, you advantage of things. Any examples that you have is what, what a new architecture like this can do that that an older architecture might struggle with or not believe. Be able to do even though when you look at the product sheet, the words sound similar. But when you get underneath the covers, it's just not a good architect well fit. >>Yeah, so it's very similar sort of the shift from physical to virtual. You can't have a paradigm shift in the infrastructure and not have a sort of a corresponding paradigm shift in management tool. So the way you monitor these environments, where you secure them the way they scale and expand, we do resource management, security. All those things are vastly different in this environment compared to, let's say, a virtual more physical environment. So this has improved many times in the past. You know, paradigm shift in the infrastructure or the application environment will drive a commensurate paradigm shift in management. That's what you're seeing here. So that's why we thought it was super important to have management that was built for these environments. by design. So it's not trying to do sort of unnatural things north manage the environment. >>Yeah, I wondered. I love to hear just a little bit your philosophy as to what's needed in this space. You know, I look back to previous generations, look at virtualization. You know, Microsoft did very well at managing their environment, the M where did the same for their environments. But, you know, we've had generations of times where solutions have tried to be management of everything, and that could be challenging. So, you know, what's Red Hat in a CM's position and what do we need in the community space, you know, today and for the next couple of years. >>So kubernetes itself is the automation platform you talked about, you know, early on in the second. So you know, Cooper navies itself provides, you know, a lot of automation around container management. What a CME does is build a top it out and then capture, you know, data and events and configuration items in the environment and then allows you to define policies. People want to move away from manual processes. Certainly, but they wanna be able to get to a more state full expression of the way things should be. You want to be able to use more about, you know, sort of get up, you know, kind of philosophy where they say, this is how I want things today. Check the version in, keep it at that level. If it changes, put it back. Tell me about it. But sort of the era of chasing. You know, management with people is changing. You're seeing a huge premium now on probation. So automation at all levels. And I think this is where a cm's automation on top of open shift automation on down the road, combined with things like ansell, will provide the most automated environment you can have for these container platforms. Um, so it's definitely changing your seeing observe ability, ai ops getups type of philosophies Coming in these air very different manager in the past helps you seeing innovation across the whole management landscape in the communities environment because they are so different. The physics of them are different than the previous environments. We think with ACM answerable or insights product and some over analytics that we've got the right thing for this environment >>and can give us a little bit of a look forward, you know? How often should we expect to see updates on this? Of course. You mentioned getting feedback from the community from the technical preview to G A. So give us a little bit. Look, you know, what should we be expecting to see from a CME down the right the So >>the ACM team is far from done, right? So they're going to continue to rev, you know, just like we read open shift, that very, very fast base we're gonna be reading ACM and fast face. Also, you see a lot of integration between ACM. A lot of the partners were already working with in the application monitoring space and the analytics space security automation I would expect to see in the uncivil fest time frame, which is mid October, will cease, um, integration with danceable on ACM around things. That insult does very well combined with what ACM does. A sand will continue to push out on Mawr cluster management, more policy based management and certainly advancing the application life cycles that people are very interested in ruined faster. They want to move faster with a higher degree of certainty in their application. Employments on ACM is right there. >>It just final question for you, Joe, is, you know, just in the broader space, looking at management in this kind of cube con cloud, native con ecosystem final words, you want customers to understand where we are today and where we need to go down the road. >>So I think the you know, the market and industry has decided communities is the platform of future right? And certainly we were one of the earliest to invest in container management platforms with open shift were one of the first to invest in communities. We have thousands of customers running open shift back Russell Industries on geography is so we bet on that a long time ago. Now we're betting on the management automation of those environments and bringing them to scale. And the other thing I think that redhead is unique on is that we think that people gonna want to run their kubernetes environments across all different kinds of environments, whether it's on premise visible in virtual multiple public clouds, where we have offerings as well as at the edge. Right. So this is gonna be an environment that's going to be very, very ubiquitous. Pervasive, deported scale. And so the management of a nation has become a necessity. And so but had investing in the right areas to make sure that enterprises continues communities particularly open shift in all the environments that they want at the scale. >>All right. Excellent. Well, Joe, I know we'll be catching up with you and your team for answerable fest. Ah, coming in the fall. Thanks so much for the update. Congratulations to you in the team on the rapid progression of ACM now being G A. >>Thanks to appreciate it, we'll see you soon. >>All right, Stay tuned for more coverage from que con club native con 2020 in Europe, the virtual addition on still minimum and thanks, as always, for watching the Cube.

from around the globe it's the cube with digital coverage of Red Hat summit 2020 brought to you by Red Hat welcome back this is the cubes coverage of Red Hat summit 2020 I'm Stu minimun and it's our seventh year doing the cube this year of course it is a digital event which means we are reaching all the community members where they are around the globe really excited to bring program first time guests and a first time to redhead summit Vachon Vora he's the chief technology officer of Vodafone idea joining me from Mumbai India bhishan nice to see you take so much for joining us it's a pleasure to be here as >> I'm looking forward to this interaction all right so as I said I've been at Red Hat show for many years the the telecommunications space you know service providers are some of the you know more interesting in the technology space you talk about scale you talk about change you talk about you know software eating the world all of those discussions are ones I've had for many years but you know I think many people know Vodafone may be a vote a fun idea escape for us you know the organisation and of course you've got the CTO at so you know what that means inside your organization sure so what a fun idea is a company that came came to acclaim as a result of a merger about 18 months ago so the number two and number three operators in India which was Vodafone an idea came together to create a telco serving over 300 million subscribers and we've been integrating the the networks over the last 18 months and consolidating and doing one of the largest integration in the world of two networks comprising over 200 thousand sites and carrying you know more than 50 billion MB of traffic per hour per day serving more than 40 million voltaic customers and we have been duplicating the network very very busy with her and we taken down so far almost a hundred thousand base stations which is equivalent to the size of a large operator in us so that's about the carnahan that is about the scale of the the operator that word of an idea is and what we've been busy with for the last day yeah well well Besant of course the reason we're doing this event online is because right now with the global pandemic the vast majority of the population they're at home so you know healthcare of course you know one of the major concerns I actually have done interviews with some of the power and energy companies critically important at this time but you know telecommunications you know what one of the top of the list you know in normal times for what people need but today it's the the only way that we can all connect it so tell us a little bit about do you know what the current situation you know the impact and importance this really highlights of your business yeah so just as the rest of the world India is also in a lockdown and India actually has one of the largest the largest lockdown in the world putting all 1.3 billion people in a lockdown yeah across the entire country so within that context the telecom network is crucial to make sure that the life goes on the essential services are delivered the industry continues to still operate as the best it can and all of that is made possible because of a stable and reliable network that we offer so a huge huge impact on the society always has been but in in this current context it is even more more critical and crucial so what we do is we make sure that we are the invisible layer you talked about health healthcare workers and emergency services well we are the invisible essential service that probably many people don't see but we are the ones who are really helping this country survive this this crisis and so far we have seen 25 30% increase in traffic in a single day in one week we experienced the same amount of traffic growth we would have experienced in the entire year so we we scalability is very very critical in our network and we've been able to keep up with that kind of a growth and continue to serve the communities and in this crucial juncture and all this dude large extent has been made possible because of a large-scale deployment of cloud technologies that we have done over the last 18 months which has really helped us scale up a large lot of our capabilities in the back yeah I'd love if you could explain a little bit more on that it you know challenging times you know I'm curious the amount of people that are using your services probably haven't changed but the demand and how much they're using it as change a lot so cloud obviously gives you scalability but you know are there concerns about what this does the profitability how you maintain things how much of this is a temporary change and how much will this be you know I know in the United States there's a lot of talk about how much work from home will become more of a standard than it had been before this pandemic so you know short term what's the impact on your business and what are you and other telecommunication companies thinking about what long-term impact this will have >> I think that's a very very interesting question I think even for me and my organization what we have been able to do working from home is amazing I never would have thought that it was possible to do as much as we've been able to do just staying young with most of the work for staying at home and that has really I think happened across industries across the entire country I think many organizations have now realized that work from home or work from anywhere which is the other term he's gonna become quite possible and prevalent going forward because people have realized that you can just get you can get just as much productivity out you can get so many things done working from home and it gives so much more personal flexibility to the individuals so I see when I look back at our organizational experience I see our productivity has been actually quite good actually better then haha where probably even in the office days so I think that is definitely one thing that is gonna come out as a global change across all industries I think the second thing that is gonna happen is data analytics I think there is going to be far more analysis of data to understand patterns and understand trends and how to take advantage of that I think of course the immediate application is in the healthcare and the spread of the pandemic but I think this will spur a lot of other analytics I think the third thing is going to do is the adoption of digital as the primary mode digital was already something that most companies are working on as is a top priority but I think going outward is gonna become very evident to people that it is actually essential just talking about my business I can tell you today you know all the stores all the shops every place that we used to check our cell or recharge vouchers are closed so the only place we are able to get any revenue from is our digital channel and on end only place where customers have been able to recharge their prepaid subscriptions etc has all been through digital I think digital we will also become a massive massive requirement so in that context I think telecom will be seen as a critical critical backbone I think to a large extent it has been seen by many in the past is more of an essential commodity but I think many organizations will realise that this is actually a value creator so I think it's a great exciting opportunity for us to take advantage of those new business opportunities that will come and at the same time be a very very important player in the digital economy that every nation around the world is gonna press you know for Sean said it really appreciates some really good commentary there you know we've been talking for years about customers going through their digital transformation it's really about the data and how they leverage that and if you're data-driven then you really have gone through that transformation and you kind of described what we call the new innovation cocktail you're leveraging cloud that there's data you put those all together as to how you drive your company and you can drive innovation oftentimes when we think about what results we're going to get from deploying cloud and using these types of new technologies we think we know what we're gonna get but the reality of how your company is dealing with things today of course you know proves what you were hoping that build for here help us understand you know what we're talking here is part of red hat summit this week you know what's red hats role in this piece and you know how did the reality of rolling this out and then how it has helped you in the current global situation impacted your business sure oh so I would say actually the three words that I used digital cloud and analytics to me they're actually inseparable cuz I do not believe that you can have a digital business that is not based on cloud or that is not good at data analytics I think if you want to really have a successful cloud offering it implies that automatically that you are a digital business and you're gonna do extensive modern data and analytics and build those capabilities I think those are three inseparable terms now speaking specifically about a red head I would say that red head has been a very very critical partner for us right from the beginning 18 months ago when the two companies too came together to create this network we knew that we had to do several things number one was actually to have a completely rationalized structure which was around extracting the synergies from the from the merger but beyond that we needed to build a telco of the future technology company of the future which will let us transform the business and create capabilities that will give us a step ahead a leapfrog ahead of our competition and cloud was a very very essential part of the journey and we knew we needed to build a cloud based on open systems because we did not want to get into a proprietary logins with anybody and we are a very large business we have suffered a sufficiently large scale to really be able to build a very large cloud so we started working with Red Hat about two years ago and it in the last two years we have deployed 80 plus cloud locations distributed cloud locations across the country and these all of these clouds our vision is to orchestrate them as a single cloud our vision is to build a cloud there is a universal cloud actually that is the word there is a word we use when we talk about cloud it's a universal cloud what does that mean that means that cloud will carry not only the traditional telco workloads but it will also carry IT workloads it will also carry lot of the enterprise offerings we have so - for the end-user for our enterprise clients and all of those capabilities out to be accommodated with a platform that is versatile that is scalable and that is gonna give me in enormous amount of flexibility and control as a organization so Red Hat has been a very important part of the journey and on the red head OpenStack cloud today I have a Daffy's working from any major supplier you can think of I have any enemies working from Nokia Ericsson Huawei ziti even some smaller players like Marvin here so we have demonstrated that this is possible we've been able to break the lock in that the traditional naps have had on their cloud offerings which were really more of a virtualized offerings rather than a cloud computer is a truly universal cloud on the back of the technology provided by a red well that's that's fantastic congratulations on that I love the the result of what you're calling Universal Cloud is the promise that we talked about for a number of years you know is that nitty gritty networking piece it was like you know network functions virtualization and if be sitting an open stack and everybody's like well OpenStack am I trying to build a cloud to compete against the public cloud providers it was like no what you said exactly there's services that you want to be able to deliver and it's not just about oh we're getting away from hardware appliances it's you know just like most people today they're used to whatever smart device they're doing I want to be able to turn on channels and access new things that's your now you know reducing that barrier to Vodafone idea to deliver that to your users have I captured that properly that is correct as a matter of fact I'll just give you one proof point my water phone app is the app that we we have for our consumers and that app is currently running on my telco clock what used to be called the telco cloud so on that platform we are running my packet or actually there are about 40 and FB is for virtualized traditional calculations running alongside with an IT application a digital application okay so one of the things I you know I would like to understand there that what you've deployed there over the last couple of years sounds like a significant shift so you know you're talking about apps you're talking more of a developer type of environment bring us inside a little organizationally you know what new skills have new people had to learn has there been new people added to the organization have there been in a restructures what what is this this this whole initiative to get to universal cloud meant for your organization sure so I look after both the network and IT pieces of the part of parts of the company and you know we traditionally were in the past legacy we have had a IT cloud and we have heard indigo cloud what we are now creating is a single universal cloud what either of the two workloads are gonna be facilitated so for that actually the two organization the two parts of the organization need to come together and start to really work as one now it is very important that the telco guys understand the scale and the 99-year the five nines required in a running a network but at the same time IT guys also understand very much what all of the the flexibility that the business requires and the responsiveness required for the for the enterprise so bringing those two talents together I think in infusing that to create a single organization is one of the biggest challenges I think any telco has we also face it that is one aspect of it the second aspect of it is that there just aren't too many cloud experts in the world and we have been struggling with that I think skill shortage is a clear challenge for us now we try to address it using variety of means we of course try to upscale rescale lot of the traditional network core engineers that we have had we also try to use talent available or from consultants and then we also try to use our vendors so one of the concepts we've been working with our vendors is a concept of a resident engineer so we try to actually get them to second some of their engineers to work with us and at the same time we've been now working with both IBM and redhead to create a program to really go out and create a community around us of developers who can really work with this cloud and therefore we will have enough of skills available to leverage all of the potential benefits there are then the platform but can only be unleashed if I have the right skills and right people you touched on a very important issue it is a challenge but we are working our way through it and so far we've been a bit we make good all right well if it's shot I can't let a CTO go without looking a little bit into the future so want to help understand we talked about some of the technologies talked about transformation of what's happening your business what's happening your organization and there's some big waves coming week you know cloud is still in early days 5g of course you know is expected to have massive impact on on everyone's environment for this so what is the winning formula for the the telecoms going forward well I think Phi G is an exciting world we are a 4G network today the Phi G spectrum hasn't been auctioned in India but what we are building today is what I call a 4G plus network which means the lot of the architectural principles of PI G we have already applied in my core networks today and in my transport network in that world I think IOT is gonna play a very very big role and if you want to do things like IOT and if you want to do things like blockchain now I think telco cloud has a huge role to play because we are the telcos are traditionally the only ones in a country anywhere in the world who have experiences experience in operating in very far front powerful places dealing with lot of the infrastructure challenges especially if you're in a developing country you know that you have to work with a poor power availability poor transport etc I do not see any of the big guys the the big cloud players really having those capabilities today I think telcos are gonna play a very big role in enabling that pi g io t work and it is going to be an exciting journey for telcos I think telcos will very soon be called tech companies that is one thing that I strongly believe in I think also many of the things that depend on blockchain will require the kind of cloud that telcos will create because a telco cloud is far more demanding than a traditional IT application in many ways for example latency or for example throughputs now all those things aren't very important in blockchain apple type of applications I think that's another exciting opportunity for telcos really is to get into that and of course there are discussions about smart cities smart government government and because of Kovach kharkova crisis I think many governments are gonna explore new ways of organizing Society's new ways of governing economic activities and the backbone for a lot of those things is gonna be our telecom networks and the cloud distributed clouds to the edge that we create so I think it'll create many many exciting business opportunities as a consequence of some of those technological innovation yeah Shanta I can't remember who said it as they said don't waste a crisis but Vasant Bora CTO of Vodafone idea pleasure talking with you thank you so much for joining us hope you enjoy the Red Hat event as it is distributed this year and definitely look to be able to meet you sometime at a future physical event back when we have those in the future Thank You Stu it's been a pleasure meeting you virtually and look forward to these all right lots more coverage from the cubes Red Hat summit at 20/20 activity I'm Stu minimun and thanks as always for watching [Music]

from around the globe it's the cube with digital coverage of Red Hat summit 2020 brought to you by Red Hat welcome back to the cubes coverage of Red Hat summit 2020 of course this year it's rather than all coming to San Francisco we are talking to red hat executives their partners and their customers where they are around the globe happy to welcome back one of our cube alumni Lisa Spellman who's a corporate vice president and general manager of the Intel Xeon and memory group Lisa thanks so much for joining us and where are you joining us from well thank you for having me and I'm a little further north than where the conference was gonna be held so I'm in Portland Oregon right now excellent yeah we've had you know customers from around the globe as part of the cube coverage here and of course you're near the mothership of Intel so Lisa you know but let's start of course you know the Red Hat partnership you know I've been the Intel executives on the keynote stage for for many years so talk about to start us off the Intel Red Hat partnership as it stands today in 2020 yeah you know on the keynote stage for many years and then actually again this year so despite the virtual nature of the event that we're having we're trying to still show up together and demonstrate together to our customers and our developer community really give them a sense for all the work that we're doing across the important transformations that are happening in the industry so we view this partnership in this event as important ways for us to connect and make sure that we have a chance to really share where we're going next and gather feedback on where our customers and that developer community need us to go together because it is a you know rich long history of partnership of the combination of our Hardware work and the open-source software work that we do with Red Hat and we see that every year increasing in value as we expand to more workloads and more market segments that we can help with our technology yeah well Lisa you know we've seen on the cube for for many years Intel strong partnerships across the industry from the data centers from the cloud I think we're gonna talk a little bit about edge for this discussion too though edge and 5g III think about all the hard work that Intel does especially with its partnership you know you talked about and I think that the early days of Red Hat you know the operating system things that were done as virtualization rolled out there's accelerations that gone through so when it comes to edge in 5g obviously big mega waves that we spend a lot of talking about what's what's Intel's piece obviously we know Intel chips go everywhere but when it comes to kind of the engineering work that gets done what are some of the pieces that Intel spork yeah and that's a great example actually of what I what we are seeing is this expansion of areas of workloads and investment and opportunity that we face so as we move forward into 5g becoming not the theoretical next thing but actually the thing that is starting to be deployed and transformed you can see a bunch of underlying work that Intel and Red Hat have done together in order to make that a reality so you look at they move from a very proprietary ASIC based type of workload with a single function running on it and what we've done is drive to have the virtualization capabilities that took over and provided so much value in the cloud data center also apply to the 5g network so the move to network function virtualization and software-defined networking and a lot of value being derived from the opportunity to run that on open source standard and have that open source community really come together to make it easier and faster to deploy those technologies and also to get good SLA s and quality of service while you're driving down your overall total cost of ownership so we've spent years working on that together in the 5g space and network space in general and now it's really starting to take off then that is very well connected to the edge so if you think about the edge as this point of content creation of where the actions happening and you start to think through how much of the compute or the value can I get out at the edge without everything having to go all the way back to the data center you start to again see how those open standards in very complex environments and help people manage their total cost of ownership and the complexity all right Lisa so when you're talking about edge solutions when I've been talking to Red Hat where their first deployments have really been talking to the service providers really I've seen it as an extension of what you were talking about network functions virtualization you know everybody talks about edges there's a lot of different edges out there the service providers being the first place we see things but you know all the way out even to the consumer edge and the device edge where Intel may or may not have you know some some devices there so help us understand you know where where you're sitting and where should we be looking as these technologies work you know it's a it's a great point we see the edge being developed by multiple types of organizations so yes the service providers are obviously there in so much as they already even own the location points out there if you think of all the myriad of poles with the the base stations and everything that's out there that's a tremendous asset to capitalize on you also see our cloud service provider customers moving towards the edge as well as they think of new developer services and capabilities and of course you see the enterprise edge coming in if you think of factory type of utilization methodologies or in manufacturing all of those are very enterprise based and are really focused on not that consumer edge but on the b2b edge or the you know the infrastructure edge is what you might think of it as but they're working through how do they add efficiency capability automation all into their existing work but making it better so at Intel the way that we look at that is it's all opportunities to provide the right foundation for that so when we look at the silicon products that we develop we gather requirements from that entire landscape and then we work through our silicon portfolio you know we have our portfolio really focused on the movement the storage and the processing of data and we try to look at that in a very holistic way and decide where the capability will best serve that workload so you do have a choice at times whether some new feature or capability goes into the CPU or the Zeon engine or you could think about whether that would be better served by being added into a smart egg type of capability and so those are just small examples of how we look at the entirety of the data flow in the edge and at what the use case is and then we utilize that to inform how we improve the silicon and where we add feature well Lisa as you were going through this it makes me also think about one of the other big mega waves out there artificial intelligence so lots of discussion as you were saying what goes where how we think about it cloud edge devices so how does AI intersect with this whole discussion of edge that we were just having yeah and you're probably gonna have to cut me off because I could go on for a long time on on this one but AI is such an exciting at capability that is coming through everywhere literally from the edge through the core network into the cloud and you see it infiltrating every single workload across the enterprise across cloud service providers across the network service providers so it is truly on its way to being completely pervasive and so again that presents the same opportunity for us so if you look at your silicon portfolio you need to be able to address artificial intelligence all the way from the edge to the cloud and that can mean adding silicon capabilities that can handle milliwatts like ruggedized super low power super long life you don't literally out at the edge and then all the way back to the data center where you're going for a much higher power at a higher capability for training of the models so we have built out a portfolio that addresses all of that and one of the interesting things about the edges people always think of it as a low compute area so they think of it as data collection but more and more of that data collection is also having a great benefit from being able to do an amount of compute and inference out at the edge so we see a tremendous amount of actual Zeon product being deployed out at the edge because of the need to actually deliver quite high-powered compute right there and that's improving customer experiences and it's changing use cases through again healthcare manufacturing automotive you see it in all the major fast mover edge industries yeah now we're really good points they make their Lisa we all got used to you know limitless compute in the cloud and therefore you know let's put everything there but of course we understand there's this little thing called the speed of light that makes it that much of the information that is collected at the edge can't go beyond it you know I saw a great presentation actually last year talking about the geosynchronous satellites they collect so much information and you know you can't just beam it back and forth so I better have some compute there so you know we've known for a long time that the challenge of you know of our day has been distributed architectures and edge just you know changes that you know the landscape and the surface area that we need the touch so much more when I think about all those areas obviously security is an area that comes up so how does Intel and its partners make sure that no matter where my data is and you talk about the various memory that you know security is still considered at each aspect of the environment oh it's a huge focus because if you think of people and phrases they used to say like oh we got to have the fat pipe or the dumb pipe to get you know data back and or there is no such thing as a dumb pipe anymore everything is smart the entire way through the lifecycle and so with that smartness you need to have security embedded from the get-go into that work flow and what people need to understand is they undergo their edge deployments and start that work is that your obligation for the security of that data begins the you collect that data it doesn't start when it's back to the cloud or back in the data center so you own it and need to be on it from the beginning so we work across our Silicon portfolio and then our software ecosystem to think through it in terms of that entire pipeline of the data movement and making sure that there's not breakdowns in each of the handoff chain it's a really complex problem and it is not one that Intel is able to solve alone nor any individual silicon or software vendor along the way and I will say that some of the security work over the past couple years has led to a bringing together of the industry to address problems together whether they be on any other given day a friend or a foe when it comes to security I feel like I've seen just an amazing increase over the past two two and a half years on the collaboration to solve these problems together and ultimately I think that leads to a better experience for our users and for our customers so we are investing in it not just at the new features from the silicon perspective but in also understanding newer and more advanced threat or attack surfaces that can happen inside of the silicon or the software component all right so Lisa final question I have for you want to circle back to where we started it's Red Hat summit this week-long partnerships as I mentioned we see Intel it all the cloud shows you partner with all the hardware software providers and the like so big message from Red Hat is the open hybrid cloud to talk about how that fits in with everything that Intel is doing it's an area of really strong interconnection between us and Red Hat because we have a vision of that open hybrid cloud that is very well aligned and the part about it is that it is rooted not just in here's my feature here's my feature from either one of us it's rooted in what our customers need and what we see our enterprise customers driving towards that desire to utilize the cloud to in prove their capabilities and services but also maintain that capability inside their own house as well so that they have really viable work load transformation they have opportunities for their total cost of ownership and can fundamentally use technology to drive their business forward all right well Lisa Spellman thank you so much for all the update from Intel and definitely look forward to seeing the breakouts the keynotes and the like yes me too all right lots more coverage here from the cube redhead summit 2020 I'm Stu minimun and thanks as always for watching [Music]