>>Okay, welcome back everyone. There's the cubes coverage of VMware Explorer, 22 formerly world. We've been here since 2010 and world 2010 to now it's 2022. And it's VMware Explorer. We're here at the CEO, regular writer. Welcome back to the cube. Great to see you in person. >>Yeah. Great to be here in person, >>Dave and I are, are proud to say that we've been to 12 straight years of covering VMware's annual conference. And thank you. We've seen the change in the growth over time and you know, it's kind of, I won't say pinch me moment, but it's more of a moment of there's the VMware that's grown into the cloud after your famous deal with Andy jazzy in 2016, we've been watching what has been a real sea change and VMware since taking that legacy core business and straightening out the cloud strategy in 2016, and then since then an acceleration of, of cloud native, like direction under your leadership at VMware. Now you're the CEO take us through that because this is where we are right now. We are here at the pinnacle of VMware 2.0 or cloud native VMware, as you point out on your keynote, take us through that history real quick. Cuz I think it's important to know that you've been the architect of a lot of this change and it's it's working. >>Yeah, definitely. We are super excited because like I said, it's working, the history is pretty simple. I mean we tried running our own cloud cloud air. We cloud air didn't work so well. Right. And then at that time, customers really gave us strong feedback that the hybrid they wanted was a Amazon together. Right. And so that's what we went back and did and the andjay announcement, et cetera. And then subsequently as we were continue to build it out, I mean, once that happened, we were able to go work with the Satia and Microsoft and others to get the thing built out all over. Then the next question was okay, Hey, that's great for the workloads that are running on vSphere. What's the story for workloads that are gonna be cloud native and benefit a lot from being cloud native. So that's when we went the Tansu route and the Kubernetes route, we did a couple of acquisitions and then we started that started paying off now with the Tansu portfolio. And last but not the least is once customers have this distributed portfolio now, right. Increasingly everything is becoming multi-cloud. How do you manage and connect and secure. So that's what you start seeing that you saw the management announcement, networking and security and everything else is cooking. And you'll see more stuff there. >>Yeah know, we've been talking about super cloud. It's kinda like a multi-cloud on steroids kind a little bit different pivot of it. And we're seeing some use cases. >>No, no, it's, it's a very great, it's a, it's pretty close to what we talk about. >>Awesome. I mean, and we're seeing this kind of alignment in the industry. It's kind of open, but I have to ask you, when did you, you have the moment where you said multicloud is the game changer moment. When did you have, because you guys had hybrid, which is really early as well. When was the Raghu? When did you have the moment where you said, Hey, multicloud is what's happening. That's we're doubling down on that go. >>I mean, if you think about the evolution of the cloud players, right. Microsoft really started picking up around the 2018 timeframe. I mean, I'm talking about Azure, right? >>In a big way. >>Yeah. In a big way. Right. When that happened and then Google got really serious, it became pretty clear that this was gonna be looking more like the old database market than it looked like a single player cloud market. Right. Equally sticky, but very strong players all with lots of IP creation capability. So that's when we said, okay, from a supplier side, this is gonna become multi. And from a customer side that has always been their desire. Right. Which is, Hey, I don't want to get locked into anybody. I want to do multiple things. And the cloud vendors also started leveraging that OnPrem. Microsoft said, Hey, if you're a windows customer, your licensing is gonna be better off if you go to Azure. Right. Oracle did the same thing. So it just became very clear. >>I am, I have gone make you laugh. I always go back to the software mainframe because I, I think you were here. Right. I mean, you're, you're almost 20 years in. Yeah. And I, the reason I appreciate that is because, well, that's technically very challenging. How do you make virtualization overhead virtually non-existent how do you run any workload? Yeah. How do you recover from, I mean, that's was not trivial. Yeah. Okay. So what's the technical, you know, analog today, the real technical challenge. When you think about cross cloud services. >>Yeah. I mean, I think it's different for each of these layers, right? So as I was alluding to for management, I mean, you can go each one of them by themselves, there is one way of Mo doing multi-cloud, which is multiple clouds. Right. You could say, look, I'm gonna build a great product for AWS. And then I'm gonna build a great product for Azure. I'm gonna build a great product for Google. That's not what aria is. Aria is a true multi-cloud, which means it pulls data in from multiple places. Right? So there are two or three, there are three things that aria has done. That's I think is super interesting. One is they're not trying to take all the data and bring it in. They're trying to federate the data sources. And secondly, they're doing it in real time and they're able to construct this graph of a customer's cloud resources. >>Right. So to keep the graph constructed and pulling data, federating data, I think that's a very interesting concept. The second thing that, like I said is it's a real time because in the cloud, a container might come and go like that. Like that is a second technical challenge. The third it's not as much a technical challenge, but I really like what they have done for the interface they've used GraphQL. Right? So it's not about if you remember in the old world, people talk about single pan or glass, et cetera. No, this is nothing to do with pan or glass. This is a data model. That's a graph and a query language that's suited for that. So you can literally think of whatever you wanna write. You can write and express it in GraphQL and pull all sorts of management applications. You can say, Hey, I can look at cost. I can look at metrics. I can look at whatever it is. It's not five different types of applications. It's one, that's what I think had to do it at scale is the other problem. And, and >>The, the technical enable there is just it's good software. It's a protocol. It's >>No, no, it's, it's, it's it's software. It's a data model. And it's the Federation architecture that they've got, which is open. Right. You can pull in data from Datadog, just as well as from >>Pretty >>Much anything data from VR op we don't care. Right? >>Yeah. Yeah. So rego, I have to ask you, I'm glad you like the Supercloud cuz you know, we, we think multi-cloud still early, but coming fast. I mean, everyone has multiple clouds, but spanning this idea of spanning across has interesting sequences. Do you data, do you do computer both and a lot of good things happening. Kubernetes been containers, all that good stuff. Okay. How do you see the first rev of multi-cloud evolving? Like is it what happens? What's the sequence, what's the order of operations for a client standpoint? Customer standpoint of, of multicloud or Supercloud because we think we're seeing it as a refactoring of something like snowflake, they're a data base, they're a data warehouse on the cloud. They, they say data cloud they'd they like they'll tell us no, you, we're not a data. We're not a data warehouse. We're data cloud. Okay. You're a data warehouse refactored for the CapEx from Amazon and cooler, newer things. Yeah, yeah, yeah. That's a behavior change. Yeah. But it's still a data warehouse. Yeah. How do you see this multi-cloud environment? Refactoring? Is there something that you see that might be different? That's the same if you know what I'm saying? Like what's what, what's the ne the new thing that's happening with multi-cloud, that's different than just saying I'm I'm doing SAS on the cloud. >>Yeah. So I would say, I would point to a, a couple of things that are different. Firstly, my, the answer depends on which category you are in. Like the category that snowflake is in is very different than Kubernetes or >>Something or Mongo DB, right? >>Yeah. Or Mongo DB. So, so it is not appropriate to talk about one multi-cloud approach across data and compute and so, so on and so forth. So I'll talk about the spaces that we play. Right. So step one, for most customers is two application architectures, right? The cloud native architecture and an enterprise native architecture and tying that together either through data or through networks or through et cetera. So that's where most of the customers are. Right. And then I would say step two is to bring these things together in a more, in a closer fashion and that's where we are going. And that is why you saw the cloud universal announcement and that's already, you've seen the Tansu announcement, et cetera. So it's really, the step one was two distinct clouds. That is just two separate islands. >>So the other thing that we did, that's really what my, the other thing that I'd like to get to your reaction on, cause this is great. You're like a masterclass in the cube here. Yeah, totally is. We see customers becoming super clouds because they're getting the benefit of, of VMware, AWS. And so if I'm like a media company or insurance company, if I have scale, if I continue to invest in, in cloud native development, I do all these things. I'm gonna have a da data scale advantage, possibly agile, which means I can build apps and functionality very quick for customers. I might become my own cloud within the vertical. Exactly. And so I could then service other people in the insurance vertical if I'm the insurance company with my technology and create a separate power curve that never existed before. Cause the CapEx is off the table, it's operating expense. Yep. That runs into the income statement. Yep. This is a fundamental business model shift and an advantage of this kind of scenario. >>And that's why I don't think snowflakes, >>What's your reaction to that? Cuz that's something that, that is not really, talk's highly nuanced and situational. But if Goldman Sachs builds the biggest cloud on the planet for financial service for their own benefit, why wouldn't they >>Exactly. >>And they're >>Gonna build it. They sort of hinted at it that when they were up on stage on AWS, right. That is just their first big step. I'm pretty sure over time they would be using other clouds. Think >>They already are on >>Prem. Yeah. On prem. Exactly. They're using VMware technology there. Right? I mean think about it, AWS. I don't know how many billions of dollars they're spending on AWS R and D Microsoft is doing the same thing. Google's doing the same thing we are doing. Not as much as them that you're doing oral chair. Yeah. If you are a CIO, you would be insane not to take advantage of all of this IP that's getting created and say, look, I'm just gonna bet on one. Doesn't make any sense. Right. So that's what you're seeing. And then >>I think >>The really smart companies, like you talked about would say, look, I will do something for my industry that uses these underlying clouds as the substrate, but encapsulates my IP and my operating model that I then offer to other >>Partners. Yeah. And their incentive for differentiation is scale. Yeah. And capability. And that's a super cloud. That's a, or would be say it environment. >>Yeah. But this is why this, >>It seems like the same >>Game, but >>This, I mean, I think it environment is different than >>Well, I mean it advantage to help the business, the old day service, you >>Said snowflake guys out the marketing guys. So you, >>You said snowflake data warehouse. See, I don't think it's in data warehouse. It's not, that's like saying, you >>Know, I, over >>VMware is a virtualization company or service now is a help desk tool. I, this is the change. Yes. That's occurring. Yes. And that you're enabling. So take the Goldman Sachs example. They're gonna run OnPrem. They're gonna use your infrastructure to do selfer. They're gonna build on AWS CapEx. They're gonna go across clouds and they're gonna need some multi-cloud services. And that's your opportunity. >>Exactly. That's that's really, when you, in the keynote, I talked about cloud universal. Right? So think of a future where we can go to a customer and say, Mr. Customer buy thousand scores, a hundred thousand cores, whatever capacity you can use it, any which way you want on any application platform. Right. And it could be OnPrem. It could be in the cloud, in the cloud of their choice in multiple clouds. And this thing can be fungible and they can tie it to the right services. If they like SageMaker they could tie it to Sage or Aurora. They could tie it to Aurora, cetera, et cetera. So I think that's really the foundation that we are setting. Well, I think, I >>Mean, you're building a cloud across clouds. I mean, that's the way I look at it. And, and that's why it's, to me, the, the DPU announcement, the project Monterey coming to fruition is so important. Yeah. Because if you don't have that, if you're not on that new Silicon curve yep. You're gonna be left behind. Oh, >>Absolutely. It allows us to build things that you would not otherwise be able to do, >>Not to pat ourselves on the back Ragu. But we, in what, 2013 day we said, feel >>Free. >>We, we said with Lou Tucker when OpenStack was crashing. Yeah. Yeah. And then Kubernetes was just a paper. We said, this could be the interoperability layer. Yeah. You got it. And you could have inter clouding cuz there was no clouding. I was gonna riff on inter networking. But if you remember inter networking during the OSI model, TCP and IP were hardened after the physical data link layer was taken care of. So that enabled an entire new industry that was open, open interconnect. Right. So we were saying inter clouding. So what you're kind of getting at with cross cloud is you're kind of creating this routing model if you will. Not necessarily routing, but like connection inter clouding, we called it. I think it's kinda a terrible name. >>What you said about Kubernetes is super critical. It is turning out to be the infrastructure API so long. It has been an infrastructure API for a certain cluster. Right. But if you think about what we said about VSE eight with VSE eight Kubernetes becomes the data center API. Now we sort of glossed over the point of the keynote, but you could do operations storage, anything that you can do on vSphere, you can do using a Kubernetes API. Yeah. And of course you can do all the containers in the Kubernetes clusters and et cetera, is what you could always do. Now you could do that on a VMware environment. OnPrem, you could do that on EKS. Now Kubernetes has become the standard programming model for infrastructure across. It >>Was the great equalizer. Yeah. You, we used to say Amazon turned the data center through an API. It turns, turns of like a lot of APIs and a lot of complexity. Right. And Kubernetes changed. >>Well, the role, the role of defacto standards played a lot into the T C P I P revolution before it became a standard standard. What the question Raghu, as you look at, we had submit on earlier, we had tutorial on as well. What's the disruptive enabler from a defacto. What in your mind, what should, because Kubernetes became kind of defacto, even though it was in the CNCF and in an open source open, it wasn't really standard standard. There's no like standards, body, but what de facto thing has to happen in your mind's eye around making inter clouding or connecting clouds in a, in a way that's gonna create extensibility and growth. What do you see as a de facto thing that the industry should rally around? Obviously Kubernetes is one, is there something else that you see that's important for in an open way that the industry can discuss and, and get behind? >>Yeah. I mean, there are things like identity, right? Which are pretty critical. There is connectivity and networking. So these are all things that the industry can rally around. Right. And that goes along with any modern application infrastructure. So I would say those are the building blocks that need to happen on the data side. Of course there are so many choices as well. So >>How about, you know, security? I think about, you know, when after stuck net, the, the whole industry said, Hey, we have to do a better job of collaborating. And then when you said identity, it just sort of struck me. But then a lot of people tried to sort of monetize private reporting and things like that. So you do you see a movement within the technology industry to do a better job of collaborating to, to solve the acute, you know, security problems? >>Yeah. I think the customer pressure and government pressure right. Causes that way. Yeah. Even now, even in our current universe, you see, there is a lot of behind the scenes collaboration amongst the security teams of all of the tech companies that is not widely seen or known. Right. For example, my CISO knows the AWS CSO or the Microsoft CSO and they all talk and they share the right information about vulnerability attacks and so on and so forth. So there's already a certain amount of collaboration that's happening and that'll only increase. Do, >>Do you, you know, I was somewhat surprised. I didn't hear more in your face about security would, is that just because you had such a strong multi-cloud message that you wanted to get, get across, cuz your security story is very strong and deep. When you get into the DPU side of things, the, you know, the separation of resources and the encryption and I'll end to end >>I'm well, we have a phenomenal security story. Yeah. Yeah. Tell security story and yes. I mean I'll need guilty to the fact that in the keynote you have yeah, yeah, sure time. But what we are doing with NSX and you will hear about some NSX projects as you, if you have time to go to some of the, the sessions. Yeah. There's one called project, not star. Another is called project Watchman or watch, I think it's called, we're all dealing with this. That is gonna strengthen the security story even more. Yeah. >>We think security and data is gonna be a big part of it. Right. As CEO, I have to ask you now that you're the CEO, first of all, I'd love to talk about product with you cuz you're yeah. Yeah. We just great conversation. We want to kind of read thet leaves and ask pointed questions cuz we're putting the puzzle together in real time here with the audience. But as CEO, now you have a lot of discussions around the business. You, the Broadcom thing happening, you got the rename here, you got multi-cloud all good stuff happening. Dave and I were chatting before we came on this morning around the marketplace, around financial valuations and EBIDA numbers. When you have so much strategic Goodwill and investment in the oven right now with the, with the investments in cloud native multi-year investments on a trajectory, you got economies of scale there. >>It's just now coming out to be harvest and more behind it. Yeah. As you come into the Broadcom and or the new world wave that's coming, how do you talk about that value? Cuz you can't really put a number on it yet because there's no customers on it. I mean some customers, but you can't probably some for form. It's not like sales numbers. Yeah. Yeah. How do you make the argument to the PE type folks out there? Like EBIDA and then all the strategic value. What's the, what's the conversation like if you can share any, I know it's obviously public company, all the things going down, but like how do you talk about strategic value to numbers folks? >>Yeah. I mean, we are not talking to PE guys at all. Right. I mean the only conversation we have is helping Broadcom with >>Yeah. But, but number people who are looking at the number, EBIDA kind of, >>Yeah. I mean, you'd be surprised if, for, for example, even with Broadcom, they look at the business holistically as what are the prospects of this business becoming a franchise that is durable and could drive a lot of value. Right. So that's how they look at it holistically. It's not a number driven. >>They do. They look at that. >>Yeah. Yeah, absolutely. So I think it's a misperception to say, Hey, it's a numbers driven conversation. It's a business driven conversation where, I mean, and Hawk's been public about it. He says, look, I look at businesses. Can they be leaders in their market? Yeah. Because leaders get, as we all know a disproportionate share of the economic value, is it a durable franchise that's gonna last 10 years or more, right. Obviously with technology changes in between, but 10 years or more >>Or 10, you got your internal, VMware talent customers and >>Partners. Yeah. Significant competitive advantage. So that's, that's really where the conversation starts and the numbers fall out of it. Got it. >>Okay. So I think >>There's a track record too. >>That culture >>That VMware has, you've always had an engineering culture. That's turned, you know, ideas and problems into products that, that have been very successful. >>Well, they had different engineering cultures. They're chips. You guys are software. Right. You guys know >>Software. Yeah. Mean they've been very successful with Broadcom, the standalone networking company since they took it over. Right. I mean, it's, there's a lot of amazing innovation going on there. >>Yeah. Not, not that I'm smiling. I want to kind of poke at this question question. I'll see if I get an answer out of you, when you talk to Hawk tan, does he feel like he bought a lot more than he thought or does he, did he, does he know it's all here? So >>The last two months, I mean, they've been going through a very deliberate process of digging into each business and certainly feels like he got a phenomenal asset base. Yeah. He said that to me even today after the keynote, right. Is the amazing amount of product capability that he's seeing in every one of our businesses. And that's been the constant frame. >>But congratulations on that. >>I've heard, I've heard Hawk talk about the shift to, to Mer merchant Silicon. Yeah. From custom Silicon. But I wanted to ask you when you look at things like AWS nitro yeah. And graviton and train and the advantage that AWS has with custom Silicon, you see Google and Microsoft sort of Alibaba following suit. Would it benefit you to have custom Silicon for, for DPU? I mean, I guess you, you know, to have a tighter integration or do you feel like with the relationships that you have that doesn't buy you anything? >>Yeah. I mean we have pretty strong relationships with in fact fantastic relationships with the Invidia and Intel and AMD >>Benon and AMD now. >>Yeah. Yeah. I mean, we've been working with the Pendo team in their previous incarnations for years. Right, right. When they were at Cisco and then same thing with the, we know the Melanox team as well as the invi original teams and Intel is the collaboration right. From the get go of the company. So we don't feel a need for any of that. We think, I mean, it's clear for those cloud folks, right. They're going towards a vertical integration model and select portions of their stack, like you talked about, but there is always a room for horizontal integration model. Right. And that's what we are a part of. Right. So there'll be a number of DPU pro vendors. There'll be a number of CPU vendors. There'll be a number of other storage, et cetera, et cetera. And we think that is goodness in an alternative model compared to a vertically integr >>And yeah. What this trade offs, right. It's not one or the other, I mean I used to tell, talk to Al Shugar about this all the time. Right. I mean, if vertically integrated, there may be some cost advantages, but then you've got flexibility advantages. If you're using, you know, what the industry is building. Right. And those are the tradeoffs, so yeah. Yeah. >>Greg, what are you excited about right now? You got a lot going on obviously great event. Branding's good. Love the graphics. I was kind of nervous about the name changed. I likem world, but you know, that's, I'm kind of like it >>Doesn't readily roll off your phone. Yeah. >>I know. We, I had everyone miscue this morning already and said VMware Explorer. So >>You pay Laura fine. Yeah. >>Now, I >>Mean a quarter >>Curse jar, whatever I did wrong. I don't believe it. Only small mistake that's because the thing wasn't on. Okay. Anyway, what's on your plate. What's your, what's some of the milestones. Do you share for your employees, your customers and your partners out there that are watching that might wanna know what's next in the whole Broadcom VMware situation. Is there a timeline? Can you talk publicly about what? To what people can expect? >>Yeah, no, we, we talk all the time in the company about that. Right? Because even if there is no news, you need to talk about what is where we are. Right. Because this is such a big transaction and employees need to know where we are at every minute of the day. Right? Yeah. So, so we definitely talk about that. We definitely talk about that with customers too. And where we are is that the, all the processes are on track, right? There is a regulatory track going on. And like I alluded to a few minutes ago, Broadcom is doing what they call the discovery phase of the integration planning, where they learn about the business. And then once that is done, they'll figure out what the operating model is. What Broadcom is said publicly is that the acquisition will close in their fiscal 23, which starts in November of this year, runs through October of next year. >>So >>Anywhere window, okay. As to where it is in that window. >>All right, Raghu, thank you so much for taking valuable time out of your conference time here for the queue. I really appreciate Dave and I both appreciate your friendship. Congratulations on the success as CEO, cuz we've been following your trials and tribulations and endeavors for many years and it's been great to chat with you. >>Yeah. Yeah. It's been great to chat with you, not just today, but yeah. Over a period of time and you guys do great work with this, so >>Yeah. And you guys making, making all the right calls at VMware. All right. More coverage. I'm shot. Dave ante cube coverage day one of three days of world war cup here in Moscone west, the cube coverage of VMware Explorer, 22 be right back.

