>> Live from Barcelona, Spain, it's theCUBE covering Cisco Live! Europe. Brought to you by Cisco and its ecosystem partners. >> Hey, welcome back, everyone. We're live here in Barcelona, Spain, for Cisco Live! Europe 2019 Cube coverage. Three days, we're in day two of three days of coverage. I'm John Furrier, your host, with Stu Miniman as well as Dave Vellante's been on interview. Our next guest, Saurav Prasad, Principal Engineer and Technical Marketing at Cisco as part of the Cisco DNA Center Platform. Welcome to theCUBE, thanks for joining us. >> Thank you. >> So you guys are having a DNA take, and we're in the DevNet zone all week. This has been a real revitalization within Cisco DevNet, Cloud Native, Cisco coming together. The DNA center has been a part of this from day one. >> Yes. >> What is the DNA center these days, what's happening? >> Okay, so, let me take you a bit back in time, right. So, back in October 2017 is when we first launched the Cisco DNA center. Since then we have added a lot more application, work flows in the DNA center. And last year in May or June of last year, 2018, is when we launched the DNA Center Platform. And this protocol, FCS, some time during October of 2018. So, we now have the DNA Center Platform, which essentially is an open platform which lets our developers, our partners, our ISVs build applications on top of DNA Center which will let them talk to the network. And the way they do it is using our APIs, our SDKs, and then we have a lot of other modules, which help them interact with the network via the DNA Center. Now the benefit of this is not really with respect to APIs or SDKs, it's more about we give them a very easy way to talk to the network. Instead of talking to 10,000 network devices, they talk to one DNA Center. So, that's the, you know, idea behind the DNA Center Platform. >> Well why not expand a little bit when we've been talking about platforms in general for many years now, and it's one thing to say you're a platform, but the proof is, who's actually building on it. What can they do on it? So, you've got the platform, FCS, first customer ship, it's available, it's launching. What can you tell us about, you know, real customers, what they're doing, give us a little bit of the spectrum as to what we see out there. >> That's right. So before we FCS'ed our platform in October, we actually relied on early field trials for almost three to four months. And in then in that time we were actually working with our 15 top partners. And this was across the world, right. So they were actually using the platform to build some integrations from their side which was beneficial for them, right, so these are partners like Dimension Data, Accenture, WWT, and I'm just naming a few of them. These are all listed on our DNA center portal, on DevNet. But, then, we were working them and we were actually looking for feedback on whether it was useful and we found that it was really, really useful for them to build some good applications, good work flows, good integrations, and that helps them drive their own business with their customers. >> So, what's the mission of the DNA center? What is the purpose? Why do you guys exist? >> So, the DNA center is built to provide you intent based networking. So instead of you having to go to each and every network device and provision things on the network devices, you now go to the DNA center and say "Here is my intent!" An example for an intent would be, "I want to prioritize Cisco job or traffic". It should be high priority. Now that means there is a lot of network devices that I need to provision quality of service. I need to make sure I have the right cue instructors in place. And guess what, we have so many devices, each one of them might have some different CLIs, different architectures, we now give them one single place where you provide the intent and not worry about the device level details. And I am just giving you one example. There could be a lot more where, for example I'm getting the telemetry back from a network. Each and every device is saying I am having some issues but they might all be the same issue here. What DNA center does is takes all of those issue provides you an insight into what really is happening in the network, so that's our idea of DNA Center. >> Saurav, come on, who doesn't want to use this? Everyone who's gone out and provisioned a device knows how much a hassle it is. I mean think about the manual labor involved. Just going out and doing all of this stuff so it's an action center, basically. You take action, one spot, window into the network policy, whatever it takes. It's driven by, and now applications can come in as well. Am I getting that right. >> That's right. So the greatest work says, again this is what we do with platform is, different partners, different customers, might have some different workflows. So within the DNA center we have decided, here is how the workflow should look like. So if I want to do an upgrade of a network device, here are the steps I might follow. But when you use the API's, you can almost define your own workflows. So this allows you the flexibility of building your own workflows. That's one example. Other is, say for example, I need some feedback from a different system, not the network maybe some other IT system. I need to get some information from them and based on that, I need to configure something on the network. You cannot do that automatically. There has to be an application in between which talks to both of these systems, one of them being the Cisco DNA Center. Now this allows you to do that. If I have the API's, if I have the event framework, I can do all of that. That's the benefit of using these. >> What's the alternative if someone doesn't use the DNA Center 'cause this is a no brainer. You've got, I get the device piece, that's just a nice window. Now the platform allows applications to integrate and be programmable with the network. Why wouldn't someone use this, it's a no brainer. >> If you don't use this, what you do is you go to each of your thousand network devices talk to each one of them and take care of all of the device level details and do it. It's doable, people have been doing it for years now but now we are making it slightly more easier to make it faster. >> Well, it comes to, we have been talking for years the need for scale and if you don't have good automation if you don't have tools to be able to help you there, you're not going to be able to reach the scale that you need for your business, explain why this is important. >> For example, what we are seeing is and we have been talking about digital networks for some time now. What really is a digital network, that's a key point to understand here. What we are seeing is there was a time 10 years back when you had to roll out a new service network admins, network architects had six months to provision that. Nowadays they don't have that. >> Six hours >> They probably have six hours, that's right. In order for you to do all of that so fast, you really cannot go into each device and talk about it. You have to abstract some of that and that's what the DNA Center provides and using our API's we are now adding a new level on top of it, which really makes it much more easier for you to scale. Again, not just scale, also integrate with other IDSM systems, other IBM systems, other reporting systems. So this is all happening automatically, instead of you having to manually touch each of these systems. >> Talk about the plug and play process. How does that fit in with DNA Center, compatible, not compatible? >> So plug and play is an application or workflow within DNA Cneter. When I look at plug and play, every network device in Cisco has a plug and play agent running. I'm going to get into a bit of a technical detail here, but they have a plug and play agent running and so when this device comes up, say for day zero onboarding, you open up the box, take out the device power it up, the agent fires up. What it looks for is the plug and play server. The Cisco DNA center is the Plug and Play server. So now I am allowing you to onboard new devices. You could roll out a new site with 25 network devices, 100 network devices in a matter of minutes. >> So all of the configuration gets pushed down from the DNA Center? >> Exactly! So you build your own profile in DNA Center and attach the templates or the configurations. You say here is a serial number and when this device comes in, I push in all the configuration, I provision a new software image on it, so your device or your site is up and running. >> Great for campus, great for remote sites. >> Exactly, so you really don't have to send a network admin on every remote site to do that. >> Will it take policy so if I set policy up in the DNA Center, will it automatically take that down through? >> Yes, yes, yeah. Once a device is onboarded, it gets added to the Cisco DNA Center and once I do that, now I can throw in policies any kind of provisions. >> I don't mean to get in the weeds, sorry Stu, go ahead. >> What's great about a platform, you've talked about some of the partners. My understanding, not just some of the integrated partners like WWT that you mentioned but even some of the technology partners like IBM have services that plug into this environment. We've seen in platforms, where you can, one of the other dimensions is the customers and what are they asking for and how are there feedback there. Is there anything in the DNA Center platform that if one customer is asking for something that more customers are going to get value of that. I think back to the day of Salesforce. When Salesforce gets something, we add a new feature and that's something that can roll out, we can learn from all the customers, you get that fly wheel of development in a platform. >> What we are doing here is we are actually working very closely with Cisco DevNet on that. They have a partner ecosystem exchange. What's happening is a lot of this channeled partners technology partners, ISV's, when they build something they go into the ecosystem exchange and they can post it there. So its not just useful for them, there are other partners, other customers that can use it. They have a data repository of all the core, sample core and again, not everybody shares it to the extent what we would like because there's a lot of intellectual property which they have built and they might want to monetize on it but that is the whole idea behind the ecosystem exchange where I am allowing partners to share what they have built and this could be used by others. >> Saurav, talk about the success, what's the uptake? It must be well received, obviously we see a lot of action her in the DevNet zone. Give us some color commentary on what the momentum has been, who's using it, how? >> From our side, I'm from the business unit which is actually building this product. The way we judge whether this product is getting traction is what is the amount of feature requests I am getting? So, we are getting a ton of feature requests with respect to new API's that we want to expose. With respect to new documentation that we have to build. I mean, what we don't want is we release a product and we got no feedback. >> So what's the fee for requests? Backlog big or what's going on? >> Oh yeah, so for example when we launched we had a limited set of API's available. Now since then, with every release, now we have a release almost every month, where we are adding newer API's and newer functionality, we are actually adding more and more API's and again there is much more to add but that's the process and-- >> Just keep jamming and taking it in, backlog it, get it out there, iterating quickly? >> Exactly, and again, the one point to add here is we are not really just exposing an API, we are exposing an intent API so it's got slightly different. So instead of, say for example, I want to provision a wireless network, that is probably a 10 step process even within the DNA Center. What we want to give you is a single API which will do all of that and all of that heavy lifting will be done by the Cisco DNA Center platform. So, we will internally call the 10 separate API's. So for a developer who is building this, he or she may not be a network expert, they might not be an expert into how the network works so all they have to do is call one single API and all of the details or all the heavy lifting will be done by the platform, so they don't really have to worry about some of those details. >> So this is where the automation will get done on behalf of the customer. They'll come in, deploy DNA Center understand what's going on and that's where they do all of their work. Figure out what to do, get it done there. What's been the biggest use case so far? >> So, a lot of use cases. Like, we have a partner who is actually building a mobile app so we have a DNA Center which is sitting on prem in their own data center, they can go and look at the browser, open up the Cisco DNA Center console and look at the various workflows or see what's happening in the network. They might see there is a router which has crashed. Or an application which is having some application performance issue but what we want to see, is also, send us even send remotely and now their network admins could be walking in a grocery store, for example and the mobile, that alert shows up. Guess what, that is application is having an issue lets do the debugging so we will provide you all of that details within our API's, which can then show up in the application externally. >> So DNA Center platform has a takeover going on in the DevNet zone. We see classrooms, we've seen labs, give us a little bit of the flavor of the solutions for the next hour as well as at the show in general. >> In general here at the Cisco DevNet zone, we have a Cisco DNA Center takeover going on right now. We have workshops, we have sandbox labs, we have learning labs. You can go to any one of them and try it out. That is not only for this hour, that is there for throughout the show, but for this hour, we have a tech talk going on from one of our distinguished sales engineers Adam Rattford, he is talking all about DNA Center Platform in deep dive, showing live examples. We have some demo systems up and running here where you can actually see how we are able to generate events, how we are able to send events to external systems, so all of that is going on. Plus, we have all of our experts. A lot of our experts from the engineering team are here on the show right now on the show floor so if there are any questions around DNA Center Platform they will be more than willing to help. >> The brain trust is here. >> My understanding, I mean, when I have talked to people the DevNet group has labs running all the time. And that's what's great, I have talked to customers that say, I need to be able to play with this and here's something that's online, it's in the cloud I just do with it whenever so. >> Just to add to that, of course for our customers, our partners, our developers who want to try this out, they are more than welcome to come and join us in the Cisco DevNet zone here. Even if you are not at Cisco live, these sandbox lives are live online and we have I think around five or six of them and we are adding more to it. You can go anytime, try our API's on that sandbox. You don't really need to have your own environment. Now of course when you go production with it you will but just for trying out or building some applications, you can do it on the sandbox. >> Saurav, thanks so much for taking the time sharing some technical insight, went a little bit deep on the plug and play but appreciate your time coming on theCUBE, thanks for coming on and congratulations. DNA Center, the Cisco DNA Center Platform, the official name, really an oasis, a place to go in and configure the networks no brainer as far as I am concerned, check it out. theCUBE's bringing you the DNA of the show here, which is all the action, coverage, I'm John Furrier, Stu Minimin. Stay with us more here live in Barcelona and we will be back after this short break. (upbeat music)

