from around the globe it's thecube with coverage of kubecon and cloudnativecon north america 2020 virtual brought to you by red hat the cloud native computing foundation and ecosystem partners and welcome back to thecube's coverage of kubecon cloudnativecon 2020 virtual i'm john furrier your host of thecube we are thecube virtual normally we're in person this year with the pandemic we have to do the remote interviews and uh wish we could be there but it's gonna be a great conference a lot of learning a lot of great conversations a lot of great community a lot of great companies who are riding the cloud weight native wave and doing it right one company pleased to have the gm here on from commvault ventures metallic io monognaire gm metallic dot io commvault ventures is it a spin out no it's great to see you first welcome welcome back to thecube great to see you thank you thank you good to be here good good to be back with you guys so you're a cube alumni i've been on many times you're now heading up this venture um metallic io which is doing extremely well good you know case of great timing and good good savvy business planning and strategic vision um and execution um but i want to just kind of get something straight real quick is it a spin out of com commvault is it a separate company what's the relationship with metallic io and commvault yeah so it's set up as a you know as a complete startup um it's uh incubated and fully owned by commvault uh but you know we have our you know full full company just like running my separate startup you know metallic is set up as a startup and uh you know it's uh some people joke right you know it's like one of those millennial kids you know i get to have a deep pocketed parent commvault and access to a lot of ip and great customers at the same time be a startup and drive fast in this cloud native sasquatch yeah we also have the microsoft you know deep partnership so that's the other angle here with metallic having a deep strategic partnership with microsoft you know the theme this year and all the shows especially kubecon in particular is modern application but speed speed and relevance right that's critical congratulations good to have a boss sanjay over there looking over your shoulder but you got freedom you're running hard as a startup and you got a good track record take me through real quick give a quick business update before we get into some of the container conversations you guys really caught the tailwind of covid kind of like the zoom caught a big tail because everyone's doing video now cloud endpoint protection i mean come on everyone's at home everyone's at the edge edge point protection i mean tell us give some quick updates absolutely you know a year plus since we launched it um i think initially the company was thinking metallic would be really good fit for the mid market and maybe the low end enterprise was always built to be enterprise grade and you know come march all of us get you know stunned by what's happening in the world we decided to make our endpoint offer available free for our customers jointly with microsoft and all it was not mid market i mean i had fortune 15 companies signing up we had the biggest of the big several of them have now become you know customers of our spa paying customers of us one of the world's largest insurance company came in that way and signed up for all their users to end up being paying customers and you think about like protecting endpoints right that's uh you know all the bad things kind of happened in droves so you have covet happening people going remote and ransomware and cyber attacks taking off 400 as the fbi is saying and that kind of becomes a very high risk point so to be able to have not just data protection but ransomware detection on those edge devices i think companies are really starting to see the the value of uh having that kind of a you know data protection as a service model well congratulations on on the timing on that i'll say there's no such thing as luck as preparation meets opportunity as the expression goes but i get why it makes sense with the pandemic but can you explain why cloud-based container protection is good for customers beyond the obvious you just mentioned what else is there what are some of the downs down downstream benefits as people come out of you know it uh you know the the uh things that people are accelerating right it's uh okay we've got to take care of the basics we talked about endpoint then it's cloud adoption um productivity suites like o365 with teams you know took off as you were talking about zoom and how do you protect that you know how do you protect all that data being created now in a platform that uh you were not protecting so that was kind of that next immediate wave and now what we're seeing is the hybrid cloud adoption is taking off now containers in my mind are intricately linked with in this hybrid cloud journey right these are the apps that people build this is your sensitive most important ip and you know how as enterprises adopt containers it's one of the paths to the cloud and it is really the most recommended plan is you take microservices you re-platform re-architect use containers to deliver microservices and these are enterprise applications so they have state and so with stateful applications you know how do you make sure that you have a cloud-native data protection available for them the second issue is the developers who are adopting and deploying containers in production they don't want to be going out deploying software to protect you know these things they want a i just want an api a service call in the cloud and they should do what i you know i do like any other cloud native service so you know cloud native protection that we're delivering for containers with our announcement today for metallic is is huge in that it behaves like a native cloud service just like you know a developer wants an api call with a cloud target no setup nothing and it's up and running yeah i mean cloud native is clear this year at kubecon this is the tipping point of you know full mainstream adoption of kubernetes and microservices so that means it's going to be impacted right so that means you know we're all early adopters let's face it we're at a point now where it's it's gone beyond test and dev and cluster testing you know kubernetes has now reached a point where it's penetrating and proliferating rapidly so i got to ask you the announcements about metallic for kubernetes as part of the broader portfolio expansion explain how that fits in because you mentioned hybrid cloud you got um back up as a service you got recovery i mean the world's changed who would have thought everyone's gonna be working at home how do you back that up that's service disruption so you know non-disruptive operations always been kind of a cliche but now you got a complicated operation how does the kubernetes fit into the broader portfolio absolutely so so it is part of a three new announcements uh the new new solutions we're announcing today all connected to this hybrid journey and you think about that hybrid journey and part of what happens with hybrid you know got all these paths rewrite re-platform re-host and uh part you know you got this whole desegregation of data and compute also happening so our offerings are you know there's a metallic for virtual machines and kubernetes uh as a service uh we've got metallic for database uh delivered as a service and metallic for unstructured data file an object and all of those are key parts of a you know cloud native stack you'll have some you know rds some some you know azure managed sql some blob storage and we had to protect all those patterns in different ways at the same time virtual machines are not going away they're going to be there and you know a lot of people say that container is a new virtual machine so what we have done is we have introduced the vm and kubernetes module but anyone who buys that gets container protection for free so anyone who buys that for the next six months for the lifetime of the subscription they get unlimited kubernetes backup as a service uh for free the reason we're doing that is just we want to make sure especially our early adopters are taking full advantage and and they're not compromising on the data protection for this cloud native application as they think through this transition you know that's a good business model also i mean you're in the cloud right so this is leverage you've got some leverage there yeah that's the new freemium we'll give you a full protection you know what's the gimmick here there's no there's no trick you get it for free it's good because you're going to make money on other air again this is the whole benefit of the new kind of freemium sas you're in an enterprise model so yeah you take care of people you make it up on the critical infrastructure i get that is that kind of how it's working it's exactly you know what uh we're thinking you know look today um you know i saw saw some stats out there 75 percent of the people who are adopting containers are not yet thinking about you know data protection for containers has to be container optimized you can't just say okay you know the data is in the vm i'll just do a snapshot and it'll be fine now what about all of the container specific you know namespaces tags the config maps pod you cannot recover this cluster if you don't have a real container native solution and so that you know for part of the thought leadership and education process we said let's let's start by just making it available take all the excuses out and that really you know i think over time our customers are going to really benefit from our approach there well while i got you here i want to just grab you uh for a quick definition master class so we see b-a-a-s not to be confused with sas or p pass platform as a service b stands for backup as a service right everything's as a service these days that's what cloud's great for could you can you define what that is from with a cloud standpoint because i mean backup as a service it could mean many things but for as you guys are doing because you have success it's working what is baas that's as a what is backup as a service what is definition yeah so backup as a service in my mind and some people call it cloud native backup really includes delivering you know turnkey experience turnkey consumption model i should be able to go sign up like any other as a service free try it if i like it immediately do an online experience to you know acquire it and be up and running our design goal was first backup even for a complex enterprise workload should be less than 15 minutes from from transaction today we're able to do it in a matter of minutes all the way from acquisition to being up and running so i'd say that's part of the definition part of the definition is never having to maintain your backup software ever that's not your responsibility we take care of that it's always updated we're using the best of uh cloud you know capabilities to do sre ops and maintain that in a very scalable 24 7 way security of the service you know between us and all the security capabilities we provide ransomware detection and all that and building on top of azure's foundation of 3500 security engineers you know that's the key component you should not have to worry this is your data your most critical the last part is cloud adoption is complicated enough for customers they shouldn't have to worry about things like egress costs and you know am i going to get nickel and dime for the service over ages and so just price transparency is a big part that we have focused on so you know our customers are double 365 they don't have to ever pay for any storage unlimited storage no egress costs and the whole thing is a turnkey service so that's the kind in my mind that's backup as a service yeah and pay as you go it's classic and i love that love the the hidden cost thing you mentioned this demand obviously out there earlier in the interview what's driving the demand besides kovid what are some of the architectural shifts that you're seeing and does it have um the same characteristics in all geographies because remember you're talking cloud you're talking regions right so you know what's the driving the demand besides covid and what's the regional impact around the world no they were seeing a global impact uh you know we had a plan to have a multi-year global rollout plan and in the last six months we have now in 14 countries around the globe and that just maps to the interest uh you know we're we're in australia and new zealand where we just launched 10 european countries last month in the u.s canada of course and that global journey is what we're seeing with our customers so you know that the pain points you know the covet crisis the economic shift uh the need to be as a service those are the things that are really driving um we we talked about remote work we talked about teams adoption really driving o365 and people think oh 365 you know there's some you know folks who just think mailboxes but you know you've seen news stories out there with what happens with config changes to teams that just blows out all the all the chat sessions and so people understand the need for data protection there hybrid i.t containers rapid cloud adoption probably the biggest one is ransomware you know we launched this metallic cloud storage service that is an air gap ransomware cloud storage that can connect to any commvault customer they don't even have to be a metallic sas customer and that's had a you know on day two we had two and a half petabytes on up and running you know our first customer and it's just taken off so you know all of those are the trends that that are today driving uh you know customer adoption uh off uh you know of our solution uh along with everything else that customers are trying to do mineos i got to ask you a personal question you're the gm which basically means you're the ceo of the commvault startup but we'll call you a gm are you having fun well i'm having a lot of fun i mean this is uh probably the most fun i've had in a long time uh and look when you are doing things that are really impactful for me you know that's uh you know i'm sitting in my startup uh you know garage here in the bay area yeah and you know touching customers around the world we have a global team uh and it's it's been uh it's a challenging year right from a human uh perspective for for all the you know all of the folks who are impacted by this and our teams are part of that journey and so their personal lives that that are difficult but we're all you know working on this very very interesting and i think you know disruptive but impactful uh offering that we can see how it touches our customers wells and i think that's partly what's kept the team and all of us doing so yeah we're having a lot of fun well we're fellow travelers we're not on site anymore i mean we did an interview in 2015 you and i were talking with docker back in 25 years ago and you're still on point now you're on the wave you got to be mindful of the current situation around you and understand reality and it's a chance to do things differently from the customer you know backwards in not inside out so you know it's it's fun to have a new category but also it's it's a big wave you don't want to be as pat gelsinger said driftwood if you make the wrong move so well keep keep keep plugging you're on the right track thanks for coming on thank you john really appreciate the time maneuver gm of metallic dot io check it out it's a it's a separate company from commvault that funded it doing cloud as a service back backup as a service in the cloud very innovative very smart thanks for coming on my notes i'm john furrier with thecube virtual for kubecon cloudnativecon 2020. thanks for watching [Music] you

