(lighthearted music) >> Hey all. Welcome back to theCube's coverage of Kubecon North America '22 CloudNativeCon. We're in Detroit. We've been here all day covering day one of the event from our perspective. Three days of coverage coming at you. Lisa Martin here with John Furrier. John, a lot of buzz today. A lot of talk about the maturation of Kubernetes with different services that vendors are offering. We talked a little bit about security earlier today. One of the things that is a hot topic is national security. >> Yeah, this is a huge segment we got coming up. It really takes that all that nerd talk about Kubernetes and puts it into action. We actually see demonstrable results. This is about advanced artificial intelligence for tactical decision making at the edge to support our military operations because a lot of the deaths are because of bad technology. And this has been talked about. We've been covering Silicon Angle, we wrote a story there now on this topic. This should be a really exciting segment so I'm really looking forward to it. >> Excellent, so am I. Please welcome back one of our alumni, Nick Barcet senior director, customer led open innovation at Red Hat. Great to have you back. Greg Forrest joins us as well from Lockheed Martin Director of AI Foundations. Guys, great to have you on the program. Nick, what's been your perception before we dig into the news and break that open of KubeCon 2022? >> So, KubeCon is always a wonderful event because we can see people working with us in the community developing new stuff, people that we see virtually all year. But it's the time at which we can really establish human contact and that's wonderful. And it's also the moments where we can make big topic move forward and the topics have been plenty at this KubeCon from MicroShift to KCP, to AI, to all domains have been covered. >> Greg, you're the director of AI foundations at Lockheed Martin. Obviously well known, contractors to the military lot of intellectual property, storied history. >> Greg: Sure. >> Talk about this announcement with Red Hat 'cause I think this is really indicative of what's happening at the edge. Data, compute, industrial equipment, and people, in this case lives are in danger or to preserve peace. This is a killer story in terms of understanding what this all means. What's your take on this relationship with Red Hat? What's the secret sauce? >> Yeah, it's really important for us. So part of our 21st century security strategy as a company is to partner with companies like Red Hat and Big Tech and bring the best of the commercial world into the Department of Defense for our soldiers on the ground. And that's exactly what we announced today or Tuesday in our partnership. And so the ability to take commercial products and utilize them in theater is really important for saving lives on the ground. And so we can go through exactly what we did as part of this demonstration, but we took MicroShift at the edge and we were able to run our AI payloads on that. That provided us with the ability to do things like AI based RF sensing, so radio frequency sensing. And we were also able to do computer vision based technologies at the edge. So we went out, we had a small UAV that went out and searched for a target on the ground. It found a target using its radio frequency capabilities, the RF capabilities. Then once we're able to hone in on that target, what Red Hat device edge and MicroShift enables us to do is actually then switch sensing modalities. And then we're able to look at this target via the camera and use computer vision-based technologies to actually more accurately locate the target and then track that target in real time. So that's one of the keys to be able to actually switch modalities in real time on one platform is really important for our joint all domain operations construct. The idea of how do you actually connect all of these assets in the environment, in the battle space. >> Talk about the challenge and how hard it is to do this. The back haul, you'll go back to the central server, bring data back, connecting things. What if there's insecurity around connectivity? I mean there's a lot of things going, can you just scope the magnitude of how hard it's to actually deploy something at a tactical edge? >> It is. There's a lot of data that comes from all of these sensors, whether they're RF sensors or EO or IR. We're working across multiple domains, right? And so we want to take that data back and train on that and then redeploy to the edge. And so with MicroShift, we're able to do that in a way that's robust, that's repeatable, and that's automated. And that really instills trust in us and our customers that when we deploy new software capabilities to the edge over the air, like we did in this demonstration that they're going to run right on the target hardware. And so that's a huge advantage to what we're doing here that when we push software to the edge in real time we know it's going to run. >> And in realtime is absolutely critical. We talk about it in so many different industries. Oh, it's customers expect realtime access whether it's your banking app or whatnot. But here we're talking about literally life and death situations on the battlefield. So that realtime data access is literally life and death. >> It's paramount to what we're doing. In this case, the aircraft started with one role which was to go find a radio frequency admitter and then switch roles to then go get cameras and eyes on that. So where is that coming from? Are there people on the ground? Are there dangerous people on the ground? And it gives the end user on the ground complete situational awareness of what is actually happening. And that is key for enhanced decision making. Enhanced decision making is critical to what we're doing. And so that's really where we're advancing this technology and where we can save lives. >> I read a report from General Mattis when he was in service that a lot of the deaths are due to not having enough information really at the edge. >> Greg: Friendly fire. >> Friendly fire, a lot of stuff that goes on there. So this is really, really important. Nick, you're sitting there saying this is great. My customer's talking about the product. This is your innovation, Red Hat device edge in action. This is real. This is industrial- >> So it's more than real. Actually this type of use case is what convinced us to transform a technology we had been working on which is a small form factor of Kubernetes to transform it into a product. Because sometimes, US engineers have a tendency to invent stuff that are great on paper, but it's a solution trying to find a problem. And we need customers to work with us to make sure that do solution do solve a real problem. And Lockheed was great. Worked with us upstream on that project. Helped us prove out that the concept was actually worth it and we waited until Lockheed had tested the concept in the air. >> Okay, so Red Hat device edge and MicroShift, explain that, how that works real quick for the folks that don't know. So one of the thing we learned is that Kubernetes is great but it's only part of the journey. In order to get those workloads on those aircraft or in order to get those workloads in a factory, you also need to consider the full life cycle of the device itself. And you don't handle a device that is inside of a UAV or inside of a factory the same way you handle a server. You have to deal with those devices in a way that is much more akin to a setup box. So we had to modify how the OS was behaving to deal with devices and we reduced what we had built in real for each edge aspect and combined it with MicroShift and that's what became with that Red Hat device edge. >> We're in a low SWAP environment, space, weight and power, right? Or very limited, We're on a small UAS in this demonstration. So the ability to spool up and spool down containers and to save computing power and to do that on demand and orchestrate that with MicroShift is paramount to what we're doing. We wouldn't be able to do it without that capability. >> John: That's awesome. >> I want to get both of your opinions. Nick, we'll start with you and then Greg we'll go to you. In terms of MicroShift , what is its superpower? What differentiates it from other competing solutions in the market? >> So MicroShift is Kubernetes but reduced to the strict minimum of a runtime version of Kubernetes so that it takes a minimal footprint so that we maximize the space available for the workload in those very constraints environments. On a board where you have eight or 16 gig of RAM, if you use only two gig of that to run the infrastructure component, you leave the rest for the AI workload that you need on the drone. And that's what is really important. >> And these AI payloads, the inference that we're doing at the edge is very compute intensive. So again, the ability to manage that and orchestrate that is paramount to running on these very small board computers. These are small drones that don't have a lot of weight that don't allow a lot of space. >> John: Got to be efficient >> And be efficient with it. >> How were you guys involved? Talk about the relationship. So you guys were tightly involved. Talk about the roles you guys played together. Was it co-development? Was it customer/partner? Talk about the relationship. >> Yeah, so we started actually with satellite. So you can think of small cube sets in a very similar environment to a low powered UAV. And it started there. And then in the last, I would say year or so, Nick we have worked together to develop MicroShift. We work closely on Slack channels together like we're part of the same team. >> John: That's great. >> And hey Red Hat, this is what we need, this is what we're looking for. These are the constraints that we have. And this team has been amazing and just delivered on everything that we've asked for. >> I mean this is really an example of the innovation at the edge, industrial edge specifically. You got an operating system, you got form factor challenges, you got operating parameters. And just to having that flex, you can't just take this and put it over there. >> But it's what really is a community applied to an industrial context. So what happened there is we worked as part of the MicroShift community together with a real time communication channel, the same slack that anybody developing Kubernetes uses we've been using to identify where the problems were, how to solve them, bring new ideas and that's how we tackle these problems. >> Yeah, a true open source model I mean the Red Hat and the Lockheed teams were in it together on a daily basis communicating like we were part of the same company. And and that's really how you move these things forward. >> Yeah, and of course open source is great but also you got to lock down the security. How did you guys handle that? What's going on with the security? 'Cause you got to make sure no take over the devices. >> So the funny thing is that even though what we produce is highly inclusive of security concern, our development model is completely open. So it's not security biopurification, it's security because we apply the best practices. >> John: You see everything. >> Absolutely. >> Yes. >> And then you harden it in the joint development, there it is. >> Yeah, but what we support, what we offer as a product is the same for Lockheed or for any other customer because there is no domain where security is not important. When you control the recognition on a drone or where you control the behavior of a robot in a factory, security is paramount because you can't immobilize a country by infecting a robot the same way you could immobilize a military operation- >> Greg: That's right. >> By infecting a UAV. >> Not to change the subject, but I got to go on a tangent here cause it pops in my head. You mentioned cube set, not related to theCUBE of course. Where theCube for the video. Cube sets are very powerful. People can launch space right now very inexpensively. So it's a highly contested and congested environment. Any space activity going on around the corner with you guys? 'Cause remember the world's not around, it's edge is now in space. Mars is the edge. >> That's right. >> Our first prototype for MicroShift was actually a cube set. >> Greg: That's where it started. >> And IBM project, the project called Endurance. That's the first time we actually put MicroShift into use. And that was a very interesting project, very early version of MicroShift . And now we have talks with many other people on reproducing that at more industrial level this was more like a cool high school project. >> But to your point, the scalability across different platforms is there. If we're running on top of MicroShift on this common OS, it just eases the development. Behind the scenes, we have a whole AI factory at Lockheed Martin where we have a common ecosystem for how we actually develop and deploy these algorithms to the edge. And now we've got a common ecosystem at the edge. And so it helps that whole process to be able to do that in automated ways, repeatable ways so we can instill trust in our DRD customer that the validation of verification of this is a really important aspect. >> John: Must be a fun place to work. >> It is, it's exciting. There's endless opportunities. >> You must get a lot of young kids applying for those jobs. They're barely into the whole. I mean, AI's a hot feel and people want to get their hands on real applications. I was serious about space. Is there space activity going on with you guys or is it just now military edge, not yet military space? Or is that classified? >> Yeah, so we're working across multiple fronts, absolutely. >> That's awesome. >> What excite, oh, sorry John. What excites you most, never a dull moment with what you're doing, but just the potential to enable a safer, a more secure world, what excites you most about this partnership and the direction and the we'll say the trajectory it's going on? >> Yeah, I think, for me, the safer insecure world is paramount to what we're doing. We're here for national defense and for our allies and that's really critical to what we're doing. That's what motivates me. That's what gets me up in the morning to know that there is a soldier on the ground who will be using this technology and we will give be giving that person the situational awareness to make the right decisions at the right time. So we can go from small UAVs to larger aircraft or we can do it in a small confined edge device like a stalker UAV. We can scale this up to different products different platforms and they don't even have to be Lockheed Martin >> John: And more devices that are going to be imagined. >> More devices that we haven't even imagined yet. >> Right, that aren't even on the frontier yet. Nick, what's next from your perspective? >> In the domain we are in, next is always plenty of things. Sustainability is a huge domain right now on which we're working. We have lots of things going on in the AI space, stuff going on with Lockheed Martin. We have things going on in the radio network domain. We've been very heavily involved in telecommunication and this is constantly evolving. There is not one domain that, in terms of infrastructure Red Hat is not touching >> Well, this is the first of multiple demonstrations. The scenarios will get more complex with multiple aircraft and in the future, we're also looking at bringing a lot of the 5G work. Lockheed has put a large focus on 5G.mil for military applications and running some of those workloads on top of MicroShift as well is things to come in the future that we are already planning and looking at. >> Yeah, and it's needed in theater to have connectivity. Got to have your own connectivity. >> It's paramount, absolutely. >> Absolutely, it's paramount. It's game-changing. Guys, thank you so much for joining John and me on theCube talking about how Red Hat and Lockheed Martin are working together to leverage AI to really improve decision making and save more lives. It was a wonderful conversation. We're going to have to have you back 'cause we got to follow this. >> Yeah, of course. >> This was great, thank you so much. >> Thank you very much for having us. >> Lisa: Our pleasure, thank you. >> Greg: Really appreciate it. >> Excellent. For our guests and John Furrier, I'm Lisa Martin. You're watching theCUBE Live from KubeCon CloudNativeCon '22 from Detroit. Stick around. Next guest is going to join John and Savannah in just a minute. (lighthearted music)

