>> From The Cube studios in Palo Alto, in Boston, bringing you data driven insights from the cube and ETR. This is breaking analysis with Dave Vellante. >> Last year, we noted in a breaking analysis that the cloud ecosystem is innovating beyond the idea or notion of multi-cloud. We've said for years that multi-cloud is really not a strategy but rather a symptom of multi-vendor. And we coined this term supercloud to describe an abstraction layer that lives above the hyperscale infrastructure that hides the underlying complexities, the APIs, and the primitives of each of the respective clouds. It interconnects whether it's On-Prem, AWS, Azure, Google, stretching out to the edge and creates a value layer on top of that. So our vision is that supercloud is more than running an individual service in cloud native mode within an individual individual cloud rather it's this new layer that builds on top of the hyperscalers. And does things irrespective of location adds value and we'll get into that in more detail. Now it turns out that we weren't the only ones thinking about this, not surprisingly, the majority of the technology ecosystem has been working towards this vision in various forms, including some examples that actually don't try to hide the underlying primitives. And we'll talk about that, but give a consistent experience across the DevSecOps tool chain. Hello, and welcome to this week's Wikibon, Cube insights powered by ETR. In this breaking analysis, we're going to share some recent examples and direct quotes about supercloud from the many Cube guests that we've had on over the last several weeks and months. And we've been trying to test this concept of supercloud. Is it technically feasible? Is it business rational? Is there business case for it? And we'll also share some recent ETR data to put this into context with some of the players that we think are going after this opportunity and where they are in their supercloud build out. And as you can see I'm not in the studio, everybody's got COVID so the studios shut down temporarily but breaking analysis continues. So here we go. Now, first thing is we uncovered an article from earlier this year by Lori MacVittie, is entitled, Supercloud: The 22 Answer to Multi-Cloud Challenges. What a great title. Of course we love it. Now, what really interested us here is not just the title, but the notion that it really doesn't matter what it's called, who cares? Supercloud, distributed cloud, someone even called it Metacloud recently, and we'll get into that. But Lori is a technologist. She's a developer by background. She works at F-Five and she's partial to the supercloud definition that was put forth by Cornell. You can see it here. That's a cloud architecture that enables application migration as a service across different availability zones or cloud providers, et cetera. And that the supercloud provides interfaces to allocate, migrate and terminate resources... And can span all major public cloud providers as well as private clouds. Now, of course, we would take that as well to the edge. So sure. That sounds about right and provides further confirmation that something new is really happening out there. And that was our initial premise when we put this fourth last year. Now we want to dig deeper and hear from the many Cube guests that we've interviewed recently probing about this topic. We're going to start with Chuck Whitten. He's Dell's new Co-COO and most likely part of the Dell succession plan, many years down the road hopefully. He coined the phrase multi-cloud by default versus multi-cloud by design. And he provides a really good business perspective. He's not a deep technologist. We're going to hear from Chuck a couple of times today including one where John Furrier asks him about leveraging hyperscale CapEx. That's an important concept that's fundamental to supercloud. Now, Ashesh Badani heads products at Red Hat and he talks about what he calls Metacloud. Again, it doesn't matter to us what you call it but it's the ecosystem gathering and innovating and we're going to get his perspective. Now we have a couple of clips from Danny Allan. He is the CTO of Veeam. He's a deep technologist and super into the weeds, which we love. And he talks about how Veeam abstracts the cloud layer. Again, a concept that's fundamental to supercloud and he describes what a supercloud is to him. And we also bring with Danny the edge discussion to the conversation. Now the bottom line from Danny is we want to know is supercloud technically feasible? And is it a thing? And then we have Jeff Clarke. Jeff Clark is the Co-COO and Vice Chairman of Dell super experienced individual. He lays out his vision of supercloud and what John Furrier calls a business operating system. You're going to hear from John a couple times. And he, Jeff Clark has a dropped the mic moment, where he says, if we can do this X, we'll describe what X is, it's game over. Okay. So of course we wanted to then go to HPE, one of Dell's biggest competitors and Patrick Osborne is the vice president of the storage business unit at Hewlett Packet Enterprise. And so given Jeff Clarke's game over strategy, we want to understand how HPE sees supercloud. And the bottom line, according to Patrick Osborne is that it's real. So you'll hear from him. And now Raghu Raghuram is the CEO of VMware. He threw a curve ball at this supercloud concept. And he flat out says, no, we don't want to hide the underlying primitives. We want to give developers access to those. We want to create a consistent developer experience in that DevsSecOps tool chain and Kubernetes runtime environments, and connect all the elements in the application development stack. So that's a really interesting perspective that Raghu brings. And then we end on Itzik Reich. Itzik is a technologist and a technical team leader who's worked as a go between customers and product developers for a number of years. And we asked Itzik, is supercloud technically feasible and will it be a reality? So let's hear from these experts and you can decide for yourselves how real supercloud is today and where it is, run the sizzle >> Operative phrase is multi-cloud by default that's kind of the buzz from your keynote. What do you mean by that? >> Well, look, customers have woken up with multiple clouds, multiple public clouds, On-Premise clouds increasingly as the edge becomes much more a reality for customers clouds at the edge. And so that's what we mean by multi-cloud by default. It's not yet been designed strategically. I think our argument yesterday was, it can be and it should be. It is a very logical place for architecture to land because ultimately customers want the innovation across all of the hyperscale public clouds. They will see workloads and use cases where they want to maintain an On-Premise cloud, On-Premise clouds are not going away, I mentioned edge clouds, so it should be strategic. It's just not today. It doesn't work particularly well today. So when we say multi-cloud by default we mean that's the state of the world today. Our goal is to bring multi-cloud by design as you heard. >> Really great question, actually, since you and I talked, Dave, I've been spending some time noodling just over that. And you're right. There's probably some terminology, something that will get developed either by us or in collaboration with the industry. Where we sort of almost have the next almost like a Metacloud that we're working our way towards. >> So we manage both the snapshots and we convert it into the Veeam portable data format. And here's where the supercloud comes into play. Because if I can convert it into the Veeam portable data format, I can move that OS anywhere. I can move it from physical to virtual, to cloud, to another cloud, back to virtual, I can put it back on physical if I want to. It actually abstracts the cloud layer. There are things that we do when we go between cloud some use BIOS, some use UEFI, but we have the data in backup format, not snapshot format, that's theirs, but we have it in backup format that we can move around and abstract workloads across all of the infrastructure. >> And your catalog is control in control of that. Is that right? Am I thinking about that the right way? >> Yeah it is, 100%. And you know what's interesting about our catalog, Dave, the catalog is inside the backup. Yes. So here's, what's interesting about the edge, two things, on the edge you don't want to have any state, if you can help it. And so containers help with that You can have stateless environments, some persistent data storage But we not not only provide the portability in operating systems, we also do this for containers. And that's true. If you go to the cloud and you're using say EKS with relational database services RDS for the persistent data later, we can pick that up and move it to GKE or move it to OpenShift On-Premises. And so that's why I call this the supercloud, we have all of this data. Actually, I think you termed the term supercloud. >> Yeah. But thank you for... I mean, I'm looking for a confirmation from a technologist that it's technically feasible. >> It is technically feasible and you can do it today. >> You said also technology and business models are tied together and enabler. If you believe that then you have to believe that it's a business operating system that they want. They want to leverage whatever they can. And at the end of the day, they have to differentiate what they do. >> Well, that's exactly right. If I take that in what Dave was saying and I summarize it the following way, if we can take these cloud assets and capabilities, combine them in an orchestrated way to deliver a distributed platform, game over. >> We have a number of platforms that are providing whether it's compute or networking or storage, running those workloads that they plum up into the cloud they have an operational experience in the cloud and they now they have data services that are running in the cloud for us in GreenLake. So it's a reality, we have a number of platforms that support that. We're going to have a a set of big announcements coming up at HPE Discover. So we led with Electra and we have a block service. We have VM backup as a service and DR on top of that. So that's something that we're providing today. GreenLake has over, I think it's actually over 60 services right now that we're providing in the GreenLake platform itself. Everything from security, single sign on, customer IDs, everything. So it's real. We have the proofpoint for it. >> Yeah. So I want to clarify something that you said because this tends to be very commonly confused by customers. I use the word abstraction. And usually when people think of abstraction, they think it hides capabilities of the cloud providers. That's not what we are trying to do. In fact, that's the last thing we are trying to do. What we are trying to do is to provide a consistent developer experience regardless of where you want to build your application. So that you can use the cloud provider services if that's what you want to use. But the DevSecOp tool chain, the runtime environment which turns out to be Kubernetes and how you control the Kubernetes environment, how do you manage and secure and connect all of these things. Those are the places where we are adding the value. And so really the VMware value proposition is you can build on the cloud of your choice but providing these consistent elements, number one, you can make better use of us, your scarce developer or operator resources and expertise. And number two, you can move faster. And number three, you can just spend less as a result of this. So that's really what we are trying to do. We are not... So I just wanted to clarify the word abstraction. In terms of where are we? We are still, I would say, in the early stages. So if you look at what customers are trying to do, they're trying to build these greenfield applications. And there is an entire ecosystem emerging around Kubernetes. There is still, Kubernetes is not a developer platform. The developer experience on top of Kubernetes is highly inconsistent. And so those are some of the areas where we are introducing new innovations with our Tanzu Application Platform. And then if you take enterprise applications, what does it take to have enterprise applications running all the time be entirely secure, et cetera. >> Well, look, the multi-cloud by default today are isolated clouds. They don't work together. Your data is siloed. It's locked up and it is expensive to move and make sense of it. So I think the word you and I were batting around before, this is an interconnected tissue. That's what the world needs. They need the clouds to work together as a single platform. That's the problem that we're trying to solve. And you saw it in some of our announcements here that we're starting to make steps on that journey to make multi-cloud work together much simpler. >> It's interesting, you mentioned the hyperscalers and all that CapEx investments. Why wouldn't you want to take advantage of a cloud and build on the CapEx and then ultimately have the solutions machine learning as one area. You see some specialization with the clouds. But you start to see the rise of superclouds, Dave calls them, and that's where you can innovate on a cloud then go to the multiple clouds. Snowflakes is one, we see a lot of examples of supercloud... >> Project Alpine was another one. I mean, it's early, but it's its clearly where you're going. The technology is just starting to come around. I mean it's real. >> Yeah. I mean, why wouldn't you want to take advantage of all of the cloud innovation out there? >> Is that something that's, that supercloud idea is a reality from a technologist perspective. >> I think it is. So for example Katie Gordon, which I believe you've interviewed earlier this week, was demonstrating the Kubernetes data mobility aspect which is another project. That's exactly part of the it's rationale, the rationale of customers being able to move some of their Kubernetes workloads to the cloud and back and between different clouds. Why are we doing? Because customers wants to have the ability to move between different cloud providers, using a common API that will be able to orchestrate all of those things with a self-service that may be offered via the APEX console itself. So it's all around enabling developers and meeting them where they are today and also meeting them into tomorrow's world where they actually may have changed their mind to do those things. So yes we are walking on all of those different aspects. >> Okay. Let's take a quick look at some of the ETR data. This is an X-Y graph. You've seen it a number of times on breaking analysis, it plots the net score or spending momentum on the Y-axis and overlap or pervasiveness in the ETR dataset on the X-axis, used to be called market share. I think that term was off putting to some people, but anyway it's an indicator of presence in the dataset. Now that red dotted line that's rarefied air where anything above that line is considered highly elevated. Now you can see we've plotted Azure and AWS in the upper right. GCP is in there and Kubernetes. We've done that as reference points. They're not necessarily building supercloud platforms. We'll see if they ever want to do so. And Kubernetes of course not a company, but we put 'em in there for context. And we've cherry picked a few players that we believe are building out or are important for supercloud build out. Let's start with Snowflake. We've talked a lot about this company. You can see they're highly elevated on the vertical axis. We see the data cloud as a supercloud in the making. You've got pure storage in there. They made the public, the early part of its supercloud journey at Accelerate 2019 when it unveiled a hybrid block storage service inside of AWS, it connects its On-Prem to AWS and creates that singular experience for pure customers. We see Hashi, HashiCorp as an enabling infrastructure, as code. So they're enabling infrastructure as code across different clouds and different locations. You see Nutanix. They're embarking on their multi-cloud strategy but it's doing so in a way that we think is supercloud, like now. Now Veeam, we were just at VeeamON. And this company has tied Dell for the number one revenue player in data protection. That's according to IDC. And we don't think it won't be long before it holds that position alone at the top as it's growing faster than in Dell in the space. We'll see, Dell is kind of waking up a little bit and putting more resource on that. But Veeam, they're a pure play vendor in data protection. And you heard their CTO, Danny Allan's view on Supercloud, they're doing it today. And we heard extensive comments as well from Dell that's clearly where they're headed, project Alpine was an early example from Dell technologies world of Supercloud in our view. And HPE with GreenLake. Finally beginning to talk about that cross cloud experience. I think it in initially HPE has been more focused on the private cloud, we'll continue to probe. We'll be at HPE discover later on the spring, actually end of June. And we'll continue to probe to see what HPE is doing specifically with GreenLake. Now, finally, Cisco, we put them on the chart. We don't have direct quotes from recent shows and events but this data really shows you the size of Cisco's footprint within the ETR data set that's on the X-axis. Now the cut of this ETR data includes all sectors across the ETR taxonomy which is not something that we commonly show but you can see the magnitude of Cisco's presence. It's impressive. Now, they had better, Cisco that is, had better be building out a supercloud in our view or they're going to be left behind. And I'm quite certain that they're actually going to do so. So we have a lot of evidence that we're putting forth here and seeing in the marketplace what we said last year, the ecosystem is take taking shape, supercloud is forming and becoming a thing. And really in our view, is the future of cloud. But there are always risks to these predictive scenarios and we want to acknowledge those. So first, look, we could end up with a bunch of bespoke superclouds. Now one supercloud is better than three separate cloud native services that do fundamentally the same thing from the same vendor. One for AWS, one for GCP and one for Azure. So maybe that's not all that bad. But to point number two, we hope there evolves a set of open standards for self-service infrastructure, federated governance, and data sharing that will evolve as a horizontal layer versus a set of proprietary vendor specific tools. Now, maybe a company like Veeam will provide that as a data management layer or some of Veeam's competitors or maybe it'll emerge again as open source. As well, and this next point, we see the potential for edge disruptions, changing the economics of the data center. Edge in fact could evolve on its own, independent of the cloud. In fact, David Floria sees the edge somewhat differently from Danny Allan. Floria says he sees a requirement for distributed stateful environments that are ephemeral where recovery is built in. And I said, David, stateful? Ephemeral? Stateful ephemeral? Isn't that an oxymoron? And he responded that, look, if it's not ephemeral the costs are going to be prohibitive. He said the biggest mistake the companies could make is thinking that the edge is simply an extension of their current cloud strategies. We're seeing that a lot. Dell largely talks about the edge as retail. Now, and Telco is a little bit different, but back to Floria's comments, he feels companies have to completely reimagine an integrated file and recovery system which is much more data efficient. And he believes that the technology will evolve with massive volumes and eventually seep into enterprise cloud and distributed data centers with better economics. In other words, as David Michelle recently wrote, we're about 15 years into the most recent cloud cycle and history shows that every 15 years or so, something new comes along that is a blind spot and highly disruptive to existing leaders. So number four here is really important. Remember, in 2007 before AWS introduced the modern cloud, IBM outpost, sorry, IBM outspent Amazon and Google and RND and CapEx and was really comparable to Microsoft. But instead of inventing cloud, IBM spent hundreds of billions of dollars on stock buybacks and dividends. And so our view is that innovation rewards leaders. And while it's not without risks, it's what powers the technology industry it always has and likely always will. So we'll be watching that very closely, how companies choose to spend their free cash flow. Okay. That's it for now. Thanks for watching this episode of The Cube Insights, powered by ETR. Thanks to Stephanie Chan who does some of the background research? Alex Morrison is on production and is going to compile all this stuff. Thank you, Alex. We're all remote this week. Kristen Nicole and Cheryl Knight do Cube distribution and social distribution and get the word out, so thank you. Robert Hof is our editor in chief. Don't forget the checkout etr.ai for all the survey action. Remember I publish each week on wikibon.com and siliconangle.com and you can check out all the breaking analysis podcasts. All you can do is search breaking analysis podcast so you can pop in the headphones and listen while you're on a walk. You can email me at david.vellante@siliconangle.com. If you want to get in touch or DM me at DVellante, you can always hit me up into a comment on our LinkedIn posts. This is Dave Vellante. Thank you for watching this episode of break analysis, stay safe, be well and we'll see you next time. (upbeat music)

