(bright upbeat music) >> Greetings, brilliant community and thank you so much for tuning in to theCUBE here for the last three days where we've been live from Detroit, Michigan. I've had the pleasure of spending this week with Lisa Martin and John Furrier. Thank you both so much for hanging out, for inviting me into the CUBE family. It's our first show together, it's been wonderful. >> Thank you. >> You nailed it. >> Oh thanks, sweetheart. >> Great job. Great job team, well done. Free wall to wall coverage, it's what we do. We stay till everyone else-- >> Savannah: 100 percent. >> Everyone else leaves, till they pull the plug. >> Lisa: Till they turn the lights out. We're still there. >> Literally. >> Literally last night. >> Still broadcasting. >> Whatever takes to get the stories and get 'em out there at scale. >> Yeah. >> Great time. >> 33. 33 different segments too. Very impressive. John, I'm curious, you're a trend watcher and you've been at every single KubeCon. >> Yep. >> What are the trends this year? Give us the breakdown. >> I think CNCF does this, it's a hard job to balance all the stakeholders. So one, congratulations to the CNCF for another great KubeCon and CloudNativeCon. It is really hard to balance bringing in the experts who, as time goes by, seven years we've been all of, as you said, you get experts, you get seniority, and people who can be mentors, 60% new people. You have vendors who are sponsoring and there's always people complaining and bitching and moaning. They want this, they want that. It's always hard and they always do a good job of balancing it. We're lucky that we get to scale the stories with CUBE and that's been great. We had some great stories here, but it's a great community and again, they're inclusive. As I've said before, we've talked about it. This year though is an inflection point in my opinion, because you're seeing the developer ecosystem growing so fast. It's global. You're seeing events pop up, you're seeing derivative events. CNCF is at the center point and they have to maintain the culture of developer experts, maintainers, while balancing the newbies. And that's going to be >> Savannah: Mm-hmm. really hard. And they've done a great job. We had a great conversation with them. So great job. And I think it's going to continue. I think the attendance metric is a little bit of a false positive. There's a lot of online people who didn't come to Detroit this year. And I think maybe the combination of the venue, the city, or just Covid preferences may not look good on paper, on the numbers 'cause it's not a major step up in attendance. It's still bigger, but the community, I think, is going to continue to grow. I'm bullish on it. >> Yeah, I mean at least we did see double the number of people that we had in Los Angeles. Very curious. I think Amsterdam, where we'll be next with CNCF in the spring, in April. I think that's actually going to be a better pulse check. We'll be in Europe, we'll see what's going on. >> John: Totally. >> I mean, who doesn't like Amsterdam in the springtime? Lisa, what have been some of your observations? >> Oh, so many observations. The evolution of the conference, the hallway track conversations really shifting towards adjusting to the enterprise. The enterprise momentum that we saw here as well. We had on the show, Ford. >> Savannah: Yes. We had MassMutual, we had ING, that was today. Home Depot is here. We are seeing all these big companies that we know and love, become software companies right before our eyes. >> Yeah. Well, and I think we forget that software powers our entire world. And so of course they're going to have to be here. So much running on Kubernetes. It's on-prem, it's at the edge, it's everywhere. It's exciting. Woo, I'm excited. John, what do you think is the number one story? This is your question. I love asking you this question. What is the number one story out KubeCon? >> Well, I think the top story is a combination of two things. One is the evolution of Cloud Native. We're starting to see web assembly. That's a big hyped up area. It got a lot of attention. >> Savannah: Yeah. That's kind of teething out the future. >> Savannah: Rightfully so. The future of this kind of lightweight. You got the heavy duty VMs, you got Kubernetes and containers, and now this web assembly, shows a trajectory of apps, server-like environment. And then the big story is security. Software supply chain is, to me, was the number one consistent theme. At almost all the interviews, in the containers, and the workflows, >> Savannah: Very hot. software supply chain is real. The CD Foundation mentioned >> Savannah: Mm-hmm. >> they had 16,000 vulnerabilities identified in their code base. They were going to automate that. So again, >> Savannah: That was wild. >> That's the top story. The growth of open source exposes potential vulnerabilities with security. So software supply chain gets my vote. >> Did you hear anything that surprised you? You guys did this great preview of what you thought we were going to hear and see and feel and touch at KubeCon, CloudNativeCon 2022. You talked about, for example, the, you know, healthcare financial services being early adopters of this. Anything surprise either one of you in terms of what you predicted versus what we saw? Savannah, let's start with you. >> You know what really surprised me, and this is ironic, so I'm a community gal by trade. But I was really just impressed by the energy that everyone brought here and the desire to help. The thing about the open source community that always strikes me is, I mean 187 different countries participating. You've got, I believe it's something like 175,000 people contributing to the 140 projects plus that CNCF is working on. But that culture of collaboration extends far beyond just the CNCF projects. Everyone here is keen to help each other. We had the conversation just before about the teaching and the learnings that are going on here. They brought in Detroit's students to come and learn, which is just the most heartwarming story out of this entire thing. And I think it's just the authenticity of everyone in this community and their passion. Even though I know it's here, it still surprises me to see it in the flesh. Especially in a place like Detroit. >> It's nice. >> Yeah. >> It's so nice to see it. And you bring up a good point. It's very authentic. >> Savannah: It's super authentic. >> I mean, what surprised me is one, the Wasm, or web assembly. I didn't see that coming at the scale of the conversation. It sucked a lot of options out of the room in my opinion, still hyped up. But this looks like it's got a good trajectory. I like that. The other thing that surprised me that was a learning was my interview with Solo.io, Idit, and Brian Gracely, because he's a CUBE alumni and former host of theCUBE, and analyst at Wikibon, was how their go-to-market was an example of a modern company in Covid with a clean sheet of paper and smart people, they're just doing things different. They're in Slack with their customers. And I walked away with, "Wow that's like a playbook that's not, was never, in the go-to-market VC-backed company playbook." I thought that was, for me, a personal walk away saying that's important. I like how they did that. And there's a lot of companies I think could learn from that. Especially as the recession comes where partnering with customers has always been a top priority. And how they did that was very clever, very effective, very efficient. So I walked away with that saying, "I think that's going to be a standard." So that was a pleasant surprise. >> That was a great surprise. Also, that's a female-founded company, which is obviously not super common. And the growth that they've experienced, to your point, really being catalyzed by Covid, is incredibly impressive. I mean they have some massive brand name customers, Amex, BMW for example. >> Savannah: Yeah. >> Great point. >> And I interviewed her years ago and I remember saying to myself, "Wow, she's impressive." I liked her. She's a player. A player for sure. And she's got confidence. Even on the interview she said, "We're just better, we have better product." And I just like the point of view. Very customer-focused but confident. And I just took, that's again, a great company. And again, I'm not surprised that Brian Gracely left Red Hat to go work there. So yeah, great, great call there. And of course other things that weren't surprising that I predicted, Red Hat continued to invest. They continue to bring people on theCUBE, they support theCUBE but more importantly they have a good strategy. They're in that multicloud positioning. They're going to have an opportunity to get a bite at the apple. And I what I call the supercloud. As enterprises try to go and be mainstream, Cloud Native, they're going to need some help. And Red Hat is always has the large enterprise customers. >> Savannah: What surprised you, Lisa? >> Oh my gosh, so many things. I think some of the memorable conversations that we had. I love talking with some of the enterprises that we mentioned, ING Bank for example. You know, or institutions that have been around for 100 plus years. >> Savannah: Oh, yeah. To see not only how much they've innovated and stayed relevant to meet the demands of the consumer, which are only increasing, but they're doing so while fostering a culture of innovation and a culture that allows these technology leaders to really grow within the organization. That was a really refreshing conversation that I think we had. 'Cause you can kind of >> Savannah: Absolutely. think about these old stodgy companies. Nah, of course they're going to digitize. >> Thinking about working for the bank, I think it's boring. >> Right? >> Yeah. And they were talking about, in fact, those great t-shirts that they had on, >> Yeah, yeah, yeah, yeah. were all about getting more people to understand how fun it is to work in tech for ING Bank in different industries. You don't just have to work for the big tech companies to be doing really cool stuff in technology. >> What I really liked about this show is we had two female hosts. >> Savannah: Yeah. >> How about that? Come on. >> Hey, well done, well done on your recruitment there, champ. >> Yes, thank you boss. (John laughs) >> And not to mention we have a really all-star production team. I do just want to give them a little shout out. To all the wonderful folks behind the lines here. (people clapping) >> John: Brendan. Good job. >> Yeah. Without Brendan, Anderson, Noah, and Andrew, we would be-- >> Of course Frank Faye holding it back there too. >> Yeah, >> Of course, Frank. >> I mean, without the business development wheels on the ship we'd really be in an unfortunate spot. I almost just swore on television. We're not going to do that. >> It's okay. No one's regulating. >> Yeah. (all laugh) >> Elon Musk just took over Twitter. >> It was a close call. >> That's right! >> It's going to be a hellscape. >> Yeah, I mean it's, shit's on fire. So we'll just see what happens next. I do, I really want to talk about this because I think it's really special. It's an ethos and some magic has happened here. Let's talk about Detroit. Let's talk about what it means to be here. We saw so many, and I can't stress this enough, but I think it really matters. There was a commitment to celebrating place here. Lisa, did you notice this too? >> Absolutely. And it surprised me because we just don't see that at conferences. >> Yeah. We're so used to going to the same places. >> Right. >> Vegas. Vegas, Vegas. More Vegas. >> Your tone-- >> San Francisco >> (both laugh) sums up my feelings. Yes. >> Right? >> Yeah. And, well, it's almost robotic but, and the fact that we're like, oh Detroit, really? But there was so much love for this city and recognizing and supporting its residents that we just don't see at conferences. You uncovered a lot of that with your swag-savvy segments, >> Savannah: Yeah. >> And you got more of that to talk about today. >> Don't worry, it's coming. Yeah. (laughs) >> What about you? Have you enjoyed Detroit? I know you hadn't been here in a long time, when we did our intro session. >> I think it's a bold move for the CNCF to come here and celebrate. What they did, from teaching the kids in the city some tech, they had a session. I thought that was good. >> Savannah: Loved that. I think it was a risky move because a lot of people, like, weren't sure if they were going to fly to Detroit. So some say it might impact the attendance. I thought they did a good job. Their theme, Road Ahead. Nice tie in. >> Savannah: Yeah. And so I think I enjoyed Detroit. The weather was great. It didn't rain. Nice breeze outside. >> Yeah. >> The weather was great, the restaurants are phenomenal. So Detroit's a good city. I missed some hockey games. I'd love to see the Red Wings play. Missed that game. But we always come back. >> I think it's really special. I mean, every time I talked to a company about their swag, that had sourced it locally, there was a real reason for this story. I mean even with Kasten in that last segment when I noticed that they had done Carhartt beanies, Carhartt being a Michigan company. They said, "I'm so glad you noticed. That's why we did it." And I think that type of, the community commitment to place, it all comes back to community. One of the bigger themes of the show. But that passion and that support, we need more of that. >> Lisa: Yeah. >> And the thing about the guests we've had this past three days have been phenomenal. We had a diverse set of companies, individuals come on theCUBE, you know, from Scott Johnston at Docker. A really one on one. We had a great intense conversation. >> Savannah: Great way to kick it off. >> We shared a lot of inside baseball, about Docker, super important company. You know, impressed with companies like Platform9 it's been around since the OpenStack days who are now in a relevant position. Rafi Systems, hot startup, they don't have a lot of resources, a lot of guerilla marketing going on. So I love to see the mix of startups really contributing. The big players are here. So it's a real great mix of companies. And I thought the interviews were phenomenal, like you said, Ford. We had, Kubia launched on theCUBE. >> Savannah: Yes. >> That's-- >> We snooped the location for KubeCon North America. >> You did? >> Chicago, everyone. In case you missed it, Bianca was nice enough to share that with us. >> We had Sarbjeet Johal, CUBE analyst came on, Keith Townsend, yesterday with you guys. >> We had like analyst speed dating last night. (all laugh) >> How'd that go? (laughs) >> It was actually great. One of the things that they-- >> Did they hug and kiss at the end? >> Here's the funny thing is that they were debating the size of the CNC app. One thinks it's too big, one thinks it's too small. And I thought, is John Goldilocks? (John laughs) >> Savannah: Yeah. >> What is John going to think about that? >> Well I loved that segment. I thought, 'cause Keith and Sarbjeet argue with each other on Twitter all the time. And I heard Keith say before, he went, "Yeah let's have it out on theCUBE." So that was fun to watch. >> Thank you for creating this forum for us to have that kind of discourse. >> Lisa: Yes, thank you. >> Well, it wouldn't be possible without the sponsors. Want to thank the CNCF. >> Absolutely. >> And all the ecosystem partners and sponsors that make theCUBE possible. We love doing this. We love getting the stories. No story's too small for theCUBE. We'll go with it. Do whatever it takes. And if it wasn't for the sponsors, the community wouldn't get all the great knowledge. So, and thank you guys. >> Hey. Yeah, we're, we're happy to be here. Speaking of sponsors and vendors, should we talk a little swag? >> Yeah. >> What do you guys think? All right. Okay. So now this is becoming a tradition on theCUBE so I'm very delighted, the savvy swag segment. I do think it's interesting though. I mean, it's not, this isn't just me shouting out folks and showing off t-shirts and socks. It's about standing out from the noise. There's a lot of players in this space. We got a lot of CNCF projects and one of the ways to catch the attention of people walking the show floor is to have interesting swag. So we looked for the most unique swag on Wednesday and I hadn't found this yet, but I do just want to bring it up. Oops, I think I might have just dropped it. This is cute. Is, most random swag of the entire show goes to this toothbrush. I don't really have more in terms of the pitch there because this is just random. (Lisa laughs) >> But so, everyone needs that. >> John: So what's their tagline? >> And you forget these. >> Yeah, so the idea was to brush your cloud bills. So I think they're reducing the cost of-- >> Kind of a hygiene angle. >> Yeah, yeah. Very much a hygiene angle, which I found a little ironic in this crowd to be completely honest with you. >> John: Don't leave the lights on theCUBE. That's what they say. >> Yeah. >> I mean we are theCUBE so it would be unjust of me not to show you a Rubik's cube. This is actually one of those speed cubes. I'm not going to be able to solve this for you with one hand on camera, but apparently someone did it in 17 seconds at the booth. Knowing this audience, not surprising to me at all. Today we are, and yesterday, was the t-shirt contest. Best t-shirt contest. Today we really dove into the socks. So this is, I noticed this trend at KubeCon in Los Angeles last year. Lots of different socks, clouds obviously a theme for the cloud. I'm just going to lay these out. Lots of gamers in the house. Not surprising. Here on this one. >> John: Level up. >> Got to level up. I love these 'cause they say, "It's not a bug." And anyone who's coded has obviously had to deal with that. We've got, so Star Wars is a huge theme here. There's Lego sets. >> John: I think it's Star Trek. But. >> That's Star Trek? >> John: That's okay. >> Could be both. (Lisa laughs) >> John: Nevermind, I don't want to. >> You can flex your nerd and geek with us anytime you want, John. I don't mind getting corrected. I'm all about, I'm all about the truth. >> Star Trek. Star Wars. Okay, we're all the same. Okay, go ahead. >> Yeah, no, no, this is great. Slim.ai was nice enough to host us for dinner on Tuesday night. These are their lovely cloud socks. You can see Cloud Native, obviously Cloud Native Foundation, cloud socks, whole theme here. But if we're going to narrow it down to some champions, I love these little bee elephants from Raft. And when I went up to these guys, I actually probably would've called these my personal winner. They said, again, so community focused and humble here at CNCF, they said that Wiz was actually the champion according to the community. These unicorn socks are pretty excellent. And I have to say the branding is flawless. So we'll go ahead and give Wiz the win on the best sock contest. >> John: For the win. >> Yeah, Wiz for the win. However, the thing that I am probably going to use the most is this really dope Detroit snapback from Kasten. So I'm going to be rocking this from now on for the rest of the segment as well. And I feel great about this snapback. >> Looks great. Looks good on you. >> Yeah. >> Thanks John. (John laughs) >> So what are we expecting between now and KubeCon in Amsterdam? >> Well, I think it's going to be great to see how they, the European side, it's a chill show. It's great. Brings in the European audience from the global perspective. I always love the EU shows because one, it's a great destination. Amsterdam's going to be a great location. >> Savannah: I'm pumped. >> The American crowd loves going over there. All the event cities that they choose are always awesome. I missed Valencia cause I got Covid. I'm really bummed about that. But I love the European shows. It's just a little bit, it's high intensity, but it's the European chill. They got a little bit more of that siesta vibe going on. >> Yeah. >> And it's just awesome. >> Yeah, >> And I think that the mojo that carried throughout this week, it's really challenging to not only have a show that's five days, >> but to go through all week, >> Savannah: Seriously. >> to a Friday at 4:00 PM Eastern Time, and still have the people here, the energy and all the collaboration. >> Savannah: Yeah. >> The conversations that are still happening. I think we're going to see a lot more innovation come spring 2023. >> Savannah: Mm-hmm. >> Yeah. >> So should we do a bet, somebody's got to buy dinner? Who, well, I guess the folks who lose this will buy dinner for the other one. How many attendees do you think we'll see in Amsterdam? So we had 4,000, >> Oh, I'm going to lose this one. >> roughly in Los Angeles. Priyanka was nice enough to share with us, there was 8,000 here in Detroit. And I'm talking in person, we're not going to meddle this with the online. >> 6500. >> Lisa: I was going to say six, six K. >> I'm going 12,000. >> Ooh! >> I'm going to go ahead and go big I'm going to go opposite Price Is Right. >> One dollar. >> Yeah. (all laugh) That's exactly where I was driving with it. I'm going, I'm going absolutely all in. I think the momentum here is building. I think if we look at the numbers from-- >> John: You could go Family Feud >> Yeah, yeah, exactly. And they mentioned that they had 11,000 people who have taken their Kubernetes course in that first year. If that's a benchmark and an indicator, we've got the veteran players here. But I do think that, I personally think that the hype of Kubernetes has actually preceded adoption. If you look at the data and now we're finally tipping over. I think the last two years we were on the fringe and right now we're there. It's great. (voice blares loudly on loudspeaker) >> Well, on that note (all laugh) On that note, actually, on that note, as we are talking, so I got to give cred to my cohosts. We deal with a lot of background noise here on theCUBE. It is a live show floor. There's literally someone on an e-scooter behind me. There's been Pong going on in the background. The sound will haunt the three of us for the rest of our lives, as well as the production crew. (Lisa laughs) And, and just as we're sitting here doing this segment last night, they turned the lights off on us, today they're letting everyone know that the event is over. So on that note, I just want to say, Lisa, thank you so much. Such a warm welcome to the team. >> Thank you. >> John, what would we do without you? >> You did an amazing job. First CUBE, three days. It's a big show. You got staying power, I got to say. >> Lisa: Absolutely. >> Look at that. Not bad. >> You said it on camera now. >> Not bad. >> So you all are stuck with me. (all laugh) >> A plus. Great job to the team. Again, we do so much flow here. Brandon, Team, Andrew, Noah, Anderson, Frank. >> They're doing our hair, they're touching up makeup. They're helping me clean my teeth, staying hydrated. >> We look good because of you. >> And the guests. Thanks for coming on and spending time with us. And of course the sponsors, again, we can't do it without the sponsors. If you're watching this and you're a sponsor, support theCUBE, it helps people get what they need. And also we're do a lot more segments around community and a lot more educational stuff. >> Savannah: Yeah. So we're going to do a lot more in the EU and beyond. So thank you. >> Yeah, thank you. And thank you to everyone. Thank you to the community, thank you to theCUBE community and thank you for tuning in, making it possible for us to have somebody to talk to on the other side of the camera. My name is Savannah Peterson for the last time in Detroit, Michigan. Thanks for tuning into theCUBE. >> Okay, we're done. (bright upbeat music)

