>>Everyone wants a cloud operating model. Since the introduction of the modern cloud. Last decade, the entire technology landscape has changed. We've learned a lot from the hyperscalers, especially from AWS. Now, one thing is certain in the technology business. It's so competitive. Then if a faster, better, cheaper idea comes along, the industry will move quickly to adopt it. They'll add their unique value and then they'll bring solutions to the market. And that's precisely what's happening throughout the technology industry because of cloud. And one of the best examples is Amazon's nitro. That's AWS has custom built hypervisor that delivers on the promise of more efficiently using resources and expanding things like processor, optionality for customers. It's a secret weapon for Amazon. As, as we, as we wrote last year, every infrastructure company needs something like nitro to compete. Why do we say this? Well, Wiki Bon our research arm estimates that nearly 30% of CPU cores in the data center are wasted. >>They're doing work that they weren't designed to do well, specifically offloading networking, storage, and security tasks. So if you can eliminate that waste, you can recapture dollars that drop right to the bottom line. That's why every company needs a nitro like solution. As a result of these developments, customers are rethinking networks and how they utilize precious compute resources. They can't, or won't put everything into the public cloud for many reasons. That's one of the tailwinds for tier two cloud service providers and why they're growing so fast. They give options to customers that don't want to keep investing in building out their own data centers, and they don't want to migrate all their workloads to the public cloud. So these providers and on-prem customers, they want to be more like hyperscalers, right? They want to be more agile and they do that. They're distributing, networking and security functions and pushing them closer to the applications. >>Now, at the same time, they're unifying their view of the network. So it can be less fragmented, manage more efficiently with more automation and better visibility. How are they doing this? Well, that's what we're going to talk about today. Welcome to changing the game for cloud networking made possible by pluribus networks. My name is Dave Vellante and today on this special cube presentation, John furrier, and I are going to explore these issues in detail. We'll dig into new solutions being created by pluribus and Nvidia to specifically address offloading, wasted resources, accelerating performance, isolating data, and making networks more secure all while unifying the network experience. We're going to start on the west coast and our Palo Alto studios, where John will talk to Mike of pluribus and AMI, but Donnie of Nvidia, then we'll bring on Alessandra Bobby airy of pluribus and Pete Lummus from Nvidia to take a deeper dive into the technology. And then we're gonna bring it back here to our east coast studio and get the independent analyst perspective from Bob Liberte of the enterprise strategy group. We hope you enjoy the program. Okay, let's do this over to John >>Okay. Let's kick things off. We're here at my cafe. One of the TMO and pluribus networks and NAMI by Dani VP of networking, marketing, and developer ecosystem at Nvidia. Great to have you welcome folks. >>Thank you. Thanks. >>So let's get into the, the problem situation with cloud unified network. What problems are out there? What challenges do cloud operators have Mike let's get into it. >>Yeah, it really, you know, the challenges we're looking at are for non hyperscalers that's enterprises, governments, um, tier two service providers, cloud service providers, and the first mandate for them is to become as agile as a hyperscaler. So they need to be able to deploy services and security policies. And second, they need to be able to abstract the complexity of the network and define things in software while it's accelerated in hardware. Um, really ultimately they need a single operating model everywhere. And then the second thing is they need to distribute networking and security services out to the edge of the host. Um, we're seeing a growth in cyber attacks. Um, it's, it's not slowing down. It's only getting worse and, you know, solving for this security problem across clouds is absolutely critical. And the way to do it is to move security out to the host. >>Okay. With that goal in mind, what's the pluribus vision. How does this tie together? >>Yeah. So, um, basically what we see is, uh, that this demands a new architecture and that new architecture has four tenants. The first tenant is unified and simplified cloud networks. If you look at cloud networks today, there's, there's sort of like discreet bespoke cloud networks, you know, per hypervisor, per private cloud edge cloud public cloud. Each of the public clouds have different networks that needs to be unified. You know, if we want these folks to be able to be agile, they need to be able to issue a single command or instantiate a security policy across all those locations with one command and not have to go to each one. The second is like I mentioned, distributed security, um, distributed security without compromise, extended out to the host is absolutely critical. So micro-segmentation and distributed firewalls, but it doesn't stop there. They also need pervasive visibility. >>You know, it's, it's, it's sort of like with security, you really can't see you can't protect what you can't see. So you need visibility everywhere. The problem is visibility to date has been very expensive. Folks have had to basically build a separate overlay network of taps, packet brokers, tap aggregation infrastructure that really needs to be built into this unified network I'm talking about. And the last thing is automation. All of this needs to be SDN enabled. So this is related to my comment about abstraction abstract, the complexity of all of these discreet networks, physic whatever's down there in the physical layer. Yeah. I don't want to see it. I want to abstract it. I wanted to find things in software, but I do want to leverage the power of hardware to accelerate that. So that's the fourth tenant is SDN automation. >>Mike, we've been talking on the cube a lot about this architectural shift and customers are looking at this. This is a big part of everyone who's looking at cloud operations next gen, how do we get there? How do customers get this vision realized? >>That's a great question. And I appreciate the tee up. I mean, we're, we're here today for that reason. We're introducing two things today. Um, the first is a unified cloud networking vision, and that is a vision of where pluribus is headed with our partners like Nvidia longterm. Um, and that is about, uh, deploying a common operating model, SDN enabled SDN, automated hardware, accelerated across all clouds. Um, and whether that's underlying overlay switch or server, um, hype, any hypervisor infrastructure containers, any workload doesn't matter. So that's ultimately where we want to get. And that's what we talked about earlier. Um, the first step in that vision is what we call the unified cloud fabric. And this is the next generation of our adaptive cloud fabric. Um, and what's nice about this is we're not starting from scratch. We have a, a, an award-winning adaptive cloud fabric product that is deployed globally. Um, and in particular, uh, we're very proud of the fact that it's deployed in over a hundred tier one mobile operators as the network fabric for their 4g and 5g virtualized cores. We know how to build carrier grade, uh, networking infrastructure, what we're doing now, um, to realize this next generation unified cloud fabric is we're extending from the switch to this Nvidia Bluefield to DPU. We know there's a, >>Hold that up real quick. That's a good, that's a good prop. That's the blue field and video. >>It's the Nvidia Bluefield two DPU data processing unit. And, um, uh, you know, what we're doing, uh, fundamentally is extending our SDN automated fabric, the unified cloud fabric out to the host, but it does take processing power. So we knew that we didn't want to do, we didn't want to implement that running on the CPU, which is what some other companies do because it consumes revenue generating CPU's from the application. So a DPU is a perfect way to implement this. And we knew that Nvidia was the leader with this blue field too. And so that is the first that's, that's the first step in the getting into realizing this vision. >>I mean, Nvidia has always been powering some great workloads of GPU. Now you've got DPU networking and then video is here. What is the relationship with clothes? How did that come together? Tell us the story. >>Yeah. So, you know, we've been working with pluribus for quite some time. I think the last several months was really when it came to fruition and, uh, what pluribus is trying to build and what Nvidia has. So we have, you know, this concept of a Bluefield data processing unit, which if you think about it, conceptually does really three things, offload, accelerate an isolate. So offload your workloads from your CPU to your data processing unit infrastructure workloads that is, uh, accelerate. So there's a bunch of acceleration engines. So you can run infrastructure workloads much faster than you would otherwise, and then isolation. So you have this nice security isolation between the data processing unit and your other CPU environment. And so you can run completely isolated workloads directly on the data processing unit. So we introduced this, you know, a couple of years ago, and with pluribus, you know, we've been talking to the pluribus team for quite some months now. >>And I think really the combination of what pluribus is trying to build and what they've developed around this unified cloud fabric, uh, is fits really nicely with the DPU and running that on the DPU and extending it really from your physical switch, all the way to your host environment, specifically on the data processing unit. So if you think about what's happening as you add data processing units to your environment. So every server we believe over time is going to have data processing units. So now you'll have to manage that complexity from the physical network layer to the host layer. And so what pluribus is really trying to do is extending the network fabric from the host, from the switch to the host, and really have that single pane of glass for network operators to be able to configure provision, manage all of the complexity of the network environment. >>So that's really how the partnership truly started. And so it started really with extending the network fabric, and now we're also working with them on security. So, you know, if you sort of take that concept of isolation and security isolation, what pluribus has within their fabric is the concept of micro-segmentation. And so now you can take that extended to the data processing unit and really have, um, isolated micro-segmentation workloads, whether it's bare metal cloud native environments, whether it's virtualized environments, whether it's public cloud, private cloud hybrid cloud. So it really is a magical partnership between the two companies with their unified cloud fabric running on, on the DPU. >>You know, what I love about this conversation is it reminds me of when you have these changing markets, the product gets pulled out of the market and, and you guys step up and create these new solutions. And I think this is a great example. So I have to ask you, how do you guys differentiate what sets this apart for customers with what's in it for the customer? >>Yeah. So I mentioned, you know, three things in terms of the value of what the Bluefield brings, right? There's offloading, accelerating, isolating, that's sort of the key core tenants of Bluefield. Um, so that, you know, if you sort of think about what, um, what Bluefields, what we've done, you know, in terms of the differentiation, we're really a robust platform for innovation. So we introduced Bluefield to, uh, last year, we're introducing Bluefield three, which is our next generation of Bluefields, you know, we'll have five X, the arm compute capacity. It will have 400 gig line rate acceleration, four X better crypto acceleration. So it will be remarkably better than the previous generation. And we'll continue to innovate and add, uh, chips to our portfolio every, every 18 months to two years. Um, so that's sort of one of the key areas of differentiation. The other is the, if you look at Nvidia and, and you know, what we're sort of known for is really known for our AI artificial intelligence and our artificial intelligence software, as well as our GPU. >>So you look at artificial intelligence and the combination of artificial intelligence plus data processing. This really creates the, you know, faster, more efficient, secure AI systems from the core of your data center, all the way out to the edge. And so with Nvidia, we really have these converged accelerators where we've combined the GPU, which does all your AI processing with your data processing with the DPU. So we have this convergence really nice convergence of that area. And I would say the third area is really around our developer environment. So, you know, one of the key, one of our key motivations at Nvidia is really to have our partner ecosystem, embrace our technology and build solutions around our technology. So if you look at what we've done with the DPU, with credit and an SDK, which is an open SDK called Doka, and it's an open SDK for our partners to really build and develop solutions using Bluefield and using all these accelerated libraries that we expose through Doka. And so part of our differentiation is really building this open ecosystem for our partners to take advantage and build solutions around our technology. >>You know, what's exciting is when I hear you talk, it's like you realize that there's no one general purpose network anymore. Everyone has their own super environment Supercloud or these new capabilities. They can really craft their own, I'd say, custom environment at scale with easy tools. Right. And it's all kind of, again, this is the new architecture Mike, you were talking about, how does customers run this effectively? Cost-effectively and how do people migrate? >>Yeah, I, I think that is the key question, right? So we've got this beautiful architecture. You, you know, Amazon nitro is a, is a good example of, of a smart NIC architecture that has been successfully deployed, but enterprises and serve tier two service providers and tier one service providers and governments are not Amazon, right? So they need to migrate there and they need this architecture to be cost-effective. And, and that's, that's super key. I mean, the reality is deep user moving fast, but they're not going to be, um, deployed everywhere on day one. Some servers will have DPS right away, some servers will have use and a year or two. And then there are devices that may never have DPS, right. IOT gateways, or legacy servers, even mainframes. Um, so that's the beauty of a solution that creates a fabric across both the switch and the DPU, right. >>Um, and by leveraging the Nvidia Bluefield DPU, what we really like about it is it's open. Um, and that drives, uh, cost efficiencies. And then, um, uh, you know, with this, with this, our architectural approach effectively, you get a unified solution across switch and DPU workload independent doesn't matter what hypervisor it is, integrated visibility, integrated security, and that can, uh, create tremendous cost efficiencies and, and really extract a lot of the expense from, from a capital perspective out of the network, as well as from an operational perspective, because now I have an SDN automated solution where I'm literally issuing a command to deploy a network service or to create or deploy our security policy and is deployed everywhere, automatically saving the oppor, the network operations team and the security operations team time. >>All right. So let me rewind that because that's super important. Get the unified cloud architecture, I'm the customer guy, but it's implemented, what's the value again, take, take me through the value to me. I have a unified environment. What's the value. >>Yeah. So I mean, the value is effectively, um, that, so there's a few pieces of value. The first piece of value is, um, I'm creating this clean D mark. I'm taking networking to the host. And like I mentioned, we're not running it on the CPU. So in implementations that run networking on the CPU, there's some conflict between the dev ops team who owned the server and the NetApps team who own the network because they're installing software on the, on the CPU stealing cycles from what should be revenue generating. Uh CPU's. So now by, by terminating the networking on the DPU, we click create this real clean DMARC. So the dev ops folks are happy because they don't necessarily have the skills to manage network and they don't necessarily want to spend the time managing networking. They've got their network counterparts who are also happy the NetApps team, because they want to control the networking. >>And now we've got this clean DMARC where the DevOps folks get the services they need and the NetApp folks get the control and agility they need. So that's a huge value. Um, the next piece of value is distributed security. This is essential. I mentioned earlier, you know, put pushing out micro-segmentation and distributed firewall, basically at the application level, right, where I create these small, small segments on an by application basis. So if a bad actor does penetrate the perimeter firewall, they're contained once they get inside. Cause the worst thing is a bad actor, penetrates a perimeter firewall and can go wherever they want and wreak havoc. Right? And so that's why this, this is so essential. Um, and the next benefit obviously is this unified networking operating model, right? Having, uh, uh, uh, an operating model across switch and server underlay and overlay, workload agnostic, making the life of the NetApps teams much easier so they can focus their time on really strategy instead of spending an afternoon, deploying a single villain, for example. >>Awesome. And I think also from my standpoint, I mean, perimeter security is pretty much, I mean, they're out there, it gets the firewall still out there exists, but pretty much they're being breached all the time, the perimeter. So you have to have this new security model. And I think the other thing that you mentioned, the separation between dev ops is cool because the infrastructure is code is about making the developers be agile and build security in from day one. So this policy aspect is, is huge. Um, new control points. I think you guys have a new architecture that enables the security to be handled more flexible. >>Right. >>That seems to be the killer feature here, >>Right? Yeah. If you look at the data processing unit, I think one of the great things about sort of this new architecture, it's really the foundation for zero trust it's. So like you talked about the perimeter is getting breached. And so now each and every compute node has to be protected. And I think that's sort of what you see with the partnership between pluribus and Nvidia is the DPU is really the foundation of zero trust. And pluribus is really building on that vision with, uh, allowing sort of micro-segmentation and being able to protect each and every compute node as well as the underlying network. >>This is super exciting. This is an illustration of how the market's evolving architectures are being reshaped and refactored for cloud scale and all this new goodness with data. So I gotta ask how you guys go into market together. Michael, start with you. What's the relationship look like in the go to market with an Nvidia? >>Sure. Um, I mean, we're, you know, we're super excited about the partnership, obviously we're here together. Um, we think we've got a really good solution for the market, so we're jointly marketing it. Um, uh, you know, obviously we appreciate that Nvidia is open. Um, that's, that's sort of in our DNA, we're about open networking. They've got other ISV who are gonna run on Bluefield too. We're probably going to run on other DPS in the, in the future, but right now, um, we're, we feel like we're partnered with the number one, uh, provider of DPS in the world and, uh, super excited about, uh, making a splash with it. >>I'm in get the hot product. >>Yeah. So Bluefield too, as I mentioned was GA last year, we're introducing, uh, well, we now also have the converged accelerator. So I talked about artificial intelligence or artificial intelligence with the Bluefield DPU, all of that put together on a converged accelerator. The nice thing there is you can either run those workloads. So if you have an artificial intelligence workload and an infrastructure workload, you can warn them separately on the same platform or you can actually use, uh, you can actually run artificial intelligence applications on the Bluefield itself. So that's what the converged accelerator really brings to the table. Uh, so that's available now. Then we have Bluefield three, which will be available late this year. And I talked about sort of, you know, uh, how much better that next generation of Bluefield is in comparison to Bluefield two. So we will see Bluefield three shipping later on this year, and then our software stack, which I talked about, which is called Doka we're on our second version are Doka one dot two. >>We're releasing Doka one dot three, uh, in about two months from now. And so that's really our open ecosystem framework. So allow you to program the Bluefields. So we have all of our acceleration libraries, um, security libraries, that's all packed into this STK called Doka. And it really gives that simplicity to our partners to be able to develop on top of Bluefield. So as we add new generations of Bluefield, you know, next, next year, we'll have, you know, another version and so on and so forth Doka is really that unified unified layer that allows, um, Bluefield to be both forwards compatible and backwards compatible. So partners only really have to think about writing to that SDK once, and then it automatically works with future generations of Bluefields. So that's sort of the nice thing around, um, around Doka. And then in terms of our go to market model, we're working with every, every major OEM. So, uh, later on this year, you'll see, you know, major server manufacturers, uh, releasing Bluefield enabled servers. So, um, more to come >>Awesome, save money, make it easier, more capabilities, more workload power. This is the future of, of cloud operations. >>Yeah. And, and, and, uh, one thing I'll add is, um, we are, um, we have a number of customers as you'll hear in the next segment, um, that are already signed up and we'll be working with us for our, uh, early field trial starting late April early may. Um, we are accepting registrations. You can go to www.pluribusnetworks.com/e F T a. If you're interested in signing up for, um, uh, being part of our field trial and providing feedback on the product, >>Awesome innovation and network. Thanks so much for sharing the news. Really appreciate it. Thanks so much. Okay. In a moment, we'll be back to look deeper in the product, the integration security zero trust use cases. You're watching the cube, the leader in enterprise tech coverage, >>Cloud networking is complex and fragmented slowing down your business. How can you simplify and unify your cloud networks to increase agility and business velocity? >>Pluribus unified cloud networking provides a unified simplify and agile network fabric across all clouds. It brings the simplicity of a public cloud operation model to private clouds, dramatically reducing complexity and improving agility, availability, and security. Now enterprises and service providers can increase their business philosophy and delight customers in the distributed multi-cloud era. We achieve this with a new approach to cloud networking, pluribus unified cloud fabric. This open vendor, independent network fabric, unifies, networking, and security across distributed clouds. The first step is extending the fabric to servers equipped with data processing units, unifying the fabric across switches and servers, and it doesn't stop there. The fabric is unified across underlay and overlay networks and across all workloads and virtualization environments. The unified cloud fabric is optimized for seamless migration to this new distributed architecture, leveraging the power of the DPU for application level micro-segmentation distributed fireball and encryption while still supporting those servers and devices that are not equipped with a DPU. Ultimately the unified cloud fabric extends seamlessly across distributed clouds, including central regional at edge private clouds and public clouds. The unified cloud fabric is a comprehensive network solution. That includes everything you need for clouds, networking built in SDN automation, distributed security without compromises, pervasive wire speed, visibility and application insight available on your choice of open networking switches and DP use all at the lowest total cost of ownership. The end result is a dramatically simplified unified cloud networking architecture that unifies your distributed clouds and frees your business to move at cloud speed, >>To learn more, visit www.pluribusnetworks.com. >>Okay. We're back I'm John ferry with the cube, and we're going to go deeper into a deep dive into unified cloud networking solution from Clovis and Nvidia. And we'll examine some of the use cases with Alessandra Burberry, VP of product management and pullovers networks and Pete Bloomberg who's director of technical marketing and video remotely guys. Thanks for coming on. Appreciate it. >>Yeah. >>So deep dive, let's get into the what and how Alexandra we heard earlier about the pluribus Nvidia partnership and the solution you're working together on what is it? >>Yeah. First let's talk about the water. What are we really integrating with the Nvidia Bluefield, the DPO technology, uh, plugable says, um, uh, there's been shipping, uh, in, uh, in volume, uh, in multiple mission critical networks. So this advisor one network operating systems, it runs today on a merchant silicone switches and effectively it's a standard open network operating system for data center. Um, and the novelty about this system that integrates a distributed control plane for, at water made effective in SDN overlay. This automation is a completely open and interoperable and extensible to other type of clouds is not enclosed them. And this is actually what we're now porting to the Nvidia DPO. >>Awesome. So how does it integrate into Nvidia hardware and specifically how has pluribus integrating its software with the Nvidia hardware? >>Yeah, I think, uh, we leverage some of the interesting properties of the Bluefield, the DPO hardware, which allows actually to integrate, uh, um, uh, our software, our network operating system in a manner which is completely isolated and independent from the guest operating system. So the first byproduct of this approach is that whatever we do at the network level on the DPU card that is completely agnostic to the hypervisor layer or OSTP layer running on, uh, on the host even more, um, uh, we can also independently manage this network, know that the switch on a Neek effectively, um, uh, managed completely independently from the host. You don't have to go through the network operating system, running on x86 to control this network node. So you throw yet the experience effectively of a top of rack for virtual machine or a top of rack for, uh, Kubernetes bots, where instead of, uh, um, if you allow me with the analogy instead of connecting a server knee directly to a switchboard, now you're connecting a VM virtual interface to a virtual interface on the switch on an ache. >>And, uh, also as part of this integration, we, uh, put a lot of effort, a lot of emphasis in, uh, accelerating the entire, uh, data plane for networking and security. So we are taking advantage of the DACA, uh, Nvidia DACA API to program the accelerators. And these accomplished two things with that. Number one, uh, you, uh, have much greater performance, much better performance. They're running the same network services on an x86 CPU. And second, this gives you the ability to free up, I would say around 20, 25% of the server capacity to be devoted either to, uh, additional workloads to run your cloud applications, or perhaps you can actually shrink the power footprint and compute footprint of your data center by 20%, if you want to run the same number of compute workloads. So great efficiencies in the overall approach, >>And this is completely independent of the server CPU, right? >>Absolutely. There is zero code from running on the x86, and this is what we think this enables a very clean demarcation between computer and network. >>So Pete, I gotta get, I gotta get you in here. We heard that, uh, the DPU is enabled cleaner separation of dev ops and net ops. Can you explain why that's important because everyone's talking DevSecOps right now, you've got net ops, net, net sec ops, this separation. Why is this clean separation important? >>Yeah, I think it's a, you know, it's a pragmatic solution in my opinion. Um, you know, we wish the world was all kind of rainbows and unicorns, but it's a little, a little messier than that. And I think a lot of the dev ops stuff and that, uh, mentality and philosophy, there's a natural fit there. Right? You have applications running on servers. So you're talking about developers with those applications integrating with the operators of those servers. Well, the network has always been this other thing and the network operators have always had a very different approach to things than compute operators. And, you know, I think that we, we in the networking industry have gotten closer together, but there's still a gap there's still some distance. And I think in that distance, isn't going to be closed. And so, you know, again, it comes down to pragmatism and I think, you know, one of my favorite phrases is look good fences, make good neighbors. And that's what this is. >>Yeah. That's a great point because dev ops has become kind of the calling card for cloud, right. But dev ops is as simply infrastructure as code and infrastructure is networking, right? So if infrastructure is code, you know, you're talking about, you know, that part of the stack under the covers under the hood, if you will, this is super important distinction. And this is where the innovation is. Can you elaborate on how you see that? Because this is really where the action is right now. >>Yeah, exactly. And I think that's where, um, one from, from the policy, the security that the zero trust aspect of this, right? If you get it wrong on that network side, all of a sudden you, you can totally open up that those capabilities. And so security is part of that. But the other part is thinking about this at scale, right? So we're taking one top of rack switch and adding, you know, up to 48 servers per rack. And so that ability to automate, orchestrate and manage at scale becomes absolutely critical. >>I'll Sandra, this is really the why we're talking about here, and this is scale. And again, getting it right. If you don't get it right, you're going to be really kind of up, you know what you know, so this is a huge deal. Networking matters, security matters, automation matters, dev ops, net ops, all coming together, clean separation, um, help us understand how this joint solution with Nvidia fits into the pluribus unified cloud networking vision, because this is what people are talking about and working on right now. >>Yeah, absolutely. So I think here with this solution, we're attacking two major problems in cloud networking. One is, uh, operation of, uh, cloud networking. And the second is a distributing security services in the cloud infrastructure. First, let me talk about the first water. We really unifying. If we're unifying something, something must be at least fragmented or this jointed and the, what is this joint that is actually the network in the cloud. If you look holistically, how networking is deployed in the cloud, you have your physical fabric infrastructure, right? Your switches and routers, you'll build your IP clause fabric leaf in spine typologies. This is actually a well understood the problem. I, I would say, um, there are multiple vendors, uh, uh, with, uh, um, uh, let's say similar technologies, um, very well standardized, whether you will understood, um, and almost a commodity, I would say building an IP fabric these days, but this is not the place where you deploy most of your services in the cloud, particularly from a security standpoint, two services are actually now moved into the compute layer where you actually were called builders, have to instrument the, a separate, uh, network virtualization layer, where they deploy segmentation and security closer to the workloads. >>And this is where the complication arise. These high value part of the cloud network is where you have a plethora of options that they don't talk to each other. And they are very dependent on the kind of hypervisor or compute solution you choose. Um, for example, the networking API to be between an GSXI environment or an hyper V or a Zen are completely disjointed. You have multiple orchestration layers. And when, and then when you throw in also Kubernetes in this, in this, in this type of architecture, uh, you're introducing yet another level of networking. And when Kubernetes runs on top of VMs, which is a prevalent approach, you actually just stacking up multiple networks on the compute layer that they eventually run on the physical fabric infrastructure. Those are all ships in the nights effectively, right? They operate as completely disjointed. And we're trying to attack this problem first with the notion of a unified fabric, which is independent from any workloads, whether it's this fabric spans on a switch, which can be con connected to a bare metal workload, or can span all the way inside the DPU, uh, where, um, you have, uh, your multi hypervisor compute environment. >>It's one API, one common network control plane, and one common set of segmentation services for the network. That's probably the number one, >>You know, it's interesting you, man, I hear you talking, I hear one network month, different operating models reminds me of the old serverless days. You know, there's still servers, but they call it serverless. Is there going to be a term network list? Because at the end of the day, it should be one network, not multiple operating models. This, this is a problem that you guys are working on. Is that right? I mean, I'm not, I'm just joking server listen network list, but the idea is it should be one thing. >>Yeah, it's effectively. What we're trying to do is we are trying to recompose this fragmentation in terms of network operation, across physical networking and server networking server networking is where the majority of the problems are because of the, uh, as much as you have standardized the ways of building, uh, physical networks and cloud fabrics with IP protocols and internet, you don't have that kind of, uh, uh, sort of, uh, um, um, uh, operational efficiency, uh, at the server layer. And, uh, this is what we're trying to attack first. The, with this technology, the second aspect we're trying to attack is are we distribute the security services throughout the infrastructure, more efficiently, whether it's micro-segmentation is a stateful firewall services, or even encryption. Those are all capabilities enabled by the blue field, uh, uh, the Butte technology and, uh, uh, we can actually integrate those capabilities directly into the nettle Fabrica, uh, limiting dramatically, at least for east-west traffic, the sprawl of, uh, security appliances, whether virtual or physical, that is typically the way the people today, uh, segment and secure the traffic in the cloud. >>Awesome. Pete, all kidding aside about network lists and serverless kind of fun, fun play on words there, the network is one thing it's basically distributed computing, right? So I love to get your thoughts about this distributed security with zero trust as the driver for this architecture you guys are doing. Can you share in more detail the depth of why DPU based approach is better than alternatives? >>Yeah, I think what's, what's beautiful and kind of what the DPU brings. That's new to this model is a completely isolated compute environment inside. So, you know, it's the, uh, yo dog, I heard you like a server, so I put a server inside your server. Uh, and so we provide, uh, you know, armed CPU's memory and network accelerators inside, and that is completely isolated from the host. So the server, the, the actual x86 host just thinks it has a regular Nick in there, but you actually have this full control plane thing. It's just like taking your top of rack switch and shoving it inside of your compute node. And so you have not only the separation, um, within the data plane, but you have this complete control plane separation. So you have this element that the network team can now control and manage, but we're taking all of the functions we used to do at the top of rack switch, and we're just shooting them now. >>And, you know, as time has gone on we've, we've struggled to put more and more and more into that network edge. And the reality is the network edge is the compute layer, not the top of rack switch layer. And so that provides this phenomenal enforcement point for security and policy. And I think outside of today's solutions around virtual firewalls, um, the other option is centralized appliances. And even if you can get one that can scale large enough, the question is, can you afford it? And so what we end up doing is we kind of hope that of aliens good enough, or we hope that if the excellent tunnel is good enough and we can actually apply more advanced techniques there because we can't physically, you know, financially afford that appliance to see all of the traffic. And now that we have a distributed model with this accelerator, we could do it. >>So what's the what's in it for the customer. I real quick, cause I think this is interesting point. You mentioned policy, everyone in networking knows policy is just a great thing and it adds, you hear it being talked about up the stack as well. When you start getting to orchestrating microservices and whatnot, all that good stuff going on there, containers and whatnot and modern applications. What's the benefit to the customers with this approach? Because what I heard was more scale, more edge deployment, flexibility, relative to security policies and application enablement. I mean, is that what what's the customer get out of this architecture? What's the enablement. >>It comes down to, uh, taking again the capabilities that were in that top of rack switch and asserting them down. So that makes simplicity smaller blast radiuses for failure, smaller failure domains, maintenance on the networks, and the systems become easier. Your ability to integrate across workloads becomes infinitely easier. Um, and again, you know, we always want to kind of separate each one of those layers. So just as in say, a VX land network, my leaf and spine don't have to be tightly coupled together. I can now do this at a different layer. And so you can run a DPU with any networking in the core there. And so you get this extreme flexibility. You can start small, you can scale large. Um, you know, to me, the, the possibilities are endless. Yes, >>It's a great security control plan. Really flexibility is key. And, and also being situationally aware of any kind of threats or new vectors or whatever's happening in the network. Alessandra, this is huge upside, right? You've already identified some successes with some customers on your early field trials. What are they doing and why are they attracted to the solution? >>Yeah, I think the response from customers has been, uh, the most, uh, encouraging and, uh, exciting, uh, for, uh, for us to, uh, to sort of continue and work and develop this product. And we have actually learned a lot in the process. Um, we talked to tier two tier three cloud providers. Uh, we talked to, uh, SP um, software Tyco type of networks, uh, as well as a large enterprise customers, um, in, uh, one particular case. Um, uh, one, uh, I think, um, let me, let me call out a couple of examples here, just to give you a flavor. Uh, there is a service provider, a cloud provider, uh, in Asia who is actually managing a cloud, uh, where they are offering services based on multiple hypervisors. They are native services based on Zen, but they also are on ramp into the cloud, uh, workloads based on, uh, ESI and, uh, uh, and KVM, depending on what the customer picks from the piece on the menu. >>And they have the problem of now orchestrating through their orchestrate or integrating with the Zen center with vSphere, uh, with, uh, open stack to coordinate these multiple environments and in the process to provide security, they actually deploy virtual appliances everywhere, which has a lot of costs, complication, and eats up into the server CPU. The problem is that they saw in this technology, they call it actually game changing is actually to remove all this complexity of in a single network and distribute the micro-segmentation service directly into the fabric. And overall, they're hoping to get out of it, uh, uh, tremendous, uh, um, opics, uh, benefit and overall, um, uh, operational simplification for the cloud infrastructure. That's one potent a use case. Uh, another, uh, large enterprise customer global enterprise customer, uh, is running, uh, both ESI and hyper V in that environment. And they don't have a solution to do micro-segmentation consistently across hypervisors. >>So again, micro-segmentation is a huge driver security looks like it's a recurring theme, uh, talking to most of these customers and in the Tyco space, um, uh, we're working with a few types of customers on the CFT program, uh, where the main goal is actually to our Monet's network operation. They typically handle all the VNF search with their own homegrown DPDK stack. This is overly complex. It is frankly also as low and inefficient, and then they have a physical network to manage the, the idea of having again, one network, uh, to coordinate the provision in our cloud services between the, the take of VNF, uh, and, uh, the rest of the infrastructure, uh, is extremely powerful on top of the offloading capability of the, by the bluefin DPOs. Those are just some examples. >>That was a great use case, a lot more potential. I see that with the unified cloud networking, great stuff, feed, shout out to you guys at Nvidia had been following your success for a long time and continuing to innovate as cloud scales and pluribus here with the unified networking, kind of bring it to the next level. Great stuff. Great to have you guys on. And again, software keeps driving the innovation again, networking is just a part of it, and it's the key solution. So I got to ask both of you to wrap this up. How can cloud operators who are interested in, in this, uh, new architecture and solution, uh, learn more because this is an architectural shift. People are working on this problem. They're trying to think about multiple clouds of trying to think about unification around the network and giving more security, more flexibility, uh, to their teams. How can people learn more? >>Yeah, so, uh, all Sandra and I have a talk at the upcoming Nvidia GTC conference. Um, so that's the week of March 21st through 24th. Um, you can go and register for free and video.com/at GTC. Um, you can also watch recorded sessions if you ended up watching us on YouTube a little bit after the fact. Um, and we're going to dive a little bit more into the specifics and the details and what we're providing in the solution. >>Alexandra, how can people learn more? >>Yeah, absolutely. People can go to the pluribus, a website, www boost networks.com/eft, and they can fill up the form and, uh, they will contact durables to either know more or to know more and actually to sign up for the actual early field trial program, which starts at the end of April. >>Okay. Well, we'll leave it there. Thanks. You both for joining. Appreciate it up next. You're going to hear an independent analyst perspective and review some of the research from the enterprise strategy group ESG. I'm John ferry with the >>Cube. Thanks for watching. >>Okay. We've heard from the folks at networks and Nvidia about their effort to transform cloud networking and unify bespoke infrastructure. Now let's get the perspective from an independent analyst and to do so. We welcome in ESG, senior analysts, Bob LA Liberte, Bob. Good to see you. Thanks for coming into our east coast studios. >>Oh, thanks for having me. It's great to be >>Here. Yeah. So this, this idea of unified cloud networking approach, how serious is it? What's what's driving it. >>Yeah, there's certainly a lot of drivers behind it, but probably the first and foremost is the fact that application environments are becoming a lot more distributed, right? So the, it pendulum tends to swing back and forth. And we're definitely on one that's swinging from consolidated to distributed. And so applications are being deployed in multiple private data centers, multiple public cloud locations, edge locations. And as a result of that, what you're seeing is a lot of complexity. So organizations are having to deal with this highly disparate environment. They have to secure it. They have to ensure connectivity to it and all that's driving up complexity. In fact, when we asked in one of our last surveys and last year about network complexity, more than half 54% came out and said, Hey, our network environment is now either more or significantly more complex than it used to be. >>And as a result of that, what you're seeing is it's really impacting agility. So everyone's moving to these modern application environments, distributing them across areas so they can improve agility yet it's creating more complexity. So a little bit counter to the fact and, you know, really counter to their overarching digital transformation initiatives. From what we've seen, you know, nine out of 10 organizations today are either beginning in process or have a mature digital transformation process or initiative, but their top goals, when you look at them, it probably shouldn't be a surprise. The number one goal is driving operational efficiency. So it makes sense. I've distributed my environment to create agility, but I've created a lot of complexity. So now I need these tools that are going to help me drive operational efficiency, drive better experience. >>I mean, I love how you bring in the data yesterday. Does a great job with that. Uh, questions is, is it about just unifying existing networks or is there sort of a need to rethink kind of a do-over network, how networks are built? >>Yeah, that's a, that's a really good point because certainly unifying networks helps right. Driving any kind of operational efficiency helps. But in this particular case, because we've made the transition to new application architectures and the impact that's having as well, it's really about changing and bringing in new frameworks and new network architectures to accommodate those new application architectures. And by that, what I'm talking about is the fact that these new modern application architectures, microservices, containers are driving a lot more east west traffic. So in the old days, it used to be easier in north south coming out of the server, one application per server, things like that. Right now you've got hundreds, if not thousands of microservices communicating with each other users communicating to them. So there's a lot more traffic and a lot of it's taking place within the servers themselves. The other issue that you starting to see as well from that security perspective, when we were all consolidated, we had those perimeter based legacy, you know, castle and moat security architectures, but that doesn't work anymore when the applications aren't in the castle, right. >>When everything's spread out that that no longer happens. So we're absolutely seeing, um, organizations trying to, trying to make a shift. And, and I think much, like if you think about the shift that we're seeing with all the remote workers and the sassy framework to enable a secure framework there, this it's almost the same thing. We're seeing this distributed services framework come up to support the applications better within the data centers, within the cloud data centers, so that you can drive that security closer to those applications and make sure they're, they're fully protected. Uh, and that's really driving a lot of the, you know, the zero trust stuff you hear, right? So never trust, always verify, making sure that everything is, is, is really secure micro-segmentation is another big area. So ensuring that these applications, when they're connected to each other, they're, they're fully segmented out. And that's again, because if someone does get a breach, if they are in your data center, you want to limit the blast radius, you want to limit the amount of damage that's done. So that by doing that, it really makes it a lot harder for them to see everything that's in there. >>You know, you mentioned zero trust. It used to be a buzzword, and now it's like become a mandate. And I love the mode analogy. You know, you build a moat to protect the queen and the castle, the Queens left the castles, it's just distributed. So how should we think about this, this pluribus and Nvidia solution. There's a spectrum, help us understand that you've got appliances, you've got pure software solutions. You've got what pluribus is doing with Nvidia, help us understand that. >>Yeah, absolutely. I think as organizations recognize the need to distribute their services to closer to the applications, they're trying different models. So from a legacy approach, you know, from a security perspective, they've got these centralized firewalls that they're deploying within their data centers. The hard part for that is if you want all this traffic to be secured, you're actually sending it out of the server up through the rack, usually to in different location in the data center and back. So with the need for agility, with the need for performance, right, that adds a lot of latency. Plus when you start needing to scale, that means adding more and more network connections, more and more appliances. So it can get very costly as well as impacting the performance. The other way that organizations are seeking to solve this problem is by taking the software itself and deploying it on the servers. Okay. So that's a, it's a great approach, right? It brings it really close to the applications, but the things you start running into there, there's a couple of things. One is that you start seeing that the DevOps team start taking on that networking and security responsibility, which they >>Don't want to >>Do, they don't want to do right. And the operations teams loses a little bit of visibility into that. Um, plus when you load the software onto the server, you're taking up precious CPU cycles. So if you're really wanting your applications to perform at an optimized state, having additional software on there, isn't going to, isn't going to do it. So, you know, when we think about all those types of things, right, and certainly the other side effects of that is the impact of the performance, but there's also a cost. So if you have to buy more servers because your CPU's are being utilized, right, and you have hundreds or thousands of servers, right, those costs are going to add up. So what, what Nvidia and pluribus have done by working together is to be able to take some of those services and be able to deploy them onto a smart Nick, right? >>To be able to deploy the DPU based smart SMARTNICK into the servers themselves. And then pluribus has come in and said, we're going to unify create that unified fabric across the networking space, into those networking services all the way down to the server. So the benefits of having that are pretty clear in that you're offloading that capability from the server. So your CPU's are optimized. You're saving a lot of money. You're not having to go outside of the server and go to a different rack somewhere else in the data center. So your performance is going to be optimized as well. You're not going to incur any latency hit for every trip round trip to the, to the firewall and back. So I think all those things are really important. Plus the fact that you're going to see from a, an organizational aspect, we talked about the dev ops and net ops teams. The network operations teams now can work with the security teams to establish the security policies and the networking policies. So that they've dev ops teams. Don't have to worry about that. So essentially they just create the guardrails and let the dev op team run. Cause that's what they want. They want that agility and speed. >>Yeah. Your point about CPU cycles is key. I mean, it's estimated that 25 to 30% of CPU cycles in the data center are wasted. The cores are wasted doing storage offload or, or networking or security offload. And, you know, I've said many times everybody needs a nitro like Amazon nugget, but you can't go, you can only buy Amazon nitro if you go into AWS. Right. Everybody needs a nitro. So is that how we should think about this? >>Yeah. That's a great analogy to think about this. Um, and I think I would take it a step further because it's, it's almost the opposite end of the spectrum because pluribus and video are doing this in a very open way. And so pluribus has always been a proponent of open networking. And so what they're trying to do is extend that now to these distributed services. So leverage working with Nvidia, who's also open as well, being able to bring that to bear so that organizations can not only take advantage of these distributed services, but also that unified networking fabric, that unified cloud fabric across that environment from the server across the switches, the other key piece of what pluribus is doing, because they've been doing this for a while now, and they've been doing it with the older application environments and the older server environments, they're able to provide that unified networking experience across a host of different types of servers and platforms. So you can have not only the modern application supported, but also the legacy environments, um, you know, bare metal. You could go any type of virtualization, you can run containers, et cetera. So a wide gambit of different technologies hosting those applications supported by a unified cloud fabric from pluribus. >>So what does that mean for the customer? I don't have to rip and replace my whole infrastructure, right? >>Yeah. Well, think what it does for, again, from that operational efficiency, when you're going from a legacy environment to that modern environment, it helps with the migration helps you accelerate that migration because you're not switching different management systems to accomplish that. You've got the same unified networking fabric that you've been working with to enable you to run your legacy as well as transfer over to those modern applications. Okay. >>So your people are comfortable with the skillsets, et cetera. All right. I'll give you the last word. Give us the bottom line here. >>So yeah, I think obviously with all the modern applications that are coming out, the distributed application environments, it's really posing a lot of risk on these organizations to be able to get not only security, but also visibility into those environments. And so organizations have to find solutions. As I said, at the beginning, they're looking to drive operational efficiency. So getting operational efficiency from a unified cloud networking solution, that it goes from the server across the servers to multiple different environments, right in different cloud environments is certainly going to help organizations drive that operational efficiency. It's going to help them save money for visibility, for security and even open networking. So a great opportunity for organizations, especially large enterprises, cloud providers who are trying to build that hyperscaler like environment. You mentioned the nitro card, right? This is a great way to do it with an open solution. >>Bob, thanks so much for, for coming in and sharing your insights. Appreciate it. >>You're welcome. Thanks. >>Thanks for watching the program today. Remember all these videos are available on demand@thekey.net. You can check out all the news from today@siliconangle.com and of course, pluribus networks.com many thanks diplomas for making this program possible and sponsoring the cube. This is Dave Volante. Thanks for watching. Be well, we'll see you next time.

