>>From around the globe. It's the cube presenting, accelerating automation with dev net brought to you by Cisco, >>Everybody Jeffery here with the Q we're in our Palo Alto studio with ongoing coverage of Cisco dev net create we've been covering dev net create for a number of years. I think since the very first show and Susie, we and the team really built, uh, a practice built a company, built a lot of momentum around software in the Cisco ecosystem and getting devs really to start to build applications and drive kind of the whole software defined networking thing forward. And a big part of that is partners and working with partners and, and developing solutions and, you know, using brain power. That's outside of the four walls of Cisco. So we're excited to have, uh, our next guest, uh, a partner for someone is Brad Hoss. He is the engineering director for dev ops at Presidio, Brad. Great to see you. >>Hey Jeff, great to be here, >>Julie and joining him is Chuck Stickney. Chuck is the business development architect for Cisco dev net partners, and he has been driving a whole lot of partner activity for a very long period of time. Chuck, great to see you. >>Thanks Jeff. Great to be here and looking forward to this conversation. >>So let's, let's start with you Chuck, because I think, um, you know, you're leading this kind of partner effort and, and, you know, software defined, networking has been talked about for a long time and you know, it's really seems to be maturing and software defined everything right. Has been taking over, especially with, with virtualization and moving the flexibility and the customer program ability customability in software and Mo and taking some of that off the hardware. Talk about, you know, the programs that you guys are putting together and how important it is to have partners to kind of move this whole thing forward, versus just worrying about people that have Cisco badges. >>Yeah, Jeff, absolutely. So along this whole journey of dev net where we're, we're trying to leverage that customization and innovation built on top of our Cisco platforms, most of Cisco's business is transacted through partners. And what we hear from our customers and our partners is they want to, our customers want a way to be able to identify, does this partner have the capabilities and the skills necessary to help me go down this automation journey? I'm trying to do, do a new implementation. I want to automate that. How can I find a partner to, to get there? And then we have some of our partners that have been building these practices going along this step, in that journey with us for the last six years, they really want to say, Hey, how can I differentiate myself against my competitors and give an edge to my customers to show them that, yes, I have these capabilities. I've built a business practice. I have technology, I have technologists that really understand this capability and they have the double net certifications to prove it, help me be able to differentiate myself throughout our ecosystem. So that's really what our Danette partner specialization is all about. Right. >>It's great. And Brad, you're certainly one of those partners and I want to get your perspective because partners are oftentimes a little bit closer to the customer cause you've got your kind of own set of customers that you're building solutions and just reflect on, we know what happened, uh, back in March 15th, when basically everybody was told to go home and you can't go to work. So, you know, there's all the memes and social media about who, you know, who pushed forward your digital transformation, the CEO, the CMO, or COVID. And we all know what the answer is, whatever you can share some information as to what happened then, and really for your business and your customers, and then reflect now we're six months into it, six months plus, and, and you know, this new normal is going to continue for a while. How's the customer attitudes kind of changed now that they're kind of buckled down past the light switch moment and really we need to put in place some foundation to carry forward for a very long time, potentially. >>Yeah, it's really quite interesting actually, you know, when code first hit, we got a lot of requests to help with automation of provisioning, our customers and the whole digital transformation got really put on hold for a little bit there. And I'd say it became more of, of the workplace transformation. So we were quickly, uh, you know, migrating customers to, you know, new typologies where instead of the, the, you know, users sitting in those offices, they were sitting at home and we had to get them connected rapidly in, uh, we, we didn't have a lot of success there in those beginning months with, you know, using automation and programmability, um, building, you know, provisioning portals for our customers to get up and running really fast. Um, and that, that was what it looked like in those early days. And then over time, I'd say that the asks from our customers has started to transition a little bit. >>You know, now they're asking, you know, how can I take advantage of the technology to, you know, look at my offices in a different way, you know, for example, you know, how many people are coming in and out of those locations, you know, what's the usage of my conference rooms. Um, are there, uh, are there, um, situations where I can use that information? Like how many people are in the building in a, at a certain point in time and make real estate decisions on that, you know, like, do I even need this office anymore? So, so the conversations have really changed in, in, in ways that you couldn't have imagined before March. Right. >>Right. And I wonder with, with you Chuck, in terms of the Cisco point of view, I mean, the network is amazing. It had had, COVID struck five years ago, 10 years ago, 15 years ago, you know, clearly there's a lot of industries that are suffering badly entertainment, um, restaurant, business, transportation, they, you know, hospitality, but for those of us in kind of the information industry, the switch was pretty easy. Um, you know, and, and the network enables the whole thing. And so I wonder if, you know, kind of from your perspective as, as you know, the importance of the network, the importance of security and the ability now to move to this new normal very quickly from a networking perspective. And then on top of that, having, you know, dev net with, with the software defined on top, you guys were pretty much in a good space as good as space as you could be given this new challenge thrown at you. >>Yeah, Jeff, we completely agree with that. Uh, Cisco has always pushed the idea that the network is transformational. The network is the foundation, and as our customers have really adopted that message, it is enabled that idea for the knowledge workers to be able to continue on. So, uh, for myself, I've, I've worked for home the entire time I've been at Cisco. So the last 13 years, this is, you know, the, the change to the normalcy is I never get on a plane anymore, but my day to day functions are still the same. And it's built because of the capabilities that we have with the network. I think the transition that we've seen in the industry, as far as kind of moving to that application type of economy, as we go to microservices, as we go to a higher dependency upon cloud, those things have really enabled the world really to be able to better respond to this, to this COVID situation. And I think it's helped to, to justify the investments that our customers have made, as well as what our partners have been, being able to do to deliver on that multicloud capability, to take those applications, get them closer to the end user instead of sitting in a common data center and then making it more applicable to, to users wherever they may be, not just inside of that traditional four walls. >>Right. Right. It's interesting that Brad, you, you made a comment on another interview. I was watching getting ready for this one in terms of, uh, applications now being first class citizens was, was what you said. And it's kind of interesting coming from an infrastructure point of view, where before it was, you know, what do I have and what can I build on it now, I really it's the infrastructure that responds back to the application. And even though you guys are both in the business of, of networking and infrastructure, it's still this recognition that apps first is the way to go, because that gives people a competitive advantage, that it gives them the ability to react in the marketplace and to innovate and move faster. So, you know, it's, it's a really interesting twist to be able to support an application first, by having a software defined in a more programmable infrastructure stack. >>Yeah, no doubt. And, you know, I think that the whole push to cloud was really interesting in the early days, it was like, Hey, we're going to change our applications to be cloud first. You know? And then I think the terminology changed over time, um, to more cloud native. So when we, when we look at what cloud has done over the past five years with customers moving, you know, their, their assets into the cloud in the early days that we were all looking at it just like another data center, but what it's really become is place to host >>Your applications. So when we talk about cloud migrations with our customers now, we're, we're no longer talking about the assets per se. We're talking about the applications and what, what do those applications look like? And even what defines an application right now, especially with the whole move to cloud native and microservices in the automation that helps make that all happen with infrastructure as code. You're now able to bundle the infrastructure with those applications together as a single unit. So when you define that application, as infrastructure, as code the application in the definition of what those software assets for the infrastructure are, all are wrapped together and you've got change control, version control, um, and it's all automated, you know, it's, it's a beautiful thing. And I think it's something that we've all kind of hoped would happen. You know, when I look back at the early definitions of software defined networking, I think everybody was trying to figure it out and they didn't really fully understand what that meant now that we can actually define what that network infrastructure could look like as it's, as it's wrapped around that application in a code template, maybe that's Terraform or Ansible, whatever that might be, whatever method or tool that you're using to, to bring it all together. >>It's, it's, you know, it's really interesting now, I think, I think we've gotten to the point where it's starting to make a lot more sense than, you know, those early days of SDN, uh we're out, you know, it was, was it a controller or is it the new version of SNMP? You know, now it makes sense it's actually something tangible. >>Right, right. But still check, as you said, right. There's still a lot of API APIs and there's still a lot of component pieces to these applications that are all run off the network that all have to fit, uh, that have to fit together. You know, we cover PagerDuty summit and you know, their whole thing is trying to find out where the, where the problems are within the very few microseconds that you have before the customer abandoned their shopping cart or whatever the particular application. So again, the network infrastructure and the program ability super important. But I wonder if you could speak to the automation because there's just too much stuff going on for individual people to keep track of, and they shouldn't be keeping track of it because they need to be focusing on the important stuff, not this increasing amount of bandwidth and traffic going through the network. >>Yeah, absolutely. Jeff said the bandwidth that's necessary in order to support everybody working from home to support this video conference. I mean, we, we used to do this sitting face to face. Now we're doing this over the internet. The amount of people necessary to, to be able to facilitate that type of traffic. If we're doing it the way we did 10 years ago, we would not scale it's automation. That makes that possible. That allows us to look up >>The ability to do that automatic provisional provisioning. Now that we're in microservices now that everything is cloud native, we have the ability to better, to better adjust to and adapt to changes that happen with the infrastructure below hand. So if something goes wrong, we can very quickly spend something up to take that load off where, you know, traditionally it was open up a ticket. Let me get someone in there, let me fix it. Now it's instantaneously identify the solution, go to my playbook, figure out exactly what solution I need to deploy and put that out there. And the network engineering team, the infrastructure engineering team, they just simply need to get notified that this happened. And as long as there's traceability, in a point that Brad made, as far as you being able to go through here doing the automation of the documentation side of it. >>I know when I was a network engineer, one of the last things we ever did was documentation. But now that we have the API is from the infrastructure. And then the ability to tie that into other systems like an IP address management or a change control, or a trouble ticketing system, that whole idea of I made an infrastructure change. And now I can automatically do that documentation update and record. I know who did it. I know when they did it and I know what they did, and I know what the test results were even five years ago, that was fantasy land. Now, today that's just the new normal, that's just how we all operate. >>Right. Right, right. So I want to get your take on the other >>Hybrid cloud, multi cloud >>Public cloud. You know, as, as I think you said Brad, when public cloud first came out, there was kind of this, this rush into, we're going to throw everything in there then for, for, for different reasons. People decided maybe that's not the best, the best solution, but really it's horses for courses. Right. And, and I think it was pretty interesting that, that you guys are all supporting the customers that are trying to figure out where they're going to put their workloads. And Oh, by the way, that might not be a static place, right. It might be moving around based on, you know, maybe I do my initial dev and, and, and Amazon. And then when I go into production, maybe I want to move it into my data center. And then maybe I'm having a big promotion or something I want to flex capability. So from, from your perspective and helping customers work through this, cause still, there's a lot of opinions about what is multicloud, what is hybrid cloud and you know, it's horses for courses. How are you helping people navigate that? And what does having programmable infrastructure enable you to do for helping customers kind of sort through, you know, everybody talks about their journey. I think there's still kind of bumbling down, bumbling down paths, trying to find new things, what works, what doesn't work. And I think it's still really early days and trying to mesh all this stuff together. Yeah, >>Yeah. No doubt. It is still early days. And you know, I, I, I go back to it being application centric because you know, being able to understand that application, when you move to the cloud, it may not look like what it used to look like when you, when you move it over there and you may be breaking parts off of it. Some of them might be running on a platform as a service while other pieces of it are running as infrastructure as a service. And some of it might still be in your data center. Those >>Are becoming much more complex than they used to be because we're breaking them apart into different services. Those services could live all over the place. So with automation, we really gain the power of being able to combine those things. As I mentioned earlier, those resources, wherever they are, can be defined in that infrastructure as code and automation. But you know, the side from provisioning, I think we focus a lot about provisioning. When we talk about automation, we also have these amazing capabilities on, on the side of operations too. Like we've got streaming telemetry in the ability to gain insights into what's going on in ways that we didn't have before, or at least in the, in, you know, in the early days of monitoring software, right? You knew exactly what that device was, where it was. It probably had a friendly name, like maybe it was, uh, something from the Hobbit right now. >>You've got things coming up and spinning and spinning up and spinning down, moving all over the place. And that thing you used to know what that was. Now, you have to quickly figure out where it went. So the observability factor is a huge thing that I think everybody should be paying attention to attention, to moving forward with regards to when you're moving things to the cloud or even to other data centers or, you know, in your premise, I'm breaking that into microservices. You really need to understand what's going on in the, you know, programmability and API APIs and, you know, yang models are tied into streaming telemetry. Now there's just so many great things coming out of this, you know, and it's all like a data structure that, that people who are going down this path and the dev net path, they're learning these data structures and being able to rationalize and make sense of them. Once you understand that, then all of these things come together, whether it's cloud or a router or switch, um, Amazon, you know, it doesn't matter. You're, you're all speaking a common language, which is that data structure. >>That's great. Check. I want to shift gears a little bit. Cause there was something that you said in another interview when I was getting ready for this one about, about Deb, not really opening up a whole different class of partners for Cisco, um, as, as really more of a software, a software lead versus kind of the traditional networking lead. I wonder if you can put a little more color on that. Um, because clearly as you said, partners are super important. It's your primary go to market and, and Presidios, I'm sure the best partner that you have in the whole world that's and you know, you said there's some, there's some non traditional people that would not ever be a Cisco partner that suddenly you guys are playing with because of really the software lead. >>Yeah. Jeff that's exactly right. So as we've been >>Talking to folks with dev nets and whether it'd be at one of the Cisco live events in the dev net zone or at the prior dev net create events, we'll have, we'll have people come up to us who Cisco today views us as a customer because they're not in our partner ecosystem. They want to be able to deliver these capabilities to our customers, but they have no interest in being in the resell market. This, what we're doing with the dev net specialization gives us the ability to bring those partners into the ecosystem, share them with our extremely large dev net community so they can get access to those, to those potential customers. But also it allows us to do partner to partner type of integration. So Brad and Presidio, they built a fantastic networking. They always have the fantastic networking business, but they built this fantastic automation business that's there, but they may come into a con into a scenario where it's working with a vertical or working with the technology piece, that they may not have an automation practice for. We can leverage some of these software specific partners to come in there and do a joint, go to markets where, so they can go where that traditional channel partner can leverage their deep Cisco knowledge in those customer relationships that they have and bring in that software partner almost as a subcontractor to help them deliver that additional business value. On top of that traditional stack, that brings us to this business outcomes of the customers are looking for and a much faster fashion and a much more collaborative fashion. >>That's terrific. Well, again, it's a, it's, it's unfortunate that we can't be in person. I mean, the, the Cisco DevNet shows, you know, they're still small, they're still intimate. There's still a lot of, uh, information sharing and you know, great to see you. And like I said, we've been at the computers museum, I think the last couple of years and in, in San Francisco. So I look forward to a time that we can actually be together. I hope maybe, maybe for next year's event, but, uh, thank you very much for stopping by and sharing the information. Really appreciate it. Happy to be here. All right. Thanks a lot. That's Brad and Chuck. I'm Jeff. You're watching Cisco dev net live coverage on the cube. Thanks for watching. We'll see you next time.