>> Voiceover: From around the globe, it's theCUBE, with coverage of Kubecon and CloudNativeCon, North America, 2020, virtual brought to you by Red Hat, the Cloud Native Computing Foundation and Ecosystem Partners. >> Welcome back to theCUBE's coverage, virtual coverage of Kubecon and CloudNativeCon 2020. We're not in person this year, normally we're there in person. We have to do remote because of the pandemic, but hey, it opens up more conversations. And this is theCUBE virtual. I'm John Furrier, your host. And you'll see a lot of interviews. We've got some great guests, Talking to the leaders, the developers, the end users, as well as the vendors with the CNCF, we got two great guests, Priyanka Sharma, the General Manager of the CNCF, great to see you and Stephen Augustus OSS Engineer at VMware. He's also the KubeCon co-chair back on the cube. Thanks for coming on folks. I appreciate it. >> Thank you for having us. So, thanks for coming on, actually, remote and virtual. We're doing a lot of interviews, we're getting some perspectives, people are chatting in Slack. It's still got the hallway vibe feel, a lot of talks, a lot of action, keynotes happening, but I think the big story for me, and I would like to talk about, I want to get your perspective is this new working group that's out there. So I know there's some news around it. Could you take a minute to explain kind of what this is all about? >> Sure. I'll give a little bit of context for those who may have missed my keynote which... very bad. (Priyanka laughs) As I announced, I'm so proud to be working with the likes of Stephen Augustus here, and a bunch of other folks from different companies, different open source projects, et cetera, to bring inclusive naming to code. I think it's been a forever issue. Quite frankly. We've had many problematic terms in software out there. The most obvious one being master-slave. That really shouldn't be there. That have no place in an inclusive world, inclusive software, inclusive community with the help of amazing people like Stephen, folks from IBM, Red Hat, and many, many others. We came together because while there's a lot of positive enthusiasm and excitement for people to make the changes that are necessary to make the community welcome for all, there's a lot of different work streams happening. And we really wanted to make sure there is a centralized place for guidelines and discussion for everybody in a very non...pan-organizational kind of way. And so that's the working group that John is talking about. With that said, Stephen, I think you can do the best justice to speak to the overall initiative. >> Yeah, absolutely. So I think that's to Priyanka's point, there are lots of people who are interested in this work and again, lots of work where this is already happening, which is very exciting to say, but as any good engineer, I think that's it's important to not duplicate your work. It's important to recognize the efforts that are happening elsewhere and work towards bringing people together. So part of this is providing, being able to provide a forum for discussion for a variety of companies, for a variety of associations that... and foundations that are involved in inclusive naming efforts. And then to also provide a framework for walking people through how we evaluate language and how we make these kinds of changes. As an example, for Kubernetes, we started off the Kubernetes working group naming and the hope for the working group naming was that it was going to evolve into hopefully an effort like this, where we could bring a lot of people on and not just talk about Kubernetes. So since we formed that back in, I want to say, June-ish, we've done some work on about of providing a language evaluation framework, providing templates for recommendations, providing a workflow for moving from just a suggestion into kind of actuating those ideas right and removing that language where it gets tricky and code is thinking about, thinking about, say a Kubernetes API. And in fact that we have API deprecation policies. And that's something that we have to if offensive language is in one of our APIs, we have to work through our deprecation policy to get that done. So lots of moving parts, I'm very excited about the overall effort. >> Yeah, I mean, your mind can explode if you just think about all the complications involved, but I think this is super important. I think the world has voted on this, I think it's pretty obvious and Priyanka, you hit some of the key top-line points, inclusive software. This is kind of the high order bit, but when you get down to it, it's hard as hell to do, because if you want to get ne new namings and/or changing namings accepted by the community and code owners, you're dealing with two things, a polarizing environment around the world today, and two, the hassles involved, which includes duplicate efforts. So you've got kind of a juggling act going on between two forces. So it's a hard problem. So how are you tackling this? Because it's certainly the right thing to do. There's no debate there. How do you make it happen? How do you go in without kind of blowing things up, if you will? And do it in a way that's elegant and clean and accept it. 'Cause that's the... end of the day, it's acceptance and putting it code owners. >> Absolutely. I think so, as you said, we live in a polarizing environment right now. Most of us here though know that this is the right thing to do. Team CloudNative is for everyone. And that is the biggest takeaway I hope people get from our work in this initiative. Open source belongs to everybody and it was built for the problems of today. That's why I've been working on this. Now, when it goes into actual execution, as you said, there are many moving parts, Stephen and the Kubernetes working group, is our shining example and a really good blueprint for many folks to utilize. In addition to that, we have to bring in diverse organizations. It's not just open source projects. It's not just companies. It's also standards organizations. It's also folks who think about language in books, who have literally done PhDs in this subject. And then there are folks who are really struggling through making the changes today and tomorrow and giving them hope and excitement. So that at the end of this journey, not only do you know you've done the right thing, but you'd be recognized for it. And more people will be encouraged by your own experience. So we and the LF have been thinking at it from a holistic perspective, let's bring in the standards bodies, let's bring in the vendors, let's bring in the open source projects, give them guidelines and blueprints that we are lucky that our projects are able to generate, combine it with learnings from other people, because many people are doing great work so that there is one cohesive place where people can go and learn from each other. Eventually, what we hope to do is also have like a recognition program so that it's like, hey, this open source project did this. They are now certified X or there's like an awards program. They're still figuring that piece out, but more to come on that space. That's my part. But Stephen can tell you about all the heavy lifting that they've been doing. >> Before we get to Steve, I just want to say congratulations to you. That's great leadership. And I think you're taking a pragmatic approach and you putting the stake in the ground. And that's the number one thing, and I want to take my hat off to you guys and Priyanka, thank you for that leadership. All right, Stephen, let's talk about how this gets done because you guys open sources is what it's all about is about the people, it's about building on the successes of others, standing on the shoulders of others, you guys are used to sitting in rooms now virtually and squabbling over things like, code reviews and you got governing bodies. This is not a new thing in collaboration. So this is also a collaboration test. What are you seeing as the playbook to get this going? Can you share your insights into what the Kubernetes group's doing and how you see this. What are the few first few steps you see happening? So people can either understand it, understand the context and get involved? >> So I think it comes down to a lot of it is scope, right? So as a new contributor, as a current contributor, maybe you are one of those language experts, that is interested in getting involved as a co-chair myself for SIG Release. A lot of the things that we do, we have to consider scope. If we make this change, how is it affecting an end user? And maybe you work in contributor experience. Maybe you work in release, maybe you work in architecture. But you may not have the entire scope that you need to make a change. So I think that first it's amazing to see all of the thought that has gone through making certain changes, like discussing master and slave, discussing how we name control plane members, doing the... having the discussion around a whitelist and blacklist. What's hard about it is, is when people start making those changes. We've already seen several instances of an invigorated contributor, and maybe the new contributor coming in and starting to kind of like search and replace words. And it... I wish it was that simple, it's a discussion that has to be heard, you need buy-in from the code owners, if it's an API that you're touching, it's a conversation that you need to have with the SIG Architecture, as well as say SIG Docs. If it's something that's happening in Release, then it's a easier 'cause you can come and talk to me, but, overall I think it's getting people to the point where they can clearly understand how a change affects the community. So we kind of in this language evaluation framework, we have this idea of like first, second and third order concerns. And as you go through those concerns, there are like diminishing impacts of potential harm that a piece of language might be causing to people. So first order concerns are the ones that we want to eliminate immediately. And the ones that we commonly hear this discussion framed around. So master-slave and whitelist, blacklist. So those are ones that we know that are kind of like on the track to be removed. The next portion of that it's kind of like understanding what it means to provide a recommendation and who actually approves the recommendation. Because this group is, we have several language aficionados in this group, but we are by now means experts. And we also want to make sure that we do not make decisions entirely for the community. So, discussing that workflow from a turning a recommendation into actuating a solution for that is something that we would also do with the steering committee. So Kubernetes kind of like top governing body. Making sure that the decision is made from the top level and kind of filtered out to all of the places where people may own code or documentation around it is I think is really the biggest thing. And having a framework to make it easy to make, do those evaluations, is what we've been craving and now have. >> Well, congratulations. That's awesome. I think it's always... it's easier said than done. I mean, it's a system when you have systems and code, it's like, there's always consequences in systems architecture, you know that you do in large scales OSS. You guys know what that means. And I think the low hanging fruit, obviously master, slave, blacklist, whitelist, that's just got to get done. I mean, to me, if that just doesn't get done, that's just like a stake in the ground that must happen. But I think this idea of it takes a village, kind of is a play here. People just buy into it. That so it's a little bit of a PR thing going on too, for get buy-in, this is again a classic, getting people on board, Priyanka, isn't it? It's the obvious and then there's like, okay, let's just do this. And then what's the framework? What's the process? What's the scope? >> Yeah, absolutely agree. And many people are midway through the journey. That's one of the big challenges. Some people are on different phases of the journey, and that was one of the big reasons we started this working group, because we want to be able to provide a place of conversation for people at different stages. So we get align now rather than a year later, where everybody has their own terms as replacements and nothing works. And maybe the downstream projects that are affected, like who knows, right? It can go pretty bad. And it's very complex and it's large-scale opensource or coasters, anywhere, large software. And so because team CloudNative belongs to everyone because open source belongs to everyone. We got up, get people on the same page. For those who are eager to learn more, as I said in my keynote, please do join the two sessions that we have planned. One is going to happen, which is about inclusive naming in general, it's an hour and a half session happening on Thursday. I'm pretty sure. And there we will talk about all the various artists who are involved. Everybody will have a seat at the table and we'll have documentation and a presentation to share on how we recommend the all move, move together as an ecosystem, and then second is a presentation by Celeste in the Kubernetes working group about how Kubernetes specifically has done naming. And I feel like Stephen, you and your peers have done such amazing work that many can benefit from it. >> Well, I think engineers, you got two things going to work in for you, which is one, it's a mission. And that's... There's certainly societal benefits for this code, code is for the people. Love that, that's always been the marching orders, but also engineers are efficient. If you have duplicate efforts. I mean, it's like you think about people just doing it on their own, why not do it now, do it together, more efficient, fixing bugs over stuff, you could have solved now. I mean, this is a huge issue. So totally believe it. I know we got to go, but I want to get the news and Priyanka, you guys had some new stuff coming out from the CNCF, new things, survey, certifications, all kinds of new reports. Give us the quick highlights on the news. >> Yes, absolutely. So much news. So many talking points. Well, and that's a good thing, why? Because the CloudNative Ecosystem is thriving. There is so many people doing so much awesome stuff that I have a lot to share with you. And what does that tell us about our spirit? It tells you about the spirit of resilience. You heard about that briefly in the conversation we just had with Stephen about our working group to align various parties and initiatives together, to bring inclusive naming to code. It's about resilience because we did not get demoralized. We did not say, "oh, it's a pandemic. I can't meet anyone. So this isn't happening." No, we kept going. And that is happening in inclusive naming that is happening in the CloudNative series we're doing, that's happening in the new members that are joining, as you may have seen Volcano Engine just joined as platinum member and that's super exciting. They come from China. They're part of the larger organization that builds Tik Tok, which is pretty cool as a frequent bruiser I can say that, in addition, on a more serious note, security is really key and as I was talking to someone just minutes ago, security is not something that's a fad. Security is something that as we keep innovating, as cloud native keeps being the ground zero, for all future innovation, it keeps evolving. The problems keep getting more complex and we have to keep solving them. So in that spirit, we in CNCF see it as our job, our duty, to enable the ecosystem to be better conversant in the security needs of our code. So to that end, we are launching the CKS program, which is a certification for our Kubernetes security specialist. And it's been in the works for awhile as many of you may know, and today we are able to accept registrations. So that's a really exciting piece of news, I recommend you go ahead and do that as part of the KubeCon registration folks have a discount to get started, and I think they should do it now because as I said, the security problems keep getting worse, keep getting more complicated. And this is a great baseline for folks to start when they are thinking about this. it's also a great boon for any company out there, whether they're end users, vendors, it's all sometimes a blurry line between the two, which is all healthy. Everybody needs developers who are security conversant I would say, and this certification help you helps you achieve that. So send all of your people to go take it. So that's sort of the announcements. Then other things I would like to share are as you go, sorry, were you saying something? >> No. Go ahead. >> No, as you know, we talked about the whole thing of team CloudNative is for everyone. Open source is for everyone And I'm really proud that CNCF has offered over 1000 diversity scholarships since 2016 to traditionally under-representing our marginalized groups. And I think that is so nice, and, but just the very, very beginning. As we grow into 2021, you will see more and more of these initiatives. Every member I talked to was so excited that we put our money where our mouth is, and we support people with scholarships, mentorships, and this is only going to grow. And it just so like at almost 17%, the CNCF mentors in our program are women. So for folks who are looking for that inspiration, for folks who want to see someone who looks like them in these places, they have more diverse people to look up to. And so overall, I think our DEI focus is something I'm very proud of and something you may hear about in other news items. And then finally, I would like to say is that CloudNative continues to grow. The cloud native wave is strong. The 2.0 for team CloudNative is going very well. For the CloudNative annual survey, 2020, we found an astonishing number of places where CloudNative technologies are in production. You heard some stories that I told in my keynote of people using multiple CNCF projects together. And these are amazing and users who have this running in production. So our ecosystem has matured. And today I can tell you that Kubernetes is used in production, by at about 83% of the places out there. And this is up by 5% from 78% last year. And just so much strength in this ecosystem. I mean, now at 92% of people are using containers. So at this point we are ubiquitous. And as you've heard from us in various times, our 70 plus project portfolio shows that we are the ground zero of innovation in cloud native. So if you asked me to summarize the news, it's number one, team CloudNative and open source is for everyone. Number two, we take pride in our diversity and over 1000 scholarships have been given out since 2016 to recipients from underrepresented groups. Number three, this is the home base for innovation with 83% of folks using Kubernetes in production and 70 plus projects that deliver a wide variety of support to enterprises as they modernize their software and utilize containers. >> Awesome. That was a great summary. First of all, you're a great host. You should be hosting theCUBE with us. Great keynote, love the virtual events that you guys have been doing, love the innovation. I think I would just say just from my perspective and being from there from the beginning is it's always been inclusive and the experience of the events and the community have been top-notch. People squabble, people talk, people have conversations, but at the end of the day, it is a great community and it's fun, memorable, and people are accepting, it's a great job. Stephen, good job as co-chair this year. Well done. Congratulations. >> Thank you very much. >> Okay. Thanks for coming on, I appreciate it. >> Take it easy. >> Okay, this is theCUBE virtual, we wish we were there in person, but we're not, we're remote. This is the virtual Cube. I'm John Furrier, your host. Thanks for watching. (upbeat music)