(bright music) >> Welcome to this Kube Conversation. I'm Dave Nicholson. And today we have a very special guest from Red Hat, Nick Barcet. Nick is the Senior Director of Technology, Technology Strategy at Red Hat. Nick, welcome back to theCUBE. >> Thank you. It's always a pleasure to be visiting you here virtually. >> It's fantastic to have you here. I see a new office surroundings at Red Hat. Have they taken a kind of a nautical theme at the office there? Where are you joining us from? >> I'm joining from my boat now, I've been living on my boat for the past few years, and that's where you'll find me most of the time. >> So would you consider your boat to be on the Edge? >> It's certainly one form of Edge. You know, there are multiple forms of Edge and a boat is one of those forms. >> Let's talk about Edge now. We're having this conversation in anticipation of KubeCon CloudNativeCon that's coming up North America 2021, coming up in Los Angeles. Let's talk about specifically the Edge, where the Edge, Edge computing and Kubernetes come together from a Red Hat perspective. Walk us through that, talk about some of the challenges that people are having at the Edge, why Kubernetes is something that would be considered at the edge. Walk us through that. >> Let's start from the premises that people have been doing stuff at the Edge for ages. I mean, nobody has been waiting for Kubernetes or any other technology to start implementing some form of computing that is happening in their stores, in their factories, wherever. What's really new today is when we talk about Edge computing, it's reusing the same technology we've been using to deploy inside of the data center and expand that all the way to the Edge. And that's what, from my perspective, constituents, Edge computing or the revolution it bring. So that means that the same GitOps, DevSecOps methodology that we were using into that center are now expandable all the way to those devices that leaves in where locations and that we can reuse the same methodology, the same tooling, and that includes Kubernetes. And all the efforts we've been doing over the past couple of years has been to make Kubernetes even more accessible for the various Edge typologies that we are encountering when discussing with our customer that have Edge projects. >> So typically when we think of a Kubernetes environment, you're talking about containers that are contained in pods, that live on physical clusters, despite all of the talk of a no-code and serverless, we still live in a world where applications and microservices run on physical servers. Are there practical limitations in terms of just how small you can scale Kubernetes? How far, how close to the Edge can you get with the Kubernetes deployment? >> So in theory, there is really no limit. As the smallest devices are always bigger than Kubernetes itself. But the reality is you never use just Kubernetes, you use Kubernetes with a series of other projects that makes it complete, or for example, stuff that is going to be reporting telemetry, components that are going to help you automatically scale, et cetera. And the further you go into the Edge, the less of these competence you can afford. So you have to make trade-offs when you reduce the size of the device. Today, what Red Hat offers, is really concentrated to where we can deliver a full OpenShift experience. So the smallest environments on which we would recommend to run OpenShift at the Edge is a single node is roughly 24 gigabytes of RAM, which is you could buy it, sorry, which is already a relatively big Edge device. And when you go a step lower then, that's where we would recommend using a standard rail for Edge configuration or something similar. Not Kubernetes anymore. >> So you said single node, are you let's double click on that for a second. Is that a single physical node that is abstracted in a way to create some level of logical redundancy? When you say single node, walk us through that. We've got containers that are in pods, so what are we talking about? >> You have, based on your requirements, you can have different way of addressing your compute need at the Edge. You can have those smallest of clusters. And this would be three nodes that are delivered, with is the control plane and the worker nodes integrated into one. When you want to go a step further, you could use worker nodes that are controlled remotely via a central control plane that is at a central site. And when you want to go, even one step further deploy Kubernetes on a very small machine, but that remains fully functional even if disconnected that's when you would use the thing that is not anymore a cluster, which is a single note, Kubernetes where you still have access to the full Kubernetes API, regardless of the connectivity of your site, whether it's active or not, whether you're at sea or in the air or not. And that's where we still offer some form of software high vulnerability, because Kubernetes, even on a single node, it'll still detect if a container dies and restarted and provide similar functionality like this, but it won't provide hardware availability since we are a single node. >> And that makes sense. Yeah, that makes, yeah, it makes perfect sense. And I would suggest that we refer to that as a single node cluster, just because we like to mix it up with terminology in our business and sometimes confuse people with it. >> Technically, that was the choice we made, actually. You like to call it a cluster because it's not a cluster >> Exactly. No, I appreciate that. Absolutely. So what's be explicit about what the trade-offs are there. Let's say that I'm thinking of deploying something at the Edge, and I'm going use Kubernetes to orchestrate my container environment and pretend for a moment that space and cost aren't huge limiting factors. I could put a three node cluster in, but the idea of putting in a single node is very, it's attractive. Where does, where's the line drawn in terms of what you would recommend from, you know, what are the trade offs? What am I losing, going to the single node cluster? See I just called that. >> Well, in a nutshell, you're losing hardware high availability. Meaning if one of your server fails since you only have one server, you lose everything. And there is no way around that. That's the biggest trade-off. Then you have also a trade-off on the memory used by the control plane, which you won't be able to use to do something else. So if I have a site with excellent connectivity and the biggest loss of connectivity might be counted in hours, maybe a remote worker use a better solution because this way, I have a single central-side that carries my control plane, and I can use all the RAM and all the CPU's on my local site to deploy my workloads, not to carries a control plane. To give you an example of these trade-off in the telco space, for example, if you're deploying an antenna in a city, you have plenty of antennas covering that city. And therefore, the loss of one antenna is not a big deal. So in that case, you will be tempted to use a remote worker because you will be maximizing your use of the RAM on the sites for the workload, which is let's have people establish communication using their phones. But now, we take another antenna that we are getting to locate in a very remote location. There, if this antenna fail, everybody fails. There's nobody that is able to make calls, even emergency vehicles cannot discuss together very often. So in that case, it's a lot better to have an autonomous deployment, something where the control plane and the workload itself are being run in one box. And this one box in fact can be duplicated. There could be a another box that is either seating in a truck in case of emergency or off, but on the antenna site, so that in case of a major failure, you have a possibility to re to restore it. So it really depends on what's your sets of constraints in terms of availability in SIM of efficiency of your RAM use is going to be that it's going to make you choose between one or the other of the deployment models. >> No, that's a great example. And so it sounds like it's not a one size fits all world, obviously. Now, from the perspective of the marketplace, looking in at Red Hat, participating in this business, some think of Red Hat as the company that deployed Linux 20 years ago. Help us make that connection between Red Hat today and what you've been doing for the last 20 years and this topic of Edge computing, 'cause some people don't automatically think of Red Hat an Edge computing. I do, I think they should, (chuckles) but help us understand that. >> Yeah, obviously a lot of people consider that Red Hat is Red Hat, Linux, and that's it. The Red Hat Enterprise Linux is what we've been known since our beginnings 25 years ago, and what has made our early success. But we consider ourselves more of an infrastructure company. We have been offering for the past 20 years, the various component that you need to deploy server, run and manage your workloads across data centers and make sure that you can store your data, and that you can automate your operations on top of this infrastructure. So we really consider ourselves much more of a company that offers everything that enables you to run your servers and run your workloads on top of your server. And that includes a tool to do virtualization, that includes tool to do continuous deployment of containers. And that's where Kubernetes entered in play about 10 years ago. Well, first it was OPAs that then became Kubernetes and the OpenShift offering that we have today. >> Yeah. Thanks for that. So I have, I've got a final question for you. It's a little bit off topic, but it's related, this is in the category of Nick predicts. So when does Nick predict that we will get to a point where we tip beyond the 50/50 point cloud versus on-premises IT spending, if you accept today that we're still in the neighborhood of 75 to 80% on-premises. When will we hit the 50/50 mark? I'm not asking you for the hundred percent cloud date, but give us a date, you give us a month and a year for 50/50. >> Given the progression of cloud, if there was no Edge, we could said two to three years from now, we would be at this 50/50 mark. But the funny thing is that at the same time, as the cloud progresses, people start realizing that they have needs that needs to be solved locally. And this is why we are deploying Edge-based solution, solution which reliably can provide answers, regardless of the connectivity to the cloud, regardless of the bandwidth. There are things that I would never want to do, like feeding a size on feeds from 4K cameras, into my cloud environment that won't scale, I won't have the bandwidth to do so. And therefore, maybe the answer to your question is, it's going to be asymptotic, and it's almost impossible to predict. >> So that is a much better answer than giving me an exact date and time, because (chuckles) because it reveals exactly the reality that we're living in. Again, there is, you know, it's fit for function. It's not cloud for cloud's sake, compute resources, data, resources have a place that they naturally belong oftentimes. And oftentimes that is on the Edge, whether it's on the edge of the edge of the world in a sailboat or out in a single server, not node, or I keep wanting to single node cluster, it's killing me. I dunno why, I think it's so funny, but a single node implementation of OpenShift where you can run Kubernetes on the Edge, it's a fascinating subject. Anything else that you want to share with us that we didn't get? >> I think one aspect that we never talk enough is how do you manage at the scale of Edge? Because even though each Edge site is very small, you can have thousands, even hundreds of thousands of these single node something that are running all over the place. And I think that what you're seeing in advent cluster management for Kubernetes, and particularly the 2.4 version that we are going to be announcing this week and actually releasing in November is I think a pretty good answer to that problem on how do I deploy with zero touch these devices? How do I update them, upgrade them? How do I deploy the workloads on top of that? How do I ensure to have the right tooling to deploy that at the scale? And we've done the testing now of ACM with up to 2,000 clusters, connected to a single ACMs. And in the future, we are planning on building federation of those, which really gives us the possibility to provide the tooling needed to manage at its scale. >> Excellent. Excellent. Yeah. That's whenever we start talking about anything in the realm of containerization and Kubernetes scale starts to become an issue. It's no longer a question of a human being managing 10 servers and 50 applications. We start talking about tens of thousands and hundreds of thousands of instances where it's beyond human scale. So that's obviously something that's very, very important. Well, Nick, I want to thank you for becoming a Kube veteran once again. Thanks for joining this Kube Conversation from Dave Nicholson, this has been a Kube Conversation in anticipation of KubeCon and CloudNativeCon North America 2021. Thanks for tuning in. (bright music)

