>>Yeah, yeah, yeah, yeah, yeah. >>Welcome to this Special Cube conversation. We're gonna unpack and have a casual conversation around the big news that VM Ware just announced the sphere 7.7 point. Oh, or V. Sphere seven. Chris Prasad, senior vice president, General manager of the Sphere Cloud Platform Business unit. Paul Turner, VP of product. Guys, we just chatted about the big news. Congratulations. Um, the bottom line, if I'm a customer, I'm moving into the cloud. I see this as really an either an enabler or blocker. You guys actually think it's an enabler? Um, I'm not saying it's a blocker, but as a customer, I just need to know, Is it going to help me go faster? I'm going cloud, Which means I've been told I got to get on the cloud you got Amazon might have azure or multiple clouds with workloads sitting around. I gotta pull them all together and make them work. But right now, I just got to get my operations cloud native necessarily kind of pressure point. >>Oh, for sure. One of the biggest drivers that you see happen in the industry right now is kubernetes. Why? Why is kubernetes taking off communities taking off because it gives you cloud independence. It gives you the ability to run with same operating model, whether it's in Google Cloud, Amazon's Cloud, Microsoft Cloud or any other cloud service. What we're doing with version seven instruction bring that same kubernetes cloud independent operating model directly in divisor. So now all of your infrastructure platforms that are out there, 90% of I T environments are all kubernetes ready platforms on. That's really powerful. So what we've done is just taken a totally different kind of, um ah, scope on how cloud should be Cloud should be any cloud. It should be independent of one particular flavor of it and on developers should be able to work then in a much more agile way. >>You just see, I've been following VM where you know my career since it was founded. And, you know, with the Cube coverage over the years is they see the innovation. You guys do a lot of great stuff. Of course, we keep on our teams to minimum. And David Lantz he made some good calls with these v san. We saw the early stuff with V Cloud Air Kind of saw that kind of going in this direction, But it's been really innovation going on around you guys. I'll see with NSX has exploded and V Sphere has been the core thing. As you guys look at the cloud model, you guys made some good moves with Amazon. I've always felt that you guys could be that Switzerland that that layer of connection points between as enterprise really moved from old way of provisioning, too much more seamless operating model where they have a deal with cyber security. They gotta deal with all the stuff that's going to come from APS that's going to come from the APP store. When you bought Hep D Oh, I was like, That's actually really smart move. You started bringing that cloud native vibe into V sphere, and that's what's essentially happening here. Isn't it? >>Exactly. This is like the the coming out party for that, like it's V Sphere having all the hefty oh goodness embedded in it. And what they would see is that because we have such a huge presence in the on Prem space, this provides the fastest bad for customers to get to the cloud. So today I mean this? I don't want this point to be lost on the today. You know, we are running the same VM Ware Cloud Foundation, our on Prem on Amazon in Google and many of the same code base. Same code base, right? It's the exact same thing. So now what does that give you as a customer? It gives you the same operational model across all these clouds. Because customers today, we thought that they're setting up set of processes and tools or Amazon. Then you go to Azure. You're doing a different set than their training people to do that. And, you know, you could get into compliance and other issues where things fall through the cracks. Right? When you do that here, the same platform you said your policies wants it applies to all the clouds. You can move your workloads between clouds, right? That's a V motion. Essentially, we don't know the >>last kept on that one, but that's ideal would be crippled >>today. It is happening today and we have thousands of other partners which are the tier two service providers who are all also offering that. So we have a huge grab off these providers are in which we live in the same platform. >>Yeah, I want to add something else, actually, to that as well. Which is? This is an open platform, which is really powerful, right? This is based on kubernetes for developers, which means you can run on the V sphere platform, and that is a hybrid infrastructure that is the most ubiquitous infrastructure out there. But if you actually want to take your application actually deployed onto a native application Native Cloud, you can do that as well. Um, and so it's very important for us to keep the platform open while making broadest available on >>Dev ops. I mean, first, I totally agree. I think open wins, But the end of the day, I think this operating consistency is a big story because it's kind of like nuance. But it is really the most important customers care about, because if you're operating successfully seamlessly across cloud, it's better. So the question I have on the Dev Op side because the dream has always been infrastructure as code. So are you guys there with this? Do you consider this V Sphere seven kind of infrastructures code from a developer? Is it all being taken care of. How close are we in your mind's eye to infrastructure as code. >>Now it's 100% there. I mean, we made the announcement around Hangzhou, which is a set off other products and capabilities that we add to what the sphere has and that whole stack. And the solution is for this targeted at the modern developer. So we have all the capabilities that the developers need to do infrastructure as scored, to deploy their applications and deployed across all these clouds. >>And I want I want to add to that the infrastructure as code really has two parts to it. We look at how do I provide the developers infrastructure's code, which is what we're doing with kubernetes enablement and we have our V San product is available. In fact, all storage services from V sphere available through that andare NSX services are available through kubernetes. So you've got full infrastructures code for developers. But infrastructures code also means how do you deploy large scale infrastructures and manage them as code? How do people actually manage the operations and the deployment of services? And so you're right in your admin team actually have a full layer of enhanced lifecycle management provisioning off configurations and settings across infrastructure. All of that is now managed, as >>that's almost under the hood kind of stuff. But that's important because networking is going to play a big role in all of this from a security standpoint and also compute storage. Pretty much looking, looking good, but networking becomes a huge part of what's under the hood. >>Yeah, I mean, look at networking is what enables us to connect all these clouds together, right? And NSX being the underlying platform for us enables us to have one single layer across all these clouds with the same operating model. So NSX is very critical. >>I want to get your guys thoughts on some little history lesson here or scar tissue, as we say in the industry. You know, I remember back during the Hadoop days, 2010 the big data movement hit, and it was just going to save us all. It's gonna be great, but what ended up happening was this very hard to stand up these clusters and what happened was the commitment the vision was there, but it was just really hard to manage and stand up clusters and hire people to do this. So it has some use cases, but it just really kind of fell down. We saw Open Stack have a similar trajectory where good on paper, things had used cases. But it's just so hard to manage the trends. We're moving very, very fast. Cloud was here. Cloud Computing kind of took everyone by storm and just got rid of all those things. And so they kind of dying. >>No. But if you think about why open Stack didn't go anywhere in the end, it's because of the operational complexity right? It took a lot to set it up, and he had essentially invest a lot more than keeping it running right. And then what we're doing is saying you don't have to worry about that aspect because it's built into the platform that you already know, right? So we have taken that complexity out completely, and so you just have this fear. The administrators know how to set up and run and do life cycle, and this year, and you get kubernetes, go >>back to my original question. If that's the case, which, by the way, I think that's the way to think about it. Then I found the customer acceleration. I can draft up with the movement of cloud as fast as I can Go is having any kind of blockers. >>Fastest lamb like cloud >>ran to the cloud >>and fastest fastest ramp to a cloud operating model, which means that all of your developers can now actually run as quickly as they can, building their applications independent of I t. In a much more dynamic way. So you want to move to that cloud operating model. That's why Kubernetes is so important on the infrastructure side. We've actually, of course, made it a much easier platform to manage. But but it's the agility that matters. >>You guys have done some great innovation. I think you've got a good ear to the market, made some good moves. Looking good. This is a great vision. I got to get your guys take on the edge. Big discussion. Five g. Certain years love that kind of vision. But the end of the day and edge. Now, if you talk about cloud operations, everything's an edge, right? So what does edge mean for V sphere? How do you guys look at the edge of the network. And as these applications with the sensors or whatever happening at the edges, How does this V Sphere look at that? How do you guys look? >>So, uh, for let me just I would say that, you know, we we have, ah, data center edge, right? We just think of it as, um, retail stores, Starbucks, right. They have a kind of a mini data center application running there. That's one kind of edge that people talk about. Then you have the kind of the telco edge, but a lot of the crossing of the five year data is happening, right? Where the cell tower, Selden. We're done. And then you have the devices. You just the cars, the You know what you have at home and we're not right. And then and we can play across all of these because we have the platform. I don't know if you know, but ah, v sphere, as the platform is, is embedded in many devices today. It's in the army. It's embarking leaders it. So it has a form factor that can live in all these devices. We certainly play in the data center, so we're well suited to play the >>piece for anywhere. >>Yeah, that is exactly right. >>I think we're already We're already at the data center edge, as we've talked about that is, it's a very common deployment use case for earlier versions of the sphere, and it will continue to be the value that you guys it's not not new at all. I think the telco edge is actually a very interesting one, particularly the five G switch over. So you know what's happening. There is. There's a whole radio access networks and you're looking at the V Ron as a big initiative there. Which is how do we bring virtualization as a service they're into into those networks? Container deployments becomes very important as well. So we actually have a platform with version seven that actually can give the telco edge and five G network deployments a much more secure, predictable runtime environment. So that's really powerful as well. And it's containers and VMS because many of those applications that are deployed a telco edge our container based applications. >>It's interesting, you know, we talk about stacks in our last segment and you guys talking about the news and now having all these stacks later on. But think about the evolution of the industry with cloud. A whole new sets of services are emerging mentioned Telco Edge. So it just looks different. What's the same kind of open model that open systems brought us, but just a little bit different? It's a distributed cloud security computer, same concepts, new new capabilities. >>Not just to add to that, I mean the biggest innovation John is happening in the hardware layer by the computer, sort of getting disaggregated. There is a lot of acceleration that is going on that are specialized chips, a six effigies that are being built into the servers and and memory's getting pulled outside because the interconnect is getting fast enough for those things to happen. And so a lot of the innovation that we do as a platform that we didn't talk about much today is really a data layer, because we had to virtual eyes all of that and provide it to the level. Of course, >>yeah, it's great. It's a great architecture. I think I just add more complexity that's coming and you guys can help. Abstract away is you just look at cybersecurity and the role of data. You got to get in front of all these these trends to get that automation dev ops going because without any automation and software is just people can't handle the inbounds. It's a big problem. >>Yeah, you really need, um, your platforms to provide intrinsic security. It shouldn't be. It shouldn't be an option. It shouldn't be something the developers need to worry about. It should be something that's just part of the platform. And that's one of the things that we see is critical and actually built into Visa or seven. And you've seen that we've made a number of acquisitions recently. Actually, in the security piece, it's it's so that we can purposely build into your runtime environment, which is your VM environment container environment that we're running. We actually build in intrinsic security would build in a dynamic checking off the scope of an application in real time. Um, while those applications running, which is very key. >>Paul, >>Thanks for sharing all that great stuff. I want to get one final thought for both of you before we wrap up is we've been seeing and we've been reporting kind of the three ways of the cloud wave one was public. We all kind of know how that turned out. Awesome Cloud Native Born in the Cloud Wave two is well right now with a lot of intensity hybrid that's got a range of definitions. And then the third wave that's coming fast is multi cloud. So I want to get your thoughts on hybrid. A lot of energy, a lot of spend a lot of dollars investment in hard causing people in hybrid. I know we have different definitions. Is also different versions of hybrid. How do you define hybrid? And how does that become a path to the next wave? Or is it a path of next wave? What's your take? >>So it's absolutely the bad the next, I would say the hybrid, in our view, is the same platform running on which cloud do you want to use in our platform, as we talked about spans all the major clouds today giving the same operating model, and that's what we view as the hybrid cloud story. But the next one is the ability to mix native cloud workloads and services with that, and we already have a set of products and services that target that it's the times. A portfolio that I talked about is all focused on the multi cloud journey. So we kind of support both, and we're looking forward and aggressively going after the multi cloud. >>I think it's important to think of them as is completely complimentary of each other, right? A hybrid infrastructure platforms. So you know, a single I T organization can actually have one operating experience for their entire infrastructure, independent of Cloud Private Cloud Public Cloud Services. But Multi Cloud is about developers. It's about developers able to deploy their applications on any cloud environment that they need to, and they don't need to worry about infrastructure. So hybrid cloud is really about, ah, hybrid infrastructure that we can deploy everywhere, multi cloud and the services that we're providing to developers is all about how you could be independent of any cloud deployment that you want. It could be a hybrid infrastructure you deploy on. It could be on a standard public cloud service, >>and what's interesting is not. Not not all clouds are created equal. I mean, Amazon has much more capability in Azure and Google, but they're finding their swim lanes. But again it's all about the workload. The workload decides which cloud to work on. And that's right. You guys just agnostic? Yes, For the operator. Well, well, Thanks for the insight, guys. Appreciate you did a little post wrap of the news. Thanks for hiring. Thank you. Big news. These fear seven Q breakdown here. I'm John Furrier. Thanks for watching, >>right? Yeah.