>>mm We're entering the fourth grade era of VM ware Executive management From its beginnings in the late 90s is a Silicon Valley startup. It's five founders quickly built the company and it ended up as one of the greatest acquisitions in the history of enterprise tech when EMC bought VM ware for $625 million as a public company. But still under EMC's governance, paul Maritz was appointed Ceo in 2000 and eight and set the company on a journey to build what he called at the time. The software mainframe meaning the company's platform would run any application at high performance with low overhead and world class recovery. Pat Gelsinger took over the Ceo reins in 2012 and through organic investments and clever m and a set of course for the software defined data center and after some early miscalculations in cloud, realigned the company strategy to successfully partner with hyper scale hours and position the company for the multi cloud future. The hallmarks of VM where over the course of its history have been great engineering that led to great products, loyal customers and a powerful ecosystem. The other telling attribute of VM where is it? CEOs have always had a deep understanding of technology and its latest Ceo is no different. It's our pleasure to welcome raghu Raghuram back to the cube the fourth Ceo of VM ware and yet another Silicon Valley Ceo graduated from the IIttie rgu, great to see you again and congratulations on your new role. >>Thanks. It's great to be here. >>Okay, five months in 1st 100 days what we have focused on that journey to become the Switzerland of multi cloud, tell us about your early experience as ceo >>it's been fantastic. Uh our customers, all our employees, all our partners have been very welcoming and of course I've given me great input. What we've been able to do in the last 100 days is to really crystallize the strategy and focus it around what I'm sure we're gonna be spending a lot of time talking about. And that's about the multi cloud era of computing that most enterprises are going to go through over the next decade. And so that's really what I've been up to and you'll see the results of that in next week's uh we involved and uh where we would be talking about the strategy and some product announcements that go along with the strategy and so it's a very exciting time to be at Vandenberg. >>Yeah, I mean, I referenced it in my intro, it's almost like the light bulb went off when VM ware realized, wow, this cloud build out is just an opportunity for us and that's really what you're doing with the multi cloud as you're building on top of all the infrastructure that the hyper cloud vendors are putting out there. Maybe you can talk about that, that opportunity and what customers are telling you. >>Yeah, it's uh here is how I describe what has happened in the industry. Right, and what will happen in the industry. So, if you look at the the past decade, as cloud became a mainstream thing, most customers pick the cloud, they built their first digital applications into it, the ones that serve their mobile users or end users with digital products and that worked great for them. Then they step back and say, okay, how many modernize everything that we're doing has become a digital company. And when you go from 10, of your portfolio, 100% of your application portfolio being modernized. What has to happen is you got to go from figuring out, okay, how am I gonna put everything in one cloud to what does the application need and how do I put it on the right place? I look at the same time, the industry has also evolved from being uh predominantly supplied by one cloud provider to multiple cloud providers. At the same time, the thanks to companies like IBM where the data center has been transformed into a private cloud. The edges growing up to be its own location for a cloud sovereign clouds are going. So truly what has happened is it's become a multi cloud world. And customers are saying in addition to just being cloud first, I want to be cloud smart. And so this distributed era of computing that we are entering is what we are seeing in the industry. And what the empire is trying to do is to say, look, let's provide customers with the fastest way of getting to this multi cloud era of computing so that they can go fast, they can spend less and most importantly, they can be free, in other words, choose the right application, right cloud for right applications and have control over how they deploy and use their applications and data. That really is a strategy that we are putting in place. This is something that we've been working towards in the last couple of years now. I'm accelerating that and making that the main piece of what we end, where is doing in order to do that, we have a great opportunity to take partner even better with all of our cloud provider partners and that's where the Switzerland of the industry comes in without impending spin, especially, we have great partnership with the cloud players, great partnerships with infrastructure players. We truly can be a neutral partner to the customers as they look at all these choices and make the right choices for their applications. >>So, I want to ask you about this multi cloud when when the early multi cloud narrative came out where I go, I was saying, look, multi cloud is really multi vendor, you you've got workloads and apps running on different, different clouds. And then increasingly, the promise and your promises, we're going to abstract the underlying complexity of those clouds and we're going to give you an experience whether it's on premise, hybrid into a cloud. Across clouds. Eventually out to the edge, it's gonna be a singular, substantially identical, if not identical experience and we're going to manage the whole kit and caboodle. And how where are we in that first of all? Is that the right way to think about it? Where are we in that sort of transition from plugging into any, you know, a cloud? I'm compatible with the cloud to it's a singular sort of VM ware cloud if you will. >>Yeah. So, um, so I wanna clarify something that he said because this tends to be very commonly confused by customers use the word abstraction. And usually when people think of abstraction, they think it hides capabilities of the uh, cloud providers. That's not what we are trying to. In fact, that's the last thing we're trying to do. What we're trying to do is to provide a consistent developer experience regardless of where you want to build your application so that you can use the cloud provider services if that's what you want to use. But the deficit cops toolchain, the runtime environment, which turns out to be Cuban aires and how you control the kubernetes environment. How do you manage and secure and connect all of these things. Those are the places where we are adding the value. Right. And so really the VM ware value proposition is you can build on the cloud of your choice but providing these consistent elements. Number one, you can make better use of us, your scarce developer or operator resources and expertise. Right. And number two, you can move faster and number three can spend less as a result of this. So that's really what we're trying to do, but not. So I just wanted to clarify the word abstraction in terms of their way, we're still, I would say in the early stages, so if you look at what customers are trying to do, they're trying to build these Greenfield applications and there is an entire ecosystem emerging around Campaneris. There is still kubernetes is not a developer platform. The developer experience on top of kubernetes is highly inconsistent. And so those are some of the areas where we are introducing new innovations with our towns, our application platform. And then if you take enterprise applications, what does it take to have enterprise applications running all the time, be entirely secure, etcetera, etcetera. That's where the we ever cloud assets that are traditionally this fear based come into play and we've got this now in all of the clouds but it's still in the early days from uh on Azure and google et cetera. How do you manage and secure those things again? We're in the early days. So that's where we are. I would say, >>yeah, thank you for that clarification, I want to sort of come back to that and just make sure we understand it. So for example, if I'm a developer and I want to take advantage of, let's say graviton uh and build an app on that, that so maybe it's some kind of data intensive app or whatever it is. I can do that. You won't restrict me from doing that at the same time. If I want to use the VM where management experience across all my clouds, I can do that as well. Is that the right way to think about it? >>Yeah, exactly. So the management experience by the way, and this is the other thing that gets missed in the remember dialogue because we've been so phenomenally successful with this fear. There's a misperception that everything we are doing atmosphere today works only on top. So everything we're doing at BM wear works only on top of the sphere. That's not the case. Take management, for example, our management portfolio is modular and independent of these, which means it can manage the Graviton application that you're building, right. It can manage a traditional, these fear based application, it can manage rage application, it can manage VM based applications, can manage computer based applications. Uh so it's truly uh, overall management layer. So that is really what we're trying to do. Same thing with our kubernetes example. Right, So our communities control plane allows you to control these kubernetes clusters. Whether the clusters are utilizing gravity and whether clusters are utilizing these fear based crew binaries environments. >>Okay, that's great. So it's kind of a set up question because my next question relates to project Monterey, Because, you know, I've always said when I write about about these things, when I saw Nitro, I saw Graviton, I saw project monitor, I said uh everybody needs a Nitro Nitro or a graviton because new workloads are coming. It's not just the X 86 can handle everything anymore asap whether it's sequel server, whatever we've got new workloads that are coming ai ml data intensive edge workloads, et cetera. Is that how we should think of? Project Monterrey. Where are you in Project Monterey? Why is it so important? Help people understand that? >>Yeah. Project mantra is super exciting for a couple of different reasons. One is uh in its first iteration and uh we announced project monitoring and last being well, we continue to build and we're making great progress along with the hardware partners that we are working with um in its first hydration it allows um um some of the functions that you would expect in the software defined data center to be offloaded into these montri processors. The smart nick processes. Right. So what that does, is it clears up the core CPU for other application functions. Right, so you get better scalability, more resource utilization, etcetera, etcetera. The second thing it does is because some of the software defined data center functions are done in the smart make um it gets accelerated as well. Because it takes advantage of the special accelerators that are there security functions, manageability functions, networking functions etcetera, etcetera. So that's that what you're alluding to is overall it's the v sphere, the sX Hyper Visor complimentary itself. That's moving into the specialized processors which allows the hyper Visor will be built into these smart mix, which means the main CPU can be an intel. CPU can be an M D C P. You can be an arm. CPU can be whatever it is you want in the future. So truly enables Monte CPU heterogeneous computing. So that's that's why this is exciting. And of course because it is the sphere, it can happen in the data centers, it can happen in Carlos. It can happen in Sovereign clouds. It can happen in the public clouds all over a period of time. And >>and potentially the Edge I would presume in the future. >>Sorry. Yeah, that's a great point. Thanks for pointing that out. In fact, the Edge is one of the most important places that will happen because we need these low latency applications such as in the telco case for example, right. Or we need these applications that have specialized processing the required. If you're setting up a cashier less store and you need to process and you need a lot of influence engines. So, Monterey helps with all of those things. >>I want to make sure our audience understands. It's because the software defined data center was awesome but but it also created waste in the sense that you have all these offload functions in storage and networking and security running on on x 86 processors which may not be the most efficient way. So emerging architectures around arm might be less expensive, maybe more cost effective, lower power. Uh maybe they do memory management differently. So there are these offload use cases. But as well you we talked about the edge there could be a lot of edge use cases that or whatever whether it's arm or in video etcetera. So now you're driving that optionality for customers so you can support more workloads of the future. >>Yeah, so this is exactly if you think about in europe when you talked about the embers evolution, the inverse core DNA has always been to master hydrogen. Itty right. And what we're seeing is this world of heterogeneous hardware coming alive. Right. You talked about Professor hydrogen Itty including GPU chips and so on. There is a memory architecture heterogeneous, their storage architecture heterogeneous. And so the idea is that regardless of what you use, how do you provide the best workload platform and a consistent way of managing all of these things and reducing the complexity while gaining the efficiency benefits and the other benefits that you talked about. >>So speaking of geniality that brings me to Tansu, you know early on people thought, oh wow containers, that's gonna kill VM where this is the opposite happened. You guys leaned in as as you have as a sign of great leadership these days. You don't get defensive, you just, you know, get the trend is your friend, as they say, give us the update on on Tan xue. Why is that so important to the future? >>Yeah. So if you look at any enterprises portfolio right, they are looking at it and saying look, there's a whole set of applications that I need to modernize. Now. The question becomes how do you modernize these applications in a way that it is essentially done with these microservices architectures and so on and so forth. In that context, how do I maximize the developer productivity and provide a great developer experience because there is not enough developers in the world to modernize every application that that's in every enterprise. Right. So, Tan xue is our answer to help enterprises modernize their applications and deliver in a way that the developed makes the developers very productive on the cloud of their choice. So that is really the strategic intent of Tancill and the core building block for Tan xue is of course kubernetes as you well know, Kubernetes has become the common infrastructure abstraction across clouds. So if you want portability for traditional VM based applications, he used this fear, if you want portability for traditional for containerized microservices applications, you assume kubernetes, that's how companies companies are thinking about it. And so that's the first thing that we did now. The second is you've got developers building applications all over the place. So now, just like you used to have physical server sprawl and now and then VM sprawl these days you have cluster sprawl, kubernetes, cluster sprawl and tons of mission control affects as a multi cloud, multi cluster kubernetes control plan works on the chaos and everything else that some of the Sun. The third point of Tanzania is the developer experience and we have introduced Andrew application platform, which is really focused on delivering a great developer experience on top of any Cuban Aires. So that's really how we're building out the towns of portfolio. And then of course we got Spring and uh as you well know a majority of enterprise applications today are java and if you want to modernize java, you use spring boot and so we had tremendous success with our uh spring boot technology and our startup, Springdale Ohio capabilities and so on and so forth. So that's the entirety of the towns of portfolio. It's multi cloud, it's kubernetes agnostic. Of course it runs great on this fear but it's really the approach making developers productive in the enterprise >>awesome. Thank you for that. I know we're tight on time but it's like speed dating with you raghu. So I'm gonna go on to another topic. Really important topic of security, you've made obviously some big acquisitions, there are things like carbon black, you've got a lot of stuff going on with, with, with endpoint, with end user computing, I'm first interested in sort of how you organize it looks like you're putting security and the networking piece together and then what's your swim lane? It seems like you're, you're focused obviously on your infrastructure. You're not trying to be all things to all people. Help us understand your strategy in that regard. >>Yeah, I mean security is a massive space, Right? And you covered very well. Hundreds and thousands of security problems that customers want to be solving. What we are focused on is how do we simplify the security problem for the customers? And we're doing it through three wells. The first one is we are baking security into the platforms that customers used ones. Right. But there are more obvious fear our workspace one, our container platform etcetera, etcetera. Right? Cloud platforms. So that's the first thing that we're doing. The second is we are putting um, bringing together, we're taking an end to end view of security, which is everything from an end user connecting from home to the corporate network or the sassy, sassy applications to the Windows devices they are using to the data center applications they're using to the club. Right? So we're taking a holistic view of security. So which means we want to combine our network security assets with our endpoint security assets with our workload security assets. That is why we bought all of those things together under one roof. And the third is we are instrumental in all of these and collecting signals from all of these and pulling it into the cloud and turning security into a machine learning and the data problem, right? And that is where the problem. Black cloud comes in and by doing that, we are able to provide a holistic view of where uh customer security posture, right? And these sensors can be on BMR platforms, on non BMR platforms etcetera. And so so that's really how we are approaching it. I mean there's the emerging industry term for a policy XDR. You might follow that. So that's really what we're trying to do. >>Outstanding. Last question and I know, I know we got to go. You mentioned the spin that's happening in november. That's an exciting time for a lot of reasons. I think the ecosystem, you know, emphasizing your independence but also gives you control of your balance sheet, regaining control of your balance sheet, tongue in cheek there. But it's important because all this, this cloud build out this multi cloud, exposing the primitives, leveraging the primitives and the A. P. I. S. Of these clouds making them identical across all these estates. That's not trivial and you're obviously gonna need resources to do that. So maybe you can talk about that and how you see the future playing out organic inorganic, maybe a little lemon A in there. What's your approach? How are you thinking about that? >>Yeah. So we are very excited with the impending spain, which like you said is on track to happen early november. Um and if you think about the spin, there are three aspects that we are excited about. The first aspect is uh we have a great relationship with Dell Tech, the company right. What we have done is we have codified that into a framework agreement that covers the gold market and technology collaboration and we are super excited by that and that baselines against what we do today and then as incentives on both sides to continue to grow that tremendously. So we're gonna continue being, doing that and that's going to continue being a great partner at the same time. From a partnership point of view, is truly going to be a Switzerland of the industry. So previously companies that were otherwise a little bit more competitive with dull now no longer have that reservation in partnering very deeply with us. I'm totally, like you said from a capital structure point of view, it gives us the flexibility to use to do em in a should we decide to do so in the future right? And use both equity and cash for them in a so so that's the capital structure, flexibility, the Switzerland positioning and the continuing great relationship with dull Those are the benefits of the spin >>love and the partner ecosystem has always been a source of, of innovation and it's a big part of the flywheel, the power of many versus the resources of one Ragu, Thanks so much for coming back in the queue. Best of luck. We're really excited for you and for the future of VM ware. >>Thank you and thanks for all the great work that you do and look forward to continuing to read your great research, >>appreciate that. And thank you for >>watching the cubes, continuous >>Coverage of VM World 2021. Keep it right there. >>Thank you. Mhm. Yeah.

