>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud, Native Computing Foundation and Ecosystem Partners. Hello, everyone. And welcome back to the cubes Ongoing coverage of Cuba con North America. Joe Fernandez is here. He's with Stephanie, Cheras and Joe's, the V, P and GM for core cloud platforms. That red hat and Stephanie is this s VP and GM of the Red Hat Enterprise. Lennox bu. Two great friends of the Cube. Awesome seeing you guys. How you doing? >>It's great to be here, Dave. Yeah, thanks >>for the opportunity. >>Hey, so we all talked, you know, recently, uh, answerable fest Seems like a while ago, but But we talked about what's new? Red hat really coming at it from an automation perspective. But I wonder if we could take a view from open shift and what's new from the standpoint of you really focus on helping customers, you know, change their operations and operationalize. And Stephanie, Maybe you could start, and then, you know, Joe, you could bring in some added color. >>No, that's great. And I think you know one of the things we try and do it. Red hat clearly building off of open source. We have been focused on this open hybrid cloud strategy for, you know, really years. Now the beauty of it is that hybrid cloud and open hybrid cloud continues to evolve right with bringing in things like speed and stability and scale and now adding in other footprints, like manage services as well as edge and pulling that all together across the whole red hat portfolio from the platforms, right? Certainly with Lennox and roll into open shift in the platform with open shift and then adding automation, which certainly you need for scale. But it's ah, it's continues to evolve as the as the definition of open hybrid cloud evolves. >>Great. So thank you, Stephanie jokes. You guys got hard news here that you could maybe talk about 46? >>Yeah. Eso eso open shift is our enterprise kubernetes platform. With this announcement, we announced the release of open ship 4.6 Eso eso We're doing releases every quarter tracking the upstream kubernetes release cycle. So this brings communities 1.19, which is, um but itself brings a number of new innovations, some specific things to call out. We have this new automated installer for open shift on bare metal, and that's definitely a trend that we're seeing is more customers not only looking at containers but looking at running containers directly on bare metal environments. Open shift provides an abstraction, you know, which combines Cuban. And he's, uh, on top of Lennox with RL. I really across all environments, from bare metal to virtualization platforms to the various public clouds and out to the edge. But we're seeing a lot of interest in bare metal. This is basically increasing the really three automation to install seamlessly and manage upgrades in those environments. We're also seeing a number of other enhancements open shifts service mesh, which is our SDO based solution for managing, uh, the interactions between micro services being able to manage traffic against those services. Being able to do tracing. We have a new release of that on open shift Ford out six on then, um, some work specific to the public cloud that we started extending into the government clouds. So we already supported AWS and Azure. With this release, we added support for the A W s government cloud as well. Azaz Acela's Microsoft Azure government on dso again This is really important to like our public sector customers who are looking to move to the public cloud leveraging open shift as an abstraction but wanted thio support it on the specialized clouds that they need to use with azure gonna meet us Cup. >>So, joke, we stay there for a minute. So so bare metal talking performance there because, you know, you know what? You really want to run fast, right? So that's the attractiveness there. And then the point about SDO in the open, open shift service measure that makes things simpler. Maybe talk a little bit about sort of business impact and what customers should expect to get out of >>these two things. So So let me take them one at a time, right? So so running on bare metal certainly performances a consideration. You know, I think a lot of fixed today are still running containers, and Cuban is on top of some form of virtualization. Either a platform like this fear or open stack, or maybe VMS in the in one of the public clouds. But, you know containers don't depend on a virtualization layer. Containers only depend on Lennox and Lennox runs great on bare metal. So as we see customers moving more towards performance and Leighton see sensitive workloads, they want to get that Barry mental performance on running open shift on bare metal and their containerized applications on that, uh, platform certainly gives them that advantage. Others just want to reduce the cost right. They want to reduce their VM sprawl, the infrastructure and operational cost of managing avert layer beneath their careers clusters. And that's another benefit. So we see a lot of uptake in open shift on bare metal on the service match side. This is really about You know how we see applications evolving, right? Uh, customers are moving more towards these distributed architectures, taking, you know, formally monolithic or enter applications and splitting them out into ah, lots of different services. The challenge there becomes. Then how do you manage all those connections? Right, Because something that was a single stack is now comprised of tens or hundreds of services on DSO. You wanna be able to manage traffic to those services, so if the service goes down, you can redirect that those requests thio to an alternative or fail over service. Also tracing. If you're looking at performance issues, you need to know where in your architecture, er you're having those degradations and so forth. And, you know, those are some of the challenges that people can sort of overcome or get help with by using service mash, which is powered by SDO. >>And then I'm sorry, Stephanie ever get to in a minute. But which is 11 follow up on that Joe is so the rial differentiation between what you bring in what I can just if I'm in a mono cloud, for instance is you're gonna you're gonna bring this across clouds. I'm gonna You're gonna bring it on, Prem And we're gonna talk about the edge in in a minute. Is that right? From a differentiation standpoint, >>Yeah, that That's one of the key >>differentiations. You know, Read has been talking about the hybrid cloud for a long time. We've we've been articulating are open hybrid cloud strategy, Andi, >>even if that's >>not a strategy that you may be thinking about, it is ultimately where folks end up right, because all of our enterprise customers still have applications running in the data center. But they're also all starting to move applications out to the public cloud. As they expand their usage of public cloud, you start seeing them adopted multi cloud strategies because they don't want to put all their eggs in one basket. And then for certain classes of applications, they need to move those applications closer to the data. And and so you start to see EJ becoming part of that hybrid cloud picture on DSO. What we do is basically provide a consistency across all those environments, right? We want run great on Amazon, but also great on Azure on Google on bare metal in the data center during medal out at the edge on top of your favorite virtualization platform. And yeah, that that consistency to take a set of applications and run them the same way across all those environments. That is just one of the key benefits of going with red hat as your provider for open hybrid cloud solutions. >>All right, thank you. Stephanie would come back to you here, so I mean, we talk about rail a lot because your business unit that you manage, but we're starting to see red hats edge strategy unfolded. Kind of real is really the linchpin I wanna You could talk about how you're thinking about the edge and and particularly interested in how you're handling scale and why you feel like you're in a good position toe handle that massive scale on the requirements of the edge and versus hey, we need a new OS for the edge. >>Yeah, I think. And Joe did a great job of said and up it does come back to our view around this open hybrid cloud story has always been about consistency. It's about that language that you speak, no matter where you want to run your applications in between rela on on my side and Joe with open shift and and of course, you know we run the same Lennox underneath. So real core os is part of open shift that consistently see leads to a lot of flexibility, whether it's through a broad ecosystem or it's across footprints. And so now is we have been talking with customers about how they want to move their applications closer to data, you know, further out and away from their data center. So some of it is about distributing your data center, getting that compute closer to the data or closer to your customers. It drives, drives some different requirements right around. How you do updates, how you do over the air updates. And so we have been working in typical red hat fashion, right? We've been looking at what's being done in the upstream. So in the fedora upstream community, there is a lot of working that has been done in what's called the I. O. T Special Interest group. They have been really investigating what the requirements are for this use case and edge. So now we're really pleased in, um, in our most recent release of really aid relate 00.3. We have put in some key capabilities that we're seeing being driven by these edge use cases. So things like How do you do quick image generation? And that's important because, as you distribute, want that consistency created tailored image, be able to deploy that in a consistent way, allow that to address scale, meet security requirements that you may have also right updates become very important when you start to spread this out. So we put in things in order to allow remote device mirroring so that you can put code into production and then you can schedule it on those remote devices toe happen with the minimal disruption. Things like things like we all know now, right with all this virtual stuff, we often run into things like not ideal bandwidth and sometimes intermittent connectivity with all of those devices out there. So we put in, um, capabilities around, being able to use something called rpm Austria, Um, in order to be able to deliver efficient over the air updates. And then, of course, you got to do intelligent rollbacks for per chance that something goes wrong. How do you come back to a previous state? So it's all about being able to deploy at scale in a distributed way, be ready for that use case and have some predictability and consistency. And again, that's what we build our platforms for. It's all about predictability and consistency, and that gives you flexibility to add your innovation on top. >>I'm glad you mentioned intelligent rollbacks I learned a long time ago. You always ask the question. What happens when something goes wrong? You learn a lot from the answer to that, but You know, we talk a lot about cloud native. Sounds like you're adapting well to become edge native. >>Yeah. I mean, I mean, we're finding whether it's inthe e verticals, right in the very specific use cases or whether it's in sort of an enterprise edge use case. Having consistency brings a ton of flexibility. It was funny, one of our talking with a customer not too long ago. And they said, you know, agility is the new version of efficiency. So it's that having that sort of language be spoken everywhere from your core data center all the way out to the edge that allows you a lot of flexibility going forward. >>So what if you could talk? I mentioned just mentioned Cloud Native. I mean, I think people sometimes just underestimate the effort. It takes tow, make all this stuff run in all the different clouds the engineering efforts required. And I'm wondering what kind of engineering you do with if any with the cloud providers and and, of course, the balance of the ecosystem. But But maybe you could describe that a little bit. >>Yeah, so? So Red Hat works closely with all the major cloud providers you know, whether that's Amazon, Azure, Google or IBM Cloud. Obviously, Andi, we're you know, we're very keen on sort of making sure that we're providing the best environment to run enterprise applications across all those environments, whether you're running it directly just with Lennox on Ralph or whether you're running it in a containerized environment with Open Chef, which which includes route eso eso, our partnership includes work we do upstream, for example. You know, Red Hat help. Google launched the Cuban community, and I've been, you know, with Google. You know, we've been the top two contributors driving that product that project since inception, um, but then also extends into sort of our hosted services. So we run a jointly developed and jointly managed service called the Azure Red Hat Open Shift Service. Together with Microsoft were our joint customers can get access to open shift in an azure environment as a native azure service, meaning it's, you know, it's fully integrated, just like any other. As your service you can tied into as you're building and so forth. It's sold by by Azure Microsoft's sales reps. Um, but you know, we get the benefit of working together with our Microsoft counterparts and developing that service in managing that service and then in supporting our joint customers. We over the summer announced sort of a similar partnership with Amazon and we'll be launching are already doing pilots on the Amazon Red Hat Open ship service, which is which is, you know, the same concept now applied to the AWS cloud. So that will be coming out g a later this year, right? But again, whether it's working upstream or whether it's, you know, partnering on managed services. I know Stephanie team also do a lot of work with Microsoft, for example, on sequel server on Lenox dot net on Lenox. Whoever thought be running that applications on Linux. But that's, you know, a couple of years old now, a few years old, So eso again. It's been a great partnership, not just with Microsoft, but with all the cloud providers. >>So I think you just shared a little little He showed a little leg there, Joe, what's what's coming g A. Later this year. I want to circle back to >>that. Yeah, eso we way announced a preview earlier this year of of the Amazon Red Hat Open ships service. It's not generally available yet. We're you know, we're taking customers. We want toe, sort of be early access, get access to pilots and then that'll be generally available later this year. Although Red Hat does manage our own service Open ship dedicated that's available on AWS today. But that's a service that's, you know, solely, uh, operated by Red Hat. This new service will be jointly operated by Red Hat and Amazon together Idea. That would be sort of a service that we are delivering together as partners >>as a managed service and and okay, so that's in beta now. I presume if it's gonna be g a little, it's >>like, Yeah, that's yeah, >>that's probably running on bare metal. I would imagine that >>one is running >>on E. C. Two. That's running an A W C C T V exactly, and >>run again. You know, all of our all of >>our I mean, we you know, that open shift does offer bare metal cloud, and we do you know, we do have customers who can take the open shift software and deploy it there right now are managed. Offering is running on top of the C two and on top of Azure VM. But again, this is this is appealing to customers who, you know, like what we bring in terms of an enterprise kubernetes platform, but don't wanna, you know, operated themselves, right? So it's a fully managed service. You just come and build and deploy your APS, and then we manage all of the infrastructure and all the underlying platform for you >>that's going to explode. My prediction. Um, let's take an example of heart example of security. And I'm interested in how you guys ensure a consistent, you know, security experience across all these locations on Prem Cloud. Multiple clouds, the edge. Maybe you could talk about that. And Stephanie, I'm sure you have a perspective on this is Well, from the standpoint of of Ralph. So who wants to start? >>Yeah, Maybe I could start from the bottom and then I'll pass it over to Joe to talk a bit. I think one of these aspects about security it's clearly top of mind of all customers. Um, it does start with the very bottom and base selection in your OS. We continue to drive SC Lennox capabilities into rural to provide that foundational layer. And then as we run real core OS and open shift, we bring over that s C Lennox capability as well. Um, but, you know, there's a whole lot of ways to tackle this we've done. We've done a lot around our policies around, um see ve updates, etcetera around rail to make sure that we are continuing to provide on DCA mitt too. Mitigating all critical and importance, providing better transparency toe how we assess those CVS. So security is certainly top of mind for us. And then as we move forward, right there's also and joke and talk about the security work we do is also capabilities to do that in container ization. But you know, we we work. We work all the way from the base to doing things like these images in these easy to build images, which are tailored so you can make them smaller, less surface area for security. Security is one of those things. That's a lifestyle, right? You gotta look at it from all the way the base in the operating system, with things like sc Lennox toe how you build your images, which now we've added new capabilities. There And then, of course, in containers. There's, um there's a whole focus in the open shift area around container container security, >>Joe. Anything you want to add to that? >>Yeah, sure. I >>mean, I think, you know, obviously, Lennox is the foundation for, you know, for all public clouds. It's it's driving enterprise applications in the data center, part of keeping those applications. Security is keeping them up to date And, you know, through, you know, through real, we provide, you know, securing up to date foundation as a Stephanie mentioned as you move into open shift, you're also been able to take advantage of, uh, Thio to take advantage of essentially mutability. Right? So now the application that you're deploying isn't immutable unit that you build once as a container image, and then you deploy that out all your various environments. When you have to do an update, you don't go and update all those environments. You build a new image that includes those updates, and then you deploy those images out rolling fashion and, as you mentioned that you could go back if there's issues. So the idea, the notion of immutable application deployments has a lot to do with security, and it's enabled by containers. And then, obviously you have cured Panetti's and, you know, and all the rest of our capabilities as part of open Shift managing that for you. We've extended that concept to the entire platform. So Stephanie mentioned, real core West Open shift has always run on real. What we have done in open shift for is we've taken an immutable version of Ralph. So it's the same red hat enterprise Lennox that we've had for years. But now, in this latest version relate, we have a new way to package and deploy it as a relic or OS image, and then that becomes part of the platform. So when customers want toe in addition to keeping their applications up to date, they need to keep their platform up to dates. Need to keep, you know, up with the latest kubernetes patches up with the latest Lennox packages. What we're doing is delivering that as one platform, so when you get updates for open shift, they could include updates for kubernetes. They could include updates for Lennox itself as well as all the integrated services and again, all of this is just you know this is how you keep your applications secure. Is making sure your you know, taking care of that hygiene of, you know, managing your vulnerabilities, keeping everything patched in up to date and ultimately ensuring security for your application and users. >>I know I'm going a little bit over, but I have I have one question that I wanna ask you guys and a broad question about maybe a trends you see in the business. I mean, you look at what we talk a lot about cloud native, and you look at kubernetes and the interest in kubernetes off the charts. It's an area that has a lot of spending momentum. People are putting resource is behind it. But you know, really, to build these sort of modern applications, it's considered state of the art on. Do you see a lot of people trying to really bring that modern approach toe any cloud we've been talking about? EJ. You wanna bring it also on Prem And people generally associate this notion of cloud native with this kind of elite developers, right? But you're bringing it to the masses and there's 20 million plus software developers out there, and most you know, with all due respect that you know they may not be the the the elites of the elite. So how are you seeing this evolve in terms of re Skilling people to be able, handle and take advantage of all this? You know, cool new stuff that's coming out. >>Yeah, I can start, you know, open shift. Our focus from the beginning has been bringing kubernetes to the enterprise. So we think of open shift as the dominant enterprise kubernetes platform enterprises come in all shapes and sizes and and skill sets. As you mentioned, they have unique requirements in terms of how they need toe run stuff in their data center and then also bring that to production, whether it's in the data center across the public clouds eso So part of it is, you know, making sure that the technology meets the requirements and then part of it is working. The people process and and culture thio make them help them understand what it means to sort of take advantage of container ization and cloud native platforms and communities. Of course, this is nothing new to red hat, right? This is what we did 20 years ago when we first brought Lennox to the Enterprise with well, right on. In essence, Carozza is basically distributed. Lennox right Kubernetes builds on Lennox and brings it out to your cluster to your distributed systems on across the hybrid cloud. So So nothing new for Red Hat. But a lot of the same challenges apply to this new cloud native world. >>Awesome. Stephanie, we'll give you the last word, >>all right? And I think just a touch on what Joe talked about it. And Joe and I worked really closely on this, right? The ability to run containers right is someone launches down this because it is magical. What could be done with deploying applications? Using a container technology, we built the capabilities and the tools directly into rural in order to be able to build and deploy, leveraging things like pod man directly into rural. And that's exactly so, folks. Everyone who has a real subscription today can start on their container journey, start to build and deploy that, and then we work to help those skills then be transferrable as you movinto open shift in kubernetes and orchestration. So, you know, we work very closely to make sure that the skills building can be done directly on rail and then transfer into open shift. Because, as Joe said, at the end of the day, it's just a different way to deploy. Lennox, >>You guys are doing some good work. Keep it up. And thanks so much for coming back in. The Cube is great to talk to you today. >>Good to see you, Dave. >>Yes, Thank you. >>All right. Thank you for watching everybody. The cubes coverage of Cuba con en a continues right after this.