>> Live from Orlando, Florida, it's The CUBE, covering Cisco Live 2018 brought to you by Cisco, Netapp, and the CUBE's ecosystem partners. >> Hello everyone, welcome back. This is the CUBE live in Orlando for Cisco Live 2018, exclusive coverage, I'm John Furrier, cohost of the CUBE. Stu Miniman all week for three days and we have Dave Alante flying in as well, cohost for our kickoff of day two of our three days of coverage, great Dave, good to see you Stu. Good morning, so I think the big news obviously day one in the books. Cisco Live pumping on all cylinders. The parties, we saw great concert last night at the Cohesity party celebrating their 250 million in funding, but the real big news here is Cisco's moving up the stack and the business performance. Dave, you had a chance to scour the landscape last night and yesterday, what did you find out? What's going on with Cisco's business? >> Well the business wise, I mean, this company is actually doing quite well. It's a large company, 50 billion dollars, they're growing at four percent. You don't usually see growth, we've seen how many quarters in a row as IBM, you know, revenues declined. Cisco's reversed that trend and is growing. The other thing about Cisco is it brought about 60 billion dollars from overseas on the tax holiday, which is just amazing. The company is trying to shift its model, more toward a cloud-like model. Stu, you've made the point many times Cisco, like Dell, doesn't have a cloud. So they've got to create a cloud-like model, they've got to go multi-cloud, they've got to be an arms dealer for the cloud. So as a company that's 50 billion dollars, a 200 billion dollar plus market value, which is down from where they were in the halcyon days but still it's a 4X revenue multiple and they throw off over $10 billion dollars in free cash flow a year, so this company's very, very strong and John, we were talking last night about the angle and security and basically a programmable network infrastructure. To me, the big trend is it's all about the data. As the data explodes, the network gets a lot of pressure. >> You know, Stu, I want to get your thoughts on this because we talked on security last night. Talk about companies that have to pivot. Cisco is not pivoting in any capacity. They are dealing with networks that are running the internet, right? So Chuck Robbins just said, "Look it, "we have done a lot of great things" but they're dealing with so much security threats. It's encrypted traffic, they are dealing with a ton of activity so the relevance of Cisco is on an all time high. The opportunity is to take that relevance and build on top of it, and so, we're looking for some signals, Stu. What do you when you squint through the noise and look at Cisco's relevance, obviously you see they run networks. You're moving up the stack with Kubernetes and containers and DevNet's been a great indicator there's a rise of the new normal, but they gotta actually put it together, they got a community. Where is the change happening, Stu, in your opinion? >> Yes, so John, first of all I look at, we've been tracking Cisco's moves in open source for many years. Dave Wright, Lou Tucker, folks we've had on the CUBE. They're very involved in open stack, they're deeply involved, Kubernetes, Ishdio, Diane Greene on stage. So there was that seed of growth and change, but it didn't really push far enough. Where the critique I've had for Cisco and many of the other big legacy companies, is they haven't really embraced cloud as fast as they could. It's good to see where Cisco is and where they're trying to bring their ecosystem. The exciting stuff has been right here, in the DevNet zone. How many events do we go to and companies we talk to? "Oh we need to be relevant to all "these developers out there," well, Susie and her team here, they've got a platform, they've got 500 thousand developers on it. John, you and I interviewed one little startup's netnology. A buddy of mine, actually, Jason Ellerman, worked for this other company called Network to Code. They've got this whole little incubator section here in the DevNet zone. These are hardcore networking people helping to bridge that gap between the network and the developer world. It's open APIs, it's all the things we've been talking about and that really does set the stage for Cisco to help, not only itself, but it's very large channel and partner ecosystem move further into this new, cloud native world. >> I want to get your thoughts real quick. I know we've got to get in day two but, if you look at Cisco, they've done a lot of things early. The human network, they've had telepresence. So they've hit megatrends, but they misfired on timing. The timing-- >> IOT is another >> IOT, they misfired on timing. But again, they had the network to fall back on, which is a core asset and core competency. But if you look at the timing of what they're doing right now, as Pat Gelsinger would say, "You get on the right wave" and what DevNet, to me, proves, Stu, is your point, is that Cisco's on the Cloud Native wave and they have a clear visibility for their network engineers, not to feel like they're not relevant and they have to retrain to learn how to code. What's important and we talked about it yesterday, is that network engineers are instrumental powering. And they're the tier one people. Now, with Cloud Native, there's a path where they can extend their career, not pivot, or reset, it's just becoming more powerful. So if you can be a network engineer, and then code with Cloud Native, you've got the best of both worlds, the power base extends. It's not like "I need to be retrained, my job's going away." No, no, your job is expanding. This is what DevNet has tapped into with DevNet Create, your reaction. >> Well when cloud exploded, everybody wanted infrastructure as code, and to your point, Stu, you remember when IBM launched Bluemix, like "We need developers." You know, Dell, HPE, Lenovo, these companies don't have a strong developer community, even Oracle kinda lost its way with developers. Here comes Cisco allowing Cisco engineers to do infrastructure as code, it's a huge leverage, it's an amazing-- >> Yeah Oracle should take a playbook out of what Cisco's doing, Stu, your thoughts. >> Yeah, absolutely, there's a lot of training. One of the strengths, actually, if you look at this community, it's about training, we talked about it in our open yesterday, John, when you walk in, there's this giant bookstore, people are excited, it's their career and they've been hearing for the last five years, up, you know. Automations gonna kill your job. That the machines are gonna kill your job. They're jumping in and most of them, at least, are understanding that they need to adjust what they're doing, learn, move forward, and embrace some of these options. >> Well, and it's not just, as we were talking earlier, John, it's not just learning python as a generalist, it's applying it specifically to Cisco infrastructure and actually getting stuff done, moving from command line interfaces to a much more facile development environment. Driving value through developer productivity and increasing value up a stack. >> Yeah as Diane Greene said yesterday in the keynote from Google Cloud is mind blowing experiences. I think Cisco is in a great position, they got a lot of core things going on, it's a position of strength. Can they execute, can they secure that network security, can they have that extensibility and the programmability in the network I think is core. I think DevNet's an indicator. Everything else will fall into place, in my opinion, so, day two Dave, thanks for joining us. >> My pleasure, thanks for having me. >> We'll have Dave Alante in the CUBE throughout the day, he's also gonna go out and get some stories. Wrapping it up here on the intro, day two begins. This is the CUBE, thanks for watching. Be right back with more after this short break. (techno music)