>>The cube presents, Dell technologies world brought to you by Dell. >>Welcome back to the cube. Lisa Martin and Dave Vale are live in Las Vegas. We are covering our third day of covering Dell technologies world 2022. The first live in-person event since 2019. It's been great to be here. We've had a lot of great conversations about all the announcements that Dell has made in the last couple of days. And we're gonna unpack a little bit more of that. Now. One of our alumni is back with us. Shannon champion joins us again, vice president product marketing at Dell technologies, and she's a company by Pete Robinson, the director of infrastructure engineering at Salesforce. Welcome. Thank >>You. >>So Shannon, you had a big announcement yesterday. I run a lot of new software innovations. Did >>You hear about that? I heard a little something >>About that. Unpack that for us. >>Yeah. Awesome. Yeah, it's so exciting to be here in person and have such a big moment across our storage portfolio, to see that on the big stage, the boom to announce major updates across power store, PowerMax and power flex all together, just a ton of innovation across the storage portfolio. And you probably also heard a ton of focus on our software driven innovation across those products, because our goal is really to deliver a continuously modern storage experience. That's what our customers are asking us for that cloud experience. Let's take the most Val get the most value from data no matter where it lives. That's on premises in the public clouds or at the edge. And that's what we, uh, unveil. That's what we're releasing. And that's what we're excited to talk about. >>Now, Pete, you, Salesforce is a long time Dell customer, but you're also its largest PowerMax customer. The biggest in the world. Tell us a little bit about what you guys are doing with PowerMax and your experience. >>Yeah, so, um, for Salesforce, trust is our number one value and that carries over into the infrastructure that we develop, we test and, and we roll out and Parex has been a key part of that. Um, we really like the, um, the technology in terms of availability, reliability, um, performance. And it, it has allowed us to, you know, continue to grow our customers, uh, continue needs for more and more data. >>So what was kind of eye popping to me was the emphasis on security. Not that you've not always emphasized security, but maybe Shannon, you could do a rundown of, yeah. Maybe not all the features, but give us the high level. And at Pete, I, I wonder how I, if you could comment on how, how you think about that as a practitioner, but please give us that. >>Sure. Yeah. So, you know, PowerMax has been leading for, uh, a long time in its space and we're continuing to lean into that and continue to lead in that space. And we're proud to say PowerMax is the world's most secure mission, critical storage platform. And the reason we can say that is because it really is designed for comprehensive cyber resiliency. It's designed with a zero trust security architecture. And in this particular release, there's 19 different security features really embedded in there. So I'm not gonna unpack all 19, but a couple, um, examples, right? So multifactor authentication also continuous ransomware anomaly detection, a leveraging cloud IQ, which is, uh, huge. Um, and last but not least, um, we have the industry's most granular cyber recovery at scale PowerMax can do up to 65 million imutable snapshots per array. So just, uh, and that's 30 times more than our next nearest competitor. So, you know, really when you're talking about recovery point objectives, power max can't be beat. >>So what does that mean to you, Pete? >>Uh, well, it's it's same thing that I was mentioning earlier about that's a trust factor. Uh, security is a big, a big part of that. You know, Salesforce invests heavily into the securing our customer data because it really is the, the core foundation of our success and our customers trust us with their data. And if we, if we were to fail at that, you know, we would lose that trust. And that's simply not, it's not an option. >>Let's talk about that trust for a minute. We know we've heard a lot about trust this week from Michael Dell. Talk to us about trust, your trust, Salesforce's trust and Dell technologies. You've been using them a long time, but cultural alignment yeah. Seems to be pretty spot on. >>I, I would agree. Um, you know, both companies have a customer first mentality, uh, you know, we, we succeed if the customer succeeds and we see that going back and forth in that partnership. So Dell is successful when Salesforce is successful and vice versa. So, um, when we've it's and it goes beyond just the initial, you know, the initial purchase of, of hardware or software, you know, how you operate it, how you manage it, um, how you continue to develop together. You know, our, you know, we work closely with the Dell engineering teams and we've, we've worked closely in development of the new, new PowerMax lines to where it's actually able to help us build our, our business. And, and again, you know, continue to help Dell in the process. So you've >>Got visibility on the new, a lot of these new features you're playing around with them. What I, I, I obviously started with security cuz that's on top of everybody's mind, but what are the things are important to you as a customer? And how do these features the new features kind of map into that? Maybe you could talk about your experience with the, I think you're in beta, maybe with these features. Maybe you could talk about that. >>Yeah. Um, probably the, the biggest thing that we're seeing right now, other than OB the obvious enhancements in hardware, which, which we love, uh, you know, better performance, better scalability, better, and a better density. Um, but also the, some of the software functionality that Dells starting to roll out, you know, we've, we've, we've uh, implemented cloud IQ for all of our PowerMax systems and it's the same thing. We continue to, um, find features that we would like. And we've actually, you know, worked closely with the cloud IQ team. And within a matter of weeks or months, those features are popping up in cloud IQ that we can then continue to, to develop and, and use. >>Yeah. I think trust goes both ways in our partnership, right? So, you know, Salesforce can trust Dell to deliver the, you know, the products they need to deliver their business outcomes, but we also have a relationship to where we can trust that Salesforce is gonna really help us develop the next generation product that's gonna, you know, really deliver the most value. Yeah. >>Can you share some business outcomes that you've achieved so far leveraging power max and how it's really enabled, maybe it's your organization's productivity perspective, but what are some of those outcomes that you've achieved so far? >>Um, there there's so many to, to, to choose from, but I would say the, probably the biggest thing that we've seen is a as we roll out new infrastructure, we have various generations that we deploy. Um, when we went to the new PowerMax, um, initially we were concerned about whether our storage infrastructure could keep up with the new compute, uh, systems that we were rolling out. And when we went through and began testing it, we came to realize that the, the performance improvements alone, that we were seeing were able to keep up with the compute demand, making that transition from the older VMAX platforms to the PMAX practically seamless and able to just deploy the new SKUs as, as they came out. >>Talk about the portfolio that you apply to PowerMax. I mean, it's the highest of the highest end mission critical the toughest workloads in the planet. Salesforce has made a lot of acquisitions. Yeah. Um, do you throw everything at PowerMax? Are you, are you selective? What's your strategy there? So >>It's, it's selective. In other words that there's no square peg that meets every need, um, you know, acquisitions take some time to, to ingest, um, you know, some run into cloud, some run in first, in, in first party. Um, but so we, we try to take a very, very intentional approach to where we deploy that technology. >>So 10 years ago, someone in your position, or maybe someone who works for you was probably do spent a lot of time managing lawns and tuning performance. And how has that changed? >>We don't do that. <laugh> we? >>We can, right. So what do you do with right. Talk, talk more double click on that. So how talk about how that transition occurred from really non-productive activities, managing storage boxes. Yeah. And, and where you are today, what are you doing with those resources? >>It, it, it all comes outta automation. Like, you know, the, you know, hardware is hardware to a point, um, but you reach a point where the, the manageability scale just goes exponential and, and we're way, well past that. And the only way we've been able to meet that, meet that need is to, to automate and really develop our operations, to be able to not just manage at a lung level or even at the system level, but manage at the data center level at the geographical, you know, location level and then being able to, to manage from there. >>Okay. Really stupid question. But I'm gonna ask it cause I wanna hear your answer. True. Why can't you just take a software defined storage platform and just run everything on that? Why do you need all these different platforms and why do you gotta spend all this money on PowerMax? Why, why can't you just do >>That? That's the million dollar question. Uh, I, I ask that all the time. <laugh>, um, I think software defined is it's on its way. Um, it's come a long way just in the last decade. Yeah. Um, but in terms of supporting what I consider mission critical, large scale, uh, applications, it's, it's not, it's just simply not on par just yet with what we do with PowerMax, for example. >>And that's exactly how we position it in our portfolio. Right? So PowerMax runs on 95% of the fortune 100 companies, top 20 healthcare companies, top 10 financial services companies in the world. So it's really mission critical high end has all of the enterprise level features and capabilities to really have that availability. That's so important to a lot of companies like Salesforce and, and Pete's right, you know, software define is on its way and it provides a lot of agility there. But at the end of the day for mission critical storage, it's all about PowerMax. >>I wonder if we're ever gonna get to, I mean, you, you, you, it was interesting answer cuz you kind of, I inferred from your that you're hopeful and even optimistic that someday will get to parody. But I wonder because you can't be just close enough. It's almost, you have to be. >>I think, I think the key answer to that is it's it's the software flying gets you halfway there. The other side of the coin is the application ecosystem has to change to be able to solve that other, other side of it. Cuz if you simply simply take an application that runs on a PowerMax and try to run it, just forklift it over to a software defined. You're not gonna have very much luck. >>Recovery has to be moved up to stack >>Operations recovery, the whole, whole whole works. >>Jenny, can you comment on how customers like Salesforce? Like what's your process for involving them in testing in roadmap and in that direction, strategic direction that you guys are going? Great >>Question. Sure. Yeah. So, you know, customer feedback is huge. You've heard it. I'm sure this is not new right product development and engineering. We love to hear from our customers. And there's multiple ways you heard about beta testing, which we're really fortunate that Salesforce can help us provide that feedback for our new releases. But we have user groups, we have forums. We, we hear directly from our sales teams, our, you know, our customers, aren't shy, they're willing to give us their feedback. And at the end of the day, we take that feedback and make sure that we're prioritizing the right things in our product management and engineering teams so that we're delivering the things that matter. Most first, >>We've heard a lot of that this week. So I would agree guys, thank you so much for joining Dave and me talking about Salesforce. What you doing with PowerMax? All the stuff that you announced yesterday, alone. Hopefully you get to go home and get a little bit of rest. >>Yes. >>I'm sure that there's, there's never a dull moment. Never. Can't wait guys. Great to have you. >>Thank you. You guys, >>For our guests on Dave Volante, I'm Lisa Martin and you're watching the queue. We are live day three of our coverage of Dell technologies world 2022, Dave and I will be right back with our final guest of the show.