>> Everyone. Welcome to a special cube conversation. We're here in Palo Alto, California Cube Studios. I'm John, four year host of the Q. We hear Atomic Wild, the CEO of Snapper out. Tom. Great to see you. You doing? I'm great. Thanks. You guys. You're launching Snapper. Snapper out. What is the company? What do you guys launching? Tell us. >> Well, quite simply stated were delivering a new class of network operating system for the cloud native era. Andrea Lee. What that does, is it. It delivers on the promise of time to service for applications. Always on security assurance and compliance. Andi greater operational efficiency, which is really one of the things that's been plaguing organizations tonight. >> How long is the company been around? This is the first public launch. A solution? Talk about the history real quick. >> So the company was founded in two thousand fifteen by some former operators from Apple. They built and ran Apple. Sort of biggest public facing data centers from the networking perspective on DH. You know, we've been working diligently on this. This is a new class of operating system that was really inspired by, you know, that their time building out those data centers on def. You, you kind of look back. NETWORKINGS not really had any major disruptive innovation in the last twenty five, thirty years. Ah, but back into the two thousand six, with the advent of a Ws and the and the new sort of big, hyper scaler tze, those guys started to realize that the network was something that was kind of getting in the way of their operational efficiency, of being able to automate and drive the network at scale on DSO. Our founders, you know, went through that whole sort of discovery process and things when when they were Apple on DH, you know, and the hyper scales drove the advent of this kind of white box disaggregated networking, separating the software operating system from the hardware and the reason behind that was really around game great gaining greater control because it's a legacy. Networking vendors were not delivering what was needed, and they needed to get more control on DSO. Are found us. You really saw the opportunity to say, Look, we think that there's a way of solving what an operator really needs and what an organization needs and one of the big challenges. There is howto networking operations. Teams collaborate with dev up stings because the devil teams are responsible for, you know, time to service for the application. And that's, you know, that's really the value of the organization. And so, you know, they set out to solve that problem to say, Well, hell, can we build a network operating system on what they realised was that you know what Deb Ops had done is embrace. It's a cloud. Native principles container ization, virtual ization, my crack services on DH. So what we've done is we've built from the ground up a newly architected network operating system that is a fully containerized micro services architecture that embeds coup Panetti's on DH allows the networking for this first time to be brought natively into the de bop store chain. Sonett ops teams can still sort of control and deploy the network and define policy and things. But now they don't have to worry about that is, you know, sort of annoying day today, tasks where, you know the Devil apps engineer is tryingto get an application on the network and, you know, they have to just do sort of some, you know, pretty trivial movies that changes things. And so, you know, in in doing that, what we also figured out was we could solve, you know, problems not just around the operational efficiencies and the time to service, but also a lot of security >> issues as well. So a lot of development going public with the product you mentioned. Cooper Netease, top of cloud. >> What are the >> big shifts in the industry that you guys air riding on because you have tail winds get cloud? Yeah, What is the way that you're on? Can you take a minute to explain some of the big shifts in the industry that's going, guys? >> Yeah, well, I I think there's several things. I think one of the biggest is that, you know, every single organization out there is looking nervously over its shoulder because we live in an age of very, very rapid disruption. It's kind of you know what call the Amazon affect. You know, those big, established companies who've been around for many, many years, who are being disrupted by, you know, Jason, you know, cos we're in adjacent spaces or new start ups coming in so everybody near realizes they need to use technology to their advantage, and they have to disrupt themselves Before, you know, they're they're disrupted. So? So that's one of the big drivers and And so time to service speed, efficiency are all sort of paramount. When you were in, you know, any C suite, you know, discussion, those air. Those are things that come up a ll the time from a technology perspective. We're seeing things, things changing significantly and how we use technology. And, you know, So everything is mobile. Ah, you know, we have the advent of I O t coming in, and so, you know, lots of services and moving to the edge. And so the data centers that were traditionally completely centralized and they'll sort of starting to distribute a little bit of well, eh? So you have this, you know, idea of sort of age data centers in H compute. So there's there's a lot of things, you know, changing and happening. And there's a lot of opportunity for us to deliver, you know, some strong value in this. >> So they obviously the cloud native trend you mentioned is big. That's driving the application market. De bobs you mentioned earlier huge we've seen years now in years of evidence of growth yet on dev ups. Okay, so now it's coming down into the network how? How our company's solving challenges for application developers that are in a devil's world because that seems to be the growth. And the sooner the pressure's coming from is that more requirements coming from the applications to the network. How are companies solving this problem? >> So, you know, So I think from the computer and storage side, things have moved along, you know, pretty, pretty, pretty swiftly eso, you know, as an application engineer. What? What you want is you want the infrastructure to service. You just You just want it to do what the application needs. Unfortunately, you know, traditionally, infrastructures has has been the other way around. You know, you deploy the infrastructure and you say, Okay, well, this is what the application could do within the constraints of the infrastructure and networking has, you know, just continued that idea. And so what you want to do is you want to take this idea of you we've talked before about infrastructure as code, you know. How do you make it? So is when an application engineer rights and application, he can actually regard the infrastructure as almost like a code library. And that's something that a lot of legacy vendors have talked about marketed to for some time. But the reality is-- >> It makes a lot of sense. >> Yeah, it does. It makes a ton of sense. But the reality is that all they could do was offer up some, you know, proprietary APIs and and programmatic interfaces. And the big challenge was the actual architecture of a network operating system was not designed in a way to actually enable that that infrastructure to react in the proper way by developing this containerized microservices architecture on by embedding communities and putting native DevOps tool chains you know inside the operating system. We actually can deliver on the promise of infrastructure as code. >> and this is what everyone wants. I gotta ask you, if everyone wants this and we hearing all around the Cuban all the events we go to clearly a requirement becoming table stakes. But what? What's been preventing people from doing this? >> Well, it's it's the architecture. I mean, if you look at, I call them Legacy Network architectures, but network architecture. Yeah, network operating system itself. The actual you know, the operating system that exists on the physical switch. That is where the problem starts, because that is designed as one big >> blob off >> coat. So all of the features Aaron there, they're all in the same place. They all sort of interact with each other, and it gives you reliability problems that give you innovation problems, because every time you change something, it has a knock on effect. If there's a bug and you have to fix that bug, you have to replace the entire blob. If you replace the entire blob, you have to down the switch or, you know, do some kind of complex patching. If there's a security vulnerability, you have to either differ like actually fixing their on DH, become non complaint or you have to down the switch. And you know we live in an age, As I said, where everything is on all the time, everything is mobile, you know, everybody wants their services right here right now. And the very you know, the very existence of a business depends on being able to deliver those applications all the time. So you can't bring network's down. So when when we've taken this micro services approach and we've containerized the actual infrastructure, you know, on the protocols and everything else, everything existed in its own container. Now, if there's a security vulnerability, we can replace just that container. If you're not using certain services on the operating system, you could kill those containers. And in the process, you reduce the threat surface off the the operating system in the switch. Where is in a legacy world with this monolithic blob, you can just you can turn off the features, but the code still there, the threat surfaces huge, and you're still vulnerable. So what's the >> solution to this and snap route? Fix this. What's the operational benefits? How do you guys play into fixing? The problems have been holding everyone back. >> Well, I think you know collaboration, I think is, you know, is one of the big benefits. You know, Quite frankly, I think there's, you know, there's there's been sort of tension in organizations. I think unfairly network operating operations teams have been, you know, treated as you know, holding things back or non responsive, whatever, anything that's completely unfair because actually, the problem is with the the vendor community. We haven't been delivering the tools that enable them to, you know, deliver the services they need. And so with you know, with our approach with this cloud native approach, we're actually able, sort of, you know, bring the net net tops world. You know, closer to Deb. Ops allow this Khun collaboration to happen on give you you know that the benefit ofthe I Abel sort of coordinated approach to delivering the application and the application is the value that the business delivers on. Biff, you know, if your application stops working, I mean, you know this in your personal life, right? You know, we use our phones and our devices. You try, use an application and it and it's not working. You're going to go and find a competitive. You're just going to go and say, Oh, well, you know, you saw download something else from the APP store on DH. So, you know, availability is a huge thing for businesses today on the network has been one of the most vulnerable pieces in terms of availability. Not because not necessarily because people are attacking it, but because it's so complex. And brittle that any time you change anything, things fall to pieces. And that's why people don't want to touch the network. And that is why we had the rise of the whole Sgn movement. The ESPN movement was on approach That said, we need to make the network more dynamic. And so, rather than addressing the actual operating system, put overlays over the top, create overlays and allow Deb ops teams to do what they need to do to deploy applications over the top of your fairly done plumbing. What we're saying is, look, we're going to simplify and claps. Thatyou don't need translation layers, and a PR is You don't need overlays. You don't need all of that stuff. We're now re architect in the operating system itself. So you, Khun Natively, address that and you know and directly, you know, control the policy that you need to deploy an application. >> Don, This is about modern infrastructure. It's what cloud is modernizing all parts of the value changing how people by consume, deploy, provide valued application known as you guys are part of that. How do people engage with snap route? So I say, Okay, this is the direction. I'm going. I'm going. I'm in cloud native and doing Cooper Netease. I got containing amusing microspheres betting my company's future on this direction. And a lot of people are. Yep. How doe I engage with you guys. And how do you fit into the equation? >> Right? So s so first of all, you know, initial engagement, you know, website linked in Facebook. You know, we're on all of those things. Weigh, You know, we're in customer trials right now. Invaders right now, you know, where was the launching the product? So you know where we'll be shipping off of your first commercial deployments. But as faras, you know how and where are the good? You know, the good opportunities to to deploy us on. Obviously, there are, you know, sort of new. Come, we're high growth companies who, you know, we're talking to who, you know, kind of wanna build off us as a base to start with. But if you already have ah, large investment in disorder deployed legacy equipment we can fit in quite nicely on. And we can still add a ton of value because one of the big problem areas, he's actually the top of rack, Switch the double racks, which is actually where Dev ops and Net ops come together. It's the first place where compute on the application touched the network on DH. This is where usually Annette, ops engineer, spends a lot of time doing, you know, fairly said of your trivial tasks to help applications, you get onto the network and you know, it's a big >> waste of conversion. You see, you think you're playing at the top Iraq switch, >> that is, that is a good place for for somebody to start to get a tremendous amount of value out of our product. You don't need to replace the entire network. You don't have to have us into end. You don't have to have us in the corps if you deploy us at the top of Rex, which so, you know, take a white box device. You know, deploy our operating system on top is very, very simple to do. The network engineer Khun very simply get that device up and running a little token. Figure itself. And then the Dev ops engineers can, you know, come in and say How would employ an application And I didn't need the network to do the following things, and the device will configure itself in that way. >> This is really two worlds coming together. Network operations and developer operations coming together. Yeah. How do you see that? Coming together and meshing together? Obviously, the top of Rex, which you mentioned? A key area where you get your kogel work. But as those cultural communities come together, you know, network operations and depth there, they're seeing benefits with each other. How are those worlds colliding? What's the benefit? What's it going to look like? And what's the opportunity? >> Yeah, well, I you know, I mean, first of all, I think that there's this misconception that these two over there, you know, these two types of organizations don't want to collaborate anything. That's a complete miss misconception. I mean, everybody wants to do the right thing they wanted, You know, their business is to grow ondas. I said earlier. I mean, I think the problem is that, you know, the vendor community is not delivered, as you know, a set of tools and products and capabilities that enable this collaboration. Andi, you know, that's what we're bringing to the table. But I do think you know that there's this This sort of, you know, this cross pollination, this this this ability to you don't have to learn each other's area of expertise. You don't suddenly have to become a networking expert. You know, the dead box engineer doesn't become a networking expert. Vice versa. But there is this, you know, there's there's this point of view, no collaboration and harmony that we can create where there was a lot of tension on DH, you know, and, you know, in fact, there was, you know, a lot of problems that way. Consider harmonize that and allow these organizations to just, you know, move forward with what really counts, which is growing the business. >> Tom, thanks for coming in. I appreciate your time. Original launch. Final question for you. Taking me displaying your background. Your previous roles in networking. We first met when you were at a PHP that he's being. Then why you attracted to snap Prada's as an opportunity on what's. >> Yeah, so, you know, I'm I've been in networking for over thirty years on and help me on DH. You know, network in security. Various roles, mostly in sort of product Rolls product management. You know, pride to snap her out. I was the general manager of the data center networking group HP on DH. You know, I got to do some, you know, fabulous things at HP. We have, you know, quite a ruber. And in other things there which have been hugely successful. So it was a lot of fun. But I came to the point with my career there, where I realized, you know, I I done, you know, many of the things that I wanted to do, and also, you know, most of the opportunities that were there in transforming and transitioning that company. And I wanted to get back to my start up roots on DH. You know, the, you know, long conversation. >> No data centers, these apple guys. >> Yeah, Andi, you know, And so I started talking Teo to snap Brown on, you know, they were asking my advice and things. And the one of the things that attracted me, as you say was it's a company built by operators for operators. You know, it's I, You know, I've never had the opportunity to be in a company founded by operators who just intrinsically know what the customer problem is on B because they've lived it. And And I think you really do have to live it to truly understand on DH. So, you know, that was a huge plus for me. I was really attracted, Teo, that Adam and Glenn, our founders, you know, really interesting great guys. But also there's this inflection point. There's this inflection point in the marking and market and everything to do with, you know, start ups and successful startups is not just having the right innovative technology, which I truly believe we do but having the right overthere innovative technology at the right time. And the timing here is perfect. I mean, child native, you know, Cuba netease, the movement behind Cuba. Netease is just a force unto itself. You know, Dev Ops is, you know, is really moving forward. There's a huge sort of groundswell within the networking team community to, you know, to modernize and to, you know, toe toe. Contribute more to the success of business s So we have a massive >> opportunity. And And the trend of programmable networks Infrastructure is code is happening now. He wanted rubber is hitting the road now? >> Yeah, absolutely. You know it's, you know, we'll go through the usual adoption curves of, you know, early adopters and mass market etcetera. And so, you know, there's a There's a journey ahead of us, but but yeah. No, I mean, you know, people are doing this right now. >> Well, congratulations on your launch net, right? We'll be watching you. Really innovative. Moving right to the core of the devices with an operating system. No abstraction. Layers with Cooper Netease. Interesting architecture. Looking forward to following it. Dominic Wild CEO Snapper out here inside the Cube studios and fellow Also, I'm John Ferrier. Thanks for watching.