>>Hi, everyone. Welcome to ASML day. My name is Yasmin Joffey. I'm the director of systems engineering for ASML at HPE. Today. We're here and joined by my colleague, Don wake, who is a technical marketing engineer who will talk to us about the date and the life of an it administrator through the lens of ASML container platform. We'll be answering your questions real time. So if you have any questions, please feel free to put your questions in the chat, and we should have some time at the end for some live Q and a. Don wants to go ahead and kick us off. >>All right. Thanks a lot, Yasir. Yeah, my name is Don wake. I'm the tech marketing guy and welcome to asthma all day, day in the life of an it admin and happy St. Patrick's day. At the same time, I hope you're wearing green virtual pinch. If you're not wearing green, don't have to look that up if you don't know what I'm scouting. So we're just going to go through some quick things. Talk about discussion of modern business. It needs to kind of set the stage and go right into a demo. Um, so what is the need here that we're trying to fulfill with, uh, ASML container platform? It's, it's all rooted in analytics. Um, modern businesses are driven by data. Um, they are also application centric and the separation of applications and data has never been more important or, or the relationship between the two applications are very data hungry. >>These days, they consume data in all new ways. The applications themselves are, are virtualized, containerized, and distributed everywhere, and optimizing every decision and every application is, is become a huge problem to tackle for every enterprise. Um, so we look at, um, for example, data science, um, as one big use case here, um, and it's, it's really a team sport and I'm today wearing the hat of perhaps, you know, operations team, maybe software engineer, guy working on, you know, continuous integration, continuous development integration with source control, and I'm supporting these data scientists, data analysts. And I also have some resource control. I can decide whether or not the data science team gets a, a particular cluster of compute and storage so that they can do their work. So this is the solution that I've been given as an it admin, and that is the ASML container platform. >>And just walking through this real quick, at the top, I'm trying to, as wherever possible, not get involved in these guys' lives. So the data engineers, scientists, app developers, dev ops guys, they all have particular needs and they can access their resources and spin up clusters, or just do work with the Jupiter notebook or run spark or Kafka or any of the, you know, popular analytics platforms by just getting in points that we can provide to them web URLs and their self service. But in the backend, I can then as the it guy makes sure the Kubernetes clusters are up and running, I can assign particular access to particular roles. I can make sure the data's well protected and I can connect them. I can import clusters from public clouds. I can, uh, you know, put my like clusters on premise if I want to. >>And I can do all this through this centralized control plane. So today I'm just going to show you I'm supporting some data scientists. So one of our very own guys is actually doing a demo right now as well, called the a day in the life of the data scientist. And he's on the opposite side, not caring about all the stuff I'm doing in the backend and he's training models and registering the models and working with data, uh, inside his, you know, Jupiter notebook, running inferences, running postman scripts. And so I'm in the background here, making sure that he's got access to his cluster storage protected, make sure it's, um, you know, his training models are up, he's got service endpoints, connecting him to, um, you know, his source control and making sure he's got access to all that stuff. So he's got like a taxi ride prediction model that he's working on and he has a Jupiter notebook and models. So why don't we, um, get hands on and I'll just jump right over it. >>It was no container platform. So this is a web UI. So this is the interface into the container platform. Our centralized control plane, I'm using my active directory credentials to log in here. >>And >>When I log in, I've also been assigned a particular role, uh, with regard to how much of the resources I can access. Now, in my case, I'm a site admin you can see right up here in the upper right hand, I'm a site admin and I have access to lots and lots of resources. And the one I'm going to be focusing on today is a Kubernetes cluster. Um, so I have a cluster I can go in here and let's say, um, we have a new data scientists come on board one. I can give him his own resources so he can do whatever he wants, use some GPU's and not affect other clusters. Um, so we have all these other clusters already created here. You can see here that, um, this is a very busy, um, you know, production system. They've got some dev clusters over here. >>I see here, we have a production cluster. So he needs to produce something for data scientists to use. It has to be well protected and, and not be treated like a development resource. So under his production cluster, I decided to create a new Kubernetes cluster. And literally I just push a button, create Kubernetes cluster once I've done that. And I'll just show you some of the screens and this is a live environment. So this is, I could actually do it all my hosts are used up right now, but I wouldn't be able to go in here and give it a name, just select, um, some hosts to use as the primary master controller and some workers answer a few more questions. And then once that's done, I have now created a special, a whole nother Kubernetes cluster, um, that I could also create tenants from. >>So tenants are really Kubernetes. Uh namespaces so in addition to taking hosts and Kubernetes clusters, I can also go to that, uh, to existing clusters and now carve out a namespace from that. So I look at some of the clusters that were already created and, um, let's see, we've got, um, we've got this year is an example of a tenant that I could have created from that production cluster. And to do that here in the namespace, I just hit create and similar to how you create a cluster. You can now carve down from a given cluster and we'll say the production cluster and give it a name and a description. I can even tell it, I want this specific one to be an AI ML project, um, which really is our ML ops license. So at the end of the day, I can say, okay, I'm going to create an ML ops tenant from that cluster that I created. >>And so I've already created it here for this demo. And I'm going to just go into that Kubernetes namespace now that we also call it tenant. I mean, it's like, multitenancy the name essentially means we're carving out resources so that somebody can be isolated from another environment. First thing I typically do. Um, and at this point I could also give access to this tenant and only this tenant to my data scientist. So the first thing I typically do is I go in here and you can actually assign users right here. So right now it's just me. But if I want it to, for example, give this, um, to Terry, I could go in here and find another user and assign him from this lead, from this list, as long as he's got the proper credentials here. So you can see here, all these other users have active directory credentials, and they, uh, when we created the cluster itself, we also made sure it integrated with our active directory, so that only authorized users can get in there. >>Let's say the first thing I want to do is make sure when I do Jupiter notebook work, or when Terry does, I'm going to connect him up straight up to the get hub repository. So he gives me a link to get hub and says, Hey man, this is all of my cluster work that I've been doing. I've got my source control there. My scripts, my Python notebooks, my Jupiter notebooks. So when I create that, I simply give him, you know, he gives me his, I create a configuration. I say, okay, here's a, here's a get repo. Here's the link to it. I can use a token, here's his username. And I can now put in that token. So this is actually a private repo and using a token, you know, standard get interface. And then the cool thing after that, you can go in here and actually copy the authorization secret. >>And this gets into the Kubernetes world. Um, you know, if you want to make sure you have secure integration with things like your source control or perhaps your active directory, that's all maintained in secrets. So you can take that secret. And when I then create his notebook, I can put that secret right in here in this, uh, launch Yammel. And I say, Hey, connect this Jupiter notebook up with this secret so he can log in. And when I've launched this Jupiter notebook cluster, this is actually now, uh, within my, my, uh, Kubernetes tenant. It is now really a pod. And if I want to, I can go right into a terminal for that, uh, Kubernetes tenant and say, coop CTL, these are standard, you know, CNCF certified Kubernetes get pods. And when I do this, it'll tell me all of the active pods and within those positive containers that I'm running. >>So I'm running quite a few pods and containers here in this, uh, artificial intelligence machine learning, um, tenant. So that's kind of cool. Also, if I wanted to, I could go straight and I can download the config for Kubernetes, uh, control. Uh well, and then I can do something like this, where on my own system where I'm more comfortable, perhaps coop CTL get pods. So this is running on my laptop and I just had to do a coop CTL refresh and give the IP address and authorization, um, information in order to connect from my laptop to that end point. So from a CIC D perspective from, you know, an it admin guides, he usually wants to use tools right on his, uh, desktop. So here am I back in my web browser, I'm also here on the dashboard of this, uh, Kubernetes, um, tenant, and I can see how it's doing. >>It looks like it's kind of busy here. I can focus specifically on a pod if I want to. I happen to know this pod is my Jupiter notebook pod. So aren't, I show how, you know, I could enable my data scientists by just giving him the, uh, URL or what we call a notebook service end points or notebook end point. And just by clicking on this URL or copying it, copying, you know, it's a link, uh, and then emailing it to them and say, okay, here's your, uh, you know, here's your duper notebook. And I say, Hey, just log in with your credentials. I've already logged in. Um, and so then he's got his Jupiter notebook here and you can see that he's connected to his GitHub repo directly. He's got all of the files that he needs to run his data science project and within here, and this is really in the data science realm, data scientists realm. >>He can see that he can have access to centralized storage and he can copy the files from his GitHub repo to that centralized storage. And, you know, these, these commands, um, are kind of cool. They're a little Jupiter magic commands, and we've got some of our own that showed that attachment to the cluster. Um, but you can see here if you run these commands, they're actually looking at the shared project repository managed by the container platform. So, you know, just to show you that again, I'll go back to the container platform. And in fact, the data scientist, uh, could do the same thing. Attitude put a notebook back to platform. So here's this project repository. So this is other big point. So now putting on my storage admin hat, you know, I've got this shared, um, storage, um, volume that is managed for me by the ESMO data fabric. >>Um, in, in here, you can see that the data scientist, um, from his get repo is able to through Jupiter notebook directly, uh, copy his code. He was able to run as Jupiter notebook and create this XG boost, uh, model. So this file can then be registered in this AIML tenant. So he can go in here and register his model. So this is, you know, this is really where the data scientist guy can self-service kick off his notebooks, even get a deployment end point so that he can then inference his cluster. So here again, another URL that you could then take this and put it into like a postman rest URL and get answers. Um, but let's say he wants to, um, he's been doing all this work and I want to make sure that his, uh, data's protected, uh, how about creating a mirror. >>So if I want to create a mirror of that data, now I go back to this other, uh, and this is the, the, uh, data fabric embedded in a very special cluster called the Picasso cluster. And it's a version of the ASML data fabric that allows you to launch what was formerly called Matt bar as a Kubernetes cluster. And when you create this special cluster, every other cluster that you create is automatically, uh, gets things like that. Tenant storage. I showed you to create a shared workspace, and it's automatically managed by this, uh, data fabric. Uh, and you're even given an end point to go into the data fabric and then use all of the awesome features of ASML data fabric. So here I can just log in here. And now I'm at the, uh, data fabric, web UI to do some data protection and mirroring. >>So >>Let's go over here. Let's say I want to, uh, create a mirror of that tenant. So I forgot to note what the name of my tenant was. I'm going to go back to my tenant, the name of the volume that I'm playing with here. So in my AIML tenant, I'm going to go to my source, control my project repository that I want to protect. And I see that the ESMO data fabric has created 10 and 30 as a volume. So I'll go back to my, um, data fabric here, and I'm going to look for 10 and 30. And if I want to, I can go into tenant 30, >>Okay. >>Down here, I can look at the usage. I can look at all of the, you know, I've used very little of the, uh, allocated storage that I want, but let's, uh, you know what, let's go ahead and create a volume to mirror that one. So very simple web UI that has said create volume. I go in here and I say, I want to do a, a tenant 30 mirror. And I say, mirror the mirror volume. Um, I want to use my Picasso cluster. I want to use tenant 30. So now that's actually looking up in the data fabric, um, database there's 10 and 30 K. So it knows exactly which one I want to use. I can go in here and I can say, you know, ext HCP, tenant, 30 mirror, you know, I can give it whatever name I want and this path here. >>And that's a whole nother, uh, demo is this could be in Tokyo. This could be mirrored to all kinds of places all over the world, because this is truly a global name, split namespace, which is a huge differentiator for us in this case, I'm creating a local mirror and that can go down here and, um, I can add, uh, audit and encryptions. I can do, um, access control. I can, you know, change permissions, you know, so full service, um, interactivity here. And of course this is using the web UI, but there's also rest API interfaces as well. So that is pretty much the, the brunt of what I wanted to show you in the demo. Um, so we got hands on and I'm just going to throw this up real quick and then come back to Yasser. See if he's got any questions he has received from anybody watching, if you have any new questions. >>Yeah. We've got a few questions. Um, we can, uh, just take some time to go, hopefully answer a few. Um, so it, it does look like you can integrate or incorporate your existing get hub, uh, to be able to, um, extract, uh, shared code or repositories. Correct? >>Yeah. So we have that built in and can either be, um, get hub or bit bucket it's, you know, pretty standard interface. So just like you can go into any given, get hub and do a clone of a, of a repo, pull it into your local environment. We integrated that directly into the gooey so that you can, uh, say to your, um, AIML tenant, uh, to your Jupiter notebook. You know, here's, here's my GitHub repo. When you open up my notebook, just connect me straight up. So it saves you some, some steps there because Jupiter notebook is designed to be integrated with get hub. So we have get hub integrated in as well or bit bucket. Right. >>Um, another question around the file system, um, has the map, our file system that was carried over, been modified in any way to run on top of Kubernetes. >>So yeah, I would say that the map, our file system data fabric, what I showed here is the Kubernetes version of it. So it gives you a lot of the same features, but if you need, um, perhaps run it on bare metal, maybe you have performance, um, concerns, um, you know, you can, uh, you can also deploy it as a separate bare metal instance of data fabric, but this is just one way that you can, uh, use it integrated directly into Kubernetes depends really the needs of, of the, uh, the user and that a fabric has a lot of different capabilities, but this is, um, it has a lot of the core file system capabilities where you can do snapshots and mirrors, and it it's of course, striped across multiple, um, multiple disks and nodes. And, uh, you know, Matt BARR data fabric has been around for years. It's, uh, and it's designed for integration with these, uh, analytic type workloads. >>Great. Um, you showed us how you can manage, um, Kubernetes clusters through the ASML container platform you buy. Um, but the question is, can you, uh, control who accesses, which tenant, I guess, namespace that you created, um, and also can you restrict or, uh, inject resource limitations for each individual namespace through the UI? >>Oh yeah. So that's, that's a great question. Yes. To both of those. So, um, as a site admin, I had lots of authority to create clusters, to go into any cluster I wanted, but typically for like the data scientist example I used, I would give him, I would create a user for him. And there's a couple of ways you can create users. Um, and it's all role-based access control. So I could create a local user and have container platform authenticate him, or I can say integrate directly with, uh, active directory or LDAP, and then even including which groups he has access to. And then in the user interface for the site admin, I could say he gets access to this tenant and only this tenant. Um, another thing you asked about is his limitations. So when you create the tenant to prevent that noisy neighbor problem, you can, um, go in and create quotas. >>So I didn't show the process of actually creating a Quentin, a tenant, but integral to that, um, flow is okay, I've defined which cluster I want to use. I defined how much memory I want to use. So there's a quota right there. You could say, Hey, how many CPU's am I taking from this pool? And that's one of the cool things about the platform is that it abstracts all that away. You don't have to really know exactly which host, um, you know, you can create the cluster and select specific hosts, but once you've created the cluster, it's not just a big pool of resources. So you can say Bob, over here, um, he's only going to get 50 of the a hundred CPU's available and he's only going to get X amount of gigabytes of memory. And he's only going to get this much storage that he can consume. So you can then safely hand off something and know they're not going to take all the resources, especially the GPU's where those will be expensive. And you want to make sure that one person doesn't hog all the resources. And so that absolutely quotas are built in there. >>Fantastic. Well, we, I think we are out of time. Um, we have, uh, a list of other questions that we will absolutely reach out and, um, get all your questions answered, uh, for those of you who ask questions in the chat. Um, Don, thank you very much. Thanks everyone else for joining Don, will this recording be made available for those who couldn't make it today? >>I believe so. Honestly, I'm not sure what the process is, but, um, yeah, it's being recorded so they must've done that for a reason. >>Fantastic. Well, Don, thank you very much for your time and thank everyone else for joining. Thank you.