>>from the Silicon Angle Media office in Boston, Massachusetts. It's the Cube now here's your host, Dave Vellante. >>Hello, everyone. And welcome to this breaking analysis. We're here to assess the VM Ware v Sphere seven announcement, which is the general availability of so called Project Pacific. VM Ware has called this the biggest change to V sphere in the last 10 years. Now Project Specific Pacific supports kubernetes and natively in VM Ware environments. Why is this important? This is critical for multi and hybrid cloud because Kubernetes and its surrounding orchestration enable application portability and management. Yeah, as we've been reporting, VM Ware is one of the big players eyeing multi cloud, along with a crowded field of aspirants that include IBM with Red hat, Microsoft, Cisco, Google and a host of specialists in the ecosystem. Like how she and rancher as well play. Some players have focused in their respective stack swim lanes like security and data protection, storage, networking, etcetera. And with me to dig into this announcement is stew. Minutemen's Do is a senior analyst at Wiki Bond and co host of The Cube is too good to see you and let's get into it great to talk about this state. Okay, so the Sphere seven, what is being announced? And why is it relevant? >>Yes. So, David, as you said in the open, this is the general availability of what they talked about at VM World 2019 as Project Pacific. So it really is integrating kubernetes into V sphere. The VM ware, of course, will position this is that they're now enabling, you know, the 90% of the data centers around the world that have VM ware. Hey, your kubernetes enabled. Congratulations. You're cloud native. Everything like that. Only being a little facetious here. But this is very important. How do we get from where we were to live in this more cloud? Native environments. So containers in general and kubernetes specifically are being a first class citizen. There's a lot of work, Dave, and my understanding this has been going on for a number of years. You know, it's not like they just started working at this six months ago. A overhaul to how this works. Because it's not just we're going to stick a couple of containers on top of, you know, the guest operating system in the virtual machine. But there is a supervisor cluster for kubernetes at the hyper visor level. And there's a lot of, you know, in the weeds things that we're all trying to understand and figure out because you've got you know, we've got a hyper visor and you've got VM. And now you've got the containers and kubernetes on. Some of them are living in my data center. Some VM ware, of course, lives on multiple clouds like the VM ware on AWS. Solutions of this will go there on and, you know, how do I manage that? How does this impact my operations? You know, how did this change my application portfolio? Because, you know, the early value proposition for VM Ware always was. Hey, you're gonna put VM ware on there. You don't need to touch your applications. Everything runs like it did before you were running windows APS on a physical server. You move into virtual. It's all great. There's a lot of nuance and complexity. So when VM Ware says this is the biggest change in a decade probably is, I think back to you know, I remember when the fx 2.0, rolled out in V motion really changed the landscape. That was big V balls. Move to really ah storage. To really understand that architecture and really fix storage was was a huge undertaking that took many years. This this definitely stacks up with some of those previous changes to really change the way that we think about VM Ware. I think the advertising you have even seen from being where some places is don't think of them as VM ware their cloud where our container ware with like because vm zehr still there. But VM Ware is much more than VMS today, >>so this feels like it's bm were trying to maintain its relevance in a cloud native world and really solidify its because, let's face it, VM Ware is a platform that Pat Gelsinger's has ride. The Waves tried many times in many angles to try to ride the cloud wave, and it's finally settled on the partnerships with AWS specifically. But others on DSO really Is this their attempt to become cloud native, not get left behind and be cloud naive? His many say >>Yeah, great question, David. Absolutely. There's the question as to you know what's happening with my applications, you know lots of customers. They say, Well, I'm just going to satisfy the environments. Watched the huge growth of companies like service now workday. Those applications, well, customers don't even know what they live on. Do they live on virtualization? Environment is a containers I don't need to worry about because SAS takes care of that. If I'm building modern applications, well, I'm probably not starting with VMS. Containers are the way that most people are doing that. Or they might even be going serverless now if we take these environments. So how does VM ware make sure that they have the broadest application support? Kubernetes really won the container orchestration wars on. And this is a way that VM ware now can enable customers to move down that path to modernize their environments on. And what they wanna have is really some consistency between what's happening in the cloud and happening in the environments that they control >>themselves. Vm ware saying that containers in our first class citizen within v sphere what does that mean? Why is that important? First of all, are they really And what does that mean? And why is that important? >>Yes. So, Dave, my understanding is, you know, absolutely. It's their, You know, the nuances that you will put there is. You know, we're not just running bare metal servers with Lennox and running containers on top of it. It is. You're still sitting on top of the hyper visors. One of the things I'm trying to understand when you dig down is you know what? The device driver level VM ware always looked a little bit like Linux. But the people that use it and operate it, they're not letting people Dave, these, you know, the OS. The number one os that always ran on VM ware was Windows and the traditional applications that ran there. So when we talk about containers and we're enabling that in a kubernetes environment, there are some questions about how do we make sure that my applications get certified? Dave, you got a lot of history knowing things like s ap and Oracle. I need to make sure that we've tested everything in this works. This is not what we were running traditionally in VM ware and VM ware. Just thanks. Hey, v Sphere seven, turn the crank. Everything certified Well, I would tell customers make sure you understand that your application has been tested, that your Eyes V has certified this environment because this is definitely, as VM Ware says, a huge architectural change. So therefore, there's some ripple effects to make sure that what I'm doing in this environment stays fully supported. Of course, I'm sure VM Ware is working with their huge ecosystem to make sure that all the pieces or environment you mentioned things like data protection. We absolutely know that VM Ware is making sure the day one the data protection plugs in and supported in these environments when you're using the kind of kubernetes persona or containers solutions in V sphere. >>Well, this brings me to my next question. I mean, we were talking to Bernard Golden the other day and he was saying, You know, Kubernetes is necessary for multi cloud, but it's insufficient. And so this seems to me to be a first step and, as I say, VM ware maintaining and growing its relevance. But there's gonna be a roadmap here that goes beyond just containers and portability. There's other management factors you mentioned security of enabling the ecosystem to plug in. So maybe talk about that a little bit in terms of what's necessary to really build this out over the next >>decade. And actually, it's a great point. So, first of all, you know, V. Sphere, of course, is the core of VM Ware's business. But there's only a piece of the overall portfolio said this lives in. I believe they would consider this part of what they call their Tansu family. Tando is their cloud native overarching piece of it, and one of the updates is their product hands admission control. Which of the existing product really came out of the Hep D Oh acquisition is how we can really manage any kubernetes anywhere, and this is pure software. Dave. I'm sure you saw the most recent earnings announcement from VM Ware, and you know what's going sass. What's going subscription? VM Ware is trying to build out some of their software portfolio that that isn't kind of the more traditional shrink wrap software, so Tan Xue can manage any kubernetes environment. So, of course, day one Hey, obviously or seven, it's a kubernetes distribution. Absolutely. It's going to manage this environment and but also if I've got Cooper days from azure kubernetes from Amazon communities from other environment. Tanja can manage across all of those environments. So when when you're what VM Ware has always done. If you think back in the early days of virtualization, I had a lot of different servers. How do I manage across those environments? Well, VM ware was a layer that lived across them. VM Ware is trying to do the same thing in the cloud. Talk about multi cloud. And how do I manage that? How do we get value across them? Well, there's certain pieces that you know VM Ware is looking to enable with their management software to go across them. But there are a lot of other companies, you know, Amazon Google actually not Amazon yet for multi cloud. But Microsoft and Google absolutely spent a lot of time talking about that in the last year. A swell as you mentioned. Companies like Rancher and Hashi Corp absolutely play across What Lots of these multi cloud. Well, >>let's talk about the competition. Who do you see is the number one competitors >>Well, so the number one competitor absolutely has to be red hat, Dave. So you know, when I've been in the kubernetes ecosystem for a number of years for many years. When I talk to practitioners, the number one, you know what kubernetes you're using? Well, the answer for many years was, Well, I'm grabbing it, you know, the open source and I'm building my own stack. And the reason customers did that was because there wasn't necessarily maturity, and this was kind of leading edge, bleeding edge customers in this space. The number two besides build my own was Red Hat was because I'm a red hat customer, a lot of Lennox tooling the way of building things the way my application developers do. Things fit in that environment. And therefore, that's why Red Hat has over 2000 open shift customers leading distribution for Kubernetes. And you know, this seems purely directly targeted at that market. That red hat did you know it was a big reason why IBM spent $34 billion on the Red Hat acquisition is to go after this multi cloud opportunity. So you know, absolutely this shot across the bow because Red Hat is a partner of VM Ware's, but absolutely is also a competitive >>Well, Maritz told me years ago that's true. We're with everybody and you could see that playing out. What if you look at what VM Ware could do and some of their options if they gave it away, that would really be a shot across the bow at open shift, wouldn't it? >>Yeah, absolutely, Dave, because kubernetes is not free if you're enabling kubernetes on my Google environment, I, you know, just within the last week's awesome things that were like, Okay, wait. If you're testing an environment, yes, it is free. But, you know, started talking about the hourly charges for the management layer of kubernetes. So you know kubernetes again. A color friend, Cory Quinn. Communities absolutely is not free, and he will give you an earful and his thoughts on it s o in Amazon or Google. And absolutely, Dave, it's an important revenue stream for red hat. So if I'm vm ware and you know, maybe for some period of time, you make it a line item, it's part of my l. A. You know, a good thing for customers to look out for is when you're renegotiating your l a toe, understand? If you're going to use this, what is the impact? Because absolutely, you know, from a financial standpoint, you know, Pat Gelsinger on the VM Ware team has been doing a lot of acquisitions. Many of those Dave have been targeted at this space. You know, not to step Geo, but a bit NAMI. And even the pivotal acquisition all fit in this environment. So they've spent billions of dollars. It shouldn't be a net zero revenue to the top line of what VM Ware is doing in the space. >>So that would be an issue from Wall Street's perspective. But at the same time, it's again, they're playing the long game here. Do we have any pricing data at this point? >>So I still have not gotten clear data as to how they're doing pricing now. >>Okay, Um, and others that are in there and in the mix. We talked about Red Hat. Certainly Microsoft is in there with Arc. I've mentioned many times Cisco coming at this from a networking perspective. But who else do you see and then Antos with Google? >>Yeah. And you know, Dave, all the companies we're talking about here, you know, Pat Gelsinger has had to leverage his intel experience to how to balance that line between a partner with everybody but slowly competing against everybody. So, you know, we've spent many hours talking about the VM Ware Amazon relationship. Amazon does not admit the multi cloud a solution yet and does not have a management tool for supporting all of the kubernetes environment. But absolutely Microsoft and Google do. Cisco has strong partnerships with all the cloud environment and is doing that hybrid solution and Dave Justice nothingto expand on a little bit there. If you talk about V sphere, you say, Okay, Visa or seven trolling out Well, how long will it take most of the customer base to roll to this environment? There will be some that absolutely want to take advantage of kubernetes and will go there. But we know that is typically a multi year process to get most of the install base over onto this. And if you extend that out to where VM Ware is putting their solution into cloud environments, there's that tension between, you know, Is there a match actually, between what I have in my data center and what is in the managed environment managed by VM Ware and Amazon, or manage for to support some of the other cloud environment. So the positioning always is that you're going to do VM Ware everywhere, and therefore it's going to be consistent everywhere. Well, the devil's in the details because I have control on what's in my data center, and I might have a little bit less control to some of those managed services that I'm consuming. So absolutely something to keep a close eye on. And not just for VM, where everybody is having these concerns. Even if you talk about the native kubernetes distributions, most of the kubernetes services from the cloud providers are not, you know, immediately on the latest revision of kubernetes, >>right, So Okay, well, let's let's talk about that. Remember when open Stack first came out? It was a Hail Mary against Amazon. Yeah, well, the new Hail Mary and looks like it has more teeth is kubernetes right, because it allows portability and and and of course, you know Amazon doesn't publicly say this, but it's not. That's not good for Amazon. If you're reporting things, applications, moving things around, moving them out of the Amazon cloud, and that makes it easier. Of course, Amazon does support kubernetes right, But you've got >>alternatives. So, David, it's fascinating. So I've talked to many practitioners that have deployed kubernetes and one of the top reasons that they say that why they're using Kubernetes is so they have options with the cloud. When you also ask them what cloud they're running, they're running Amazon. Did they have planned to move off of it? Well, probably not. I had a great customer that I didn't interview with that one of the Cube con shows, and they actually started out with Azure just because it was a little further head with kubernetes and then for the services they wanted. They ended up moving to AWS and Dave. It's not a click a button and you move from one kubernetes to another. You need toe match up and say, Okay, here's the five or six services I'm using. What are the equivalent? What changes do I need to make? Multi cloud is not simple. Today, I mentioned Hashi Corp is one of those companies that help people across these environments. If you have haji solution and you're managing across multiple clouds, you look in the code and you understand that there's a lot of difference between those different clouds, and they simplify that. But don't eliminate it. Just it is not. There is not a way today. This is not a utility when you talk about the public cloud. So you know Kubernetes absolutely is existentially a little bit of a threat to Amazon but Amazon still going strong in that space. And you know that the majority of customers that have deployed kubernetes in the public cloud are doing it on Amazon just because of their position in the marketplace and what they're. >>So let's double click on that. So Jassy, an exclusive interview with John Furrier before last year's re invent, said, Look, we understand there's a lot of reasons why people might choose multiple clouds, you know, go through them in a developer preference. And I think I think, you know, people want o optionality and reduce lock in potentially. But I've always said, by the way, just as an aside, that that the risk of lock in it is far down on the list relative to business value, people will choose business value over over, you know, no lock in every time. About 15% of the customers you might not agree. Nonetheless, Jassy claimed that typically when you get into a multiple cloud environment, he didn't use the term multi cloud that it's it's not a 50 50. It's a premier primary cloud supplier. So might be 70 30 or 80 20 or even 90 10. But it's really that kind of, you know, imbalance. First of all, do you see that? And then what does that mean for how they approach of this space? Multi cloud and in particular. >>So I'm sorry. You're asking how Amazon should approach the space. And you've said that I don't think they'll >>eventually enter this market place. >>Yeah, you know, absolutely, Dave. You know, first of all, in general, yes, I do agree. It is not. There are certain financial companies that, you know, have always chosen two of everything. Because for regulation and you know certain we need to protect ourselves. We're gonna have to suppliers. We're going to keep them as even as possible. But that is a corner case. Most customers I have a primary cloud. That's what I'm doing. That what I t tries to get everybody on and you need to have Is there a reason why you want to use a secondary or tertiary cloud because there's a service that they need. Of course, Google. You often run it. It's like, Oh, well, there's certain data services that they're doing well And, of course, the business productivity solutions that Microsoft's doing where the relationship with Oracle that are driving people towards Microsoft. But just as we saw Amazon soften on their hybrid solutions, we spent a lot of time at re invent talking about all the various hybrid solutions. Um, since their customers are going to have multiple clouds on and even you take most of their customers that have M and a involved you buy another company, they might be using another cloud. As Microsoft's position in the marketplace has grown, you would expect that Amazon would have not just migration services but management services to match what customers need, especially in this kubernetes environment, seems that it seems a natural fit for them. It's possible they might just leverage, you know, partnerships with red hat VM ware, you know, in some of the other players for the time being. But if the market gets big enough and customers are asking for it, that's usually when Amazon response >>So let's let's wrap with what this means to the customer. And I've said that last decade really multi cloud was a symptom of multi vendor and not so much of the strategy that's changing. You know, clearly, jokes CIOs are being called in to clean up the crime scene on do you know, put in edicts corporate edicts around security and governance and compliance and so forth. So it started to become a complicated situation for a lot of companies. We've said that multi cloud is gonna it's gonna be they're going. People are going to put the right war load and the right cloud, etcetera, and this advantages to certain clouds. But what should customers be thinking specifically as it relates to v. Sphere seven? >>Yes. So, Dave, the biggest thing I would say that people need to look at it is that understanding in your organization that that boundary and line between infrastructure and application people have often looked at you looked at the ascendancy of VM Ware, Andi V. M's and then what's happening with cloud and containers. And we think of it from an infrastructure standpoint that I'm just changing the underlying pieces. This is where it lives and where I put things. But the really important thing is it's about my data and my applications, Dave. So if I'm moving an application to a new environment, how do I take advantage of it? You know, we don't just move it to a new environment and run it the same way we were doing it. I need to take advantage of those new environments. Kubernetes is involved in infrastructure, but the real piece is how I have my application, my developers, my app. Dev's working on this environment and therefore it might be that if VM Ware's the right environment, I'm doing a lot of it that the development team says, Hey, I need you to give me a pool and provisioned this for me and I can have my sandbox where I can move really fast. But VM Ware helped initially customers when they went from physical to virtual, move faster. From an infrastructure standpoint, what it needs to do to really enable this environment is help me move faster on the application side. And that's a big gap from VM. Ware's history is where the pivotal people and hefty O people and bit NAMI and all the new people are helping along to help that whole cloud native team. But that is a big shift from customers. So for this to be successful, it's not just, oh, the virtualization admin. He upgraded to the new thing. He made some changes and said, Okay, hey, I can give you a kubernetes cluster when you need it. It's really understanding what's going to happen on the application side in a lot of that is going to be very similar to what you're doing in cloud environments. And I think this is Dave often where your customers, they say, Oh, well, I did that cloud and it was too expensive and it was too hard, and I repatriated. Everything else is, well, you probably didn't plan properly and you didn't understand what you're getting yourself into. And you jumped into the deep end of the pool and oh, wait, I forgot how to learn how to swim. So you know, that is where we are. You know, Dave, you know the technology parts. Always the easiest piece. It's getting all of the organizational and political things sorted out. And you know the developer we know how important that is, we're seeing. It's great to see VM Ware pushing faster in this environment. Kudos to them for how fast they moved. Project Pacific to G. A. That is really impressive to see and can't wait to hear the customers roll out because if this is successful, we should be hearing great transformation stories from customers as to how this is enabling their business, enabling them to move faster on. You know, that has been what, one of the favorite stories that I've been telling with customers on the Cube last couple of years. >>The vast majority of VM Ware's business, of course, is on print, and essentially they're doing here is enabling developers in their customer base and the half a 1,000,000 customers to really develop in a cloud native manner. The question is, you know, from a ah, from a cultural standpoint, is that actually gonna happen? Or the developers gonna reject the organ and say, No, I want to develop in AWS or Microsoft in the cloud. I think VM Ware would say, We're trying to embrace no matter where they want to develop, but they're still going to be. That's interesting organizational tension or developer attention in terms of what their primary choices is. They're not. >>Yeah, Dave, Absolutely. We've been saying for years. That cloud is not a location. It is an operating model. So this is helping to enable that operating model more in the data center. There's still questions and concerns, of course around, you know, consumption on demand versus you know, whether whether you've bought the entire thing as more and more services become available in the public cloud, are those actually enabled to be able to be used, you know, in my data center hosted environment. So you know, this story is not completed, but we're definitely ready. I believe we're saying it's the multi clouds Chapter three of what? We've been watching >>you and you're seeing a major tam expansion yet again from VM Ware that started with the NSX. And then, of course, went in tow networking and storage. And now they've got a cloud security division. We're talking about the the cloud native capabilities here and and on and on, it goes to thanks for helping us break this VC seven announcement down and good job fixed. All right. And thank you for watching everybody. This is Dave Volante for stew Minimum. We'll see you next time on the Cube. >>Yeah,

