>> Narrator: From around the globe, it's theCUBE. With coverage of KubeCon and CloudNativeCon North America 2020, virtual. Brought to you by Red Hat, the Cloud Native Computing Foundation and ecosystem partners. >> Hi, I'm Joep Piscaer. Welcome to theCUBEs coverage of KubeCon, CloudNativeCon 2020. So I'm joined today by Matt Kixmoeller, he's VP of strategy at Pure Storage, as well as Michael Ferranti, he's the senior director of product marketing at Portworx now acquired by Pure Storage. Fellows, welcome to the show. >> Thanks here. >> I want to start out with you know , how about the lay of the land of storage in the Cloud Native space in the Kubernetes space. You know, what's hard? what's happening? What are the trends that you see going on? Matt, if you could shed some light on that for me? >> Yeah, I think you know, from a Pure point of view obviously we just told customers will they maturing their comprehensive deployments and particularly leaning towards persistant, you know applications and so you know we noticed within our customer base that there was quite a lot of deployments of a Portworx on Pure Storage. And that inspired us to start talking to one another you know, almost six plus months ago that eventually ended in us bringing the two companies together. So it's been a great journey from the Pure point of view, bringing Portworx into the Pure family. And, you know, we're working through now with our joint customers, integration strategies and how to really broaden the use of the technology. So that's quite exciting times for us. >> And of course, it's good to hear that the match goes beyond just the marketing color, like the brand color. >> Absolutely. Yeah. I mean, the fact that both companies were orange and you know, their logo looked like kind of a folded up version of ours, just started things off on the right foot >> A match made in heaven, right? So I want to talk a little bit about you know, the acquisition, what's happened there and especially, you know looking at Portworx as a company, and as a product set, it's fairly popular in the cloud community. A lot of traction with customers. So I want to zoom in on the acquisition itself and kind of the roadmap going forward merging the two companies and adding Portworx to that Pure portfolio. Matt, if you could shed some light on that as well. >> Yeah. Why don't I start and then Michael can jump in as well? So, you know, we at Pure had been really working for years now to outfit our all flash storage arrays for the container use case and shipped a piece of software that we call PSO. That was really a super CSI driver that allowed us to do intelligent placement of you know, persistent volumes on Pure arrays. But the more time we spent in the market, the more we just started to engage with customers and realized that there were a whole number of use cases that didn't really want a hardware based solution, you know. They either wanted to run completely in the cloud, hybrid between on-prem and cloud and leverage bare metal hardware. And so you know, we came to the conclusion that you know, first off, although positioning arrays for the market was the right thing to do, we wouldn't really be able to serve the broader needs restoratively for containers, if you did that. And then, you know, the second thing I think was that we heard from customers that they wanted a much richer data management stack. You know, it's not just about providing the business versus the volume for the container, but you know, all the capabilities around snapshoting and replication and mobilization and mobility between on-prem and cloud were necessary. And so, you know, Portworx we bought to bear not only a software based solution into our portfolio, but really that full data management stack platform in addition to just storage. And so as we look to integrate our product lines you know, we're looking to deliver a consistent experience for data management, for Kubernetes whatever infrastructure customer would like to, whether they want to run on all flash arrays, white box servers, bare metal, VMs or on cloud storage as well. You know, all of that can have a consistent experience with the Portworx platform. >> Yeah, and because you know, data management especially in this world of containers is you know, it's a little more difficult it's definitely more fragmented across you know, multiple clouds, multiple cloud vendors, multiple cloud services, multiple instances of a service. So the fragmentation has you know, given IT departments quite the headache in operationally managing all that. So Michael you know, what's kind of the use case for Portworx in this fragmented cloud storage space. >> Yeah. It's a great question. You know, the used cases are many and varied, you know to put it in a little bit of historical perspective you know, I've been attending coupons either (indistinct) for about five or six years now, kind of losing count. And we really started seeing Kubernetes as kind of an agile way to run CI/CD environments and other test dev environments. And there were just a handful of customers that were really running production workloads at the very, very beginning. If you fast forward to today, Kubernetes is being used to tackle some of the biggest central board level problems that enterprises face, because they need that scale and they need that agility. So you know, COVID's accelerated that. So we see customers say in the retail space, who are having to cope with a massive increase in traffic on their website. People searching for kind of you know, the products that they can't find anywhere else. Are they available? Can I buy them online? And so they're re-architecting those web services to use often open source databases in this case Elasticsearch, in order to create a great user experiences. And they're managing that across clouds and across environments using Kubernetes. Another customer that I would say kind of a very different use case but also one that matches that scale would be Esri which unfortunately the circumstances of becoming a household name are a lot of the covert tracking ArcGIS system to keep track of, tracing and outbreaks. They're running that service in the cloud using Portworx. And again, it's all about how do we reliably and agilely deploy applications that are always available and create that experience that our customers need. And so we see kind of you know, financial services doing similar things healthcare, pharmaceutical, doing similar things. Again, the theme is it's the biggest business problems that we're using now, not just the kind of the low hanging fruit as we used to talk about. >> Yeah exactly. Because you know storage, is it a lot of the times it's kind of a boiler plate functionality you know, it's there it works. And if it doesn't, you know, the problem with storage in a cloud data space is that fragmentation right? Is that enormous you know, on the one hand that you don't have a scale on the other hand, the tons of different services that can hold data that need protecting as well as data management. So I want to zoom in on a recent development in the Portworx portfolio where the PX backup product has spun out its own little product. You know, what's the strategy there, Michael? >> Yeah, so I think, you know fundamentally data protection needs to change in a Kubernetes context. The way in which we protected applications in the past was very closely related to the way in which we protected servers. Because we would run one app per server. So if we protected the server our application was protected. Kubernetes breaks that model now an individual application is made up of dozens or hundreds of components that are spread across multiple servers. And you have container images, you have configuration I mean you have data, and it's very difficult for any one person to understand where any of that is in the cluster at any given moment. And so you need to leverage automation and the ability for Kubernetes to understand where a particular set of components is deployed and use that Kubernetes native functionality to take what we call application aware backups. So what PX backup provides is data protection engineered from the ground up for this new application delivery model that we see within Kubernetes. So unlike traditional backup and recovery solutions that were very machine focused, we can allow a team to back up a single application within their Kubernetes cluster, all of the applications in a namespace or the entire cluster all at once, and do so in a self-service manner where integrated with your corporate identity systems individuals can be responsible for protecting their own applications. So we marry kind of a couple of really important concepts. One is kind of the application specific nature of Kubernetes the self service desire of DevOps teams, as well as with the page you go model, where you can have this flexible consumption model, where as you grow, you can pay more. You don't have to do an upfront payment in order to protect your Kubernetes applications. >> Yeah. I think one key thing that Michael hit on was just how this obligation is designed to fit like a glove with the Kubernetes admin. I see a lot of parallels to what happened over a decade ago in the VMware space when you know, VMware came about they needed to be backed up differently. And a little company called Veem built a tool that was purpose-built for it. And it just had a really warm embrace by the VMware community because it really felt like it was built for them, not some legacy enterprise backup application that was forced to fit into this new use case. And you know, we think that the opportunity is very similar on Kubernetes backup and perhaps the difference of the environment is even more profound than on the VMware side where you know, the Kubernetes admin really wants something that fits in their operational model, deploys within the cluster itself, backs up to object storage. Is just perfect purpose-built for this use case. And so we see a huge opportunity for that, and we believe that for a lot of customers, this might be the easiest place for them to start trying to Portworx portfolio. You know, you've got an existing competitors cluster download this, give it a shot, it'll work on any instructions you've got going with Kubernetes today. >> And especially because, you know, looking at the kind of breakdown of Kubernetes in a way data is, you know, infrastructure is provisioned. Data is placing in cloud services. It's no longer the cluster admin necessarily, that gets to decide where data goes, what application has access to it, you know, that's in the hands of the developers. And that's a pretty big shift you know, it used to be the VI admin the virtualization admin that did that, had control over where data was living, where data was accessed out, how it was accessed. But now we see developers kind of taking control over their infrastructure resources. They get to decide where it runs, how it runs what services to use, what applications to tie it into. So I'm curious, you know, how our Portworx and PX backup kind of help the developer stay in control and still have that freedom of choice. >> Yeah, we think of it in terms of data services. So I have a database and I needed to be highly available. I needed to be encrypted, backed up. I might need a DR. An off site DR schedule. And with Portworx, you can think about adding these services HA, security, backup, capacity management as really just I want to check a box and now I have this service available. My database is now highly available. It's backed up, it's encrypted. I can migrate it. I can attach a backup schedule to it. So 'cause within a Kubernetes cluster some apps are going to need that entire menu of services. And some apps might not need any of those services because we're only in Testa phage, everything is multiplexed into a single cluster. And so being able to turn off and turn on these various data services is how we empower a developer, a DevOps team to take an application all the way from test dev, into production, without having to really change anything about their Kubernetes deployments besides, you know, a flag within their YAML file. It makes it really, really easy to get the performance and the security and the availability that we were used to with VM based applications via that admin now within Kubernetes. >> So Matt, I want to spend the last couple of minutes talking about the bigger picture, right? We've talked about Portworx, PX backup. I want to take a look at the broader storage picture of cloud native and kind of look at the Pure angle on the trends on what you see happening in this space. >> Yeah absolutely. You know, a couple of high-level things I would, you know, kind of talk about, you know, the first buzz that I think, you know hybrid cloud deployments are the de facto now. And so when people are picking storage, whether they be you know, a storage for a traditional database application or next gen application, cloud native application, the thought from the beginning is how do I architect for hybrid? And so you know, within the Pure portfolio, we've really thought about how we build solutions that work with cloud native apps like Portworx, but also traditional applications. And our cloud block store allows you know, those to be mobilized to the cloud without, with minimal re-architecture. Another big trend that we see is the growth of object storage. And, you know if you look at the first generation of object storage, object storage is what? 15 plus years old and many of the first deployments were characterized by really low costs low performance, kind of the last retention layer if you will, for unimportant content. But then this web application thing happens and people started to build web apps that used object storage as their primary storage. And so now, as people try to bring those cloud native applications on-prem and build them in a multicloud way there's a real growth in the need for you know, high-performance kind of applications object storage. And so we see this real change to the needs and requirements on the object storage landscape. And it's one that in particular, we're trying to serve with our FlashBlade product that provides a unified file and object access, because many of those applications are kind of graduating from file or moving towards object, but they can't do that overnight. And so being able to provide a high-performance way to deliver unstructured data (indistinct) object files solve is very strategic right now. >> Well, that's insightful. Thanks. So I want to thank you both for being here. And, you know, I look forward to hearing about Portworx and Pure in the future as is acquisition. You know, it integrates and new products and new developments come out from the Pure side. So thanks both for being here and thank you at home for watching. I'm Joep Piscaer, thanks for watching the theCUBE's coverage of KubeCon CloudNativeCon 2020. Thanks. >> Yeah. Thanks too. >> Yeah. Thank you. (gentle music)