>> Announcer: Live from San Francisco, it's The Cube. Covering DevNet Create 2017. Brought to you by Cisco. >> Hey, welcome back, everyone. We're live in San Francisco for Cisco System's Inaugural DevNet Create Event. Which is an extension of their DevNet Developer Program. Which is the Cisco, you know, core developer program. Now, going out to the community to create, kind of, ingratiate into the DevOps developer world, connecting IOT and infrastructure together. This is The Cube's exclusive coverage for two days. Our next guest is Todd Nightingale, senior vice president and general manager of Cisco. Welcome to The Cube, I'm John Furrier. My co-host Peter Burris, welcome to The Cube. >> Thanks. >> Tell us about your group first. Just explain your division, what you guys do and why is it relevant to DevNet Create? I mean, you guys already got a massive developer program that's kicked off and growth within Cisco. Why DevNet Create? Why ingratiate out into the community and connect with these new developers? >> Sure, sure yeah. The Meraki business, it's cloud-managed infrastructure. We make wireless, switching, routing. And now phones and cameras and mobile device management. You know what we've realized is as simple to manage, simple to monitor, that our solution is, a lot of our customers, they want to do more. They want to expand and build custom applications. They want to leverage social logins. And do all kinds of different analytics on top of the infrastructure. The infrastructure is starting to be a part of a greater technology you know, digitization of their business, or their school, or their government. And really I think the lesson that we've learned over the last couple years is the key is to open up the platform. Is to have some faith in the community. Open up the platform and do your best to recruit, you know, best in class development teams from around the world. And once people can get more from your platform than others than they're going to flock to you over time. We're lucky, right, as a cloud managed solution, we've got all of our devices already being managed and monitored from the cloud. So for developers, it's very easy to develop on cloud APIs. >> So, they don't need to come in and be a total network guru. They just come in and leverage infrastructure as code for a gameable infrastructure, is that right? >> Exactly, yeah, rest APIs in the cloud. Just like you might integrate to a Facebook API or a Google API. You integrate to a Meraki API. And you're able to control the infrastructure, get analytics from the infrastructure, understand your locations better, all of that stuff. >> Peter and I always talk on The Cube about a couple concepts, but two are relevant. For this one, I'll give you a reaction to. One is internet scale now is going to a whole nother dimension. Cisco dominating with scale at the router level within internet one. But now, with internet and things, he brings up this concept of this known technology but unknown processing development. You mentioned new devices connecting. This is, like, a new connection point that needs to be managed dynamically. You don't know when they're going to come on and off. So, that's kind of cool. I'm going to get your reaction to that. Is that how you guys see the world? Because that really is IOT. New devices are connected to the network, they need a connection, they need power, and they need to be provisioned, managed, and allocated. They're throwing off data. This is a developer dream but also could be a nightmare. >> Yeah, look, I think that a lot of the story of networking has been this concept of, like, building a network, configuring it up just right, and then when it's perfect, you don't touch it. You're afraid you might break something. The concept of fat-fingering is so common, right? And so these networks are incredibly powerful but brittle. And that just can't be the way anymore. It has to be simple enough that people can feel that their network is nimble and changeable and can be configured and managed and changed over time to react to this stuff. I think the technology is getting better when it comes to simple and automated provisioning of IOT devices. We're tracking very carefully a technology called mud that allows for these devices to provision with a policy set by the manufacturer, and all that stuff. The real story is the networks were deploying today will have to be nimble. And they'll have to be upgradable from the cloud and be able to get better over time and make it easier and easier for people who have maybe a thousand users on their network today, they're going to have a hundred thousand devices on their network in five years. And they have to be ready for that. And be ready to continue to evolve over time. >> So, one of the things, that our researchers, we've talked to a lot of CIOs, is that they're moving to an orientation that's focused on elasticity, which might be no workload at any scale to what we're calling, plasticity. Which has very, very specific meaning, at least, in the physics sense. Not only are you able to scale up and down, but you're also able to reconfigure very, very rapidly. So, things will plop into a new shape that will sustain itself. And I want to know what you think about this concept. Not just elasticity, but plasticity. The ability for the infrastructure to reconfigure itself in ways that make sense and sustain that shape as the business evolves. >> Yeah, I think, look on the compute side, that's very real, right? When you think about load on different servers, with applications running across different clouds and data centers. This stuff has to be expandable and also, expandable in a controlled way, not just, you know, spinning up thousands and thousands of servers. And I think this concept of plasticity gets to that. It has to scale but in a controlled concept. When it comes to the infrastructure, the bigger deal is, the infrastructure is always optimizing whatever networking resources you have. There's only so much ban with coming to your site or to and from you cloud and all that stuff. And when the load starts to spike, and really explode over time, before you have the ability to find more ban with another service provider. What the infrastructure has to do is it has to automatically optimize your most important apps, you more important applications. Prioritize that through your network and optimize the rest to do its best in whatever limited resource it has. Infrastructure and network infrastructure, I think of this more of like resource optimization. And those algorithms having to be nimble. And to be honest, really dynamic, as the load spikes in different ways, over different times. >> I think it's a great point. But let me push you on this. But don't we also have to remember the patterns associated with that? So we can anticipate the infrastructure, can anticipate some of these spikes, time of month, time of day. In response to particular other business events. So, the infrastructure itself has to then, have a muscle memory associated with some of these things. So, that it can, again, kind of, constantly reconfigured itself to support what the business events that are becoming more obvious overall. So that we don't have to reconfigure them ourselves. Does that make sense to you? >> Yeah, I think, you know, we talk about this, sort of, next generation of network intelligence. And really using some type of machine learning to predict these type of events. To me, it's not just about, you know, automatically reconfiguring the infrastructure. But it's also about making the next recommendation about hey, the way your trends are going, you're really going to need, x, y, z change in the physical network in two months, in six months, in nine months. Predicting what will be the next shoe to drop and how IT managers will have to expand their network capacity in what ways. You know, I think that's really this concept of networking intelligence. It's a serious problem. I mean, the machine learning to understand these patterns and to be able to see through a lot of noise and really see what's happening is interesting. I think what app dynamics does for the application space, in, like, large day centers, understanding which code is being used more often and where your load really is happening. We're going to start to see some of those same, like, deep learning data analytics applications in networking. And I think it's exciting, I agree. It's an exciting space. >> Todd, I want to get your thoughts on something because we're before we came on camera about your background at MIT and Meroki, when it's got a start on the roots. You guys were hackers, okay? You were freedom fighters for the internet band. Which, by the way, we still have broadband starvation in this country, in my opinion. But I got to give you guys props for that. So, you got kind of a hacker mentality. But you talk about your journey, about how you group is, kind of, bringing in some group core IP. You're also, kind of, a global system integrator within Cisco, among the core IP. That's more important now than ever, as app dynamics collides with the Cisco infrastructure DNA. Can you share some insight on what it's like internally as Cisco? Because this is the classic, you know, decade and a half long argument within Cisco of moving up the stack. I mean, I've talked to many SBPs at Cisco, "We got to move up the stack." And, "No, we're good down here." You guys are moving up the stack, you're on of the hackers in there. I mean, technically, maybe not a hacker now. But I mean, mentality wise, you're looking at it differently. What's the different view? Share some color. >> It's been awhile since checked in any code. Yeah, look, I'd say there's a really great reality to inquire by Cisco. If you're in networking. And we focus a lot on adding value up the stack, putting things into the cloud platform, not just into the device and all that stuff. But if you're at Cisco, Cisco is holding on the richest infrastructure, IT infrastructure, intellectual property portfolio in the world. Almost indisputably, right? And as soon as you're acquired by Cisco, you get access to this immediately. We have, through different acquisitions, been able to leverage like, source fire amp and directory of modules, networking components from around Cisco. You know, since part of Cisco, we've been able to build stackable switching and aggregation, fiber switching, all this stuff. Deep, deep networking IP from all around Cisco. And like, I keep waiting for the bill to arrive. And it never has. >> It's your like Picasso, you got this canvass, you got freedom. >> There is a lot of teamwork there. You really have access to all of the intellectual properties. As a network hacker, it's a pretty amazing opportunity. So, we're excited about that. >> But the other thing it does is that you not only get access to all of this intellectual property, but you've got an install base that is so extremely relevant and is the basis for much of what the computing industry and computing world does now and for some extended time into the future. So, you've got a ready-made target of people ready to adopt. How do you think that your core professionals, on the networking side, are going to evolve their skills and their capabilities to make themselves increasingly relevant in this emerging world. >> You know, look, I think that's the story of definite. We see a lot of IT shops that have, you know, really deep infrastructure management capability. And as the infrastructure gets more automated or they start to use Meraki and it gets simpler to manage, they find themselves with time to finally focus on their own mission. Their mission is not, like, massive management of thousands of networking devices. CIOs care about education technology, or hotel technology, or restaurant technology. They finally have time to really work on digitizing the hotel industry, or digitizing schools in Latin America, whatever that happens to be. I really see them, like, moving up the stack. The skills of IT groups around the world are what really are moving up the stack. And all of a sudden, they're building apps. And they're, like, analyzing data and trying to apply machine intelligence to customer behavior. And everything that the promise of this technology used to be. First, we got to get out of the weeds. We got to simplify the infrastructure and get our IT shops out of that and into that business-relevant IT. >> It's also a mindset shift too. Again, you mentioned earlier, it used to be the network is fixed and brittle. And then you were constrained by what the network could provide you above. Now, the apps are dictating down to the networks. So, there's now a new model of app saying, "Hey, I don't need you to be "a provisioning configuration management guru, "on provisioning new devices. "I just want to get the network to do "what I need and not be an expert." That's ethos of DevOps. How is that playing forth for you guys, with DevNet Create out here? Give us some examples of how you guys are making that a reality and some of the directional things that you were working on. >> Yeah, it's a great example. You know, we have an awesome deployment in Mexico, called Mexico Conectado. And it's kind of near and dear to my heart. Federal buildings all over Mexico. The government funded, for the first time ever, internet access and all those sites with wi-fi for the building but also publicly accessible. And a lot of the sites they deployed, it was the first internet connection going into that building. Or maybe even for that town in rural Mexico. You know, deploying out at thousands and thousands, tens of thousands of sites all around Mexico. That could've easily been it. Just trying to make that work. Just the crushing complexity of that many devices and that many sites and a dozen different service providers managing it. By using Meraki, those guys were able to, you know, deploy it out, and really have it managed by the service providers but monitored by the government. And then, open up the APIs. So, that the government can actually analyze across all of those deployments. How the network is being used, what kind of utility they're getting in urban areas verus rural areas. Is this initiative really working that they're bringing, internet's really being used in locations it hasn't been before. Or are they just, kind of, subsidizing internet for well-connected cities already? And they're really getting to see that visibility and understand if they're really meeting their goals. Not just scrambling all day to get off the ground. >> Okay, question from the crowd. Thanks for sending in the questions. Go to crowdchat.net/devnetcreate. A question is, "What is the most important "DevOps practice to you?" And you can globalize for Cisco or in your view, just the industry, community. "Infrastructure is code, configuration management, "continuous delivery, automated testing, or other?" >> Todd: Or other? >> Other being fill in the blank. One that you might think. >> Automated testing is near and dear to my heart. (John chuckles) It's near and dear to my heart. If we didn't implement a strong, automated testing practice at Meraki, we wouldn't ship anything. (John chuckling) Well, if you think about infrastructure is code, obviously that's important to us because that's what we're building, kind of, is a programmable network using these cloud APIs. Maybe the one that I feel is missing from the list would be the real concept of new product instruction through an MVP process. And this concept of building the minimally viable product. So that you get it in the hands of users as early as possible and start getting real feedback. But one value proposition, one used case met, if you can find a way to get that into the hand of users or in the hands of paying customers and start to get that feedback, that's the day that you hire the first real product manager. No one knows what people really want than active users trying to get value out of your product. And trying to figure out and get that expert in on day one before you start development. Don't believe experts, you know, believe users. >> Todd, thanks for coming on The Cube. And sharing the inside, really appreciate. Final question for you. DevNet's been very successful at the Susie. And the team put that together. It's pumping on all cylinders. Just go live, big showcase there. DevNet created an augural event. As it progresses, what's the objective of this event? And how is it different than DevNext events in your mind? >> Yeah, look, I think, just as my opinion and this is how I see it. For a long time, infrastructure has been this closed ecosystem. You buy expensive networking IT infrastructure, you configure it using whatever CLI is available and, like, that's it. And new systems came into being, like, in the cloud, even modern CRMs systems. Like salesforce, modern POS systems, all that stuff. And they all were open platforms. But infrastructure lagged. It was always a close ecosystem. I think what DevNet, kind of, stands for is the opening up of that ecosystem. And allowing the network to, like, dynamically react to the needs of the business. And to really be controlled in a new way. DevNet create for me is, sort of, this is inaugural event of, sort of, Cisco really stepping out and declaring, this is going to be the way of the future. I think we're all going to be sitting here in five years down at Moscone as they tear down the super structure from a five thousand person DevNet create. And we're going to be saying, "I was here at the first one. "I was in San Francisco for the first DevNet." >> Present and creation. >> Todd: Yes, exactly. >> Well done, totally love the mission. I think it's super important. Again, they're not mutually exclusive communities, they're merging together and it's a rising tide, congratulations. Todd Nightingale, senior vice president, general manager of Cisco Meraki cloud automation. Loves automated testing, but again, that's many practices that DevOps eat, those infrastructure is code, developer freedom. That's the theme here. We've got the more live coverage. I'm John Furrier with Peter Burris, stay with us. (upbeat music)