(upbeat funky music) >> From our studios in the heart of Silicon Valley, Palo Alto, California. This is a Cube conversation. >> Hello everyone welcome to this special Cube conversation here in Palo Alto, California. I'm John Furrier. Co-host of the Cube. We got two special expert guests here talking multi-cloud, Jonathan King, Vice President of Strategy, Data Center, and Cloud for WWT. And Fabio Gori, Senior Director Cloud Solution and Marketing at Cisco. Multi-cloud is the topic. Guys are in the throes of it. Jonathan, you're in the front wave of a massive shift. Cisco powers networks for all companies these days, so guys multi-cloud is a reality. It's here. I want to get your thoughts on that, have a conversation. Thanks for joining us. >> Great, glad to be here. >> So multi-cloud is not really been debated. I mean people generally now step back and say multi-cloud is a reality. It's here, people have multiple clouds. Should only have data center on premise. But this idea of multi-cloud and hybrid cloud are somewhat getting mixed up, but multi-cloud is certainly more realistic in the reality sense than anything else. What's your take on multi-cloud, Jonathan? >> So I think we're at a point where there's a growing acceptance of multi-cloud as the architecture of the future. And when you arrive at that point it also means that multi-cloud is the architecture for today. Because if you see your competitors, you see new entrants in your space, moving in a rapid digital pace to meet their business needs, and you're not on the same kind of architecture. The same footing. Then you're going to be left behind. So, used to debate private cloud, hybrid cloud, multi-cloud. The way we see it is that we're in this multi-cloud world. And multi-cloud embraces an end-to-end imperative. How am I getting my apps and my development teams building those apps closer to my business and meeting my needs more rapidly? And then how am I connecting my entire business, my data, my network, all of it, to meet that needs. So multi-cloud architecture's really an imperative. It doesn't mean it's the only thing. There's other elements in terms of having a clear digital strategy. Thinking about how you're going to modernize your infrastructure. Of course, thinking about how you're transforming your security. All four of those elements really comprise a enterprise architecture. Multi-cloud being a core part of it. >> Fabio, Cisco, you guys have seen the waves of innovation, internet, connecting companies together through networking etc. Multi-cloud's a big part of your focus. Certainly at Cisco Live we covered that. What's the definition of multi-cloud now, because I've heard, it's been debunked, but I've heard people say, oh multi-cloud's an application workload moving across multiple clouds. Some say, no, it just means I have two clouds. So what is the definition? Baseline us here. >> So it's interesting because you can go Wikipedia and actually read the definition of multi-cloud, but what I'm really interested in is exactly what Jonathan was saying a moment ago. This is one of those rare cases where what you hear architecture is actually a technology architecture and the business architecture really coincide. People want to use innovation wherever it comes from. And because you can't allow yourself to be just restricted your choice, people want to have choice. Multiple choices. And that's why we're seeing adoption of multiple cloud services. Multiple SaaS solutioning for structure service solutions and the likes. So this is really what multi-cloud means. You're satisfying a business need. And while cloud computing was born, as we know, around 10 years ago, and it probably started with a kind of cost connotation, the speed and agility that you can get out of it now overwhelm the other parameters. And people are ready to spend anything it takes to become faster than their competitor, because that ultimately will really determines your destiny in the marketplace. >> And I want to drill into the tech side and have some specific pointed questions I'd love to ask you. Jonathan, first, talk about the relationship that WWT, World Wide Technology, has with Cisco, and your credibility in multi-cloud. You guys have a unique view First of all you work with Cisco, you guys partner together. A big part of your business. But you guys are in the middle of a lot of the action. Talk about the company. What kind of deals you guys are doing? What visibility do you guys have? Is it a landscape? Give an example of some of the work that you guys do, and then talk about the relationship with Cisco. >> Yeah so, the Cisco is a very strategic partner of ours. They have been for a long time. And we have the benefit of being at scale with Cisco. For repeatable waves of technology roll outs. In repeatable domains of technologies. So, customers come to us and look for our help as a trusted advisor to help them with their architectural decisions. And to help them often with knowledge gaps. So, architecture is a challenge. Especially when you're dealing with rapid change. So you have a pace of change externally. You cover this space. I mean every day, right? We were sitting here there's some kind of new thing going on. And, that change, I mean even companies who know what they're doing, and have deep benches of talent, have architectural challenges. But you take it to an enterprise or a government agency. How are they going to keep up? Well that's really our job and the value we bring is. We are constantly watching, talking to partners, talking to customers. And there's almost no one we're that as closely with as we are with Cisco, in terms of how we're watching trends, looking what's happening. And from a multi-cloud standpoint, in answer to your question there, it's a bit of a thought experiment. So if you define multi-cloud as really just, oh it's just between Amazon, Azure, Google. Multi-cloud is just multi public cloud. We do not see it that way, our clients don't see it that way. Our clients see it as a bigger domain. That multi-cloud includes how you're connecting to SaaS. How you're, there's multiple public clouds, a bigger definition there. But then it's also the edge, the cloud edge, the different edges that are out there are are being deployed in a cloud architecture. Your core data center has a private cloud. All of that we see as multi-cloud. And when you define it that way, you start to look at it. Companies are saying who do I turn to to help me with a multi-cloud architecture? Do I turn to someone that was born in the cloud. Who just really knows AWS. They know it really well. But that's what they know. Or a similar consulting company who's over here. The credibility that we have, we have those capabilities. But we also have depth and breadth, and history, and knowledge, and contracts and relationships. An incredible ecosystem. And important with Cisco, it's not just a one-way relationship. We have an ecosystem around us, collectively, that Cisco benefits because we have that ecosystem. And that's really what companies look for. It puts us in a very unique position because we see this AND world. It's not an OR world. And I think even the investments and movements that the public clouds have made recently. The hybrid offerings that they're bringing, and where Kubernetes is going to enable portability. All these things really are about a multi-cloud world, and we're just excited about where we are. >> It's interesting, there's the first wave, Amazon, I call it the Amazon wave because they really did take out the beach. And then public cloud. It kind of showed the way, the economics and the value creation piece. And you mentioned a few things that point at this next wave. That next big wave I see it is about people and technology. This holistic view around multiple architectures is a systems concept so it's not unproven. And Fabio we've seen this movie before in systems. Operating systems. You need networking. You got to connect things together. So this next wave of thinking about workloads and applications in context to an architecture see to the next narrative that people are starting to talk about. Versus. >> Absolutely >> Public cloud, because the people equation, who's going to run it, who's going to service it, who's the coders, what tools and APIs do I use. People behave in certain ways, and they like their favorite cloud, so it's a whole different ball game. You're thoughts. What's driving all this? >> I would say, look, we could talk about this forever. But I think we're seeing a pretty dramatic shift into an architectural model, right? I mean, if you remember a few years ago, we had networking specialists in the data center, storage specialists and compu-specialists, well guess what, people moved to full-stack type of expertise, right? And now we even have systems that are completely converged. Or hybrid converged. Well, we're seeing the same movie in the cloud. Where we're seeing the rise of cloud architectures, enterprise architectures, which become really determinable of the business. And these people, especially in the companies that are ahead of the game, in terms of cloud adoption and expertise. These guys are issuing the new guidance and guardrails for the entire organization in terms of what governance role you need to take, right? And the other groups actually execute this kind of strategy. This is, some people say this is finally SOA coming alive. The SOA, Service Oriented Architecture. That's exactly what it is without probably some of the kind of propriety underpinnings, or driven by certain market players in the past. This is a true, so if you think about microservices in containers, that's exactly what it is. And also we're seeing a lot of companies that are starting getting even organized by microservices. Which is the ultimate demonstration that the technology architecture and the business architecture are really converged. It's a fairly complicated concept, but in the end it's about really connecting the business to the underlying technology. >> And it's a shift that's happening in front of our eyes. And we're covering a lot of the news. Some notable news that we've been covering lately, the Department of Defense JEDI contract. That's in the public sector and military. CNCF, Amazon re:Invent. Google Nexus coming out. You're starting to see the formation where it's not about the cloud vendor or the cloud supplier anymore, as much as it is about the workload. So, there's been a debate of sole sourcing the cloud, that's certainly, we're seeing that on the DOD side 'cause it's more a military procurement thing. But that's not the right answer anymore, we're seeing that whole, spread the multi-vendor love around. It's not so much like it used to be. It's different now, there's new architecture. So, Jonathan, I want to go back to your multi-cloud architecture because I think the strategic question that I'd like to get to is. It might not be a bad thing to pick a cloud, a sole cloud for workload. But that's not meaning you're going to not use other clouds. This is a whole different thinking. So I can pick Amazon for this workload or pick Azure for that workload and Google for that workload. And holistically connect them all together. Seamlessly, this is not a bad thing. Your thoughts. >> There's a somewhat of a paradox when you talk about multi-cloud architecture and then you talk about moments in time where it makes architectural sense to pick one cloud, right? That particular decision there's issues around people and training and technology, and time to market, and API coverage. So there's all these things that you're trying to get a job done or a mission done and the amount of time that you have to achieve that job or that mission. What path am I going to choose? What engine am I going to put on the plane to get me there? Now that doesn't mean that that's the only engine you're going to put on your fleet. It just means that particular plane is going to have that kind of engine. And then the next time, you got another engine, you got a different kind of plane. You're thinking about how you're doing these things in waves and modules, and you're trying to build your aggregate velocity, 'cause really if you strip it all down. You know earlier we were talking about multi-cloud and people and talent, we're in a distributed computing land rush. And businesses of all sizes, government agencies, companies are trying to figure out how do we, you know. Electricity came along, now cloud has come along, right over the horizon cognification's coming along. How am I as an enterprise getting digitally ready, and getting on a footing to be able to do what I need to do in that domain? And really, it's about velocity and movement, so. Now that means that, that's why architecture is so important, because you have to make, you want a, people talk about one-way doors and two-way doors. So you want stop and think about, am I going through a one-way door or am I going through a two-way door? Meaning, do I have a way to come back? Is this a decision that I'm going to live with? If so how long? Is this a decision I can go through and I can come back? These kinds of approaches let you look across it. So an example would be networking. So networking is a foundation to every multi-cloud strategy. So you have to think, today my network in many enterprises is still a campus branch architecture. Well traffic patterns have changed. Even if you've just done nothing your customers have moved. Like all of a sudden, you know we talk to customers. We work with retailers, we work with all kinds of people, and it is like Global Climate Change. It's like global network change. The scale at which the clouds have arrived have changed the network patterns. So, if you start to look at it, you're saying, well what is a multi-cloud networking strategy? How do I need to rethink, well, guess what, the campus, my headquarters, is no longer the hub it used to be. The hub is now at the cloud edge, where all the other clouds are geographically aggregated. I need to move my network closer to that location. So we do a lot of work with Equinix in that context, right? So they have and have built a business around >> Sort of re-architecture's happening, and it's being driven by value creation, value shifting. >> Yes. >> Moving everything around. >> And that's where from a cloud networking standpoint, you look at that's a discussion where Cisco's so uniquely situated, because they are the networking company. They've been through the generations and they've been through different changes of generations. You know Wi-Fi, didn't used to be Wi-Fi. Now it is, right, it's here. And now we're in this next paradigm, where cloud networking didn't used to be here. Now it is, so. >> What's the new thought process for cloud networking. Because it makes a lot of sense, you have to connect clouds, obviously networking latency, SLAs around moving things around from point a to point b, storing stuff as well. Fabio, what's the equation look like? What's changed? Where do your customers go in this new architecture? >> Well, just building on top of what Jonathan was saying before, first of all the way we architect the networks, enterprise networks were networks in the past. Of course this is coming to an end. We need to rethink them, right? The fact that users now are going to use an enormous amount of software as a service applications that don't sit in your data center, means that constricting all the software in a single place doesn't make any more sense. But there's not just the traffic element. Think about all the intrusion detection and prevention, firewalling capabilities. Because you're moving away from that model, you need to start visualizing also those security functions and distributing them all the way to the edge of the network. In some cases, you need to have them in the cloud as well. We believe that the best way is a fully distributed model. Where you have a choice. Whether you keep it in your data center, or you put into the cloud, or even the to edge of the network. Again, you got to be ready for any kind of scenario. It's interesting how, you know, we're going to distributed computing as you said. But everything else is getting distributed as well. >> Oh yeah. >> Your entire infrastructure needs to follow your application and data. Wherever they go. And that's actually something unprecedented that we're seeing right now. >> And you brought up cloud architecture earlier, Jonathan. You mentioned it briefly. And this comes back to some of that this nuanced point around cloud architecture. The procurement standards aren't driving what you buy, its architectural workload dynamics are now telling procurement how we're buying. So the world shifting from, oh, I'm going to buy these servers. I'm going to buy this gear, the approved vendors. When you think about architecture the way you pointed it out, it's a completely different decision making process. So what's happening is old ways of procuring and buying and consuming technology are now shifting to. Still not going to stand up a cloud with a credit card if I'm doing dev ops, but now you start thinking holistically. The decision making on what that will look like has changed. This is probably impacting the cultural people side as well. What's your thoughts on this dynamic between cloud selection, security, architecture, and procurement? >> The example I normally give is, it's changing but it's also evolving, right? Because you're dealing with patterns that are there, and they're not going to go away, right? Money still has to be paid. Processes have to be followed and respected. The examples that I give would be, I've run large clouds in my past. Different platforms. And one thing you always watch out for when you're running a cloud is capacity. How much money do I have in the bank, so to speak, right? Am I going to have a run on the bank? So if you're running that cloud, either, and this is true if you're a service provider or you have your own private cloud. You're very concerned about you don't want to run out of capacity. Because bad things happen. Even unrecoverable bad things happen. Well in the public cloud, hey, I'm free and clear, I no longer have a capacity management team, I don't need to worry about them anymore. No, no, no no. 'Cause, you know, we just saw some press recently of a company that had a big overage. In cloud, what used to be capacity management is now cost optimization. 'Cause if you don't have it, you're going to have a similarly bad outcome. It's those kinds of things, right? How do you go, and it's those things, right? >> Once a benefit, now it's a challenge. So this could back down to the billion dollar question on the table in the industry is, how do I manage all this? I know how to connect it. Cisco could help me there. I understand multi-cloud, I totally buy into the architecture. I think this is clearly the direction. The management piece is kind of a fuzzy area. Can you guys help unpack cloud management? What are the table stakes? How should people be thinking about it? Because you mentioned security and intrusion detection. Not just moving packets around. We were talking before you came on about Kubernetes. There's all new sets of services moving up the stack, inside this dynamic. How do I manage it all? What single pane of glass is going to do it for me? >> Well, yeah, it's interesting you mentioned there. We've talked a lot about almost like an East West type shift you can think of where, multi-cloud is this thing that goes this way. Well, there's an equally crazy paradigm that's happening in a very fast period of time where it's almost like a North South North shift. Which is, Kubernetes, containers, service meshes. These architectures that are abstracting and lifting everything up. And in some ways, coming underneath as well, at the same time. Because now you've got a return of bare metal. You have these concepts architecturally where the VM is here to stay, it ain't going anywhere. It's still, the tooling around is insanely valuable. But you have now another benefit layer at a container orchestration layer, where there's portability, speed. There's all these benefits that come. And you just look at the stats of how fast containers are growing as a share. You're approaching a billion containers out there right now. And therein lies the challenge. Is that it'd be enough of a difficulty if you were saying I need to go from managing my private cloud, the stuff I have at a cloud edge, edge location, and the stuff I have in multiple public clouds. That's not all we're saying. We're saying also, you have a new tooling and a new set, and it's all software defined, and there's security, network, there's data. It just it's -- >> Complex. >> Exploding, it's complex. So the area that we're working on and want to hear more from Fabio is were innovating with Cisco on, we have great offerings and capabilities around cross cloud and VM orchestration. We're also looking now at that Kubernetes layer. >> Absolutely. >> What's real on that, the complexity he just pointed out is an opportunity at the same time because it just validates the shift that's going on. >> Absolutely. >> Management is an opportunity. >> Jonathan almost went through the entire set of needs. And what you take away from this is that fundamentally you have to instrument this incredibly distributed environment multiple sources and sourcing of this. In fact I love the analogy that you did with the planes, because there's a lot of kind of similarities to a supply chain management kind of business model, right? Where you want to supply different services. But a bottom line is that you're now moving away from what you have. It's a journey. And so this instrumentation, whether it's networking, security, analytics, management, these are actually the four pillars of our company multi-cloud strategy. They need to work across the old and the new. You can't afford to build another silo and maybe leveraging a bunch of open stores like-- >> So a data plane strategy is critical. >> It's, yeah, and it has to-- >> Across the hybrid and multi-cloud. >> East West, North South, and across the old and the new. It sounds very complex, but in reality the-- >> But you could build a taxonomy around this. And we've seen some research come out certainly from Wikiban and others. If it fits into the architecture that seems to be the question. So Jonathan, where does that fit in to the multi-cloud architecture in your opinion? >> So we, there's, you get into different terminology. We think about every company needs a cloud services strategy. So there's a taxonomy of services that we've developed. Where companies have to think about their application services strategy. Their operation strategy, governance strategy, foundation strategy. And this is, it's sort of coming what I teased upon earlier about moving from capacity planning when you own the cloud to cost optimization when you're running the cloud, right? It's the same, but different. And a lot of that difference gets down to services. I am going from a model of running my own product in an information technology modality to now I'm consuming services. So, I used to architect, and design, and build. Now I have to architect and really understand those differences. And so that's our cloud services strategy portfolio. And what we often see is we also have a dev ops portfolio. And we short-hand it, you could call it cloud native, right? Where we're looking at solutions around infrastructures code, around CICD pipelines, around cloud foundation capabilities that connect back-- >> Are they best practices or actually implementation? >> So both, we have content and workshops that we've developed, and then we have. Helping clients on projects very actively. And, you know, that's where it gets back to that architectural gap and knowledge gap. Is companies are looking for, hey, what's the pattern, what are the best practices. And then they don't expect, 'cause there's so many elements that change for a given company. And that change in the market, that there's a shelf-life to this. And it's like fresh produce. >> I love your example of engine in a plane. Do you have it for a single plane or fleet of planes? Does your company have two three big planes. It depends really, I mean, beauty's in the eye of the beholder, here, right? How you build and architect cloud, there's no boilerplate. It really is comes down to figuring it out. >> Where you are. >> So, with that, I want to go to my final point I want to dig into on the people side. So technology shift, business shift, check. You guys did a great job there. Great insight. Comes up every time I have to go to a Cube event and talk about cloud, is the cultural people skills gap problem. One, our company doesn't have the culture and/or we don't have the skill and we don't have the people to run it. So, automation certainly can help there but at the end of the day, if you don't have the people to do this. How do you solve the people problem? How are you guys helping companies? What is some of the state-of-the-art techniques? What's out there? >> So, I'll say a little. I appreciate Fabio's perspective, too. I think for us, really, you know, the old saying, culture eats strategy for breakfast. Culture's more important than ever. Because really, you're now moving to a mode where siloed organizations implementing siloed technology is enormously challenging. You have to move, and that's where dev ops and other patterns come in, where the people who build the app are doing the operations. Storage and networking and compute and apps and the business, they're all talking to each other. So culture really is foundational so that a culture where you're not making boundaries more rigid, you have to get to a point, and there's different ways to do this. I already recommend if people haven't already read the Phoenix Project. Hard to believe but it's an excellent book. And it's a fictional work about tech. It's like a novel about tech. >> I haven't read it yet, I'm going to get that. >> It's awesome. And it really gets you in the mindset of an organization going through change with the net. And it really, I mean I'm a geek, so I like it, but I've had other non-Geeks read it and they like it. But that's the key, it's a-- >> So you really got to set the table and invest in culture, making sure it's >> Culture's foundational. >> appropriately aligned. >> Culture's foundational. And then there's other best practices that always apply, right? So, what is your business vision? What is your mission? What are your values? What are the objectives you're trying to achieve in this space and time relationship? How are you prioritizing? These are all things because then if you have the right build around all that. Then what you drive to is an outcome at a certain point of time. And time's critical. We're in a market that's competing on time. So if you are not hyper aware of time. And what you're doing in a set point of time. And the trade-offs in making changes if your assumptions are wrong. These are all things that are foundational. >> Fabio, I want to get your thoughts. Chuck Robbins talks about solving the tech problems just because a tech company can solve tech problems all day long. He's also behind the people skillset. I've heard him publicly talk about it. But you guys at Cisco have actually had a great transformation with the DevNet Create community, where you harness the culture, and everyone's engaged around cloud, cloud native, and you have a kind of cloud DNA developing out of the core network. Your thoughts and Cisco's view on culture and people solving the problem. Because we need an army of cloud architects out there. There's not enough people. >> So that's true, but we carry an enormous responsibility in the marketplace as a vendor. We have to make things simple, right? There's still, you know, most of the IT infrastructure's still very complex to program and automate and the likes. That's why we're putting an enormous amount of RnD efforts, right? DevNet is like the tip of the spear. It's showing fundamentally our very loyal CCIEs and everybody else there's a better way to do things, right? Where you can actually really automate things together. You can get access to the APIs and simplify your life. You can simplify your life and the life of the business 'cause you can get faster. So making things simple, automating them, I don't know, if you think about, for instance, our cloud management orchestration philosophy. With the cloud center, we have a patent where we can actually model the application at once. And deploying it to wherever you want. We can deploy that application on-prem, on a VM, or like viralize kind of infrastructure. You can put it into AWS, you can put it into Azure, whatever you want. Kubernetes is kind of target on-prem. That is simplicity, right? We have to drive simplicity. And for me, it's all about automation, and sometimes you hear things like, in 10-base architecture and infrastructure all of that means simplicity and security. And that's the complexity of the whole thing for us is trading off, of course some of the complexity, richness, and flexibility. But it's got to be simple. If we don't make it simple, we are actually failing our goals. And that's where we're putting an enormous amount of RnD effort. >> And Jonathan, you guys at WWT have a unique aperture, view of the marketplace. You see a lot of the landscape, knowing what you guys do. Every vendor says they it, but you're really customer focused, so you're in you're digging in with the customers, it's a real value added service. I got to ask you the question with multi-cloud it sounds easy just to connect them all, right? It's like a subnet plug it in the coax, put a hub there. Put some adapter cards on a PC. The old days of connecting things. It just metaphorically seems easy What's the opportunity for connecting multi-cloud? So, as people realize when they wake up tomorrow or today. And they go, hey, you know what, I got lot of multi-cloud around. How do I connect them together? What's the opportunity, what's the opportunity for Cisco. 'Cause that seems to be the first order of business. I can connect things together in the architecture. And then what happens next? What's the opportunity to connect these clouds. >> The opportunity is gigantic. If you look at just the growth of the public clouds themselves. The CAGRs that they're representing. They're growing the rate their growing on very big numbers already. And it often gets overlooked, but Gartner will tell you also that the co-location, that cloud edge space, is also growing at a good CAGR. So you have just more and more going there. All of that needs to be connected. All of it needs to be protected. So networking is not just networking. Networking is security. A critical pillar of any security practice is really understanding and knowing in-depth your network. The introspection of it all. And at the same time, we're moving from a physical world. And we've moved and virtualized, but now the virtualization of the network now with SD-WAN coming, you're moving to a programmable model, where everything needs to be programmed. So it's not humans. So it's almost like every arc. Just in terms of the amount of data, the amount of traffic, that's all growing. Now, it's not just humans, it's machines doing things. And then also it's not just physical connections. It's software. So it's a three dimensional plot and it's growing on every axis. >> It just not in every device, it's software as a device. Software device connections. Service connections. What's Cisco's opportunity? How positioned are they that can do this? Because there's a lot of conversation around edge. Now you just mentioned a few of them, 5G. What's Cisco's opportunity in all this? >> Well I mean I think Cisco's shown recently and then through generations that they have a unique ability to lead and move with the market. And they're demonstrating that now. So, I think the importance of where the network sits, and not just the network, but again there's an adjacency of security. There's an adjacency of orchestration and management. Their global presence, their global operation. The sophistication of their channel business. All those things put them in a really strong place, we feel. >> You mentioned SD-WAN in a previous comment around talking about edge and stuff. If you think about Office 365, when companies roll that out. That basically takes SD-WAN from a little niche industry to all the internet. SD-WAN is basically the internet now. Your old grandfather's SD-WAN was over here, now everything's SD-WAN. That's basically the internet. So talk about the SD-WAN impact in this because with edge, that's super important too. Your thoughts. >> Well, it was back when we were talking about that traffic patterns are changing. So you're moving to no longer really this campus branch closed network. There's still an important need for that, of course. But now you're doing your business where your customers are. On their phone, in their car. Which means you're having to traverse and work and scale in a very different way. It's part where you have to put the network. And then, it's how you have to run and connect the network in your retail store or in these other things. Part of it is doing what we've always done in a better way. And then probably every day, more of it is about doing things in a new way that you couldn't do in the past to achieve a new business objective. >> Well Jonathan, thanks for coming on theCUBE conversation. I'd love to have you back on. Great insight. We could also do remotes. So when you go back to the home branch in St. Louis we can bring you in. >> Tells you Silicon Valley and St. Louis, man. Silicon angle, Silicon Valley, St. Louis. >> Let's do it. And I'll say congratulations on your success with Cisco. Fabio, it's been great to see you. Final word, Fabio, just bring it all together. Multi-cloud, it's here, kind of that's the reality. >> Yeah, I want to go back really to where we started the conversation, right? We can't forget the multicloud is still like a mean to and end. The end is, companies want to become and need to become innovative and fast. And that's actually why all this interest in multicloud. It's a business engine. That's why we're all so excited. Because it's a business issue. It's not so much a brand new technology that probably in two years is going to be out of fashion. My personal prediction, we're going to be talking about multicloud for several years. On the contrary of other trends. >> And just to real quickly bring in what we talked about before we came on camera. This is a CEO issue of companies, not CIO. >> Absolutely. >> This is showing the culture and the urgency, really, in all this. >> That's right. >> Absolutely. Guys, thanks so much for coming on. Great insight. Multi-cloud conversation, fantastic. Jonathan King, Vice President of Strategy, Data Center, and Cloud for WWT. Also Fabio Gori, friend of theCUBE, Senior Director Cloud Solution and Marketing at Cisco. Thanks for coming on. This theCUBE conversation. I'm John Furrier, thanks for watching. (upbeat funky music)