>>Good morning, welcome to the cubes coverage of Qube con and cloud native con 21 live from Los Angeles. Lisa Martin, here with Dave Nicholson. David's great to be in person with other humans at this conference. Finally, I can't believe >>You're arms length away. It's unreal. >>I know, and they checked backs cards. So everybody's here is nice and safe. We're excited to welcome kingdom Barrett to the program, flux, maintainer and open source support engineer at we works. He came to him. Welcome to the program. >>Oh, thank you for having me on today. >>So let's talk about flux. This is a CNCF incubating project. I saw catalyze as adopt talk to us about flux and its evolution. >>Uh, so flex is, uh, uh, just got into its second version a while ago. We've been, uh, working on, um, uh, we're an incubating project and we're going towards graduation at this point. Um, flex has seen a great deal of adoption from, uh, infant cloud infrastructure vendors in particular, uh, like Microsoft and Amazon and VMware, all building products on, um, flux, uh, the latest version of flux. And, uh, we've heard, uh, from companies like Alibaba and state farm. We had a, uh, uh, conference, uh, at a co-hosted event earlier on Tuesday called get-ups con, uh, where we presented all about get ops, which is the technology, uh, guiding, uh, set of principles that underlies flux. And, uh, there are new adopters, um, all, all every day, including, uh, the department of defense, uh, who has a hundred thousand developers. Um, it's, it's, it's very successful project at this point, who are the >>Key users of flux flux? >>Excuse me. The key users of flux are, uh, probably, uh, application developers and infrastructure engineers, and platform support folks. So a pretty broad spectrum of people. >>And you've got some news at the event. >>Yeah, we actually, uh, we have a, uh, ecosystem event that's coming up, um, on October 20th, uh, it's free virtual event. Uh, folks can join us to hear from these companies. We have people from high level, uh, CTOs and GMs, uh, from companies like Microsoft, Amazon VMware, uh, we've worked D two IQ, um, that are, uh, going to be speaking, uh, about their, uh, products that you can buy from their cloud vendor, uh, that, uh, are based on flux. Uh, so, so that's a milestone for us. That's a major milestone. These are large vendors, um, major cloud vendors that have decided that they trust, uh, flux with their customers workloads. And it's, it's the way that they want to push get ups. Great >>Validation. Yeah. >>So give us an example, just digging in a little bit on flux and get ops. What are some of the things that flux either enforces or enables or validates? What, how would you describe the flux get ops relationship? >>So the first to get ops principles is declarative infrastructure and that's, uh, that's something that people who are using Kubernetes are already very familiar with. Um, flux has a basic itself, or, or I guess spawned, uh, maybe is a better way to say it. Uh, this, um, uh, whole get ops working group, that's just defined the principles. There's four of them in the formal definition. That's just been promoted to a 1.0 and, uh, the get ups working group, publish, publish this at, uh, open get-ups dot dev where you can read all four. And, um, it's great copy site. If you're not really familiar with get ops, you can, you can read all four, but, uh, the other, uh, the second one I would have mentioned is, uh, version storage is, is, uh, it's called get ups and get as a version store. So it's a good for, um, disaster recovery. >>Uh, and, uh, if you have an issue with a new release, if you're, uh, pushing changes frequently, that's, you know, more than likely you will have issues from time to time. Uh, you can roll back with, get ups because everything is version. Um, and, uh, you can do those releases rapidly because the deployment is automatic, um, and it's continuously reconciling. So those are the four principles of get ups. Uh, and they're, they're not exactly prescriptive. You don't have to adopt them all at once. You can pick and choose where you want to get started. Um, but that's what, uh, is underneath flux. >>How do you help customers pick and choose based on what are some of the key criteria that you would advise them on? >>We would advise them to try to follow all of those principles, because that's what you get out of the box with fluxes is a solution that does those things. But if there is one of those things that gets in a way, um, there's also the concept of a closed loop that is, um, sometimes debated as whether it should be part of the get ops principles or not. Um, that just means that, uh, when you use get-ups the only changes that go to your infrastructure are coming through get-ups. Uh, so you don't have someone coming in and using the back door. Um, it all goes through get, uh, w when you want to make a change to your cluster or your application, you push it to get the automation takes over from there and, um, and makes, uh, developers and platform engineers jobs a lot easier. And it makes it easier for them to collaborate with each other, >>Of course, productivity. You mentioned AWS, Microsoft, VMware, uh, all working with you to deliver, get ups to enterprise customers. Talk to me about some of the benefits in it for these big guys. I mean, that's great validation, but what's in it for AWS and VMware and Microsoft, for example, business outcome wise. >>Well, uh, one of the things that we've been promoting and since June is a flex has been, uh, uh, there's an API underneath, that's called the get ops toolkit. This is, uh, if you're building a platform for platforms like these cloud vendors are, um, we announced that fluxes APRs are officially stable. So that means that it's safe for them to build on top of, and they can, uh, go ahead and build things and not worry that we're going to pull the rug out from under them. So that's one of the major vendors, uh, one of the major, uh, uh, vendor benefits and, um, uh, we've, we've also added a recent improvement, uh, uh, called service side apply that, uh, will improve performance. Uh, we reduced the number of, um, API calls, but also for, for, uh, users, it makes things a lot easier because they don't have to write explicitly health checks on everything. Uh, it's possible for them to say, we'd like to see everything is healthy, and it's a one-line addition, that's it? >>So, you know, there's been a lot of discussion from a lot of different angles of the subject of security, uh, in this space. Um, how does this, how does this dovetail with that? A lot of discussion specifically about software supply chain security. Now this is more in the operations space. How do, how do those come together? Do you have any thoughts on security? >>Well, flux is built for security first. Um, there are a lot of products out there that, uh, will shell out to other tools and, and that's a potential vulnerability and flux does not do that. Uh, we've recently undergone a security audit, which we're waiting for the results and the report over, but this is part of our progress towards the CNCF graduated status. Um, and, uh, we've, we've liked what we've seen and preliminary results. Uh, we've, we've prepared for the security audit on knowing that it was coming and, uh, uh, flexes, uh, uh, designed for security first. Uh, you're able to verify that the commits that you're applying to your cluster are signed and actually come from a valid author who is, uh, permitted to make changes to the cluster and, uh, get ops itself is, is this, uh, model of operations by poll requests. So, um, you, you have an opportunity to make sure that your changes are, uh, appropriately reviewed before they get applied. >>Got it. So you had a session at coupon this week. Talk to me a little bit about that. What were like the top three takeaways, and maybe even share with us some of the feedback that you got from the audience? >>Um, so, uh, the session was about Jenkins and get ups or Jenkins and flux. And the, um, the main idea is that when you use flux, flux is a tool for delivery. So you've heard maybe of CIC, D C I N C D are separate influx. We consider these as two separate jobs that should not cross over. And, uh, when, when, uh, you do that. So the talk is about Jenkins and flux. Jenkins is a very popular CII solution and the messages, uh, you don't have to abandon, if you've made a large infrastructure investment in a CII solution, you don't have to abandon your Jenkins or your GitHub actions or, or whatever other CII solution you're using to build and test images. Uh, you can take it with you and adopt get ups. >>Um, so there's compatibility there and, and usability familiarity for the audience, the users. Yeah. What was some of the feedback that they provided to you? Um, were they surprised by that? Happy about that? >>Well, and talk to us a little bit fast paced. Uh, we'll put it in the advanced CIC D track. I covered a lot of ground in that talk, and I hope to go back and cover things in a little bit smaller steps. Um, I tried to show as many of the features of Fluxus as I could. Uh, and, and so one of the feedback that I got was actually, it was a little bit difficult to follow up as, so I'm a new presenter. Um, this is my first year we've worked. I've never presented at CubeCon before. Um, I'm really glad I got the opportunity to be here. This is a great, uh, opportunity to collaborate with other open source teams. And, um, that's, that's, uh, that's the takeaway from me? No. >>So you've got to give a shout out to, uh, to weave works. Absolutely. You know, any, any organization that realizes the benefit of having its folks participating in the community, realizing that it, it helps the community, it helps you, it helps them, you know, that's, that's what we love about, about all of this. >>Yeah. We're, uh, we're really excited to grow adoption for, um, Kubernetes and get ops together. So, >>So I've asked a few people this over the last couple of days, where do you think we are in the peak Kubernetes curve? Are we still just at the very beginning stages of this, of this as a, as a movement? >>Um, certainly we're, um, it's, it's, uh, for, for people who are here at CubeCon, I think we see that, you know, uh, a lot of companies are very successful with Kubernetes, but, um, I come from a university, it, uh, background and I haven't seen a lot of adoption, uh, in, in large enterprise, um, more conservative enterprises, at least in, in my personal experience. And I think that, uh, there is a lot for those places to gain, um, through, through, uh, adopting Kubernetes and get ups together. I think get ops is, uh, we'll provide them with the opportunity to, uh, experience Kubernetes in the best way possible. >>We've seen such acceleration in the last 18, 19 months of digital transformation for companies to survive, to pivot during COVID to survive, doubt to thrive. Do you see that influencing the adoption of Kubernetes and maybe different industries getting more comfortable with leveraging it as a platform? >>Sure. Um, a lot of companies see it as a cost center. And so if you can make it easier or possible to do, uh, operations with fewer people in the loop, um, that, that makes it a cost benefit for a lot of people, but also you need to keep people in the loop. You need to keep the people that you have included and, and be transparent about what infrastructure choices and changes you're making. So, uh, that's one of the things that get ups really helps with >>At transparency is key. One more question for you. Can you share a little bit before we wrap here about the project roadmap and some of the things that are coming down the pike? Yeah. >>So I mentioned a graduation. That's the immediate goal that we're working towards? Uh, most directly, uh, we have, um, grown our, uh, number of integrations pretty significantly. We have an operator how entry in red hat, open shift there's operator hub, where you can go and click to install flux. And that's great. Um, and, uh, we looked forward to, uh, making flux more compatible with more of the tools that you find in the CNCF umbrella. Um, that's, that's what our roadmap is for >>Increasing that compatibility. And one more time mentioned the event, October 20th, I believe he said, let folks know where they can go and find it on the web. Yeah. >>If you're interested in the get ups days.com, it's the get-ups one-stop shop and it's, uh, vendors like AWS and Microsoft and VMware detour IQ. And we've worked, we've all built a flux based solutions, um, for, uh, that are available for sale right now. So if you're, uh, trying to use get-ups and you have one of these vendors as your cloud vendor, um, it seems like a natural fit to try the solution that's out of the box. Uh, but if you need convincing, you get Upstate's dot com, you can go find out more about the event and, uh, we'll hope to see you there. >>I get upstairs.com kingdom. Thank you. You're joining Dave and me on the program, talking to us about flux. Congratulations on its evolution. We look forward to hearing more great things as the years unfold. >>Thank you so much for having me on our pleasure >>For Dave Nicholson. I'm Lisa Martin. You're watching the kid live from Los Angeles at CubeCon cloud native con 21 stick around Dave and I, and we'll be right back with our next guest.

