(upbeat music) >> Live from Barcelona, Spain. It's theCUBE covering Cisco Live Europe, brought to you by Cisco and its ecosystem partners. >> Hello everyone welcome back to theCUBE's live coverage here in Barcelona, Spain for Cisco Live Europe 2019. I'm John Furrier with theCUBE, with Stu Miniman and Dave Alonte also here doing interviews. Our next guests, two guests from the DNA center platform, Cisco, the agent platform team, Prakash Rajamani, director of product management, Cisco and Ronnie Ray, vice president of product management, Cisco, the DNA center platform growing 70% of the use cases, software distractions, API automation. Congratulations. Great success. Thanks for joining us. >> Thanks John. >> Big Fan of the DNA center. You guys have made great progress. Take a step through us. The positioning, how things are rolling, what's some of the feedback? Where's the DNA center platform at right now for Cisco? >> Yup. >> So DNA center was launched about 80 months back and it's probably one of the products in Cisco that has completely started to transform how we do the selling motions. So this is one of the key drivers of Cisco moving into light sensing mode switch, more software like. Now as part of how we do management Typically and traditionally it has been very much a manual driven process there's some reporting but it is a lot of expert light capabilities that you need to have to do management of the infrastructure then it's kind of moving that access to where you can now do machine-lift management. Of course it doesn't solve all the use cases absolutely as you mentioned, more than 70% but there's a whole host of new capabilities that you have to put on top and that's where developers come in because this is a platform that's built for developers to be able to extend it's capabilities to really look at solving problems for our customers. >> I think you know, after listening to all the announcements in temp based networking, ACI anywhere, hyperflex anywhere, data at the center of the value, data centered as you guys say, it's clever but I think it highlights what you guys are doing because you're talking about programmability of the network as two worlds collide actually three worlds collide, Cloud, On Premises and Edge into one network, you have a network, the network is key it's getting bigger, to cross domains is a big theme here, these are hard problems that are being solved by Cisco more complex cause there's more moving parts but it still has to operate as one network. This is essentially highlights the success of the DNA platform, am I kind of getting it right or is that kind of in line with how you guys see it? >> Sure, I mean I think Cisco DNA centered I mean if you look at the evolution we started in the network domain. You're absolutely right we have kind of extended to the brand change, there's nine integrations that are happening with the data center integrations, happening with the cloud, so yeah absolutely looking at the fabric that we launched about 18 months back now extending and stretching to all of those domains and wherever users connect and wherever users go to and that's of Cisco data center but think about that as we kind of do that, yes there is a change that also required not just in the product but also in the IT process because earlier companies had silos of things and now those silos will be forced to work together and CI was one that our network folks that support us because really they want to see cross domain bring power to the organizations but we are the enabler of making that happen. >> No brainer. >> Prakash, I'd love for you to take us inside ya know, we love looking at the product management piece here because you've had a lot of constituencies. You've got the internal product teams that all I'm sure want to get in and mature and expand their used cases. You've got all your partners that are building the platform. You've got the customers asking for feedback You've got a - ya know, a lot of options to choose from which is a good thing but you've obviously got limited resources. So take us inside that, what you've learned over the last year and how you helped prioritize and move this product forward so fast over the last 18 months. >> So one of the main things we did when we started with Data Center is to start thinking and having the vision to get a data center platform. With that in mind, every feature, every capability that we built in the product was built API first before we built a UI around it. Right? That has helped us immensely in the last couple releases we've started delivering features as APIs even before it had a face to it, and I think that has helped us prioritize and make sure that we are able to meet the demands going demands of customer or partner we had a customer who was like "I need this feature now" and we were hands strapped, we had a big back log, we couldn't get things done but the fact that we were able to get the APIs we were able to work with the customer and say "Hey here you can wire these three APIs and you can get what you're looking for" and he was like "Wow, that's so simple and I'm on my own" he was happy, we are happy we are able to manage our back log better. So I think the main strategy for us that's working is going API first on a pragmatic basis. This is us moving completely software driven as Ronnie was highlighting earlier in that relevant process that is helping us get there and that's part of it >> Well, it's customers a lot I mean they get to roll their own if you will without having be customized, it's still standardized with the APIs >> That's right, right? I mean the benefit is as you start getting into the 30% used case where "Hey, what's coming out of the box is not meeting exactly what I do today" we provide very grander APIs to very business driven, simplified interned APIs. The grander APIs allows the customer who wants to say I want A, B and then D and E to move forward compared to intern based API who is using the pride in the simplicity in driving that formula. >> Yeah, Ronnie I'm wondering if we can up level for a second here cause feedback I've gotten over the last year. Ya know, a year ago we heard Cisco is moving heavily towards software. When I talked to a lot of the partners both technology partners and channel partners they said this had a ripple effect inside Cisco it's not so much okay here's the skews and here's the new boards and here's the products but I need to sell a solution and therefore that's platforms that I have to have and therefore everything needs to work together and I have to think API first and like it does significant changes to how Cisco is, the joke I used to have is Cisco is like 100 companies and some people were like "Well, maybe it's 100, maybe it's 200." But today it's now something like platform is a unifying place, is that what is your solution set part of that drive and is that something you're seeing more broadly inside Cisco? >> Certainly, I think you're absolutely right that is does have a unifying effect if I might put it that way. >> Yeah Right? Because there's so many different capabilities that existed in different tools that are coalescing on Cisco data central and which is becoming part of the platform which is now customizable by our entire development community but think how fast that happens in a now within the sales force, within Cisco as a company there is no more cross domain knowledge that'll be required because now it operates different parts it can tune different things, that also means that is supposed to change the business model because going into software and kind of bringing it together and is increasing Cisco is obviously ya know foyering into softer subscriptions, this is a key product that's kind of supporting that, so in many ways it's not just the technology, it's not just APIs but also as a business process that's changing Cisco just like it'll change customers. >> One of the things we're seeing is a lot of design thinking principles this year. Love the new positioning bridged to the future bridged to tomorrow, wherever it goes but it's clean. Connecting the worlds are connecting together through the network get that. What has been some of the challenges and opportunities you guys are seeing around simplicity? Love this API, exposing API allows for customization, I love the broader intent based templates are great but it's hard to make things simple. Can you just elaborate on how you guys are thinking about the product short, medium, long term in terms of continuing to work the back log, I'm sure the feature list is growing like crazy but you got a challenge to make it simpler. >> Absolutely >> How hard is it? What does it entail? Share some insight there. >> So lets take the question in two parts and Prakash can talk to the product simplicity because that is a certainly something that we've got to manage very very carefully but think about also when simple doesn't just mean usable product, it also means a product that can fit into the ecosystem and make the process simpler. So there's a lot of deeper understanding that we are developing through the learning as we work with customers and how do we embed how do we make customers life easier how do we make the process easier and then after goal is how do we make their operational expenses lower? Because we want them to go faster, we want them to go faster at a lower cost and so there's a certainly both learning and investment that's happening there and the product side Prakash. >> On the product side it's about how we used to build to how we are building right now the way we used to do was a new feature comes in it goes to the device layer first the device team builds it puts CLI around it ships it off, sends it to the management team and the management team says "Oh, I got to support this feature" They go, they wrap a UI around it to support the feature, ships. Now we have flipped it turn completely around we start with like what is a customer's work field? What do they need to do and how can we do it in the minimal steps? Once we identify that we push that down to saying "Here is what the user interface looks like here are the three steps that they need to do. That trickles down to saying what we need as an APA on the device layer to develop the feature so we've gone down from going a bottom up way to build a product to a top down, customer driven, used case driven way to build a product. That means we are addressing the customer head on from a simplicity perspective and that's basically what has made us successful in moving the ball forward on this one. >> What has been some of the customer feedback? Can you share some anecdotes around some of the early customers you started rolling this out and what are the ones receiving on the receiving end today saying? >> So when you see from a simplicity feedback perspective I have a large retail store rolling out like maybe 60 APs in a single store over night and they've gone from having that be done over three nights to one person spending 20 minutes putting all the APs up going to the tool and the tool recognizing everything that's come up and deployed. So it's a night and day transformation on how it used to be to how it is right now. So the simplicity >> Sounds like the old way was >> Sounds like you saved a night in a day >> Manually configure, go put a wireless ping to it >> Yep, the old way was yeah you go you plugged the AP, you come back you look at the tool, the AP is there >> Check the channel, stuff is there. >> Map it to the right controller, do all the mappings Now you don't have to do anything just plug the APs and upload preloaded to say these APs are going to the store. The tool takes care of the rest of the stuff that's how simple it is become >> It's almost like old way new way What why are we doing that? And it's good when they have consistent environments with policies there's definitely more expansion. I get that, what about other used cases? Wireless is one hot one, I could see that branch off it's deployments what are some of the popular used cases that you're seeing in the customer base I know you got a broad base but what are the ones what are the patterns that are emerging out of this? >> So let me start another then have Ronnie chime in on the used cases he's seen. Some of the ones that are probably very transformational is that on the policy based used case, we have companies turning around and creating small subdivisions within their organizations. We have a large government in Yasha who is deploying that, they have 20 divisions. Earlier to do that it's extremely complex. They have to go in, they have to understand what division, who is using on which device, which ports mapped to them, just planning that it says it's so huge. For the new policy different approach that we have going, they don't have to know about anything they just need to know Prakash works for division A, Ronnie works for division B assign me to respective divisions, as I come in my policy gets right over to the network. I deploy the network as is, as I speak that is basically the level of simplicity that has changed and that all ties back to doing your network from a policy perspective not a networking from a feature perspective. >> Got it, Ronnie any comments on used case on your end? >> Yeah absolutely so think about we've talked about assurance we launched segmentation that's doing very very well of course even with when all of the public acknowledgement that goes with it but an interesting used case that's come up which is in fact in the keynote this week at Cisco live is about IUT extensions. So Data seto owa is extending to the factory floor, the production equipment and transportation and these are tremendous neo opportunities that are both for companies to kind of look at IT and OT and how this comes together, again going back to the unification simplification theme that do many more things at the same time they try to make it in a rationally much more operable. >> Okay so lot of progress in 18 months give us the road map going forward. We're at the beginning of 2019 what you'll be looking for, can a high level show show us what we should expect to see down the road >> K so from a road map perspective it's in a think about that we've been very focused on getting the customer value. Now the lens is kind of shifting to how do we deal with large enterprise capabilities? So both the hardening of the system itself, how do we look at, for example multiple clusters opening up in diverse locations will give us geo diversity and support there from that perspective and high availability. So these are enterprise class features every large customer requires it and as they move from smaller deployments to full scale deployments that is something that the labs look to need >> Yeah, Prakash when I heard you talking about things I need to think a little bit differently. It's like okay I'm used to going into the deploy and it's going to take me three days wait how do I learn about the fact that I can do it now in a couple of hours? What kind of training or retraining or education is that part of what you're doing in your team or where does that happen? >> It's part of the education, part of the videos we double up and publish to customers so that they don't think about this as I'm going to approach my same 20 steps and think that I'm going do that through data center except that I'm going to do that through a user interface. The first thing that we tell them is like "You're going to do 20" You're going to do two. Right? So the immediate feedback is oh does it address everything I want to do? And so that's the 70% used case more would rather say yes it addresses only thing is we have simplified it, we have compressed it so you don't have to go and go through all these 20 steps but instead get it done in two, so the watts have helped some of the trainings that you have done has helped even talking to from a sales process the customer to know "Hey this is what I'm embracing" so when they come in they don't come in with I'm going to run my network the same way but no no I'm going to run it differently has helped us immensely to make the transition >> Well guys, congratulations on a great successful product, big fan I love that thing, I think it's going to be the future there's a lot more head room there that's cause we're looking at automations the devnet zone we're in is showing massive growth. The appetite for automation the appetite for configuration and scale and managing the complexity is a sweet spot I think that you guys had a nice formally hear looking forward to it. Final question for these guys Ronnie and Prakash are going to both answer it. Say something about DNA center platform that people should pay attention to that they might not hear in the mainstream chatter that's important that they should maybe want to kick the tires or understand it further, an area that they should know about that they might not hear about or they should know about what's the most important feature. Share some, share some insight. >> So again just looking at a little bit into the future of Cisco data center platform, right now we're kind of talking of APIs, there's capability that's coming in the future that will also deal with work flows and the work flows will be built on something which is machine built so there will be a lot of analytics in fact in a data center not only does automation but also extends data analytics so a lot of cool stuff that'll come there and again we'll talk about it more as we get to the next Cisco live. >> Prakash anything? >> I'm going to go a little more ground level people tend to talk about simplicity, talk about how we can do things way differently with data center and people tend to forget that we have not forgotten the network engineer who has been managing the network. We have APIs for you to do the same things you've done all along, create articles create re-lance, do some of the basic networking stuff so that it's not about this just as simple we also have the more detailed breakdown of the API so that you can still continue to know the nuts and the bolts and other things as well as much as the simple stuff so it's the >> It's an empowering all personas in the network from network engineer low level getting down and dirty to large scale automations, whatever the use case is you got the empowerment. >> Yep that's basically what I would like to >> That's awesome, well congratulations Again big fan, DNA center takeover here in the Devnet zone I'm John Furrier with Stu Miniman Cube coverage day two of three days stay with us for more after this short break. (electronic music plays)

>> 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.