>> Announcer: From around the globe, it's theCUBE! With coverage of KubeCon and CloudNativeCon Europe 2020, virtual. Brought to you by Red Hat, the Cloud Native Computing Foundation, and ecosystem partners. >> Hi, and welcome back, I'm Stu Miniman, and this is theCUBE's coverage of KubeCon CloudNativeCon 2020 in Europe, the virtual edition of course. We're talking to practitioners, we're talking to contributors, we're talking to end users from around the globe where they are, and of course when we talk about the CNCF, it's not just Kubernetes, there's a lot of projects in there, and it's not just for building things in the cloud, one of the interesting use cases that we've been talking about the last year or two has been about how edge computing fits into this whole ecosystem. To help us dig in a little bit deeper into that conversation, welcome on board one of our CUBE alumni, Nick Barcet, he is a senior director of technology strategy at Red Hat. Nick, great to see you again, thanks so much for joining us. >> Thanks for inviting me again. >> All right, so as I teed up, containerization and Kubernetes, a lot of times people think about it's the big public cloud that's my data center, but of course, cloud is not a destination, there's so much happening with the containerized world, and of course these lightweight environments, when we can make them lightweight, makes sense to go to the edge, so if you could, just tell us where we are with the state of containerization and the cloud-native ecosystem, and where does that fit with edge computing today? >> So what we're seeing currently is every ISV, every customer we talk with, are converting to developing their application with container as a target. This is making it so much simpler for them to be able to establish their application wherever they want. Of course, when we add, for example, the operator framework that we just got accepted into the CNCF, and normalize how you're going to do day one and day two of the life cycle of this container, this is making things a lot simpler. And this is allowing us to have the same principle reapplied for deployments happening in the cloud, on your private data center, and anywhere at the edge. And that's really the core of our strategy, whether in the open source community, or as a commercial company. It is to make all these different footprints absolutely equal when you are writing code, when you're deploying code, when you're managing it. >> Yeah, Nick, we talk about the edge from my standpoint, tend to think that it is going to need a lighter weight, smaller footprint than if I'm thinking about my data center or the environment, reminds me some ways of of course Red Hat, but CoreOS was how do we build something that can be updated faster and be a thinner operating system. When we think of Kubernetes, Kubernetes today isn't as simple, there's obviously a lot of managed services out there, of course with OpenShift you've got an industry leading solution out there, but is there something different I need to do to be able to do containerization and Kubernetes at the edge? How does that fit? >> As a developer, as a user, I hope you have nothing different to do. It's our job to make our platform suit the requirement that are very specific to the edge. For example, if you're going to put Kubernetes inside of a plane, you're not going to be able to use all the space you want. You're very space-constrained. Or if you put it in a train, or if you put it in a boat, you're going to have different types of constraints. And we need to be able to have a implementation of Kubernetes that fits the smallest requirement, but still has the components that enables you as a developer or you as the administrator to feel at home regardless of the implementation of it. And that's the real beauty of what we are trying to do, and that's why we are not rushing it. We are trying to do it upstream so that we have something that is as smooth as possible across different points. >> All right, when we talk about going to the edge, one of the considerations of course is the network to get there. So help us connect what the impact is of 5G, where we are with the rollout, and are there any industries maybe that are leading the pack when it comes to this discussion? >> Yeah, so when I talk about 5G, I like to distinguish two things. There is 5G as the network that the carriers are currently deploying to support all kinds of terminal endpoints. And it happens that in order to have an efficient 5G deployment, operators use edge technology to deploy computing power as close as possible to the tower. So that the latency between your device and what is connecting you to the internet, the time packets take to go across that last mile, is as short as possible. There is a second case, which is also very interesting in the edge part. Which is private 5G, because private 5G enables the customer to establish his, let's say his own antenna, his own local 5G network completely secure, that will enable connecting sensors or devices of all kinds, without having to run wire, and in a much more reliable way than if you're using Wi-Fi or similar kinds of connectivity. So these two aspects are crucial to edge, one because edge is enabling the deployment of it, the other one because it's enabling the growth of the number of sensors without multiplying the cost like crazy. In terms of deployments, well, you know our largest reference is Verizon, and Verizon is moving forward with its plan. This is going very well, I believe they have communicated around this so I will point you around what Verizon has stated on their deployment, but we have multiple other customers starting their journey and clearly, the fact that we have the ability to deploy the stack on the version of Kubernetes that is basically the same regardless of where you're deploying it. That has the ability to support both containers and VM for those applications that are not yet containerized, makes a huge difference in the simplicity of this transition. >> Yeah, it's interesting, you talk about the conversion between virtual machines and containers. One of the big use cases often talked about for edge computing is in industrial manufacturing, and there you've got the boundary between IT and OT, and OT traditionally doesn't want to even think about all those IT conversions and challenges that they've got their proprietary systems for the most part, so is that something, speak to what you're seeing in that segment. >> So, it's interesting, because we just released last week our first inclination about the industrial blueprint that we are proposing. And for us, the convergence between IT and OT comes at when you have automation in the interpretation of data provided by sensors. This automation generally takes the form of machine learning algorithms, that are deployed on the factory floors, that analyzes the sensor data in real time, and will be able to predict failure, or will be able to look at video feed to verify that employees are respecting safety measures, and many many other applications. So because of the value this brings to the operational people, this bridge is very easily closed once you've resolved the technical difficulty, and the technical difficulty are mostly what I call plumbing. Plumbing that takes the form of norms being widely different between the industrial world and the IT world so far. Difficulties because you don't speak the same language. Let's take an example. In the industrial world, CAN is the way you're synchronizing time resources. In the IT world, we have been using other protocol, and more recently, especially in the telco space, we're using PTP. But it seems that PTP is now crossing over to the industrial world, so things are slowly but very safely evolving with something that is enabling this next wave of revolution into the factories. >> Yeah, Nick, it's been fascinating always to watch when you have some of those silos, and when is the right time that things pull together. Curious, one of the big questions in 2020 of course is with the global pandemic going on, which projects get accelerated, and which ones might be pushed off a little bit, where does edge computing fall in the conversations you're having with customers, is that something mission-critical that they need to accelerate, or is it something that might take a little bit longer, possibly even a delay with the current pandemic? >> So it's quite hard to answer this question because we are in an up slope. Is the slope less up now than it would have been without the pandemic, I have no way to tell. What I'm seeing is a constant uptick of people moving forward with their projects, in fact some projects are made, for example for worker safety, are made even more urgent than they were before, because by just analyzing video feed, you can ensure that your processes prevents too close contact between coworkers, and making them vulnerable in this way. So it really depends on the industry, I imagine, but right now we see the demand growing regardless of the pandemic. >> All right, Nick, you mentioned earlier that when I think about the edge, it should be the same code, I hopefully shouldn't have to think about it differently no matter where it is. That begs the question, help connect OpenShift for us as to what is Red Hat offering when it comes to the edge solution with OpenShift? >> So, you have, what we say is the edge is like an onion, where you have different layers. And every time I look at the onion in the perspective of a given customer, the layers are very different. But what we are finding is, similar requirements in terms of security, in terms of power consumption, in terms of space allocated for the hardware, and in order to satisfy these requirements, we found out that we need to build three new ways of deploying OpenShift, so that we can match all of these potential layers. The first one that we have released and are announcing this week is OpenShift deployable on three nodes, that means that you have your supervisors, your controllers, and your workers, on the same three physical machines. That's not the smallest footprint that we need, but it's a pretty good footprint to solve the case of a factory. In this environment, with these three nodes, we have something that is capable of being fully connected or working disconnected with. The second footprint that we need to be able to satisfy for is what we call single node deployment. And single node deployment from our perspective need to come in two flavors. The easy way, the one we're going to be releasing next quarter, is what we call remote worker node. So you have your controllers in a central site, and you can have up to 2000 remote worker nodes spread across as many site as you want. The caveat with this is that you need to have full time connectivity. So in order to solve for this connected site, then we need something that is a standalone single node deployment, and that's something that a lot of people have prototypes so far, and we are currently working on delivering a version that we hope is going to be satisfying 99% of the requirement, and is going to be fully upstream. >> All right, last piece on this, Nick, how should I be thinking about managing my environment when it comes to the edge, seen a lot of course from Red Hat at Red Hat Summit and talked to some of your peers, some recent announcements, so how do we plug in what's happening at the edge and make sure we've got full visibility and management across all of my environments? >> So if I had one word to explain what we need to do, it's GitOps. Basically, you need immutable deployments, you need to be pulling configuration and all information from a central site and adapt it to the local site, without manual intervention. You need full automation. And you need a tool to manage your policies on top of it, and of course aggregate information on how things are going. What we don't want is to have to sit one administrator per site. What we do not want is to have to send people on each site at the time of deployment. So you need to be abiding by this completely automated model in order to be edge compliant. Does that make sense? >> It does, and I'm assuming the ACM solution, Advanced Cluster Management, is a piece of that overall offer. >> Absolutely, ACM is the way we present, we organize policies, the way we get reporting information, and the way we do our GitOps automation. >> All right, so Nick, final question for you, give us a little bit of a look forward, you just mentioned earlier one of the things that's getting worked on is that single node disconnected type of solution. What else should we be looking at in the maturity of edge solutions in this containerizing Kubernetes world? >> So it's not only about the architecture that we need to support. It's a lot more about the workloads that we are going to have running there. And in order to help our customer make their choice, in how they design the network, we need to provide them with what we call blueprints. And in our mind, a blueprint is more than just a piece of paper. It's actually a complete set of instruction, abiding with this GitOps model that I described, that you can pull from a Git repository, that enables automation of the deployment of something. So for example, the first blueprint we are going to be releasing is the one for industrial manufacturing using AIML, and this is going to be something that we are going to be maintaining over time, accepting contribution from outside, and is an end to end example of how to do it in a factory. We are going to follow up with that with other blueprints for 5G, for private 5G, for how do you deploy that in maybe a healthcare environment, et cetera, et cetera, the idea here is to exemplify and help people make the right choices and also ensuring that the stack we provide at one point in time remains compatible given the complexity of the components we have in there over time, and that's really the thing that we think we need to be providing to our customers. >> All right, well Nick, thank you so much for giving us the update, in regards to edge computing, really important and exciting segment of the market. >> Thank you very much, 'twas a pleasure being with you once again. >> All right, and stay with us, lots more coverage from KubeCon CloudNativeCon 2020 in Europe, the virtual edition. I'm Stu Miniman and thank you for watching theCUBE. (calm music)