(bright music) (crowd talking indistinctly in the background) >> Hey guys, welcome back to Detroit, Michigan. theCUBE is live at KubeCon + CloudNativeCon 2022. You might notice something really unique here. Lisa Martin with our newest co-host of theCUBE, Savannah Peterson! Savannah, it's great to see you. >> It's so good to be here with you (laughs). >> I know, I know. We have a great segment coming up. I always love talking couple things, cars, one, two, with companies that have been around for a hundred plus years and how they've actually transformed. >> Oh yeah. >> Ford is here. You have a great story about how you, about Ford. >> Ford brought me to Detroit the first time. I was here at the North American International Auto Show. Some of you may be familiar, and the fine folks from Ford brought me out to commentate just like this, as they were announcing the Ford Bronco. >> Satish: Oh wow. >> Which I am still lusting after. >> You don't have one yet? >> For the record. No, I don't. My next car's got to be an EV. Although, ironically, there's a Ford EV right behind us here on set today. >> I know, I know. >> Which we were both just contemplating before we went live. >> It's really shiny. >> We're going to have to go check it out. >> I have to check it out. Yep, we'll do that. Yeah. Well, please welcome our two guests from Ford, Satish Puranam, is here, The Technical Leader at Cloud and Rebecca Risk, Principal Architect, developer relations. We are so excited to have you guys on the program. >> Clearly. >> Thanks for joining us. (all laugh) >> Thank you for having us. >> I love you're Ford enthusiasts! Yeah, that's awesome. >> I drive a Ford. >> Oh, awesome! Thank you. >> I can only say that's one car company here. >> That's great. >> Yes, yes. >> Great! Thank you a lot. >> Thank you for your business! >> Absolutely. (all laugh) >> So, Satish, talk to us a little bit about- I mean I think of Cloud as a car company but it seems like it's a technology company that makes cars. >> Yes. Talk to us about Ford as a Cloud first, technology driven company, and then we're going to talk about what you're doing with Red Hat and Boston University. >> Yeah, I'm like everything that all these cars that you're seeing, beautiful right behind us it's all built on, around, and with technology, right? So there's so much code goes into these cars these days, it's probably, it's mind boggling to think that probably your iPhones might be having less code as opposed to these cars. Everything from control systems, everything is code. We don't do any more clay models. Everything is done digital, 3D, virtual reality and all that stuff. So all that takes code, all of that takes technology. And we have been in that journey for the last- since 2016 when we started our first mobile app and all that stuff. And of late we have been like, heavily invested in Google. Moving a lot of these experiences, data acquisition systems AI/ML modeling for like all the autonomous cars. It's all technology and like from the day it is conceived, to the day it is marketed, to the day when you show up for a servicing, and hopefully soon how you can buy and you know, provide feedback to us, is all technology that drives all of this stuff. So it's amazing for us to see everything that we go and immerse ourselves in the technology. There is a real life thing that we can see what we all do for it, right? So- >> Yes, we're only sorry that our audience can't actually see the car, >> Yep. >> but we'll get some B-roll for you later on. Rebecca, talk a little bit about your role. Here we are at KubeCon, Savannah and I and John were talking when we went live this morning, that this is huge. That the show floor is massive, a lot bigger than last year. The collaboration and the spirit of the community is not only alive and well, as we heard in the keynote this morning, it's thriving. >> Yeah. >> Talk about developer relations at Ford and what you are helping to drive in your role. >> Yeah, so my team is all about helping developers work faster with different platforms that my team curates and produces, so that our developers don't have to deal with all of the details of setting up their environments to actually code. And we have really great people, kind of the top software developers in the company, are part of my team to produce those products that other people can use, and accelerate their development. And we have a great relationship with the developers in the company and outside with the different vendor relationships that we have, to make sure that we're always producing the next platform with the next tech stack that our developers will want to continue to use to produce the really great products that we are all about making at Ford. >> Let's dig in there a little bit because I'm curious and I suspect you both had something to do with it. How did you approach your Cloud Native transformation and how do you evaluate new technologies for the team? >> It's sometimes- many a times I would say it's like dogfooding and like experimentation. >> Yeah. Isn't anything in innovation a lot of- >> Yeah, a lot of experimentation. We started our, as I said, the Cloud Native journey back in 2016 with Cloud Foundry and things, technologies around that. Soon realized, that there was like a lot of buzz around that time. Twelve-Factor was a thing, Stateless was a thing. And then all those Stateful needs to drive the Stateless. So where do we do that thing? And the next logical iteration was Kubernetes was bursting upon the scene at that time. So we started doing a lot of experimentation. >> Like the Kool-Aid man, burst on the Kubernetes scene- >> Exactly right. >> Through the wall. >> So, the question is like, why can't we do? I think we were like crazy enough to say that Kubernetes people are talking about our serverless or Twelve-Factor on Kubernetes. We are crazy enough to do Stateful on Kubernetes and we've been doing it successfully for five years. So it's a lot about experimentation. I think good chunk of experiments that we do do not yield the results that we get, but many a times, some of them are like Gangbusters. Like, other aspects that we've been doing of late is like partnering with Becky and rest of the organization, right? Because they are the people who are like closest to the developers. We are somewhat behind the scenes doing some things but it is Becky and the rest of the architecture teams who are actually front and center with the customers, right? So it is the collaborative effort that we've been working through past few years that has been really really been useful and coming around and helping us to make some of these products really beautiful. >> Yeah, well you make a lot of beautiful products. I think we've all, I think we've all seen them. Something that I think is really interesting and part of why I was so excited for this interview, and kind of nudged John out, was because you've been- Ford has been investing in technology in a committed way for decades and I don't think most people are aware of that. When I originally came out to Dearborn, I learned that you've had a head of VR who happens to be a female. For what it's worth, Elizabeth, who's been running VR for you for two and a half decades, for 25 years. >> Satish: Yep. >> That is an impressive commitment. What is that like from a culture perspective inside of Ford? What is the attitude around innovation and technology? >> So I've been a long time Ford employee. I just celebrated my 29th year. >> Oh, wow! >> Congratulations! >> Wow, congrats! That's a huge deal. >> Yeah, it's a huge deal. I'm so proud of my career and all that Ford has brought to me and it's just a testament. I have many colleagues like me who've been there for their whole career or have done other things and come to Ford and then spent another 20 years with us because we foster the culture that makes you want to stay. We have development programs to allow you to upscale and change your role and learn new things and play with the new technologies that people are interested in doing and really make an impact to our community of developers at Ford or the company itself and the results that we're delivering. So to have that, you know, culture for so many years that people really love to work. They love to work with the people that they're working with. They love to stay engaged and they love the fact that you can have many different careers within the same umbrella, which we call the "blue oval". And that's really why I've been there for so long. I think I probably had 13 very unique and different jobs along the way. It's as if I left, and you know shopped around my skills elsewhere. But I didn't ever have to leave the company. It's been fabulous. >> The cultural change and adoption of- embracing modern technology- Cloud Native automotive software is impressive because a lot of historied companies, you guys have been there a long time, have challenges with that because it's really hard to get an entire moving, you'll call it the blue oval, to change and adapt- >> Savannah: I love that. >> and be willing to experiment. So that that is impressive. Talk about, you go by Becky, so I'll call you Becky, >> Rebecca/Becky: Yeah. >> The developer culture in terms of the developers really being the center of the nucleus of influencing the direction in which the company's going. I imagine that they probably are fairly influential. >> Yeah, so I had a very- one of the unique positions I held was a culture change for our department, Information Technology in 2016. >> Satish: Yeah. >> As the teacher was involved with moving us to the cloud, I was responsible- >> You are the transformation team! This is beautiful. I love this. We've got the right people on the show. >> Yeah, we do. >> I was responsible for changing the culture to orient our employees to pay attention to what do we want to create for tomorrow? What are the kind of skills we need to trust each other to move quickly. And that was completely unique. >> Satish: Yeah. >> Like I had men in the trenches delivering software before that, and then plucked out because they wanted someone, you know who had authentic experience with our development team to be that voice. And it was such a great investment that Ford continues to do is invest in our culture transformation. Because with each step forward that we do, we have to refine what our priorities are. And you do that through culture transformation and culture management. And that's been, I think really, the key to our successful pivots that we've made over the last six years that we've been able to continue to refine and hone where we really want to go through that culture movement. >> Absolutely. I think if I could add another- >> Please. >> spotlight to it is like the biggest thing about Ford has been among various startup-like culture, right? So the idea is that we encourage people to think outside the box, right? >> Savannah: Or outside the oval? >> Right! (laughs) >> Lisa: Outside the oval, yes! >> Absolutely! Right. >> So the question is like, you can experiment with various things, new technologies and you will get all the leadership support to go along with it. I think that is very important too and like we can be in the trenches and talk about all of these nice little things but who the heck would've thought that, you know Kubernetes was announced in 2015, in late 2016, we have early dev Kubernetes clusters already running. 2017, we are live with workloads on Kubernetes! >> Savannah: Early adopters over here. >> Yeah. >> Yeah. >> I'm like all of this thing doesn't happen without lot of foresight and support from the leadership, but it's also the grassroot efforts that is encouraged all along to be on the front end of all of these things and try different things. Some of them may not work >> Savannah: Right. >> But that's okay. But how do we know we are doing something, if you're not failing? We have to fail in order to do something, right? >> Lisa: I always say- >> So I think that's been a great thing that is encouraged very often and otherwise I would not be doing, I've done a whole bunch of stuff at Ford. Without that kind of ability to support and have an appetite for, some of those things would not have been here at all. >> I always say failure is not a bad F-word. >> Satish: Yep. >> Savannah: I love that. >> But what you're talking about there is kind of like driving this hot wheel of experimentation. You have to have the right culture and the mindset- >> Satish: Absolutely. >> to do that. Try fail, move on, learn, iterate, go. >> Satish: Correct. >> You guys have a great partnership with Red Hat and Boston University. You're speaking about that later today. >> Satish: Yes. >> Unpack that for us. What, from a technical perspective, what are you doing and what's it resulting in? >> Yeah, I think the biggest thing is Becky was talking about as during this transformation journey, is lot has changed in very small amount of time. So we traditionally been like, "Hey, here's a spreadsheet of things I need you to deliver for me" to "Here is a catalog of things, you can get it today and be successful with it". That is frightening to several of our developers. The goal, one of the things that we've been working with Q By Example, Red Hat and all the thing, is that how can we lower the bar for the developers, right? Kubernetes is great. It's also a wall of YAML. >> It's extremely complex, number one complaint. >> The question is how can I zero on? I'm like, if we go back think like when we talk about in cars with human-machine interfaces, which parts do I need to know? Here's the steering wheel, here's the gas pedal, or here's the brake. As long as you know these two, three different things you should be fairly be okay to drive those things, right? So the idea of some of the things with enablementing we are trying to do is like reduce that barrier, right? Reduce- lower the bar so that more people can participate in it. >> One of the ways that you did that was Q By Example, right, QBE? >> Satish: Yes, Yes. >> Can you tell us a little bit more about that as you finish this answer? >> Yeah, I think the biggest thing with Q By Example is like Q By Example gives you the small bite-sized things about Kubernetes, right? >> Savannah: Great place to start. >> But what we wanted to do is that we wanted to reinforce that learning by turning into a real world living example app. We took part info, we said, Hey, what does it look like? How do I make sure that it is highly available? How do I make sure that it is secure? Here is an example YAML of it that you can literally verbatim copy and paste into your editor and click run and then you will get an instant gratification feedback loop >> I was going to say, yeah, they feel like you're learning too! >> Yes. Right. So the idea would be is like, and then instead of giving you just a boring prose text to read, we actually drop links to relevant blog posts saying that, hey you can just go there. And that has been inspirational in terms of like and reinforcing the learning. So that has been where we started working with the Boston University, Red Hat and the community around all of that stuff. >> Talk a little bit about, Becky, about some of the business outcomes. You mentioned things like upskilling the workforce which is really nice to hear that there's such a big focus on it. But I imagine too, there's more participation in the community, but also from an end customer perspective. Obviously, everything Ford's doing is to serve the end customers >> Becky: Right. How does this help the end customer have that experience that they really, these days, demand with patience being something that, I think, is gone because of the pandemic? >> Right? Right. So one of the things that my team does is we create the platforms that help Accelerate developers be successful and it helps educate them more quickly on appropriate use of the platforms and helps them by adopting the platforms to be more secure which inherently lead to the better results for our end customers because their data is secure because the products that they have are well created and they're tested thoroughly. So we catch all those things earlier in the cycle by using these platforms that we help curate and produce. And that's really important because, like you had mentioned, this steep learning curve associated with Kubernetes, right? >> Savannah: Yeah. >> So my team is able to kind of help with that abstraction so that we solve kind of the higher complex problems for them so that developers can move faster and then we focus our education on what's important for them. We use things like Q By Example, as a source instead of creating that content ourselves, right? We are able to point them to that. So it's great that there's that community and we're definitely involved with that. But that's so important to help our developers be successful in moving as quickly as they want and not having 20,000 people solve the same problems. >> Satish: (chuckles) Yeah. >> Each individually- >> Savannah: you don't need to! >> and sometimes differently. >> Savannah: We're stronger together, you know? >> Exactly. >> The water level rises together and Ford is definitely a company that illustrates that by example. >> Yeah, I'm like, we can't make a better round wheel right? >> Yeah! So, we have to build upon what we have already been built ahead of us. And I think a lot of it is also about how can we give back and participate in the community, right? So I think that is paramount for us as like, here we are in Detroit so we're trying to recruit and show people that you know, everything that we do is not just old car and sheet metal >> Savannah: Combustion. >> and everything and right? There's a lot of tech goes and sometimes it is really, really cool to do that. And biggest thing for us is like how can we involve our community of developers sooner, earlier, faster without actually encumbering them and saying that, hey here is a book, go master it. We'll talk two months later. So I think that has been another journey. I think that has been a biggest uphill challenge for us is that how can we actually democratize all of these things for everybody. >> Yeah. Well no one better to try than you I would suspect. >> We can only try and hope everything turns out well, right? >> You know, as long as there's room for the bumpers on the lane for if you fail. >> Exactly. >> It sounds like you're driving the program in the right direction. Closing question for you, what's next? Is electric the future? Is Kubernetes the future? What's Ford all in on right now, looking forward? (crowd murmuring in the background) >> Data is the king, right? >> Savannah: Oh, okay, yes! >> Data is a new currency. We use that for several things to improve the cars improve the quality of autonomous driving Is Level 5 driving here? Maybe will be here soon, we'll see. But we are all working towards it, right? So machine learning, AI feedback. How do you actually post sale experience for example? So all of these are all areas that we are working to. We are, may not be getting like Kubernetes in a car but we are putting Kubernetes in plants. Like you order a Marquis or you order a Bronco, you see that here. Here's where in the assembly line your car is. It's taking pictures. It's actually taking pictures on Kubernetes platform. >> That's pretty cool. >> And it is tweeting for you on the Twitter and the social media platform. So there's a lot of that. So it is real and we are doing it. We need more help. A lot of the community efforts that we are seeing and a lot of the innovation that is happening on the floor here, it's phenomenal. The question is how we can incorporate those things into our workflows. >> Yeah, well you have the right audience for that here. You also have the right attitude, >> Exactly. >> the right appetite, and the right foundation. Becky, last question for you. Top three takeaways from your talk today. If you're talking to the developer community you want to inspire: Come work for us! What would you say? >> If you're ready to invest in yourself and upskill and be part of something that is pretty remarkable, come work for us! We have many, many different technical career paths that you can follow. We invest in our employees. When you master something, it's time for you to move on. We have career growth for you. It's been a wonderful gift to me and my family and I encourage everyone to check us out careers.ford.com or stop by our booth if you're happen to be here in person. >> Satish: Absolutely! >> We have our curated job openings that are specific for this community, available. >> Satish: Absolutely. >> Love it. Perfect close. Nailed pitch there. I'm sure you're all going to check out their job page. (all laugh) >> Exactly! And what you talked about, the developer experience, the customer experience are inextricably linked and you guys are really focused on that. Congratulations on all the work that you've done. We got to go get a selfie with that car girl. >> Yes, we do. >> Absolutely. >> We got to show them, we got to show the audience what it looks like on the inside too. We'll do a little IG video. (Lisa laughs) >> Absolutely. >> We will show you that for our guests and my cohost, Savannah Peterson. Lisa Martin here live in Detroit with theCUBE at KubeCon and CloudNativeCon 2022. The one and only John Furrier, who you know gets FOMO, is going to be back with me next. So stick around. (all laugh) (bright music)