>> live from San Francisco celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019 brought to you by IBM Wear and its ecosystem partners. >> Welcome back to San Francisco. We continue our coverage here. Live on the Cube. 10th year John of covering Veum World This is 29 teens version John for John Wall's Got to have inside the Moscone Center. We're joined now by Varun Chabrol It was the vice president of marketing at Delhi M. C. Good to see you today. >> Thanks for having me. >> How's your week been? So far? >> It's been amazing. How can you don't get excited? All the innovation we're seeing this week >> we'll hear about some big announcements. Do you guys have made? And Moon Young Man Azzedine, who is the vice president of product marketing that for cloud security and works based solutions at Veum wear when you're good to see you. >> Good to see you again. You, By >> the way, you might be the busiest guy here. Yesterday, when you came into the set, you were coming in. Just spoken to 1300 people in a standing room only session You coming out? 500 folks, How many sessions have you done? The seven. So >> you don't count the the one on one with the analyst. And, uh, you know, the customers and partners and press. And tomorrow actually host ah 140 press media analyst on campus in Palo Alto from Asia Pacific because they float all the way from Asia >> plus 140. Yeah, it's a piece of cake. >> Yeah, hose them from 10 to 4. So, I mean, >> you're always smiling >> knowing that this is a pretty wide audience to whom you've been speaking. But just generally, what are you if there's a common thread at all about the kinds of questions that people are coming to you with, or or the concerns or maybe just the things they want to talk about being inspired. But what they're hearing here at the show, >> Okay. Now, according to two aspects of it, one obviously from analysts themselves, you know, they are actually have been very complimentary about the way we've taken our approach. I'm not sure if you could have paid attention. In the last couple of years, we've been talking especially the cloud side, the narrative, to be very much about use cases, solving problems. You know the key? No, we talked about hate my grade modernize. It wasn't about Hey, I've got the next big product here with all these features and capabilities. You do this and that. So we're gonna shifted out narrative. And it was very, you know, the the analyst across the boat. You know, we've been seeing an appreciative of the fact that you actually changing a narrative to be re compelling and we're gonna reflected. And we have some things here like Cloud City, where it's not a standard demo boot. It's a it's ah, Customers walk in and they touch and feel and see which we did it, Adele technology will, too. It's like, What's your business? Probably going through these applications. I'm sitting. I don't know if I should be modernizing them or should be migrating into Amazon. A ridge or so. So you know that narrative the analysts are appreciative off, and that reflects into the customer conversations I've been having in the briefings, like one on one with customers. They're really kind of lost us. D'oh! Hey, I've I'm working in this environment. There's a lot of pressure for me. Thio modernize my applications or go adopt my cloud. First strategy is where do I start? Where do I go? It's like, you know, there's a big pressure, so they just want clarity. I think in the end, everything we're gonna we're doing in our study that comes out obviously the buzzword for this weird world. It stanza, right? And, you know, >> we've won the product announcements was >> actually Brandon can Oh, yeah. Branding announcement, to be honest is yeah, because we're trying to bring together, as you know, in Tansy has landed in Bill Run Manage billed as in you know how our intent to acquire Pivotal Already acquired Big Tommy. How all our different acquisitions with different brand names are coming together to establish our bills portfolio again. The sphere. Everybody knows the sphere Project Pacific P ks. All of those create a good run time, environment and manageability like Adi manage with assets from ve Franta gain morbid Nami and you know it. So this multiple brands that are coming into this package off Iran. So we had a creative tan Xue too, you know, put forward statement together that yes is going to be 78 different brands coming into this, but going forward to stand. >> So so that's a great strategy on De Liam Seaside on Del Technology. Michael Dell was in here and I asked him. I said he could have been number one in everything you could. Let's talk about I'm number one in servers again. You kind of get on HP, little baby. But those air peace parts now. So we've got the cloud game. It's bringing despair it at parts together kind and making it coherent from a positioning standpoint and understandable and deployable. So you guys are going down there. That's your cloud strategy. Take a minute to explain that. >> Yeah, absolutely, John. So So what? What we've been doing. We announced this at Del Technologies will this year. But, you know, in the cloud infrastructure space, we're working very closely with the anywhere too tightly integrate our hardware solutions with their their cloud software. And we think that by combining these two in a tightly integrated joined engineer, jointly engineered solutions coupled with the service, is that you know, both of'em were and l e m c bring the customers we think we have. We're giving customers are very consistent experience both with their own premises, infrastructure with public cloud as well as with the edge cloud. And that's really what we're trying to do. That's what we've been building upon and uniting the announcements this week. You know, just just hopefully show customers that the sky's the limit, whether it's not just your infrastructure management. Also app development. Managing your APS both traditional and and cloud native. It's all here for And >> what's the big takeaway free from your standpoint that you'd like people to know about what's going on? Adele the emcee for the VM. Where relation. What's the big top item? >> Yeah, there's there's there's just so much good Doctor Wait forever drank the town about. If someone rises >> way, only have two hours >> time work. The most important thing that people should should know about it, >> you know, both deli M. C and V. M. R. I think, are very, very customer driven companies that we respond to customer feedback and we try to respond to them very fast. That's been true to our respective lifetimes and what we've done in the so that I think there's two broad areas of collaboration. One is in the cloud space, which is all about, you know, making sure that the the innovation that GM is bringing the market, we're providing that in a toy tightly integrated infrastructure solution. Right. So we announced from a deli in seaside support for Vienna, where p ks being deployed automatically on Vieques trail using VCF return. Our customers can you know, a lot of teams were telling us we have our developers and turning developers banging slash knocking on the door, saying we need to build a cloud. Native applications. You need to give us an environment that we can use. And you know, if if all righty, if these IittIe teams don't turn around and give them something relatively quickly Well, guess what? The developers will go somewhere else, right? Yeah, exactly. So And if you look at the kubernetes environment today, if you really look look at what the work that's required to set up kubernetes and ready infrastructure. So a lot of scripting a lot of manual, you know, work command line interface is testing stuff. And what what? V m r p k s does. And you know what times you will do as well is really makes it easy when we've taken that with the magic of the American Foundation sitting on top of the exhale to make it super easy for our customers to be able to deploy kubernetes ready infrastructure and then have it be ready for scale, right? And then the important thing here also is this is the same infrastructure of the expelling bcf that our customers are using for traditional applications as well, right? Trying to reduce that complexity. Give them the one platform. So this cloud, you know, we had we were doing the same integration on just with R A C I platform, but also with our best to breach storage or we're not working with the C f. And then we're also making investments on data protection like it's so important to be able to manage your data in this multi cloud world. We have applications sitting everywhere, data. We all know that it is a crown jewel. So >> it's really a king validating from the Vienna a point of view. How that works right is is about applications is about the infrastructure, and it's about the operation and it really kind of together as we talk about Han Xue p. K s is giving our customers that Chuy's off. You pick Cuban eighties, you know, environments, application choice. >> Um, >> it took us. Actually, we didn't We didn't arrive it in that order. Wait. Did it. In the outer off Infrastructure Plot Foundation is a critical piece of the joint engineering. But being aware and the Della Bella Technologies is really from aviary perspective. It took Locke Foundation, and that's the stack that runs in every public cloud. So, you know AWS as your G C P 4000 plus, you know, cloud provider partners. But Flat Foundation is a platform that was validated on. They'll take hardware and you know, that's the package. But now, as you see, we're lighting that it's same infrastructure up for traditional and culminated applications. >> I think the app sides important to point out, because if you could ve m wears heritage, you look at Dale's heritage. You had abs that ran on PCs absent, ran on servers, client server. And if you look at the fertilization that wasn't under the covers, apt an innovation that didn't require code changes. So that's the DNA that you guys have. Now, when you think about like cloud to point out which we've been riffing on that concept that's basically enterprise cloud mean donut. Hybrid cloud applications are gonna drive. The value on our premises is that they're going to be customer requirements that traditionally wouldn't have fit in the product. Marketing, management, featureless customs. Gonna define what they want. They'll build it, and then they'll dictate to the infrastructure to make it run. What? We can't do that yet. It'll be, Yes, we cannot be enabled to be dynamics. This is a a new cloud. 2.0, feature. This changes the complete game on suppliers >> completely agree. You know to your point, because, you know, you bring it thio back toward civilization. We've been going higher up the stack on So Day zero virtualization infrastructure will virtual eyes. So the line off abstraction has just been climbing from hardware retort realization next to like, you know, Pat platform of the service, and you kind of were working up our way down infrastructure. Now that base infrastructure platform looks like plants. Right? >> And there were times out a little bit over here. On the upside, you meet in the middle of >> it in the middle >> that is Hello, >> absolutely so ap and at middle wears shrinking down this way. Infrastructures. You know that the cloud incriminating stride in the middle to say, Well, that's a bit of, you know, infrastructure is a Kodak and pull. He's a bit of a AP AP eyes I can can I draw from And that's kind of nice future middleware. But our dad, I >> mean, I think applications air in charge, right? I mean, that's not sure That's the dynamic. That's the way it should be. But it never was that way before is basically the infrastructure was your gating factor. The network exact cloud two points Network security data. Yes, Dev Ops. A true Dev Ops Devane, Ops, Infrastructures Code. >> The only point I wanted to add is the reason the emphasis on abscess change acts in the past. Used to be a business support system after today is business. >> Yeah, I mean, it's >> really or you're you're gonna live or die based on the digital services you provide your customers. The other thing I was going to say about cloud 2.0, is that it's also becoming increasingly clear when we Dr customers that, um, customers are realizing Cloud is not a place right. There was this kind of cloud. One point it was okay. Big honking data centers, hyper skaters will be found now is that customers have gone through that process of and there's a lot more maturity in terms of understanding. What is good, better running on premises. What is what's better running in public Cloud? There's a place for both of them and that, um, and the cloud is actually the automation, the service delivery. It's Maurin operation and a way of being almost than a place. >> And what is it? Well, what does it do for you all? Then, in terms of challenge, especially at your teams, because you talk about all this customization, you're allowing the application to almost drive. You know, you're changing places in terms of who's the power of the relationship? Yes. Oh, me, yeah, How what? What does that do for you? Oh, in terms of how you approach that, how you change of mindset and how you change what you deliver? >> I think John, it's the way I think about it is that both daily emcee in Vienna, or any technology provider that's worth their salt is in the business of building platforms. Right? And platforms are essentially extensible. They're really they really provide a foundation that other people can innovate on top of it. And that's how I think you handled the customers issue. If one thing I think we can all agree on is that I t has always taught us there's no one size fits. All right? Right. So I think providing choice along every single dimension is super important for our >> customers. Yeah, I think that platform thing is a huge point. And I was gonna ask that question before John got jumped in because one of the things that you just brought up was platform is you guys have to build an enabling platform. One as suppliers. Okay, The successful cloud to point out cos are ones that are innovating in weird areas. Monitoring, for instance, they who will have thought that monitoring now observe ability would be such a massive, lucrative sector four. I pose M and A Why? Because it's data. It's instrumentation. This is operating system kind of thinking here is like network. So thinking like a platform on the supplier size one, the customers got to start thinking like a platform because their stakeholders air their internal developers or a P I shipping to suppliers. This is new for enterprises. This is news requires full hybrid capability. This requires date at the center of the value proposition. >> That's again the biggest value is business and I tr coming together on the area of applications and data. Yeah, that's starting up giving because the successful businesses are the ones who leveraged. Those guys have failed in the future, or the ones who don't pay attention to how critical applications are to the business logic and how critical data is to be able to mine and get the behavioral analytics to get ahead. And >> now the challenge in all this. But I'm learning and covering some of the public sector activity from the C I. A contract Jedi with Amazon to we had Raytheon Her here earlier is another customer example with another client is that procurement? And how they do business is not just a technical thing. There's like all this old legacy, things like, How do you procure technology, who you hire her and we hire developers? We build our own stack, so there's a lot of things going on. >> Yes, and you know, it's really interesting on the even on the procurement front, how our customers experience with Cloud has changed expectations, right, And that's really what we're doing with the McLaren DMC is what customers told us is, Hey, I love the agility of the cloud portal based access. Easy procurement. I love just being able to click a button and not have to navigate all this complexity. I need that for my own premises infrastructure. Imagine FRA structure. And that's, you know, in an example, while all of these dynamics are really all converging, >> well, if you can create abstraction, layer on a level of complexity and make things easy, simple and affordable, that's good business. Model >> one of our customers without taking the name right. The massive retailer you know they're spinning up, um, the retail outlets like crazy. They measure success in This was one truck roll, so they wanna have the entire infrastructure come into stand up one of the retail outlets in one truck roll. When everything comes in one button push that everything gets in a provision and up together. >> So that means I gotta have full software instrumentation automation Got intelligence. This is kind of where cloud 2.0, will lead us all >> likely. And that's expectation now that they go so fast and deploying this one Truck roll Hardware's there. Switch it on from the cloud it stood up and they're in operation 24 hours. >> Well, guys, we're going to get you on our power panels in our Palace of studio on this topic cloudy. But it's gonna be very aggressive and controversial topic because it's going to challenge the status quo. And that's really what this we're talking about >> that's in our DNA. >> And the good news is that that's more time with John. >> So as we before, we say so long, we've talked about clients. We talked about the folks you bet here. We talked about the presentation on this thing and what they're all getting out of it. What are you getting out of this? I mean, what are your takeaways? As you had back to your respective work orders, you get first. Okay? >> I think for me the biggest takeaway is just how incredibly vibrant via more user communities. I mean, it is unlike anything else I've seen before and now with the things like Project Pacific. I just feel like it's It's an opportunity for this community to be able to take the skills they have right now and actually go into this brave new world of containers with so much help forces having to do this all by yourself. Which means it's gonna be, you know, if you think about how largest community is, think about how much innovation this will spore in the container space and because of that in the application space and then because of that in business is I mean, this is a It just feels like a tipping point for me >> to me. Sure, I got high fives from every tech geek, you know, when we came out, you know, I also on our technical advisory boats for the company that these are the hot core geeks who were followed and you know us to the, you know, these were the fans and they were like, you know, they always kind of like if you walk out of them and you talk to them and they, uh how did it work? Because they my bar, you have a very high bar. They cut through all your marketing messaging. They go right to the hay. Is there meet in this And the high fives? I got the hajj. I got out. This is like, guys, you're nailing it. That's enough to tell me that a This is, like, 10 years ago. Yeah, that body. It's like you're so busy. I'm still smiling because the energy is I >> can't give you a hug. Give me a high five. Right. Good work, gentlemen. Thanks for the time. Always, he's still smiling to >> get you to a step. >> Good deal. Thanks for being with us. Thank you. Live on the Cube. You're watching our coverage in world 2019. Where? San Francisco. Back with more. Right after this.