>> Announcer: From around the globe, it's theCUBE with digital coverage of Red Hat Summit 2020. brought to you by Red Hat. >> Welcome back. This is theCUBE's coverage of Red Hat Summit 2020. Of course this year instead of all gathering together in San Francisco, we're getting to talk to Red Hat executives, their partners and their customers where they are around the globe. I'm your host Stuart Miniman and happy to welcome to the program Nick Barcet, who is the Senior Director of Technology Strategy at Red Hat. He happens to be on a boat in the Bahamas. So Nick, thanks so much for joining us. >> Hey thank you for inviting me. It's a great pleasure to be here and it's a great pleasure to work for a company that has always dealt with remote people. So it's really easy for us to, kind of thing. >> Yeah Nick. You know it's interesting, I've been saying probably for the last 10 years that the challenge of our time is really distributed systems. You know from a software standpoint that's what we talk about and even more so today number one of course the current situation with the global pandemic but number two the topic we're going to talk to you about is edge and 5G. It's obviously gotten a lot of hype. So before we get into that my understanding Nick, you know you came into Red Hat through an acquisition. So give us a little bit about your background and what you work on for Red Hat. >> About five years ago company I was working for eNovance got acquired by Red Hat and I've been very lucky in that acquisition where I found a perfect home to express my talent. I've been free software advocate for the past 20 some years. Always been working in free software for the past 20 years and Red Hat is really wonderful for that. >> Yeah it's addressing me okay yeah. I remember back the early days we used to talk about free software. Now we don't talk free, open-source is what we talk about you know. Bream is a piece of what we're doing but let's talk about you know, You know, eNovanceI absolutely remember they were partner of Red Hat. I talked to them and a lot at some of the OpenStack shows. So I'm guessing when we're talking about edge, these are kind of the pieces coming together of what Red had done for years with OpenStack and with NFB. So what, what's the solution set you're talking about? Bring us inside, how you're helping your customers with these types of split. >> Well clearly the solution we are trying to put together as to combine what people already have with where they want to go. Our vision for the future is a vision where OpenShift is delivering a common service on any platform including hardware at the far edge on a model where both v-ends and containers can be hosted on the same machine. However there is a long road to get there and until we can fulfill all the needs, we are going to be using combination of OpenShift, OpenStack and many other product that we have in our portfolio to fulfill the needs of our customer. We've seen for example Verizon starting with OpenStack quite a few years ago now going with us with OpenShift that they're going to place on up of OpenStack or directly on bare metal. We've seen other big telcos use that in very successful to deploy their 5G networks. There is great capabilities in the existing portfolio. We are just expanding that simplifying it because when we are talking about the edge, we are talking about managing thousands if not millions of device and simplicity is key if you do not want to have your management parts in Crete. >> Excellent. So you talked a lot about the service providers. Obviously 5G as a big wave coming a lot of promise as what it will enable both for the service providers as well as the end-users. Help us understand where that is today and what we should expect to see in the coming years though. >> So in respect of 5G, there is two reason why 5G is important. One it is-- It is important in terms of edge strategy because any person deploying 5G will need to deploy computer resources much closer to the antenna if they want to be able to deliver the promise of 5G and the promise of very low latency. The second reason it is important is because it allows to build a network of things which do not need to be interconnected other than through a 5G connection. And this simplifies a lot some of the edge application that we are going to see where sensors need to provide data in a way where you're not necessarily always connected to a physical network and maintaining a WiFi connection is really complex and costly. >> Yeah Nick a lot of pieces that sometimes get confused or conflated, I want you to help us connect the dots between what you're talking about for edge and what's happening in the telcos and the the broader conversation about hybrid cloud or Red Hat calls at the open hybrid cloud because you know there were some articles that were like you know edge is going to kill the cloud. I think we all know an IP nothing ever dies, everything is all additive. So how do these pieces all go together? >> So for us at Red Hat, it's very important to build edge as an extension of our open hybrid cloud strategy. Clearly what we are trying to build is an environment where developers can develop workloads once and then can the administrator that needs to deploy a workload or the business mode that needs to deploy a workload can do it on any footprint. And the edge is just one of these footprint as is the cloud as is a private environment. So really having a single way to administer all these footprints, having a single way to define the workloads running on it, is really what we are achieving today and making better and better in the years to come. The reality of... to process the data as close as possible to where the data is being consumed or generated. So you have new footprints to let's say summarize or simplify or analyze the data where it is being used. And then you can limit the traffic to a more central site to only the essential of it. It is clear that with the current growth of data, there won't be enough capacity to have all the data going directly to the central path. And this is what the edge is about, making sure we have intermediary of points of processing. >> Yeah absolutely. So Nick you talked about OpenStack and OpenShift. Of course there's open source project with with OpenStack. OpenShift the big piece of that is is Kubernetes. When it comes to edge are there other open source project, the parts of the foundations out there that we should highlight when looking at these edge loop? >> Oh, there is a tremendous amount of projects that are pertaining to the edge. Red Hat carries many of these projects in its portfolio. The middleware components for example Quercus or AMQ mechanism, Carlcare are very important components. We've got storage solutions that are super important also when you're talking about storing or handling data. You've got in our management portfolio two very key tool one called Ansible that allows to configure remotely confidence that is super handy when you need to reconfigure firewall in mass. You've got another tool that is the central piece of our strategy which is called ACM, Red Hat's I forgot the name of the product now. We are using the acronym all the time which is our central management mechanism just delivered to us through IBM. So this is a portfolio wide we are making and I forgot the important one which is Red Hat Enterprise Linux which is delivering very soon a new version that is going to enable easier management at yet. >> Yeah. Well of course we know that realers you know the core foundational piece fit with most of the solution in a portfolio. That it's really interesting how you laid that out though. As you know some people on the outside look and say, " Okay, Red Hat's got a really big portfolio. How does it all fit together?" You just discussed that all of these pieces become really important when they come together for the edge. So maybe you know, one of the things when we get together summit of course, we get to hear a lot from your customers. So any customers you can talk about, that might be a good proof point for these solutions that you're talking about today? >> So right now most of the proof points are in the telco industry because these are the first one that have made the investment in depth. And when we are talking about various and we are talking about very large investment that is reinforced in their strategy. We've got customers in telco all over the world that are starting to use our products to deploy their 5G networks and we've got lots of customer starting to work with us on creating their strategy for in other vertical particularly in the industrial and manufacturing sector which is our next endeavour after telco yet. >> Yeah well absolutely. Verizon a customer, I'm well familiar with when it comes to what they've been used with Red Hat. I'd interviewed them, it opens back few years back when they talked about that those nav-pipe solutions. You brought a manufacturing so that brings up one of the concerns when you talk about edge or specifically about IOT environment. When we did some original research looking at the industrial internet, the boundaries between the IT group and the OT which heavily lives in manufacturing wouldn't, they don't necessarily talk or work together. So how's Red Hat helping to make sure that customers you know, go through these transitions, pass through those silos and can take advantage of these sorts of new technologies? >> Well obviously you have to look at a problem in the entirety. You've got to look at the change management aspect and for this, you need to understand how people interact together if you intend on modifying the way they work together. You also need to ensure that the requirements of one are not impeding the other on demand, on environment of a manufacturer. Is really important especially when we are talking about dealing with IOT sensors which have very limited security capability. So you need to add in the appropriate security layers to make what is not secure, secure and if you don't do that you're going to introduce a friction. And you also need to ensure that you can delegate administration of the component to the right people. You cannot say, Oh from now on all of what you used to be controlling on a manufacturing floor is now controlled centrally and you have to go through this form in order to have anything modified. So having the flexibility in our tooling to enable respect of the existing organization and handle a change management the appropriate way. These are way to answer this... >> Right Nick, last thing for you. Obviously this is a maturing space, lots of change happening. So give us a little bit of a look forward as to what users should be expecting and you know what pieces will be the industry and Red Hat be working on that bring full value out of the edge and 5G solution? >> So as always, any such changes are driven by the applications. And what we are seeing is in terms of application, a very large predominance of requirements for AI, ML and data processing capability. So reinforcing all the components around this environment is one of our key addition and that we are making as we speak. You can see Chris keynote which is going to demonstrate how we are enabling a manufacturer to process the signal sent from multiple sensors through an AI and during early failure detection. You can also expect us to enable more and more complex use case in terms of footprint. Right now, we can do very small data center that are residing on three machine. Tomorrow we'll be able to handle remote worker nodes that are on a single machine. Further along we'll be able to deal with disconnected node. A single machine acting as a cluster. All these are elements that are going to allow us to go further and further in the complication of the use cases. It's not the same thing when you have to connect a manufacturer that is on solid grounds with fiber access or when you have to connect the knowledge for example or a vote and talk about that to. >> Well, Nick thank you so much for all the updates. I know there's some really good breakouts. I'm sure there's lots on the Red Hat website to find out more about edge in five B's. Nick Barcet thanks so much for joining us. >> Thank you very much for having me. >> All right. Back with lots more covered from Red Hat Summit 2020. I'm Stuart Miniman and thanks for watching theCUBE. (bright upbeat 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 this is the cubes coverage of Red Hat summit 2020 of course this year instead of all gathering together in San Francisco we're getting to talk to red hat executives their partners and their customers where they are around the globe I'm your host Stu minimun and happy to welcome to the program Nick Barr said who is the senior director of Technology Strategy at Red Hat he happens to be on a boat in the Bahamas so Nick thanks so much for joining us hey thank you for inviting me it's a great pleasure to be here and it's a great pleasure to work for a company that has always dealt with remote people so it's really easy for us to kind of thing yeah Nick you know it's interesting I've been saying probably for the last 10 years that the challenge of our time is really distributed systems you know from a software standpoint that's what we talked about and even more so today and number one of course the current situation with the global plan global pandemic but number two the topic we're gonna talk to you about is edge and 5g it's obviously gotten a lot of hype so before we get into that - training Nick you know you came into Red Hat through an acquisition so give us a little bit about your background and what you work on Baretta about five years ago company I was working for involves got acquired by read at and I've been very lucky in that acquisition where I found a perfect home to express my talent I've been free software advocate for the past 20-some years always been working in free software for the past 20 years and Red Hat is really wonderful for that yeah it's addressing me ok yeah I remember back the early days we used to talk about free software now we don't talk free open-source is what we talk about you know dream is a piece of what we're doing but yeah let's talk about you know Ino Vaughn's I absolutely remember the they were a partner of Red Hat talked to them a lot at some of the OpenStack goes so I I'm guessing when we're talking about edge these are kind of the pieces coming together of what red had done for years with OpenStack and with NFB so what what what's the solution set you're talking about Ferguson side how you're helping your customers with these blue well clearly the solution we are trying to put together as to combine what people already have with where they want to go our vision for the future is a vision where openshift is delivering a common service on any platform including hardware at the far edge on a model where both viens and containers can be hosted on the same machine however there is a long road to get there and until we can fulfill all the needs we are going to be using combination of openshift OpenStack and many other product that we have in our portfolio to fulfill the needs of our customer we've seen for example a Verizon starting with OpenStack quite a few years ago now going with us with openshift that they're going to place on up of OpenStack or directly on bare metal we've seen other big telcos use tag in very successful to deploy their party networks there is great capabilities in the existing portfolio we are just expanding that simplifying it because when we are talking about the edge we are talking about managing thousands if not millions of device and simplicity is key if you do not want to have your management box in Crete excellent so you talked a lot about the service providers obviously 5g as a big wave coming a lot of promise as what it will enable both for the service providers as well as the end-users help us understand where that is today and what we should expect to see in the coming years though so in respect of 5g there is two reason why 5g is important one it is B it is important in terms of ad strategy because any person deploying 5g will need to deploy computer resources much closer to the antenna if they want to be able to deliver the promise of 5g and the promise of very low latency the second reason it is important is because it allows to build a network of things which do not need to be interconnected other than through a 5g connection and this simplifies a lot some of the edge application that we are going to see where sensors needs to provide data in a way where you're not necessarily always connected to a physical network and maintaining a Wi-Fi connection is really complex and costly yeah Nick a lot of pieces that sometimes get confused or conflated I want you to help us connect the dots between what you're talking about for edge and what's happening the telcos and the the broader conversation about hybrid cloud or red hat calls at the O the open hybrid cloud because you know there were some articles that were like you know edge is going to kill the cloud I think we all know an IP nothing ever dies everything is all additive so how do these pieces all go together so for us at reddit it's very important to build edge as an extension of our open hybrid cloud strategy clearly what we are trying to build is an environment where developers can develop workloads once and then can the administrator that needs to deploy a workload or the business mode that means to deploy a workload can do it on any footprint and the edge is just one of these footprint as is the cloud as is a private environment so really having a single way to administer all these footprints having a single way to define the workloads running on it is really what we are achieving today and making better and better in the years to come um the the reality of [Music] who process the data as close as possible to where the data is being consumed or generated so you have new footprints - let's say summarize or simplify or analyze the data where it is being used and then you can limit the traffic to a more central site to only the essential of it is clear that we've the current growth of data there won't be enough capacity to have all the data going directly to the central part and this is what the edge is about making sure we have intermediary of points of processing yeah absolutely so Nikki you talked about OpenStack and OpenShift of course there's open source project with with OpenStack openshift the big piece of that is is kubernetes when it comes to edge are there other open source project the parts of the foundations out there that we should highlight when looking at these that's Luke oh there is a tremendous amount of projects that are pertaining to the edge read ad carry's many of these projects in its portfolio the middleware components for example Quercus or our amq mechanism caki are very important components we've got storage solutions that are super important also when you're talking about storing or handling data you've got in our management portfolio two very key tool one called ansible that allows to configure remotely confidence that that is super handy when you need to reconfigure firewall in Mass you've got another tool that he's a central piece of our strategy which is called a CM read at forgot the name of the product now we are using the acronym all the time which is our central management mechanism just delivered to us through IBM so this is a portfolio wide we are making and I forgot the important one which is real that Enterprise Linux which is delivering very soon a new version that is going to enable easier management at the edge yeah well of course we know that well is you know the core foundational piece with most of the solution in a portfolio that's really interesting how you laid that out though as you know some people on the outside look and say ok Red Hat's got a really big portfolio how does it all fit together you just discussed that all of these pieces become really important when when they come together for the edge so maybe uh you know one of the things when we get together summit of course we get to hear a lot from your your your customer so any customers you can talk about that might be a good proof point for these solutions that you're talking about today so right now most of the proof points are in the telco industry because these are the first one that have made the investment in it and when we are talking about their eyes and we are talking about a very large investment that is reinforced in their strategy we've got customers in telco all over the world that are starting to use our products to deploy their 5g networks and we've got lots of customer starting to work with us on creating their tragedy for in other vertical particularly in the industrial and manufacturing sector which is our necks and ever after telco yet yeah well absolutely Verizon a customer I'm well familiar with when it comes to what they've been used with Red Hat I'd interviewed them it opens back few years back when they talked about that those nmv type solutions you brought a manufacturing so that brings up one of the concerns when you talk about edge or specifically about IOT environment when we did some original research looking at the industrial Internet the boundaries between the IT group and the OT which heavily lives lives in manufacturing wouldn't they did they don't necessarily talk or work together so Houser had had to help to make sure that customers you know go through these transitions Plus through those silos and can take advantage of these sorts of new technologies well obviously you you have to look at a problem in entirety you've got to look at the change management aspect and for this you need to understand how people interact together if you intend on modifying the way they work together you also need to ensure that the requirements of one are not impeding the yeah other the man an environment of a manufacturer is really important especially when we are talking about dealing with IOT sensors which have very limited security capability so you need to add in the appropriate security layers to make what is not secure secure and if you don't do that you're going to introduce a friction and you also need to ensure that you can delegate administration of the component to the right people you cannot say Oh from now on all of what you used to be controlling on a manufacturing floor is now controlled centrally and you have to go through this form in order to have anything modified so having the flexibility in our tooling to enable respect of the existing organization and handle a change management the appropriate way is our way to answer this problem right Nick last thing for you obviously this is a maturing space lots of age happening so gives a little bit of a look forward as to what users should be affecting and you know what what what pieces will the industry and RedHat be working on that bring full value out of the edge and find a solution so as always any such changes are driven by the application and what we are seeing is in terms of application a very large predominance of requirements for AI ml and data processing capability so reinforcing all the components around this environment is one of our key addition and that we are making as we speak you can see Chris keynote which is going to demonstrate how we are enabling a manufacturer to process the signal sent from multiple sensors through an AI and during early failure detection you can also expect us to enable more and more complex use case in terms of footprint right now we can do very small data center that are residing on three machine tomorrow we'll be able to handle remote worker nodes that are on a single machine further along we'll be able to deal with disconnected node a single machine acting as a cluster all these are elements that are going to allow us to go further and further in the complication of the use cases it's not the same thing when you have to connect a manufacturer that is on solid grounds with fiber access or when you have to connect the Norway for example or a vote and talk about that too Nick thank you so much for all the updates no there's some really good breakouts I'm sure there's lots on the Red Hat website find out more about edge in five B's the Nick bark set thanks so much for joining us thank you very much for having me all right back with lots more covered from Red Hat summit 2020 I'm stoom in a man and thanks though we for watching the queue [Music]

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