(upbeat music) >> Welcome back to Las Vegas. theCUBE is here, live at AWS re:Invent 2021. Lisa Martin with Dave Nicholson. theCUBE has two sets today, two, not one, two, two live sets, two remote sets, over 100 guests on the program at this event, it's a lot, talking about the next generation of cloud innovation with AWS and its massive ecosystem of partners and we are pleased to welcome Walton Smith to the program, the public sector, director of strategic partnerships for Worldwide Technology, Walton welcome to the program. >> Thank you so much for having me, it's really amazing to be here and look forward to a great conversation. Isn't it great to be in person again? >> It's so nice to be in person, I mean I'm glad everybody's being safe and, and checking vaccine status and whatnot, but it's good to get back and, and, and work with people cause we can really drive innovation when, when we get together. >> Those hallway conversations or those conversations here at events that you just can't replicate by video conferencing, right? Not replicate that, you getting grabbed in the hall and say, hey, have you thought about leveraging XYZ to do something? To me that's what makes this conference great. >> Talk to me about what's going on at WWT. What are some of the, the things that you guys have been working on? >> It's a really exciting time at Worldwide, we're really working closely with AWS to drive innovation to the edge. We're excited about their outpost offering, we actually have one in our data center, Sandy announced it today in a partnership with Intel to, to allow our customers to try to work out use cases, to, to kick the tires, so to speak, to see how it works as well as our partners to get their ISV products certified on the outpost platform. >> So I'm familiar with your ATC in St. Louis, is that what you're referring to? >> That's correct. >> Give us a little, give us a little insight into what goes on there, I know it's pretty amazing from a customer perspective because you are agnostic. because you are agnostic. >> Walton: Correct. >> You're there to serve the customer, but tell me, tell me what happens in the ATC. >> We say we're agnostic, but we have our, our, our preferences because we know- >> sure, sure, okay. what actually works. But our ATC is our crown jewel, it's about a $600 million data center that we built solely for proof of concepts for our customers. So our, our top customers come in and say, I have this problem, how can I solve it? And so with us being the single biggest reseller of just about every ISV is out there, I can stand up a, a, a Dell, I can stand up a, a, a Dell, Dell compute next to NetApp storage with Cisco router on top of it to replicate what my customer has at the VA, for example, and then to be able to plug in an outpost to show how leveraging the outpost can give them a single pane of glass to be able to work on their workload, so the training that our FSI, Federal System Integrators have put into their staff or our government customers on the Amazon platform can now be driven into their data center, so it's really taking the cloud down to where the data is. >> In terms of public sector, what are some of the prominent use cases that you guys are helping customers to solve, especially given the tumultuous times that we're still living in? Sure, so what we saw during COVID especially was how most of the government agencies had the capability to allow say 5% to 10% of their workforce to work remotely. And then with COVID, they went to 95% to a 100% workforce. So, a lot of the time we've spent over the last year is how do we securely allow our government employees to get access to the information, because as we know, the government was more valuable than ever to get us through this pandemic, we had to give them the tools that they needed to be able to make the decisions to, to move the country forward. >> Talk about security if you will for a second, we have seen such a dramatic change in the security landscape, the threat landscape, ransomware as a service, it's, you know, the cyber criminals, lot of money in it, they're becoming far more brazen. What are some of the things that you're seeing specifically with respect to security use cases? >> It's, it's gone from, let me just buy everything that's out there and that'll give me security to, I need to have visibility into my environment, because if, if you look at target, it's a great case studies around that, they had all the tools, they just didn't tie it all together. And so as more and more nation state actors And so as more and more nation state actors try to attack our government, or it's a great way to make money, I mean, in, in this, in the presentation, Sandy's today, they talked about, if you looked at the GDP of what's been taken in ransomware, it's like the 10th biggest country in the world, I mean, it's scary and staggering how much money is lost. So what we think, going back to our ATC, we can stand up their environment, we can work with the top security providers in the world to show those customers how we can give them that visibility, the, the, the protection and the ability to get back up, because there's really only two types of organizations, those who've been hacked and those who don't know they've been hacked, they're going to get in, it's how do we mitigate the damage, how do we get them back up and running and how we protect my customers or have some of the most sensitive data in the world, how do we protect that so our government can keep us safe and keep us moving forward. >> Yeah, cause these days it's a matter of when we get hacked, not if. And of course we are only hearing about the large attacks. >> Walton: Correct. We don't hear about- all of the ones that go on day in and day out, I think, I think I saw a stat recently that a ransomware attack happens like once every 11 seconds. >> Correct, I mean, just walking through here, how many text messages you've gotten? You want a free iPad click here, I mean, they're, they're down to the individual level. It's a whole lot cheaper to give a couple people, really powerful laptops, pizza and beer, and have them go attack, than it is to, to set up a real business and so, unfortunately, as long as there's money in it, there's going to be bad actors out there. We think partnering with AWS and other partners can help build solutions. >> You know, WWT has had an interesting history because you didn't start with the dawn of cloud. >> Walton: Right. So you've been in the business of AT for a long time So you've been in the business of AT for a long time and logistics out of St. Louis in a lot of ways. What does that look like in terms of navigating that divide? You know, there's a, there's a whole storied history of companies that were not able to cross the divide from the mainframe era to the client server era, let alone to cloud. You seem to have, you seem to be doing that pretty well. >> I, I appreciate that, I mean, we're the biggest company no one's ever heard of. We're 14, $15 billion privately held firm, the same two guys that founded it, still run it today and all they want to do is do cool things, they want it to be truly the best place to work. So from day one, they've invested in training our staff, building the ATC to give us the tools we need to be successful and then because we're a trusted partner with Amazon Intel and our other partners out there, they're investing in us to help build solutions, so we have over 6,000 engineers, they get up every day, how do I build something that can help our customers really drive change and innovation? So it's been a really fun ride and the, the best is yet to come. >> Talk to me about your customer focus, you know, when we talk, here we are at reinvent, we always talk with AWS about their, you know, Dave, we talked about this customer obsession, the fact that they're working backwards from the customer, do you share that sort of philosophy? Does WWT share that philosophy with AWS? >> 100%?, if you go to WWT.com we've published everything that we have so you can get full access to our lab to learn about x ISV and go deep to learn about x ISV and go deep and see the million and a half labs we've built around, say Red Hat and go and get access to it. So we think that if we educate our customers, there are going to be customers for life, and they're going to come to us with their biggest problems. And that what's, is what's exciting and what enables us to, to really continue to grow. >> And how did the customers help you innovate? And that's one of the things we, I was thinking yesterday with, with this AWS flywheel of when Adam was introducing, and now we have a, now we have, and it was because he would say, we did this, but you needed more, but you being the customer needed more. >> 100%, it, it's we want our customers to come to us with their biggest problems, because that's when we, the exciting innovation works. And so the ability to sit down with the foremost expert in, in virus control and be able to, in, in virus control and be able to, what are the tools that she need to be able to get ahead of the next change to COVID? How can we give them the tools to do that? That's what we want to do, the scalability, the ability to reach out to others is what Amazon brings. So we can bring the data science, we can bring the understanding of the storage, the security, and the network and then AWS gives that limitless scalability to solve those problems and to bring in someone from Africa, to bring in someone from the European Union to, to work together to solve those problems, that's what's, what's exciting and then coming back to the outpost, to be able to put that in the data center, we know the data center is better than just about anybody out there, so it would be the ability to add innovation to them, to bring those part ISV partners together. It's really exciting that Intel is funding it because they know that if, if customers can see the art of the possible, they're going to push that innovation. >> One of the things we've also sort of thematically Dave and I with guests, and the other has been talking about this week is that every company has to be a data company, whether it's public sector, private sector, if you're not, or if you're not on your way, there's a competitor right here in the rear view mirror ready to take your place. How do you help public sector organizations really develop, embrace an execute a data full course strategy? >> So we have a cadre of over 125 data scientists that work every day to help organizations unlock their most valuable asset, that data, their people and be able to put the data in the right place at the right time and so by investing in those data scientists, investing in the networking folks to be able to look at the holistic picture is how we can bring those solutions to our customers, because the data is the new oil of, of the environment and sorry for my Southern twang on the oil, but it, but it truly is the most valuable asset they have and so, how do we unlock that? How do they pull that data together, secure it? Because now that you're aggregating all that data, you're making it a treasure trove for those bad actors that are out there, so you've got to secure it, but then to be able to learn and, and automate based on, on what you learned from that data. >> You know I, I think with hindsight, it's easy to, it's easy to say, well, of course WWT is where WWT is today. Five years ago, though, I think it would have been an honest question to ask, how are you going to survive in the world of cloud? And here we are, you've got outposts. >> Walton: Sure. >> And, and of course it makes sense because you're focused on customers, sounds like I'm doing a commercial for you, But I'm a fan- >> I'll gladly apreciate that- because I, I, I've worked with you guys in a variety of roles for a long time, seems like yesterday we were testing a bunch of different storage arrays of the ATC and now you've got outposts in cloud and you're integrating it together. It's really more of the same, I'm sure if we had your founders here, they'd tell you, Dave, it's all the same. >> Walton: Correct. It's all the same. >> It's AT, it's where, where's the compute, where's the storage, how do you get access to it and the cloud has given the ability to, to scale and do things you could never imagine. I think it's the reason we're here is because our leadership continues to invest and pushing that envelope to give people the freedom to go out with that crazy idea, what if we did this? And having the tools and the ability to do that is, is what, what drives our innovation and that's what we bring to our customers and our partners, that ability to innovate to, that ability to innovate to, to tackle that next problem. >> So what's the tip of the spear right now for you guys? What are you, what's, what's, what's kind of, what's next? What are you waiting to have delivered to the ATC to racket, stack and cable up? >> Lot's of stuff that I can't tell you about because there, there's things that Amazon is, is always working on that we work with before it, it's, it's made public, so there's a lot of really cool stuff in the pipeline, because the, as you think about moving to the data center, that's one thing, moving to truly to the edge, where you can help that war fighter, where you can help that mission, where you can do disaster recovery, leveraging the snowball family, the outpost family, and custom built tools that really allow for quick response and custom built tools that really allow for quick response to whatever that problem is, is that next front and that's where we've been for a long time, helping our, our war fighters and folks do what needs to be done. Outpost sees that you can leverage big AWS Outpost sees that you can leverage big AWS to build the models, push it down to the edge because you don't have time or the bandwidth to get it back into the big cloud, to be able to put that compute and storage and analytics on the edge to make real time decisions, is what we have to do to stay relevant and that's where the joint partnership is really exciting. >> It's what you have to do to stay relevant, it's also what your customers need, cause one of the things that we've learned in the pandemic is that real-time data and access to it is no longer, longer a nice to have, this is business critical for everything. >> Correct and even if you have a fat pipe to get it, you need to make real time decisions and if you're in a really sandy space, excuse me, making hard decisions, you've got to get the best information to that soldier when, when they need it to, to save our lives or to save the other people's lives so it's, it's, it's not just a nice to have, it's mission critical. >> It is mission critical, Walton, thank you so much, we're out of time, but thank you for joining Dave and me talking about- >> Really enjoyed it. all the stuff going on with, with worldwide, the partnership with AWS, how you're helping really transform the public sector, we appreciate your time and your insights. >> Thank you so much, have a great conference. >> Thanks, you too. >> Okay, thanks. >> All right, from my buddy, Dave Nicholson, I'm Lisa Martin, you're watching theCUBE, the global leader in live tech coverage. (upbeat music)