>> live from Barcelona, Spain. It's the key covering KubeCon Cloud, Native Con Europe twenty nineteen by Red Hat, the Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to Barcelona, Spain >> were here of the era, and seventy seven hundred people are here for the KubeCon Cloud NativeCon, twenty, nineteen, Off student. My co host for the two days of coverage is Corey Quinn, and joining Me are the two co chairs of this CNC event. Janet Cooper, who is also thie, suffer engineer with Google and having done the wrap up on stage in the keynote this morning, find Lyle's a senior staff engineer with BM where thank you both for joining us, >> Thank you. >> Thanks for having me. >> So let's start. We're celebrating five years of Kubernetes as damn calm laid out this morning. You know, of course, you know came from Google board in over a decade of experience there. So it just helps out the state for us. >> Um, so I started working on communities since before the 1.4 release and then steal a project Montana today. And I feel so proud to see, uh, the progress off this project and its has grown exponentially. And today we have already thirty one thousand contributors and expect it to grow even more if you can. >> All right. So, Brian, you work with some of the original people that helped create who Burnett ease because you came to be and where, by way of the FTO acquisition, seventy seven hundred people here we said it. So it's, you know, just about the size of us feel that we had in Seattle a few months ago Way Expect that San Diego is going to be massive when we get there in the fall. But you know, talk to us is the co chair, you know, What's it mean to, you know, put something like this together? >> Well, so as ah is a long time open source person and seeing you know, all these companies move around for, you know, decades. Now it's nice to be a part of something that I saw from the sidelines for so, so long. I'm actually... it's kind of surreal because I didn't do anything special to get here. I just did what I was doing. And you know, Jan and I just wound up here together, so it's a great feeling, and it's the best part about it is whenever I get off stage and I walked outside and I walked back. It's like a ten minute walk each way. So many people are like, Yeah, you really made my morning And that's that's super special. >> Yeah. I mean, look, you know, we're we're huge fans of open source in general and, you know, communities, especially here. So look, there was no, you know, you both have full time jobs, and you're giving your time to support this. So thank you for what you did. And, you know, we know it takes an army to put together in a community. Some of these people, we're Brian, you know, you got upstate talk about all the various project. There's so many pieces here. We've only have a few minutes. Any kind of major highlights You wanna pull from the keynote? >> So the biggest. Actually, I I've only highlight won the open census open. Tracing merge is great, because not only because it's going to make a better product, but he had two pretty good pieces of software. One from Google, actually, literally both from Google. Ultimately, But they realize that. Hey, we have the same goals. We have similar interfaces. And instead of going through this arms race, what they did is sable. This is what we'LL do. We'LL create a new project and will merge them. That is, you know, that is one of the best things about open source. You know, you want to see this in a lot of places, but people are mature enough to say, Hey, we're going to actually make something bigger and better for everyone. And that was my favorite update. >> Yeah, well, I tell you, and I'm doing my job well, because literally like during the keynote, I reached out to Ben. And Ben and Morgan are going to come on the program to talk about that merging later today. That was interested. >> I've often been accused of having that first language being snark, and I guess in that light, something that I'm not particularly clear on, and this is not the setup for a joke. But one announcement that was made on stage today was that Tiller is no longer included in the current version of Wasn't Helm. Yes, yes, And everyone clapped and applauded, and my immediate response was first off. Wow, if you were the person that wrote Tiller, that probably didn't feel so good given. Everyone was copping and happy about it. But it seems that that was big and transformative and revelatory for a lot of the audience. What is Tiller and why is it perceived as being less than awesome? >> All right, so I will give you a disclaimer, >> please. >> The disclaimer is I do not work on the helm project... Wonderful >> ...so anything that I say should be fact checked. >> Excellent. >> So Well, so here's the big deal. When Tiller, when Helm was introduced, they had this thing called Tiller. And what tiller did was it ran at a basically a cluster wide level to make sure that it could coordinate software being installed and Kubernetes named Spaces or groups how Kubernetes applications are distributed. So what happens is is that that was the best vector for security problems. Basically, you had this root level piece of software running, and people were figuring out ways to get around it. And it was a big security hole. What >> they've done Just a component. It's an attack platform. It >> was one hundred percent. I mean, I remember bit. Nami actually wrote a block post. You know, disclaimer of'em were just bought that bit na me. >> Yes, I insisted It's called Bitten, am I? But we'LL get to that >> another. This's a disclaimer, You know, There Now you know there now my co workers But they wrote they were with very good article about a year and a half ago about just all the attack vectors, but and then also gave us solution around that. Now you don't need that solution. What you get by default. Now something is much more secure. And that's the most important piece. And I think the community really loves Helm, and now they have helm with better defaults. >> So, Janet, a lot of people at the show you talk about, you know, tens of thousands of contributors to it. But that being said, there's still a lot of the world that is just getting started. Part of the key note. And I knew you wrote something running workloads and cover Netease talk a little bit about how we're helping you know, those that aren't yet, you know, on board with you getting into the community ship. >> So I work on the C gaps. So she grabs one of the sub fracture that own is the work wells AP Eyes. That's why I had that. What post? About running for closing covered alleys. So basically, you you're using coronaries clarity, baby eyes to run a different type of application, and we call it were close. So you have stay full state wears or jobs and demons and you have different guys to run those clothes in the communities. And then for those who are just getting started, maybe start with, uh, stay last were close. That's the easiest one. And then for people who are looking Teo, contribute war I. I encouraged you to start with maybe small fixes, maybe take some documents or do some small P R's and you're reputations from there and star from small contributions and then feel all the way up. >> Yeah, so you know, one of one of the things when I look out there, you know, it's a complex ecosystem now, and, you know, there's a lot of pieces in there, you know, you know, trend we see is a lot of customers looking for manage services. A lot of you know, you know, I need opinions to help get me through all of these various pieces. You know what? What do you say to those people? And they're coming in And there's that, you know, paradox of choice When they, you know, come, come looking. You know, all the options out there. >> So I would say, Start with something simple that works. And then you can always ask others for advice for what works, What doesn't work. And you can hear from their success stories or failure stories. And then I think I recently he saw Block post about Some people in the community is collecting a potential failure stories. There is also a talk about humanity's fellow, the stories. So maybe you can go there and learn from the old those mistakes and then how to build a better system from there. >> I'd love that. We have to celebrate those failures that we hopefully can learn from them. Find anything on that, You know, from your viewpoint. >> Eso Actually, it's something I research is developer experience for you. Bernetti. So my communities is this whole big ping. I look on top of it and I'm looking at the outside in howto developers interact with Burnett, ese. And what we're seeing is that there's lots of room for opportunities and Mohr tools outside of the main community space that will help people actually interact with it because that's not really communities. Developers responsibility, you know, so one anything that I think that we're doing now is we're looking and this is something that we're doing and be aware that I can talk about is that we're looking at a P ice we're looking at. We realize that client go, which is the way that you burnett ese talks with sapi eyes, and a lot of people are using out externally were looking at. But what does it actually mean for human to use this and a lot of my work is just really around. Well, that's cool for computers. Now, what if a human has to use it? So what we're finding is that no. And I'm going to talk about this in my keynote tomorrow. You know, we're on this journey, and Kubernetes is not the destination. Coover Netease is the vehicle that is getting us to the destination that we don't even know what it is. So there's lots of spaces that we can look around to improve Kubernetes without even touching Cooper Netease itself, because actually, it's pretty good and it's fairly stable in a lot of cases. But it's hard, and that's the best part. So that's, you know, lots of work for us, the salt >> from my perspective. One of the turning points in Kou Burnett is a success. Story was when it got beyond just Google. Well, folks working on it. For better or worse, Google has a certain step of coding standards, and then you bring it to the real world, where there are people who are, Let's be honest, like me, where my coding standard is. I should try to right some some days, and not everything winds up having the same constraints. Not everything has the same approach. To some extent, it really feels like a tipping point for all of it was when you wind up getting to a position where people are bringing their real world workload that don't look like anything, anyone would be able to write a googol and keep their job. But still having to work with this, there was a wound up being sort of blossoming effect really accelerating the project. Conversely, other large infrastructure projects we need not mention when they had that tipping point in getting more people involved, they sort of imploded on themselves. I'm curious. Do you have any thoughts as to why you Burnett? He started thriving where other projects and failed trying to do the same things. >> I have something you go first. And >> I think the biggest thing about cybernetics is the really strong community and the ecosystem and also communities has the extensive bility for you to build on top of communities. We've seen people building from works, and then the platform is different platforms. Open source platforms on top of you. Burnett is so other people can use on other layers. Hyah. Layers off stacks on top of fraternities. Just use those open source. So, for example, we have the CRD. It's an A P I that allows you to feel your own customized, overnighted style FBI, so they're using some custom for couple databases. You could just create your own carbonated style FBI and call out your database or other stuffs, and then you can combine them into your own platform. And that's very powerful because everywhere. I can just use the same FBI, the Carbonari style idea to manage almost everything and that enables a Teo be able to, you know, on communities being adopted in different industry, such as I o t. A and Lord. >> So actually, this is perfect because the sleaze and so what I was going to say The secret of community is that we don't talk about actually job, Ada says. It's a lot, but it's a communities is a platform for creating platforms. So Kubernetes really is almost built on itself. You can extend Cooper. Netease like communities extends itself with the same semantics that it lets users extended. So Janet was talking about >> becoming the software that is eating the world. Yeah, it >> literally is. So Janet talked about the CRD sees custom resource definitions. It's the same. It's the same mechanism that Kubernetes uses to add new features. So whenever you're using these mechanisms, you're using Kou Burnett. He's basically the Cooper Nate's infrastructure to create. So really, what it is is that this is the tool kit for creating your solutions. What is why I say that Kubernetes is not an end point its its journey. >> So the cloud native system. >> So you know what? Yeah, and I like I like the limits analogy that people talk about. Like Coburn. Eighties is is like clinics. If you think about how Lennox you know little l. Lennox. Yeah. You know, I'm saying little l olynyk sub Let's put together. Yeah, you Burnett. He's like parts of communities would be system. And it's it's all these components come together the creature operating system, and that's the best part about it. >> Okay, so for me, the people that are not the seventy seven hundred that air here give them a little bit of, you know, walk around the show and some of the nooks and crannies that they might not know, like, you know, for myself having been to a number of these like Boy, there were so many half day and full day workshops yesterday there were, like, at least, like fifteen or seventeen or something like that that I saw, You know, obviously there's some of the big keynote. The Expo Hall is sprawling it, you know, I've been toe, you know, fifteen twenty thousand people show here This sex Bohol feels is bustling ahs that one is and well as tons of breakout session. So, you know, give us some of the things that people would have been missing if they didn't come to the show here. >> So just for the record, if you missed the show, you can still watch all the videos online. And then you can also watch the lifestream for keynotes so on. I personally love the applicant the different ways for a customizing covered at ease. So there's Ah, customizing overnight is track. And also there's the apple that applications track and I personally love that. And also I like the color case studies So you can't go to the case studies track to see on different users and users off Cooper, Natty shared. There were war stories, >> Yes, So I think that she will miss. There's a few things that you'll miss if you if you're not here in Barcelona right now, the first thing is that this convention center is huge. It's a ten minute walk from the door to where we're sitting right now, but more seriously, one. The things you'LL miss is that before the conference starts, there are there are a whole bunch of summits, Red had had a summit and fewer people had some. It's yesterday where they talk about things. There's the training sessions, which a lot of cases aren't recorded. And then another thing is that the special interest groups, the cigs. So Cooper ninety six, they all get together and they have faced the face discussions and then generally one from yesterday We're not. We're not recorded. So what you're missing is the people who actually make this big machine turn. They get together face to face and they first of all, they built from a rotary. But they get to discuss items that have require high bit of bandwith that you really can't do over again of issue or email, or even even a slack call like you can actually get this thing solved. And the best thing is watching these people. And then you watch the great ideas that in, you know, three, six months to a year become like, really big thing. So I bet yesterday, so something was discussed. Actually, I know of some things that we discussed yesterday that might fundamentally change how we deal with communities. So that's that is the value of being here and then the third thing is like when you come to a conference like this, where there's almost a thousand people, there's a lot of conversations that happened between, you know, the Expo Hall and the session rooms. And there's, um there's, you know, people are getting jobs here, People are finding new friends and people are learning. And before thing and I'll end with This is that I walk around looking for people who come in on the on the diversity scholarships, and I would not hear their stories if I did not come. So I met two people. I met a young lady from New Zealand who got the scholarship and flew here, you know, and super smart, but is in New Zealand and university, and I get to hear her insights with life. And then I get to share how you could be better in the same thing. I met a gentleman from Zimbabwe yesterday was going to school and take down, and what I hear is that there's so many smart people without opportunities, so if you're looking for opportunities, it's in these halls. There's a lot of people who have either money for you or they have re sources were really doesn't have a job or just you know what? Maybe there's someone you can call whenever you're stuck. So there is a lot of benefit to come into these. If you can get here, >> talent is evenly distributed. Opportunity is not. So I think the diversity scholarship program is one of the most inspirational things I saw mentioned out of a number of inspirational things that >> I know. It's It's my favorite part of communities. You know, I am super lucky that I haven't employees that our employer that can afford to send me here. Then I'm also super lucky that I probably couldn't afford to send myself here if I wanted to. And I do as much as I can to get people >> here. Well, Brian and Janet thank you so much for all you did to put this and sharing it with our community here. I'Ll repeat something that I said in Seattle. Actually, there was a lot of cloud shows out there. But if you're looking for you know, that independent cloud show that you know, lives in this multi hybrid cloud, whatever you wanna call it world you know this is one of the best out there. And the people? Absolutely. If you don't come with networking opportunities, we had into it on earlier, and they talked about how you know, this is the kind of place you come and you find a few people that you could hire to train the hundreds of people inside on all of the latest cloud native pieces. >> Can I say one thing, please? Brian S O, this is This is significant and it's significant for Janet and I. We are in the United States. We are, you know, Janet is a minority and I am a minority. This is the largest open source conference in the world. Siri's This is the largest open source conference in Europe. When we do, when we do, it ended a year. Whenever we do San Diego, it'Ll be the largest open source conference in the world. And look who's running it. You know, my new co chair is also a minority. This is amazing. And I love that. It shows that people who look like us we can come up here and do these things because like you said, opportunity is is, you know, opportunities the hard thing. Talent is everywhere. It's all over the place. And I'm glad we had a chance to do this. >> All right. Well, Brian, Janet, thank you so much for all of that. And Cory and I will be back with more coverage after this brief break. Thank you for watching the cues.