>> [Narrator] From San Francisco, it's theCUBE. Covering Radio 2018, brought to you by VMware. >> Hey, welcome back everyone. This is theCUBE's exclusive coverage of Radio 2018. We are in San Francisco for their VMware's Radio 2018. It's their R&D fiesta, party. As Steve Harris said, former CTO, it's like a sales kickoff for engineers. It's a great time, but it's also serious. A lot of real serious discussion and of course people are flexing their technical muscle and stretching their minds. And I'm here with one of the chief operator, one of the main principals and legend in VMware, Raghu Raghuram. Chief Operating Officer, new title. Chief Operating Officer, Products and Cloud Services. >> That's right. >> Great to see you. >> Great to see you, John. >> What year did you join VMware? >> 2003 (chuckling) >> 15 years >> So, you've seen many of these radios. >> Yes, it's one of the highlights of the year for me. >> Yeah, super important architect of VMware, great part of the community, leader, architect of the AWS relationship. >> [Raghu] Sure >> Part of that movement with Andy Jassy, Sanjay Poonen. This is the 14th year of radio and VMware has changed a lot since you joined. It's now a world class organization. Getting check marks for one of the best places to work. Certainly for engineers it's like a great party environment. Take a minute to explain the radio culture, it's 14th year, there's t-shirts behind us, to commemorate the key milestones, where it's come from, where it's gone, your thoughts on the program and the community. >> Yeah, I mean this is in fact one of the unique characteristics of VMware. I have checked around with my peers in the industry and I don't think any other tech company of our size does this. Radio stands for R&D innovation offsite. Like you said, we started fourteen years ago just to take a bunch of engineers out from their daily grinds and say, "what could we be building fundamentally that's groundbreaking?" So, I would say it's a cross between a wild science fair and a research conference. In fact, both of these go hand in hand at this place. People publish papers and there is a selection committee just like in serious conferences. In fact, Ray had some amazing stats for this year's submissions and the selection is very very rigorous. At the same time, you'll go upstairs and you'll see the exhibition hall where there are all kinds of things that are displayed. Things that could be very well incremental things in the next release and things that are wild and wacky off the wall that we might never ever do. So, it's really the full gamut. Another interesting thing is we've gone bigger. We are getting people from pretty much all parts of the Emirate. I think there is representation from 25 companies. >> [John] How many engineering centers are there roughly? I mean, there's core centers and then you have engineers all over the world. How many engineers, ballpark? >> I would say, in terms of medium to big size centers, there are probably over a dozen across the globe and literally every continent. Clearly, in the US we have four big centers. In Europe, we have three at least. In Asia, we have another three or four. So, we definitely have over 10. >> I mean everyone who knows the VMware and also knows theCUBE, for nine years, well this is our ninth year covering VMworld, all you gotta do is look at VMworld and you can tell one thing right out of the gate. Very community oriented. All the decisions are made in the community. Also, people who know VMware know you're highly an engineering organization. >> [Raghu] Yep. >> This is not like a lot of marketing fluff. Although, you do have some good marketing here and there, but the point is it's an engineering culture with community. This is unique. I've seen companies that don't walk the talk on "community engineering". They have silos, there's a lot of infighting. How have you- How has VMware preserved a culture of innovation amongst their peers when it's competitive as hell inside VMware? One to be smart, achieve the success. But, also, VMware has always been in always a moving market. How do you guys do it? What's the secret sauce? >> I mean, there's not a single thing. Like you said, culture is something that happens over time and is preserved over time and is preserved through people. It's not like anything you can write down, right? Of course you can write it down. But, it won't be worth the paper it's written down on unless it's practiced everyday by other people. And so, I think that is the key thing here. Right from the get go, customer centric innovation has ruled the rules here. So, the question to ask always is great innovation, look at it from a customer end point of view. I think that matters a lot here. Secondly, there is a lot of emphasis on breaking the rules in terms of doing something disruptive, right? And, the engineers that come here tend to be the kind to respond to that, right? And then lots of venues. Like this is not the only thing that we do, right? We do these things called borathons, which is our internal version of hackathons. We do regional versions of these things. Each of the teams, like the business units, have their own little R&D innovation activities that go on. >> They have a playground. They can basically go outside the scope of their job. >> Exactly. >> Get an idea, a passion, an idea and go after it and not have to worry about anything. >> Yup, exactly. >> [John] With a path to commercialization, if it hits. >> Yeah, that's what I was gonna say. We have a fairly high success rate, I would say, of taking things that we see here and turning them into product and eventually into monetizable businesses. All the things that go into the product features. >> Give some examples of historically, successes, notables, and then also talk about some ones that aren't notable that have come out. I know a lot has come out of this, the numbers are clear. What are some highlights that have come out of the radio event that have been blockbuster successes? >> A lot of the things that you see in the networking today came out of radio. Things about doing security and networking from the hypervisor up, came from here. What you see today as vSAN, had its roots here. What you see today with the app defense and the security stuff, had its roots here. A lot of the features that are in vSphere today, especially the storage vMotion and so on and so forth, was first showcased here. This goes on and on and on. We also have a lot of things that have shown up here that we have not pursued. For example, almost like an eBay for VM capacity. We didn't pursue it. God knows, that could've been a huge idea. (laughing) >> It's the misses too. >> Yeah, there's the misses too. But, that's the whole point of this. >> Yeah. There's parts to creativity. How much creativity goes on at this event? I mean there's certainly a lot of barnstorming, brainstorming, or whatever you wanna call it. A lot of interaction, physical face to face. How much creativity is happening you think here? >> Yeah, so a few years back they introduced a couple of things. One is a instant birds of a feather. Where you can literally go to a whiteboard and say, "hey let's discuss this topic," and set up a time and then people show up. There's this other one they call Lightning Rounds, which literally happens over drinks I think tomorrow or something. Where people come in and it's lots of the mini gauntlet where nothing is scripted. All sorts of crazy ideas keep flowing. I would say those are two examples where there's a lot of on the spot creativity. As a company, the R&D teams have gotten more dispersed. This is the opportunity for people to get together even within the same business unit or across business units and say let's go solve this problem. You and I have been talking about this on email, let's talk about it face to face. Hey, let's bring somebody else in that's relevant to this conversation as well. So, those are the kind of things that go on here that spark the creativity. And then of course, the exhibits. When people start thinking about these exhibits and talking to people that are showing there, other ideas get spawned off as well. >> Raghu, talk about just from your experience, you got a great track record, and certainly it was in VMware, it goes back to the early 2000s. What is your observation on the innovation formula? What's been the consistent constant of innovation? As the waves have changed- I mean, I've been in Palo Alto for 19 years now, in my 20th year. Even Palo Alto's changed. So, the world's changed, modern. And we'll get to the Amazon deal in a second. Certainly cloud's here. What have you seen as the constant innovation variable? >> What I would say is this. Fundamentally the people that we tend to recruit into VMware are by large what we call, or at least I call, platform thinkers. So, they think of building a fundamental piece of technology that can be possibly be used in 10 different ways, and they build it for one particular use case. And then, the questions goes back to, now we've done this, what else can we do with this foundational technology? If you look at vSphere, does the same thing. If you look at networking, same thing. Storage is the same thing. So, I would say that is the constant. That's one constant here. Which is, how do you build fundamentally a platform that could be used in very different ways. >> Some will also say systems thinking. >> Exactly, so that's a compliment. >> The cloud is a system. >> (mumbles) I think Paul Maritz is a 2010 picture. Although, some of the calls didn't come out. He kind of generally had the architecture. >> Yeah, yeah >> He nailed it (laughs) >> There are a few people like Paul in the world and absolutely he nailed it. >> Dave and I would give him a lot of credit for that. Okay, let's talk about Amazon Web Services. Certainly Radio's now 14th year. At what point did the cloud start clicking in? You said there's some misses, the eBay for VMs. Certainly cloud is on the radar. >> Yeah >> And vCloud, we know what happened there. Pat talked about how you guys really took that opportunity, which is, you made lemonade out of some lemons there with that product. That's my words, not his. When did cloud first appear on the horizon in Radio and how do you see that happening now as we talk multi-cloud? >> You missed the alumni session today. One of the early engineers said when he was interviewed by Mendel, which was in 1999, Mendel is of course the founder and first chief scientist here. He said he foresaw the event. When the engineer asked him, "how are we gonna make money on this?" He thought there would be a day when people just rent computer capacity from a data center instead of going out and buying gear. In some ways- >> He predicted >> He predicted >> Cloud operations >> Back in the company's starting days. But really I think we saw this in 2005, 2006, 2007. At the same time actually as Amazon saw this. But, the big difference was we were growing 100% a year on core business and we had our hands full that way. We felt like as a software company the way to play it was by delivering technology to other people to build it. So, that's when it really made it's way here, in Radio and in the products. >> And by the way, it wasn't obvious to many people in the industry at that time, to Amazon. I've had many conversations with Andy Chassy and he now uses the term being misunderstood. They were completely misunderstood unless you were an entrepreneur who was using EC-2 just to avoid seed money. 'Cause it was a dream for entrepreneur's at that time. I remember that clearly. That was not obvious. It really wasn't obvious until about 2010, nine, 10. So you guys were growing. Missed that. Radio is not about missing it. It's about identifying. >> Exactly. >> So, how does it translate today for Amazon? >> The Amazon relationship, if you think about the technical underpinnings of it, clearly we did a vCloud error. We learned a lot on that. Within some of our engineers, the question that was asked was, "what if we could run a cloud on top of other peoples clouds?" And we did experiments with nested virtualization. We did experiments with bare metal. And then we chose the start of our model. So, that's one of the technical early indicators of what we could do on other people's clouds. So, that's a big thing. The rest of the things we're doing with respect to elastically growing capacity and all those things, came from experiments that were shown up here. So, that was the connection back to Radio. In terms of the Amazon partnership itself, a lot of it was driven from the customer end. As we were thinking about VCN not working the way we wanted it to work, we went back to the customers and said, "what is wrong with this picture?" And, the answer that came back was very clear. They said, we like the hybrid idea, but we want the hybrid to be VMware on prem and Amazon in the cloud because 70% of our customers turned out to be AWS customers. And at the same time AWS was hearing the same thing. Why don't you guys team up instead of being either or? That's what led to the partnership. >> Your team at VMware came as the cloud native piece? >> Yeah >> Aspect of it. So Kubernetes is on the horizon. Not on the horizon, in your face. And you've got service mesh over the top. >> Yep, yep >> That's up the stack. It's networking. >> Yep, exactly. >> Still needs to do networking. >> Yeah, exactly. >> It's like, you guys must be like, hey we love what's going on up there. Come down to the store. >> Yeah. So, the boundary between what is application platform and infrastructure platform is constantly changing. Kubernetes, when it started out people said oh it's an application platform. Now it turns out its actually infrastructure. Same thing in networking. So what we see is, things were the lower level of the infrastructure constructs, the same idea is applied at the next level up. That's why we love Kubernetes. We love Service Mesh. We love similar concepts that are coming about in storage and security it's one- >> A unified stack is coming. >> Yep, exactly. >> Just someone fix networking and then the holy grail, programmable networks. >> Yep >> When are they coming? >> At the application level. >> Let's go >> Yeah >> Holy grail is finally here. It's not where you thought it was gonna be. >> It is at both places, right. I mean, it's tying back to the conventional layer, two layer, three stuff because that's also important still. >> Raghu, I love having a chat with you. It's great to chat. >> Good to see you again John. >> Super impressive with the work you've been doing. Love the cloud deal with Amazon, you know that. Love what's going on at Kubernetes and containerization. Love what's going on with Service Mesh, unified stack. Love cryptocurrency, which I didn't get to ask you. >> Yep >> Thumbs up? >> Crazy things going on there too >> Thumbs up, okay, thumbs up. >> We're watching the cryptocurrency. >> Watching, token economics coming right behind it. It's theCUBE bringing you all the action here at Radio. We're the signal. 2018, Radio 2018. I'm theCUBE with Raghu. I'll be right back with more coverage after this short break. (upbeat music)