(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)

>> Live from Orlando, Florida, it's theCUBE. Covering Cisco Live 2018. Brought to you by Cisco, NetApp, and theCUBE's ecosystem partnership. (upbeat music) >> Hello everyone, welcome back live here in Orlando, Florida for Cisco Live 2018. This is theCUBE's exclusive coverage of Cisco Live. Gonna go throughout the events, extract them. I'm John Furrier, my co-host Stu Miniman. Three days of live coverage, our next guest is Sachin Gupta, Senior Vice President and Product Management, Cisco, 20 plus year career, welcome to theCUBE. Thanks for joining us. >> Thank you, thank you for having me. >> So we love the product execs, because you've got visibility into the customers but also into the engineering roadmap, which now, as Chuck the CEO laid out, is in a new modern era. >> Exactly. >> So you guys are busy (laughs), right? >> Yeah. >> What does that mean? I mean, what do you guys think about, what do you talk about in the product teams, to go modern with cloud, obviously a lot going on. You got cyber-ops go-- really heavily on with the routers right now, and all the core products. You gotta maintain that. >> Right. >> But yet build out a future path. >> Yeah. >> What are you guys working on? What's the core story? >> I mean this has been pretty significant, I mean we had to reinvent the entire network. And, the motivation behind this is, for many many years, our customers could go in, manually operate these networks, go box by box, they're putting command line in, they're deciding the configuration of each element, setting it up this way, and they provide connectivity, some basic security, some experience this way. And what's happening now is, it's just a sheer volume and scale of things that they're having to deal with. I mean everybody comes in with four mobile devices, there's all these things that are connecting. We talk about 26 billion things connected to the network in 2020. It's mind boggling. And then at the same time, the applications are moving to the cloud, which means your threats surface has expanded. We needed to do things fundamentally differently. And so we reinvented the entire stack, and we're serious about that. The ASICS, the platforms, that they're built on, the operating system, modular, programmable, API driven, the controller system on top. Everything had to be redone from scratch. >> One of the exciting things in following Cisco over the years, Stu and I have been following you guys from really the beginning, you go back, say 15 years ago. The big debate in Cisco is, should we move up the stack, and how should we move the stack? But now, the time, it's almost a perfect path, 'cause you got software defined data center, completely going full throttle, really relevant, lot of stuff going on at the root level of the networks, so networking's not going away anytime soon, and as the things I mentioned, security's obviously a big concern, and then now you got Kubernetes and Diane Greene from Google Cloud saying, "Hey this Kubernetes and containers and service meshes, feels a lot like some of the kind of coolness of networking." So the network engineers now have a kind of a path, if you will, to take their core competence, and drive more value around that. Talk about what that actually means. >> Yeah, so there's a couple of things, interesting things that you mentioned. First of all the data center moving to a software defined path. So we've applied a lot of learning from that. And so we've taken the fabric approach, the automation approach, and brought that to the campus with DNA Center, right. Basically Software-Defined Access and DNA Center. And DNA Center actually is built on a Kubernetes model, so in a cloud type of platform, to allow it to scale out with service offers. So we've actually taken both examples applied it. What does it mean from a network engineer point of view? Instead of repeating mundane tasks again and again, now they can automate network wide. The entire network operates as a single system. I can define a policy, and say "I need this user group, I need these doctors, to have access to these medical records. I want this telepresence application to get high priority." Specify intent, let that system automatically apply that everywhere. And then take data and analytics out of that infrastructure, to ensure that the intent was delivered as expected. It's a very powerful-- They can sort of instead of be boxed by box network engineers, now they're system wide looking at the entire network as a whole system. >> Yeah, Sachin, wondering if you can give us a little bit of insight here. You talked about customers not being box by box. Well, from the product side, you know, you spent a lot of your career helping define the catalyst boxes, and we watched the generations of catalyst switches over the years. Cisco transforming from being measured in boxes and ports, to being a software company. How do you, on the inside, measure that transformation? You talked about things like, the DNA Center and the like, but, what's that been like on the inside, and how do you measure internally that balance between software and kind of the hardware world? >> We measure it through customer success through that software. So how many customers were actually able to get a DNA Center - it's an appliance that has software embedded in it - and get value through the network. And I think one thing I'll tell you is, we found that while, reinvention of the network sounds scary, or "Hey, how do I even start reinventing my entire network, as a customer how do I start?" That you can take DNA Center, take the network that you have, and start sending data from DNA Center, as from your network, sorry, from your access points, from your switches, your routers, your identity product. Send it to DNA Center, and start getting immediate value. Immediate value. So what was the experience for this user at this time, how do I pinpoint where the issue is and go fix it? And so we find that, for these customers, yes the switches, the, all the new products we brought out are important because they're programmable, they have rich capabilities, rich data streaming. But, at the same time a lot of the products they have through a software model they can now get network wide assurance. They can troubleshoot, get automated remediation steps that Cisco recommends. And now the new announcement, if we go there is, how do we expose all of this through an API layer? >> Yeah, it's interesting, 'cause if you think back 10, 15 years ago, doing a network upgrade, oh my God, that was a scary thing for customers. You're thinking forklift, am I doing some major build out, I start up my core, I build out to the edge, it's generation shifting. What we hear from the DevNet team here is you gotta meet them where they are, add value, and then you can make change along the way, almost like we do with applications, slowly pulling things apart. >> Absolutely right, and one of the immediate values is assurance, analytics for assurance. Helping you troubleshoot better. But other piece of value that customers love and that we get great feedback, is you know, racking and stacking a switch sometimes, like in a branch site, they would pay more to get it stacked than the switch itself. Because imagine you know you've got a remote side, you don't have a highly trained person flying somebody out, getting them, installing it, spending a few days there, costs a lot of money. And now we're seeing we can automate onboarding your product, we can automate software upgrades for those products, using DNA Center with intent-based networking. So you start there. Then you start transforming it for policy based automation, some of the more advanced security capabilities that the system provides. >> Yeah, we hear day zero a lot, when some of those use cases, and then you see the shift happening with software as a holistic view. Wanna explore that with you for a second. Because if you think about the system, which I totally agree with by the way, it's awesome. Then you got the DNA Center. A lot of people like, understand it, and people are now moving to that, now trying to understand it. Share the mental model, on how people should think architecturally around DNA Center. Is it an abstraction layer, is it just a set of API's? What are you enabling with the API's? What's actually gonna be the result from that architecture? So, how should I think about it, architecturally, and then what are some of the enabling things that could come as a result? >> Let me explain this a little bit, maybe with two examples, right? On, an example of how it works, an example of where we think we can take this. So how it works is, before the API's on the switch would mean that, you can say, "Hey, how much memory do you have left," you know, "Let me copy an image to you," "Let me reboot the switch to upgrade it," "Let me check if it works." And that's the level you were operating at. When we say DNA Center is a platform and has API's, now you have an intent that you could express which says, "Take all the switches of this type, on this site, and upgrade all of them." Right, and now you have to go through all those steps behind the scenes and that's the abstraction that it provides. So those are intent-based API's. So what's exciting first of all is, look, with that, I can extend, integrate it with IT services, I can integrate it with ServiceNow for example, IP address management schemes, cross network domains. I can support third party, I could do all those things. What's exciting for me is, I'm gonna pull out my device, right? You think about it, this thing has a phone, it has a camera, accelerometer, all sorts of things. But the way it's exposed through the app developer, is through very simple API's and through an app store. We are-- >> So you're essentially enabling. >> We're unleashing innovation on that network. By taking away the need to understanding the depths of networking for the developer that sits on top. >> So it's really on top, a holistic view. So, you're taking away steps it takes to get something done. >> Right. >> And integrating other things. Is that-- on the app side. >> Yeah, from the app side now, I mean, you look at DevNet, and the capabilities that DevNet brings to the table, and now, of the app developer, our systems integrator can invoke powerful network technology without understanding the depths of networking. 'Cause what they're looking for is, you know what I'll give you an example, I'll talk about doctors and medical records. If you need to onboard a group of contractors to help out for six months and have secure access, you can now define that in an application layer, at an identity layer, and automate that completely through DNA Center, without understanding exactly what the network will need to do, in a highly sophisticated way, across all those boxes to make it happen. >> So is DNA Center a net new capability for your customers? >> It is. DNA Center's been around since last August. So less than a year. It is a new controller built for the enterprise. And so yes, many many customers are using it. But for a lot of customers, it's a net new powerful piece of technology. >> I gotta ask you a personal question. You've been in Cisco for a long time, you've seen waves come, and new waves emerging. Why has DevNet been so successful? And you got DevNet Create with the cloud native side kinda coming together, bringing those two worlds together. I mean timing's everything, right? In life, right? So is it timing, is it just-- What is the, I mean the success is pretty significant. 500 thousand developers, you know you guys have. And that's a great developer program. That's robust. >> Yeah. >> So it's on its way to continuing to rise. Why is it so successful? >> I'll give you my honest example. I think you know, networking, people have thought, is sort of big, you know, big boxes, is sort of what networking is. And we always tell people, that even when you think about switches, the majority of our engineering investment is in software. So my network engineers, yes they're plugging in a switch, but the majority of their life is operating the software on that infrastructure. And so by the very nature of networking and network engineers, they're actually very comfortable with software. They're very comfortable with scripting and those kinds of capabilities. Now you enter DevNet. DevNet says, "I am now going to give you a easy way, sandbox way, learning and enablement, for you to learn the API's not just on the network, on the collapse systems, on the security systems, in the data center, and be much more powerful at how quickly you can move. You're much more agile." So I think it was a pretty natural evolution for the network engineer. Now, the last piece of the puzzle was the network. And now with DNA Center, we provide the same sort of API abstraction for the network itself. And I mean, look, so far, network engineers are loving it. I was talking to Paul, who's at Presidio, who's a network engineer. He's actually one of the DevNet Creator award winners. And, loves it. He's a network practitioner, and now can solve problems for his business as a partner and his customers, could never do before. >> Great point. I mean we interviewed Paul, great guy. But you just said something I think is really interesting. The people in the community, the network engineers, they've been solving problems. That's what they do. >> That's what they do! And with software! >> And so now you add scripting to your point, this is not new things, it's not foreign, but the networks are core. >> Yes. >> They're not learning Python to get a career change. They're extending their capability. >> That's exactly right. They're not doing Python just to do Python. They're using Python, they're using the API's, they're using the DNA Center platform to become more powerful as a network engineer. For networking, to solve business problems. >> Yeah, I think the timing, combined with just where cloud is, where you guys are with the programmability, it really is, right, again, timing's everything. >> It's exciting. I think-- >> So, one of the things we've been looking at with Cisco is, Cisco's moving up the stack. And I think, we want you to help connect the dots for us. Intent-based networking really is one of the ways that networking people are building applications. I think in the key note, they walked through some specific examples. What kind of things are people building with intent-based networks that they couldn't do before? >> I think, you know, so some of the app examples that sit on top, right? So, I'll give you simple examples, and some other interesting things. Accenture, for example, is doing automated software updates, much more intelligent software updates, based on you know business information, like who, how many people will get impacted with the update, tying it to the service process with ServiceNow. That's an Accenture use case. World Wide Tech has taken DNA Center, made it mobile. So instead of consuming it on your laptop like this, you can now consume network status, client status, health, on your mobile device. You've got, Dimension Data, that's actually doing SSID leasing. So in your sites as a customer, if you need to create temporary network connectivity, for certain types of users, you can deliver that automatically. Right, so you've got examples of all kinds that are leveraging the power of the network, without actually have to understand all the nitty gritty details behind it. And as a developer or a systems integrator, providing tremendous more value to our customers. >> It's interesting too, one of things that World Wide Technology said here when we interviewed them on the first day yesterday, was, in the old model, there was dislocated capabilities. They'd go talk about business outcomes, essentially what the intent was on the business side, and then, "Great we're done. Now let's shake hands with Cisco." Cisco would come in, and the networking guys would come in, "Okay, here's what you can do." So now, those are coming together. >> Yes. >> Which shrinks the accela--, the time frame, on the execution. So, to actually put it together, that is really kind of DevOps-like. I mean, this is integration, this is kind of like-- >> Right. >> This is a big trend. >> It's a big trend, because now the network has an ability through DNA Center, to take that business outcome, you described it as an intent, translate that into what the network understands, activate it, and then provide the data analytics and assurance, back to the application. And so, you're absolutely right. Before, you'd have to go manually, take that business outcome, and figure out now, how do I, you know, make this happen, through a network that did not operate as a single system. >> Yeah. >> And now the worlds are coming together, and our partners and our customers can move much much more quickly. >> Well you guys are doing a great job, we really think that the clear path to the stack, where the stack is integrating with networking, is colliding - in a good way - you've still got the hard core, software defined, networking in the data center and the networks. So it's awesome. I wanna get your thoughts on, as an industry participant, also Cisco executive, for the folks that couldn't make Cisco live this year, what's the biggest story? I mean we heard a lot of things. If you had to boil it down, what's the most important development happening this year at Cisco live? >> I think the big announcement is DNA Center platform. Where, it is an open API system which supports third party infrastructure, and has that API layer, accelerating innovation through our partners. But what I will tell you, is, that the important message I'd like to deliver, is they can start on this network reinvention today. It is not about a rip and replace of the gear that they have. They can add the software capabilities of DNA Center on the infrastructure they have. And get immediate out the gate benefit, with things like network assurance, DNA assurance. And so I really encourage everybody to look at this and say, "Yes, you know what? Maybe I'll get to the last step later." Start now. You're gonna see immediate value. >> And there's not a lot of-- there's really no disruption. >> And there's no disruption in that. >> They can put their toe in the water, or jump all-- full throttle. >> Exactly. And once you like the controller approach, you can see how it integrates with API's, with everything else in your IT processes, you can then take more steps, like software defined access, policy based automation. Which are more intrusive, and but provide tremendous value. But there's a way to start that's not intrusive. >> Well we're super excited to see how DNA Center continues to accelerate, we love what's going on in DevNet, DevNet Create, you're seeing the cloud growth happen, you're seeing all kinds of new modern era things that we've never seen before. So congratulations. >> DNA Center platform, multiplied by DevNet, right? It's exponential growth. >> Yeah, so it's a great wave. People's jobs will become easier, again, automation for the right reasons, accelerating new value creation opportunities. This is theCUBE. Here in Orlando. Bringing you all the action at Cisco Live. Extracting the signal of noise. I'm John Furrier, Stu Miniman. Stay with us, we've got more. Here on day two of three days of coverage. Stay with us. (music)