>> from San Francisco. It's the Cube covering the M Wear Radio twenty nineteen. Brought to you by the M >> where >> Hi. Welcome to the Cube. Lisa Martin with John Farrier at the fifteenth annual Veum, Where radio, which is there are anti innovation summit. Pleased to welcome back one of the Cube alumni extraordinaire CEO Being where hot girl singer. Hey, Pat. Good morning. >> Good morning. Great to be with you guys today. Thanks >> so much Right to be here. So this this is the fifteenth radio your internal innovation summit that really has been very influential. NPM wears development over the last fifteen or so years About eighteen hundred engineers here. So each year growing Mohr and Mohr interest, excitement cross collaboration with India More talk to us about how this is really worthy of the CEOs. Time to come here. And with this geek fest, >> well, it is, in many ways, just one of these pieces of the VM wear R and D culture is a research and development innovation off site. And it's something, you know, long preceded me. But when I got here, it's like I'm going to keep doing it. Of course we are. You know this is sort of like the party for the top engineers, right? You know, they get to come geek out, share their best ideas, interact with each other. So it's become one of those unique pieces of our of our development culture and ultimately is, I say, bm where well to do two things right, developed great, breakthrough, innovative, disrupt the products and make our customers successful with those products. So everything that we do sort of centers around those two things. And obviously, if the products are great, we don't have that. We know what to do So to us, keeping that culture of innovation and giving our engineers time to really just geek out, see what each others are doing, challenge each other. It's really pretty special. And yeah, it deserves the CEO's time. >> And you've got You just had your sales president's club without top performers. On the sales side, this is the technical version. It hasn't been that organic piece of the VM were culture, engineering, leadership. But you also have acquisitions, just acquired it. Nami. Yes, you've had a few other you cloud health big time moves relationship with a ws azure. The cloud foundation stuff. How is lending it together? Because you have all this organic innovation. I see cloud management, networking, security outside suffer to find data center is playing out. As you you guys had predicted. How does the acquisitions fit into the culture and the radio? >> Well, you know, part of it is when we talked to many of the engineers about the acquisitions, we say, Hey, we do radio. They're like, huh? All right, this is well, it's this opportunity for us to see what everybody is doing interactive that level and good engineers are almost always part of the decision with respect acquisitions. So they just take to it like, you know, fish and water, right? They just jump in, right, start interacting with their peers. And it is such a, you know, open, diverse pool that all of sudden ideas air being a bounced off each other, homogenize challenged and, you know, people seeing how they can connect with people. So tow us. Many of the acquisitions just find us to be so beneficial to how they come into the company. And they quite appreciate it, you know, just getting back from sales club hate sales leaders >> and he was pretty good. I like this, you >> know, for many of those acquisitions. But the engineers, this is even better for you >> guys aren't just buying stuff up. You guys are very specific in your acquisitions. Cloud Health again is a great example. Scene. No air watch going with further back. Why? Bit, Nami, What was so big and important about it, Nami to acquire them? >> Well, you know, we saw a couple of things. One is that, you know, it's a company. They definitely had this ability, this respect. We're poor with the open source community, you know, and being able to cross between open source and enterprise credibility. That's exactly where I am, where seas and wants to be able to position ourselves so they fit exactly into that space. This idea of being able to bring enterprise packages is the cool open source applications space. And we already had a multiple set of marketplace efforts internally where we saw that we needed that ecosystem play for activities so they just snap so perfectly into the middle of that and very much hybrid will take cloud, uh, aspects to it. And as we do for every one of our acquisitions and I personally meet with every CEO before we do the deal Are they going to fit our culture? And you know, there aren't that many of our acquisitions where I have people saying no, no I'll i'll be the executive sponsor for this one. No, no, no, I will, I will. I will be No, no, no, please. I'll do this one. And you know, of course, the fact that it's in Seville, Spain, right? You know, I think I think if you it was just driven by vacation plans. But it's >> all well, of course, Erica Cube alumni. And we have a whole cube alumni thing going on here. There's no emanate work we're doing here just good people of nice. And so >> you're planing the Cube visit to civilly explain. It's >> like love, Teo. Of course, we have international presents. One of the things I always quote from you is Besides, that hybrid cloud reference years ago was a quote. You said I think twenty, twelve or twenty thirteen feet which year it wass seems like yesterday. You said if you're not out on that next wave your driftwood, so I gotta ask you here at radio you got You got all this organic stuff. It's kind of the wave's coming. Is this what wave is? Are you seeing the end? We're riding right now, because business is great. Um, you're pumping on all cylinders. You've kind of gone through your ten years that through the early days of and you got CEO and you know it. Everything's normal life now and you're on a good run. What waiver? You're going to be surfing on the business side of all this stuff behind you. What's what? When is this all fit in? >> Well, you know, one of the things that I think is so critical for us now and particularly with the, you know, the, um, war cloud on eight of us. Go now with the relationships with Azure and IBM. Alibaba are four thousand BC PP partners. So that's, you know, really starting to take off our BM or Cloud Foundation on premise. We have a big customer saying Okay, I get it right. Don't look down the stack. Look up. Rely on you guys to be the infrastructure. Bring that together for the hybrid infrastructure is a service. And to me You know, part of what I'm looking for for this from the conference is putting all those pieces together because our customers don't want to be doing it. They want us to do it, but we have to make it so consumable, so compelling that just sort of like the sphere. Was it our beginning? They just sort of say, the M where your hybrid cloud, That's what I want, right? And be ableto operationalize at a scale. And if we get that really working well for customers, the management, the automation, the security operations of that boy. Now we do have the opportunity to ride the Cuban eighties wife right into me. It really is. We have to straddle those two over the next several years, >> so make you know, super nice party stand, >> that embracing that next major trend, >> which is up on top of the stack program ability. >> Yeah. You know, when the aside describe Coburn at ease and containers, it's like Java was twenty years ago. You know, what was the last major software abstraction that the industry agreed upon? Jonah, It's almost exactly twenty years ago, and it defined middleware abstraction for the last twenty years. Containers Cooper, Netease the next middleware abstraction. And we see Cooper. Nate is becoming the next native a P I that thie VM where infrastructure, STD see will support and will deliver. And we're going to make containers and cue bernetti so seamless with regard to the core bm infrastructure that a customer never needs to decide. >> What impact will this have? I mean, I see you've been involved many ways talked about the Pentium in the Intel side of your career, I'll see and and what that enabled in terms of inflection, point and growth and creation of value. Where do you see this Cooper Netease Abstraction. If this is going to be one of those inflection points as you as you point out, how do you envision the impact to the industry? What's gonna happen? >> We see that Cuban eighties layer impacting down as well as impacting up, and that's why we see it. It's so critical to get it right. You know, it becomes the consumption a p I infrastructure, and we've talked about, you know, infrastructure is code or, you know, a P. I ittle dismiss a displace open stack. As an AP, I becomes the middle, where a pea eye of choice, but also that defines the middle where abstraction of choice. So all of your Web spheres, Web logics, Java communities, they're going to get displaced as well as they are re factored into this automated containerized, the scale out world. That's exactly where we're sitting. And that's another piece of the bit Nami acquisition that we just announce because you know, being ableto package containerized, open source applications packages exactly fits into that strategy as well. And if we do those two things, I think VM where is going to be extraordinarily well positioned for decades to come way past me? >> So let's talk about customers. Here we are at radio twenty, nineteen, fifteen years I mentioned you guys, This is a really competitive event. Engineers want to be here. You probably had well over a thousand projects. Submissions. How do customers one benefit from the innovations that are discussed here at radio, but also how to customers influence some of the projects of the exciting things that engineers want to put together? >> Well, one of the things that we really enjoy about the whole BM where R D community is you know engineers are leaving with customers all the time. We push him out into those places, you know, we selectively bring customers in and have them in Iraq. Tear a radio. We have other mechanisms, like flings, right? Yeah. These open source lightweight things that customers could be giving us code. We could be giving them code. We you regularly, you know, bring them into our campus for, you know, their participation and different advance programs. So it really is a very constant, ongoing and somewhat end and dialogue that we're having weather. That's from an early product concept that we might be seeing for the first time here at Radio Teo Act The part, this patient and beta activities before we roll them out broadly. So it really is having them participate in the end, the end roll of innovation. And sometimes Hey, it sounds like a good idea. And it sort of sucked right when we tried to do it. Other times they're like, Oh, wow, some of these things, really. I've taken off and gain legs while beyond what we would have dreamed of. >> What have you seen that this year's event? Project Wise featured project. Why's that really kind of caught your attention, Like you. That's a really good idea. >> Well, I must admit, I just landed last night, So today is my first day at radios. So I just got back from our sales club, as John mentioned earlier. So I think I'm gonna have to take a buy on that question here because I got to go do my homework here. >> We'LL ask the questions. I have attracted talent, engineering, talent That's also the best of the best elite forces. This is a challenge in the streets of retain talent on engineers. Love to work on a hard problem. I gotta ask you what, Some of the hard problems at the end where is trying to tackle that would attract the elite engineering forces to the company. Because again, you're talking about something really big is going on with software. What are some of the big problems? >> Yeah, well, a couple of them that, you know, I'm pretty focused on for our team, and one is we said, you know, we said it's a software defined data center. Right? Going forward. It's the self driving data center. How do we bring so much telemetry? and automation that we truly are running the data center on customers behalf. And if I, you know, build on the Del Technologies World announcement of'em were cloud on Delhi emcee. You know, we're now managing their on premise data center from our cloud. You know what? If we can put more machine learning a I into the middle of that, it's not just that I wantto do it instead of them. I want to do it dramatically better than they ever could write. Using the greatest algorithms telemetry, learning, etcetera that the infrastructure becomes more reliable, right, it becomes higher performance. It becomes increasingly predicted right of its behavior and adjusting to those things. So the self driving data center's pretty high on the list for us. You know this idea then of a true multi cloud operational plane. We're customers. Just say, Here's there's my working. Would you figure out where to run it here? My policies. Here's the work will take care of it for me today. I was running it on this cloud the afternoon I brought it back on promise, because you it >> sounds easy, >> Cassidy. Right? Wow, If you could do that, its scale But then you say, boy, You know, if I move it around, where does the day to reside? Right, You know, have I met my policies and compliance requirements? So this a multi cloud operational plane is a >> big problem that you're attracting talent Is that distract complexity away and making it easy? >> Yeah, right, R, that's what we do. It's hard. I know. You know some >> of the cool things, you know, the are blockchain All right, you know, also breaking through reside. Describe blockchain. It's like the public private key encryption breakthroughs of forty years ago. But they're still very raw, right? Their performances crappy. You know, they don't scale very well. You have all sorts of issues associated with audit ability and repute, ability of those mechanisms. So those are some of the new problems and then also attacking entirely new new segments like NFI, right? Hey, we're going to build a five g network. That's not reliant on hard work, right? >> Well, when you're out of the quiet here, we're going to come to your office, will go deeper, dive on the business and some of the cool tech stuff, >> and we're just coming up on the M world in a couple of months. I think this will be the cubes tenth time there and any little teasers that you could give us about the world twenty nineteen. >> Well, we certainly hope that, you know, we're able to bring a lot of these club messages together right and have sort of, you know, connected all the dots. Att VM world This year's >> state When you heard it here on the Q first, some exciting announcements coming from BM, where in just a few months at being World twenty nineteen. Pak Gil Senior Seo Thank you so much for joining Jon and me at Radio twenty nineteen. As a pleasure. Always thank you so much. We want to thank you for watching for John Ferrier. I'm Lisa Martin. You're watching the Cube from Vienna, where Radio twenty nineteen and San Francisco. Thanks for watching