>>The cute presents on the ground. Here's your host, John furrier. >>Hello, I'm John foray with Silicon angle media, the cube, and we are here for an Inn at the Ritz Carlton in San Francisco for the special exclusive press event with Andy Jassy. And the special announcement was Pat Gelsinger, CEO of VMware announcing what, in my opinion is probably the biggest, most historic announcement in the industry. And certainly for VMware as the future migration to the cloud migration of the next generation infrastructure continues. Uh, and so big, significant as exclusive. I'm having a one-on-one interview with Andy and Pat shortly, but I had a chance to grab the chief architect of this deal. One of the many that the lead EVP and general manager. So I don't think it's an, a Ragu Ragu Ragu around welcome, uh, to see, great to see you. Thanks for spending the time to see you. Thanks. So Ragu you're, you're an old timer VMware, but now you're also architecting. What looks to be the bridge to the future for VMware? Um, this relationship with AWS, Amazon web services puts VMware in the cloud the best, the best, most functional best, biggest public cloud, and most robust capabilities immediately in Amazon available mid 2017. But this is a path instantly for all of the and where customers, um, what's when did this all start and what motivated you to architect this? >>Yeah, I mean, um, as you recall, the past VMware, we announced our cross-cloud architecture and the idea that customers, enterprise customers want choice with control, right? The legwork for that was done, um, over a year ago, right? When we internally, we finalized our strategy to enable our platform to run in multiple different, uh, clouds, such as our weekend partner network and IBM and now AWS. So that's when we all started around this. But the key idea here is for customers that are increasingly putting a variety of workloads from the, in their private cloud, in their public cloud, you want to have a consistent way of running and managing and securing and operating these applications. And as you just pointed out, one of the biggest cloud providers for our customer is AWS. And so this was a natural partnership from that point of view. >>So one of my favorite tweets out there for us from, you know, obviously Dave Alante co-host of the cube, he said, um, please allow me to translate. He was translating from a customer, went help our customer impact one. You've squeezed the blood from the data center stone with virtualization. You've done all you can. This is my customer translation, too. You have, um, a legacy amount of VMware processes and procedures and software, AKA VMware, three year Jones, and for the agility and innovation of AWS, come on in the water's nice and warm. So essentially it's kind of tongue in cheek, but you know, the data center is, has been maxed out. So data center consolidation, certainly people don't want to be in the data center business, but they want the benefits of a data center with the cloud. You guys are not providing that. What is the impact to customers because they are jonesing for innovation that Jones and from microservices, they're jonesing for cloud native, that Jones and for the, some of the goodness that Amazon has shown works, but yet it's a huge migration nightmare and they want a SAS business model. They want a SAS company. This is the digital transformation. What is the impact of customers? >>Yeah, I mean, it's ultimately comes down to simplicity and agility, right? And the, there is two big transformations going on. One is there's a huge data center transformation going on, driven by simplicity, driven by software. And that is the whole software defined data center while you're absolutely right. Many of our customers have maxed out the server virtualization, but their network is inefficient and the storage is efficient, et cetera, et cetera. So the software defined data centers, one of the moves they're making now at the same time, like you said, they're jonesing for all these advanced services, uh, for their new applications. Uh, they want some way to bridge both environments. And that's where this service, uh, hits the sweet spot. If you will, right now, without replatforming, without changing your operational models, like your quote that you, the tweet that you quoted without changing any of our operational models, you can have an agile on demand of VMware data center. And what's running in that VMware data center is the full software defined data center stack, all of the great security and manageability capabilities of networking, of NSX, of virtual San, of vSphere at the same time, connecting to all these great services that AWS provides. It's really a best of both worlds story. >>So look from a customer standpoint, if I get this right, there's a big breathing out. Oh, finally, he got there, right? It's I don't have to do all this heavy lifting to move my VMware to the cloud. One, two in the demo that we show in V center. So specifically under the hood, what is running in the full stack? I mentioned V motion. I heard V motion mentioned. Is it all, all of the entire VMware stack running on the cloud? >>Yes. So the stack that's powering that, that you saw in the demo is a virtual sun watch lies in the storage underneath, um, NSX, providing the network virtualization. And of course, vSphere that's the core infrastructure stack. And in order to manage an ESX nodes for the hypervisor in order to manage ESX and control these resource pools and so on, you have the vSphere functionality built into V-Center. And that was a key requirement. Design requirement for this service is customers are very, very familiar with V-Center. They've been operating it for 15 years and have that as a huge ecosystem of tools, operational tools, backup dual security tools, you name it built around V-Center and all of that had to work seamlessly in the cloud. And that's why we sent her is so important. >>And certainly got a lot helps with the storage side of it. You mentioned networking, how does the Amazon relationship and the co-located if you want cold locating, but running managed in AWS help on the networking because in the demo, it was very cool besides the pay by credit card and pay by VMware account was the fact that you can pick a global footprint instantly, which means from what I took away, was it, I can be up and running in a geography with networking in the cloud, but not just Amazon's networking, you're networking. Absolutely. That's that accurate? You got it. Right. >>So, um, Amazon obviously has got a global network fabric that powers their services. And so you can stand up these clusters of the STDC hardware, if you will, on any one of their data centers in the fullness of time, maybe not on day one. And NSX already has the capability to connect across STDC clusters across different data centers. So now we can stretch a logical network, um, and have literally applications in the Portland data center of AWS and, uh, applications at the Virginia data center of AWS and applications in their London data center, all tied together, biological network. >>All right. So I'm going to ask some hard questions down so densely, by the way. So here's the hard question. So here's the hard question. So Paul Moritz and Joe Tucci no longer involved Maritz, retired, Tucci, retired, he wanted to own the enterprise. The private cloud was the original thing. Amazon was just kind of getting strong lift at that time. The world has gone all hybrids. There's a lot of hybrid cloud going around. So the world is different from them. So I want to get your comments on where the private cloud has came from to this reality and to comment to the naysayers out that I've heard some tweets like, Oh, rip VM-ware, they rang the bell, they tapped out, they capitulated talk about those two dynamics, private cloud, that vision, uh, from Mauritson Gelsey, uh, to cheek. And how do you answer the critics to say, Oh, they capitulated VMware's toast. >>Yeah. So, um, what the, uh, I would say are significantly incorrect views of how you look at this. The private cloud is still very strong, right? And you've got customers deploying the private cloud, literally every large enterprise that we talked to and we've got the leading share when it comes to private cloud deployments. And along with pivotal cloud Foundry, we can offer not just the infrastructure services of a private cloud, but also the application platform services of the private cloud or the private cloud exists for lots of different reasons can be regular. >>It's not done. The cloud is not going away anytime soon. What >>This allows customers to do is really get a hybrid that combines the best of a VMware environment or the best of an AWS. And that's really, what's unique. And what is in the service is the full VMware stack. And you've got to remember that 95% of our customers are still largely on vSphere. They've just started deploying and adopting NSX and virtual sand by adopting this service, they automatically get upgraded to the full power of network virtualization and storage virtualization. >>Of course. So you see this as an expansion of the business model, not anything I see complete expansion of the business model, that's going to come from SAS apps or, yep. >>So the whole service is a mad at service. So customers are not have to learn how to sort of rearchitect their data center. They can just get a rearchitected data center on demand wherever they want, or they can build the rearchitecture data center by themselves and connect it all up. Right. >>Okay. Final question. I'll see. Um, I'd love to chat more about what it's like cut this deal with Amazon fan of both of you guys. Um, actually we use Amazon work customer. Um, talk about your relationship with other clauses comes up with the press. People who are, you know, not as deep on, on the, on the industry they talk about IBM, Oh, it was IBM and Azure Azure. We can see that as competitive thing. I don't want to want to go there because we're going to do a whole blog post on the impact of Microsoft, which I think is the big competitor for us, for customers. But you guys have an open cloud strategy. And I think the IBM thing is let them compete. Now they have soft layer. Now some would argue Amazon, Andy talked about the relationship with them, the soft layer and how they compete. But ultimately IBM is deep with you guys. They're adding 20,000 developers. I think million people, which 4 million people trained highly integrated with VMware. So your strategy with them is the same, right? But primarily as a service operating on Amazon, are you guys going to be operating on soft layer and blue mix as well in a similar fashion? >>So, um, the service that we announced, uh, last month with IBM is a service that IBM is managing and operating, right? And we have worked very closely with them, the VMware cloud foundation, >>Just their business model. They're going to operate that you guys will operate the AWS cloud. >>We operate the VMware and IBM operates that service, but we go to market together with IBM on their service, right. And we work very closely with them. >>So this is a choice thing for you guys, as nothing to do with picking a better part, I'll even use the word primary. Okay. >>I mean, like Pat talked about, uh, the QA session, we've had lots of customers that are customers of AWS and for them, the first choice might be the VMware cloud on AWS. We equally got a lot of customers that are customers of IBM and for them and software and for them, uh, the choice would be running their on the IBM cloud with the cloud. >>Thanks for taking the time to speak with us. I'll give you the final word, not on the business side, cause it's pretty obvious. It's a good win-win on the business side. What is the coolest technical under the hood thing about this deal that people should know about? >>I think what AWS has engineered to build a service and how we are taking advantage of it for Delaware and elastic data centers across the globe is going to be very, very cool. Once you can talk more about it in a public domain >>Raku he's he had a, vice-president great to see you, a chief architect of this deal among many other things at VM-ware well-known within the industry legend in the, uh, VMware community. Thanks for joining us here on the non live Q, but we're here in San Francisco for the exclusive announcement of the AWS VMware relationship partnership integration. A lot of glad of goodness there. I'm John Ferrari. Thanks for watching.