>> Narrator: theCUBE presents KubeCon and CloudNativeCon Europe 2022, brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partners. >> Welcome to Valencia, Spain, KubeCon, CloudNativeCon Europe 2022. I'm Keith Townsend, your host. And we're continuing the conversations around ecosystem cloud native, 7,500 people here, 170 plus show for sponsors. It is for open source conference, I think the destination. I might even premise that this may be, this may eventually roll to the biggest tech conference in the industry, maybe outside of AWS re:Invent. My next guest is Nick van Wiggeren. >> Wiggeren. >> VP engineering of PlanetScale. Nick, I'm going to start off the conversation right off the bat PlanetScale cloud native database, why do we need another database? >> Well, why don't you need another database? I mean, are you happy with yours? Is anyone happy with theirs? >> That's a good question. I don't think anyone is quite happy with, I don't know, I've never seen a excited database user, except for guys with really (murmurs) guys with great beards. >> Yeah. >> Keith: Or guys with gray hair maybe. >> Yeah. Outside of the dungeon I think... >> Keith: Right. >> No one is really is happy with their database, and that's what we're here to change. We're not just building the database, we're actually building the whole kind of start to finish experience, so that people can get more done. >> So what do you mean by getting more done? Because MySQL has been the underpinnings of like massive cloud database deployments. >> 100% >> It has been the de-facto standard. >> Nick: Yep. >> For cloud databases. >> Nick: Yep. >> What is PlanetScale doing in enabling us to do that I can't do with something like a MySQL or a SQL server? >> Great question. So we are MySQL compatible. So under the hood it's a lot of the MySQL you know and love. But on top of that we've layered workflows, we've layered scalability, we've layered serverless. So that you can get all of the the parts of the MySQL, that dependability, the thing that people have used for 20, 30 years, right? People don't even know a world before MySQL. But then you also get this ability to make schema changes faster. So you can kind of do your work quicker get to the business objectives faster. You can scale farther. So when you get to your MySQL and you say, well, can we handle adding this one feature on top? Can we handle the user growth we've got? You don't have to worry about that either. So it's kind of the best of both worlds. We've got one foot in history and we've got one foot in the new kind of cloud native database world. We want to give everyone the best of both. >> So when I think of serverless because that's the buzzy world. >> Yeah. >> But when I think of serverless I think about developers being able to write code. >> Yep. >> Deploy the code, not worry about VM sizes. >> Yep. >> Amount of disk space. >> Yep. >> CPU, et cetera. But we're talking about databases. >> Yep. >> I got to describe what type of disk I want to use. I got to describe the performance levels. >> Yep. >> I got all the descriptive stuff that I have to do about infrastructures. Databases are not... >> Yep. >> Keith: Serverless. >> Yep. >> They're the furthest thing from it. >> So despite what the name may say, I can guarantee you PlanetScale, your PlanetScale database does run on at least one server, usually more than one. But the idea is exactly what you said. So especially when you're starting off, when you're first beginning your, let's say database journey. That's a word I use a lot. The furthest thing from your mind is, how many CPUs do I need? How many disk iOS do I need? How much memory do I need? What we want you to be able to do is get started on focusing on shipping your code, right? The same way that Lambda, the same way that Kubernetes, and all of these other cloud native technologies just help people get done what they want to get done. PlanetScale is the same way, you want a database, you sign up, you click two buttons, you've got a database. We'll handle scaling the disk as you grow, we'll handle giving you more resources. And when you get to a spot where you're really starting to think about, my database has got hundreds of gigabytes or petabytes, terabytes, that's when we'll start to talk to you a little bit more about, hey, you know it really does run on a server, we ain't got to help you with the capacity planning, but there's no reason people should have to do that up front. I mean, that stinks. When you want to use a database you want to use a database. You don't want to use, 747 with 27 different knobs. You just want to get going. >> So, also when I think of serverless and cloud native, I think of stateless. >> Yep. >> Now there's stateless with databases, help me reconcile like, when you say it's cloud native. >> Nick: Yep. >> How is it cloud native when I think of cloud native as stateless? >> Yeah. So it's cloud native because it exists where you want it in the cloud, right? No matter where you've deployed your application on your own cloud, on a public cloud, or something like that, our job is to meet you and match the same level of velocity and the same level of change that you've got on your kind of cloud native setup. So there's a lot of state, right? We are your state and that's a big responsibility. And so what we want to do is, we want to let you experiment with the rest of the stateless workloads, and be right there next to you so that you can kind of get done what you need to get done. >> All right. So this concept of clicking two buttons... >> Nick: Yeah. >> And deploying, it's a database. >> Nick: Yep. >> It has to run somewhere. So let's say that I'm in AWS. >> Nick: Yep. >> And I have AWS VPC. What does it look like from a developer's perspective to consume the service? >> Yeah. So we've got a couple of different offerings, and AWS is a great example. So at the very kind of the most basic database unit you click, you get an endpoint, a host name, a password, and the username. You feed that right into your application and it's TLS secure and stuff like that, goes right into the database no problem. As you grow larger and larger, we can use things like AWS PrivateLink and stuff like that, to actually start to integrate more with your AWS environment, all the way over to what we call PlanetScale Managed. Which is where we actually deploy your data plan in your AWS account. So you give us some permissions and we kind of create a sub-account and stuff like that. And we can actually start sending pods, and hold clusters and stuff like that into your AWS account, give you a PrivateLink, so that everything looks like it's kind of wrapped up in your ownership but you still get the same kind of PlanetScale cloud experience, cloud native experience. >> So how do I make calls to the database? I mean, do I have to install a new... >> Nick: Great question. >> Like agent, or do some weird SQL configuration on my end? Or like what's the experience? >> Nope, we just need MySQL. Same way you'd go, install MySQL if you're on a Mac or app store to install MySQL on analytics PC, you just username, password, database name, and stuff like that, you feed that into your app and it just works. >> All right. So databases are typically security. >> Nick: Yep. >> When my security person. >> Nick: Yep. >> Sees a new database. >> Nick: Yep. >> Oh, they get excited. They're like, oh my job... >> Nick: I bet they do. >> My job just got real easy. I can find like eight or nine different findings. >> Right. >> How do you help me with compliance? >> Yeah. >> And answering these tough security questions from security? >> Great question. So security's at the core of what we do, right? We've got security people ourselves. We do the same thing for all the new vendors that we onboard. So we invest a lot. For example, the only way you can connect to a PlanetScale database even if you're using PrivateLink, even if you're not touching the public internet at all, is over TLS secured endpoint, right? From the very first day, the very first beta that we had we knew not a single byte goes over the internet that's not encrypted. It's encrypted at rest, we have audit logging, we do a ton internally as well to make sure that, what's happening to your database is something you can find out. The favorite thing that I think though is all your schema changes are tracked on PlanetScale, because we provide an entire workflow for your schema changes. We actually have like a GitHub Polar Request style thing, your security folks can actually look and say, what changes were made to the database day in and day out. They can go back and there's a full history of that log. So you actually have, I think better security than a lot of other databases where you've got to build all these tools and stuff like that, it's all built into PlanetScale. >> So, we started out the conversation with two clicks but I'm a developer. >> Nick: Yeah. >> And I'm developing a service at scale. >> Yep. >> I want to have a SaaS offering. How do I automate the deployment of the database and the management of the database across multiple customers? >> Yeah, so everything is API driven. We've got an API that you can use supervision databases to make schema changes, to make whatever changes you want to that database. We have an API that powers our website, the same API that customers can use to kind of automate any part of the workflow that they want. There's actually someone who did talk earlier using, I think, wwww.crossplane.io, or they can use Kubernetes custom resource definitions to provision PlanetScale databases completely automatically. So you can even do it as part of your standard deployment workflow. Just create a PlanetScale database, create a password, inject it in your app, all automatically. >> So Nick, as I'm thinking about scale. >> Yep. >> I'm thinking about multiple customers. >> Nick: Yep. >> I have a successful product. >> Nick: Yep. >> And now these customers are coming to me with different requirements. One customer wants to upgrade once every 1/4, another one, it's like, you know what? Just bring it on. Like bring the schema changes on. >> Yep. >> I want the latest features, et cetera. >> Nick: Right. >> How do I manage that with PlanetScale? When I'm thinking about MySQL it's a little, that can be a little difficult. >> Nick: Yeah. >> But how does PlanetScale help me solve that problem? >> Yeah. So, again I think it's that same workflow engine that we've built. So every database has its own kind of deploy queue, its own migration system. So you can automate all these processes and say, on this database, I want to change this schema this way, on this database I'm going to hold off. You can use our API to drive a view into like, well, what's the schema on this database? What's schema on this database? What version am I running on this database? And you can actually bring all that in. And if you were really successful you'd have this single plane of glass where you can see what's the status of all my databases and how are they doing, all powered by kind of the PlanetScale API. >> So we can't talk about databases without talking about backup. >> Nick: Yep. >> And recovery. >> Yep. >> How do I back this thing up and make sure that I can fall back? If someone deleted a table. >> Nick: Yep. >> It happens all the time in production. >> Nick: Yeah, 100%. >> How do I recover from it? >> So there's two pieces to this, and I'm going to talk about two different ways that we can help you solve this problem. One of them is, every PlanetScale database comes with backups built in and we test them fairly often, right? We use these backups. We actually give you a free daily backup on every database 'cause it's important to us as well. We want to be able to restore from backup, we want to be able to do failovers and stuff like that, all that is handled automatically. The other thing though is this feature that we launched in March called the PlanetScale Rewind. And what Rewind is, is actually a schema migration undo button. So let's say, you're a developer you're dropping a table or a column, you mean to drop this, but you drop the other one on accident, or you thought this column was unused but it wasn't. You know when you do something wrong, you cause an incident and you get that sick feeling in your stomach. >> Oh, I'm sorry. I've pulled a drive that was written not ready file and it was horrible. >> Exactly. And you kind of start to go, oh man, what am I going to do next? Everyone watching this right now is probably squirming in their seat a bit, you know the feeling. >> Yeah, I know the feeling >> Well, PlanetScale gives you an undo button. So you can click, undo migration, for 30 minutes after you do the migration and we'll revert your schema with all the data in it back to what your database looked like before you did that migration. Drop a column on accident, drop a table on accident, click the Rewind button, there's all the data there. And, the new rights that you've taken while that's happened are there as well. So it's not just a restore to a point in time backup. It's actually that we've replicated your rights sent them to both the old and the new schema, and we can get you right back to where you started, downtime solved. >> Both: So. >> Nick: Go ahead. >> DBAs are DBAs, whether they've become now reformed DBAs that are cloud architects, but they're DBAs. So there's a couple of things that they're going to want to know, one, how do I get my zero back up in my hands? >> Yeah. >> I want my, it's MySQL data. >> Nick: Yeah. >> I want my MySQL backup. >> Yeah. So you can just take backups off the database yourself the same way that you're doing today, right? MySQL dump, MySQL backup, and all those kinds of things. If you don't trust PlanetScale, and look, I'm all about backups, right? You want them in two different data centers on different mediums, you can just add on your own backup tools that you have right now and also use that. I'd like you to trust that PlanetScale has the backups as well. But if you want to keep doing that and run your own system, we're totally cool with that as well. In fact, I'd go as far as to say, I recommend it. You never have too many backups. >> So in a moment we're going to run Kube clock. So get your... >> Okay, all right. >> You know, stand tall. >> All right. >> I'll get ready. I'm going to... >> Nick: I'm tall, I'm tall. >> We're both tall. The last question before Kube clock. >> Nick: Yeah. >> It is, let's talk a little nerve knobs. >> Nick: Okay. >> The reform DBA. >> Nick: Yeah. >> They want, they're like, oh, this query ran a little bit slow. I know I can squeeze a little bit more out of that. >> Nick: Yeah. >> Who do they talk to? >> Yeah. So that's a great question. So we provide you some insights on the product itself, right? So you can take a look and see how are my queries performing and stuff like that. Our goal, our job is to surface to you all the metrics that you need to make that decision. 'Cause at the end of the day, a reform DBA or not it is still a skill to analyze the performance of a MySQL query, run and explain, kind of figure all that out. We can't do all of that for you. So we want to give you the information you need either knowledge or you know, stuff to learn whatever it is because some of it does have to come back to, what's my schema? What's my query? And how can I optimize it? I'm missing an index and stuff like that. >> All right. So, you're early adopter of the Kube clock. >> Okay. >> I have to, people say they're ready. >> Nick: Ooh, okay. >> All the time people say they're ready. >> Nick: Woo. >> But I'm not quite sure that they're ready. >> Nick: Well, now I'm nervous. >> So are you ready? >> Do I have any other choice? >> No, you don't. >> Nick: Then I am. >> But are you ready? >> Sure, let's go. >> All right. Start the Kube clock. (upbeat music) >> Nick: All right, what do you want me to do? >> Go. >> All right. >> You said you were ready. >> I'm ready, all right, I'm ready. All right. >> Okay, I'll reset. I'll give you, I'll give, see people say they're ready. >> All right. You're right. You're right. >> Start the Kube clock, go. >> Okay. Are you happy with how your database works? Are you happy with the velocity? Are you happy with what your engineers and what your teams can do with their database? >> Follow the dream not the... Well, follow the green... >> You got to be. >> Not the dream. >> You got to be able to deliver. At the end of the day you got to deliver what the business wants. It's not about performance. >> You got to crawl before you go. You got to crawl, you got to crawl. >> It's not just about is my query fast, it's not just about is my query right, it's about, are my customers getting what they want? >> You're here, you deserve a seat at the table. >> And that's what PlanetScale provides, right? PlanetScale... >> Keith: Ten more seconds. >> PlanetScale is a tool for getting done what you need to get done as a business. That's what we're here for. Ultimately, we want to be the best database for developing software. >> Keith: Two, one. >> That's it. End it there. >> Nick, you took a shot, I'm buying it. Great job. You know, this is fun. Our jobs are complex. >> Yep. >> Databases are hard. >> Yep. >> It is the, where your organization keeps the most valuable assets that you have. >> Nick: A 100%. >> And we are having these tough conversations. >> Nick: Yep. >> Here in Valencia, you're talking to the leader in tech coverage. From Valencia, Spain, I'm Keith Townsend, and you're watching theCUBE, the leader in high tech coverage. (upbeat music)

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America. 2020. Virtual Brought to You by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners Welcome back to the Cube. Virtual coverage of KUB Con Cloud native 2020. It's virtual this year. We're not face to face. Were normally in person where we have great interviews. Everyone's kind of jamming in the hallways, having a good time talking tech, identifying the new projects and knew where So we're not. There were remote. I'm John for your host. We've got two great gas, both Cuba alumni's Chris. And is it chief technology officer of the C and C F Chris, Welcome back. Great to see you. Thanks for coming on. Appreciate it. >>Awesome. Glad to be here. >>And, of course, another Cube alumni who is in studio. But we haven't had him at a Show Jr store meant executive director of the Fin Ops Foundation. And that's the purpose of this session. A interesting data point we're going to dig into how cloud has been enabling Mawr communities, more networks of practitioners who are still working together, and it's also a success point Chris on the C N C F vision, which has been playing out beautifully. So we're looking forward to digging. Jr. Thanks for coming on. Great to see you. >>Yeah, great to be here. Thanks, John. >>So, first of all, I want to get the facts out there. I think this is really important story that people should pay attention to the Finn Ops Foundation. That J. R. That you're running is really an interesting success point because it's it's not the c n c f. Okay. It's a practitioner that builds on cloud. Your experience in community you had is doing specific things that they're I won't say narrow but specific toe a certain fintech things. But it's really about the success of Cloud. Can you explain and and layout for take a minute to explain What is the fin Ops foundation and has it relate to see NCF? >>Yeah, definitely. So you know, if you think about this, the shift that we've had to companies deploying primarily in cloud, whether it be containers a ciencia focuses on or traditional infrastructure. The thing that typically people focus on right is the technology and innovation and speed to market in all those areas. But invariably companies hit this. We'd like to call the spend panic moment where they realize they're They're initially spending much more than they expected. But more importantly, they don't really have the processes in place or the people or the tools to do things like fully, you know, understand where their costs are going to look at how to optimize those to operate that in their organizations. And so the foundation pinups foundation eyes really focused on, uh, the people in practitioners who are in organizations doing cloud financial management, which is, you know, being those who drive this accountability of this variable spin model that's existed. So we were partnering very closely with, uh, see NCF. And we're now actually part of the Linux Foundation as of a few months ago, Uh, and you know, just to kind of put into context how that you kind of Iraq together, whereas, you know, CNC s very focused on open source coordinative projects, you know, For example, Spotify just launched their backstage cloud called Management Tool into CFCF Spotify folks, in our end, are working on the best practices around the cloud financial management that standards to go along with that. So we're there to help, you know, define this sort of cultural transformation, which is a shift to now. Engineers happen to think about costs as they never did before. On finance, people happen to partner with technology teams at the speed of cloud, and, you know executives happen to make trade off decisions and really change the way that they operate the business. With this variable page ago, engineers have all the access to spend the money in Cloud Model. >>Hey, blank check for engineers who doesn't like that rain that in its like shift left for security. And now you've got to deal with the financial Finn ops. It's really important. It's super point, Chris. In all seriousness. Putting kidding aside, this is exactly the kind of thing you see with open sores. You're seeing things like shift left, where you wanna have security baked in. You know what Jr is done in a fabulous job with his community now part of Linux Foundation scaling up, there's important things to nail down that is specific to that domain that are related to cloud. What's your thoughts on this? Because you're seeing it play out. >>Yeah, no, I mean, you know, I talked to a lot of our end user members and companies that have been adopting Cloud Native and I have lots of friends that run, you know, cloud infrastructure at companies. And Justus Jr said, You know, eventually there's been a lot of success and cognitive and want to start using a lot of things. Your bills are a little bit more higher than you expect. You actually have trouble figuring out, you know, kind of who's using what because, you know, let's be honest. A lot of the clouds have built amazing services. But let's say the financial management and cost management accounting tools charge back is not really built in well. And so I kind of noticed this this issue where it's like, great everyone's using all these services. Everything is great, But costs are a little bit confusing, hard to manage and, you know, you know, scientifically, you know, I ran into, you know, Jr and his community out there because my community was having a need of like, you know, there's just not good tools, standards, no practices out there. And, you know, the Finau Foundation was working on these kind of great things. So we started definitely found a way to kind of work together and be under the same umbrella foundation, you know, under the under Linux Foundation. In my personal opinion, I see more and more standards and tools to be created in this space. You know, there's, you know, very few specifications or standards and trying to get cost, you know, data out of different clouds and tools out there, I predict, Ah, lot more work is going to be done. Um, in this space, whether it's done and defendants foundation itself, CNC f, I think will probably be, uh, collaboration amongst communities. Can I truly figure this out? So, uh, engineers have any easier understanding of, you know, if I spent up the service or experiment? How much is this actually going to potentially impact the cost of things and and for a while, You know, uh, engineers just don't think about this. When I was at Twitter, we spot up services all time without really care about cost on, and that's happening a lot of small companies now, which don't necessarily have as a big bucket. So I'm excited about the space. I think you're gonna see a huge amount of focus on cloud financial management drops in the near future. >>Chris, thanks for that great insight. I think you've got a great perspective. You know, in some cases, it's a fast and loose environment. Like Twitter. You mentioned you've got kind of a blank check and the rocket ships going. But, Jr, this brings up to kind of points. This kind of like the whole code side of it. The software piece where people are building code, but also this the human error. I mean, we were playing with clubs, so we have a big media cloud and Amazon and we left there. One of the buckets open on the switches and elemental. We're getting charged. Massive amounts for us cash were like, Wait a minute, not even using this thing. We used it once, and it left it open. It was like the water was flowing through the pipes and charging us. So you know, this human error is throwing the wrong switch. I mean, it was simply one configuration error, in some cases, just more about planning and thinking about prototypes. >>Yeah. I mean, so take what your experience there. Waas and multiply by 1000 development teams in a big organization who all have access to cloud. And then, you know, it's it's and this isn't really about a set of new technologies. It's about a new set of processes and a cultural change, as Chris mentioned, you know, engineers now thinking about cost and this being a whole new efficiency metric for them to manage, right? You know, finance teams now see this world where it's like tomorrow. The cost could go three x the next day they could go down. You've got, you know, things spending up by the second. So there's a whole set of cross functional, and that's the majority of the work that are members do is really around. How do we get these cross functional teams working together? How do we get you know, each team up leveled on what they need, understand with cloud? Because not only is it, you know, highly variable, but it's highly decentralized now, and we're seeing, you know, cloud hit. These sort of material spend levels where you know, the big, big cloud spenders out there spending, you know, high nine figures in some cases you know, in cloud and it's this material for their for their businesses. >>And let's just let's be honest. Here is like Clouds, for the most part, don't really have a huge incentive in offering limits and so on. It's just, you know, like, hey, the more usage that the better And hopefully getting a group of practitioners in real figures. Well, holy put pressure to build better tools and services in this area. I think actually it is happening. I think Jared could correct me if wrong. I think AWS recently announced a feature where I think it's finally like quotas, you know, enabled, you know, you have introducing quotas now for and building limits at some level, which, you know, I think it's 2020 Thank you know, >>just to push back a little bit in support of our friends, you ask Google this company, you know, for a long time doing this work, we were worried that the cloud would be like, What are you doing? Are you trying to get our trying to minimize commitments and you know the dirty secret of this type of work? And I were just talking a bunch of practitioners today is that cloud spend never really goes down. When you do this work, you actually end up spending more because you know you're more comfortable with the efficiency that you're getting, and your CEO is like, let's move more workloads over. But let's accelerate. Let's let's do Maurin Cloud goes out more data centers. And so the cloud providers air actually largely incentivized to say, Yeah, we want people to be officially don't understand this And so it's been a great collaboration with those companies. As you said, you know, aws, Google, that you're certainly really focused in this area and ship more features and more data for you. It's >>really about getting smart. I mean, you know, they no, >>you could >>do it. I mean, remember the old browser days you could switch the default search engine through 10 menus. You could certainly find the way if you really wanted to dig in and make policy a simple abstraction layer feature, which is really a no brainer thing. So I think getting smarter is the right message. I want to get into the synergy Chris, between this this trend, because I think this points to, um kind of what actually happened here if you look at it at least from my perspective and correct me if I'm wrong. But you had jr had a community of practitioners who was sharing information. Sounds like open source. They're talking and sharing, you know? Hey, don't throw that switch. Do This is the best practice. Um, that's what open communities do. But now you're getting into software. You have to embed cost management into everything, just like security I mentioned earlier. So this trend, I think if you kind of connect the dots is gonna happen in other areas on this is really the synergy. Um, I getting that right with CNC >>f eso The way I see it is, and I dream of a future where developers, as they develop software, will be able to have some insight almost immediately off how much potential, you know, cost or impact. They'll have, you know, on maybe a new service or spinning up or potentially earlier in the development cycle saying, Hey, maybe you're not doing this in a way that is efficient. Maybe you something else. Just having that feedback loop. Ah lot. You know, closer to Deb time than you know a couple weeks out. Something crazy happens all of a sudden you notice, You know, based on you know, your phase or financial folks reaching out to you saying, Hey, what's going on here? This is a little bit insane. So I think what we'll see is, as you know, practitioners and you know, Jr spinoffs, foundation community, you know, get together share practices. A lot of them, you know, just as we saw on sense. Yeah, kind of build their own tools, models, abstractions. And, you know, they're starting to share these things. And once you start sharing these things, you end up with a you know, a dozen tools. Eventually, you know, sharing, you know, knowledge sharing, code sharing, you know, specifications. Sharing happens Eventually, things kind of, you know, become de facto tools and standards. And I think we'll see that, you know, transition in the thin ops community over the next 12 to 4 months. You know, very soon in my thing. I think that's kind of where I see things going, >>Jr. This really kind of also puts a riel, you know, spotlight and illustrates the whole developer. First cliche. I mean, it's really not a cliche. It's It's happening. Developers first, when you start getting into the calculations of our oi, which is the number one C level question is Hey, what's the are aware of this problem Project or I won't say cover your ass. But I mean, if someone kind of does a project that it breaks the bank or causes a, you know, financial problem, you know, someone gets pulled out to the back would shed. So, you know, here you're you're balancing both ends of the spectrum, you know, risk management on one side, and you've got return on investment on the other. Is that coming out from the conversation where you guys just in the early stages, I could almost imagine that this is a beautiful tailwind for you? These thes trends, >>Yeah. I mean, if you think about the work that we're doing in our practice you're doing, it's not about saving money. It's about making money because you actually want empower those engineers to be the innovation engines in the organization to deliver faster to ship faster. At the same time, they now can have, you know, tangible financial roo impacts on the business. So it's a new up leveling skill for them. But then it's also, I think, to Christmas point of, you know, people seeing this stuff more quickly. You know what the model looks like when it's really great is that engineers get near real time visibility into the impact of their change is on the business, and they can start to have conversations with the business or with their finance partners about Okay, you know, if you want me to move fast, I could move fast, But it's gonna cost this if you want me to optimize the cost. I could do that or I can optimize performance. And there's actually, you know, deeper are like conversation the candidate up. >>Now I know a lot of people who watch the Cube always share with me privately and Chris, you got great vision on this. We talked many times about it. We're learning a lot, and the developers are on the front lines and, you know, a lot of them don't have MBAs and, you know they're not in the business, but they can learn quick. If you can code, you can learn business. So, you know, I want you to take a minute Jr and share some, um, educational knowledge to developers were out there who have to sit in these meetings and have to say, Hey, I got to justify this project. Buy versus build. I need to learn all that in business school when I had to see s degree and got my MBA, so I kind of blended it together. But could you share what the community is doing and saying, How does that engineer sit in the meeting and defend or justify, or you some of the best practices what's coming out of the foundation? >>Yeah, I mean, and we're looking at first what a core principles that the whole organization used to line around. And then for each persona, like engineers, what they need to know. So I mean, first and foremost, it's It's about collaboration, you know, with their partners andan starting to get to that world where you're thinking about your use of cloud from a business value driver, right? Like, what is the impact of this? The critical part of that? Those early decentralization where you know, now you've got everybody basically taking ownership for their cloud usage. So for engineers, it's yes, we get that information in front of us quickly. But now we have a new efficiency metric. And engineers don't like inefficiency, right? They want to write fishing code. They wanna have efficient outcomes. Um, at the same time, those engineers need to now, you know, have ah, we call it, call it a common lexicon. Or for Hitchhiker's Guide to the Galaxy, folks. Ah, Babel fish that needs to be developed between these teams. So a lot of the conversations with engineers right now is in the foundation is okay. What What financial terms do I need to understand? To have meaningful conversations about Op X and Capex? And what I'm going to make a commitment to a cloud provider like a committed use discount, Google or reserved instance or savings Planet AWS. You know, Is it okay for me to make that? What? How does that impact our, you know, cost of capital. And then and then once I make that, how do I ensure that I could work with those teams to get that allocated and accounted? The right area is not just for charge back purposes, but also so that my teams can see my portion of the estate, right? And they were having the flip side of that conversation with all the finance folks of like, You need to understand how the variable cloud, you know, model works. And you need to understand what these things mean and how they impact the business. And then all that's coming together. And to the point of like, how we're working with C and C f you know, into best practices White papers, you know, training Siri's etcetera, sets of KP eyes and capabilities. Onda. All these problems have been around for years, and I wouldn't say they're solved. But the knowledge is out there were pulling it together. The new level that we're trying to talk with the NCF is okay. In the old world of Cloud, you had 1 to 1 use of a resource. You're running a thing on an instance in the new world, you're running in containers and that, you know, cluster may have lots of pods and name spaces, things inside of it that may be doing lots of different workloads, and you can no longer allocate. I've got this easy to instance and this storage to this thing it's now split up and very ephemeral. And it is a whole new layer of virtualization on top of virtual ization that we didn't have to deal with before. >>And you've got multiple cloud. I'll throw that in there, just make another dimension on it. Chris, tie this together cause this is nice energy to scale up what he's built with the community now, part of the Linux Foundation. This fits nicely into your vision, you know, perfectly. >>Yeah, no, 100% like, you know, so little foundation. You know, as you're well, well aware, is just a federation of open source foundations of groups working together to share knowledge. So it definitely fits in kind of the little foundation mission of, you know, building the largest share technology investment for, you know, humankind. So definitely good there with my kind of C and C f c T o hat, you know, on is, you know, I want to make sure that you know, you know my community and and, you know, the community of cloud native has access and, you know, knowledge about modern. You know, cloud financial management practices out there. If you look at some of the new and upcoming projects in ciencia things like, you know, you know, backstage, which came out of Spotify. They're starting to add functionality that, you know, you know, originally backstage kind of started out as this, you know, everyone builds their own service catalog to go catalog, and you know who owns what and, you know and all that goodness and developers used it. And eventually what happened is they started to add cost, you know, metrics to each of these services and so on. So it surfaces things a little bit closer, you know, a depth time. So my whole goal is to, you know, take some of these great, you know, practices and potential tools that were being built by this wonderful spinoffs community and trying to bring it into the project. You know, front inside of CNC F. So having more projects either exposed, you know, useful. You know, Finn, ops related metrics or, you know, be able to, you know, uh, you know, tool themselves to quickly be able to get useful metrics that could be used by thin ox practitioners out there. That's my kind of goal. And, you know, I just love seeing two communities, uh, come together to improve, improve the state of the world. >>It's just a great vision, and it's needed so and again. It's not about saving money. Certainly does that if you play it right, but it's about growth and people. You need better instrumentation. You need better data. You've got cloud scale. Why not do something there, right? >>Absolutely. It's just maturity after the day because, you know, a lot of engineers, you know, they just love this whole like, you know, rental model just uses many Resource is they want, you know, without even thinking about just basic, you know, metrics in terms of, you know, how many idle instances do I have out there and so, like, people just don't think about that. They think about getting the work done, getting the job done. And if they anything we do to kind of make them think a little bit earlier about costs and impact efficiency, charge back, you know, I think the better the world isn't Honestly, you know, I do see this to me. It's It's almost like, you know, with my hippie hat on. It's like Stephen Green or for the more efficient we are. You know, the better the world off cloud is coming. Can you grow? But we need to be more efficient and careful about the resource is that we use in sentencing >>and certainly with the pandemic, people are virtually you wanted mental health, too. I mean, if people gonna be pulling their hair out, worrying about dollars and cents at scale, I mean, people are gonna be freaking out and you're in meetings justifying why you did things. I mean, that's a time waster, right? I mean, you know, talking about wasting time. >>I have a lot of friends who, you know, run infrastructure at companies. And there's a lot of you know, some companies have been, you know, blessed during this, you know, crazy time with usage. But there is a kind of laser focused on understanding costs and so on and you not be. Do not believe how difficult it is sometimes even just to get, you know, reporting out of these systems, especially if you're using, you know, multiple clouds and multiple services across them. It's not. It's non trivial. And, you know, Jared could speak to this, But, you know, a lot of this world runs in like terrible spreadsheets, right and in versus kind of, you know, nice automated tools with potential, a p I. So there's a lot of this stuff. It's just done sadly in spreadsheets. >>Yeah, salute the flag toe. One standard to rally around us. We see this all the time Jr and emerging inflection points. No de facto kind of things develop. Kubernetes took that track. That was great. What's your take on what he just said? I mean, this is a critical path item for people from all around. >>Yeah, and it's It's really like becoming this bigger and bigger data problem is well, because if you look at the way the clouds are building, they're building per seconds and and down to the very fine grain detail, you know, or functions and and service. And that's amazing for being able to have accountability. But also you get people with at the end of the month of 300 gigabyte billing files, with hundreds of millions of rows and columns attached. So, you know, that's where we do see you companies come together. So yeah, it is a spreadsheet problem, but you can now no longer open your bill in a spreadsheet because it's too big. Eso you know, there's the native tools are doing a lot of work, you know, as you mentioned, you know, AWS and Azure Google shipping a lot. There's there's great, you know, management platforms out there. They're doing work in this area, you know, there's there's people trying to build their own open source the things like Chris was talking about as well. But really, at the end of the day like this, this is This is not a technology. Changes is sort of a cultural shift internally, and it's It's a lot like the like, you know, move from data center to cloud or like waterfall to Dev ops. It's It's a shift in how we're managing, you know, the finances of the money in the business and bringing these groups together. So it it takes time and it takes involvement. I'm also amazed I look like the job titles of the people who are plugged into the Phenoms Foundation and they range from like principal engineers to tech procurement. Thio you know, product leaders to C. T. O. S. And these people are now coming together in the classic to get a seat at the table right toe, Have these conversations and talk about not How do we reduce, you know, cost in the old eighties world. But how do we work together to be more quickly to innovate, to take advantage of these cognitive technologies so that we could be more competitive? Especially now >>it's automation. I mean, all these things are at play. It's about software. I mean, software defined operations is clearly the trend we've been covering. You guys been riding the wave cloud Native actually is so important in all these modern APS, and it applies to almost every aspect of stacks, so makes total sense. Great vision. Um, Chris props to you for that, Jr. Congratulations on a great community, Jerry. I'll give you the final word. Put a plug in for the folks watching on the fin ops Foundation where you're at. What are you looking to do? You adding people, What's your objectives? Take a minute to give the plug? >>Yeah, definitely. We were in open source community, which means we thrive on people contributing inputs. You know, we've got now almost 3000 practitioner members, which is up from 1500 just this this summer on You know, we're looking for those who have either an interesting need to plug into are checked advisory council to help define standards as part of this event, The cognitive gone we're launching Ah, white paper on kubernetes. Uh, and how to do confidential management for it, which was a collaborative effort of a few dozen of our practitioners, as well as our vendor members from VM Ware and Google and APP Thio and a bunch of others who have come together to basically defined how to do this. Well, and, you know, we're looking for folks to plug into that, you know, because at the end of the day, this is about everybody sort of up leveling their skills and knowledge and, you know, the knowledge is out there, nobody's head, and we're focused on how toe drive. Ah, you know, a central collection of that be the central community for it. You enable the people doing this work to get better their jobs and, you know, contribute more of their companies. So I invite you to join us. You know, if your practitioner ITT's Frito, get in there and plug into all the bits and there's great slack interaction channels where people are talking about kubernetes or pinups kubernetes or I need to be asked Google or where we want to go. So I hope you consider joining in the community and join the conversation. >>Thanks for doing that, Chris. Good vision. Thanks for being part of the segment. And, as always, C N C F. This is an enablement model. You throw out the soil, but the 1000 flowers bloom. You don't know what's going to come out of it. You know, new standards, new communities, new vendors, new companies, some entrepreneur Mike jump in this thing and say, Hey, I'm gonna build a better tool. >>Love it. >>You never know. Right? So thanks so much for you guys for coming in. Thanks for the insight. Appreciate. >>Thanks so much, John. >>Thank you for having us. >>Okay. I'm John Furry, the host of the Cube covering Coop Con Cloud, Native Con 2020 with virtual This year, we wish we could be there face to face, but it's cute. Virtual. Thanks for watching

