>>Hi and welcome back to Red Hat. Summit 2020. This is the Cube, and I'm your host. Stew minimum. We're talking so many topics. This event happening globally. We're treating our partners in the red hat executives where they are around the globe. And I guess right now is Nick Carr said, Who's the senior director of technology strategy with Red Hat, And Nic is coming to us. He's early in the Bahamas, speaking to us from his boat, though. Nick, pleasure to see you. And thanks so much for joining us. >>Very nice to meet you. Yeah, remote employees. And I enjoy that a lot. >>Absolutely. So we've been talking your team a lot. Of course. You know, many employees of Red Hat already were remote, but everyone now is working where they are. You're gonna be about a topic, of course, which is even more about riveted solutions. And where things are, we're going to talk about edge and five G before we get into the topic. It's a little bit about your background, how long you've been with red hat. And you know what? Your what your role is. >>So I joined right as a little more than five years ago after the acquisition. Off of all the companies that was working on open stack. Interesting technology. I've been in open source for the past 20 more years. Um, I was, uh, working miss of many distributions of Lennox over the years, so I consider myself in open source veteran. >>Excellent. I I remember that acquisition. We had the Cube at the open stack summit for many years on that, um, you know, new the company before the acquisition >>of the >>brand. And frankly, >>though, let's talk about it. First of all, you know, you talk about edge. Edge means different things to a >>lot of people >>are talking about it >>from a >>career perspective. You know, every customer in the Iot piece. Where does Red Hat into the whole notion of edge on? You know what kind of pieces of the portfolio? Yeah. >>So obviously, edge is about building an infrastructure that goes as far as possible to be as close as possible to where people are either producing or consuming data and building infrastructure as always, being the very heart off what Red Hat has been doing. And we've been growing. That's infrastructure capability. over time. So that means that today we feel the need to fulfill the requirements of those customers that want to extend their infrastructure to there. Because when we say the edge, we have to be countries that we're talking about. Like the layers of an onion more You dig into it. The more layers you find, the more particle case you have. There's no way there is a single. >>Yeah, no, you're absolutely right. So, you know, back in the open stack days, we talked a lot about in it, though Some of the barriers I know I've spoken to prizes. Who's, You know, we are of red Hat, though, you know, Maybe start there and help us understand. You know, where are we with the solution? Uh, talk about how five g fits into it. Of course. Everybody's talking about five feet. Well, that will take time, but help us understand where we are today. >>So, um, obviously for us, the edge years, just an extension of our open ivory clouds. Right? We have always been very vocal in saying that you need to be able to deploy the same workload in any place, and the edges are Justin extensions off these anyplace. So the same strategy that we've been developing first we use open stack, uh then with open shift and making open shift are both our development and our deployment platform for all types of workloads having open shift now, this report normally container based workloads, but also the visualization based workloads are exactly what we are doing at the edge. We want people to be able to deploy a single type of platform on various types of fruit brands managers globally. Ah is complete consistency so that there is no extra cost in maintaining those thousands, sometimes millions off added location into their existing infrastructure off course. In order to do that, we need to develop new tools to do the management to develop new AI or machine learning technology, to help people process not only the data coming from the platform, but also the management of the platform itself. We are reaching such scales that we wouldn't be able to do it. We've out. You are no from the platform yourself. >>Yeah, absolutely. And of course, scale is a relative before rise in. Yeah, I've talked to a couple of times. My understanding you've got news related. This that horizon went off? >>Yeah. This week Horizon has bean announcing ah, reinforce partnership between our two companies to help them heal their edge Platform. Ah, here we are talking about the first step in their edge platform which years? What we call the extension off the board we are talking about developing small data centers are going to be closer to the certainly. Um, And here we are talking about scales that, um can comprise to hundreds of data center, each having to 20 machines or more, um, to do all the processing of their future five g network and further, um, five g years, one off the enabler off edge. But it's also the reason for telcos to start deploying their edge network because the have a requirement to boot treatments off the information closer to where the five g antennas. And this is what we are developing. >>Alright. So, Nick, we talked. You've talked a minute ago about open stack and open fifth, help our audience understand a little bit. We've already talked a lot of customers. You don't. You can have one without the other, or you can layer off of the open stack when it comes to the the solution that you're talking about Verizon or ah, you know, other other service providers out there is it? Is it one is in both eyes that I've been there, Help us understand. >>So currently we have a complete shorts. We can do an edge platform. So Levi's open stack. You've got multiple customer doing that around the world. We can build an edge platform. We is open shift on top of the stack. But if we look at a future as we are, you know, designing it, we are looking at enabling simplicity and simplicity. Means deploying a single seeing open shift on to bare metal and have these bare metal platform deal we both vm and container so that you only have one AP I. You only have one management. You only have one thing to worry about. And since open shift and bark the OS, um, there is extreme simplicity in the methodology for updating or upgrading, and I think this is going to be a key point, making things simple, reducing the number of layers in your set. >>All right, that that really intrigued Nick, help us understand a little bit this ICO, Obviously any red hat doing is open source. It's how you're for that, you know, Red hat does. But you know how you're involved in the industry to help make the word that as edge solutions roll out that customers have flexibility in the first place. >>So you have multiple tee off partnership in this industry, you've got the partnership that are built around community and we are participating in numerous community, like the Lennox Foundation. Edge on many, many more. And this is where we are building the fundamental block off our future solutions we have. Partnership also is multiple vendor. Every time you're dealing with is a specific vertical. You will have a certain number of vendors that are going to be the one enabling 80% of the applications are going to be deployed, and that's okay for the edge. And then you have the partnership we made. We see our customers because the best source off requirements are always our customers. And that's something that we've now made a strong principle, which is to always find early adopters with when we are going to build a solution in a vertical sector on the horizon is one of them has been one of them. For what, a few years now and then replicate this success on to other customers of same sex. And we are reproducing this in the industry and manufacturing sector and in many other virtual. >>Excellent. Uh, you talked earlier about the open hybrid cloud. Obviously talk about they right, Wild help us understand, Nick. You know, edge and cloud. How do they actually go together? Many people. First of all, the people living article that was, you know, edge kills the cloud we've been talking about for a while. We know everything in i t is always additive. But how should customers on the surface but really be thinking about how edge cloud fit together >>in our design? The cloud and the edge is the same thing. You address the edge, you address the cloud, you should address your on premise art where the same way you use the same guy. And this driving FBI ease of communities, FBI, which we deliver through open ship. Um, soon. What is the difference? The difference is going to be who owns the edge, or we also machine running in your cloud who owns the machine running in your private data center. What network you're using, you're going to have Ah, a lot of constrained are going to be a bit more complex when you aren't yet. For example, you are sometimes going to go through the satellite connection. These huge delays in communication you're sometime going to put machines location that are absolutely not secure. So you need to have security layers. You're ensuring that nobody can remember these machines. These are you know it. But overall, once the deployment has done, we really, really on. People should consider that's their edge piece parts of their cloud or vice versa. >>Yeah, Nick, you brought up a lot of good points there. Security, of course. Critical. A one piece that I want to get your honest about. So we're spending a few years really looking at in a worker's process at the edge. What that's brought back core talk about AI work. Both generally understood praying things out at the edge. That's gonna happen. You know more of the core and then get out of the overall devices. What do you seeing where your customers But that overall, when it comes to their data. And >>from a technical perspective, data is the real real motivation about yet they are generating so much data that we are not able to process it anymore in a central location. So we have to process this data locally where it is generated. Or I suppose it's possible to where it is generated before sending, Let's say, a summary of these data or alerts or whatever the business process that pulls for to the center of operation. The use cases that we are demonstrating in this week, uh, that you can watch through the demo booth or you can watch increases. Ah, known presentation. Use the pays off manufacturer, which is installing sensors on many of the machine producing oh stuff. And when you have the right sensors like the vibration sensor or a temperature sensor, you can very easily develop knowledge off. Oh, this machine is going to break in a short amount of time. Maybe I should start scheduling some preventive maintenance on these machines, and you can do that by just actually leading the data and have humans read it. And you can do that a lot more efficiently. Training a machine learning algorithm This is what we are demonstrating that is processing the data and sending the alerts in real part when issues are discovered. Um, all this off course needs to be down in a very scalable fashion. Here we are talking about a use case where the customer may have 50 factories >>around the world. >>Are you updates all these machine learning models in all the factories when you have an update percent to learn about something you so data and data processing and now the eye. But big data are the heart off all of the use cases we, uh, discovered around old verticals for edge. And this is why we are now almost joining forces between the team working on AI. That's right out producing the open data hub and the team marking teams working on our solution. >>Yeah, I'm really glad you brought up manufacturing as the is one of the verticals. Look at their one of the turns and challenges we saw with all of that is yeah, some of the organization, Specifically, if you look at manufacturing, it could be an ot. Um, I'm curious is you're seeing solutions. Roll out your work, Aziz. How Customers are getting beyond those barriers. You know, some of the traditional silos where there was thoroughly collaborate. >>Well, it's always Ah, problem. Every time you introduce a change, you have to manage this in every project off, deploying something you anywhere well, fail if you do not account for the human factor and edge is no different in that. And when you're talking about the factory, if you're not directly talking with the people on the floor well, regarding their needs, you're only talking is a central guy. And you just arrived one day saying, Oh, everything is going to change. It's going to be a failure that the same way is a failure when the government make a decision without going through a consultative process before implementing it. So, um, nothing new, I would say. But as usual, And maybe because of the scale of edge, yeah, we will need to ensure that our customers are aware of those challenges that lay ahead of us. >>Alright, Well, next sounds Sounds like a lot of good progress. Been made definitely further breakout. What? From summit? You learn more. Thank you so much for joining. >>Thank you for having me >>all right. More coverage from the Cube at Red Hat Summit 2020. I'm screaming a man and as always what? Alright, Nick. Good stuff.