(intro music plays) >> Okay, welcome back to Supercloud 2. I'm John Furrier with my co-host, Dave Vellante, here in our Palo Alto Studio, with a live performance all day unpacking the wave of Supercloud. This is our second edition. Back for keynote review here is Vittorio Viarengo, talking about the hype and the reality of the Supercloud momentum. Vittorio, great to see you. You got a presentation. Looking forward to hearing the update. >> It's always great to be here on this stage with you guys. >> John Furrier: (chuckles) So the business imperative for cloud right now is clear and the Supercloud wave points to the builders and they want to break through. VMware, you guys have a lot of builders in the ecosystem. Where do you guys see multicloud today? What's going on? >> So, what we see is, when we talk with our customers is that customers are in a state of cloud chaos. Raghu Raghuram, our CEO, introduced this term at our user conference and it really resonated with our customers. And the chaos comes from the fact that most enterprises have applications spread across private cloud, multiple hyperscalers, and the edge increasingly. And so with that, every hyperscaler brings their own vertical integrated stack of infrastructure development, platform security, and so on and so forth. And so our customers are left with a ballooning cost because they have to train their employees across multiple stacks. And the costs are only going up. >> John Furrier: Have you talked about the Supercloud with your customers? What are they looking for when they look at the business value of Cross-Cloud Services? Why are they digging into it? What are some of the reasons? >> First of all, let's put this in perspective. 90, 87% of customers use two or more cloud including the private cloud. And 55%, get this, 55% use three or more clouds, right? And so, when you talk to these customers they're all asking for two things. One, they find that managing the multicloud is more difficult than the private cloud. And that goes without saying because it's new, they don't have the skills, and they have many of these. And pretty much everybody, 87% of them, are seeing their cost getting out of control. And so they need a new approach. We believe that the industry needs a new approach to solving the multicloud problem, which you guys have introduced and you call it the Supercloud. We call it Cross-Cloud Services. But the idea is that- and the parallel goes back to the private cloud. In the private cloud, if you remember the old days, before we called it the private cloud, we would install SAP. And the CIO would go, "Oh, I hear SAP works great on HP hardware. Oh, let's buy the HP stack", right? (hosts laugh) And then you go, "Oh, oh, Oracle databases. They run phenomenally on Sun Stack." That's another stack. And it wasn't sustainable, right? And so, VMware came in with virtualization and made everything look the same. And we unleashed a tremendous era of growth and speed and cost saving for our customers. So we believe, and I think the industry also believes, if you look at the success of Supercloud, first instance and today, that we need to create a new level of abstraction in the cloud. And this abstraction needs to be at a higher level. It needs to be built around the lingua franca of the cloud, which is Kubernetes, APIs, open source stacks. And by doing so, we're going to allow our customers to have a more unified way of building, managing, running, connecting, and securing applications across cloud. >> So where should that standardization occur? 'Cause we're going to hear from some customers today. When I ask them about cloud chaos, they're like, "Well, the way we deal with cloud chaos is MonoCloud". They sort of put on the blinders, right? But of course, they may be risking not being able to take advantage of best-of-breed. So where should that standardization layer occur across clouds? >> [Vittorio Viarengo] Well, I also hear that from some customers. "Oh, we are one cloud". They are in denial. There's no question about it. In fact, when I met at our user conference with a number of CIOs, and I went around the room and I asked them, I saw the entire spectrum. (laughs) The person is in denial. "Oh, we're using AWS." I said, "Great." "And the private cloud, so we're all set." "Okay, thank you. Next." "Oh, the business units are using AWS." "Ah, okay. So you have three." "Oh, and we just bought a company that is using Google back in Europe." So, okay, so you got four right there. So that person in denial. Then, you have the second category of customers that are seeing the problem, they're ahead of the pack, and they're building their solution. We're going to hear from Walmart later today. >> Dave Vellante: Yeah. >> So they're building their own. Not everybody has the skills and the scale of Walmart to build their own. >> Dave Vellante: Right. >> So, eventually, then you get to the third category of customers. They're actually buying solutions from one of the many ISVs that you are going to talk with today. You know, whether it is Azure Corp or Snowflake or all this. I will argue, any new company, any new ISV, is by definition a multicloud service company, right? And so these people... Or they're buying our Cross-Cloud Services to solve this problem. So that's the spectrum of customers out there. >> What's the stack you're focusing on specifically? What is VMware? Because virtualization is not going away. You're seeing a lot more in the cloud with networking, for example, this abstraction layer. What specifically are you guys focusing on? >> [Vittorio Viarengo] So, I like to talk about this beyond what VMware does, just 'cause I think this is an industry movement. A market is forming around multicloud services. And so it's an approach that pretty much a whole industry is taking of building this abstraction layer. In our approach, it is to bring these services together to simplify things even further. So, initially, we were the first to see multicloud happening. You know, Raghu and Sanjay, back in what, like 2016, 17, saw this coming and our first foray in multicloud was to take this sphere and our hypervisor and port it natively on all the hyperscaling, which is a phenomenal solution to get your enterprise application in the cloud and modernize them. But then we realized that customers were already in the cloud natively. And so we had to have (all chuckle) a religion discussion internally and drop that hypervisor religion and say, "Hey, we need to go and help our customers where they are, in a native cloud". And that's where we brought back Pivotal. We built tons around it. We shifted. And then Aria. And so basically, our evolution was to go from, you know, our hypervisor to cloud native. And then eventually we ended up at what we believe is the most comprehensive multicloud services solution that covers Application Development with Tanzu, Management with Aria, and then you have NSX for security and user computing for connectivity. And so we believe that we have the most comprehensive set of integrated services to solve the challenges of multicloud, bringing excess simplicity into the picture. >> John Furrier: As some would say, multicloud and multi environment, when you get to the distributed computing with the edge, you're going to need that capability. And you guys have been very successful with private cloud. But to be devil's advocate, you guys have been great with private cloud, but some are saying like, you guys don't get public cloud yet. How do you answer that? Because there's a lot of work that you guys have done in public cloud and it seems like private cloud successes are moving up into public cloud. Like networking. You're seeing a lot of that being configured in. So the enterprise-grade solutions are moving into the cloud. So what would you say to the skeptics out there that say, "Oh, I think you got private cloud nailed down, but you don't really have public cloud." (chuckles) >> [Vittorio Viarengo] First of all, we love skeptics. Our engineering team love skeptics and love to prove them wrong. (John laughs) And I would never ever bet against our engineering team. So I believe that VMware has been so successful in building a private cloud and the technology that actually became the foundation for the public cloud. But that is always hard, to be known in a new environment, right? There's always that period where you have to prove yourself. But what I love about VMware is that VMware has what I believe, what I like to call "enterprise pragmatism". The private cloud is not going away. So we're going to help our customers there, and then, as they move to the cloud, we are going to give them an option to adopt the cloud at their own pace, with VMware cloud, to allow them to move to the cloud and be able to rely on the enterprise-class capabilities we built on-prem in the cloud. But then with Tanzu and Aria and the rest of the Cross-Cloud Service portfolio, being able to meet them where they are. If they're already in the cloud, have them have a single place to build application, a single place to manage application, and so on and so forth. >> John Furrier: You know, Dave, we were talking in the opening. Vittorio, I want to get your reaction to this because we were saying in the opening that the market's obviously pushing this next gen. You see ChatGPT and the success of these new apps that are coming out. The business models are demanding kind of a digital transformation. The tech, the builders, are out there, and you guys have a interesting view because your customer base is almost the canary in the coal mine because this is an Operations challenge as well as just enabling the cloud native. So, I want to get your thoughts on, you know, your customer base, VMware customers. They've been in IT Ops for generations. And now, as that crowd moves and sees this Supercloud environment, it's IT again, but it's everywhere. It's not just IT in a data center. It's on-premises, it's cloud, it's edge. So, almost, your customer base is like a canary in the coal mine for this movement of how do you operationalize multiple environments? Which includes clouds, which includes apps. I mean, this is the core question. >> [Vittorio Viarengo] Yeah. And I want to make this an industry conversation. Forget about VMware for a second. We believe that there are like four or five major pillars that you need to implement to create this level of abstraction. It starts from observability. If you don't know- You need to know where your apps are, where your data is, how the the applications are performing, what is the security posture, what is their performance? So then, you can do something about it. We call that the observability part of this, creating this abstraction. The second one is security. So you need to be- Sorry. Infrastructure. An infrastructure. Creating an abstraction layer for infrastructure means to be able to give the applications, and the developer who builds application, the right infrastructure for the application at the right time. Whether it is a VM, whether it's a Kubernetes cluster, or whether it's microservices, and so on and so forth. And so, that allows our developers to think about infrastructure just as code. If it is available, whatever application needs, whatever the cost makes sense for my application, right? The third part of security, and I can give you a very, very simple example. Say that I was talking to a CIO of a major insurance company in Europe and he is saying to me, "The developers went wild, built all these great front office applications. Now the business is coming to me and says, 'What is my compliance report?'" And the guy is saying, "Say that I want to implement the policy that says, 'I want to encrypt all my data no matter where it resides.' How does it do it? It needs to have somebody logging in into Amazon and configure it, then go to Google, configure it, go to the private cloud." That's time and cost, right? >> Yeah. >> So, you need to have a way to enforce security policy from the infrastructure to the app to the firewall in one place and distribute it across. And finally, the developer experience, right? Developers, developers, developers. (all laugh) We're always trying to keep up with... >> Host: You can dance if you want to do... >> [Vittorio Viarengo] Yeah, let's not make a fool of ourselves. More than usual. Developers are the kings and queens of the hill. They are. Why? Because they build the application. They're making us money and saving us money. And so we need- And right now, they have to go into these different stacks. So, you need to give developers two things. One, a common development experience across this different Kubernetes distribution. And two, a way for the operators. To your point. The operators have fallen behind the developers. And they cannot go to the developer there and tell them, "This is how you're going to do things." They have to see how they're doing things and figure out how to bring the gallery underneath so that developers can be developers, but the operators can lay down the tracks and the infrastructure there is secure and compliant. >> Dave Vellante: So two big inferences from that. One is self-serve infrastructure. You got- In a decentralized cloud, a Supercloud world, you got to have self-serve infrastructure, you got to be simple. And the second is governance. You mentioned security, but it's also governance. You know, data sovereignty as we talked about. So the question I have, Vittorio, is where does the customer start? >> [Vittorio Viarengo] So I, it always depends on the business need, but to me, the foundational layer is observability. If you don't know where your staff is, you cannot manage, you cannot secure it, you cannot manage its cost, right? So I think observability is the bar to entry. And then it depends on the business needs, right? So, we go back to the CIO that I talked to. He is clearly struggling with compliance and security. >> Hosts: Mm hmm. >> And so, like many customers. And so, that's maybe where they start. There are other customers that are a little behind the head of the pack in terms of building applications, right? And so they're looking at these, you know, innovative companies that have the developers that get the cloud and build all these application. They are leader in the industry. They're saying, "How do I get some of that?" Well, the way you get some of that is by adopting modern application development and platform operational capabilities. So, that's maybe, that's where they should start. And so on and so forth. It really depends on the business. To me, observability is the foundational part of this. >> John Furrier: Vittorio, we've been on this conversation with you for over a year and a half now with Supercloud. You've been a leader in seeing the wave, you and Raghu and the team at VMware, among other industry leaders. This is our second event. If you're- In the minute and a half that we have left, when you get asked, "what is this Supercloud multicloud Cross-Cloud thing? What's it mean?" I mean, I mentioned earlier, the market, the business models are changing, tech's changing, society needs more economic value out of the cloud. Builders are out there. If someone says, "Hey, Vittorio, what's the bottom line? What's really going on? Why should I pay attention to this wave? What's going on?" How would you describe the relevance of Supercloud? >> I think that this industry is full of smart vendors and smart customers. And if we are smart about it, we look at the history of IT and the history of IT repeats itself over and over again. You follow the- He said, "Follow the money." I say, "Follow the developers." That's how I made my career. I follow great developers. I look at, you know, Kit Colbert. I say, "Okay. I'm going to get behind that guy wherever he is going." And I try to add value to that person. I look at Raghu and all the great engineers that I was blessed to work with. And so the engineers go and explore new territories and then the rest of the stacks moves around. The developers have gone multicloud. And just like in any iteration of IT, at some point, the way you get the right scales at the right cost is with abstractions. And you can see it everywhere from, you know, bits and bytes, integration, to SOA, to APIs and microservices. You can see it now from best-of-breed hyperscaler across multiple clouds to creating an abstraction layer, a Supercloud, that creates a unified way of building, managing, running, securing, and accessing applications. So if you're a customer- (laughs) A minute and a half. (hosts chuckle) If you are customers that are out there and feeling the pain, you got to adopt this. If you are customers that is behind and saying, "Maybe you're in denial" look at the customers that are solving the problems today, and we're going to have some today. See what they're doing and learn from them so you don't make the same mistakes and you can get there ahead of it. >> Dave Vellante: Gracely's Law, John. Brian Gracely. That history repeats itself and- >> John Furrier: And I think one of these, "follow the developers" is interesting. And the other big wave, I want to get your comment real quick, is that developers aren't just application developers. They're network developers. The stack has completely been software-enabled so that you have software-defined networking, you have all kinds of software at all aspects of observability, infrastructure, security. The developers are everywhere. It's not just software. Software is everywhere. >> [Vittorio Viarengo] Yeah. Developers, developers, developers. The other thing that we can tell, I can tell, and we know, because we live in Silicon Valley. We worship developers but if you are out there in manufacturing, healthcare... If you have developers that understand this stuff, pamper them, keep them happy. (hosts laugh) If you don't have them, figure out where they hang out and go recruit them because developers indeed make the IT world go round. >> John Furrier: Vittorio, thank you for coming on with that opening keynote here for Supercloud 2. We're going to unpack what Supercloud is all about in our second edition of our live performance here in Palo Alto. Virtual event. We're going to talk to customers, experts, leaders, investors, everyone who's looking at the future, what's being enabled by this new big wave coming on called Supercloud. I'm John Furrier with Dave Vellante. We'll be right back after this short break. (ambient theme music plays)