>> Man: from around the globe, it's "theCUBE" with coverage of "Kubecon" and "CloudNativeCon Europe 2020", virtual. Brought to you by Red Hat, the cloud native computing foundation and ecosystem partners. >> Welcome back, I'm Stu Miniman, and this is "theCUBE's" coverage of KubeCon CloudNativeCon Europe 2020, the virtual edition of course, it, this ecosystem has been bustling, a lot of activity in the five years that we've been covering it with "theCUBE" we've watched very much the maturation of what's going on. Remember, in the early days, it was open source projects, companies pulling all the pieces together. Now, there's a lot more things to choose from lots of projects, not just Kubernetes, but all the other pieces, and still lots of new innovations and new startups coming into the space. So happy to welcome to the program, have two first time guests from Spectro Cloud, first of all, we have the co founder and CEO Tenry Fu, and also Tina Notle who's the Vice President of product, Tina and Tenry, thank you so much for joining us. >> Thank you for having us. >> Likewise. >> All right, so Tenry, as one of the co founders, I want to understand, you know, why Spectro Cloud? Why now, you know, many outsiders, would they have said for a while, you know, Kubernetes, it's just getting baked into all of the environment. They looked at all the platforms, whether you're talking, you know, Google and AWS or VMware, they all have their platforms, they all have their managed services offering. So help us understand, what your team does and how you differentiate from what's already existing. >> Absolutely yeah, so I actually used to work at VMware, I, and then, I saw clouds taking off right and then I left VMware, to start my first startup called CliQr Technologies, which focus on multicloud management. But at that time, really, multicloud management through a single pane of glass is obviously right, and then clicker later acquired by Cisco. So at Cisco, I kind of witness The Container and Kubernetes taking off, right? And it makes a lot of sense, right for the first time both the application workloads and infrastructure became truly portable across multiple environments, but also very interestingly at Cisco I observed there are many developer teams, right? That is adopting Kubernetes and everyone is doing a little bit different things, that because different teams, they have a different stack constructor requirements, like some for AI/ML, some, they need a different base OS, some they just don't want to have a different version, and a lot of existing solutions doesn't really provide this kind of flexibility to satisfy all the different needs, right? one size fit all, typically is a one size fit for nothing. So we asked ourselves, why can't we try to create a platform that will give people the flexibility, but not turning it into a DIY project, right, still have a full manageability, so that user don't need to worry about the upgrade, Day Two operations, governance so and so forth. >> Yeah to Tina, I know when I've looked at your product, it's discussed as layers, which my background's in networking. So I love seeing things visually and understanding the pieces as they lay out the stack. So maybe help us understand a little bit as to, you know, that the flexibility that you give and how it's not just the Paradox of Choice, just too many options out there and you know, developers left to create their own mess that they can't then support. (laughing) >> Yeah, so you know, as Tenry mentioned, offering folks flexibility without turning into a do it yourself, you know, hot mess is what we're what we're helping People do at Spectrol Cloud, the core of our solution, the core of the differentiation within our solution is around this concept of a cluster profile, and as you mentioned, cluster profile basically allows people to define in a layered fashion, what's part of their Kubernetes infrastructure stack? So at the bottom, you're talking, what's the base operating system? What's the version of Kubernetes, that's going to be part of clusters that uses profile? What's your networking and storage interface look like? And then on top of that, you have a number of optional layers. So again, you know, back to flexibility manageability, we give people options around what those other layers look like on top. They include everything from security, logging, monitoring, etc, just anything that you want to go ahead and kind of bake into a definition, a profile of what a cluster should look like in one of your deployed environments. >> All right, well, Want to make sure I understand when you talk about Kubernetes in there, can it be, you know, say VMware with Vsphere7, now has Kubernetes support. Red Hat open shift is an option, all of the cloud players have their, you know, AKS, EKS. And they're like, can I bake that Kubernetes in or are you taking a different approach? >> We're going with upstream vanilla Kubernetes today, that allows us to go ahead and provide what's newest within the ecosystem, and let people go ahead and have a really open, really open solution that's replying. >> Okay, so when I talk to, when you look out there, a lot of companies are saying how can I manage multiple clusters? So if you look at what Google, Microsoft and VMware, they're talking about, we can manage our clusters and we can also help you with those other clusters. How does that impact Tenry, your Solution, doesn't it need to be, it's just the upstream solution that I put into that cluster profile, or can I connect to, say a managed cloud solution? >> Yeah, so I think in terms the multi class management or the consistency is really the key, right. So through this class profile concept, not only it can be used as the initial template to deploy a cluster, but it can also use as a single source for choose, to drive the cluster Lifecycle Management income upgrade. So right now, as Tina mentioned, we primarily focus on upstream, so that we want to provide the maximum flexibility in terms of our end to end Kubernetes stack. But we do also have a plan, that down the road that we go into in Brownfield existing clusters. So that enterprise, existing investment to their Kubernete infrastructure can be under managed by us. >> Well there always reaches a time when the brand new technology gets called Brownfield. I think that's the first time I've heard something like, you know, EKS or the like, you know, referred to as Brownfield. Tina, you know, when I think back to my history with integrated solutions, obviously, if I have the various pieces, it should be easier for me to stay on the latest make upgrades, roll things forward or roll things back, but you know, what, give us if you could some of the, the key values of, you know, building these cluster profiles, what that enables for your customers. >> So the key around cluster profiles, we offer this policy based management, so you describe as an administrator, what it is that those clusters need to look like, right? And we've got, we adopt a declarative desired state, you know, management approach along what Kubernetes does itself, and so what you're able to get through adopting, utilize cluster profiles, is this guarantee that from deployment and then into day two as well, what you've described in this profile, winds up maintaining itself, it remains true of the clusters that have been deployed. So what it is that you require as far as the operating system, what is required as far as some configuration options, etc. So the profile itself winds up being ground source of truth and around what it is that you've got running at all these various locations, across clouds, across different clusters, etc. >> All right. Tenry, you mentioned that having things more standardized is going to help customers, absolutely, we saw that in data centers for a long time, and standardized, how do you help customers make sure that the configuration that they build are going to work, are going to be stable, if they make changes that they're not going to get things out of sync. Is there you know, interoperability matrix or some other ways that we're trying to make sure that customers, you know, stay on the rails, if you will. >> Absolutely right, So through our system, right, all the integration points, we carry the additional metadata, right to basically give the hint about compatibility, resource constraints, right, and also the upgradability, in terms of moving from one version to another. So this way, we can kind of give you some guidance, when they initially construct a class profile, what will work together nicely and then what will not, right. And then on top of that, when upgrading from one existing cluster to a new version of a class profile definition, then we can look at the environment, right to understand, right, if there's something that potentially incompatible will popping up right, so we call that pre pilot integration, check right and also post deployment, we also allow user to run additional conformance tests. So that make sure the cluster everything is actually is still acting as as it's supposed to be. >> Another way to explain that is that you know, the cluster profile concept has a lot of flexibility attached with to it, right? That's a lot of power, it can get you into trouble if you don't have the right safety nets and safety harnesses underneath you. So we have a multi layered approach to helping make sure that people are getting benefit out of that flexibility. >> Wonderful and I'm wondering did, when you've had more customers using this, is their shared information, and if there're community guidelines that help, you know, understand when it's going to be okay, hey, 1.19's out, we're looking at 1.20. You might want to do this or hey, if you're using this piece of networking, you might want to wait a little bit before you go to the next version. >> That's definitely the idea over time, folks that are engaging with us, are very interested in the fact that, because of the fact that we're SaaS management platform, SaaS space management platform today, that it offers them the opportunity to learn from their peers, if you will, right, and their peers experiences. On top of that, we also have the ability to watch just what's been going on in other deployments in the Kubernetes ecosystem and we can make sure that all that's available, as Tenry mentioned, you know, in the form of the metadata that's on top of those packs. >> All right, how about how do you price this solution? When I look out there, I talked about Kubernetes baked into all the platforms, oftentimes, it can be baked into ELA, It's part of, you know, my just general cloud spend from that platform. So how do you do the pricing and, you know, are you plugged into any of the cloud marketplaces yet? >> Yeah, so flexibility is really part of our DNA. So even for pricing, we want to provide the maximum flexibility to our customer. So unlike some traditional solution typically is priced based on number of pause, right, a year, or even number of nodes, right. So we actually price based on number of CPU cores of all workers node under management by hour. So what we call those, core hour under management, right, and then every thousand core hours at one unit, we call kilo core hours. So kind of similar to how electricity is consumed, right, so this way, based on these core hour consumption, we allow user to either pay as you go as amongst the on demand plan, or you can do an annual commitment. >> And we are in process on the marketplaces. >> Yeah. >> All right, how about, we talked about Kubernetes, I think service mesh are part of it. What in this Kube, kubecon cloud native con ecosystem, which projects are the most tied into what you're doing anything that specter cloud is particularly contributing to that you can share? >> Yeah, so our system is built on top of Kubernetes cluster API project. So we are one of the contributor to class API, we are actively adding additional functionality to enhance class API, especially by in some other VMware environment for some custom use case, such as static IP or some special placement behaviors, and also adding additional contribute on different cloud support. >> Yeah, and as far as things that we're watching, and clearly we're, we've seen a dramatic increase in the number of people on our customer front that are interested in actual deployment, of service mesh now. So that's something that you know, we're going to be more engaged in over time. And another one that we're hoping to see, check out more talks around Kubecon is AI ML, right? A lot of interest on the part of customers around AIML use cases. >> Yeah, absolutely edge and AI and ML. Definitely very hot topics to conversation this year at the, at the Europe show, expect that to continue. Tina, I'm wondering, do you have any customer examples, maybe even anonymized that could kind of just explain the key values that your customers are seeing using your solution? >> Yeah, sure, so we've got one of our earliest customers is a Canadian financial, who came to us because, they were looking to figure out how to manage consistently at scale, and they have the problem that Tenry described earlier, around, I've got different development teams, they have different needs, and you know, how do you satisfy all those guys without going crazy, right? They've got an AIML use case, that's a special snowflake they've got two separate teams in different groups that would like to be under an IT management umbrella. That's a convergence use case that they're looking at, so kind of a typical example of somebody that we think of is, you know, a really good set of people for us to be having conversations with. We've also been working with a telecom provider that it's in a similar, similar vein actually, there's an AIML, there are multiple teams of different infrastructure, and they want to be able to consistently manage it's a story that we're seeing over and over again, thankfully. >> Yeah, we also see right from I think, at individual group or team level, right. There are a lot of, kind of a product owner or data scientists that they really want to have a kind of an easy button to quickly be able to provision Kubernetes clusters that suit for their need, right. And a lot of these groups, their primary focus is really the application, right? It's not their interest to spend a lot of time and resource on Kubernete management, in terms of deploying update, or secure an operation. So through us, they can very easily spin up a Kubernetes cluster, whether it's for AIML or for developing experiment, they can very quickly do that But with the flexibility, because a lot of existing solution, they may limit the version of Kubernetes clusters, they may limit the what kind of integration they can do. >> Yeah, Tenry you, we talked a little bit earlier about, you know, potential integration down the road. I'm curious, just there's so many companies creating innovations out there, you know, say for example, one that I hear a lot of feedback on is AWS now has far gate support for their EKS offering. Is that Something down the line you should look at or do you have some guidance as to how customers should be thinking about that, and if they want that kind of functionality, how they would get that with a solution like yours? >> Yeah, actually, we really share the same vision as AWS, right. So we believe, ultimately is the infrastructure really should be transparent to application developers, right, and it should be boundary-less. So our goal is not only manage Kubernetes, across multiple environment, but eventually we will be able to link all these cluster together, to make them acting as a single infrastructure. So developers, they can still use their familiar Kubernetes interface to deploy and manage their application, but without worrying about the how infrastructure underneath is operated or managed, right. So this in a way will eventually become kind of a phallic model, but across multiple cluster and multiple clouds. >> Alright, Tina, if maybe if you could give us the final takeaway, people attending Kubecon, cloud native con, what's the one thing that if you know they have a problem, they should be coming to Spectro cloud to hear more about? >> Yeah, sure so what Spectrol cloud aims to do is help enterprises not have to trade off between flexibility and control of their infrastructure, and manageability of use that stuff's that's the main, the main thing that we would like people to remember. >> All right, well Tenry and Tina, thank you so much for sharing with our community a little bit about Specter Cloud great talking to you and look forward to hearing more in the future. >> Thanks so much. >> Thank you too. >> All right, and stay tuned more coverage from Kubecon Cloud Native Con 2020. I'm Stu MiniMan and thank you, for watching "theCUBE." (light music)

(upbeat music) >> From around the globe, it's theCUBE with coverage of KubeCon and CloudNativeCon Europe 2020 Virtual brought to you by Red Hat, the Cloud Native Computing Foundation, and the ecosystem partners. >> Hi, and welcome back to theCUBE's coverage of KubeCon + CloudNativeCon 2020 in Europe, of course, the virtual edition. I'm Stu Miniman, and happy to welcome you back to the program. One of the keynote speakers is also a board member of the CNCF, Vijoy Pandey, who is the Vice President and Chief Technology Officer for Cloud at Cisco. Vijoy, nice to see you, thanks so much for joining us. >> Hi there, Stu, so nice to see you again. It's a strange setting to be in, but as long as we are both healthy, everything's good. >> Yeah, we still get to be together a little bit even though while we're apart. We love the the engagement and interaction that we normally get to the community, but we just have to do it a little bit differently this year. So we're going to get to your keynote. We've had you on the program to talk about "Networking, Please Evolve". I've been watching that journey. But why don't we start at first, you've had a little bit of change in roles and responsibility. I know there's been some restructuring at Cisco since the last time we got together. So give us the update on your role. >> Yeah, so let's start there. So I've taken on a new responsibility. It's VP of Engineering and Research for a new group that's been formed at Cisco. It's called Emerging Tech and Incubation. Liz Centoni leads that and she reports on to Chuck. The charter for the team, this new team, is to incubate the next bets for Cisco. And if you can imagine, it's natural for Cisco to start with bets which are closer to its core business. But the charter for this group is to move further and further out from Cisco's core business and take Cisco into newer markets, into newer products, and newer businesses. I'm running the engineering and resource for that group. And again, the whole deal behind this is to be a little bit nimble, to be a little bit, to startupy in nature, where you bring ideas, you incubate them, you iterate pretty fast, and you throw out 80% of those, and concentrate on the 20% that makes sense to take forward as a venture. >> Interesting. So it reminds me a little bit but different, I remember John Chambers, a number of years back, talking about various adjacencies trying to grow those next multi-billion dollar businesses inside Cisco. In some ways, Vijoy, it reminds me a little bit of your previous company, very well known for driving innovation, giving engineers 20% of their time to work on things, maybe give us a little bit insight, what's kind of an example of a bet that you might be looking at in this space, bring us in tight a little bit. >> Well, that's actually a good question. And I think a little bit of that comparison is all those conversations are taking place within Cisco as well as to how far out from Cisco's core business do we want to get when we're incubating these bets? And yes, my previous employer, I mean, Google X actually goes pretty far out when it comes to incubations, the core business being primarily around ads, now Google Cloud as well. But you have things like Verily and Calico, and others, which are pretty far out from where Google started. And the way we're looking at the these things within Cisco is, it's a new muscle for Cisco, so we want to prove ourselves first. So the first few bets that we are betting upon are pretty close to Cisco's core but still not fitting into Cisco's BU when it comes to, go to market alignment or business alignment. So one of the first bets that we're taking into account is around API being the queen when it comes to the future of infrastructure, so to speak. So it's not just making our infrastructure consumable as infrastructure as code but also talking about developer relevance, talking about how developers are actually influencing infrastructure deployments. So if you think about the problem statement in that sense, then networking needs to evolve. And I've talked a lot about this in the past couple of keynotes, where Cisco's core business has been around connecting and securing physical endpoints, physical I/O endpoints, wherever they happen to be, of whatever type they happen to be. And one of the bets that we are, actually two of the bets, that we're going after is around connecting and securing API endpoints, wherever they happen to be, of whatever type they happen to be. And so API networking or app networking is one big bet that we're going after. Another big bet is around API security. And that has a bunch of other connotations to it, where we think about security moving from runtime security, where traditionally Cisco has played in that space, especially on the infrastructure side, but moving into API security, which is earlier in the development pipeline, and higher up in the stack. So those are two big bets that we're going after. And as you can see, they're pretty close to Cisco's core business, but also are very differentiated from where Cisco is today. And once you prove some of these bets out, you can walk further and further away, or a few degrees away from Cisco's core. >> All right, Vijoy, why don't you give us the update about how Cisco is leveraging and participating in open source? >> So I think we've been pretty, deeply involved in open source in our past. We've been deeply involved in Linux Foundation Networking. We've actually chartered FD.io as a project there and we still are. We've been involved in OpenStack, we have been supporters of OpenStack. We have a couple of products that are around the OpenStack offering. And as you all know, we've been involved in CNCF, right from the get-go, as a foundation member. We brought NSM as a project. I had Sandbox currently, but we're hoping to move it forward. But even beyond that, I mean, we are big users of open source, a lot of those has offerings that we have from Cisco, and you will not know this if you're not inside of Cisco. But Webex, for example, is a big, big user of Linkerd, right from the get-go, from version 1.0, but we don't talk about it, which is sad. I think, for example, we use Kubernetes pretty deeply in our DNAC platform on the enterprise side. We use Kubernetes very deeply in our security platforms. So we're pretty good, pretty deep users internally in our SaaS products. But we want to press the accelerator and accelerate this whole journey towards open source, quite a bit moving forward as part of ET&I, Emerging Tech and Incubation, as well. So you will see more of us in open source forums, not just CNCF, but very recently, we joined the Linux Foundation for Public Health as a premier foundational member. Dan Kohn, our old friend, is actually chartering that initiative, and we actually are big believers in handling data in ethical and privacy-preserving ways. So that's actually something that enticed us to join Linux Foundation for Public Health, and we will be working very closely with Dan and foundational companies that do not just bring open source but also evangelize and use what comes out of that forum. >> All right, well, Vijoy, I think it's time for us to dig into your keynote. We've we've spoken with you in previous KubeCons about the "Network, Please Evolve" theme that you've been driving on. And big focus you talked about was SD-WAN. Of course, anybody that's been watching the industry has watched the real ascension of SD-WAN. We've called it one of those just critical foundational pieces of companies enabling multi-cloud. So help explain to our audience a little bit, what do you mean when you talk about things like Cloud Native SD-WAN and how that helps people really enable their applications in the modern environment? >> Yes, well, I mean, we've been talking about SD-WAN for a while. I mean, it's one of the transformational technologies of our time where prior to SD-WAN existing, you had to stitch all of these MPLS labels and actually get your connectivity across to your enterprise or branch. And SD-WAN came in and changed the game there, but I think SD-WAN, as it exists today, is application-unaware. And that's one of the big things that I talk about in my keynote. Also, we've talked about how NSM, the other side of the spectrum, is how NSM or Network Service Mesh has actually helped us simplify operational complexities, simplify the ticketing and process health that any developer needs to go through just to get a multi-cloud, multi-cluster app up and running. So the keynote actually talked about bringing those two things together, where we've talked about using NSM in the past in chapter one and chapter two. And I know this is chapter three, and at some point, I would like to stop the chapters. I don't want this like an encyclopedia of "Networking, Please Evolve". But we are at chapter three, and we are talking about how you can take the same consumption models that I talked about in chapter two, which is just adding a simple annotation in your CRD, and extending that notion of multi-cloud, multi-cluster wires within the components of our application, but extending it all the way down to the user in an enterprise. And as we saw an example, Gavin Belson is trying to give a keynote holographically and he's suffering from SD-WAN being application-unaware. And using this construct of a simple annotation, we can actually make SD-WAN cloud native, we can make it application-aware, and we can guarantee the SLOs, that Gavin is looking for, in terms of 3D video, in terms of file access for audio, just to make sure that he's successful and Ross doesn't come in and take his place. >> Well, I expect Gavin will do something to mess things up on his own even if the technology works flawlessly. Vijoy, the modernization journey that customers are on is a never-ending story. I understand the chapters need to end on the current volume that you're working on, but we'd love to get your viewpoint. You talk about things like service mesh, it's definitely been a hot topic of conversation for the last couple of years. What are you hearing from your customers? What are some of the kind of real challenges but opportunities that they see in today's cloud native space? >> In general, service meshes are here to stay. In fact, they're here to proliferate to some degree, and we are seeing a lot of that happening, where not only are we seeing different service meshes coming into the picture through various open source mechanisms. You've got Istio there, you've Linkerd, you've got various proprietary notions around control planes like App Mesh, from Amazon, there's Consul, which is an open source project, but not part of CNCF today. So there's a whole bunch of service meshes in terms of control planes coming in. Envoy is becoming a de facto sidecar data plane, whatever you would like to call it, de facto standard there, which is good for the community, I would say. But this proliferation of control planes is actually a problem. And I see customers actually deploying a multitude of service meshes in their environment, and that's here to stay. In fact, we are seeing a whole bunch of things that we would use different tools for, like API gateways in the past, and those functions actually rolling into service meshes. And so I think service meshes are here to stay. I think the diversity of service meshes is here to stay. And so some work has to be done in bringing these things together. And that's something that we are trying to focus in on as well. Because that's something that our customers are asking for. >> Yeah, actually, you connected for me something I wanted to get your viewpoint on, go dial back, 10, 15 years ago, and everybody would say, "Oh, I really want to have a single pane of glass "to be able to manage everything." Cisco's partnering with all of the major cloud providers. I saw, not that long before this event, Google had their Google Cloud Show, talking about the partnership that you have with, Cisco with Google. They have Anthos, you look at Azure has Arc, VMware has Tanzu. Everybody's talking about really the kind of this multi-cluster management type of solution out there, and just want to get your viewpoint on this Vijoy as to how are we doing on the management plane, and what do you think we need to do as an industry as a whole to make things better for customers? >> Yeah, I think this is where I think we need to be careful as an industry, as a community and make things simpler for our customers. Because, like I said, the proliferation of all of these control planes begs the question, do we need to build something else to bring all these things together? I think the SMI proposal from Microsoft is bang on on that front, where you're trying to unify at least the consumption model around how you consume these service meshes. But it's not just a question of service meshes as you saw in the SD-WAN announcement back in the Google discussion that we just, Google conference that you just referred. It's also how SD-WANs are going to interoperate with the services that exist within these cloud silos to some degree. And how does that happen? And there was a teaser there that you saw earlier in the keynote where we are taking those constructs that we talked about in the Google conference and bringing it all the way to a cloud native environment in the keynote. But I think the bigger problem here is how do we manage this complexity of this pallet stacks? Whether it's service meshes, whether it's development stacks, or whether it's SD-WAN deployments, how do we manage that complexity? And single pane of glass is overloaded as a term, because it brings in these notions of big monolithic panes of glass. And I think that's not the way we should be solving it. We should be solving it towards using API simplicity and API interoperability. And I think that's where we as a community need to go. >> Absolutely. Well, Vijoy, as you said, the API economy should be able to help on these, the service architecture should allow things to be more flexible and give me the visibility I need without trying to have to build something that's completely monolithic. Vijoy, thanks so much for joining. Looking forward to hearing more about the big bets coming out of Cisco, and congratulations on the new role. >> Thank you, Stu. It was a pleasure to be here. >> All right, and stay tuned for lots more coverage of theCUBE at KubeCon + CloudNativeCon. I'm Stu Miniman. Thanks for watching. (upbeat music)

>>live from San Diego, California It's the Q covering Koopa and Cloud Native Cot brought to you by Red Cloud. Native Computing Pounding and its ecosystem March >>Welcome back. This is the cubes coverage. Fourth year of Q Khan Cloud native Khan, 2019 Here in San Diego. I am still Minutemen like co host for this afternoon is Justin Warrant and happy to welcome to the program A first time guests, but was on the keynote stage yesterday Sougou Super Marine, who is the co founder and CEO of Planet Scale and also one of the, uh, we're gonna be talking about the test which graduated, announced on the stage. They didn't put a cap and gown or roll everything out, which they did a couple of years ago. But first, thanks so much for joining us. And congratulations. Thank you. All right, so, Sougou, bring us back. You know, we're talking about a cloud native database and we'll dig into that and everything, but bring us back to what you were working on. And you know why of what we now call >>so the When we started with us, we were really not thinking of cloud native itself. for say, it was kind of a sequence of events that kind of forced with us to become cloud native long before cloud native was actually born as even the term was born. Which was when we had to move the test from YouTube on print into Google's board, which use the predecessor off Cooper natives. Um, the reason why the test is kind of one of the leading storage projects in Cloud Native was because it was probably the first project that remained open source, even though we managed to ram it with >>work. Yeah, you know what? One of things we've been talking about at the show here is you know, in the early days, you know, we were very much talking about infrastructure, but we know the reason we have infrastructure is to run applications, and one of the most important applications is databases, and I talk to customers. It's not just one database. Often they have many different databases on, and that is one of the big challenges today. So, you know, you kind of look at that landscape, help us understand how this fits into that. That overall picture. >>Yeah, so that kind of goes back in tow, Google's history and how that can influence kubernetes itself. So if you look at Google's board, most off its features are meant for running stateless application. So within Google, people who wrote applications when they wanted to store state they just called out into a service that was semi part of board but wasn't itself run by board as if you would run your application. So many of those properties were inherited by Cooper natives. So which is the reason why? Um, right from the beginning, it was hard to make storage work for cover natives on Dhe. For that reason, even a zoo recently as early this year, If you look at the tweets from Kelsey Hightower, don't just move your database into communities. You're going to regret it. People still say that, but at the same time, because we test way, we're able to figure out howto make storage work under the stringent rules that Borg had, which was mainly to support stateless applications. In other words, we actually land because, as if it was a stateless application, while still managing while still making state state will not survive this stateless behavior, which is actually why we just managed to be launched within communities as soon as it was born. Ah, but it has been a struggle for other people because they didn't have the luxury of preparing for it without even knowing. Uh so I think that more effort needs to be made on both sides, both from people who are writing storage to make them work with communities as well as kubernetes itself, trying to meet them halfway, trying to add features to help the storage developers. >>It has been a real struggle. I remember from even the very first show I came to four years ago in Seattle looking at the set. My media thing is an ex storage guy and has a backup guy was to go and look at things and say OK, this is lovely for stateless applications, you said. But riel applications have data in them and they need to maintain state. Where's the state looking at all of the group in any type of things, like there were no state full sets with another thing that has changed a lot in four years, and people have come to the party and we need to be able to manage state. But now that you we have a database like a test, isn't that just taking things to the point where I as an app developer, I can just write my stateless application and then my data can live inside a data management service like a test? So I don't actually need to deal with any of that state management problem myself. >>That's what it amounts to. Uh, the the one property of the test is that it can run both in communities and outside. So there are people who run tests on Prem and they have their own orchestration layer. So that has given some challenge where we just cannot depend on communities. You cannot call into communities a p I s o. The way we have the architect of the test is that it knows when it runs within a orchestrated environment, how to interact with it, but it doesn't assume that it exists. So >>why have you provided that functionality? Is that because customers said that I actually want to be able to run the test, But I don't wanna have to deal with kubernetes >>exactly like so not everyone has migrated to communities. It is surprising that everybody wants to migrate communities. But then many of them are saying, I don't know how many years out it is on. Then for them, we just solved a different problem, which is the problem of sheer massive scale ability on dhe for them. They want to be able to still run with us on print s. So for that reason, that is actually a small gap between communities and the test itself. On dhe, we're filling that gap with health charts in the open source on Dhe Planet Scale, which is the company that I founded has built an operator that we're also going to open source so that people can use that to launch community >>before we talk about planet scale You. No, no, no, no. Absolutely. In the keynote you had some customer stories on might might help illustrate some what we're talking about, you know, the scalability of the environment, everything. So you know, I'll let you choose that kind of a short example. You know, the slack One you know, is one that I think president in the audience there. But >>I would choose slack. Ah, Jerry's always obviously enormous, but I will choose slack and nozzle because they represent two very different but really genuine needs in the industry. Slack once not just massive scale, but they want flexibility with manipulating data on DDE. That is something that is manipulating data really, really hard. Onda. We believe that we found the secret sauce to make that work with tests, and that is the reason you saw those statements from Slack. They're so passionate and with so much conviction, that is because they were fascinated by what we could do with their data. So that is one example and slack does not run on communities. They don't run on cloud. They run on AWS, but they don't they run it like they their own claim. They have very fixed I p addresses fixed instance names, but they're on it like a cloud. Sometimes I would say they are more coordinated behavior than some applications that run on kubernetes like they treat everything as disposable. When something goes away, they don't try to recover it or anything destroyed out. Replace it with something new, which is property off cloud native behavior. And on the other hand, a company like nozzle because they're they're actually a startup on dhe. It is surprising that why would the start of one to use? Ah, something that is Mento scale. Massively. That's when we realized that the cloud native nature of it does fills a gap that currently is not filled by many people, which is I want to run everything in Cooper natives all in one. And we didn't realize until they showed us what they did with it, which is, like, completely migrate from one cloud to another. They're a super amazing. And I heard it on dhe. They did that without even telling me are telling anybody in the community because one day I talked to them. They say they are on a key s on. A few days later, I still assumed that they are Nikki s and they know of your booty. Jakey, when did you do this? Oh, we did that last month because we got some really good deal with them, super exciting, >>and that that is a surprising, exactly affected. That's surprising. It is a bit of a concern to me because we hear a lot of talk about multi cloud and the idea of applications being being mobile between different clouds. Data movement is really hot. Exactly. So the fact that someone has actually managed to do that and haven't moved from one community service across to another one is that we find that remarkable because we know it's such a hard problem. But that's one of the great things I think about kubernetes, which is possibly under appreciated, is that it's not that it makes everything easy, but it makes what What used to be hard is now >>possible. Yes, yes, yes, that is very true. Yeah, it's, um uh, like it took It took us a while to, uh, think to make this mind shit, because some of these things, even though they're like it looks, looks looks very obvious. But for the longest time, we were, you're saying, tested for massive scale ability. It's for It's what this and that and even two years ago, up sport came and said, We're going to use the tests for communities orchestration. Weird, but okay, feel free. We don't have a problem with it. And then nozzle came out, and now suddenly you see Oh, this is this is why. And this Saul's really, really difficult problem on. They all did especially hot Spot. Did a lot of work in with tests to actually make it easier. But now we see Now we see the light. >>So Sougou Planet scales the company. Help us understand Vitesse planet scale. How that fits together. What's kind of the business model for your company? >>Yeah. So, um uh, so the test was originally developed at YouTube by you, too. There was one thing That was some pressure. We were beginning to feel when we developed it. We didn't mean for anybody to use it. Really. It was open source, more for academic reasons to show that we can do these things on. But it was interesting when people started adopting it. You're adopting this system. Okay, so we'll see what we can do to help you. But after a while, when the community started growing, some of them were contributing. But definitely storage is a difficult software to write, too. It's not like a pitiful software. Any anybody can understand the cord and start writing. It was obvious that the number of people wanting to use with death and wanting peaches from it are also people that we're not really capable of. writing those features because they're really hard features, too. Right on DDE. That pressure was going and they were saying all I wish you two could do this for me. You know, YouTube is a video company. They're not in the We just did this for ourselves. There's no reason for us to spend so many person years they've left in the future for you. And that time it became obvious that we need to start a company to support this community where there's this huge growing demand, Which is kind of what motivated towards us, uh, thinking about starting planet scale and one requirement waas It cannot remain a YouTube project at that point. So which is why we work it out that way, will actually move it to see NCF. And then I ended up leaving. You do have to start planet scale with my co founder. Then >>so is just from a business standpoint, is that service is on their customers ask for things and fun that that that gets contributed upskirt stream. >>So that was initially what we thought we will do. Initially we thought it was just get out laptops and start helping people that that was our initial thinking. But what we realized was at the same time the industry has shifted towards this new business model which is to actually run everything as a service. And we realized, Oh, my God, years All we have to do is we know how to run with us. You've done it at YouTube. You help people deployed with testing various companies. You know exactly what it takes to run with us. All we have to do is take this. I'm does the service. And that's exactly what people want. Because otherwise, because of the fact that we tested this flexible, it is also extremely complex, too confident because it can run on frame. Then you have to sit all these flags. You runnin carbonate is you said all these flags. So all this has to be managed and we realized, OK, we can manage this and we know exactly how to make it work. And we actually just announced two days ago that our planet scale CNDP Cloud native database is available for people to come in use. >>Well, congratulations on the progress of the business as well as the test graduation and thank you. So much for joining us here on the Cube. Thank you. Alright for Justin Warren. I'm stupid Men. We will be back with more of our day. Two of three days. Whoa! Wall coverage here from San Diego. Thank you for watching the Cube.

