 Live from Orlando, Florida, it's theCUBE, covering Cisco Live 2018, brought to you by Cisco, NetApp, and theCUBE's ecosystem partners. Hello, welcome back, everyone. It's the live CUBE coverage here in Orlando, Florida for Cisco Live 2018. I'm John Furrier, my co-host, Stu Miniman, three days of wall-to-wall live coverage. We have Manny Whaley, Senior Director of Developer Experience, Cisco DevNet and Par Marat, who is the Senior Director of Community and Ecosystem for DevNet, and you're great to see you, CUBE alumni. Every single time we had theCUBE with DevNet team, Par, great to see you. Congratulations, first of all, thanks for coming on. Thank you, we're happy to be here. Congratulations, so really kind of a proud moment for you guys, and I want to give you some mad props on the fact that you guys have built a successful developer program, DevNet and DevNet Create for Cloud Native, over a half a million registered, engaged users of developers using it, not just people who come to the site, real developers. For an infrastructure enterprise company, that's a big deal. Congratulations. It is, thank you, thank you. We were just chatting this morning about the really early days of DevNet at Cisco Live and the first year of DevNet Create, and it's been great to see that community grow and see, early on we had this vision of bringing the application developers and the infrastructure engineers together and cross-pollinating those teams and having them learn about each other's fields and then build these programmable infrastructure enabled apps, and that's really, that synergy is happening within the community and it's great to see them exchanging ideas here at events like this. And so we love to talk about, you know, seminal moments, and obviously DevOps drove a lot of the cloud, and Chuck Robbins, your CEO, said, without networking, there'd be no cloud. True statement, absolutely. But Stu and I always talk about the role of a network engineer and that the power that they used to have in the enterprise, as I still do, used to be the top people running the network, mission critical, obviously security, but it's not about a retraining. It's about a path, and I think what you guys have done in success is you've shown a path where it's not about pivoting and being relevant and retraining to get a new job, it's been an extension of what they already know. And I think that's very refreshing and I think that's the real discovery. And we've been able to grow because I think in our foundational years, we really spent a lot of time providing the content and the skill training, and what Mandy likes to say is we met them where they are. So no question was too novice. Likewise, if they were a little more advanced, we could direct them and point them in that same direction. So those early years, where Mandy, we were just reminiscing about the first DevNet, Putting 101. Yes, exactly. She wrote it over the weekend and we rolled that whole event out, literally in three months. And what year was that? This is important. 2014, May of 2014. 2014, the seeds that we should do something. You guys have had certifications. We're looking at CCIEs. You go back to 1993 all the way now to 2018. So it's not like you guys are new to certification and training. It's just taking the IQ of network people and giving them some insight. So what happened in 2014? Take us through the, obviously, you bootstrapped it. Yes. What happened next? We did. Everyone's saying, whoa, we can't. We're staying below the stack here. We knew there was a lot of buzz around SDN and programmability and we both actually, I should even back up further. We were both on the DevNet team when the DevNet program was PowerPoints. So we weren't even there yet. When we were just planning what it even could be. Like the idea of Cisco having a developer program. And like Parv was saying, we knew SDN was coming. We knew network controllers were coming. We didn't know what they were going to be called. We didn't know what those APIs looked like. But we said, the network engineers are going to need to know how to make REST API calls. They're going to need to know how to operate in Python. And so we started this program building around that vision before the portfolio is where it is today. Like today, now we have APIs across the whole portfolio, data center, service provider, enterprise and then up and down from the devices all the way to controllers up to the analytics level. So the portfolios really filled out and we've been able to bring that community along with it, which has been great. I want to dig into the north, south, east, west and that whole kind of the cloud paradigm. But I got to ask you on a personal question relative to the definite success. Was there a moment where, actually the seminal was in 2014. Was there a moment where you're like, wow, this is working. And like, you know, pinch me moment. Or was it more of, we got to get more resources. This is not just the things flying. Well it's always that, it's always the challenge. When was the point where you said this is actually the best path, it's working, double down, what was that happening? I mean I think after we started teaching those very early coding classes, I got this like flood of email from people who attended them that said, I took this task, I automated it, it saved my team months of work. And like getting that flow of information back from the community was early signs to me from like the technical level of there's value, this is going to take off. And then I think we just saw that kind of grow and grow and grow, yeah. The other thing that I heard from a network engineer which really resonated with me was you were saying the network guy, or gal likes to be there and solve the problem and they're sort of at this deep level of control. And what I heard them say about the programmability skills was that that was another tool that they added to their sort of toolbox that let them be that person in the moment solving that problem and they could just solve it in a new way. So hearing the network engineers say that they've adopted programmability in that fashion, that let me know that that was going to work, I think. Yeah. All right, so let's get into some of the meat and potatoes because you guys had some really good announcements. We saw you have the code ecosystem that you announced at DevNet Create, which is your emerging cloud native worlds coming together. That's available now. Yes. So take a minute. It's fully released. So give us the update. Yes, so DevNet code exchange is developer.sysco.com slash code exchange. So you can go there, it's live. And the idea behind this was we wanted to make it easy for the community to contribute and also to discover code written by the community. So it's on GitHub. You can go and search on GitHub, but you get back a ton of hits if you go search Cisco on GitHub, which is great. But what we wanted to have was a curated list that you can filter by product, by language. I sometimes joke that it's like Zappos for sample code because you can go on and say, you know, I want black boots, you know, the two inch heel. You can say, I want code for DNA center or ACI and I want it in Python and then see all of the repositories submitted by the community. And then the community can also share their code. Say, I've been working on this project. I'm going to add it to code exchange so that other people can build off of it and find it. So it's really about this community contribution, which is a strategic initiative for DevNet for this year. Mandy, how does that tie into other networking initiatives happen in the industry? I think of Open Daylight, a lot of stuff happening in Dockercons this week, Kubernetes, and networking's a critical piece of all of these environments. Yeah, so some of the projects that you'll find in code exchange are things that relate. So we have like some really good open source community projects around Yang models and the tooling to help you deal with Yang models. So those might be in code exchange, but those are also part of the Open Daylight community and being worked in that. So because it is all open source, because it is freely shared and it's really just a way to improve discoverability, we can share easily back and forth between the community. So code and share is designed to really help people peer to peer, work together, and reuse code in the classic open source ethos. Exactly. Okay, so Par, you have something going on with ecosystem exchange. We do. Okay, so it sounds like code exchange, ecosystem partners, matchmaking service. What is it? It's kind of the next level up and what I think we have to understand is when we've got code exchange and ecosystem exchange under the umbrella of exchange, because within our 500, half a million community of developers where they work, what we've found is predominantly at SIs, at our vars, at our ISVs. So these are the builders. So code exchange will even help that persona because they can come and see what's already been built as there's something that can jumpstart my development. And if there's not, then they can work with each other, right? So if I am looking for a partner, a VAR in Australia to help me roll out my application, my navigation application, which needs to know and get data from the network, I can partner through this exchange because I can go in, see everyone, and be able to make that connection digitally versus organically. And this really started, you asked earlier, what was one of the pinnacle moments? Well, at these DevNet zones, what we found is that an ISV would partner and start talking to an SI or to a VAR, and they'd start doing business planning because what this is all about is driving those business outcomes for our customer base and we're finding more and more they're trying to work together. So you're enabling people to do some work together, but not trying to be a marketplace where you're actually charging or transaction. It's really kind of a matchmaking. This is all about discovery right now. Community-driven discovery around business. Yeah, it's interesting, I heard a story in the hallway about DevNet because I love to get the examples of, we love what you're doing by the way, but love to get the examples. Overheard a guy saying we were basically cratering a business, jumped into the DevNet program and turned it around because there was deals happening. So the organic nature of the community allowed for him to get his hands dirty and leverage it, but actually build business value. That's exactly right. That's a huge, at the end of the day, people love to play with COVID, they're building something for business purposes or open source projects. And that's what this is about. It's really transitioning from the, I'm going to build to now there's business value associated with it and that's spectacular. I think so much of my career, you talk to the poor network administrators, like, oh, I'm going to lock myself for a month and I'm going to do all this scripting and then three months later the business comes and asks for something and I need to go do it again because it's not repeatable. It's what we say is that the challenge has been that undifferentiated, heavy lifting that too many companies do. Well, that's exactly it. And the interesting thing, especially around intent-based networking, is that's opening up a whole new opportunity of innovation and services. And one of the things that is very much different with our ecosystem exchange is it's the whole portfolio. So we have SIs in there as well as ISVs and most, you know, marketplaces or catalogs really look at it in a siloed version. I have one example of kind of the two coming together that's really interesting. So, Meraki, which is the wireless network, has really great indoor location-based services you can get from the wifi. And then there's Ben ISVs who have built indoor wayfinding on top of it, really great applications. But those software companies don't necessarily know how to go install a Meraki network or sell a Meraki network to something like this, you know? And so it's been a great way to see how some of those wayfinding companies can get together with the people who actually go sell and install and admin Meraki networks and come together because they would have a hard time finding each other. And the example is actually rolled out here at Cisco Live. We've Cisco Live partnered with the ISV to embed a cloud-based service in their app, which is navigation. So, you can go into the Cisco Live app, tap on the session that you want to see. Map will come up that will navigate you from where you are here to get there. And this is, I think this is the second largest conference center in the United States. So, having that map is really important. We've all got the steps to prove that. Yeah, and that actually brings one of the questions I had was, is it typically some new thing? Is, you know, it's new wireless rollout, some SD-WAN discovery? Or is it core networking, or is it kind of across the board as to when people get involved? It's definitely both, it's definitely both. I mean, from the code exchange piece, like I've talked to a lot of customers this week who are saying, we've got our core networking teams, we want to move towards more automation. We're trying to figure out how to get started. And so, we give them all the resources to get started, like our video series and the now code exchange. And then I heard from some people here, they actually coded up some things and submitted it to code exchange while they were here because they had an idea for just a simple, like, quick automation piece that they needed and they were like, I bet somebody else needs it too. So, it was definitely that. I noticed you guys also have your Cisco team, I was talking to some of the folks there, patents are being filed. So, internally at Cisco, it's kind of a wind of change happening. It is, it is. It is exciting times. I mean, IOT cameras, I just saw a solution behind us here where you plug in Raspberry Pi hardware prototype to an AP, makes the camera a video, you know, looks at facial recognition, saves the metadata, never stores video. Right, right. So, this is kind of the new model. So, final question I want to ask you is, as you guys continue to build community, you're looking for feedback, the role of integrating is critical. You mentioned the Cisco example about going to market together. It used to be, hey, I'm an integrator of our solution, business planning, okay, and then, you got to go to the Cisco rep and then it's just located. More and more it's coming together. It is. How are you guys bridging that, those two worlds? How are you tying it together? What's the plan? So, what we're finding is a lot of those partners are also sort of morphing. So, they're not just one thing anymore. And so, what we're doing is we're working with them, enabling them on our platforms, providing solid APIs that they can leverage, transitioning or expanding the code, the skill sets of their workers, and then we're partnering them up with our business partners and with our ISVs and doing a lot of that matchmaking. And with ecosystem exchange, again, they'll now be able to take that to a digital format. So, we're seeing a whole wave of people have to take them there. So, you guys see it coming. You're on that wave. All right, real quick. I know we got it short on time, but I would, Mandy, if you could just talk about what Susie, we, your leader, talked about on stage on the keynote. She mentioned DNA Center. Can you just take a quick second? Yes. Describe what that is, what's why it's important and impact to the community. Yes. So, we're really excited about DNA Center platform. DNA Center is the controller, kind of at the heart of all of our new enterprise networking software. So, it sits on top of the devices and it exposes a whole library of APIs that let you do assurance, policy, get device information, would allow you to build kind of self-service ops models so you could give more power to your power users to get access to network resources on board new devices, things like that. So, sets of services. So, it's APIs, and then you can build the services on top. And part of that is also the assurance which Dave Guckler showed in his keynote which we're really excited about. So, in DevNet, we've been working to build all the resources around those APIs and we have many code samples and code exchange. We actually have a community contribution sprints going on right now that's called Code Intent with DevNet. And it's all around DNA Center. It's asking developers to take a business intent and turn it into code and close the loop with assurance and submit that back to DevNet. So, we're really excited about that. It's real business process improvement with code. Yeah. So, you're enabling that and slinging APIs around, having fun. Yes. Are you having fun? Definitely having fun. Yeah. Absolutely. We always have fun. It's great too. I can say, working with you guys up close, it's been fun to work with you. And congratulations. You guys have worked really hard and built a very successful growing ecosystem of developers and partners. Congratulations. Thank you. You guys have helped. I appreciate it. Thanks for supporting theCUBE. We appreciate it. This is theCUBE, the DevNet team. Back in the early days, 2014, when it started now, it's booming. One of the successful developer programs in the enterprise here. Cisco's really showing the path. So, all about the community and the ecosystems. theCUBE, of course, doing our share, broadcasting here live in Orlando at Cisco Live 2018. Stay with us for more live coverage after this short break.