(bright upbeat music) >> Narrator: From around the globe, it's theCUBE! With digital coverage of AnsibleFest 2020 brought to you by Red Hat. >> Welcome back to the cube virtual coverage of AnsibleFest 2020. Virtual, not face to face this year, obviously because of COVID, and all events are going virtual. This is theCUBE virtual. I'm excited to have on CUBE, alumni Mandy Whaley, who's the Senior Director of DevNet & Cisco Certifications. Mandy, great to see you, >> Thank you. >> virtually. >> Great to see you too. It's exciting to be here with theCUBE again, and especially here at AnsibleFest. >> Last time we saw each other at a physical event was Barcelona in January, as the world was taking a turn. I see a lot of people online, learning has been great. What would DevOpsSec things going on, we'll get to that in a second, but I want to first talk about you and your role in Cisco and Red Hat Ansible. You're a trusted adviser. What are customers experiencing? And what are their expectations around automation? The big theme of this conference? >> Absolutely. So, in terms of the community that I work with at Cisco, it's our DevNet, and our learning community, all of our Cisco certified engineers, as well as our DevNet developer audience. And so, automation is at the core of what they're working on. And we've seen even the move to more work from home, all the virtual things that we're dealing with, that's even more emphasis on companies needing to do automation and needing to have the skills to build that within their teams. So we're really seeing that everyone has expectations around platforms being able to have open API's, integrate with tool sets, having choice in how they integrate things into their different workflows that they may already be using. And then we're seeing a big demand for people wanting to skill up and learn about automation, learn about Ansible, learn about Python. Our new DevNet certifications, they actually cover Cisco platforms as well as industry standard topics like Python and Ansible. And we've seen really great feedback from the community around loving that combination of getting to work really deeply with our Cisco technologies, as well as learning things like Ansible and Python. We had a special special challenge when we launched the DevNet Certifications, for the first 500 people to earn that certification. And we were really excited to see the community achieve that within the first 16 days. So I just think that shows how important automation is to our community right now. >> What do you hear from customers around this certification opportunity around Ansible and Python? Can you give an example? >> So what we're hearing from companies and customers and individual developers is that they're having to deal with more scale, they are seeing more opportunity to handle consistent policy to make sure configurations are consistent. All of these things are really important right now with the scale they're trying to handle. And so, they're looking for ways that they can quickly add these skills to their tool set. And since we are working from home, not traveling as much, everyone's schedule is a little bit different. There is extra opportunity for teams to dig in and do some learning. So, leaders, IT leaders are looking for how do they work with their teams to go after these skills and add them into their way that they approach problems, the way solve problems. And then individuals are looking for how they add them to open up new job roles and new opportunities for themselves. >> Well, I want to give you a shout out and props and kudos for the work you guys have done over at DevNet. We've watched the evolution. Obviously you guys have transformed the learning but also, the API enabled products and economy that Cisco is driving with the SaaS. This is consistent with Ansible's success in the cloud and on premise with private cloud. Again, Cloud, Ops, Sec, everything's kind of happening. Tell us the importance of automation within the Cisco products and how Ansible fits in. >> Absolutely. So, like I said earlier, having this open API's really, across the whole Cisco portfolio, and up and down the stack at the device level, at the controller level. That's part of our strategy. It's important to our customers, it's important to Cisco. We actually have a developer event, DevNet Create, coming up. And, Chuck Robbins, will be talking about some of that importance of developers and automation in the Cisco strategy at DevNet Create. So maybe you can tune in and see some of that as well. We have been working with Ansible since early on in terms of how we bring Cisco technologies together with Ansible. And as Ansible moved to the new collections, we stepped into that very early, we knew it was important to have a seamless transition around that for our community. And that's been a big part of our work this year in terms of how we've been working with Ansible and getting ready for the the new collection structure. >> The people who are watching and know theCUBE know that, or maybe new to theCUBE and our work, know that I've been a cheerleader for Cloud Native, but now it's actually happening, Mandy, we've been cheering it on and saying it's going to happen. Cloud Native and the modern app focus, again, this is some of the narrative on the inside, the industry is now mainstream. This is really a big deal because it's now DevOps and sec, so all that's happening mainstream, the rise of Kubernetes. Everything is on the front burner when it comes to Cloud Native. So I got to ask you, how do the developers here at AnsibleFest get to learn more about Cisco? Because now you're bringing everything together. The automation up and down the stack from modern apps down to the plumbing network's certainly super important from edge, 5G's right around the corner. This is a business enterprise opportunity. How can developers at AnsibleFest learn more about Cisco? >> Fantastic, yes. The one place to learn about all of our Cisco platforms, and like you said, how all these things, Cloud Native, DevOps, DevsSecOps, how all of these things are coming together. You can learn about it at developer.cisco.com. It's where all of our developer resources are, it's where you can find, if you're wanting to get started with Cisco products and Ansible. We have learning labs, engineer to engineer tutorials, videos, sample code, all kinds of the resources to help people get started on that journey. And the other thing we're really seeing is, like you said, this coming together and the real move in enterprises towards DevOps is creating all of these new job roles around DevSecOps, and network automation engineer, and web scale developer. And one of the things we're seeing is people are needing to add skills to their current skill set, mix and match, bringing hardware and software together, cloud and networking skills and development skills to really meet the need for these new job roles, which is being driven by the business demands that we're facing. And that's one of the things that we're working really hard on in the DevNet and Cisco community right now. >> Can't go wrong by continuing your career at Cisco and certainly configuration management software comes together as awesome. So, thanks for sharing that. One of the topics at AnsibleFest 2020 virtual this year is the theme is kind of three things, as we heard on some of the interviews, collections, collections collections. This notion of Ansible (Mandy laughs) automation platform has a numerous Cisco certified collections. Can you share some insight and anecdotes from your community on, from the DevNet users on what they're dealing with day to day around automation and how these collections and the certified collections fits in? >> Yeah, absolutely. So, part of my team has been working with our community, with Ansible, to bring the Cisco Ansible collections together. And it's been a big part of our work throughout the year. And we've seen tremendous use by the community. So we've been following the downloads of people downloading connections and using them is growing rapidly. We are really excited to see the use of the community and then the community interest support. And then we're doing our best to make sure that we have playbooks in our DevNet code exchange, so people can go in and find them. That we're helping people understand collections and how all that fits together in the current Ansible structure. And we've just seen tremendous interesting response from the community on that. >> How does this tie into security automation? Another theme that comes up, you talk about network, you got cloud, you got security, intrusion, detection, prevention, these are all useful things to DevNet users, how does that all fit in? >> Security is one of the areas that I'm consistently hearing about from our community and customers. I think people are really looking for how they can deal with increased scale, how they can increase the scale that they're able to deal with and keep it secure. We're seeing people want to take quick action, when a malicious activity occurs, or even something like ensuring that policy is consistent across a range of security endpoints. And these are all places where automation can really help out, and help teams manage the scale that they're having to deal with. So, one of the things we've been working with is showing some learning labs on DevNet, that combine using Ansible with our security products to help people tackle some of those use cases. We have an area called automation exchange. And it's all about these automation use cases, and giving you the sample code to get started on tackling some of these harder use cases. That's where we have seen a lot of interest around security. >> On a broader scale, could you tell us where you see NetOps going? I mean, it's a big theme, Susie Wee, April, yourself. We've all chatted about this in the past NetOps, or DevOps for networking ops for basically DevOps for networking, basically. >> Yes. >> Where's this... Where's it going in the future? Where are we on the progress? Certainly there's been great evolution. How is DevNet evolving to push this mission forward? >> So, one of the things that we talk with customers a lot about when they are moving down this pathway to bringing DevOps to the way that they run their network is we talk about a walk, run, fly progression. And walk is where there, I use cases where maybe you are only doing read-only type things, and you're gathering insight, you're gathering information to help with troubleshooting, you're gathering information that maybe gets packaged up into a ticket that then an engineer takes action on. And this is a great place where a lot of organizations can start. If they are learning these skills, building these practices, they don't have to worry about it, making changes but they get a lot of the benefit of the automation. So, we're recommending that to at least two companies who are getting started, teams that are getting started, as a place to start their automation journey. And then really moving through that progression of next, taking some automated action, all the way to that full DevOps, lifecycle and workflow. And we're seeing companies move through that progression as their teams also move through that progression. >> Just as a side note, one of the things we've been riffing on lately around the Cloud Native, as you know now, it's mainstream as we just talked about, is that the integrations are a big part of it. So, you could have an environment that has a little bit of that, a little bit of this. A lot of integrations because of API's, and also microservices, you get Kubernetes around to tie it on, glue it all together. You got DevNet Create coming up, and you guys always have a great DevNet Zone at your events. It's a real learning environment. Talk of Ansible developers in the community out there and how you guys work together for these classes, because you guys have a lot of learning, is like a cross section of the community that work together, some don't some do. The Cloud Native really enables the integrations to happen quicker. Can you just share what's going on at DevNet Create, and your world? >> Absolutely. So, and it's great because, John, you were at our first DevNet Create years ago when we started it. So it's really exciting. This is our first virtual DevNet Create, that's October 13th. And we had planned it to be an in person event in March when the pandemic hit the US, and so we had to re-plan, and regroup and bring it to a virtual audience this fall. And it's actually been great with our virtual events, we've been able to see how there's many more people who can participate, who can learn who can be a part of that community, because it's not only limited to the people who can be there in person. So we're actually really excited about that virtual part of it. And DevNet Create is the event where we have speakers from all over our community, from companies, from partners, from community groups, and all kinds of technologies, like you said, it's a great place to look at the integrations. So you'll find talks on Ansible, you'll find talks on Kubernetes, you'll find talks on IoT, you'll find talks on mashing up different API's to go after use cases. And it's really about that strength of the community speakers that brings a lot of excellent content into DevNet Create, and we're so thankful for them, and the way that our community likes to, step up and share and help each other. >> Well, yes, we were there for the first one we will still be there with you. But the question that comes up, and I'd like you to just quickly take a minute to clarify the difference between DevNet and DevNet Create, cause there is a nuance here, it's important. Take a minute to explain DevNet and DevNet Create, and the objective of the two. >> Absolutely. So DevNet are DevNet Zone Event, which happen typically in our Cisco lives, they have more of a focus on our more network engineer community who's spanning into programmability, DevOps, moving that direction because it happens within a Cisco live event, normally, the DevNet Zone. DevNet Create is our conference that started to focus on the application developer, the cloud developer, and how they are starting to tackle some of these hybrid use cases. And so DevNet Create is the place where that really comes together. And when, last year, Susie and I are on stage and we really wanted to know kind of what aspects people were bringing to the conference. And we asked the community, how many people are really focused on application development in their day job? That's their main focus. How many people are more on the Ops side? Infrastructure developer, DevOps engineer? And then how many people are really working to bridge that? And it was one third, one third, one third, in terms of the people at Create that year. And that was just really great to see. And to me, I think really shows the community that's building around around DevNet Create. >> And if you look at the trends too, the discussions are about modern applications, and certainly with COVID, people are looking at this and saying, "Hey, it's an opportunity to use this pandemic "and look at the opportunity to be very agile, "and create these modern apps which require programmability, "which require "some instructions away >> That's right. >> "from the complexity, all the way down to the network." I mean, it really gives great vision. >> All the way to the network. Yeah, and even things like, using things with Meraki cameras with using things like our collaboration products, to build those use cases that are really helping out in a lot of the new challenges that we're facing. So that's all what you can find at DevNet Create. It's one of my favorite events because it does cover such a range of topics. >> I'm in my first interview at one of your first event with Todd Nightingale. He is doing the Meraki thing. Now he's running a lot of the big part of the business there. But it really was a great vision. You guys really nailed it. Hats off to you guys. Kudos props. Congratulations and stay safe. And we'll see you at your event. Thanks for joining me. >> Thank you so much, and thanks to AnsibleFest. >> Okay, that's theCUBE virtual coverage. I'm John Furrier, your host with AnsibleFest 2020. Thanks for watching. (bright upbeat music)