>> From Seattle, Washington, it's theCUBE covering KubeCon and CloudNativeCon North America 2018. Brought to you by Red Hat, the Cloud-Native computing foundation and its ecoystem partners. >> Everyone welcome back to theCUBE's exclusive coverage here live in Seattle for KubeCon and CloudNativeCon 2018. I'm John Furrier with Stu Miniman, breaking down all the content and the analysis, opinion, getting all the data, sharing that with you, three days of wall-to-wall coverage, we're in day three winding down, great event. Our next guest is one of the stars of the show here, original Kubernetes, a pioneer, Joe Beda, also the Kube founder at Heptio, recently sold to VMware in acquisition. Startup only what, two years old? >> Yeah, about two years. >> About two years. Welcome back to theCUBE, great to see you. >> Thanks for having me. >> Google. Great work you've done with Craig and with pioneering Kubernetes, Heptio startup. >> Yep, yep. >> Got taken off the table as you were ramping up. Congratulations! >> Thank you so much! It's been a little bit of a wild ride, I can tell you that. >> So first question for you is, I don't want to get into the whole VMware thing, we're going to hit that up in VMworld next year. But as you look at the ecosystem of Kubernetes, I mean, you've got to be looking at this sayin, "Hey, we knew this was going to be big." You guys have been running it with Borg and where that came from in the DNA. The magic wand almost was kind of passed out. Hey, this happened! It's kind of happening in a big way. What's your reaction? How do you feel at an emotional level? What's the vibe going on in your mind right now? >> I mean, I look at this and it blows my mind. I think we knew that we had a possibility with Kubernetes to do something big, we could feel it. I don't think we ever expected this, to be honest. The thing, though, that I think surprises me, and it was both about building startup and building a company, but also seeing the community grow, is that every time you hire a new person to do a startup, every time you have somebody join the community and start contributing, it's like it's another cylinder in the engine. And it really starts taking it in directions that you had no idea it was going to to go into. And so, I look around here and this is a product of a community. This is not a product of any single company, any single set of folks. I mean, you start things snowballing and interesting things happen, but it really is a group effort. >> It's so hard to do a startup. You know, I've done a lot of startups. We've done a lot of interviews with startups. It's hard. You got to start a company, you got to do all that legal work, then you've got to get the momentum, and it's capped off by the validation, certainly by VMware, who announced heavily at the VMworld, Pat Gelsinger said that Kubernetes is the dial tone. (laughs) And I'm like, okay, I guess. We were talking earlier, it's the ethernet. I've called it the TCP/IP. So, all the analogies come to this enabling kind of capability. And that's where we see a lot of the value. Where do you see the opportunities for the ecosystem to innovate. I mean, getting some clear visibility around the stability. But now value is starting to get created. What's your thoughts on value creation? Where are some areas that are ripe? >> Yeah, well, I think a couple of things. I think we're at the point now where it's about how do we bring these technologies to new people, to new audiences, to folks who might not have heard about it, don't quite get it. How do we make this stuff more relevant to them? So we're moving out of this technology-focus phase, into this phase that's focused on solution and value that's delivered. And this isn't always about innovation and building on top. Some of it is about different ways to do it, and also just, you know, having these ideas just permeate, right? And as technologists, we build on incredibly complicated technology. We look at, say, something like AWS. If you were to approach that brand new without any idea of the history there, it would be incredibly intimidating. But it's been around long enough, it's grown organically, that everyone's like, "Oh yeah, I totally understand all that stuff." It just takes time sometimes for these technologies to become understood, to become part of the fabric of what people assume the technical skill set is. And I think that's a big part of what we're seeing starting to happen now, too. >> Joe, I want to get your viewpoint. When I think about the last ten, fifteen years, the whole discussion of hybrid cloud, multicloud, portability, even thinking about things from a VMware context, or from a cloud-computing context, it seems like we have a lot of false starts and false expectations about, you know, we've listed Pat Gelsinger and Andy Jassy and others who talk about the three laws of the cloud. We're not changing physics. And Kubernetes is super-important for multicloud, but portability was kind of thrown out there. I want to get you to help us tease out what it is, what it isn't, and how do you see multicloud today? >> Yeah, so I mean, first, on the topic of false starts, there's this popular narrative that, oh, it's going to be this, now this is the hot thing, now it's this. And the reality is that main frames are still around. Technologies don't disappear, it's an additive type of thing. So it's not like, say for example, Kubernetes or Serverless or machine learning, right? It's all of those things working together and I think, if you look at it in that way, it doesn't feel like a false start. It just seems like we're adding more different techniques, more technologies onto the pile. In terms of where I see this stuff going, I think multicloud and compatibility do go hand-in-hand. From the very start, we never wanted to pretend that Kubernetes was going to be this magic layer that was going to make differences between different environments disappear. What we did want to do, though, was actually find the commonalities and minimize the extra differences that didn't need to be there. And so a lot of times, when I talked to customers, I don't say, "Hey, don't use this special service in this cloud." I don't tell them that. What I do say, though, is, "If you are going to start using those things, "do it in an eyes-open type of way. "Understand the trade-offs, "understand why you're doing it" versus just willy-nilly adopting technologies cuz they look nice and shiny, and that's what you want to do, right? So I think, whether you're adopting Kubernetes, whether you're adopting a specific cloud technology, whether you're moving to cloud versus actually building automatable infrastructure on prem, make sure that you're thoughtful about how you enter those types of decisions. >> The way the feedback we hear from people here on theCUBE this week and other places as well, is, pick a problem to solve. Don't boil all of the ocean, get in there, use Kubernetes for what you think you can nail a problem on, iterate from there. That's the common theme. Now as you guys pivot over to VMware, they've been investing a lot in their strategy also with AWS, RDS is now on VMware, they'd look at Kubernetes as a great opportunity to bridge on-premises and cloud. So it's clear to see why they like it. Explain for the folks watching who are fans of you and Craig and Heptio, what's next for you guys? You joined VMware, you just closed the deal, you're principal engineer at VM where you're in the business unit side, share some of the specifics that you can on what's going to happen next. >> Yeah, I think it's too early for me to speak on sort of a grand strategy across VMware. I think I'm still mapping things out and understanding things. What I can talk about is the way that we were thinking about the market from Heptio's point of view. And every indication that I've seen that this is actually very, very compatible for VMware. A lot of the keynotes that you saw here at KubeCon Show, that adoption curve, where we're in the early phase versus the early majority, that type of thing, and I think there's some truth to that. But I also think that there's an axis to that, that actually isn't shown up there, around the different personas that you see adopt different technologies inside of the enterprise organization. And so the strength of somebody like VMware, and I think the early adopters for things like Kubernetes, are that operator persona. And we're seeing an evolution of that persona as it starts to come to grips with the world of the cloud. We're moving from a place where things are ticket-based, human intensive, to how do we move to API-driven, policy-drive types of things, right? And so that's obviously where the cloud is. But how do we take those learnings, how do we take those lessons and actually apply those things on problems? And so our goal from Heptio's point of view, and I think it's incredibly well-aligned with VMware, and an enormous opportunity, is taking the VMware-faithful, the folks who do go to VMworld, that have built careers on that solution, how do we help them move their career forward, move their positioning forward in a way that doesn't eliminate their jobs, but actually helps them be smart in a modern world where cloud is actually part of the landscape. >> We had Aparna on from Google, and you know Aparna from your Google days, and she was making a comment about these new personas, new opportunities, new jobs that are opening up based on Kube. Okay, great, we see some of that. And then we've done rift on the idea that Kubernetes also is a uplift for existing roles: system architect, Network Guy, Server Guy, and then the VMware operator that had been wearing virtual machines, this is a lift for them. Talk about what specifically is going to get them jazzed up, is it the policy knobs on Kubernetes, what's going to really appeal to people below Kubernetes and what's really going to appeal to the developers above Kubernetes? >> Well, for centralized IT within an organization, cloud has been a challenge, right? If, I'm not thinking of a specific customer, but it's not insane to think about something like a developer who wants to write an app, they have to file a ticket, it can take anywhere from two weeks to three months to get stuff provisioned, right? And they're sitting there twiddling their thumbs waiting to actually get that stuff ready. Meanwhile, they take their credit card, go to a cloud, get a machine up and running within 30 seconds, and get their app shipped. So while they're waiting on that ticket, they can get that app shipped, and then they dare their manager to deny the credit card charge when it comes due. That is a challenge for centralized IT which oftentimes has not had any competition. Now, all of a sudden, they find themselves in a situation where they're competing with cloud for the hearts and minds of their own customers, for their developers. And different organizations have reacted to this in different ways. Some of them had said, we're just going to explode out IT and actually say to different business units, "You own your own destiny." But, depending on the enterprise, depending on the goals, depending on their requirements around regulatory needs, around policy, around cost controls, around mobility of developer skills across the organization, that may or may not work for them. And so, for me, the bridge forward for that centralized IT, is really one of giving them the power tools so they can actually serve their customers better in a world where cloud exists. >> Yeah. Their jobs! That's their job to serve the business. >> Well, I mean, the bar has been raised, right? And so we want to help them meet that challenge. >> Awesome. >> Joe, I want to get your thoughts on this growing ecosystem. I said in our open this morning, we've been looking for the last five years or so. Where is that independent, cloud-computing show? And sitting here with 8 thousand people, and another 2 thousand people are in the hallways or on the wait list and things like that. It's here, and there's all of these projects into multiple communities come together. How does it feel that Kubernetes, was it kind of the first domino to help tip something broader with CloudNative? >> I mean it feels really good, to be honest. I think one of the things that we saw Heptio as, and I think VMware is actually in a great position also, is to be a neutral party that really is on the side of customers as they enter this complex world where they're dancing with elephants that are the big cloud providers. And I think that there is an enormous appetite for customers to actually have trusted partners in that world. Now, with respect to the conference, I think, what I love doing is I love being on the floor here, I love talking to people, I love going to the session tracks. That's where I think the heart of this conference is. Some of the contributor community days that happened on Monday that don't get a lot of coverage, the big headlines are one thing but there really is an undercurrent of community that's happening in this conference that is really something pretty special. >> I think that's a great point, and, at least what I've seen that's contributed, you know, the Envoy Group, tomorrow there's the Operators Group, this is not a monolithic community, it's not like, look, I've been at VMworld for years. It was about virtualization and primarily a single product from a single company and everything that wrapped around it. This is not a vendor doing it, there's all of these. I talked to the people that all they care about is Helm, we talked about all these different pieces, and many of them tie into what was going on at Kubernetes, but there's just so much diversity, and it's a common ground for everybody to work together. >> And I think, this is one of the things that I think has been interesting about the CNCF is that there is no, there is an idea that we want to create a set of projects that work well together, but there also is the realization that there is no one way to skin the cat, there is no one way to solve a problem. So there is room for projects to disagree, there's room for projects to experiment, there is room for folks to try and find their audience and be successful. >> That's the modern upgrade in my mind, to, not going against the open source ethos but also innovating with it, You're balancing commercial so you just, I think they've got to apply this upstream concept called CNCF where the downstream benefits for commercialization, you can still do the open source community thing while having an impact downstream to IT and just regular developers. This is the trend we see at Enterprise when we talk to the customers, we talk to other people, IT has been outsourced for decades. Now there has to be a competitive advantage, and we have the competition thing that you pointed out. And the smart CIO CX's are bringing developers in to create a competitive advantage, and it's a new reset. And, not throwing away networks, they're not throwing away compute and storage. They're going to change it. And I think this is where the real tailwind is. Do you agree with that or what's your thoughts? >> The way I like to think about it is that, and I'm using company names here as an example, but I think there is this race between Tesla learning how to become a car company versus, say, Ford or GM learning how to become a software company, right? And that dynamic is playing itself out across every single industry. And I think there is not a CEO or CIO or board out there that doesn't realize that the way for us to be relevant in the future is to turn software into, not just a cost-center and something we deal with, but something that becomes a fundamental advantage and driver of our business. >> Every industry: media, software! We're a software company that happens to do media, with theCUBE. You're totally right, it's just like-- >> Any industry. This is why Amazon's getting into grocery stores. >> It's integration. This is a completely new horizontal dynamic with a little bit of special machine learning at the outlay. >> We're moving into a software-defined world, for sure. >> Joe, been great to have your commentary here on theCUBE. Thanks for sharing. Congratulations on the acquisition. Super outcome, the numbers floating out there. It's pretty large, good deal. We have no comment. (laughs) >> Open source! >> Read DCSE C file. >> Open source business models are changing, but the value is still the same. Those who create the value can extract it. That's the ethos of open source, of course theCUBE as well. Thanks for watching. Stay with us for more coverage after this short break.

>> Live, from the Seattle, Washington. It's theCUBE, covering KubeCon and CloudNativeCon, North America 2018, brought to you by Red Hat, the Cloud Native Computing Foundation and it's ecosystem partners. >> Welcome back everyone. We're live here in Seattle for theCUBE's exclusive coverage of KubeCon and CloudNativeCon 2018. I'm John Furrier at Stuart Miniman. Our next guest Stephan Fabel, who is the Director of Product Management at Canonical. CUBE alumni, welcome back. Good to see you. >> Thank you. Good to see you too. Thanks for having me. >> You guys are always in the middle of all the action. It's fun to talk to you guys. You have a pulse on the developers, you have pulse on the ecosystem. You've been deep in it for many, many years. Great value. What's hot here, what's the announcement, what's the hard news? Let's get to the hard news out of the way. What's happening? What's happening here at the show for you guys? >> Yeah, we've had a great number of announcements, a great number of threads of work that came into fruition over the last couple of months, and now just last week where we announced hardware reference architectures with our hardware partners, Dell and SuperMicro. We announced ARM support, ARM64 support for Kubernetes. We released our version 1.13 of our Charmed Distribution of Kubernetes, last week And we also released, very proud to release, MicroK8s. Kubernetes in a single snap for your workstation in the latest release 1.13. >> Maybe explain that, 'cause we often talk about scale, but there is big scale, and then we're talking about edge, we're talking about so many of these things. >> That's right. >> That small scale is super important, so- >> It really is, it really is, so, MicroK8s came out of this idea that we want to enable a developer to just quickly standup a Kubernetes cluster on their workstation. And it really came out of this idea to really enable, for example, AIML work clouds, locally from development on the workstation all the way to on-prem and into the public cloud. So that's kind of where this whole thing started. And it ended up being quite obvious to us that if we do this in a snap, then we actually can also tie this into appliances and devices at the edge. Now we're looking at interesting new use cases for Kubernetes at the edge as an actual API end point. So it's a quite nice. >> Stephan talk about ... I want to take a step back. There's kind of dynamics going on in the Kubernetes wave, which by the way is phenomenal, 8000 people here at KubeCon, up from 4000. It's got that hockey stick growth. It's almost like a Moore's Law, if you will, for the events. You guys have been around, so you have a lot of existing big players that have been in the space for a while, doing a lot of work around cloud, multi-cloud, whatever ... That's the new word, but again, you guys have been there. You got like the Cisco's of the world, you guys, big players actively involved, a lot of new entrants coming in. What's your perspective of what's happening here? A lot of people looking at this scratching their head saying: Okay I get Kubernetes, I get the magic. Kubernetes enables a lot of things. What's the impact to me? What's in it for me as an enterprise or a developer? How do you guys see this market place developing? What's really going on here? >> Well I think that the draw to this conference and to technology and all the different vendors et cetera, it's ultimately a multi-cloud experience, right? It is about enabling workload portability and enabling the operator to operate Kubernetes, independently of where that is being deployed. That's actually also the core value proposition of our charmed Kubernetes. The idea that a single operational paradigm allows you to experience, to deploy, lifecycle manage and administer Kubernetes on-prem, as well as any of the public clouds, as well as on other virtual substrates, such as VMware. So ultimately I think the consolidation of application delivery into a single container format, such as Docker and other compatible formats, OCI formats right? That was ultimately a really good thing, 'cause it enabled that portability. Now I think the question is, I know how to deploy my applications in multiple ways, 'cause it's always the same API, right? But how do I actually manage a lot of Kubernetes clusters and a lot of Kubernetes API end points all over the place? >> So break down the hype and reality, because again, a lot of stuff looks good on paper. Love the soundbites of people saying, "Hey, Kubernetes," all this stuff. But people admitting some things that need to be done, work areas. Security is a big concern and people are working on that. Where is the reality? Where does the rubber meet the road when it comes down to, "Okay, I'm an enterprise. What am I buying into with Kubernetes? How do I get there?" We heard Lyft take an approach that's saying, "Look, it solved one problem." Get a beachhead and take the incremental approach. Where's the hype, where's the reality? Separate that for us. >> I think that there is certainly a lot of hype around the technology aspect of Kubernetes. Obviously containerization is invoked. This is how developers choose to engage in application development. We have Microservices architecture. All of those things we're very well aware of and have been around for quite some time and in the conversation. Now looking at container management, container orchestration at scale, it was a natural fit for something like Kubernetes to become quite popular in this space. So from a technology perspective I'm not surprised. I think the rubber meets the road, as always, in two things: In economics and in operations. So if I can roll out more Kubernetes clusters per day, or more containers per day, then my competitor ... I gain a competitive advantage, that the cost per container is ultimately what's going to be the deciding factor here. >> Yeah, Stephan, when I think about developers how do I start with something and then how do I scale it out in the economics of that? I think Canonical has a lot of experience with that to share. What are you seeing ... What's the same, what's different about this ecosystem, CloudNative versus, when we were just talking about Linux or previous ways of infrastructure? >> Well I think that ultimately Kubernetes, in and of itself, is a mechanism to enable developers. It plays one part in the whole software development lifecycle. It accelerates a certain part. Now it's on us, distributors of Kubernetes, to ensure that all the other portions of this whole lifecycle and ecosystem around Kubernetes, where do I deploy it? How do I lifecycle manage it? If there's a security breach like last Monday, what happens to my existing stack and how does that go down? That acceleration is not solved by Kubernetes, it's solved for Kubernetes. >> Your software lives in lots and lots of environments. Maybe you can help clarify for people trying to understand how Kubernetes fits, and when you're playing with the public cloud, your Kubernetes versus their Kubernetes. The distinction I think is, there's a lot of nuance there that people may need help with. >> That's true, yeah. So I think that, first of all, we always distance ourself from the notion of having our Kubernetes. I think we have a distribution of Kubernetes. I think there is conformance, tests that are in place that they're in place for a reason. I think it is the right approach, and we won't install a fourth version of Kubernetes anytime soon. Certainly, that is one of the principles we adhere to. What is different about our distribution of Kubernetes is the operational tooling and the ability to really cookie-cutter out Kubernetes clusters that feel identical, even though they're distributed and spread across multiple different substrates. So I think that is really the fundamental difference of our Kubernetes distribution versus others that are out there on the market. >> The role of developers now, 'cause obviously you're seeing a lot of different personas emerging in this world. I'm just going to lay them out there and I want to get your reaction. The classic application developer, the ones who are sitting there writing code inside a company. It could be a consumer company like Lyft or an enterprise company that needs ... They're rebuilding inside, so it's clear that CIOs or enterprises, CXOs or whatever the title is, they're bringing more software in-house, bringing that competitive advantage under application development. You have the IT pro expert, practitioner kind of role, classic IT, and then you got the opensource community vibe, this show. So you got these three things inter-playing with each other, this show, to me feels a lot like an opensource show, which it is, but it also feels a lot like an IT show. >> Which it also is. >> It also is, and it feels like an app development show, which it also is. So, opportunity, challenge, is this a marketplace condition? What's you thoughts on these kind of personas? >> Well I think it's really a question of how far are you willing to go in your implementation of devops cultural change, right? If you look at that notion of devops and that movement that has really taken ahold in people's minds and hearts over the last couple of years, we're still far off in a lot of ways and a lot of places, right? Even the places who are saying they're doing devops, they're still quite early, if at all, on that adoption curve. I think bringing operators, developers and IT professionals together in a single show is a great way for the community and for the market to actually engage in a larger devops conversation, without the constraint of the individual enterprise that those teams find themselves in. If you can just talk about how you should do something better and how would that work, and there is other kinds of personas and roles at the same table, it is much better that you have the conversation without the constraint of like a deadline or a milestone, or some outage somewhere. Something is always going on. Being able to just have that conversation around a technology and really say, "Hey, this is going to be the one, the vehicle that we use to solve this problem and further that conversation," I think it's extremely powerful. >> Yeah, and we always talk about who's winning and who's losing. It's what media companies do. We do it on theCUBE, we debate it. At the end of the day we always like ... There's no magic quadrant for this kind of market, but the scoreboard can be customers. Amazon's got over 5000 reputable customers. I don't know how many CNCF has. It's probably a handful, not 5000. The customer implications are really where this is going. Multi-cloud equals choice. What's your conversations like with customers? What do you see on the customer landscape in terms of appetite, IQ, or progress for devops? We were talking, not everyone's on server lists yet and that's so obvious that's going to be a big thing. Enterprises are hot right now and they want the tech. Seeing the cloud growth, where's your customer-base? What are those conversations like? Where are they in the adoption of CloudNative? >> It's an extremely interesting question actually, because it really depends on whether they started with PaaS or not. If they ever had a PaaS strategy then they're mostly disillusioned. They came out, they thought it was going to solve a huge problem for them and save them a lot of money, and it turns out that developers want more flexibility than any PaaS approach really was able to offer them. So ultimately they're saying, "You know what, let's go back to basics." I'll just give you a Kubernetes API end point. You already know how to deal with everything else beyond that, and actually you're not cookie-cuttering out post ReSQueL- >> Kubernetes is a reset to PaaS. >> It really does. It kind of disrupted that whole space, and took a step back. >> All right, Stephan, how about Serverless. So a lot of discussion about Knative here. We've been teasing out where that fits compared to functions from AWS and Azure. What's the canonical take on this? What are you hearing from your customers? >> So Serverless is one of those ... Well it's certainly a hot technology and a technology of interest to our customers, but we have longstanding partnerships with Galactic Fog and others in place around Serverless. I haven't seen real production deployments of that yet, and frankly it's probably going to take a little bit longer before that materializes. I do think that there's a lot of efforts right now in containerization. Lots of folks are at that point where they are ready to, and are already running containerized workloads. I think they're busy now implementing Kubernetes. Once they have done that, I think they'll think a little bit more about Serverless. >> One of the things that interest me about this ecosystem is the rise of Kubernetes, the rise of choice, the rise of a lot of tools, a lot of services, trying to fend off the tsunami wave that's hit the beach out of Amazon. I've always said in theCUBE that that's ... They're going to take as much inland territory on this tsunami unless someone puts up a sea wall. I think this is this community here. The question is, is that ... And I want to get your expert opinion on this, because the behemoths, the big guys are getting richer. The innovation's coming from them, they have scale. You mentioned that as a key point in the value of Kubernetes, is scale, as one of those players, I would consider in the big size, not like a behemoth like an Amazon, you got a unique position. How can the industry move forward with disruption and innovation, with the big guys dominating? What has to happen? Is there going to change the size of certain TAMs? Is there going to be new service providers emerging? Something's got to give, either the big guys get richer at the expense of the little guys, or market expands with new categories. How do you guys look at that? Developers are out there, so is it promising look to new categories, but your thoughts. >> I think it's ... So a technology perspective certainly would be, there could be a disruptive technology that comes in and just eats their lunch, which I don't believe is going to happen, but I think it might actually be a more of a market functionality actually. If it goes down to the economics, and as they start to compete there will be a limit to the race to the bottom. So if I go in on an economical advantage point as a public cloud, then I can only take that so far. Now, I can still take it a lot further, but there's going to be a limit to that ultimately. So, I would say that all of the public clouds, we see that increasingly happening, are starting to differentiate. So they're saying, "Come to me for IML." "Come to me for a rich service catalog." "Come to me for workload portability," or something like that, right? And we'll se more differentiation as time goes on. I think that will develop in a little bit of a bubble, to the point where actually other players who are not watching, for example, Chinese clouds, right? Very large, very influential, very rich in services, they can come in and disrupt their market in a totally different way than a technology ever could. >> So key point you mentioned earlier, I want to pivot on that and get to the AI conversation, but scale is a competitive advantage. We've seen that on theCUBE, we see it in the marketplace. Kubernetese by itself is great but at scale it gets better, got nobs and policy. AI is a great example of where a dormant computer science concept that has not yet been unleashed ... Well, it gets unleashed by cloud. Now that's proliferating. AI, what else is out there? How do you see this trend around just large-scale Kubernetes, AI and machine learning coming on around the corner? That's going to be unique, and is new. So you mentioned the Chinese cloud could be a developer here. It's a lever. >> Absolutely, we've been involved with kubeflow since the early days. Early days, it's barely a year, so what early days? It's a year old. >> It's yesterday. >> So a year a ago we started working with kubeflow, and we published one of the first tutorials of how to actually get that up and running and started on Ubuntu, and with our distribution of Kubernetes, and it has since been a focal point of our distribution. We do a couple of things with kubeflow. So the first thing, something that we can bring as a unique value preposition is, because we're the operating system for almost all GKE, all of AKS, all EKS, such a strong standing as an operating system, and have strong partnerships with folks like NVIDIA. It was kind of one of the big milestones that we tried to achieve and we've since completed, actually as another announcement since last week, is the full automatic deployment of GPU enablement on Kubernetes clusters, and have that identical experience happen across the public clouds. So, GPGPU enablement on Kubernetes, as one of the key enablers for projects like kubeflow, which gives you machine learning stacks on demand, right? And then a parallel, we've been working with kubeflow in the community, very active, formed a steering committee to really get the industry perspective into the needs of kubeflow as a community and work with everybody else in that community to make sure that kubeflow releases on time, and hopefully soon, and a 1.0, which is due this summer, but right now they're focused on 0.4. That's a key area of innovation though, opportunity. >> Oh, absolutely. >> I see Amazon's certainly promoting that. What else is new? I've got one last question for you. What's next for you guys? Get a quick plugin for Canonical. What's coming around the corner, what's up? >> We're definitely happy to continue to work on GPGPU enablement. I think that is one of the key aspects that needs to stay ... That we need to stay on top of. We're looking at Kubernates across many different use cases now, especially with our IoT, open to core operating system, which we'll release shortly, and here actually having new use cases for AIML inference. For example, out at the edge looking at drones, robots, self-driving cars, et cetera. We're working with a bunch of different industry partners as well. So increased focus on the devices side of the house can be expected in 2019. >> And that's key these data, in a way that's really relevant. >> Absolutely. >> All right, Stephan, thanks for coming on theCUBE. I appreciate it, Canonical's. Great insight here, bringing in more commentary to the conversation here at KubeCon, CoudNativeCon. Large-scale deployments as a competitive advantage. Kubernetes really does well there: Data, machine learning, AI, all a part of the value and above and below Kubernatese. We're seeing a lot of great advances. CUBE coverage here in Seattle. We'll be back with more after this short break. (digital music)