>> From The Cube studios in Palo Alto, in Boston, bringing you data driven insights from the cube and ETR. This is breaking analysis with Dave Vellante. >> Last year, we noted in a breaking analysis that the cloud ecosystem is innovating beyond the idea or notion of multi-cloud. We've said for years that multi-cloud is really not a strategy but rather a symptom of multi-vendor. And we coined this term supercloud to describe an abstraction layer that lives above the hyperscale infrastructure that hides the underlying complexities, the APIs, and the primitives of each of the respective clouds. It interconnects whether it's On-Prem, AWS, Azure, Google, stretching out to the edge and creates a value layer on top of that. So our vision is that supercloud is more than running an individual service in cloud native mode within an individual individual cloud rather it's this new layer that builds on top of the hyperscalers. And does things irrespective of location adds value and we'll get into that in more detail. Now it turns out that we weren't the only ones thinking about this, not surprisingly, the majority of the technology ecosystem has been working towards this vision in various forms, including some examples that actually don't try to hide the underlying primitives. And we'll talk about that, but give a consistent experience across the DevSecOps tool chain. Hello, and welcome to this week's Wikibon, Cube insights powered by ETR. In this breaking analysis, we're going to share some recent examples and direct quotes about supercloud from the many Cube guests that we've had on over the last several weeks and months. And we've been trying to test this concept of supercloud. Is it technically feasible? Is it business rational? Is there business case for it? And we'll also share some recent ETR data to put this into context with some of the players that we think are going after this opportunity and where they are in their supercloud build out. And as you can see I'm not in the studio, everybody's got COVID so the studios shut down temporarily but breaking analysis continues. So here we go. Now, first thing is we uncovered an article from earlier this year by Lori MacVittie, is entitled, Supercloud: The 22 Answer to Multi-Cloud Challenges. What a great title. Of course we love it. Now, what really interested us here is not just the title, but the notion that it really doesn't matter what it's called, who cares? Supercloud, distributed cloud, someone even called it Metacloud recently, and we'll get into that. But Lori is a technologist. She's a developer by background. She works at F-Five and she's partial to the supercloud definition that was put forth by Cornell. You can see it here. That's a cloud architecture that enables application migration as a service across different availability zones or cloud providers, et cetera. And that the supercloud provides interfaces to allocate, migrate and terminate resources... And can span all major public cloud providers as well as private clouds. Now, of course, we would take that as well to the edge. So sure. That sounds about right and provides further confirmation that something new is really happening out there. And that was our initial premise when we put this fourth last year. Now we want to dig deeper and hear from the many Cube guests that we've interviewed recently probing about this topic. We're going to start with Chuck Whitten. He's Dell's new Co-COO and most likely part of the Dell succession plan, many years down the road hopefully. He coined the phrase multi-cloud by default versus multi-cloud by design. And he provides a really good business perspective. He's not a deep technologist. We're going to hear from Chuck a couple of times today including one where John Furrier asks him about leveraging hyperscale CapEx. That's an important concept that's fundamental to supercloud. Now, Ashesh Badani heads products at Red Hat and he talks about what he calls Metacloud. Again, it doesn't matter to us what you call it but it's the ecosystem gathering and innovating and we're going to get his perspective. Now we have a couple of clips from Danny Allan. He is the CTO of Veeam. He's a deep technologist and super into the weeds, which we love. And he talks about how Veeam abstracts the cloud layer. Again, a concept that's fundamental to supercloud and he describes what a supercloud is to him. And we also bring with Danny the edge discussion to the conversation. Now the bottom line from Danny is we want to know is supercloud technically feasible? And is it a thing? And then we have Jeff Clarke. Jeff Clark is the Co-COO and Vice Chairman of Dell super experienced individual. He lays out his vision of supercloud and what John Furrier calls a business operating system. You're going to hear from John a couple times. And he, Jeff Clark has a dropped the mic moment, where he says, if we can do this X, we'll describe what X is, it's game over. Okay. So of course we wanted to then go to HPE, one of Dell's biggest competitors and Patrick Osborne is the vice president of the storage business unit at Hewlett Packet Enterprise. And so given Jeff Clarke's game over strategy, we want to understand how HPE sees supercloud. And the bottom line, according to Patrick Osborne is that it's real. So you'll hear from him. And now Raghu Raghuram is the CEO of VMware. He threw a curve ball at this supercloud concept. And he flat out says, no, we don't want to hide the underlying primitives. We want to give developers access to those. We want to create a consistent developer experience in that DevsSecOps tool chain and Kubernetes runtime environments, and connect all the elements in the application development stack. So that's a really interesting perspective that Raghu brings. And then we end on Itzik Reich. Itzik is a technologist and a technical team leader who's worked as a go between customers and product developers for a number of years. And we asked Itzik, is supercloud technically feasible and will it be a reality? So let's hear from these experts and you can decide for yourselves how real supercloud is today and where it is, run the sizzle >> Operative phrase is multi-cloud by default that's kind of the buzz from your keynote. What do you mean by that? >> Well, look, customers have woken up with multiple clouds, multiple public clouds, On-Premise clouds increasingly as the edge becomes much more a reality for customers clouds at the edge. And so that's what we mean by multi-cloud by default. It's not yet been designed strategically. I think our argument yesterday was, it can be and it should be. It is a very logical place for architecture to land because ultimately customers want the innovation across all of the hyperscale public clouds. They will see workloads and use cases where they want to maintain an On-Premise cloud, On-Premise clouds are not going away, I mentioned edge clouds, so it should be strategic. It's just not today. It doesn't work particularly well today. So when we say multi-cloud by default we mean that's the state of the world today. Our goal is to bring multi-cloud by design as you heard. >> Really great question, actually, since you and I talked, Dave, I've been spending some time noodling just over that. And you're right. There's probably some terminology, something that will get developed either by us or in collaboration with the industry. Where we sort of almost have the next almost like a Metacloud that we're working our way towards. >> So we manage both the snapshots and we convert it into the Veeam portable data format. And here's where the supercloud comes into play. Because if I can convert it into the Veeam portable data format, I can move that OS anywhere. I can move it from physical to virtual, to cloud, to another cloud, back to virtual, I can put it back on physical if I want to. It actually abstracts the cloud layer. There are things that we do when we go between cloud some use BIOS, some use UEFI, but we have the data in backup format, not snapshot format, that's theirs, but we have it in backup format that we can move around and abstract workloads across all of the infrastructure. >> And your catalog is control in control of that. Is that right? Am I thinking about that the right way? >> Yeah it is, 100%. And you know what's interesting about our catalog, Dave, the catalog is inside the backup. Yes. So here's, what's interesting about the edge, two things, on the edge you don't want to have any state, if you can help it. And so containers help with that You can have stateless environments, some persistent data storage But we not not only provide the portability in operating systems, we also do this for containers. And that's true. If you go to the cloud and you're using say EKS with relational database services RDS for the persistent data later, we can pick that up and move it to GKE or move it to OpenShift On-Premises. And so that's why I call this the supercloud, we have all of this data. Actually, I think you termed the term supercloud. >> Yeah. But thank you for... I mean, I'm looking for a confirmation from a technologist that it's technically feasible. >> It is technically feasible and you can do it today. >> You said also technology and business models are tied together and enabler. If you believe that then you have to believe that it's a business operating system that they want. They want to leverage whatever they can. And at the end of the day, they have to differentiate what they do. >> Well, that's exactly right. If I take that in what Dave was saying and I summarize it the following way, if we can take these cloud assets and capabilities, combine them in an orchestrated way to deliver a distributed platform, game over. >> We have a number of platforms that are providing whether it's compute or networking or storage, running those workloads that they plum up into the cloud they have an operational experience in the cloud and they now they have data services that are running in the cloud for us in GreenLake. So it's a reality, we have a number of platforms that support that. We're going to have a a set of big announcements coming up at HPE Discover. So we led with Electra and we have a block service. We have VM backup as a service and DR on top of that. So that's something that we're providing today. GreenLake has over, I think it's actually over 60 services right now that we're providing in the GreenLake platform itself. Everything from security, single sign on, customer IDs, everything. So it's real. We have the proofpoint for it. >> Yeah. So I want to clarify something that you said because this tends to be very commonly confused by customers. I use the word abstraction. And usually when people think of abstraction, they think it hides capabilities of the cloud providers. That's not what we are trying to do. In fact, that's the last thing we are trying to do. What we are trying to do is to provide a consistent developer experience regardless of where you want to build your application. So that you can use the cloud provider services if that's what you want to use. But the DevSecOp tool chain, the runtime environment which turns out to be Kubernetes and how you control the Kubernetes environment, how do you manage and secure and connect all of these things. Those are the places where we are adding the value. And so really the VMware value proposition is you can build on the cloud of your choice but providing these consistent elements, number one, you can make better use of us, your scarce developer or operator resources and expertise. And number two, you can move faster. And number three, you can just spend less as a result of this. So that's really what we are trying to do. We are not... So I just wanted to clarify the word abstraction. In terms of where are we? We are still, I would say, in the early stages. So if you look at what customers are trying to do, they're trying to build these greenfield applications. And there is an entire ecosystem emerging around Kubernetes. There is still, Kubernetes is not a developer platform. The developer experience on top of Kubernetes is highly inconsistent. And so those are some of the areas where we are introducing new innovations with our Tanzu Application Platform. And then if you take enterprise applications, what does it take to have enterprise applications running all the time be entirely secure, et cetera. >> Well, look, the multi-cloud by default today are isolated clouds. They don't work together. Your data is siloed. It's locked up and it is expensive to move and make sense of it. So I think the word you and I were batting around before, this is an interconnected tissue. That's what the world needs. They need the clouds to work together as a single platform. That's the problem that we're trying to solve. And you saw it in some of our announcements here that we're starting to make steps on that journey to make multi-cloud work together much simpler. >> It's interesting, you mentioned the hyperscalers and all that CapEx investments. Why wouldn't you want to take advantage of a cloud and build on the CapEx and then ultimately have the solutions machine learning as one area. You see some specialization with the clouds. But you start to see the rise of superclouds, Dave calls them, and that's where you can innovate on a cloud then go to the multiple clouds. Snowflakes is one, we see a lot of examples of supercloud... >> Project Alpine was another one. I mean, it's early, but it's its clearly where you're going. The technology is just starting to come around. I mean it's real. >> Yeah. I mean, why wouldn't you want to take advantage of all of the cloud innovation out there? >> Is that something that's, that supercloud idea is a reality from a technologist perspective. >> I think it is. So for example Katie Gordon, which I believe you've interviewed earlier this week, was demonstrating the Kubernetes data mobility aspect which is another project. That's exactly part of the it's rationale, the rationale of customers being able to move some of their Kubernetes workloads to the cloud and back and between different clouds. Why are we doing? Because customers wants to have the ability to move between different cloud providers, using a common API that will be able to orchestrate all of those things with a self-service that may be offered via the APEX console itself. So it's all around enabling developers and meeting them where they are today and also meeting them into tomorrow's world where they actually may have changed their mind to do those things. So yes we are walking on all of those different aspects. >> Okay. Let's take a quick look at some of the ETR data. This is an X-Y graph. You've seen it a number of times on breaking analysis, it plots the net score or spending momentum on the Y-axis and overlap or pervasiveness in the ETR dataset on the X-axis, used to be called market share. I think that term was off putting to some people, but anyway it's an indicator of presence in the dataset. Now that red dotted line that's rarefied air where anything above that line is considered highly elevated. Now you can see we've plotted Azure and AWS in the upper right. GCP is in there and Kubernetes. We've done that as reference points. They're not necessarily building supercloud platforms. We'll see if they ever want to do so. And Kubernetes of course not a company, but we put 'em in there for context. And we've cherry picked a few players that we believe are building out or are important for supercloud build out. Let's start with Snowflake. We've talked a lot about this company. You can see they're highly elevated on the vertical axis. We see the data cloud as a supercloud in the making. You've got pure storage in there. They made the public, the early part of its supercloud journey at Accelerate 2019 when it unveiled a hybrid block storage service inside of AWS, it connects its On-Prem to AWS and creates that singular experience for pure customers. We see Hashi, HashiCorp as an enabling infrastructure, as code. So they're enabling infrastructure as code across different clouds and different locations. You see Nutanix. They're embarking on their multi-cloud strategy but it's doing so in a way that we think is supercloud, like now. Now Veeam, we were just at VeeamON. And this company has tied Dell for the number one revenue player in data protection. That's according to IDC. And we don't think it won't be long before it holds that position alone at the top as it's growing faster than in Dell in the space. We'll see, Dell is kind of waking up a little bit and putting more resource on that. But Veeam, they're a pure play vendor in data protection. And you heard their CTO, Danny Allan's view on Supercloud, they're doing it today. And we heard extensive comments as well from Dell that's clearly where they're headed, project Alpine was an early example from Dell technologies world of Supercloud in our view. And HPE with GreenLake. Finally beginning to talk about that cross cloud experience. I think it in initially HPE has been more focused on the private cloud, we'll continue to probe. We'll be at HPE discover later on the spring, actually end of June. And we'll continue to probe to see what HPE is doing specifically with GreenLake. Now, finally, Cisco, we put them on the chart. We don't have direct quotes from recent shows and events but this data really shows you the size of Cisco's footprint within the ETR data set that's on the X-axis. Now the cut of this ETR data includes all sectors across the ETR taxonomy which is not something that we commonly show but you can see the magnitude of Cisco's presence. It's impressive. Now, they had better, Cisco that is, had better be building out a supercloud in our view or they're going to be left behind. And I'm quite certain that they're actually going to do so. So we have a lot of evidence that we're putting forth here and seeing in the marketplace what we said last year, the ecosystem is take taking shape, supercloud is forming and becoming a thing. And really in our view, is the future of cloud. But there are always risks to these predictive scenarios and we want to acknowledge those. So first, look, we could end up with a bunch of bespoke superclouds. Now one supercloud is better than three separate cloud native services that do fundamentally the same thing from the same vendor. One for AWS, one for GCP and one for Azure. So maybe that's not all that bad. But to point number two, we hope there evolves a set of open standards for self-service infrastructure, federated governance, and data sharing that will evolve as a horizontal layer versus a set of proprietary vendor specific tools. Now, maybe a company like Veeam will provide that as a data management layer or some of Veeam's competitors or maybe it'll emerge again as open source. As well, and this next point, we see the potential for edge disruptions, changing the economics of the data center. Edge in fact could evolve on its own, independent of the cloud. In fact, David Floria sees the edge somewhat differently from Danny Allan. Floria says he sees a requirement for distributed stateful environments that are ephemeral where recovery is built in. And I said, David, stateful? Ephemeral? Stateful ephemeral? Isn't that an oxymoron? And he responded that, look, if it's not ephemeral the costs are going to be prohibitive. He said the biggest mistake the companies could make is thinking that the edge is simply an extension of their current cloud strategies. We're seeing that a lot. Dell largely talks about the edge as retail. Now, and Telco is a little bit different, but back to Floria's comments, he feels companies have to completely reimagine an integrated file and recovery system which is much more data efficient. And he believes that the technology will evolve with massive volumes and eventually seep into enterprise cloud and distributed data centers with better economics. In other words, as David Michelle recently wrote, we're about 15 years into the most recent cloud cycle and history shows that every 15 years or so, something new comes along that is a blind spot and highly disruptive to existing leaders. So number four here is really important. Remember, in 2007 before AWS introduced the modern cloud, IBM outpost, sorry, IBM outspent Amazon and Google and RND and CapEx and was really comparable to Microsoft. But instead of inventing cloud, IBM spent hundreds of billions of dollars on stock buybacks and dividends. And so our view is that innovation rewards leaders. And while it's not without risks, it's what powers the technology industry it always has and likely always will. So we'll be watching that very closely, how companies choose to spend their free cash flow. Okay. That's it for now. Thanks for watching this episode of The Cube Insights, powered by ETR. Thanks to Stephanie Chan who does some of the background research? Alex Morrison is on production and is going to compile all this stuff. Thank you, Alex. We're all remote this week. Kristen Nicole and Cheryl Knight do Cube distribution and social distribution and get the word out, so thank you. Robert Hof is our editor in chief. Don't forget the checkout etr.ai for all the survey action. Remember I publish each week on wikibon.com and siliconangle.com and you can check out all the breaking analysis podcasts. All you can do is search breaking analysis podcast so you can pop in the headphones and listen while you're on a walk. You can email me at david.vellante@siliconangle.com. If you want to get in touch or DM me at DVellante, you can always hit me up into a comment on our LinkedIn posts. This is Dave Vellante. Thank you for watching this episode of break analysis, stay safe, be well and we'll see you next time. (upbeat music)