>> Live from Orlando, Florida, it's theCUBE, covering Cisco Live 2018 brought to you by Cisco, NetApp, and theCUBE's ecosystem partners. >> Welcome back everyone. This is theCUBE's live coverage here in Orlando, Florida, for Cisco Live 2018. I'm John Furrier with theCUBE. Stu Miniman, my co-host, for the next two more days. We're in three days of coverage. Our next two guests here from Cisco Ronnie Ray, Vice President of Cisco, and Prakash Rajamani, Director of Project Management at Cisco. Guys, welcome to theCube. Thanks for coming on. >> Thank you, John. >> So all the buzz is about the DevNet developer aspect, the rise of the network engineer moving up to the stack while taking care of business in the software-defined data center, software-defined service provider. Everything is software-defined. You guys are involved in the DNA Center Platform. We talked about the DNA Center, the product. This is a real innovation environment for you guys, so take a minute to explain, what is the DNA Center Platform? And how does that compare from the DNA Center? How should customers think about this? What is it? what's the offering? >> Absolutely. So if we just walk back about a year. A year ago we launched DNA Center. DNA Center is the product, and that supported things, like SD-Access, which is absolutely a new innovation about Software-Defined campuses. Through the year, we've launched showrooms, through the year we've launched Enterprise Network Functions Virtualization, we have capabilities in automation, and these are all product capabilities that DNA Center has. What we're doing today and this week in Cisco live and in the DevNet area right now is that we have launched DNA Center platform, which is the ability to open up and expose all of the APIs and the STKs that now makes DNA Center a product that our customers, our partners and developers out there can now work on and create new value. It could be apps, it could be integrations, it could be new devices, third-party devices that Cisco's never supported before, but they can now make that supportable in DNA Center because we're giving them the tools to do that. >> So this is not so much a customer thing, it's more of a partner or app, is that kind of how this goes? So if I'm a partner, makes sense. is this kind of where it's different? I mean, where's the line here, or is it open for everybody? >> It is for everybody. If you are a networking expert and you've done CLI in the past, what we are doing is making API simpler, we are making them intent-based, which means that they can achieve a lot more and this is open to you as a networking expert, you as an application developer, you as a partner that is providing, creating your services for your end customer or client. All of you can now use DNA Center platform to create new value. >> This is great, it's for everyone. So this is where, if I get this right, we love this notion of DevOps on cloud, Susie and you guys have been talking about network programmability. Is this kind of where it is? We're talking about network programmability, is this where the APIs shine, and what's our vision? >> This is truly network programmability, in fact in the past what we've talked about is device programmability, but now what you're doing in DNA Center platform is really expressing intent and using APIs that apply across the whole network. Prakash can probably give you some examples of what these intent APIs look like. >> I think as Ronnie said, we like to call it Network DevOps, I think Susie calls it that too. And this is the way in which Network DevOps is conductible. There are two kinds of target market that we look at. One is the network engineer who understands everything network-centric, who knows all the nuances, and are very comfortable with those, but then being able to achieve those through a programmable API, that's one market. The way we want to go with the intent API is for the software engineers who want to be able to say, I want to prioritize YouTube traffic less than my network, and I want to prioritize my custom-built app as the most critical for my enterprise, as the most critical on my network. And I want to express that as an intent through an API, and then let the DNA Center platform take care of making that real on the network without having to worry about all the technologies and all the, >> How to provision it, what's going on under the hood, essentially to them it's a call. >> To them it's a call, and it's taken care of. >> That is actually seamless to the software developer, by the way, who doesn't want to get in the weeds of networking. The networking guys who are under the hood, what does it mean for them? They get to provide services to the developers, so it sounds like everyone's winning here. What's the benefit to the network engineers? They get scalability? I see the benefits to the software developer, that's awesome, but where's the network engineer, what are they getting out of it? >> They can achieve more things faster, they can get deeper, and this is absolutely making it simpler for them operationally to run their network. So they can basically free up time to do other tasks, like design and architecture that typically is, very hard to explain. >> Cooler tasks. (laughs) Not boring, mundane, cut and paste the scripts, CLI scripts, to another device. >> Absolutely and that's one part. The other part is about the cool new apps that they can create because there are use cases, even if you look at all the show floor, the companies that are here in Cisco Live and that they come every year, there are use cases out there that even collectively as an industry we cannot solve, that needs to be solved in the context of the company and the environment that you're in and so the network expert that's sitting in a customer environment can say, "Okay, I have this problem, let me solve it, "let me go build-" >> But they're gettable problems to solve now. Because now you're taking off more time, but also cloud and some of the software-defined things are now at the disposal to create that creativity. Is that what you're getting at, this is the new opportunity. Is that what Chuck was kind of referring to in his keynote around getting at these new use cases? >> Certainly, this opens up a new use case because this is a new way to program across the entire network in a much more simpler fashion than it's ever been done before. >> So when I hear a new way to program, I want to understand, what's the learning curve for this? If somebody understands the rocky APIs, is this a short learning curve, if they don't, is it a longer learning curve? >> So what we have done from a learning curve perspective, we have worked with a development team, we have learning labs where somebody who's not familiar with programming completely can start with the basics of, okay, how do I get started with DNA Center platform APIs and get started and go through a sequence of learning labs to get them completely familiarized with everything. Somebody like what you said, like a Meraki person, who's already using the Meraki API, for them, anybody who understands REST XML APIs can just turn around and there's a bunch of new APIs available that they can understand, program, try within the product, and then get sample codes and then build on top of that. So it's that easy as that. >> It was interesting, I was walking through the show floor, talking to some of the customers here, and for some of them, what's off the shelf is good, but I hear them griping about, not about Cisco, some of the partners, like "I can't customize what I need." One of the challenges we've always had in IT is, it's great if you can take the off the shelf, but everybody needs to tweak and adjust what they have. How's that addressed with this solution? >> From a customer's perspective, because we provide in our product we provide a specific set of capabilities, but when it comes to API, we make it much, much, much richer and granular so that people can create any workflow that they want. The workflows that we create in the API context is in three formats. We have what we call as tasks, which are individual operations that we perform, and then we group the tasks and offer them as workflows. And we group the workflows and offer them as an intent. So as a user, based on what level of granular they need, you can go to the lowest level task, or you can go all the way up to the intent based on your skillset and then use them and customize them as it fits your needs. >> So they can get up and running pretty quickly, sounds like, and if you know APIs then it's just JSON, it's all the same XML, all the great stuff, but I gotta ask where this goes from here because one of the things we were talking about before we came on camera is, we've been covering all the Linux Foundation, the Cloud Native Computing Foundation, CNCF, you've got Docker Containers, and containers now have been a great thing. Pretty much check, standard, everyone's using containers. And it's great, put a container around it, a lot of great things could happen. Kubernetes and then microservices around Service Meshes, Diane Greene mentioned in her keynote with Chuck Robbins, Istio was a big hot, one of the hottest projects in the Linux foundation, so that's kind of microservices, this sounds like it's got a lot of levels of granularity. I love that word because now when you get to that point, you can really make the software targeted and strong and bullet-proof. How is that on the road map, where does someone who's actually looking at microservices as a North Star, what does your offering mean for them? Is it right in line? What's the progression, what's the road map? >> So, from a microservice perspective, DNA Center as a product itself is completely microservice-based architecture. There's 110 microservices today that make up what is DNA Center. This gives us a flexibility to really update every single service, every single capability, and make it almost like giving customers ability to do this every two weeks or every four weeks, new changes, new announcements, in a very simple fashion. That's kind of how the part is being built. What we eventually want to do is extend the platform as an ability for partners and others to build microservices that can be built and deployed within DNA Center over time. That's further down the road, but given that solution and given the strategy where we are as a product architecture that lends us to extend that to them. >> It's natural extension, so basically you're cloudified. You've got all the APIs, so if a customer wants to sling APIs, customers want to integrate in, like you mentioned, ServiceNow, they can do that easily today, and then you've got some extensibility in the road map to be kind of Cloud Native when things start growing. Timing's everything, it's kind of evolving right now heavily at the Cloud Native. >> I mean that's the benefit of this architecture, that you can really pick and choose where you want to run over time. We are right now on a box, an appliance that helps us solve the solution, but there's nothing that stops us from going anywhere. >> So Ronnie, I want you to talk about the significance, this is an open platform. I've watched Cisco my entire career, and always Cisco's been heavily involved in standards, but takes arrows from people as to how they do this. This is open, what does that mean? And what's that mean to your customers? >> Absolutely, this is basically opening up Cisco to industry-wide innovation. So until now, if you look at everything that we've done on DNA Center and on some of the other Cisco platforms that Cisco developed, but we are now getting to a point where with DevNet, now with 500,000 developers registered, we have the critical mass to basically say the industry can come and develop on top of Cisco platforms. And so this is completely new kinds of innovation that we will see, use cases that we've never thought of, and this will happen. And of course we will continue to contribute to all whether it's IETF or whether it's OpenConfig, all of these in with the YANG models that we are doing across the industry, those will continue, the open source confirmations that we do, but this is really saying, okay, let's provide our best customers and our partners and of course the individual developer that's out there a way to today build new creations and maybe tomorrow there's a part to monetize that. >> It's interesting you bring that up, I love the open. We love open, we're open content. You guys are now open networking, for lack of a better description. Chuck Robbins talked about in his keynote, one of the things I was really impressed on, he highlighted something that we've been talking about, is that the geo-political, the geo-technical world, is a huge factor, you look at just cloud computing, you've got Regis, you've got GDPR, I mean all these things going on, you mentioned assurances off camera, this is like a huge deal, right. You've got a global tech landscape, you've got global tech compliance issues, so you got this now open source and it's whatever fourth generation where it's part of the entrepreneurial fabric. So Ronnie, I've got to ask you, you've been an entrepreneur before. With bringing entrepreneurship into networking, what's the guiding principles, what's your inspirational view on this because this is really, not only save time for engineers, it makes them part of an open collaborative culture, like open source which you're used to, bringing an entrepreneurial vibe to it. >> Absolutely. >> This is a big dynamic, what's your view on this? >> It's a huge dynamic and I can talk from personal experience, you know when I've done start-ups and I've raised money or put my own money into it, 70% of your calories go in building a platform. So you're just looking at how do I store data, how do I process data, how to I look at availability of systems, and 30% of it really goes into building a use case. What we are doing with DNA Center platform is basically saying forget about the 70%. We will give you normalized data, whether it's for Cisco equipment or whether it's for third-party equipment. So the STK will allow you to bring in Juniper or Huawei or Aruba or whoever that's out there and you can bring that into DNA Center, so now you have a view of the entire network, Cisco and Non-Cisco. You have normalized data for all of those and you can configure all of those, you can image update all of those. It's very very powerful. Just from an ISV standpoint, individual available standpoint now you are kind of unlocking, making this almost democratic. >> You've done the heavy-lifting. >> Yep, absolutely. >> That's what Cloud is all about, but talk about the creativity because you mentioned that entrepreneurial, a lot of the energy goes into trying to find the fatal flaw, is the product gonna be product-market fit, you do all that heavy-lifting and bootstrap it, right now it's simply, okay, I can sling some APIs together, get a prototype, then the creativity starts. Talk about the creativity impact. How do you see that impacting some of these new use cases, these hard problems. This is gonna come from, not some guy coming out of business school saying, "Hey, I'm gonna go hire "some engineers and solve that big, hard problem." It's gonna come organically, this is a huge deal. >> This is a huge deal, and because we're making it simpler it can come from any quarters, it doesn't have to be an established company, it can be an individual person that can't solve any use case, and then we ask Cisco, not only do we have, and of course the majority share in the market, but will also we have the platforms, like DevNet, and DevNet now has an equal system exchange, so if something that's cool can float up in the exchange can be voted on, can become something that becomes an absolutely easy part to monetization for somebody, that basically saying, "Okay, how do I marry business "and how do I take network and bring them together." >> This is awesome and it's also external to Cisco, but talk about the global impact. Just outside North America, massive growth, you're seeing things going on in Europe, but really in the Asia and China, huge growth markets going on. When you go to China, talk about mobility, they have mobility nailed down. India is absolutely on fire, growing like crazy. The talent, this is a melting pot of tech talent. How do you make all that work from a Cisco standpoint because what you want to do is bring the goods to everybody, that's open source. >> Absolutely, so think about any of the logical place that people go to with, given the way that the platform is already built, which is, it is Cloud Native. We've not in the cloud yet, but at some point the platform will go to cloud. And we are looking at harnessing the creative talent worldwide, whether it be in Asia or whether it be in Europe, or whether it be in the Americas, really doing that new value creation and taking that to the masses. And Cisco has the right to claim this market, we are absolutely in support of folks that want to do that. That's why DevNet has all of the learning labs and the sandboxes and everything else that's there in support, these are free to use. We want people to come and learn and co-create on the platform. >> And making it open and collaborative, the community aspect of it. >> Absolutely. >> Alright, final question while you guys are here, obviously you're at the Cisco perspective, but put your industry landscape hat on, people who couldn't make Cisco Live this year here in Orlando, they might be watching this video either live or on demand when it goes up to YouTube. What's the big story, I mean obviously what you guys are doing, across the whole show, what's the most important stories that are developing here this week that people should pay attention to deeply? >> So in terms of looking at the openness of the platform, Cisco is an open platform, API is really the new CLI because that's the way that you'll talk to the network. And think about what Chuck said at the opening keynote, this starts from the user, the things that you want to do to the applications, wherever they live, whether it be in a cloud, in a multi-cloud environment, Cisco is bringing all of that together. >> Prakash, what's your thoughts? >> Adding on to Ronnie's point, the openness and something that new that we are doing, not just from campus perspective, but campus, branch, data center, and making it open across everything, which is what Dave Goeckeler covered today in his keynote, I think that's something that Cisco is not just looking at one infrastructure, but across all of his portfolio and making it unique is really something that people should take away from this one. >> That's awesome. Great stuff, well guys, thanks for sharing. Thanks for co-sharing, co-developing content with us. I gotta say just from the hallway conversations, people are impressed that you guys are taking a very practical approach, not trying to boil over the ocean here with all these capabilities and announcements, focusing on the network value, where it fits in, and being Cloud Native from day one with microservices is a good start, so congratulations. >> Thank you. >> Thanks for sharing. Live coverage here in theCUBER. Day two of Cisco Live, I'm John Furrier with Stu Miniman. More live coverage, stay with us here at day two as we start winding down day two here at Cisco Live in Orlando, Florida, be right back.