>> Live, from London, England, it's theCUBE covering .NEXT Conference Europe 2018! Brought to you buy Nutanix. >> Good morning from London, England. I'm Stu Miniman with my co-host Joep Piscaer, and you're watching theCUBE's two day coverage of Nutanix .NEXT 2018 here at the ExCel Center. Welcome to our program. Joep and I are gonna spend a couple minutes giving our thoughts on Nutanix, what's happened in ecosystems, what we're hearing from the customers. So Joep, 3,500 people here, I think back two years ago when they held the first show in Europe in Vienna, you and I talked there, it was a much smaller show. Nutanix is growing some strong momentum here. Generally as you say at these kind of shows, you usually have the true believers, but it is nice to see that a company, Nutanix, now nine years old, you know their customers seem pretty passionate. That they love what it does for them, different careers. One of the executives, it was Sunil up on stage yesterday, said, "Hey, you might not get fired for buying "an IBM or VMware, but you get promoted for buying Nutanix." So what's your impressions, tell me what you're hearing from your peers and compatriots at the event. >> So, what I'm seeing around me here is the buzz is definitely much bigger than a couple of years ago. The show's bigger, it seems to attract more customers from all over, small companies, big companies, so seeing that buzz, compared to a couple of years ago kind of proves that Nutanix has a place in the industry and that their products are gaining traction with customers. And looking at the keynotes from yesterday and today, I see a lot of announcements, a see a lot of work not just in the products customers are using now, but also kind of in a forward looking, we wanna go here fashion. And that's exciting to me, because Nutanix is growing beyond just a core infrastructure company. They are building a portfolio, they're building a platform. And I think, from what I've been hearing from customers, it does have traction. Customers like the direction Nutanix is going, but I can't help but wonder how many customers are already using these services or planning to use these in the near future. >> Yeah, and one of things I look at, and I think I've seen good progress here, this isn't just taking the US show and shipping it over to Europe. Nutanix has many years of doing road shows, it's the .NEXT on the road, things like that. In the keynotes, we're seeing European, not in just European customers, but that the demo this morning was senior SE, Nutanix woman from Spain and you see culture when I walk around the show floor, I know a lot of the vendors here and it is their European presence and hear good proof points of what they're doing. I mean, you're from here in Europe. What do you hear and see? >> Yes, I agree, this is not just a carbon copy of the US show, it has its own identity, it attracts its own customers, its own partners. Walking around the show floor, I do see a lot of customers that I recognize. I do see a lot of partners from the Netherlands or from Europe that I recognize, that I work with. So seeing all that attention from the crowd, that helps, and seeing Nutanix as a company, not just US based, but focusing on Europe as well. >> Yeah, wanna get your opinion. How's Nutanix doing on painting their vision? I think back to early days, Dheeraj and the team have a clear direction as to where they want to take things and I think they do a good job of focusing on the customer and laying out a vision without getting too far over their skis. Today, I'd look at it, most customers today, they're really using, I'm using HCI probably for more than just VDI and starting to spread out, but when you start talking about from the core to the essentials, to the enterprise, some of that is mostly customers aren't ready, but they need to be hearing a lot of these things. What's your take, what's some of your takeaways so far? >> So I think you've said it exactly right. So, even though customers are only using core products, mainly, it does help that Nutanix is laying down this vision of next steps for customers because even though you could say infrastructure's a commodity and the cloud is overruling on-prem installations, it's still customers are struggling to go from their current, on-prem, three tier virtualization layer up to an application focus in the cloud. And Nutanix telling that story, Nutanix telling, okay, this should be the next step, after that, you can do this. That helps to guide customers to not only where Nutanix wants the customer to go, obviously, but also from that customer centric perspective, helping customers navigating that difficult swamp of the next step of cloud, of applications, and moving from an infrastructure focus to that application focus. >> Yeah, look, there's a mental map I use for when I look at this. I kind of say that the world of the future is definitely, I prefer the term multi-cloud, but that definitely includes my own data centers or service provider data centers where I manage more of it. Let's call that the private piece of the hybrid and public cloud, and then of course, there's a lot of SAS in there. And when I put a company in there and say, okay, did they lean a little bit too far? Of course, Amazon, very heavily towards the public cloud, but we saw an announcement, AWS Outpost, where they're saying, hey, they're going deeper with VMware and also with their own stack to be able to go the private. Take a company like Dell who leans very heavily towards private, they have VMware and Pivotal to help get them a little bit more to public. VMware going deeper into public. Nutanix definitely leans a little bit towards private, but they're doing enough in the public cloud, they're making partnerships. I actually like the messaging I heard on Cloud Native this morning, saying that look, this is just like cloud is mostly an operational model and sure there's a lot of great innovation in the public cloud, but Cloud Native doesn't mean I built it in the cloud, it milked it. It's microservices and containerization and all those things, even serverless. We can debate whether that can only be in the public cloud. So, the hybrid message, I'd like to see a little bit more clarity from Nutanix as to where that has, and definitely feedback I've gotten from customers, but for the most part, I think they're doing a solid job. >> I agree, so, I think it's a matter of perspective, right? Where are your roots, where do you come from? So for VMware, for Nutanix, it makes the most sense to go from on-prem into cloud, into SAS, whereas Amazon was born in the cloud. They attract developers, they attract application builders, website builders, and so they have the different perspective, right? So they are now realizing, okay, on-prem has a place too. And so the difference is it's just a matter of perspective and what type of customers are you serving? So VMware and Nutanix are serving the enterprise customer that has big legacy roots in the data center, and they're helping those customers move towards the public cloud. But the other way around is just as valid, because there are so many companies that built an e-com solution on the public cloud and are moving back to on-prem for cost reasons, for security reasons, whichever reason is there for a customer. But both perspective make total sense to me. And if you compare Outpost to the work Nutanix is now doing with Carbon, technologically it isn't all that different, but I think it's a matter of perspective which customers are we helping in which way. >> Yeah, you've actually, I'll put a fine point on this. When I looked back to the early days of Nutanix, what their mission was is they took hyperscale, what the really big guys were doing, and they were going to bring that to the enterprise. They've done a great job of packaging that. Early days, we talked about the hyperscale companies really can put in a lot of high value resources to build what they need. The enterprise doesn't have a big team of Ph.D.'s to throw at things, they don't have the amount of resources, so they will spend money to buy what they have. So that's what Nutanix has done, they've got great things to show for it, public company, over seven billion dollars of market cap, so they can grow that. They've met the customs where they are and definitely are a trusted partner to help bring them towards what Nutanix calls the enterprise cloud, what most of us call that multi-cloud or hybrid cloud world. Alright, Joep, thank you so much for helping us dig in with some of the analysis. Be sure to stay with us for a full day, second day, of coverage. As always, turn to theCUBE.net for all the interviews. I'm Stu Miniman and thank you for watching theCUBE. (techno music) (relaxing music)

>> Announcer: Live, from Vancouver, Canada, it's theCUBE, covering OpenStack Summit North America 2018. Brought to you by Red Hat, the OpenStack Foundation, and its ecosystem partners. >> Welcome to theCUBE's coverage of OpenStack Summit 2018 here in Vancouver. I'm Stu Miniman with my cohost, John Troyer. And happy to welcome back to the program, fresh off the keynote stage, Mark Collier, who's the chief operating officer of the OpenStack Foundation. >> Thank you. Thanks for having me back. >> Thank you for having us back and thank you again for doing the show in Vancouver, so-- >> Oh man, such an amazing place. Like this convention center, I don't think it's fair to call it a convention center because it's like a work of art, you know? >> And it's my second time here for this show, and I think kudos to your team because you have good enough content that people aren't just wandering around, taking pictures of the mountains. My wife is off seizing the whale watching right now, but everybody else here, they're engaged. And that's what you want in the community. >> Yeah, definitely. I guess you have to make sure you don't lose their attention to the whales and the sea planes, but so far everyone seems to be gettin' down to business. >> You know, I think it would be fair to say that there's some transitions going on in the marketplace in general, and at this show I notice when I got the invitation, it's like the OpenStack slash open infrastructure summit. Got a big track on edge computing, got another one on containers, been talking about containers for a few years at this show, which really interesting to talk about. And I mean, the edge stuff, we were talking about it as NFV and the telcos and all that stuff in the past. What is the OpenStack Summit these days, Mark? >> Yeah, I mean I think that it's evolving to reflect what people are doing with open source when it comes to infrastructure. And so we call it open infrastructure, but basically it's just a world of possibilities have been opened up by, of course, OpenStack, but also many, many other components, some of which came before like Linux and things like that, and some of which started after, like Kubernetes, and there's many other examples, TensorFlow for AI machine learning. So there's kind of this like embarrassment of riches these days if yo want to automate your infrastructure in a cloud-like fashion. You can do so many more things with it, and OpenStack solves a very specific, very important layer which is that kind of traditional infrastructure as a service layer, compute storage and networking. But once you automate that, it's proven, it's reliable, you could run millions of cores with it like some of our users are doing. You want to do more and that means layering other things on top or sort of connecting them in different ways. So just trying to help users get something more out of the technology is really what we're about and OpenStack becomes like an enabler rather than kind of like the whole conversation. Yeah, one of the things I always say in this industry, sometimes we just don't have the right expectations going into these environments. You know, when I think back 15 years ago as to what we thought Linux was going to do. Oh it's going to crush Microsoft. It's like, well, Microsoft is still doing quite well and Linux has done phenomenal. We wouldn't have companies like, Google if it wasn't for the likes of Linux. In an open source you've got a lot of tools out there. So while there are the CERNs and Walmarts of the world that take a full OpenStack distribution and put out tons of cores, I've run into software companies where when I dig into their IP, oh what do ya know, there's a project from OpenStack in there that enables what they're doing. So I've seen at a lot of shows they're like, there's companies that are like, yes, I want it, and then there's like, oh no, there's this piece of it I want, there's that piece what I want. And that's kind of the wonder of OpenStack that I can do all of those things. >> Yeah exactly. I think we've talked before about sort of calling it composable open infrastructure, and making, OpenStack's always been architecturally designed from, in terms of the goals around it, to be pluggable so from the beginning you could plug multiple hypervisors kind of underneath and you could plug different backends for storage and networking, so that sort of concept of being something, integration engine that plugs things in is part of the OpenStack kind of philosophy, but now you see that the OpenStack services themselves are sort of, you can think of them as microservices, and like if you just need block storage you can use sender. And that may make sense for some specific environments, and are you running OpenStack? Well, you are, but it gets a little bit fuzzy in terms of are you running all of it or part of it? And the reality is the things are not as simple as a binary yes or no. It's just that the options are much greater now. >> Well Mark, that has been some of the discussion in the community over the last few years, the core versus the big tent, and now of course with all this interoperability, conversations with both OpenStack participating in other communities and other communities here today, this week. I mean, what's the current state of that conversation about what is OpenStack and how does it interrelate? I think you kind of touched on it with this composable idea. >> Yeah, I mean I think that basically it's kind of like OpenStack is as OpenStack does, you know? So what are people doing with it and that tells you kind of what it is and what people are doing with it. There are a lot of different patterns. There's no like one specific deployment pattern that everyone uses, but probably by and large, by far the most common pattern is OpenStack plus Kubernetes. And so when you talk about the interop piece, this is a really good example where OpenStack has evolved to become a better, kind of better citizen, I guess, of open infrastructure by having more reliable APIs, kind of being a target that tools that build on top can rely on and not sort of have to worry about the snowflakes of different clouds and there's still more work to be done in that area, but we talked about OpenLab, which is an initiative, this morning, that puts together OpenStack, Kubernetes, and other pieces like Terraform and things like that, and does constant end-to-end testing on it, and that's really how you make sure that you know kind of what combinations work well together, and sometimes you just find bugs, and it turns out a couple of changes need to be made upstream in Kubernetes or in OpenStack or in gophercloud or in Terraform, and just if you don't know, then the user kind of with the some assembly required model, finds out and they're like, I don't know, it doesn't work, it's broken. Well, is it OpenStack's fault or Kubernetes's fault, and they don't, they just want it to work. >> So you're saying >> Identified upstream we can fix it. >> You're saying OpenStack has become more of a stable layer of the (mumbles). >> Yes exactly, yes. It has become a much more stable layer. >> Which means there wasn't a whole lot of flashy storage network and compute up on stage actually. >> A lot of the talk-- >> Yeah, it's a really good point. I think it's just really proven in that way, and you know, one of the things that was highlighted was like the virtual GPUs, right? So, if OpenStack is designed to be pluggable, what do people want to have as an option now in terms of compute storage and networking, on the compute side is they want GPUs, because that gives an AI machine learning much faster, if they're bit coin miners, like I'm sure you all are in your basement, they're going to want GPUs. And what was really interesting is that the PTL, like the technical leader of the Nova Project, got up and talked about virtual GPUs. I was back in the green room and like three of the other keynote speakers were like, oh man, we are so excited about this VGPU support. Like, our customers are asking for it, the guy, Mohammad from Vexos, is the CEO of Vexos, he said, our customers are demanding this queens release, which is the latest OpenStack, and we were kind of surprised, they just really want this queens release. So we asked them why and they're like well they want VGPU. So that's kind of an example of an evolution in OpenStack itself, but it's an extension, enabler for things like GPUs, and that's kind of an exciting area as well. >> You know, it's interesting because in previous years it was the major release was one of the main things we talked about. Queens, as you mentioned, other than the VGPUs and that little discussions, spent a lot more time outside, talked to a lot of the users. You talked about the new tracks that were there. And something I heard a lot this year that I hadn't heard for a few years was, get involved, we're looking to build. And I was trying to think of a sports analogy, and maybe it was like, okay, we're actually building more of a league here and we're looking to recruit as opposed to or is it rebuilding what exactly OpenStack 2.0 is in the future? >> Yeah, that's a really interesting point. You're absolutely right, and I can imagine or can remember sort of talking to some of the speakers as they were working on their content, and I don't think I totally picked up that that was a big trend, but you're absolutely right, that was a major call to action from so many different people. I think it's because when we think about what we are as a community, I talked about how we're a community of people who build and operate open infrastructure, and it's really about solving problems, and if you're as open to community collaboration and you want to solve problems, you can't be afraid to stand up and say we have problems. And sometimes maybe that feels awkward. It's like the tech 101 is get up and say you solved all the problems and you should buy it today. It's online or downloaded or whatever. And I think we just realized that the magic of our community is solving problems. There's always going to be more problems to solve, now you're putting more pieces together, which means the pieces themselves have to evolve and the testing and integration has to evolve. Like it's just a new set of challenges and sort of saying, here's what we're trying to solve, it's not done, help us, actually is more, I think, true to kind of what the community is all about. >> I'm wondering, do we know how many people are at the show this year? >> I don't have the exact count. I think it's around 2600, something like that. >> Yeah, so fair to say it might be a little bit less than last year's North America show? >> Yeah, it is a little bit less. >> And what are you hearing from the user? What are the main things they come for? That you got the new tracks, you've got the open dev conference co-located. What kind of key themes can you get from the users? >> Yeah, I mean, I think one of the things that we found is that we have twice as many cloud architects this year than a year ago. So I think there's always this period of time where conference attendance is driven by curiosity. Like, I've heard about this thing, what is it, or it's the cool factor, hype curves and all that stuff, I want to learn about it. At this point people know what OpenStack is. We've got tons of ways you can learn about it. There's local meetups, there's OpenStack Days all over the world, there's content, videos online. It's just not like a mystery anymore. Like the mystery draws in kind of the people that are just poking around to learn. Now we're at that point of, okay I know what it is, I know what it's for, I want to architect a solution around it, so seeing twice as many cloud architects I think is an interesting data point to think about how we're shifting more towards, people are not asking if it's proven, they're like it's been proven for whatever, two, three years, however, the perception is, but the technology is just very, very solid. It's running infrastructure all over the world, the largest banks and so on and so, I think that's kind of how things are shifting to what else can we do and put on top of it, now that it's a solid foundation. >> I wonder, sometimes there's that buzz as to what's going on out there. There was a certain large analyst firm that wrote a report a couple months ago that wasn't all that favorable about OpenStack. There's others that watching on Twitter during the keynote, and they're like, they're spending all their time talking about containers, why isn't this just part of the Cloud Native Con, KubCon show? What's the foundation's feedback on, what are you hearing kind of, what's your core deliverables? And why this show should continue in the future? >> Sure, I mean I think that what we're hearing generally from users and seeing in our data as well as from analysts like 451 and IDC, those are a couple of different reports coming out, like right now or just came out, that Jonathan mentioned this morning, I think is adoption just continues to grow, and so you know, I think people are not looking at just one technology stack. And maybe they never were, but I think there was this kind of temptation to just think of it, is it containers versus VMs or is it Kubernetes versus OpenStack? And it's like, no one who really runs infrastructure thinks like that because they might have thought it until they tried it, they realized these things go together. So I think the future of this conference is just becoming more and more centered around what are the use cases? What are the technical challenges we're trying to solve? And to the extent we're getting patterns and tools that are emerging like the lamp stack of the cloud, so to speak. How can people adopt them? So you think about cloud as taking all kinds of new forms, edge computing, those are the kinds of things that I think will become a bigger part of the conference in the future. I do like the open infrastructure angle on this. I mean, as infrastructure folks, right, you know that that storage compute network doesn't manage itself, doesn't configure itself. >> Mark: Totally. >> Doesn't provision itself. And so a lot of the app layer things should rely on this lower layer. And I thought last year in Boston there was this kind of curious OpenStack or containers conversation, which seemed odd at the time, and that's clarified, I think, at a number of levels from a number of camps and vendors. >> Yeah I agree, I think we have done our best from our point of view, from the foundation, myself, and the others that are involved in our community to try to dispell those myths or tamper down that kind of sense of a rivalry, but it takes time and I do feel like there is kind of a sea change now. There are just so many people running in production with various container tools, predominantly Kubernetes and in OpenStack that I think that that sort of myth that they're, that one's replacing the other, it's hard for that cognitive dissonance to last forever when you're given like the hundredth example of like somebody running in production at scale. Like they must be doing it for a reason, and then people start to go, well why is that? >> And I did like the comment you did make about cloud is not consolidating and simplifying, right? Even at the Dell Technologies World show, Michael Dell got up and talked about the distributed core, which is a little bit of an oxymoron, but the fact is compute and compute is everywhere, right? And it's not only, it's on the edge, it's on telephone poles, it's in little boxes in our, you know, going to be on our walls, in our walls, right? And this open infrastructure idea can play everywhere. It's not just about an on-prem data center anymore. >> Yeah and I think that's a big part of why we started to say open infrastructure instead of cloud, just because, I mean, you know, I guess we spent 10 years arguing over the definition of cloud, now we can argue over open infrastructure. But to me it's a little more descriptive and a little less kind of, I don't know, a little less baggage than the term cloud. >> Yeah, definitely differentiates it as to where you sit in the marketplace. And one thing I definitely want to give the foundation great kudos on, the diversity of this show is excellent. Not just that there was a welcome happy hour and there's a lunch, but look at all the PTLs, the project leads that are there, a lot of diversity, up on stage. It's just evident. >> Mark: Thank you. >> And it's just something kind of built into the community, so great job there. >> Thank you, I'm very proud of the fact that we had just so many excellent keynote speakers this morning, and you know, that's always something that we strive for, but I feel like we got closer to the goal than ever in terms of just getting broad representation up on the stage. And some amazing leaders. >> It's always nice from our standpoint because we always say give us your keynote speakers and give us some of the main people making things happen, and it just naturally flows that we have a nice diversity, from gender, from geography. >> Yeah, absolutely. >> From various backgrounds, so that's good. All right, want to give you the final word. Take aways that you want people after the show or maybe some things that people might not know if they didn't make it here for the show. >> I mean, I think, you know, the number one take away is it's all about the people, and we want to make it about the headlines or the technology, and even the technology is about the people, but certainly the operators are not, like I said, logos don't operate clouds or infrastructure, people do, so getting to meet the people, seeing what they're doing, like the Adobe I mentioned, they're marketing cloud. They have 100,000 cores of compute with four people operating it. So if you've got the right four people and the right playbook, you can do that, too. But you got to meet those people and find out how they're doing it, get their recipe, get their playbook, and they're happy to share it, and then you can run at that kind of scale, too, without a big team and you can change the way you operate. >> Yeah, I know I said in my last question, but the last thing, I know there's been a big emphasis to not just do the two big shows a year, but the OpenStack days and other events globally, give people, how do they get involved and where can they come to find out more? >> Yeah, that's a great question. I'm glad you asked because, there are so many ways to get involved and of course it's online, it's IRC, it's mailing lists 24/7, but there's no substitute when it's about the people for meeting in person. So we have the two summits a year. We're also having an event which is called the PTG, which is really for the developers and some of the operators will be coming this fall as well where we're having it in Denver, but the summits are the big shows twice a year, but the OpenStack days are really important. Those are annual, typically one to two day events, in 15 plus countries around the world. One in particular that is going to be really exciting this year is in Beijing. You know, we've had that for the last couple of years. Huge event, but of course, others throughout Europe and Asia. Tokyo is always an awesome OpenStack day, and then there are quite a few in Europe as well. So that's another way you can get involved. Not necessarily have to fly around the world, but if you do have to fly around the world, being in Vancouver is not a bad spot, so. >> Yeah, absolutely, and boy we know there's a lot of OpenStack happening in China. >> Yes there is. >> So Mark Collier, thanks again to the foundation for allowing theCUBE to cover this. >> Sure. >> And thanks so much for joining us. >> Mark: Thank you. >> For John Troyer, I'm Stu Miniman, back here with lots more of three days wall-to-wall coverage here from OpenStack Summit 2018. Thanks for watching theCUBE. (techno music) (shutter clicks)