>>from around the globe. It's the Cube >>with digital coverage of VM World 2020 brought to you by VM Ware and its ecosystem partners. Hello and welcome back to the VM World 2020 Virtual coverage with the Cube Virtual I'm John for day. Volonte your hosts our 11th year covering VM. We'll get a great guest Greg Lavender, SBP and the CTO of VM. Where, uh, welcome to the Cube. Virtual for VM World 2020 Virtual Great. Thanks for coming on. >>Privileged to be here. Thank you. >>Um, really. You know, one of the things Dave and I were commenting with Pat on just in general start 11th year covering VM world. Uh, a little difference not face to face. But it's always been a technical conference. Always a lot of technical innovation. Project Monterey's out there. It's pretty nerdy, but it's a it's called the catnip of the future. Right? People get excited by it, right? So there's really ah lot of awareness to it because it kinda it smells like a systems overhaul. It smells like an operating system. Feels like a, you know, a lot of moving parts that are, quite frankly, what distributed computing geeks and software geeks love to hear about and to end distributed software intelligence with new kinds of hardware innovations from and video and whatnot. Where's that innovation coming from? Can you share your thoughts on this direction? >>Yeah, I think first I should say this isn't like, you know, something that just, you know, we decided to do, you know, six months ago, actually, in the office of C T 04 years ago, we actually had a project. Um, you know, future looking project to get our core hyper visor technology running on arm processors and that incubated in the office of the CTO for three years. And then last December, move the engineering team that had done that research and advanced development work in the office of the CTO over to our cloud platforms business unit, you know, and smart Knicks, you know, kind of converged with that. And so we were already, you know, well along the innovation path there, and it's really now about building the partnerships we have with smart nick vendors and driving this technology out to the benefit of our customers who don't want to leverage it. >>You get >>Greg, I want if you could clarify something for me on that. So Pat talked about Monterey, a complete re architect ing of the i o Stack. And he talked about it affecting in video. Uh, intel, melon, ox and Sandoz part of that when he talks about the Iot stack, you know, specifically what are we talking about there? >>So you know any any computing server in the data center, you know, in a cola facility or even even in the cloud, you know? Ah, large portion of the, you know CPU resource is, and even some memory resource is can get consumed by just processing. You know, the high volumes of Iot that's going out, you know, storage devices, you know, communicating between the different parts of multi tiered applications. And so there's there's a there's an overhead that that gets consumed in the course server CPU, even if its multi core multi socket. And so by offloading that a lot of that I owe work onto the arm core and taking advantage of the of the hardware offloads there in the smart Knicks, you can You can offload that processing and free up even as much as 30% of the CPU of a server, multi socket, multicourse server, and give that back to the application so that the application gets the benefit of that extra compute and memory resource is >>So what about a single sort of low cost flash tear to avoid the complexities of tearing? Is that part of the equation? >>Well, you know, you can you can, um you know, much storage now is network attached. And so you could if it's all flash storage, you know, using something like envy me fabric over over Ethernet, you can essentially build large scale storage networks more efficiently, you know more cheaply and take advantage of that offload processing, uh, to begin to reduce the Iot Leighton. See, that's required taxes. That network attached storage and not just storage. But, you know, other devices, you know, that you can use you could better network attached. So disaggregated architectures is term. >>Uh, is that a yes? Or is that a stay tuned? >>Yeah, Yeah, yeah, yeah, yes. I mean the storage. You know, more efficient use of different classes of storage and storage. Tearing is definitely a prime use case there. >>Yeah, great. Thank you. Thanks for that. John, >>How could people think about the edge now? Because one of the things that's in this end to end is the edge. Pat brought it up multi cloud and edge or two areas that are extending off cloud and hybrid. What should people think about the innovation equation around those things? Is that these offload techniques? What specifically in the systems architecture? Er, do you guys see as the key keys there? >>So so, you know, edges very diversified, heterogeneous place, Uh, in the architectures of multi cloud services. So one thing we do know is, you know, workload. I would like to say workload follows data, and a lot of the data will be analyzed, the process at the edge. So the more that you can accelerate that data processing at the edge and apply some machine learning referencing at the edge were almost certainly gonna have kubernetes everywhere, including the edge. So I think you're seeing a convergence of the hardware architectures er the kubernetes control plane and services and machine learning workloads. You know, traveling to the edge where the where the data is going to be processed and actions could be taken autonomously at the edge. So I think we're in this convergence point in the industry where all that comes together. >>How important do you >>do you see that? Okay, John, >>how important is the intelligence piece? Because again, the potatoes at the edge. How do you guys see the data architecture being built out there? >>Um, well, again, it's depending on the other. The thick edge of the thin edge. You know, you're gonna have different, different types of data, and and again, a lot of the the inference thing that could happen at the edges. Going to, I think, for mawr, you know, again to take action at the edges, opposed to calling home to a cloud, you know, to decide what to do. So, depending on, you know, the computational power and the problem with its video processing or monitoring, you know, sensors, Aaron, oil. Well, the kind of interesting that will happen at the edge will will be dependent on that data type and what kind of decisions you want to make. So I think data will be moving, you know, from the edge to the cloud for historical analytics and maybe transitional training mechanisms. But, you know, the five G is gonna play heavily into this is well right for the network connectivity. So we read This unique point is often occurs in the industry every few years of all these technology innovations converging to open up an entirely new platform in a new way of computing that happens at the edge, not just in your data center at the cloud. >>So, Greg, you did a fairly major stint at a large bank. What would something you mentioned? You know, like an oil rig. But what would something like these changes mean for a new industry like banking or financial? Uh, will it have an impact there and put on your customer hat for a minute and take us through that >>e? You know, eight machines, you know, branches, chaos. You know, there's all make banks always been a very distributed computing platform. And so, you know, people want to deliver mawr user experience, services, more video services. You know all these things at the edge to interact positively with the customer without using the people in the loop. And so the banking industry has already gone through the SD when, and I want transformation to deliver the bandwidth more capably to the edge. And I just think that they'll just now be able to deliver Mawr Edge services that happened can happen more autonomously at the edge is opposed that having the hairpin home run everything back to the data center. >>Awesome. Well, Pat talks about the modern platform, the modern companies. Greg, I wanna ask you because we're seeing with Kovar, there's to use cases, you know, the people who don't have a tailwind, Um, companies that are, you know, not doing well because there's no business that you have there modernizing their business while they have some downtime. Other ones have a tailwind. They have a modern app that that takes advantage, this covert situation. So that brings up this idea of what is a modern app look like? Because now, if you're talking about a distributed architecture, some of things you're mentioning around inference, data edge. People are starting to think about these modern naps, and they are changing the game for the business. Now you have vertical industries. You mentioned oil and gas, you got financial services. It used to be you had industry solution. It worked like that and was siloed. Now you have a little bit of a different architectures. If we believe that we're looking up, not down. Does it matter by industry? How should people think about a modern application, how they move faster? Can you share your insights into into some of this conceptual? What is a modern approach and does it doesn't matter by vertical or industry. >>Yes, I mean, certainly over the course of my career, I mean, there's there's a massive diversity of applications. And of course, you know, the explosion of mobile and edge computing is just another sort of sort of use cases that will put demands on the infrastructure in the architecture and the networking. So a modern, a modern app I mean, we historically built sort of these monolithic app. So we sort of built these sort of three tier apse with, you know, sort of the client side, the middleware side. The database back in is the system of record. I mean, this is even being more disaggregated in terms of, you know, the the consumer edges both not just web here, but mobile tear. And, you know, we'll see what emerges out of that. The one thing for sure that is that, um they're becoming less monolithic and mawr a conglomeration of sass and other services that are being brought together, whether it's from the cloud services or whether it's s, you know, SBS delivering, you know, bring your own software. Um, and they're becoming more distributed because people need operated higher degrees of scale. There's a limit to Virgil vertical scaling, so you have to go to horizontal scaling, which is what the cloud is really good at. So I think all these things were driving a whole new set of technologies like next generation AP gateways. Message Busses, service mesh. We're announcing Tanzi's service message being world. Um, you know, this is just allowing allowing that application to be disaggregated and then integrated with other APS assassin services that allow you to get faster time to market. So speed of delivery is everything. So modern C I. C d. Modern software, technology and ability to deploy and run that workload anywhere at the edge of the core in the data center in the cloud. >>So when you do in your re architecture like this, Greg, I mean you've seen over the course of history in our industry you've seen so many companies have hit a wall and in VM, whereas it's just amazing engineering culture. How are you able toe, you know, change the engine mid flight here and avoid like, serious technical debt. And I mean, it took, you know, you said started four years ago, but can you give us a peek inside? You know, that sort of transformation and how you're pulling that off? >>Well, I mean, we're providing were delivered the platform and, you know, spring Buddhas a key, you know, technology that's used widely across the industry already, which is what we've got is part of our pivotal acquisition. And so what we're just trying to do is just keep keep delivering the technology and the platform that allows people to go faster with quality security and safety and resiliency. That's what we do really well at VM ware. So I think you're seeing more people building these APS Cloud native is opposed to, you know, taking an existing legacy app In trying to re factor it, they might do what it called e think somebody's called two speed architectures. Take the user front, end the consumer front in, and put that cloud native in the cloud. But the back end system of record still runs in the private cloud in a highly resilient you know, backed up disaster recovered way. So you're having, I think, brand new cloud native APS we're seeing. And then you're seeing people very carefully because there's a cost to it of looking at How do I basically modernized the front end but maintain the reliability of the scalability of security and the reliability of that sort of system of record back in? So either way, it's it's winning for the companies because they could do faster delivery to their businesses and their clients and their partners. But you have to have the resiliency and reliability that were known for for running those mission critical workloads, >>right? So the scenario is that back end stays on premise on the last earnings call, I think, Pat said, or somebody said that, that I think I just they said on Prem or maybe the man hybrid 30 to 40% cheaper, then doing it in the cloud. I presume they were talking about those kind of back end systems that you know you don't wanna migrate. Can you add some color that again from your customer perspective That the economics? >>Yeah. You know, um, somebody asked me one time what's really a cloud. Greg and I said, automation, automation, automation you can take you can take You can take your current environments and highly automate the release. Lifecycle management develop more agile software delivery methods. And so therefore, you could you could get sort of cloud benefits, you know, from your existing applications by just highly optimizing them and, you know, on the cost of goods and services. And then again, the hybrid cloud model just gives customers more choice, which is okay. I want to reduce the number of data centers I have, but I need to maintain reliability, scalability, etcetera. Take advantage of, you know, the hybrid cloud that we offer. But you'll still run things. Cloud natives. I think you're seeing this true multi cloud technology and paradigm, you know, grow out as people have these choices. And then the question is okay. If you have those choices, how do you maintain security? How do you maintain reliability? How do you maintain up time yet be able to move quickly. And so I think there's different speeds in which those platforms will evolve. And our goal is to give you the ability to basically make those choices and and optimize for economics as well as technical. You know, capability. >>Great. I want to ask you a question with Cove it we're seeing and we've been reporting the Cube virtual evolve because we used to be it at events, but we're not there anymore. But the as everyone has realized with cove it it's exposed some projects that you might not want to double down on or highlighted some gaps in architecture. Er, I mean, certainly who would have forecast of the disruption of 100% work from home VP and provisioning to access and access management security, and it really is exposed. What kind of who's where in the journey, Right in digital transformation. So I gotta ask you, what's the most important story or thing to pay attention, Thio as the smart money and smart customers go, Hey, you know what? I'm gonna double down on that. I'm gonna kill that project or sunset. That or I'm not gonna re factor that I'm gonna contain Arise it and there's probably there's a lot of that going on. In our conversations with customers, they're like it's pretty obvious. It's critical path. It's like we stay in business. We build a modern app, but I'm doubling down. I'm transitioning. It's a whole nother ballgame. What >>is >>the most important thing that you see that people should pay attention to around maintaining an innovation and coming out on the other side? >>Yeah, well, I think I think it just generally goes to the whole thesis of software defined. I mean, you know the idea of taking an appliance physical, You know, you have to order the hardware, get it on your loading dock, install in your data center. You know, go configure it, mapping into the rest of your environment. You know, whereas or you could just spend up new, softer instances of load balancers, firewalls, etcetera. So I think you know what's What's really helped in the covert era is the maturity of software to find everything. Compute storage, networking. Lan really allowed customers and many of our customers toe, you know, rapidly make that pivot. And so you know what? It's the you know, the workspace, the remote workspace. You gotta secure it. That's a key part of it, and you've got to give it. You know, you gotta have the scalability back in your data centers or, if you don't have it, be able to run those virtual desktops you know, in the cloud. And I think so. This ability again to take your current environment and, more importantly, your operating model, which, you know the technology could be agile and fast. But if you're operating models not agile, you know you can't executed Well, One of the best comments I heard from a customer CEO was, you know, for six months we debated, you know, the virtual networking architecture and how to deploy the virtual network. And, you know, when covet hit. We made the decision that did it all in one week. So the question the CEO asked now is like Well, why do we Why do we have to operate in that six month model going forward? Let's operate in the one week model going forward. E. I think that that z yeah, that's e think that's the big That's a big inflection point is the operating model has to be agile. We got all kinds of agile technology and choices I mentioned it's like, How do you make your organization agile to take advantage of those technological offerings? That's really what I've been doing the last six months, helping our customers achieve. >>I think that's a key point worth calling out and doubling down on day because, you know, whether you talk about our q Q virtual, our operating model has changed and we're doing new things. But it's not bad. It's actually beneficial. We could talk to more people. This idea of virtual ization. I mean pun intended virtual izing workforces face to face interactions air now remote. This is a software defined operating business. This is the rial innovation. I think this is the exposure. As companies wake up and going. Why didn't we do that before? Reminds me of the old mainframe days. Days? You know, why do we have that mainframe? Because they're still clutching and grabbing onto it. They got a transition. So this is the new the new reality. >>We were joking earlier that you know it ain't broke, don't fix it. And all of a sudden Covic broke everything. And so you know, virtualization becomes a fundamental component of of of how you respond. But and I wonder if Greg you could talk about the security. Peace? How how that fits in. You know everybody you know, the bromide, of course, is security can't be a bolt on. It's gotta be designed in from the start, Pat Gelsinger said years ago in the Cube. Security is a do over. You guys have purchased many different security components you've built in. Security comes. So how should we think about? And how are you thinking about designing insecurity across that entire stack without really bolting in, You know, pieces, whether it's carbon, carbon, black or other acquisitions that you've made? >>Yeah, I mean, I think that's that's the key. Inflection point we're in is an industry. I mean, getting back to my banking experience, I was responsible for cybersecurity, engineering the platforms that we engineered and deployed across the bank globally. And the challenge, the challenge. You know, that's I had, you know, 150 plus security products, and you go to bed at night wondering what? Which one did I forget to deploy or what did I get that gap? Do you think you think you're safe by the sheer number, but when you really boil down to it is like, you know, because you have to sort of like both all this stuff together to create a secure environment, you know, on a global level. And so really, our philosophy of VM where is Okay? Well, let's kind of break that model. That's what we call it intrinsic security, which is just, you know, we have the hyper visor. If you're running, the hyper visor is running on most of the service in your data center. If we have your if you have our network virtualization, we see all the traffic going between all those hyper visors and out to the cloud as well hybrid cloud or public cloud with our NSX technology. And then, you know, then you sort of bring into that the load balancers and the software to find firewalls. And pretty soon you have realized Okay, look, we have we have most of the estate. Therefore we could see everything and bring some intelligent machine learning to that and get proactive as opposed to reactive. Because our whole model now is we. All this technology and some alert pops and we get reactive. How about proactively telling me that something nasty is going on. >>I need to ask you a >>question. May be remediated. Sorry, John. It may be remediated at some point anyway. Bring in some machine intelligence tow. So instead of like you said, getting an alert actually tells me what what happened and how it was fixed, you know? Or at least recommending what I should dio, right? >>Yeah. I mean, part of the problem in the historic architectures is it was all these little silos. You know, every business unit had its own sort of technology. And Aziz, you make things virtualized. You you sort of do the virtual networking. The virtual stories of virtual compute all the software. You know, all of a sudden you have you have a different platform, you have lots of standardization. Therefore you don't have your operating model simplifies right and amount of and then it's about just collecting all the data and then making sense of the data. So you're not overwhelming the human's capacity to respond to it. And so I think that's really the fundamental thing we're all trying to get to. But the surface area is enlarged outside the data centers we've discussed out to the edge, whatever the edges, you know, into the cloud hybrid or public. So now you've got this big surface area where you've gotta have all that telemetry and all that visibility again, Back to getting proactive. So you got to do it in Band is opposed out of band. >>Great. I want to ask you a question on cyber security. We have an event on October 4th, the virtual event that Cuba is hosting with Cal Poly around this space and cybersecurity, symposiums, intersection of space and cyber. I noticed VM Ware recently announced last month that the United States Space Force has committed to the Tan Xue platform for for Continuous Dev ops operation for agility. I interviewed Lieutenant General John Thompson, Space Force, and we talked about that. He said quote, it's hard to do break fix in space. Uh, illustrating, really? Just can't send someone to swap out something in space. Not yet, at least. So they're looking at software defined as a key operating reality. Okay, so again, talk about the edge of space Isas edges. You're gonna get it. Need to be completely mad and talk about payloads and data. This >>is kind >>of interesting data point because you have security issues because space is gonna be contested and congested as an edge device. So it's actually the government's interested in that. But fundamentally, the death hops problem that you're you guys are involved in This >>is a >>reality. It's kind of connects this reality idea of operating models based in reality have to be software. What's >>your name? Yeah. I mean, I think the term we use now is def sec ops because you can't just do Dev ops. You have to have the security component in there, So, uh, yeah, the interesting. You know, like, there's a lot of interesting things happen just in fundamental networking, right? I mean, you know, the StarLink, you know, satellites at Testa. His launched Elon musk has launched and, you know, bringing sort of, you know, higher band with laurel agency to those. Yeah, we'll call it near space the and then again, just opens up all new opportunities for what we can dio. And so, Yeah, I think that's the software that the whole the whole saw for development ecosystem again, back to this idea. I think of three things. You gotta have speed. You gotta have scale and you gotta have security. And so that's really the emerging platform, whether it's a terrestrial or in near space, Uh, that's giving us the opportunity, Thio Do new architectures create service measures of services, some terrestrial, some some you know, far remote. And as you bring these new application architectures and system platform architectures together with all the underlying hardware and networking innovations that are occurring, you mentioned flash. But even getting into pmm persistent memory, right? So this this is so much happening that is converging. What's exciting to me about being a TV? Where is the CTO and we partner with all the hardware vendors? We partner with all the system providers, like in video and others. You know, the smart nick vendors. And then we get to come up with software architectures that sort of bring that together holistically and give people a platform. We can run your workloads to get work done wherever you need to land those workloads. And that's really the excitement about >>the candy store. And yet you've got problems hard problems to work on to solve. I mean, this really brings the whole project moderate, full circle because we think about space and networks and all these things you're talking about, You need to have smart everything. I mean, isn't that software? It's a complete tie into the Monterey. >>Yeah, yeah, yeah, Exactly. You're right. It's not just it's not just connecting everything and pushing data around its than having the intelligence to do it efficiently, economically, insecurely. And that's you know. So I see that you don't want to over hype machine learning. I did not to use the term AI, but use the machine learning technologies, you know, properly trained with the proper data sets, you know, and then the proper algorithms. You know that you can then a employee, you know, at the edge small edge, thick edge, you know, in the data center at the cloud is really Then you give the visibility so that we get to that proactive world I was talking about. >>Yeah, great stuff, Greg. Great insight, great conversation. Looking forward to talking mawr Tech with you. Obviously you are in the right spot was in the center of all the action across the board final point. If you could just close it out for us. What is the most important story at VM World 2020 this year. >>Um, well, I think you know, I like to say that I have the best job. I think you know that I've had in my career. I've had some great ones is you know, we get to be disruptive innovators, and we have a culture of perpetual innovation and really being world for us, Aly employees and all the people that work together to put it together is we get to showcase. You know, some of that obviously have more up our sleeves for the future. But, you know, being world is are, you know, coming coming out out show of the latest set of innovations and technologies. So there's going to be so much I have, ah, vision and innovation. Keynote kickoff, right. Do some lightning demos. And actually, I talk about work we're doing in sustainability, and we're putting a micro grid on our campus in Palo Alto and partnership with City of Palo Alto so that when the wildfires come through or there is power outages, you know we're in oasis of power generating capacity with our solar in our batteries. And so the city of Palo Alto could take their emergency command vehicles and plug into our batteries when the power is out in Palo Alto and operate city services and city emergency services. So we're not just innovating, you know, in cortex we're innovating to become a more, you know, sustainable company and provide sustainable, you know, carbon neutral technology for our customers to adopt. And I think that's an area we wanna talk about me. We talk about it next time, but I think you know our innovations. We're gonna basically help change the world with regard to climate as well. >>Let's definitely do that. Let's follow up for another in depth conversation on the societal impact. Of course, VM Ware VM Ware's VM World's 2020 is virtual is a ton of sessions. There's a Cloud City portion. Check out the 60 solution demos. Of course, they ask the expert, Greg, you're in there with Joe Beta Raghu, all the experts, um, engage and check it out. Thank you so much for the insight here on the Cube. Virtual. Thanks for coming on. >>Appreciate the opportunity. Great conversation and good questions. >>Great stuff. Thank you very much. Innovation that vm where it's the heart of their missions always has been, but they're doing well on the business side, Dave. Okay. The cube coverage. They're not there in person. Virtual. I'm John for day. Volonte. Thanks for watching.