(upbeat music) >> Live from Orlando Florida. It's the Cube. Covering Cisco Live 2018. Brought to Cisco NetApp and the Cube's ecosystem partners. >> Welcome back to the Cube's Live coverage here in Orlando Florida for Cisco Live 2018. It's the Cube's coverage. >> I'm John Furrier. The host. Here for three days of wall-to wall-coverage. Our next guest is Shubha Govil. Whose the director of product management for Cisco DevNet. Welcome to the Cube. Thanks for coming on. >> Thanks John. Thanks for having me on Cube. >> Great conversation before the cameras came out. We're talking about development and Cloud Native. But we're super impressed with the work you guys have done at DevNet. Certainly it's the top story of the show here is that Cisco has now crossed over the flywheel of innovation where 500,000 registered developers. >> Developers. Not visitors to a website. >> Yes. Or some marketing program. >> Correct. >> Real engaging developers. >> Absolutely. >> Congratulations. >> Thank you John. Thank you. >> A couple of years. Four years and you're here. You've got DevNet. And DevNet Create. Which we've been covering extensively as well. >> Yes. >> Which is the Cloud Native world coming together. >> Yes. >> This is for the first time in Cisco's history where you have now a clear line of sight for network engineers network developers network experts who have been certified in the CCIE and other certifications. CCNA, CCNP. All the stuff you guys do. You can now see a clear line where you can extend the capabilities and knowledge and expertise in power of networking. >> Absolutely. >> Up the stack. >> Absolutely. >> Finally Cisco's moving up the stack. >> Yes. >> Tell us what's going on in the product side? >> Yeah Absolutely. And I'm gonna talk about very specific example today. And today if you heard the keynote speak. And Susie opened up a few things and announcement. One of them was DNA developer center. And I'm gonna talk about that. Because part of it is how network is an open platform now. And that was part of the announcement. You will hear a lot about that. And linking it back to Dev reports. Quite right. They should care about why they should look into it. So three things I'm gonna talk about. DNA, developer center and what they can find there. And once they go there and they really start learning about our platform on API's on DevNet. What cord exchange does for them. And how they can start not only programming the Intent based on our Intent API's and what they want network to do for them but also sharing some community cord. Are using that community cord. Community Cord if they are just getting started. Right? So on DNA Developers Center we have four capabilities highlighted. These are the API's. Whether they are Intent API's Integration API's to connect with other third parties. Or SDK's to manage multi-party devices. Or there for ITSM or a specific use case integrations. >> So hold up. Go slow. >> I'm kind of not on the uptake as you are on this. Because you're in it. IF DNA is a set of abstractions API's on top of the equipment. >> Correct. >> So it's not natively. It's a set of API. >> Set of API's. >> So that people could use those API's to create services. >> To manage their network wealth. To automate and drive these right use cases. So I might. >> Give me an example. >> Yeah let's talk about an example. Intent. My intent might be to. We were talking about radio conferences awhile back. And I come from that environment. I want to drive a Butler QS for certain level of execs. Right? If they are on the call this was the thing of like eight ten years back. If my execs are on a call make sure they have the best experience. So the QS quality of your network should be set up to a level that there's no disruption. There's no latency in the call. Right? So that's an intent. That's a business intent. Give best experience to my execs. >> So really that's combining policy and QOS together to make it meet the outcome. Which is no latency. >> To meet the outcome. But for the network engineer now let's connect back to the developer. The network engineer whose trying to make this intent possible for the execs. There's a places they need to set up the SQSS. And won't it be easy of them if there was a simple API that they can use to create that solution to drive that policy across the devices. Whether Cisco devices or non Cisco devices. >> This has been the challenge for network engineers in general. Because you want to have things in control and locked down but as you want to do more things that are programmable. >> Correct. >> There's been some provisioning and some configuration management things. >> Correct. >> You're saying, hey you're gonna lock down all the architecture and then move up. Use the API's to do better integration. Make things run smoothly without disrupting the network. Is that right? >> That's part of it. But also it's about making it easy for them. Correct? Simplify the process of doing it. The process of making it happen was long steps of CLI command. That now that network engineer was going continuously. A lot of the time people actually tells us that they would have this cut and paste copy of the command. That they will take from one place go to the next place next device and next device. And continue to do that step. And that's the productivity game we are driving by simplifying where one API call can go across all the devices and make that change happen. >> We've heard that a lot from on DevNet and the hallway conversations that said DevNet's made my life easier. >> Yes. >> I don't have to do those mundane tasks. >> Exactly. >> That were part of getting things done. Okay. Let me ask you personal question. As director of product management for DevNet. What is your product scope? What are you working on? Can you take a minute? >> That's a very good question. And that's where some of these offers we were talking about earlier come in to play. So for example, within Devnet we create a lot of offers to make developers lives simple. Whether we are talking about giving them the best quality of learning content. Or giving them hosted Sandbox environment to try and test. All of that requires a lot of product management knowledge and the need. But really what the 2ADS we have work more closely to get them out to market. One is the thing called Code Exchange. It's a tool for our developer committee. Where we have aggregated the public git code across the Cisco technologies. >> That's on GitHub I think. >> GitHub code right. Absolutely. But the second powerful thing on top of that is our Ecosystem Exchange. This is where we are bringing an aggregated view of every partner out there. Every Cisco partner whose creating great solutions on our API's in a single place our developers can go and find that solution. To really address the business outcome they are looking to address. >> Shubha, I want you to put some color commentary around of some of the feedback you've heard. We hear people of the DevNet community saying I've come to Cisco Live and I spend all my week here in DevNet. Because it really is kind of like a kid in the candy store. (Shubha laughs) >> From a computer science or developer prospective. >> Yeah. >> What are some of the cool examples and demos that you guys have here? What's your favorite? What are some of the things that are jumping out that people are gravitating towards? >> I will tell you one of the most popular sessions that I have seen in the last few days here is Network Programmability for Networking Juniors. That's one. There's also a very Network Programmability one-on-one. Coding one-on-one class. It's basic Python. But applying it in network context. Those are some of the most popular sessions that I have seen. But when it comes to cool demos there's a cool demo around Flex IQ. I think you might be talking to Ashish later about that. >> Yes. >> And really it's a retail scenario how you are tracking. Using the location based service example. But in this case camera feed. Really analyzing where people are. And you'll get to hear more about this. >> We took a ad. I saw the demo. >> Yeah. >> The Flex IQ. First of all I love the name. I said trademark it immediately. (Shubha laughs) Get it out there. First use wins. And it's already out there. But it's really taking a A access point. >> This is an access point. >> And it plugs into a camera. And a great example of some of the coolness you can do with a preexisting condition. In this case an access point. >> So each of these information points that data one that they are collecting. Whether it's a camera feed. It's a location service. Like information about the devices and the environment. Each set of data is the relevance in this. Which is driving the newest use cases. And this data is coming through API's that have labeled but I'd say morockie access point API. All the camera API that are labeled that have enabled C Space. >> This is really the aha moment for me. I've been following Cisco really since the 90's. >> Yeah. >> Or at least when they formed. Being the young gun at the time. Younger than I am now. 30 years ago. But it was really networking. Connecting companies together. It was the plumbing. It was the core. >> Yes. Unstoppable since then. Now the success is still there. But it's really the problem solving is never going away. I saw this security challenges that were outlined in the keynote. We all know Cybe Ops is a huge issue. Cloud is here. You've got industrial IOT going on. And IOT. But these examples that DevNet is showing is that these new capabilities with I won't say a hack but a maker faire culture. >> It is a maker culture right. Which is lot of DIY stuff. So this lot of learning by playing with the API's and multiple one of them. And you'd really find use cases you have never addressed before. We also have a design thinking workshop here going on. And part of it is really thinking about the use cases from the user prospective. What you are trying to address. Before finding the cool technologies. Really understand what your users' needs are. >> Yeah. >> And we are doing a lot of things around that. And bringing it connecting it back to the APIs. Once we learn the right needs. And finding these use cases that were never possible before. >> Well I talked to Susie all the time about this. >> Yeah. >> And I know she's really hardcore on this. But you guys have nailed the community aspect as well. You've brought that open source ethos into the formula. Which makes it more collaborative. No one wants to be alone. I mean the last thing a network engineer wants to do is be the old way of being tied to the chair on the network. Troubleshooting problems. They want to have more collaboration As some of this creativity kicks in. So it's really a new time. How are you guys handling this? Is it like people are having an awakening moment? Or what are you guys doing to nature this? What are some of the exciting things? >> And the best part about the community is that communities learning with each other. Right? It's this feeling of we are enabling our community both traditionally and through even like Cisco Live and DevNet Create. We bring them together to be able to learn from each other much as we learn with them. And trying to define the right use cases and solutions. And that's what the company's behind. The 500,000 developers who are coming and learning with us. They have found the use cases they were addressing for their business. They also found a new skill set that they were looking to learn before. >> Yeah. >> And a lot of them have come along where they are showing their tech cred in the community. Really being the community leaders. >> You know it's been kind of a downer some of the narrative I've seen from press outlets other press outlets and other kind of naysayers has been Hey network guys. You're gonna be automated away. Go learn how to code to save your career. Actually that's not happening. >> That is not happening at all. >> The power of networking certainly as security moves down lower on the stack. And policy and these cool service oriented service meshes. Kubernetes. Really points to the relevance of the network engineer more than ever. You've got SDN. Software Defined Data Center. That's not going away. Automation is going to take mundane tasks away. >> Yes. >> But actions happening at the app layer. >> They have that expertise and 20 years plus experience knowing how networks should be running to make these things possible. The use cases around the applications possible. >> They're more relevant than ever. >> They are more relevant than ever. I would say. Exactly. That's the key. >> Well you guys are at the beginning I think of another set of inflection point. Certainly DevNet's gone in a quick four years. You're connecting to the Cloud Native World with DevNet Create. Which is phenomenal. Those are two worlds that are coming together. I just see another inflection point coming. Maybe it's a million developers. But you've been success in the enterprise where it's been really difficult. Even Microsoft with their legacy developer program .net. The Visual Basic and all the MSDM stuff. >> At the by GitHub >> Yup. >> To kind of maintain relevance. Other companies like Oracle VM wear and other ones they're having a hard time. You guys are just kicking butt. >> So part of it for us is not only focusing on traditional infrastructure. But also talking about the app developer. So these application developers who did not know about network at all. A lot of times they had to fight with their networking juniors to get their application the particular function they wanted to have. Right? So that what we are enabling by bringing them together. Also we have been running small programs like we are trying new markets. Global markets. China, India and some of the things like really reaching out to the big large hackathons. Which are traditionally. For example in India we were recently doing a smart India hackathon. >> Nice. >> There are 500,00 students participated in solving real problems for the country. And DevNet was the provider of applications and API's. Bringing them into the application world with the understanding of network. >> A lot of growth in India and China. Certainly massive new developers coming on board. Okay final question to wrap up the segment. I gotta get your prospective. Take your DevNet hat off for a second. >> Okay. Put your Cisco hat on. >> Sure. For the folks who couldn't make Cisco Live this year what's the big story coming out of the event this year? You guys have been successful with the 500,000 developers. What's the big story developing here? What should people know is the most important story for Cisco Live 2018? >> I think the biggest story I would like to call out is that network is open for business. Network is really open for you to really come and make your intent. Your use cases. Your business outcomes possible. And that's the biggest story I will call out. >> Shubha Govil here product management for DevNet. Here on the Cube. Live coverage. Day two of three days. I'm John Furrier. Stay with us for more live coverage. As we start winding down day two. A lot of great action. The network is programmable. It's creating value and new use cases. And the developers are in the center of the action. The network engineers seeing a clear path of the Cloud and more. We'll be back with more after this short break. (upbeat music)