>> Presenter: Live from Copenhagen, Denmark, it's the Cube. Covering Kubecon and CloudNativeCon Europe 2018. Brought to you by the Cloud Native Computing foundation, and it's ecosystem partners. >> Well, welcome back everyone, we're live here with the Cube in Copenhagen, Denmark, for KubeCon 2018 Europe, via the CFCF Cloud Native Computing foundation, part of the Linux foundation. I'm John Furrier, my co-host Lauren Cooney here this week. And up next to Yaron Haviv, the founder, and CTO of Iguazio, and Doug Davis, who is the co-chair of the serverless working group, And the CNCF, as well as a developer advocate for IBM, IBM cloud. Great to see you welcome to the Cube. >> Thank you. >> Thanks. >> Thanks for coming in. So love the serverless work, and want to dig into that with a bunch of questions. So, super important trend as we see in that success functions, and all the good stuff that's going on, programmable infrastructure. So I want to dig into that. But first, Yaron, I want to get into what's going on with the business, what's new with you? Iguazio, I saw you're on the sponsorship list here, you're doing a lot of work. You have some news as well. What's going on at KubeCon, Europe for you. >> Yeah, so we're expanding on the business side very nicely, taking more momentum, and this strength towards edge analytics, edge cloud, people starting to understand that central cloud is not the only way to build clouds. We're also progressing nicely on our serverless framework, called Nuclio. It just was published, maybe eight months ago, already made 2000 stars in GitHub, you know, users. We've got some quotes, NPR's around production version of that, including strong partnership with Acer, on being able to run the same functions in Acer, and the cloud in a joint development effort, as well as customers actually using it to build real-time analytics use case in development in the cloud, and deployment in different locations. >> Our audience knows you well, you've been on the cube many times. You also write for us, as well as other blogs with your opinion pieces and commentary. It's always edgy, and strong, and right on the money, I want to ask you your thoughts on serverless, because you were there from day one, I remember the conversation. It wasn't called serverless, we were talking about resource pools and looking at cloud computing, pontificating about, potentially, what Kubernetes and orchestration was going to look like. It's happening. So, are you happy with the progress of the industry, performance of the tech stack? What's your thoughts on serverless today, state of the union? What's your opinion? >> I think it's progressing nicely. I think many people call everything almost, serverless now. You have serverless data bases, you have serverless everything. I think serverless will become, more and more, a feature of a platform, not necessarily a thing. But, like Salesforce will have serverless functions, Wix will have serverless functions, for their own stuff. Obviously cloud platforms, analytic platforms, et cetera. So there'll be, maybe a family of generic ones, and a family of platform specific, that are more use case oriented. >> Does that connect with your business plan for Iguazio? Are you evolving with it? How are you navigating those waters on the adoption side. >> So, you know, I'm sort of trying to be inclusive, I think there's room for more than one serverless framework. There's also OpenWhisk, and Openfazzer, and a few of those. Our focus is mainly real-time analytics, and high performance in data processing. Yes, we can also do other things, but maybe we won't invest too much in some features that are more front-end oriented, or stuff like that. >> John: So you're staying focused on the core. >> Yes, on the other hand, other people to deal with front-end, we'll focus on HTTP, and Blue Logic, and things like that. Most of the frameworks don't have the same capabilities of Nuclio, like real-time stream distribution, real-time, low latencies, all that stuff. So, I think there's room for multiple frameworks, and that's also part of the relationship with Acer. Acer have their own product, which is very good with integration with the Acer stack, and the Acer components. On the other hand there is real-time analytics, in IOT Nuclio is stronger, So, there interest is, rather than saying, no we'll choose just one horse, why won't we enable the market, and allow the people the choice in solution. >> That's great. On IBM's side, Doug I want to get your thoughts on the working group, as well as IBM. You guys have done a lot of open source, IBM well known in the Linux history books, as we know. And now very active again, continuing that mission, congratulations, and thanks for doing that. But the serverless working group. This is a broader scope now, can you just give us some color on the commentary around how that's evolving, because you guys have a lot of blue chip customers. Cloud Foundry just did a survey, I was talking to Abby Kearns yesterday, about the results came back, mainstream tech, not middle of the country, but they heard about Kubenettis like, what's kubenettis? So you have people going, Okay, I've got a job to do, but now kubenettis has arrived, this is a key part of a micro-services focus. >> Right. Yeah, and so the way the serverless group got started was, about a year ago the CNCF TOC, technical oversight committee, decided serverless is kind of a new technology, we want to figure out what's going on in that space, and so they started up a working group. And our job wasn't to really decide what to do about it yet, it was to sort of give us the landscape of what's going on out there, what are people doing? What does serverless even mean, relative to function of the service, or even the other as's, and stuff like that What does a serverless framework generally look like? What do people use it for? Use cases, and stuff like that. And then at the end of that we produced a white paper with our results, as well as a landscape spreadsheet, to say all of the various technologies out there in that space, who's doing what. Without trying to pick winners, just saying what's there. And then we ended with a set of recommendations in terms of what possible next steps the CNCF could do in this space, with an eye towards interoperability building more than anything else, because that's what, really, we care about. We don't want vendor lock in and all the other good stuff. And so we had a set of recommendations, and one of the main ones was, two main things, one was function signatures was a very popular one, but we decided to focus on eventing first, because we thought that might be an easier fruit to pick off the tree first. And so we were going to focus on the formats, or meta data of an event, as it transfers between systems. And so from the service working group we create a cloud events, sort of little sub-group within our working group, to focus on creating a specification around what the meta-data around an event would look like, just so we can get some commonality. That way, at least the infrastructure between the two systems can transfer the events back and forth, much in the same way HTTP layer, doesn't have to understand the body of the message, but can look at common headers, and know how to route it properly. Same kind of thing with eventing. And again, this is all about trying to get interoperability, and portability for applications, and users more than anybody else. And so that's kind of where our focus has been on. How can we help the end user not get locked into one platform, not get locked into one solution, and make their life easier overall. >> Great. Where are you now with that? Is it running? Is it-- >> Overall done. No. >> Oh you're complete, yeah (laughs) >> Doug: But we did that last week. No, actually as of last week though, we just released our first version, 0.1. It's a very, very basic thing, and people might look at it and say, what's the big deal? But even with that simple little thing we've been able to get some level of interoperability between the various platforms. And if people actually join, when is it? Friday 11 o'clock? >> Yaron: Yeah. >> We have a session where someone's going to demonstrate interoperability between, oh gosh, IBM, you guys, Microsoft. >> Google. >> Dameware, Google. All the various companies involved in this thing. >> Love it, that's great. >> Huawei. >> Yeah. They're all going to be either sending or receiving events, using the cloud event format, to prove interoperability around the specification. So we're just at 0.1, we have some way to go, but that first step was huge just to get agreement, and everybody to the table to agree. So it's been really fun >> And it wasn't easy, it wasn't easy. And he's the peacemaker in the group. (laughs) I'm the troublemaker, he's the peacemaker. >> We have a lot of vocal people in the group, yes. (laughs) >> We're not pointing at anyone. >> No, never. >> Important first step obviously, commonality, and having some sort of standardization kind of thinking. >> Doug: Yes. >> Yaron: Don't use the standard word. There are people allergic to that. >> Well yeah, the standard bodies and what not, but in terms of the community work going on, this is super important. What's the impact of that? Obviously it's a small step, but a big step, right? So, what's it going to impact? What's next, what's coming next now that you've got the meta-data, and you've got the interoperability, what's next? >> Well, obviously we need to finish it up, because 0.1 is obviously just the first step. As I said, I think beyond that people are really itching to do function signatures. Because I think if you can get the event format coming in to be somewhat similar, and then you can get portability of moving your function from one platform to another, with hopefully minimal changes from a function signature point of view, you're a long way there towards getting portability for people. And I think that's probably the next step we're going to be looking at. >> What's the technical case from a commercial entity like yourself, who's in business to make money, obviously you have a business to run. As you build out your architecture, where is this going to be applied for you? What's the impact of this project to your product? >> So beyond my strong religion around open APIs, and you've seen the blogs I've written about it, our interest is twofold. First, we're not the market leader, Amazon is the market leader, et cetera. So if we have a better technology, and things are standard, it's easier for customers to move. Second, is we believe in interoperability, closer to the data, closer to where the processing, especially when 5G is going to evolve, and we're going to see bottlenecks between metro locations. Our sales is, go develop in the cloud, and then push it, you know the diesel twin model. This is exactly what we're demonstrating with Acer. You could develop at Acer, our Nuclio functions and deploy in a factory. So it may not be the same platform, it may not be the same serverless framework. So having the ability to run the same code in different frameworks or different platforms is very important. >> And IBM, you're doing a lot of work. OpenWhisk has been something that's gotten a lot of press and notoriety. What's up with you guys and open source? Obviously we see you guys out there doing a lot of studies and a lot content, a lot of coding. What's new over on the IBM side of the house with serverless? >> From my point of view, I think probably the biggest thing is, we're leading the charge in putting OpenWhisk to run on top of Kubernetes. And I think what's interesting about that is we're going to see, probably, some changes to Kubernetes need to be made to get the better performance that we need. Because when OpenWhisk runs vanilla on top of, say run C, or the docker stuff, we have a lot more freedom there. Pausing containers, stuff like that. Stuff you can't do in Kubernetes. We're probably going to see some more pressure on Kubernetes to add some more features, to get the kind of performance numbers we need going forward. >> And scale too, is important to understand. I was just talking about the keynotes earlier with another guest, and Cern is up there. They have a thousand nodes, it's not massive numbers yet, at scale, I mean Amazon are the big clouds, you guys have clouds. You've got a lot of nodes, so it's a lot more scale going on in the cloud as Kubernetes starts to get it's footing. >> Doug: Yep. >> How do you explain Kubernetes, how do both of you guys explain Kubernetes to the IT transformation group out there, that's going cloud operations. >> So what we've seen, because we're also selling an appliance, a full integrated solution, people, in the enterprise, they don't necessarily want to understand low level of Kubernetes. And actually serverless is a nice way for doing that. If you look at the new Nuclio dashboard, you just go, you write some code, you click deploy, it auto scales, you don't need to think about the underlying cube cut whole, the underlying networking. It's all done there for you. And I think, what you see in the trend in the industry, some people call it serverless, some people call it other things, is more and more abstractions, where users will deploy code, will deploy containers, and some frameworks underneath will deal with the high availability, elasticity, all that. I think that's what enterprise customers are looking for. Not everyone is eBay, and Google, and Netflix. >> John: Your thoughts? >> What I think is interesting, I agree with what you said, but I think it's interesting is you actually have a wider range of people, right. You have some people who think Kubernetes, as you said, nice abstraction layer, you don't have to get into the nitty gritty if you don't need to. But Kubernetes does allow you to get under the covers and twiddle those lower level bits if you actually need to. I think that's one of the things that. People who start out with Docker, they like it, it's so simple to use, and it's wonderful, and they love it. But they found it a little bit limiting, because it was too opinionated, or it didn't give you access to things under the covers. Kubernetes, I think, is trying to find that right balance between the two, and I think for the most part they kind of hit it. There's a little bit more of a learning, because it's not quite as user friendly as Docker is. But once you get over that learning hump, all the flexibility it gives you, people seem to really, really, like that. >> What are some of the things that people do under the covers, you mentioned some tweaks here and there. Is it policy based stuff? What's happening under the covers that Kubernetes getting that their groove swing on now. >> There is something called custom resource definition. So for example, when we deploy a Nulio, maybe OpenWhisk or others have it as well. It's essentially, Nuclio becomes another resource that you can actually view when you're running the Kubernetes CLI, or all the other things that manage it's liveliness, et cetera. So those are services that you get for free as a platform. But if you want your function to keep being alive you need to code your functions into the liveliness API, the thing that monitors it staying alive. So you're getting a generic service, but you need to work with it. >> Yeah, actually I'd go one step further with that and abstract it a little. Because obviously Kubernetes has a lot of knobs you can turn, a lot more than other platforms, like Docker has. But I think, for me the biggest benefit of Kubernetes is the plugability. Custom resource definitions, one of them. Ripping out schedulers, or whatever controllers you want, and replace it with your own. That kind of flexibility to say, I don't have to leave the entire Kubernetes world just to run my own scheduler, or write the infrastructure around it, I can plug in my own. That's the kind of flexibility people seem to really, really like. That way they don't feel locked in, they can still play with part of the ecosystem, but get the flexibility and customization they need. >> Awesome, great commentary there. I want to get your thoughts on KubeCon 2018 Europe, for CNCF. Continuing to see growth in CNCF, fantastic to see. As the boat gets full of people, you've got to be the peacemaker if you're co-chair. As people want to start getting their claws into the projects, this imbalance on the community side, are you guys happy with the direction, obviously the success, and the visibility is increased. What's your take on the show here? What are you guys doing? What's going on around the event for you guys. >> So it only started today, but my impression, comparing it with the previous show in the U.S. There are a lot more decision makers here. I don't know if it's the European culture of not funding every student to every show, or just the maturity of the ecosystem. But that's something I've noticed, the discussions I had with decision makers. and they're also not everyone, like in the U.S.A. everyone wants to build it their own way. People here think about operationalizing solutions, so sometimes you need to take something that someone else already built and test. >> And what's the conversations like, that you're having? Is it architecture? Is it deploying production workloads? >> So for us it's a lot about use cases, because we're doing things in a very different way. We're doing some nice demos on how, we're running real-time analytics with the sample database as the core, and we're showing how it's equivalent to another solution that they may build. And that immediately clicks. The other aspect is really, there is so much technology, but we need someone to wrap it up for us as a package solution. >> Doug, your thoughts. First of all I love your shirt, it says code with all the words in the community. >> Doug: Yeah, it's one of my favorite shirts. I like it. >> Love that shirt. I'm just looking at it like, all these questions are popping in my head. What's your plan at the show here? What's your goal, what are you guys doing, what conversations are you hearing in the hallways? >> Well, obviously being from IBM, we just promote IBM as much as we can. But beyond that, really talk about interoperability around what we're doing here, and make sure people understand that we're not here to necessarily sell our products, which we obviously want to do. We want to make sure that we do it in a way that gives people choice. And that's why we have the serverless working group, the cloud events spec. It's all about giving everybody the choice to move from one platform to another, to get their job done. As much as we want people to buy our stuff, if the customer isn't happy in getting what they need, then we're all going to lose. >> And these projects are super important to get the solidarity around these, quote, standards. >> And just to follow on your previous question about the conference, and stuff that we'd like. Obviously it's great that it's growing so much, but what I really like about this conference, beyond some other ones that I've seen is, a lot of the other ones tend to have more marketing flair to them. And obviously there's a little bit of that here, people are promoting their stuff, but I love the fact that most of the stuff that I'm doing here aren't in the sessions. Because the sessions are great and interesting, but it's the hallway chatter, and interacting with people face to face, and not just to meet them, to actually have real technical, deep discussion with them, here at the conference, because everybody's here you can do that much better face to face than you can over a Zoom call, or something else. The productivity from that level is just astronomical, I love it. >> Yeah, I totally agree. And one thing I would add, just my observation, interviews in the hallways, is that we're living, and we talk about this on the Cube all the time, a modern software architectures here. And it's got some visibility around it, it's not filled in yet, but I think there's clear visibility. Cloud, micro-service, interoperability, portability, pretty clear. And I think people are engaged, people are excited. So you have the progressive new guard coming in, on board. Great job. Thanks for coming on the cube, we appreciate that. >> Thank you. >> Thank you. >> Iguazio and IBM, here on the Cube, breaking down KubeCon 2018 Europe. More live coverage, stay with us, we'll be right back after this short break. (electronic music)

>> Hey welcome back to everybody, Jeff Frick here with theCUBE. We're in our Palo Alto studio for a CUBE conversation. The crazy conference schedule is just about ready to break over our heads, but we still have a little time to do CUBE conversations before we hit the road. But one show we're doing this summer that we've never done before is Kubecon Cloud Native Con, I got to get all the words. It used to be Cloud Native, now Kubecon's up front. But we're going to go to the European show first time ever. It's May 2nd through 4th at the Bella Center in Copenhagen, Denmark. We're really excited to go 'cause obviously a ton of activity around containers and Kubecon and Kubernetes, and we're excited to have a little preview of the show with two folks. We've got Wendy Cartee, she is the Senior Director Cloud Native Applications Marketing for VMWare. Welcome. >> Thank you, it's a pleasure to be here. >> And also giving us a little preview on her keynote, maybe we can get something out of her, I don't know, Aparna Sinha, she is a Group Product Manager for Kubernetes and Google's Kubernete Engine at Google, long title. Just see the Kubernete shirt, that's all we need to see. Welcome. >> Thank you. Glad to be here. >> Absolutely. So for the folks that have not been to Kubecon before, let's go through some of the basics. How big is it? Who can they expect to be there? Do you have the fancy letter for them to give to their boss to get out of work for a week? >> Yeah, yeah. >> Give us the basics. >> This is going to be our biggest event in Europe yet. So we're expecting actually four thousand plus people. We expect that it'll be sold out. So, folks should register early. And who should go? Actually tends to be a mix of developers who want to contribute to the project as well as users. I think in Austin, which was our last conference, there was about a 50/50 mix of folks that were using Kubernetes. So it's a really great place to meet others that are using the software. >> Are there a couple of new themes this year? Or is just just kind of generic training and moving the platform along? Or are there some big announcements that people can expect? >> Yeah, I expect some big announcements. And I expect that there'll be a couple of themes around security, around Serverless, that's a major area, and around developer experience, and of course machine learning. So those are some of the things that are top of mind for the community. >> And probably Service Mesh will be another round of hot topics this year as well. >> Which one? >> Service Mesh. >> Jeff: What is that? >> It's a project that is a part of CNCF around Envoy. And it's essentially the notion of having a stack of services that provide everything from connectivity to API access for microservices. >> I ask because we had an old customer of Service Mesh saying they got bought by some services company... >> Yeah, this is, I think the term is an old term, so obviously when you start using Kubernetes it's really around breaking down your applications and having microservices. You get a proliferation of microservices. Service Mesh essentially enables you to manage those, so set up security and communication between those services and then manage them at scale, so that's really what a Service Mesh is. And Envoy is at the heart of that. And then there's a project called Istio. There will definitely be, and there was a lot of discussion around that at Kubecon in Austin. And they'll be some training before the conference this time. There are several co-located events. There'll be some training beforehand. So for folks that want to learn, they're new to Kubernetes, they're new to the concept of Service Mesh, I would recommend coming a day early or two days early, 30th and 1st, there's a number of different workshops. >> It's pretty amazing just the growth and the momentum of containers and Serverless, and obviously Docker kind of came out of nowhere a couple three or four years ago. And then Kubernetes really kind of seemed to jump on the scene in terms of at least me paying attention, probably a couple two, three years ago. And it's phenomenal. And even only just to check it out, Google's putting on all these little development workshops. This one was at Santa Clara Convention Center probably a month ago that I went down. And the place was packed, packed. And it was, get out your laptop, get out your notes, and let's start going through and developing applications and really learning. I mean, why does this momentum continue to grow so strongly? >> From what we see, we have enterprises that are in the journey of digital, you're kind of going on the digital transformation. >> Jeff: Right. >> And to drive that faster business model they need technologies like Cloud Native to help them with faster development, to help them with driving new innovations in their application, and I think that that's what we see in the Kubernetes community. I think we see developers and contributors coming to conferences like Kubecon, especially to really learn from each other and find out what are some of the latest innovations in this space and how they can bring that back into their companies to drive faster development, and at the end of it, essentially driving better services, better experience for their end users as well. >> And it's really been interesting watching the VMWare story particularly, because you know people were a little confused when the merger happened with Dell and EMC and how was that going to affect (mumbles) and VMWare, and yet, the ecosystem is super vibrant. We do VMworld every single year. It's one of our biggest shows. The thing is packed with a really excited ecosystem, obviously you guys made big moves with Amazon last year. You're making moves with Google and Kubernetes, and it was funny. People were concerned a couple years. It's almost this rebirth of what's going on at VMworld and this adoption of really (mumbles) technology as well as open source technologies. Has the culture changed inside? Is this something that you guys figured you have to do or was it always there under the covers and maybe we just weren't paying enough attention? >> Yeah, I think it was always there. I think we are very close to the transformation and the journey that our customers are on. And obviously the customers themselves have a full stack solution deployed in their environment today. Many of them are using vSphere or vSan or NSX, vRealize Portfolio to build their business, and they're looking at how to transform and add containers as another layer on top of their software defined data center, to essentially breathe some of these newer technologies into their environment as well. >> Yeah, and Aparna, Google's been sharing open source stuff for a while. Even back to early Hadoop, Hadoop days. So, as big and powerful as a company that it is and as much as scale is such an important piece of that competitive advantage, it's wild that you guys are opening things up and really embracing an open source developer kind of ethos to acknowledge. As smart as you are, as big as you are, as much power as you have, you don't have all the smartest people inside the four walls of Google. Well, Google has always contributed to open source. I think we have a very long and rich history of sharing software and, you know, really doing joint development. So Android is an open source, Chrome, Chromium is open source. TensorFlow is open source. And Kubernetes really is, I think, different in that sense in that there is a thriving community around it and Google's been very, very active, and I've been very active personally, in developing that community and engaging in the project. And I think that goes back to what you were saying about the meetups. There are several meetups all around, so it's not just in one location. I think globally. And I think the reason it's so diverse and so many people are involved is because it does lead to, you know, Kubernetes enables a benefit that is meaningful in enterprises, large and small, where you can start rolling out applications multiple times a day. And it just gives developers that productivity. It's very accessible. And over the years, especially as the project has matured, it has become, it's like my daughter or my son can go and they can use it. It's really easy to use. So it's not hard to pick up either. >> And it's also interesting because we do a lot of shows, as you know, theCUBE goes to a ton of shows, and everybody wants the attention of developer if they haven't had (mumbles) everybody's got a developer track a developer this, a developer that. Everybody wants to get to developers. It's very competitive. As a developer you have a lot of options of where you want to spend your time. But really, especially Google, kind of comes at it from, and always has, development first. Right? It's kind of developer first. So I'm curious, you talked about the community that's going to be gathered in Denmark when you've got contributors as well as users and contributors all kind of blended together. Not really forced together, but coming together around this universal gravity that is Kubernetes. What is that enable that you don't get if you're traditionally either a developer show or kind of a user show? >> Yes, I think that's really important and one of the beautiful things about open source, is that you get what you see. And you can actually change it and own it and it's not some other entity that owns it. So we'll have many companies presenting, so Bookings.com, Spotify, New York Times, Ebay, Lyft. These are all companies that are using Kubernetes and also contributing to Kubernetes. And so it's a nice virtual cycle. And what you get from that is you're in touch, you're in constant touch with your users. So a lot of them actually use Google Kubernetes Engine, and I know what they're looking for. And so we can then shape the project and shape the product accordingly. >> Then the other question I always think is interesting when you're working with open source projects and contributors, right? A lot of times it's a big part of whom they are, especially if they're a good contributor. You know, it's part of their identity, it's part of the way they connect with their community, but they got to get work done for the company, too. So in terms of kind of managing in the development world with contributing people, people contributing to open source projects as well as you got to get our work done that we're working on, too. How do you manage that? How is kind of best practices for having a vibrant open source contributing staff that's also being very productive in getting their day job done? >> I think engineers love to learn from other engineers and developers, and I think that community is the reason why they come. And it's not only our conferences when everybody gets together at a conference like Kubecon, but there's a tremendous amount of activity day to day offline over conference calls like Zoom and, you know I'm on some of the calls that Aparna is on and its amazing. You have people from all over the world, developers from everywhere, who will meet on a weekly basis, and they'll Slack each other. And I think that that sense of community, that sharing of information and really learning some of the best practices and learning what others have done is why people come, and it's great to have a conference like Kubecon where people can finally come together and meet in person and just kind of enjoy each other's presence and communicate face to face, and really connect in person. We're very excited about Kubecon and kind of being part of that energy, that enthusiasm that is in the community. >> It's interesting, the Slack, the kind of cross-enterprise Slack phenomenon, which I hadn't really been exposed to until a couple of projects we got involved with, and I got invited into these other companies' Slack, which I didn't really know that that was a thing to open up that wall in between the two companies and enable a very similar type of interaction and engagement that I have with my peers inside the walls as I do now with my peers outside the walls. So that's a pretty interesting twist in enabling these tools to build community outside of your own company. >> Yes, it is, and Slack is a great tool for that. But even aside from the tooling, I think that the pace of software innovation is very, very fast these days. And if you stay within the walls of your company you miss out on so much innovation that is available, and I totally agree with Wendy. Contributors and developers in general, they like to know what's next. And they like to contribute to what's next. And you said you went to some of the meetups, so you can sort of see that you're actually benefiting from that, from both contributing as well as from meeting with and absorbing what others are doing. You're directly benefiting your company, you're directly benefiting in your own job because you're innovating. >> So before we let you go, any particular session or something is happening at the show in Denmark that either you're super excited about or maybe is a little bit kind of flying underneath the radar that people should be aware of that maybe they didn't think to go to that type of session. >> Well I think there are a variety of excellent sessions at the Kubecon that's coming up. There are user topics. Arpana talked about some of the companies that will be there to share their experience. I've seen talks about communities and contributors and how they can contribute and build the community. I think there are SIG updates that I think would be very informative. And I also think that there are a lot of announcements that will be made at the event as well. I think that's exciting for everybody to see the new innovations that's coming out that impact the community, the users, and in general the ecosystem as well. >> Aparna? >> Yeah, yeah, so if I were to lay it out, I mean definitely folks should register early 'cause it's going to sell out. There were a thousand plus submissions and a 125 talks have been accepted. There are 31 Google talks. There's all manner of content. I would suggest users go a little bit early if they want to get the hands-on training in the workshops. And then as Wendy mentioned, I think on May 2nd there's a contributor summit, which is actually, that's the thing that's flying under the radar. It's a free event, and if you want to learn how to contribute to Kubernetes, that's where a lot of the training will be. And the SIGs, the special interest groups, in the community, each of them will be giving an introduction to what they do. So it's a really good event to meet maintainers, meet contributors, become one yourself. And then in terms of the agenda, I think I mentioned the topics. I'm giving a keynote. I think I'm giving the opening keynote there. It'll be about developer experience, because that's a big deal that we're working on in Kubernetes, and I think there's many new innovations in improving the developer experience with Kubernetes. I'll also be giving an overall project update. And then some of the other keynotes, there's a keynote on KubeFlow, which is a machine learning framework on top of Kubernetes. And then there's a series of talks on security and how to run securely in containers. >> All right, well I think we're almost ready. We got to register, we got to study up, and make a couple contributions before we're headin' over there, right? >> Absolutely. >> All right, Wendy, Aparna, thanks for taking a few minutes and look forward to seeing you across the pond in a month or so. It's May 2nd through 4th in Denmark at the Bella Center, Copenhagen, Denmark. Thanks again for stopping by. >> Wendy: Thank you. >> Aparna: Thank you. >> All right, I'm Jeff Frick, you're watching theCUBE from Palo Alto, we'll see you next time. Thanks for watchin'.

>> Narrator: Live, from Santa Clara in the heart of Silicon Valley, it's theCUBE. Covering Cloud Foundry Summit 2017. Brought to you by the Cloud Foundry Foundation and Pivotal. >> Hi this is Stu Miniman, joined with my cohost, John Troyer. Happy to welcome to the program a first-time guest, Chip Childers, who's the CTO of the Cloud Foundry Foundation. Chip, fresh off the keynote stage, >> Yep. >> how's everything going? >> It's going great. We're really happy with the turnout of the conference. We are really happy with the number of large enterprises that are here to share their story. The really active vendor ecosystem around the project. It's great. It's a wonderful event so far. >> Yeah, I was looking back, I think the last time I came to the Cloud Foundry Show, it was before the Foundation existed, We were in the Hilton in San Francisco, it was obviously a way smaller group. Tell us kind of the goals of the Foundation, doing the event, bringing the community in. >> Yeah, you can think about our goals as being of course, we're the stewards of the intellectual property, the actual software that the vendors distribute. We see our role in the ecosystem as being really two key things. One: we're focused on supporting the users, the customers, and the direct uses of the Open Source software. That's first and foremost. Second though, we want to make sure there is a really robust market ecosystem that is wrapped around this project, right. Both in terms of the distribution, the regional providers that offer Cloud Foundry based services, but also large system integrators that are helping those customers go through digital transformation. Re-platform applications, you know really figure out their way through this process. So, it's all about supporting the users and then supporting the market around it. >> Yeah, as we go to a lot of these events, you know, there are certain themes that emerge. There were two big ones that both of them showed up in what you did in the Keynote. Number one is Multicloud, number two is you got all of these various open sourced pieces, >> Chip: Yep. you know, what fits together, what interlocks together, you know which ones sit side by side. Why don't we start with kind of the open source piece first? Because you're heavily involved in a lot of those. Cloud Foundry, you know, what are the new pieces that are bolting on, or sitting on top, or digging into it, and what's going on there? >> You know, I think first I want to start with a basic philosophy of our upstream community. There are billions of dollars that rely on this platform today. And that continues to grow. Right, because we're showing up in Fortune 500, Global 2000, as well as lots of small start-ups, that are using Cloud Foundry to get code shipped faster. So our community that builds the UpStream software, spends a lot of time being very thoughtful about their technical decisions. So what we release and that what gets productized by the down streams is a complete system. From operating system all the way up to including the various programming languages and frameworks and everything in between. And because we release a complete platform, at a really high velocity, so many people rely on it's quality, we're very thoughtful about when is the right time to build our own, when should we adopt and embrace and continue to support another OpenSource project, so we spend a lot of time really thinking about that. And the areas today that I highlight around specific collaborations include the Open Service Broker API which we actually spun out of being just a Club Foundry implementation. And we embrace other communities, and found a way to share the governance of that. So we move forward as a big industry together. >> Stu: Yeah and speaking on that a little bit more. Very interesting to see. I saw Red Hat for instance speaking with Open Shift, Kubernetes is there. So, how should customers think about this? Are the path wars over? Now you can choose all the pieces that you want? Or, it's probably oversimplifying it. >> I think it's over simplifying it, it depends. You can go try to build your own platform if you want, through a number of serious components, or you can just use something like Cloud Foundry, that has solve for that. But the important thing is that we have specifically designed Cloud Foundry to allow for the backing services to come from anywhere. And so, it's both a differentiator for the various distributions of Cloud Foundry, but also an opportunity for Cloud providers, and even more importantly, it's an opportunity for the enterprise users that live in complex worlds, right? They're going to have multiple platforms, they're going be multiple levels of abstraction from Bms to containers, you know, to the path abstraction even event driven frameworks. We want that all to work really well together. Regardless of the choices you make, because that's what's most valuable to the customers. >> Okay, the other piece, networking you talked about. Why don't you share. >> Yeah, yeah so, besides the Service Broker API, we've added support for what's called Container to Container Networking. I don't necessarily need to dig into the details there, but let's just say that when you're building microservices that the application that the user is experiencing is actually a combination of a lot of different applications. That all talk to each other and rely on each other. So we want to make sure there's a policy-based framework for describing how the webs here is going to talk to the authentication service or is going to talk to the booking service, or the inventory service. They all need to have rules about how they communicate with each other. And we want to do that in the most efficient way possible. So we've adopted the Containing Networking interface as the standard plugin that is now at CNCF, the Cloud Native Computing Foundation. We think it's the right abstraction, we think it's great. It gives us access to all the fascinating work that is going on around software networking, overlay networking, industry standard API plugin to our policy-driven framework. >> Along the same theme, Kubo, a big new news project also kind of integration of some Cloud Foundry concepts with a broader ecosystem, in this case another CNCF project, Kubernetes. Could you speak a little bit to that? >> The Kubernetes community is doing a great job creating great container driven experience. You know that abstraction is all about the container. It's not about, you know, the code. So it's different than Cloud Foundry. There are workloads that make sense to run in one or the other. And we want to make sure that they run really well. Right, so the problem that we're solving with the Kuber project is what deploys Kubernetes? What supports Kubernetes if there is an infrastructure adage and a node goes offline? Right, because it does a great job of restarting containers, but if you have ten nodes in a cluster, and then now you're down to nine, that's a problem. So what Bosh does, is it takes care of solving the node outage level problem. You can also do rolling upgrades that are seamless, no downtime for the Kubernetes cluster. It brings a level of operational maturity to the Kubernetes users that they may not have had otherwise. >> Chip, can you bring us inside a little bit the creation of Kubo, is that something that the market and customers drove towards you? I talked to a couple other Cloud Foundry ecosystem members that were doing some other ways of integrating in Kubernetes. So what lead to this way of deploying it with Bosh? >> Yeah, absolutely so, it came out of a direct collaboration between Pivotal and Google. And it was driven based on Pivotal customer demand. It also, if you speak with people from Google that are involved in the project, they also see it as a need, for the Kubernetes ecosystem. So it's driven based on real-world large financial services companies that wanted to have the multiple abstractions available, they wanted to do it with a common operational platform that is proven mature that they've already adopted. And then as that collaboration board, the fruit of the project, and it was announced by Pivotal and Google several months back, they realized that they needed to move it to the vendor neutral locations so that we can continue to expand the community that can work on it, that can build up the story. >> The other topic I raised at the beginning of the interview, was the Multicloud. So in a panel, Microsoft, Google, MTC for Amazon was there. All of the Cloud guys are going to tell you we have the best platform and can do the best things for you. >> Of course they do. >> How do you balance the "We want to live in a multicultural Cloud world" and be able to go there versus "Oh I'm going to take standard plus and get in a little bit deeper to make sure that we're stickier with the customers there." What role does Cloud Foundry play? What have you seen in the marketplace for that? >> Well the public lab providers are, if you look at the services that they offer, you can roughly categorize them with two things. One, are the infrastructure building blocks. Two, are the higher level services, like their database capabilities, their analytics capabilities, log aggregation, you know, and they all have a portfolio that varies, some have specific things that are very similar. So when we talk about MultiCloud we talk about Cloud Foundry as a way to make use of those common capabilities, now they're going to differentiate based on speeds and feeds, availability, whatever they choose to, but you can then as a user have choice. And then secondarily, that Open Service Broker initiative is what's really about saying "great, there's also all these really valuable additional capabilities, that, as a user, I may choose to integrate with a Google machine learning-service, or I may choose to integrate with a wonderful Microsoft capability, or an Amazon capability." And we just want to make that easy for a developer to make that choice. >> Chip, Cloud Founder was very early in terms of a concept of a platform of services, let's not call it platform as a service right now. But you know, this platform that going to make developers lives easier, multi-target, MultiCloud we call it now, on from your laptop to anywhere. And it's been a really interesting discussion over the last couple years as this parallel container thread can come up with Kubernetes and Mesosphere and all the orchestration tools, and the focus has been on orchestration tools. And I've always thought Cloud Foundry was kind of way ahead of the game in saying "wait a minute, there's a set of services that you're going to have for full life-cycles, day two operation, at scale that you all are going to have to pull together from components." As we're doing this interview here, and this year at Cloud Foundry Summit are there anything that you think people don't kind of realize that over and over again people who are using Cloud Foundry go, "Wow I'm really glad "I had logging or identity management," or what are some of the frameworks that people sometimes don't realize is in there that actually is a huge time-savor. >> Yeah, there are a lot of operational capabilities in the Cloud Foundry platform. When you include both our Bosh layer, as well as the elastic runtime which is in the developer centers experience-- >> John: Anything that people don't often realize is in there? >> Well, I think that the right way to think of it is, it's all the things you need in one application, right? So we've been doing this for years as developers. In the applications operators team, we've been doing it. We've just been doing it via bunch of tickets, we've been doing it via bunch of scripts. What Cloud Foundry does is it takes all of those capabilities you need to really trust a platform to operate something on your behalf, and give you the right view into it, right? The appropriate telemetry, log aggregation, and know that there's going to be help monitoring there. It makes it really easy. Right, so we were talking earlier about the haiku, that Onsi Fakhouri from Pivotal had authored, it's appropriate. It's a promise that a platform makes. And platforms designed to let a user trust that the declarative nature of asking a platform to do X, Y, or Z, will be delivered. >> Chip, we've been hearing Pivotal talks a lot about Spring, when Cloud Foundry's involved. Is it so much so that the Foundation needs to be behind that, or support that? How does that interact and work? >> Well, we're super supportive of all the languages in the framework communities that are out there. You know, even if you pick a particular vendor, Pivotal in this case has a very strong investment in the Spring, Spring Cloud, Spring Boot, they're doing really amazing things. But that's also, it's our software, you know, they steward that community, so all the other vendors actually get the advantage of that. Let's take Dot Net and Microsoft. Microsoft open sourced Dot Net. So now you can run Dot Net applications on Linux. They're embrace of the container details and the APIs and their operating system is making it so that now it can also run on Windows. So the whole Microsoft technology stack, languages and frameworks, they matter quite a bit to the enterprise as well. So we see ourselves as supportive of all of these communities, right? Even ones like the Ruby community. When there's an enterprise developer that chooses to use something like Ruby, with the Ruby on Rails framework, if they use Cloud Foundry, they're getting the latest and greatest version of that language, framework, they know that it's secure, they know that it's going to be patched for them. So it's actually a great experience for that developer, that's working with the language. So, we like to support all of them, we're big fans of any that work really well with the platform and maybe integrate deeper. But it's a polyglot platform. >> We want to give you the final word. People take away from Cloud Foundry Summit 2017, what would you want them to take away? >> Yeah the simple takeaway that I can give you is that this is an absolutely enterprise grade open source ecosystem. And you don't hear that often, right? Because normally we talk about products, being enterprise great. >> Did somebody say in the keynote enterprise great mean that there's a huge salesforce that's going to try sell you stuff? (Chip laughs) Well that's coming from the buying side of the market for years. And you know, it was a bit of a joke. What is "enterprise great?" Well, it means that there's a piece of paper that says, this product will cost x dollars and the salesperson is offering it to you. So of course it's going to be enterprise great. But really, we see it as four key things, right? It's about security, it's about being well-integrated, it's about being able to scale to the needs of even the largest enterprises, and it's also about that great developer experience. So, Cloud Foundry is an ecosystem and all of our downstream distributions get the advantage of this really robust and mature technical community that is producing this software. >> Chip, really appreciate you sharing all the updates with us, and appreciate the foundation's support to bring theCUBE here. We'll be back with lots more coverage here from The Cloud Foundry Summit 2017, you're watching theCUBE. (techno music)

>> Voiceover: Live from Washington D.C., it's theCube, covering AWS Public Sector Summit 2017, brought to you by Amazon Web Services and its partner Ecosystem. >> Good morning, welcome back here on theCube, the Silicon Valley or Siliconangle TV flagship broadcast, here as we continue our coverage live from the Nation's capital, Washington D.C., the AWS Public Sector Summit 2017. I'm John Walls, we're glad to have you hear on theCube along with John Furrier, good morning. >> Morning. >> Good night? >> Great night. I had two great meetings, learned some information, got some exclusive material for a story that has to do with government stuff. >> So you were kind of working then weren't you? >> I'm always working. We're in D.C. I want to put my ear to the ground and bring all these stories back to my show, Silicon Valley Friday Show, which has been on hiatus during the month of May and June for all theCube events. >> Slacker. >> I got some great metadata as they say. (laughter) >> Good about data. >> I went home and watched the Nat's game. That was my big night. Jeff McAllister is with us now, he is the GM of the Americas for Druva and Jeff, glad to have you on theCube, we appreciate the time. >> Oh gee, thank you for the opportunity and it's a pleasure to meet you. >> Alright so you guys are all data, all the time on the Cloud right? >> That's right. >> All about data protection and security, availability. Tell us a little big more just about Druva and then we'll get into maybe your relationship with AWS but first off about you, about Druva. >> I've been fortunate to be with Druva since we really embarked on our enterprise strategy. I've been part of the team that made the investment a couple of years ago to start to pursue FedRAMP and some of the specifications for the Federal Government. And as you know, we are Cloud native. We are for the Cloud and built on the Cloud. We've been a partner with AWS for over eight years now. So we've had a very strong working relationship with them and the opportunity to come and speak here today and with you gentlemen, has really been tremendously exciting and frankly they're absolutely wonderful partners to go to market with. >> Yeah, talk about a minute about how integral that obviously is to your business to have not just a relationship, but to have the relationship that you do with AWS. >> Well, AWS obviously provides a world-class platform on which to build a service like ours. For our customers, it means tremendous levels of security, tremendous data durability, a reliability and availability of that data, but also the idea that many of our customers are very mobile. They have great geographic dispersion among their employees. Their employees are engaging in other parts of the world. So availability of that Cloud and that Cloud infrastructure, in local areas is tremendously important. And for our Federal customers, the certification for ITAR and other things that are specific to that market, having a platform like GovCloud, built specifically to their specifications, to service them, creates great leverage for us and our customers. >> John F.: I mean, eight year relationship, and that's going back. >> Yes it is. >> And they're only 10 years old and they spent their 10th birthday going on their 11th year, just AWS. So, obviously they saw some federal action right away, or public sector action right away. Nature of the Cloud, very friendly to developers back then. But still it was building blocks foundational back then. >> That's right, exactly. >> What's changed? How would you chronicalize that change other than the massive growth we've seen in the market place which we've chronicalized as well but I mean, from your perspective in the public sector, this is on a nice trajectory. >> I've been in the business now for over 30 years. Started out at Data General through Sun Microsystems and I've seen much of the industry change. The one thing that has been very impressive with the public sector, is that the interval in product innovation would come to the public sector a year or two years behind what we saw in the commercial marketplace. That time and space is absolutely shrinking down to nothing. They are pursuing the same business continuity, data transformation issues the Cloud-first strategies that our commercial customers are. And frankly, the government worker today has become more mobile. And the requirements to protect that data and secure it, are at an all-time high. And the AWS platform in combination with what we do, really provides a level of security that is hard to do on your own. >> So yesterday, we talked about a term I coined, or phrase I coined, around the seminal moments in GovCloud's history and really in the Amazon public sector. Is called "the shot heard around the Cloud", and that was the CIA deal where AWS came in and beat IBM, which had a lock-in spec and they're old-school IBM, they know how to sell. The sponsorships, they had everything locked and loaded. Who knows what they were doing, wining and dining. You know how the Federal Government is? >> Jeff: That's right. >> Things were very much picked out, everything's buttoned up and then boom, Shadow IT is happening, Amazon wins. Since then, we've seen a lot of change in how people are securing, how people are deploying. >> Jeff: Right. >> No better example than data protection because there's no wall, there's no firewall. You're in the middle of it. Talk about that dynamic about how the no walls, no perimeter in the Cloud has changed the role of data and data protection. >> Sure. So, gone are the days where we can dictate the device, how somebody wants to work, what solutions they're going to use. Cloud applications like Office 365, Box, Slack, other, have really created an environment where the IT folks, want to stimulate innovation, stimulate the work in places where people want to get done. But then provide the same level of protection and governance that they would on a non-platform solution. So, watching that evolution take place, its really driven us to really have to be mindful that we're in the performance business and with that performance we have to be respectful of the requirements from a security and protection standpoint that our customers call for. FIP certification became fundamental for us being able to service the government. That led us into the pursuit now of FedRAMP, which we're now FedRAMP ready. But all of those things provide the infrastructure to allow them to embrace these new strategies and this digital transformation, be it in my Cloud-first strategy or my mobility strategy, and be able to extend that same level of security that I would need, and provide that flexibility for my users to get their jobs done. >> Yeah and honestly, Cloud native, as you know, we love Cloud native, we've covered it. >> We do too. >> Covered it from day one. (laughs) Cloud-first is kind of like a moniker that people use. >> Sure. >> Kind of an ethos. It's more of a manifesto, it's more agile. But really Amazon has never hidden the ball in the fact what they believe the future will be and that is API economy. And from day one it's all about APIs and they believe that you should have APIs everywhere. The Cloud has no perimeter so that changes the security game. But the one thing that's emerged out of all this, is a new SaaS business model for businesses and government, and federal, and education. So everything's as a service. >> Jeff: Correct. >> That is a huge deal and this is maybe nuanced a bit, but how does public sector turn into a service model with the Cloud? 'Cause that's something that everyone's kind of going at. You have Cloud natives great, we're going to be Cloud natives, check. But really what they're getting to is, everything's as a service. >> Right. It's created a lot of flexibility in the buying process. First of all, you're bringing that elasticity of demand, right? So they are able to embrace the idea that, I only pay for the services I actually consume. So, should I have a movement in employees, should I change in structure, should my usage suddenly spike, I have the ability to adjust on the fly. That's a big part of it. But the other piece of it is that we can deliver our service at a fixed price cost for a certain period of time within that government fiscal year. So not only does it become easy to manage technologically, but from a budget stand point, it makes it a very predictable cost. I'm no longer having an explosion of data that I have to manage and go off books to try and find data to provide those IOPS and storage on sight. I can simply continue to go at the same budget level that I've already set aside. >> One dynamic that has come up while you brought this up, 'cause I think it's relevant to what we were just talking about is, lock-in. Right? I mean the word lock-in has always been vendor lock-in but really that's on one side of the coin. The other side of the coin is user lock-in. So last night, one of my secret meetings I had last night was with a senior government official and we were talking about how, they're all pissed 'cause they got Microsoft Surfaces instead of Macs. They wanted Macs. So they were just handed a bunch of Microsoft Surfaces. No offense Microsoft, I love the Surface personally, but I've got a Mac here. The point is, they didn't want it. >> Jeff: Right. >> It was forced down their throat. >> Let's just shut that for a moment here. (laughs) >> This is the old way. We made a decision, we're going with this product. So this is really the flexibility point is, very interesting, 'cause now with the Cloud, you can actually do these really agile deployments. >> Jeff: Exactly. >> And give people more choice. >> That's right. The time to value on these products, we have a very large defense contractor inside the Beltway. We were able to deploy to 23,000 users worldwide in under six weeks. But we understand that we're in the performance business and the idea that our customers could leave us at any point in time when the term is up, keeps us very conscious of the specifications that they require. And frankly, it requires us to be innovative on their behalf. Certainly taking their feedback, but really starting to anticipate their requirements, so that we continue to earn that business year over year. And frankly, if you want to talk about lock-in, SaaS provides tremendous flexibility to switch when a contractor isn't performing to spec, versus a perpetual license where I'm locked in for the duration. >> And that's a fear obviously that they're going to use their dollars wisely. I want to get you to weigh in on Druva's digital transformation in back of the customer. Obviously you guys are doing well, you're in the sweet spot, data protection is a hot area. It's one of the hottest area no one really kind of looks at, but it's really hot with the Cloud. What impact are you having with customers and how are you rolling out your value proposition to the public sector? What are the key highlights? I mean, how do they work with you? Is it FedRAMP? Is it GovCloud? Just take us through your value proposition with respect to the- >> Our value proposition, I think is fairly unique. So first, we run on the most wildly accepted Cloud platform by the public sector, AWS GovCloud. Without question the market leader there. We bring all of our experience from the commercial marketplace into that same experience on GovCloud. With the added certifications of FIPS, certification 140-2 moderate. Our FedRAMP in process. We're also HIPPA certified so that we have the ability to address HHS and FDA as some of our customers. 'Cause they also process a lot of personal information that is unique to that particular agency. But at the end of the day, the piece that really is most interesting to our public sector customers is, one, this is a very easy service to bring to the Cloud at lower cost and frankly higher value. The plethora of features and the security, the ease of management that we bring, relieving them of having to manage hundreds of terrabytes of data and apps on behalf of this service, is tremendously beneficial. The predictability of the cost year over year, makes it very very easy to manage. But I think the biggest thing that people have come to embrace is that the innovation that takes place in the Cloud comes to market so much faster in the Cloud. Just think of the QA cycles and how they've been reduced 'cause we're QAing for one platform. Being able to consistently, quarter in, quarter out, deliver that additional feature set and additional value, at no additional cost to our customers, is really what they've really gelled around. >> How do you guys handle the certification processes that are going? I'm sure there'll be more. I mean, they're coming. With all the free-flowing data, I'm sure there's going to be a lot of regulations and policies and governance issues. But you've got to move fast. How do you guys move fast to certify? Is there a secret sauce? Is there a secret playbook? How do you guys stay on top of it? 'Cause automations, machine learning, what's the secret sauce? >> You know, I think it's interesting, part of the uniqueness that is Druva I think is, our ability to anticipate market demand. I think we have a very experienced team of individuals. Look at the choice to go to AWS eight years ago. It was unthinkable at that time, but its turned out to be a visionary sort of choice. We identified that FedRAMP and FIPs certification, three or four years ago, was an absolute mandate to play in this marketplace. So we went there way ahead of our success in the market but we saw a very unique opportunity to go there. So I think it's just a tremendously creative group of people. It's a very dynamic marketplace. And it's one that requires a little bravery and a little bit of thinking in advance of the marketplace. I don't know that we have any magic sauce, but so far it's worked pretty well. I think it's worked out alright. >> I always ask just to see. >> Although that's a good question. >> To that point though, eight years ago when you went, it was a leap right? >> It was. >> Big leap. And now here you are 2017, things are rolling along. I imagine your sale or your pitch has taken on a different tone because you have so much proof in the pudding now, right? >> Oh, it does. A long time ago it was strictly backup. We've now moved into governance, e-discovery, the idea of user behavior analysis so I can find anomalies that may occur so that I can avoid Cryptolocker or other sorts of viruses or things that may be able to affect the operation of my customers. All of those things have come into play that weren't there four years ago. So it's really been an advancement of the added services beyond what we just did in backup, that have really kind of driven the business and differentiated us from the market. But it's still kind of fundamentally that idea that I'm going to protect your data, make it available to you and separate now from your device and really help you manage your data wherever you're doing your work. >> I know we're running tight on time, I do want to get one more question in from your perspective because again, present and creation is really a benefit to Druva, congratulations on that. You get to ride the wave and now the wave is bigger and more sets coming in. That's to use the surfing analogy. But talk about the perspective from your personal standpoint, just the changes going on in this marketplace right now. Teresa Carlson, when we were commenting on our opening, how tenacious she's been. She's knocked on a lot of doors. Eight years ago, what the hell's cloud? No one even knew what it was right? And then the shot heard around the Cloud with the CIA deal and just more and more and more in them, this is just a great business opportunity for Amazon Web Services, not just the enterprise, which they're doing well in now. >> Right. >> They own the startup market. This could be, it could have a 90% market share of public sector. >> That's right, that's right. >> John F.: Talk about the change. What's going on? Is it the perfect storm? Is it like right now, what's the progress. >> Well you know, it seems like its a perfect storm but for somebody who's been banging at it for the last four or five years, it seems to be a little bit more evolutionary. But it's interesting, when I started at Druva, if I looked across our opportunities across the Americas. It was fairly evenly split between the idea that I'm going to do this on premise or I'm going to do it in the Cloud. Today, if I look across all o6f North America and all the commercial entities and public sector entities that we're dealing with, we're probably engaged in well over 500 opportunities at any one time, literally less than two, quarter over quarter, is now on premise. People have come to embrace the idea that this is a place where I can conduct business safely and securely. And frankly, for us, you look at that digital transformation or business transformation, we become two really compelling services to start and experiment with moving to the Cloud. So very often, we are the tip of that spear. Lets backup our endpoint devices to the Cloud, let's get out of that business, 'cause we can do it much more effectively with Druva than we can for ourselves at less cost. >> It's almost the reverse of what on prem was. I've had many opportunities where I've bumped into IT practitioners, friends and what not in the industry. "Oh, I forgot to do the backup plan. I got the procurement going on." It's kind of an afterthought, it's been kind of an afterthought. I am oversimplifying but generally, it's not the primary. When you go outside the walls of a company, into the Cloud where there's no perimeter, it's the first conversation. >> That's right. >> So I hear what you're saying and I totally agree. This is unique, it's a complete flip around. >> Well it's amazing. So often, we're backing up server data to the cloud. So now it used to be just backing up to the Cloud. Now it's, I have the application running in the Cloud and I want to back it up and secure it into another Cloud. It's completely morphing into all sorts of interesting places. But the part that's really interesting is that we will bring to our customers disaster recovery, for example. Well that's a service, we turn it on and if you never experience the disaster, you don't pay for it. It just creates a whole new mindset of how we're going to think and how we're going to approach the infrastructure that we're now building. >> No license fee. It's just if you need it, you get whacked on it and you deserve to get whacked on it because you need the service. >> Well, they know what the cost will be. We've set it up for a nominal fee but if you're fortunate enough that you never experience the problem, why should you pay for it. So literally cutting that price in half, removing the requirement of 2XL Servers and 430 tip. >> John F.: It's a new operating model. >> That's right. And the flexibility that it creates to change to your computing requirements is just phenomenal. >> Well, phenomenal, I think would be a way to describe your ascent as well. >> Oh thank you. >> So congratulations on that front. Glad you could be with us Jeff, at the show. Continued success and we hope to see you down the road on theCube. >> John, John, it was a real pleasure. >> John W.: First time right? >> It was, it was, thank you. >> John W.: You're a tour alum now or a Cube alum. (laughs) >> John F.: Cube alumni. >> Good to have you with us. >> Jeff: Thank you, thank you so much. >> Jeff McAllister with Druva. Back with more here from AWS Public Sector Summit 2017 on theCube. You're watching live in Washington D.C..