(gentle upbeat music) >> Hello everyone, and welcome back to KubeCon CloudNativeCon here in Detroit, Michigan. My name is Savannah Peterson, joined with John Furrier. John, we are in the meat of the conference. >> It's really in crunch time, day two of three days of wall-to-wall coverage and this next guest is running the show at CNCF, the OG and been in the community doing a great job. I'm looking forward to this segment. >> Me too. I'm even wearing... You may notice, I am in my CNCF tee, and I actually brought my tee from last year for those of you. And the reason I brought it, actually, I want to use this to help introduce our next guest is the theme last year was resistance realized, and I think that KubeCon this year is an illustration of that resistance realized. Please welcome Priyanka Sharma to the show. Priyanka, thank you so much for being here with us. >> Thank you for having me. >> This is your show. How are you feeling right now? What does it feel like to be here? >> It's all of our show. I am just another participant, but I am so happy to be here. I think this is our third hybrid in person back event. And the whole ecosystem, we seem to have gotten into the groove now. You know, the first one we did, was in LA >> Savannah: Yes. >> Where you have that shirt from. Then we went to Valencia, and now here in Detroit I could sense the ease in the attendees. I can sense that it just feels great for everyone to be here. >> Savannah: Yeah. >> And you guys, who were face to face in LA, but this is really kind of back face to face, somewhat normalized, right? >> Priyanka: Yeah. >> And so that's a lot of feedback there. What's your reaction? Because the community's changed so much in three years, >> Savannah: Yes. >> Even two years, even last year. Where do you see it now? Because there's so much more work to do, but it feels like it's just getting started, but also at the same time it feels like people are celebrating at the same time. >> Yeah. >> Kubernetes is mainstream, CloudNative at scale. >> Savannah: That feels like a celebration. >> People are talking about developer... more developers coming on board, more traction, more scale, more interoperability, just a lot of action. What's your thoughts? >> I think you're absolutely right that we are just getting started. I've been part of many open source movements and communities. This is... I think this is something special where we have our flagship project considered mainstream, but yet so much to be done right over there. I mean, you've seen announcements around more and more vendors coming to support the project in, you know, the boring but essential ways that happened I think this week, just today, I think. And so Kubernetes continues to garner support and energy, which is unique in the ecosystem, right? Because once something becomes mainstream, normally, it's like, "Okay, boring." (John laughs) But that's happening. And I think the reason for that is CloudNative. It's built upon Kubernetes and so much more than Kubernetes. >> We have 140 plus projects >> Absolutely. >> and folks have a choice to contribute to something totally cutting edge or something that's, you know, used by everyone. So, the diversity of options and room for innovation at the same time means this is just the beginning. >> And also projects are coming together too. >> Priyanka: Yes. >> You're starting to see formation, you're starting to see some defacto alignment. >> Priyanka: Yes. >> You're starting to see the- >> Priyanka: Clustering. >> Some visibility into how the big moves are being playing out, almost the harvesting of that hard work. >> Priyanka: Yes, I do think there is consolidation, but I would definitely say that there's consolidation and innovation. >> John: Yeah. >> And that is something... I genuinely have not seen this before. I think there are definitely areas we're all really focusing on. I talked a lot about security in my keynote because it continues to gain importance in CloudNative, whether that is through projects or through practices. The same, I did not mention this in my keynote, but around like, you know, continuous delivery generally the software delivery cycle, there's a lot coming together happening there. And, you know, >> John: Yeah. >> many other spaces. So, absolutely right. >> Let's dig in a little bit actually, because I'm curious. You get to see these 140 plus projects. >> Yes. >> What are some of the other trends that you're seeing, especially now, as we're feeling this momentum around Kubernetes? The excitement is back in the ecosystem. >> Yes. So, so much happening. But I would definitely say that like the underlying basis of all these projects, right? I brought that up in my keynote, is the maintainers. And I think the maintainer group, is the talent keeps thriving and growing, the load on them is very heavy though. >> Savannah: Yeah. >> And I do think there's a lot more we all company, the companies around us need to do to support these people, because the innovation they're bringing is unprecedented. Besides Kubernetes, which has its own cool stuff all the time. I think I'm particularly excited about the Argo projects. >> Savannah: Yeah. >> So, they're the quadruplets as I like to call them. Right? Because there's four of them within the Argo banner. I had Yuan from Argo on my keynote actually. >> Savannah: Oh, nice. >> Alongside Hiba from Kubernetes. And we talked about their maintainer journey. And it's interesting. Totally different projects. Same asks, you know, which is more support and time from employers, more ways to build up contributors and ultimately they love the CNCF marketing supports. >> That Argo project's really in a great umbrella. There are a lot of action going on. Arlon, I saw that. Got some traction. A lot of great stuff. The question I want to ask you, and I want to get your reaction to this, you know, we always go to a lot of events with theCUBE and you can always tell the vibrant of the ecosystem when you see developers doing stuff, projects going on. But when you start seeing the commercialization >> Priyanka: Yes. >> The news briefings coming out of this show feels a lot like reinvent, like it's like a tsunami. I've never seen this much news. Everyone's got a story, they got announcing products. >> Savannah: That was a lot of news. That's a great point, John. >> There was a lot of flow even from the CNCF. >> Yeah. >> What's your reaction to that? I mean like to me it's a tell sign of activity, certainly, >> Right. >> And engagement. >> Right. >> But there's real proof coming out, real visibility into the value propositions, >> Priyanka: Yes. >> rendering itself with real products. What's your reaction to the news flow? >> Absolutely. I think it's market proof, like you said, right? >> Savannah: Yeah. >> That we have awesome technologies that are useful to lots of people around the world. And I think that, I hope this continues to increase. And with the bite basket of project portfolios that's what I hope to see. CNCF itself will continue supporting the maintainers with things like conformance programs which are really essential when you are... when you have people building products on top of your projects and other initiatives so that the technological integrity remains solid while innovation keeps happening. >> I know from a little birdie, Brendan, good friend of mine that you had a board meeting today. >> Priyanka: Yes. >> And I am curious because I hope I'm not going out about an assumption I imagine that room is full of passionate people. >> Priyanka: Absolutely. >> CNCF board would be a wild one. (Priyanka laughs) What are the priorities for the board between now and KubeCon next year? >> Sure. So the CNCF governing board is an over... It's like an oversight body. And their focus is on working with us on the executive team to make sure that we have the right game plan for the foundation. They tend to focus on the business decisions, things such as how do we manage our budget, how do we deploy it, and what are the initiatives? And that's always their priority. But because this is CloudNative and we are all technologists who love our projects, >> Savannah: Yeah. >> we also engage closely with the technical oversight committee who was in the said meeting that we just talked about. And so lots of discussions are around project health, sustainability. How do we keep moving? Because as you said, Kubernetes is going mainstream but it's still cool. There are all these other cool things. It's a lot going on, right? >> Savannah: Yeah. You got a lot of balls in the air. It's complex decision making and balancing of priorities. >> Priyanka: Yes. >> John: And demands, stakeholders. You have how many stakeholders? Every project, every person, every company. >> Everyone's a stakeholder. You're a stakeholder, too. >> And a hundred... I mean, I love how community focused you are. Obviously we're here to talk about the community. You have contributors from 187 different countries. >> Priyanka: It's one of the things I'm the most proud of. >> Savannah: It's... Yeah. It gives me all the feels as a community builder as well. >> Priyanka: Yeah. >> What an accomplishment and supporting community members in those different environments must be so dynamic for you and the team. >> Absolutely, and it behooves us to think globally in how we solve problems. Even when we introduce programs. My first question is, are we by accident being, let's say, default U.S. or are we being default Europe, whatever it may be because we really got to think about the whole world. >> John: It's global culture, it's a global village. >> Priyanka: Yes. >> And I think global now more than ever is so important. And, the Ukraine >> Priyanka: Yes. >> discussion on the main stage was awesome. I love how you guys did that because this is impacting the technology. We need the diverse input. Now I made a comment yesterday that it's going to make... it might slow things down. I meant as is more diversity, there's more conversations. >> Priyanka: Yes. >> But once people get aligned and committed, that's where the magic happens. Share your thoughts on the global diversity, why it's important, how things are made, how decisions are made. What's the philosophy? Because there's more to get your arms around. >> Yes, absolutely. It may seem harder or slower or whatever but once it gets done, aligned and committed, the product's better, everything's better. >> Priyanka: Yes, absolutely. I think the more people involved, the better it is for sure. Especially from a robustness resilience perspective. Because you know, as they say, sunlight makes bugs shallow. That's because the more eyes on something the faster people will solve problems, fix bugs and make, you know, look for security, vulnerability, solve all that. So especially in those areas, I think, where you want to be more resilient, the more the people, the better it is. A hundred percent. And then when it comes to direct technical direction and choosing a path, I think that's where, you know it's the role of the maintainers. And as I was saying there's only a thousand audit maintainers for 140 plus projects, right? So they are catering- >> Wow, they have a lot of responsibility. >> Right. >> Serious amount of responsibility. >> It's crazy. I know. And we have to do everything we can for those people because they are the ones who set the vision, set the direction, and then 176,000 plus contributors follow their lead. So we have... I think, the bright mechanisms of contribution and collaboration in a global way are in place. And we keep chugging along and doing better and better each year. >> What's next for you guys? You got the EU of show coming out, >> Priyanka: Correct, Amsterdam. the economy looking, I don't see your recession for technology, but that's me. I'm Polish on tech. Yeah, there's some layoffs going on, some cleaning up, overinflated expectations on valuations of startups, but I don't see this stopping or slowing down. But what's your take? >> Priyanka: Yeah, I mean, as I said in my keynote, right? Open source usage soars in times of turmoil and financial turmoil is one example of that. So we are expecting growth and heavy growth this year, next year and onwards. And in fact, going back to the whole maintainer journey, now is a time there's even more pressure on them and companies as they manage their, you know, workforces and prioritization, they really need to remember they're building products off of open source. They are... This is open sources on which what their business realize, whether they're a vendor or end user and give maintainers a space time to work on what they need to work on. >> Yeah. They need a little work-life balance. I mean the self-care there, I can't even imagine the complexity of the decision matrix in their mind. Speaking of that, and obviously you... Culture must be a huge part of how you lead these teams. How do you approach that as leader? >> I think the number one... So the foundation is a very small set of staff, just so you know. >> Savannah: I was actually... Let's tell the audience, how many people are on the team? >> Priyanka: You know, it's actually a difficult question because we have folks who like spin up and down and we have matrix support from the Linux Foundation, but about 30 people in total are dedicated to CNCF at any given time. >> Savannah: Wow. >> But compared... >> Savannah: You all do hard work. >> Yes. >> Savannah: You're doing great. I am impressed. >> It's a flat organization. >> It's pretty flat. >> Seriously, it's beautiful. >> It's actually in some ways very similar to the projects and there the, you know, contribution communities there where it's like everyone kind of like steps up and does what needs to be done, which is wonderful and beautiful, but with the responsibility on our shoulders, it's definitely a balancing act. So first off, it is, I ask everyone to have some grace for the staff. They are in a startup land with no IPO on the other side of the rainbow. They're doing it because they love love, love this community and technology so much. >> John: Yeah. Yeah, and then also they're acknowledging that nobody in open source wants to see a bureaucracy. >> Priyanka: Right. >> I mean, everyone see lean, efficient. >> Savannah: Yeah, absolutely John. It's great. It's a great point. And and I think that it's just... It's amazing what passionate people can do if given the opportunity. Let's talk a little bit about the literal event that we're at right now. >> Priyanka: Yes. >> Theme today, building for the road ahead. >> Priyanka: Yes. >> What was the inspiration for that? >> Detroit. (group laughs) We're in Detroit, people drive here. >> Savannah: In case you didn't know, cars have been made in this city. >> Motor city. >> It's everywhere being here in this city, which is awesome. >> But you know, it did... There was of course a geographical element but it also aligns with where we're at, right? >> Savannah: Yeah. >> We're building for the road ahead, which frankly given the changes going on in the world is a bumpy road. So it's important to talk about it. And that's what the theme was. >> And how many folks have shown up... This is a totally different energy from Los Angeles last year. I'm sure we can both agree. Everyone was excited last year, but this is an order of magnitude. >> Yes. >> How many folks do you think are milling around? >> Yeah, it's much more than double of Los Angeles. We are close to 8,000. >> Savannah: That's amazing. And it's so... You're absolutely right. The energy is just... >> Savannah: Way up. >> It's so good. People are enjoying themselves. It's been lovely. >> That's great. So you're feeling good? You're riding the high? >> Congratulations. >> Awesome. >> Yeah, thank you. I mean, I'm a little bit of a zombie right now. (group laughs) >> You don't look it, we wouldn't know. Nobody knows. They don't know. >> If you want to take a break, We got 12 interviews tomorrow. (Savannah and Priyanka laughing) You can co-host with us. We'd love to have you. >> Exactly. You're welcome anytime. Welcome anytime, Priyanka. >> Well thank you. But no, it's been such a wonderful show and you folks are part of the reason you say everybody here is contributing to the awesomeness. >> John: Yep. >> You're part of it. Look at your smiley faces. >> John: And Lisa Marty is over there. Lisa's over there. >> Yes! >> Say hi to Lisa and team. >> Yes, the team is awesome. >> Guys, thank you for your support for theCUBE. We really appreciate it. We enjoy it a lot. And we love the community. Thank you. >> Yes. Thank you for your support for CloudNative. >> Thank you. >> One last thing I just want to point out, because it's not always it happens in this industry. The women outnumber the men on this stage right now. >> John: Proud of that? >> And I know the diversity and inclusion is a priority for CNCF. >> Priyanka: Top priority. >> Yeah. Can you tell us a little bit more about that? >> Yes. It is something at the forefront of my mind, no matter what we do. And it's because I have such great role models. You know, when I was just a participant in the ecosystem, Dan Conn was leading the foundation and he took it so seriously to always try to uplift people from a diverse backgrounds and bring those faces into CloudNative. >> Savannah: Yes. >> And he made a serious lasting impact. >> John: Yes. >> And I am not going to let that go to waste. It's not going to be me who drops the ball. (group laughs) >> We're behind you all the way. >> Right? >> We see improvement over here. >> We got your back. >> I mean, even from an attendance perspective on stage I feel like you've done just an outstanding job with the curation and representation. I don't say that lightly. It really matters to me. But even in the audience looking around, it's so refreshing. Even it sounds silly. The shirts are more fitted. >> It's not silly. >> There's different types of shirts, and I mean, you know how it is. We've been in this industry long enough. >> It's a shirt you want to wear. >> Savannah: Exactly. And that's the whole point. I absolutely love it. Have we announced a location for KubeCon North America 2023, yet? >> It's Chicago. >> Savannah: Exciting! >> Yes. >> Savannah: All right. So we'll be seeing you >> Midwest. >> not that far away. >> This is the first time I've said this publicly, I just realized, It's Chicago, people. >> The scoop, yay! >> Oh, I feel so lucky we got to break the scoop. I was learning from John's lead there and I'm very excited. Amsterdam, Chicago. It's going to be absolutely >> I'll get my hotel now. >> Fantastic. >> Yes. >> Smart move. Everybody listen to him. >> Yeah, right? Especially after Detroit. It's actually not a... It's not a bad move. Priyanka, is there anything else you'd like to say to folks? Maybe they're thinking about coming or contributing to the ecosystem? >> Priyanka: Yes. Anyone and everyone can and should contribute and join us. The maintainers are holding us all up. Let's rally to support them. We have more and more programs to do that. As you know, we did ContribFest here this week which was the first time. So we will help you get involved so you're not on your own. So that's my number one message, which is anyone and everyone, you're welcome here. We'll make sure you have a good time. So just come. >> Okay. Please do it. >> I can tell you that Priyanka is not blowing smoke. I feel very welcome here. This community has welcomed me as a non-technical, so I think you're absolutely preaching the truth. Priyanka, thank you so much for being here with us today on the show, for helping herd the cats and wrangle the brilliant minds that make CNCF possible. And honestly for just bringing your energy and joy to the entire experience. John, thank you for hanging out with me. >> I'm glad I can contribute in a small way. >> I was going to say... I was going to say thank you for founding theCUBE so that we could be here in this little marriage and collaboration can be possible. And thank all of you for tuning in to theCUBE here, live from Detroit, Michigan. My name is Savannah Peterson. I am thrilled to be sharing this content with you today and I hope to see you for the rest of our interviews this afternoon. (gentle upbeat music)

>>Hey everyone. Welcome back to the Cube's live coverage of snowflake summit 22 live from Las Vegas. Caesar's forum. Lisa Martin here with Dave Valante. We've got a couple of guests here. We're gonna be talking about every day. AI. You wanna know what that means? You're in the right spot. Kurt UL joins us, the chief customer officer at data ICU and the mod Conn, the head of AI and ML strategy at snowflake guys. Great to have you on the program. >>It's wonderful to be here. Thank you so much. >>So we wanna understand Kurt what everyday AI means, but before we do that for the audience who might not be familiar with data, I could give them a little bit of an overview. What about what you guys do your mission and maybe a little bit about the partnership? >>Yeah, great. Uh, very happy to do so. And thanks so much for this opportunity. Um, well, data IKU, we are a collaborative platform, uh, for enterprise AI. And what that means is it's a software, you know, that sits on top of incredible infrastructure, notably snowflake that allows people from different backgrounds of data, analysts, data, scientists, data, engineers, all to come together, to work together, to build out machine learning models and ultimately the AI that's gonna be the future, uh, of their business. Um, and so we're very excited to, uh, to be here, uh, and you know, very proud to be a, a, a very close partner of snowflake. >>So Amad, what is Snowflake's AI strategy? Is it to, is it to partner? Where do, where do you pick up? And Frank said today, we, we're not doing it all. Yeah. The ecosystem by design. >>Yeah. Yeah, absolutely. So we believe in the best of breed look. Um, I think, um, we, we think that we're the best data platform and for data science and machine learning, we want our customers to really use the best tool for their use cases. Right. And, you know, data ICU is, is our leading partner in that space. And so, you know, when, when you talk about, uh, machine learning and data science, people talk about training a model, but it's really the difficult part and challenges are really, before you train the model, how do you get access to the right data? And then after you train the model, how do you then run the model? And then how do you manage the model? Uh, that's very, very important. And that's where our partnership with, with data, uh, IKU comes in place. Snowflake provides the platform that can process data at scale for the pre-processing bit and, and data IKU comes in and really, uh, simplifies the process for deploying the models and managing the model. >>Got it. Thank >>You. You talk about KD data. Aico talks about everyday AI. I wanna break that down. What do you mean by that? And how is this partnership with snowflake empowering you to deliver that to companies? >>Yeah, absolutely. So everyday AI for us is, uh, you know, kind of a future state that we are building towards where we believe that AI will become so pervasive in all of the business processes, all the decision making that organizations have to go through that it's no longer this special thing that we talk about. It's just the, the day to day life of, uh, of our businesses. And we can't do that without partners like snowflake and, uh, because they're bringing together all of that data and ensuring that there is the, uh, the computational horsepower behind that to drive that we heard that this morning in some of the keynote talking about that broad democratization and the, um, let's call it the, uh, you know, the pressure that that's going to put on the underlying infrastructure. Um, and so ultimately everyday AI for us is where companies own that AI capability. They're building it themselves very broad, uh, participation in the development of that. And all that work then is being pushed down into best of breed, uh, infrastructure, notably of course, snowflake. Well, >>You said push down, you, you guys, you there's a term in the industry push down optimization. What does that mean? How is it evolving? Why is it so important? >>So Amma, do you want to take a first step at that? >>Yeah, absolutely. So, I mean, when, when you're, you know, processing data, so saying data, um, before you train a, uh, a model, you have to do it at scale, that that, that data is, is coming from all different sources. It's human generated machine generated data, we're talking millions and billions of rows of data. Uh, and you have to make sense of it. You have to transform that data into the right kind of features into the right kind of signals that inform the machine learning model that you're trying to, uh, train. Uh, and so that's where, you know, any kind of large scale data processing is automatically pushed down by data IQ, into snowflakes, scalable infrastructure. Um, so you don't get into like memory issues. You don't get into, um, uh, situations where you're where your pipeline is running overnight, and it doesn't finish in time. Right? And so, uh, you can really take advantage of the scalable nature of cloud computing, uh, using Snowflake's infrastructure. So a lot of that processing is actually getting pushed down from data I could down into the scalable snowflake compute engine. How >>Does this affect the life of a data scientist? You always hear a data scientist spend 80% of the time wrangling data. Uh, I presume there's an infrastructure component around that you trying, we heard this morning, you're making infrastructure, my words, infrastructure, self serve, uh, does this directly address that problem and, and talk about that. And what else are you doing to address that 80% problem? >>It, it certainly does, right? Uh, that's how you solve for, uh, data scientists needing to have on demand access to computing resources, or of course, to the, uh, to the underlying data, um, is by ensuring that that work doesn't have to run on their laptop, doesn't have to run on some, you know, constrained, uh, physical machines, uh, in, in a data center somewhere. Instead it gets pushed down into snowflake and can be executed at scale with incredible parallelization. Now what's really, uh, I important is the ongoing development, uh, between the two products, uh, and within that technology. And so today snowflake, uh, announced the introduction of Python within snow park, um, which is really, really exciting, uh, because that really opens up this capability to a much wider audience. Now DataCo provides that both through a visual interface, um, in historically, uh, since last year through Java UDFs, but that's kind of the, the two extremes, right? You have people who don't code on one side, you know, very no code or a low code, uh, population, and then a very high code population. On the other side, this Python, uh, integration really allows us to, to touch really kind the, the fat center of the data science population, who, uh, who, for whom, you know, Python really is the lingua franca that they've been learning for, uh, for decades now. Sure. So >>Talking about the data scientist, I wanna elevate that a little bit because you both are enterprise customers, data ICO, and snowflake Kurt as the chief customer officer, obviously you're with customers all the time. If we look at the macro environment of all the challenges, companies have to be a data company these days, if you're not, you're not gonna be successful. It's how do we do that? Extract insights, value, action, take it. But I'm just curious if your customer conversations are elevating up to the C-suite or, or the board in terms of being able to get democratize access to data, to be competitive, new products, new services, we've seen tremendous momentum, um, on, on the, the part of customer's growth on the snowflake side. But what are you hearing from customers as they're dealing with some of these current macro pains? >>Yeah, no, I, I think it is the conversation today, uh, at that sea level is not only how do we, you know, leverage, uh, new infrastructure, right. You know, they they're, you know, most of them now are starting to have snowflake. I think Frank said, uh, you know, 50% of the, uh, fortune 500, so we can say most, um, have that in place. Um, but now the question is, how do we, how do we ensure that we're getting access to that data, to that, to that computational horsepower, to a broader group of people so that it becomes truly a transformational initiative and not just an it initiative, not just a technology initiative, but really a core business initiative. And that, that really has been a pivot. You know, I've been, you know, with my company now for almost eight years, right. Uh, and we've really seen a change in that discussion going from, you know, much more niche discussions at the team or departmental level now to truly corporate strategic level. How do we build AI into our corporate strategy? How do we really do that in practice? And >>We hear a lot about, Hey, I want to inject data into apps, AI, and machine intelligence into applications. And we've talked about, those are separate stacks. You got the data stack and analytics stack over here. You got the application development, stack the databases off in the corner. And so we see you guys bringing those worlds together. And my question is, what does that stack look like? I took a snapshot. I think it was Frank's presentation today. He had infrastructure at the lowest level live data. So infrastructure's cloud live data. That's multiple data sources coming in workload execution. You made some announcements there. Mm-hmm, <affirmative>, uh, to expend expand that application development. That's the tooling that is needed. Uh, and then marketplace, that's how you bring together this ecosystem. Yes. Monetization is how you turn data into data products and make money. Is that the stack, is that the new stack that's emerging here? Are you guys defining that? >>Absolutely. Absolutely. You talked about like the 80% of the time being spent by data scientists and part of that is actually discovering the right data. Right. Um, being able to give the right access to the right people and being able to go and discover that data. And so you, you, you go from that angle all the way to processing, training a model. And then all those predictions that are insights that are coming out of the model are being consumed downstream by data applications. And so the two major announcements I'm super excited about today is, is the ability to run Python, which is snow park, uh, in, in snowflake. Um, that will do, you know, you can now as a Python developer come and bring the processing to where the data lives rather than move the data out to where the processing lives. Right. Um, so both SQL developers, Python developers, fully enabled. Um, and then the predictions that are coming out of models that are being trained by data ICU are then being used downstream by these data applications for most of our customers. And so that's where number, the second announcement with streamlet is super exciting. I can write a complete data application without writing a single line of JavaScript CSS or HTML. I can write it completely in Python. It's it makes me super excited as, as a Python developer, myself >>And you guys have joint customers that are headed in this direction, doing this today. Where, where can you talk about >>That? Yeah, we do. Uh, you know, there's a few that we're very proud of. Um, you know, company, well known companies like, uh, like REI or emeritus. Um, but one that was mentioned today, uh, this morning by Frank again, uh, Novartis, uh, pharmaceutical company, you know, they have been extremely successful, uh, in accelerating their AI and ML development by expanding access to their data. And that's a combination of, uh, both the data ICU, uh, layer, you know, allowing for that work to be developed in that, uh, in that workspace. Um, but of course, without, you know, the, the underlying, uh, uh, platform of snowflake, right, they, they would not have been able to, to have re realized those, uh, those gains. And they were talking about, you know, very, very significant increases in inefficiency everything from data access to the actual model development to the deployment. Um, it's just really, really honestly inspiring to see. >>And it was great to see Novartis mentioned on the main stage, massive time to value there. We've actually got them on the program later this week. So that was great. Another joint customer, you mentioned re I we'll let you go, cuz you're off to do a, a session with re I, is that right? >>Yes, that's exactly right. So, uh, so we're going to be doing a fireside chat, uh, talking about, in fact, you know, much of the same, all of the success that they've had in accelerating their, uh, analytics, workflow development, uh, the actual development of AI capabilities within, uh, of course that, uh, that beloved brand. >>Excellent guys, thank you so much for joining Dave and me talking about everyday AI, what you're doing together, data ICO, and snowflake to empower organizations to actually achieve that and live it. We appreciate your insights. Thank you both. You guys. Thank you for having us for our guests and Dave ante. I'm Lisa Martin. You're watching the Cube's live coverage of snowflake summit 22 from Las Vegas. Stick around our next guest joins us momentarily.

>>And welcome to the DockerCon cube cover here on the main stage. So HIRA RA development manager at J Frogg. Welcome to the cube. You guys have been on many times, uh, with J Frogg on the cube, great product you guys are doing great. Congratulations on all the six. Thanks for coming on the cube. >>Thank you. Thank you for having >>Me. So I'm really interested in talking about the supply chain, uh, package management, supply chain, and software workflow, huge discussion. This is one of the hottest issues that's being solved on by, with, with in DevOps and DevSecOps in, in the planet. It's all over the, all over the news, a real challenge, open source, growing so fast and so successful with cloud scale and with automation, as you guys know, you gotta ha you gotta know what's trusted, so you gotta build trust into the, the product itself. So developers don't have to do all the rework. Everyone kind of knows this right now, and this is a key solve problem you guys are solving. So I gotta ask you, what is the package management issue? Why is it such an important topic when you're talking about security? >>Yeah. Uh, so if you look at, uh, look at how software is built today, about 80 to 90% of that is open source. And currently the way we, the way we pull those open source libraries, we just, we just have blind trust in, in repositories that are central, and we rely on whatever mechanism they have built to, to establish that trust, uh, with the developer who is building it. And from, from our experience, uh, we have learned that that is not sufficient, uh, that is not sufficient to tell us that that particular developer built that end product and, uh, whatever code that they build is actually coming out in the end product. So we need, we need something to bridge that gap. We need, we need a trustworthy mechanism there to bridge that gap. And there are, there are a few other, uh, elements to it. >>Um, all these center depositories are prone to, uh, single point of failures. And, you know, in, we have all experience what happens when one of those goes down and how it stops production and how it, how it stops just software, uh, development, right? And we, what we are working on is how do we build a system where we, we can actually have, uh, liquid software as a reality and just continue to build software, regardless of all these systems of being live all the time, uh, and also have a, an implicit, uh, way of mechanism to trust, uh, what is coming out of those systems? >>You know, we've talked with you guys in the past about the building blocks of software and what flows through the pipelines, all that stuff's part of what is automated these days and, and, and important. And what I gotta ask you because security these days is like, don't trust anything, you know, um, here it's, you're, you're trusting software to be in essence verified. I'm simplifying, obviously. So I gotta ask you what is being done to solve this problem, because states change, you know, you got data, you got software injections, and you got, we got containers and Kubernetes right here, helping all this is on the table now, but what is currently being done to solve the problem? Cause it's really hard. >>Yeah, it is. It is a really hard problem. And currently, right, when we develop software, we have a team, uh, which, which we work with and we trust whatever is coming out of the team. And we have, we have a, um, what do you call certified, uh, pro production mechanism to build that software and actually release it to our customers. And when it is done in house, it is easy because we are, we control all the pieces. Now what happens when, when we are doing this with open source, we don't have that chain. We need that chain, which is independent. We just independent of where the software was, you know, produced versus where it is going to be used. We need a way to have Providence of how it was built, which parts actually went in, uh, making, uh, making the end product. Uh, and, and what are the things that we see are, are, are, uh, continuing, uh, uh, continuing evidences that this software can be used. So if there is a vulnerability that is discovered now, that is discovered, and it is released in some database, and we need to do corrective action to say that this vulnerability associated with this version, and there is no, there's no automated mechanism. So we are working on an automated mechanism where, where you can run a command, which will tell you what has happened with this piece of, uh, software, this version of it, and whether it is production worthy or not. >>It's a great goal. I gotta say, but I'll tell you, I can guarantee there's gonna be a ton of skeptics on this security people. Oh, no, I don't. I doubt it's always a back door. Um, what's the relationship with Docker? How do you guys see this evolving? Obviously it's a super important mission. Um, it's not a trend that's gonna go away. Supply chain software is here to stay. Um, it's not gonna go away. And we saw this in hardware and everyone kind of knows kind of what happens when you see these vulnerabilities. Um, you gotta have trusted software, right? This is gonna be continuing what's the relationship with DockerCon? What are you guys doing with dock and here at DockerCon? >>So we, when we actually started working on this project, uh, both Docker and, uh, J frog had had similar ideas in mind of how, how do we make this, uh, this trust mechanism available to anyone, uh, who wants it, whether they're, whether they're in interacting with dock hub or, or regardless of that, right. And how do we actually make it a mechanism, uh, that just, uh, uh, that just provides this kind of, uh, this kind of trust, uh, without, without the developer having to do something. Uh, so what we worked with, uh, with Docker is actually integrating, um, integrating our solution so that anywhere there, uh, there is, uh, Docker being used currently, uh, people don't have to change those, uh, those behaviors or change those code, uh, those code lines, uh, right. Uh, because changing hand, uh, changing this a single line of code in hundreds of systems, hundreds of CI systems is gonna be really hard. Uh, and we wanted to build a seamless integration between Docker and the solution that we are building, uh, so that, so that you can continue to do Docker pro and dock push and, but get, uh, get all the benefits of the supply chain security solution that we have. >>Okay. So let's step back for a minute and let's discuss about the pro what is the project and where's the commercial J Frogg Docker intersect take that, break that apart, just step out the project for us. What's the intended goals. What is the project? Where is it? How do people get involved and how does that intersect with the commercial interest of JRO and Docker? >>Yeah. Yeah. My favorite topic to talk about. So the, the project is called Peria, uh, Peria is, uh, is an open source project. It is, it is an effort that started with JRO and, and Docker, but by no means limited to just JRO and dock contributing, we already have five companies contributing. Uh, we are actually building a working product, uh, which will demo during, uh, during our, uh, our talk. And there is more to come there's more to come. It is being built iteratively, and, and the solution is basically to provide a decentralized mechanism, uh, similar to similar to how, how you, uh, do things with GI, so that you have, you have the, uh, the packages that you are using available at your nearest peer. Uh, there is also going to be a multi load build verification mechanism, uh, and all of the information about the packages that you're going to use will be available on a Providence log. >>So you can always query that and find out what is the latest state of affairs, what ES were discovered and make, make quick decisions. And you don't have to react after the fact after it has been in the news for a while. Uh, so you can react to your customer's needs, um, uh, as quick as they happen. And we feel that the, our emphasis on open source is key here because, uh, given our experience, you know, 80 to 90% of software that is packaged, contains open source, and there is no way currently, which we, uh, or no engineering mechanisms currently that give us that, uh, that confidence that we, whatever we are building and whatever we are dependencies we are pulling is actually worthwhile putting it into production. >>I mean, you really, it's a great service. I mean, you think about like all that's coming out, open source, open source become very social, too. People are starting projects just to code and get, get in the, in the community and hang out, uh, and just get in the fray and just do stuff. And then you see venture capitals coming in funding those projects, it's a new economic system as well, not just code, so I can see this pipeline beautifully up for scale. How do people get involved with this project? Cause again, my, my questions all gonna be around integration, how frictionless it is. That's gonna be the challenge. You mentioned that, so I can see people getting involved. What's what's how do people join? What do they do? What can they do here at Docker con? >>Yeah. Uh, so we have a website, Percy, I P yr S I a.io, and you'll find all kinds of information there. Uh, we have a GI presence. Uh, we have community meetings that are open to public. We are all, we are all doing this under the, uh, under the umbrella limits foundation. We had a boots scrap project within Linux foundation. Uh, so people who have interest in, in all these areas can come in, just, just attend those meetings, uh, add, uh, you know, add comments or just attend our stand up. So we are running it like a, like a agile from, uh, process. We are doing stand up, we are doing retrospectives and we are, we are doing planning and, and we are, we are iteratively building this. So what you'll see at Dr. Conn is, is just a, a little bit of a teaser of what we have built so far and what you, what you can expect to, uh, see in, in future such events. >>So thanks for coming on the queue. We've got 30 seconds left, put a quick plug in for the swamp up, coming up. >>Yeah. Uh, so we, we will talk a lot more about Peria and our open source efforts and how we would like you all to collaborate. We'll be at swamp up, uh, in San Diego on May 26th, uh, May 24th to 26th. Uh, so hope to see you there, hope to discuss more about Peria and, and see what he will do with, uh, with this project. Thank you. >>All right. Thanks for coming on the back to the main stage. I'm John cube. Thanks for watching. >>Thank >>You.

>>mhm Yes. >>Hello and welcome back to the cubes coverage of dr khan 2021 virtual. I'm john Kerry hosted the Q got a great cube segment here. Simon Maple Field C T Oh it's technique. Great company security shifting left great to have you on Simon. Thanks for thanks for stopping by >>absolute pleasure. Thank you very much for having me. >>So you guys were on last year the big partnership with DR Conn remember that interview vividly because it was really the beginning at the beginning but really come to me the mainstream of shifting left as devops. It's not been it's been around for a while. But as a matter of practice as containers have been going super mainstream. Super ballistic in the developer community then you're seeing what's happening. It's containers everywhere. Security Now dev sec apps is the standard. So devops great infrastructure as code. We all know that but now it's def sec ops is standard. This is the real deal. Give us the update on what's going on with sneak. >>Absolutely, yeah. And you know, we're still tireless in our approach of trying to get make sure developers don't just have the visibility of security but are very much empowered in terms of actually fixing issues and secure development is what we're really striving for. So yeah, the update, we're still very, very deep into a partnership with DACA. We have updates on DR desktop which allows developers to scan the containers on the command line, providing developers that really fast feedback as as early as possible. We also have uh, you know, new updates and support for running Docker scan on Lennox. Um, and yeah, you know, we're still there on the Docker hub and providing that security insights um, to, to users who are going to Docker hub to grab their images. >>Well, for the folks watching maybe for the first time, the sneak Docker partnership, we went in great detail last year was the big reveal why Docker and sneak partnership, what is the evolution of that partnership over the year? They speak highly of you guys as a developer partner. Why Doctor? What's the evolution looked like? >>It's a it's a really great question. And I think, you know, when you look at the combination of DACA and sneak well actually let's take let's take each as an individual. Both companies are very, very developer focused. First of all, right, so our goals and will be strife or what we what we tirelessly spend their time doing is creating features and creating, creating an environment in which a developer you can do what they need to do as easily as possible. And that, you know, everyone says they want to be developer friendly, They want to be developer focused. But very few companies can achieve. And you look at a company like doctor, you're a company like sneak it really, really provides that developer with the developer experience that they need to actually get things done. Um, and it's not just about being in a place that a developer exists. It's not enough to do that. You need to provide a developer with that experience. So what we wanted to do was when we saw doctor and extremely developer friendly environment and a developer friendly company, when we saw the opportunity there to partner with Yoko, we wanted to provide our security developer friendliness and developer experience into an already developed a friendly tool. So what the partnership provides is the ease of, you know, deploying code in a container combined with the ease of testing your code for security issues and fixing security issues in your code and your container and pulling it together in one place. Now, one of the things which we as a as a security company um pride ourselves on is actually not necessarily saying we provide security tools. One of what our favorite way of saying is we're a developer tooling company. So we provide tools that are four developers now in doing that. It's important you go to where the developers are and developers on DACA are obviously in places like the Docker hub or the Docker Cli. And so it's important for us to embed that behavior and that ease of use inside Dhaka for us to have that uh that that flow. So the developer doesn't need to leave the Docker Cli developer that doesn't need to leave Docker hub in order to see that data. If you want to go deeper, then there are probably easier ways to find that data perhaps with sneak or on the sneak site or something like that. But the core is to get that insight to get that visibility and to get that remediation, you can see that directly in in the in the Dhaka environment. And so that's what makes the relationship so so powerful. The fact that you combine everything together and you do it at source >>and doing it at the point of code. >>Writing >>code is one of the big things I've always liked about the value proposition is simple shift left. Um So let's just step back for a second. I got to ask you this question because this I wanted to make sure we get this on the table. What are the main challenges uh and needs to, developers have with container security? What are you seeing as the main top uh A few things that they need to have right now for the challenges uh with container security? >>Yeah, it's a it's a very good question. And I think to answer that, I think we need to um we need to think of it in a couple of ways. First of all, you've just got developers security uh in general, across containers. Um And the that in itself is there are different levels at which developers engage with containers. Um In some organizations, you have security teams that are very stringent in terms of what developers can and can't do in other organizations. It's very much the developer that that chooses their environment, chooses their parent image, et cetera. And so there when a developer has many, many choices in which they need to need to decide on, some of those choices will lead to more issues, more risk. And when we look at a cloud native environment, um uh Let's take let's take a node uh image as an example, the number of different uh images tags you can choose from as a developer. It's you know, there are hundreds, probably thousands. That you can actually you can actually choose. What is the developer gonna do? Well, are they going to just copy paste from another doctor file, for example, most likely. What if there are issues in that docker file? They're just gonna copy paste that across mis configurations that exist. Not because the developer is making the wrong decision, but because the developer very often doesn't necessarily know that they need to add a specific directive in. Uh So it's not necessarily what you add in a conflict file, but it's very often what you admit. So there are a couple of things I would say from a developer point of view that are important when we think about cloud security, the first one is just that knowledge that understanding what they need to do, why they need to do it. Secure development doesn't need to be, doesn't mean they need to be deep in security. It means they need to understand how they can develop securely and what what the best decisions that could come from guard rails, from the security team that they provide the development team to offer. But that's the that's an important error of secure development. The second thing and I think one of the most important things is understanding or not understanding necessarily, but having the information to get an act on those things early. So we know the length of time that developers are uh working on a branch or working on um some some code changes that is reducing more and more and more so that we can push to production very, very quickly. Um What we need to do is make sure that as a developer is making their changes, they can make the right decision at the right time and they have the right information at that time. And a lot of this could be getting information from tools, could be getting information from your team where it could be getting information from your production environments and having that information early is extremely important to make. That decision. May be in isolation with your team in an autonomous way or with advice from the security team. But I would say those are the two things having that information that will allow you to make that action, that positive change. Um uh and and yeah, understanding and having that knowledge about how you can develop security. >>All right. So I have a security thing. So I'm a development team and by the way, this whole team's thing is a huge deal. I think we'll get to that. I want to come back to that in a second but just throw this out there. Got containers, got some security, it's out there and you got kubernetes clusters where containers are coming and going. Sometimes containers could have malware in them. Um and and this is, I've heard this out and about how do how that happens off container or off process? How do you know about it? Is that infected by someone else? I mean is it gonna be protected? How does the development team once it's released into the wild, so to speak. Not to be like that, but you get the idea, it's like, okay, I'm concerned off process this containers flying around. What is it How do you track all >>and you know, there's a there's a few things here that are kind of like potential potential areas that, you know, we can trip up when we think about malware that's running um there are certain things that we need to that we need to consider and what we're really looking at here are kind of, what do we have in place in the runtime that can kind of detect these issues are happening? How do we block that? And how do you provide that information back to the developer? The area that I think is, and that is very, very important in order to in order to be able to identify monitor that those environments and then feed that back. So that that that's the kind of thing that can be that can be fixed. Another aspect is, is the static issues and the static issues whether that's in your os in your OS packages, for example, that could be key binaries that exist in your in your in your docker container out the box as well or of course in your application, these are again, areas that are extremely important to detect and they can be detected very very early. So some things, you know, if it's malware in a package that has been identified as malware then absolutely. That can be that can be tracked very very early. Sometimes these things need to be detected a little bit later as well. But yeah, different tools for different for different environments and wear sneak is really focused. Is this static analysis as early as possible. >>Great, great insight there. Thanks for sharing that certainly. Certainly important. And you know, some companies classes are locked down and all of sudden incomes, you know, some some malware from a container, people worried about that. So I want to bring that up. Uh The other thing I want to ask you is this idea of end to end security um and this is a team formation thing we're seeing where modern teams have essentially visibility of their workload and to end. So this is a huge topic. And then by the way it might integrate their their app might integrate with other processes to that's great for containers as well and observe ability and microservices. So this is the trend. What's in it for the developer? If I work with sneak and docker, what benefits do I get if I want to go down that road of having these teams began to end, but I want the security built in. >>Mhm. Yeah, really, really important. And I think what's what's most important there is if we don't look end to end, there are component views and there are applications. If we don't look into end, we could have our development team fixing things that realistically aren't in production anyway or aren't the key risks that are potentially hurting us in our production environment. So it's important to have that end to end of you so that we have the right insights and can prioritize what we need to identify and look at early. Um, so I think, I think that visibility into end is extremely important. If we think about who, who is re fixing uh certain issues, again, this is gonna depend from dog to walk, but what we're seeing more and more is this becoming a developer lead initiative to not just find or be given that information, but ultimately fixed. They're getting more and more responsible for DR files for for I see for for their application code as well. So one of the areas which we've looked into as well is identifying and actually running in cuba Netease workloads to identify where the most important areas that a developer needs to look at and this is all about prioritization. So, you know, if the developer has just a component view and they have 100 different images, 100 different kubernetes conflicts, you know, et cetera. Where do they prioritize, where do they spend their time? They shouldn't consider everything equal. So this identification of where the workloads are running and what um is causing you the most risk as a business and as an organization, that is the data. That can be directly fed back into your, your your vulnerability data and then you can prioritize based on the kubernetes workloads that are in your production and that can be fed directly into the results in the dashboards. That's neat. Can provide you as well. So that end to end story really provides the context you need in order to not just develop securely, but act and action issues in a proper way. >>That's a great point. Context matters here because making it easy to do the right thing as early as possible, the right time is totally an efficiency productivity gain, you see in that that's clearly what people want. It's a great formula, success, reduce the time it takes to do something, reduced the steps and make it easy. Right, come on, that's a that's a formula. Okay, so I gotta bring that to the next level. When I ask you specifically around automation, this is one the hot topic and def sec ops, automation is part of it. You got scale, you got speed, you've got a I machine learning, you go out of all these new things. Microservices, how do you guys fit into the automation story? >>It's a great question. And you know, one of the recent reports that we that we did based on a survey data this year called the state of a state of cloud, native applications security. We we asked the question how automated our people in their in their deployment pipelines and we found some really strong correlations between value from a security point of view um in terms of in terms of having that automation in it, if I can take you through a couple of them and then I'll address that question about how we can be automated in that. So what we found is a really strong correlation as you would expect with security testing in ci in your source code repositories and all the way through the deployment ci and source code were the two of the most most well tested areas across the pipeline. However the most automated teams were twice as likely to test in I. D. S. And testing your CLS in local development. And now those are areas that are really hard to automate if at all because it's developers running running their cli developers running and testing in their I. D. So the having a full automation and full uh proper testing throughout the sclc actually encourages and and makes developers test more in their development environment. I'm not saying there's causation there but there's definite correlation. A couple of other things that this pushes is um Much much more likely to test daily or continuously being automated as you would expect because it's part of the bills as part of your monitoring. But crucially uh 73% of our respondents were able to fix a critical issue in less than a week as opposed to just over 30% of people that were not automated, so almost double people are More likely to fix within a week. 36% of people who are automated can fix a critical security issue in less than a day as opposed to 8% of people who aren't automated. So really strong data that correlates being automated with being able to react now. If you look at something like Sneak what if our um goals of obviously being developer friendly developer first and being able to integrate where developers are and throughout the pipeline we want to test everywhere and often. Okay, so we start as far left as we can um integrating into, you know, CLS integrating into Docker hub, integrating into into doctors can so at the command line you type in doctors can you get sneak embedded in DHAKA desktop to provide you those results so as early as possible, you get that data then all the way through to to uh get reposed providing that testing and automatically testing and importing results from there as well as as well as other repositories, container repositories, being at a poor from there and test then going into ci being able to run container tests in C I to make sure we're not regressing and to choose what we want to do their whether we break, whether we continue with with raising an issue or something like that, and then continuing beyond that into production. So we can monitor tests and automatically send pull requests, etcetera. As and when new issues or new fixes occur. So it's about integrating at every single stage, but providing some kind of action. So, for example, in our ui we provide the ability to say this is the base level you should be or could be at, it will reduce your number of vulnerabilities by X and as a result you're going to be that much more secure that action ability across the pipeline. >>That's a great, great data dump, that's a masterclass right there on automation. Thanks for sharing that sign. I appreciate it. I gotta ask you the next question that comes to my mind because I think this is kind of the dots connect for the customer is okay. I love this kind of hyper focus on containers and security. You guys are all over it, shift left as far as possible, be there all the time, test, test, test all through the life cycle of the code. Well, the one thing that is popping up as a huge growth areas, obviously hybrid cloud devops across both environments and the edge, whether it's five G industrial or intelligent edge, you're gonna have kubernetes clusters at the edge now. So you've got containers. The relationship to kubernetes and then ultimately cloud native work clothes at, say, the edge, which has data has containers. So there's a lot of stuff going on all over the place. What's your, what's your comment there for customer says, Hey, you know, I got, this is my architecture that's happening to me now. I'm building it out. We're comfortable with kubernetes put in containers everywhere, even on the edge how to sneak fit into that story. >>Yeah, really, really great question. And I think, you know, a lot of what we're doing right now is looking at a developer platform. So we care about, we care about everything that a developer can check in. Okay, so we care about get, we care about the repositories, we care about the artifact. So um, if you look at the expansion of our platform today, we've gone from code that people uh, third party libraries that people test. We added containers. We've also added infrastructure as code. So Cuban eighties conflicts, Terror form scripts and things like that. We're we're able to look at everything that the developer touches from their code with sneak code all the way through to your to your container. And I see, so I think, you know, as we see more and more of this pushing out into the edge, cuba Nitties conflict that that, you know, controls a lot of that. So much of this is now going to be or not going to be, but so much of the environment that we need to look at is in the configurations or the MIS configurations in that in those deployment scripts, um, these are some of the areas which which we care a lot about in terms of trying to identify those vulnerabilities, those miS configurations that exist within within those scripts. So I can see yeah more and more of this and there's a potential shift like that across to the edge. I think it's actually really exciting to be able to see, to be able to see those uh, those pushing across. I don't necessarily see any other, any, you know, different security threats or the threat landscape changing as a result of that. Um there could be differences in terms of configurations, in terms of miS configurations that that that could increase as a result, but, you know, a lot of this and it just needs to be dealt with in the appropriate way through tooling through, through education of of of of how that's done. >>Well, obviously threat vectors are all gonna look devops like there's no perimeter. So they're everywhere right? Looking at I think like a hacker to be being there. Great stuff. Quick question on the future relationship with DR. Obviously you're betting a lot here on that container relationship, a good place to start. A lot of benefits there. They have dependencies, they're going to have implications. People love them, they love to use them, helps old run with the new and helps the new run better. Certainly with kubernetes, everything gets better together. What's the future with the DACA relationship? Take us through how you see it. >>So yeah, I mean it's been an absolute blast the doctor and you know, even from looking at some of the internal internal chats, it's been it's been truly wonderful to see the, the way in which both the doctor and sneak from everything from an engineering point of view from a marketing, from a product team. It's been a pleasure to, it's been a pleasure to see that relationship grow and flourish. And, and I think there's two things, first of all, I think it's great that as companies, we, we both worked very, very well together. I think as as as users um seeing, you know, doctor and and and sneak work so so seamlessly and integrated a couple of things. I would love to see. Um, I think what we're gonna see more and more and this is one of the areas that I think, um you know, looking at the way sneak is going to be viewing security in general. We see a lot of components scanning a lot, a lot of people looking at a components can and seeing vulnerabilities in your components. Can I think what we need to, to to look more upon is consolidating a lot of the a lot of the data which we have in and around different scans. What I would love to see is perhaps, you know, if you're running something through doctors can how can you how can you view that data through through sneak perhaps how can we get that closer integration through the data that we that we see. So I would love to see a lot more of that occur, you know, within that relationship and these are kind of like, you know, we're getting to that at that stage where we see integration, it just various levels. So we have the integration where we have we are embedded but how can we make that better for say a sneak user who also comes to the sneak pages and wants to see that data through sneak. So I would love to see at that level uh more there where as I mentioned, we have we have some some additional support as well. So you can run doctors can from from Lenox as well. So I can see more and more of that support rolling out but but yeah, in terms of the future, that's where I would love to see us uh to grow more >>and I'll see in the landscape side on the industry side, um, security is going beyond the multiple control planes out there. Kubernetes surveillance service matches, etcetera, continues to be the horizontally scalable cloud world. I mean, and you got you mentioned the edge. So a lot more complexity to rein in and make easier. >>Yeah, I mean there's a lot more complexity, you know, from a security point of view, the technology is the ability to move quickly and react fast in production actually help security a lot because you know, being able to spin a container and make changes and and bring a container down. These things just weren't possible, you know, 10 years ago, 20 years ago. Pre that it's like it was it's insanely hard compared trying to trying to do that compared to just re spinning a container up. However, the issue I see from a security point of view, the concerns I see is more around a culture and an education point of view of we've got all this great tech and it's it's awesome but we need to do it correctly. So making sure that as you mentioned with making the right decision, what we want to make sure is that right decision is also the easy decision and the clear decision. So we just need to make sure that as we as we go down this journey and we're going down it fast and it's not gonna, I don't see it slowing down, we're going fast down that journey. How do we make, how do we prepare ourselves for that? We're already seeing, you know, miss configurations left, right and center in the news, I am roles as three buckets, etcetera. These are they're they're simpler fixes than we than we believe, right? We just need to identify them and and make those changes as needed. So we just need to make sure that that is in place as we go forward. But it's exciting times for sure. >>It's really exciting. And you got the scanning and right at the point of coding automation to help take that basic mis configuration, take that off the table. Not a lot of manual work, but ultimately get to that cloud scale cool stuff. >>Simon, thank you >>for coming on the cube dr khan coverage. Really appreciate your time. Drop some nice commentary there. Really appreciate it. Thank you. >>My pleasure. Thank you very much. >>Simon Maple Field C T. O. A sneak hot startup. Big partner with Docker Security, actually built in deVOPS, is now dead. Say cops. This is dr khan cube 2021 virtual coverage. I'm sean for your host. Thanks for watching. Mm.

>>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 Everyone welcome back to the cubes. Coverage of Coop con Cloud, native con North America 2020. Normally the Cuba's in person. But like the EU event, this is gonna be a remote virtual event. This is the Cube virtual. We are the Cube Virtual. This is a keynote and show review with our analysts and hosts Lisa Martin, GOP Scar and myself. Guys, welcome to the program. Lisa, Great to see you. You great to see you remotely. Thanks for coming on. >>Always great to be part of the Cuban acute virtual keeping us connected. >>So Coop Con Cloud Native cons November and I remember in 2016 the first Coop Con. That's when Hillary Clinton got defeated by Trump. And now this year the election's passed this time and, uh, Biden the winner. So, you know, election more good vibes this year in the community because everyone was kind of sad last time. So if you remember the first Cube con, it was in Seattle during that time, so that was important to kinda reminisce on. That other thing I want to bring up to you guys is the somber news of the passing of Dan Con who was the executive director of C N C F. He passed a few weeks ago on his home. It was illness and great legend. So we're gonna call that out, and there are thoughts and prayers. Go with the families. Condolences to his wife and kids. So what? I'm say, Dan. Godspeed. Funny dance story, Lisa. Yo, piece that I always always pronounce his name wrong on the queue was like, John, it's con, not Cohen. Okay. All right, Dan, Good to see you. Sorry, but a great guy friend to everyone And super great human being. So rest in peace. Okay. Que con, I >>think the big thing. >>This you wanna get your thoughts, you have to start with you, C and C F. What are they up to? Obviously remote. It's been a terrible year with the pandemic and all the disruptions on DCI change your thoughts on where they are now, this year. >>So you know, it's funny, even though it's remote. Even though reaching people, it's become harder. Uh, you know, we all have to deal with this from our you know, our living room, our office at home. But still, the C in C F is doing what it's been doing for a little while now. So instead of focusing on the technology part of RT world, there are focusing on you know, the community side of it. So they're fighting for inclusivity. They're fighting for diversity, for resilience in terms off their community. And they are really working on making the open source community more accessible, both for end user companies. A swell as offer developers thio enter the space, have their contribution and, you know, make sure that everyone can reap the full benefits off these open source products. >>You know, we talked to Priyanka Sharma and Stephen Augustus, and this was a big theme. There's there's been there's been a lot of engagement online, obviously, even though they have a remote platform, some people are thrilled with it. Some aren't. No one's ever happy these days. It's on the Web. It's always difficult, but the community been activated and a lot more diversity. I covered the big story around. You know, Master slave. The terminology now is gonna go main, you know, terminology and how that's gonna be safer. Also for diversity stem women in tech, This >>has been >>a big theme. I'd love to get your thoughts on that, because I think that's been a very positive thing. Uh, Lisa, you and I have been talking about this for years on the Cube around this diversity peace. What's your thoughts as well, like to get both your reactions on where this directions going. >>Yeah. You know, I think there's a number of things that have been catalyzed this year by the challenges that we've been through and the diversity pushed into the spotlight again. The spotlight is different, and it's really causing change for good. I think it's opening people's minds and perspective, as is, I think, this entire time, you know, it's for events like Yukon and all the other events that were normally getting a lot of airline miles for John and you were not getting. We're sitting at home with our in home studios, but at the same time, the engagement is increasing in every event, I imagine that the great Q. Khan and cognitive community that Dan Cohen has built is on Lee getting bigger and stronger, even though folks are physically separated. That's been just been my observation and something I felt from everything show I've covered every interview I've done that diversity is being raised now to a visibility level that we haven't seen in terms of a catalyzing action. >>You your reaction, Thio. >>No, I completely agree. And I want to add to that where you know, just like Lisa said. You know, we used to fly to these events. We were privileged and lucky to to be there to have the opportunity. But because everything is now digital and virtual, it opens the community up to so many other people who, for whatever reason, weren't able to join in person but are able to join virtually indigenously. So I think you know, even though there's a lot of downsides Thio to this pandemic, this is one of the, you know, the small nuggets of off seeing the sea NCF community opening up to a broader audience. >>Yeah, and that's a great point. You know, we aren't getting the airline miles we're getting Certainly the zoom and the cube mileage remote Lisa, because what's interesting you're saying is is that you know, we're getting more action with him coming in, doing some or hosting yourself, um, Eliana Gesu as well, Others. But we can get people more because remember, the people aren't we're not trying, but so aren't other people that were coming the big names, but also the fresh voices, the new names, names? We don't know yet. I think that's what we're seeing with the remote interviews is that it's one click away from being on the Cube now. So cute. Virtual is 24 73 65 we're gonna continue to do that. I think this is gonna change the makeup of the engagement in the conversation because you're gonna have mawr participation that's going to be highly accelerated. But also, these new voices are gonna bring a positive change. It might upset the hierarchy a little bit in the working groups at the top you, But you know they're open. I mean, I talked with Stephen Augustus. He's totally cool with this Chris, and I check is the same way he's like, Hey, bring on more people. This is the >>This is >>the vibe of the of the Lennox foundations always been. >>It's always been that way. And, you know, going back Teoh to the early open source events in Europe that I went to you. I started doing that as a teenager 15 years ago, and the vibe, you know, hasn't necessarily changed. The makeup of the audience certainly has changed right from it, being dominated by white males. It's totally opened up. And, you know, if we see that happening with the C N C F now as well, I think that's for you know, for the better. I think, um, our community, the i t community in the open source community need that resilience. Need all of those different perspectives from all of you know, different kinds of people from different walks of life with different histories. And I think that only makes the community stronger and more viable in the long run. I >>agree it's that >>open source needs. >>Sorry, it's not thought diversity that I think we're seeing even more now again. Just my perspective is just that the light that this challenging time is shining on, exposing things that are really opportunities and it's I think it's imperative to look at it in that way. But that thought diversity just opens up so many more opportunities that folks that are maybe a little bit more tunnel visioned aren't thinking of. But for businesses, thio and people Thio thrive and move forward and learn from this we need to be able Thio, take into consideration other concepts, other perspectives as we learn and grow. >>Yeah, that's a good point. You know, It was giving a a shout out to Dan Conn. And when I heard the news, I put a clip. One of my favorite clips over the interviews was really me kind of congratulating him on the success of C and C. I think it was, like two years ago or maybe last year. I forget, Um, but I >>was a >>critic of it ever initially, and I was publicly on the record on the Cube. Lisa, you remember, uh, with Stew, who's now having a great new career? Red hat Still and I were arguing, and I was saying, Stew, I think this is gonna fail, because if c. N. C F doesn't balance the end user peace with the logos that we're coming because remember, you about four years ago. It was like a NASCAR logo. Farmers like you know, it's like, you know, everything was like sponsored by Google this and then Amazon came in. You look at the sponsor list. It was like It's the who's who and cloud and now cloud native. It was the industry the entire industry was like, stacked up against reinvent. This is before Amazon made their move. I mean, uh, as your maid, they're moving for Google. Cloud kind of got their footing. So is essentially coop con against a W s. And I said, That's gonna fail, and I had to eat my words, and I did. It was rightfully so, But the balance, the balance between end user projects and vendor was very successful. And that's still plays out today. Lisa. This is important now because you said pandemic de ecosystem still needs to thrive, but there's no face to face anymore. >>What's the >>challenge? What's the opportunity there? I wanna put you on the spot. >>Sure. No, I think I think it's both challenging and opportunistic. I tend to look at it more from an opportunistic view. I think that it forced a lot of us, Even people like myself who worked from home a lot before, when I wasn't traveling for my marketing company or the Cube. You can really have very personal interactions. The people on Zoom and I found that it's connecting people in a deeper way than you even would get in the office. That's something that I actually really appreciate, how it has been an opportunity to really kind of expand relationships or toe open new doors that wouldn't be there if we were able to be studying together physically in person. And it's obviously changing. You know, all the vendors that we work with. It's very different to engage an audience when you are on Lee on camera, and it's something that, as we know, is we work with folks who haven't done it before. That's one of the things that I think a lot of the C suite I talked to Mrs is that opportunity Thio. You know, be on a stage and and be able to show your body language and your energy with your customers and your partners and your employees. But I actually do think that there is what we're doing through Zoom and and all these virtual platforms like the Cube virtual is well, we're opening up doors for a more intimate way that I think the conversations are more authentic. You know, people are have, like, three year old Discover occurs and they're running in the room when they're screaming behind that. That's how things are today. We're learning toe work with that, but we're also seeing people in a more human >>way. Containers Mitch, mainstream and shifting, left the role of security this year. What's your >>take? So I mean, if we're talking about security and nothing else, I think we're at a point where you know, the C N C. F has become mainstream. Its most popular products have become mainstream. Um, because if we're talking about security, there's, you know, not a lot left. And I say that with, you know, a little bit of sarcasm. I don't mean to offend anyone, but if I did, uh, I do apologize, but, you know, security. Even though it is super important again, it means that we have, you know, moved on from talking about kubernetes and and container Management, or we've moved on from storage. Um, it means that the technology part of the C N. C. F. Like the hard work has been done for 80%. We're now into the 20% where we're kind of, you know, dotting the I's and and making sure that we cover all of the bases. And so one of the news sandbox sandbox projects that has been accepted, I think, today even eyes certain Manager Thio to manage certificates Uh, you know, at scale, um, in an automated fashion. And I think that's, you know, 11 prime example of how security is becoming the theme and kind of the conversation at Yukon this year where, you know, we're again seeing that maturity come into play with even with sandbox projects now being able to help customers help end users with, you know, certificates which is, you know, in in the the macro picture a very specific, a very niche thing to be able to solve with open source software. But for every company, this is one of those vital, you know, kind of boilerplate security measures so that the, um the customer and all of their infrastructure remains safe. >>I think you what You're kind of really articulate, and there is the evolution of CNC off much to John Surprises. You said you thought in the very beginning that this wasn't gonna take off. It has. Clearly, Dan Cohen's left a great legacy there. But we're seeing the evolution of that. I do know John. Wanna ask because you did a lot of the interviews here. We've been talking for, what, nine months now on the Cube Virtual about the acceleration of transformation, of every business to go from that. Okay, how do we do this work in this in this weird environment? Keep the lights on. How do we actually be successful and actually become a thriving business? As things go forward, what are some of the things that you heard from the guests regarding? Kobe has an accelerator. >>Well, I think I think a couple of things. Good. Good question. I think it ranges. Right. So the new They had some news that they're trying to announce. Obviously, new survey certifications, K a security certification, new new tech radar support, diversity stats. You know, the normal stuff they do in the event, they gotta get the word out. So that was one thing I heard, but on the overall macro trend. You know, we saw the covert impact, and no >>one's >>afraid of it there. I mean, I think, you know, part of the legacy of these tech communities is they've been online. They're they're used to being online. So it's not a new thing. So I don't think that the work environment has been that much of a disruption to the people in the in the core community. Linux Foundation, for instance, had a great shot with Chris and a sticker on this. He's the CTO. He's been the CEO, brought a senior roles. Um, in fact, they're they're creating a template around C N C f. And then they're announced The Finn Finn Ops Foundation. Uh, Jr store meant, um, is an executive director. That's part of the new foundation. It's a practitioner community. So I think, um, teasing out the conversation is you're gonna see a template model of the C N. C f. Where you're going to see how groups work together. I think what cove? It has definitely shown in some of the things that you guys were saying around how people are gonna be more engaged, more diversity, more access. I >>think you're >>gonna start to see new social constructs emerge around distinct user groups. And I think this Finn ops Foundation is a tell sign around how groups of people going to start together, whether they're cube host coming together on Cube fans and cube alumni. I mean, let me think about the alumni that have been on the Cube. Lisa, you know Tim Hopkins, Sarah Novotny. Chelsie Hightower. Um, Dan Burns, Craig MK Lucky. I mean, we've had everybody on that's now Captain of the industry. So, um, way had capital one we've had, uh, you know, lift on. I mean, it's becoming a really tight knit. Everyone knows each other, and I think now they realize that they have a lot of, uh, power to infect change. And so when you're trying to affect change, um, that's a good thing, and people are pumped about. So I think the big focus was, um, CNC have a successful again. It's there's there's a somber note around Dan cons passing, but I think he had already moved on to a new position. So he was already passed the baton to management, But he did leave a mark, but I think there's Priyanka Sharma. She's doing a great job. People are upbeat and I think the theme is kubernetes. It happened. It's went next level, then it's going next level again and I think that's kind of what people really aren't saying is kind of the public secret, which is okay, this thing's going mainstream. Now you're gonna start to see it in, in, In commercial deployments. You're gonna start to see it scale into organizations. And that's not the cool kids or the Emerging Dev ops crowd. That's I t. So you know you know it's gonna happen is like, Hey, you know, I'm a nice guy, our developer. What is this? It has toe work. Well, that's the big I think I think people weren't talking about That's the most important story. >>I think another element to that John is the cultural shift. You know, we were talking when we talk about Dev ops who was think about speed and I talked to some folks who said, You know, it's it has to be the I T. Cultures on the business cultures coming together in a meaningful way to collaborate in a very new way. Thankfully, we have the technology to enable us to collaborate. But I think that's been another underlying thing that I've heard a lot through recent times. Is that that facilitator of of cultural change, which is always hard to dio? And there's a bit of a catalyst here for organizations to not just keep the lights on. But to be successful, going forward and and and find new ways of delighting their customers, >>we'll get the final word. I just want to say my big take away to the show is and we'll go down the line. I'll start Lisa in Europe, you could go is the usage of cloud and multi cloud is here. Everyone sees that. I think there's a financial aspect going on with security. You're gonna be tied in. I think you see new sets of services coming built on the foundation of the C N C F. But cloud and multi cloud is here. Multi cloud meeting edges. Well, that is definitely on everyone's radar. That was a big theme throughout the interview, so we'll see more of that. Lisa, your takeaways. >>Yeah, I would agree with that. And I think one of the biggest things that I hear consistently is the opportunities that have been uncovered, the the collaboration becoming tighter and folks having the opportunity to engage more with events like Coop Con and C and C F. Because of this virtual shift, I think there's only ah lot of positive things that we're going to stay to come. >>Yep. Yeah, my point of view is I mean, open source is validated completely right? It's a viable model to build around software. On the one hand, on the other hand, the C and C s role in making that open source community broadly accessible and inclusive is, I think, the biggest win Thio look back at at the last year. >>Well, I'm super excited for moving on to the next event. It's been great pleasure. Lisa. You you guys are great co host Virtual Cube. Thanks for participating. And we'll see you next time. Thank you. Okay, that's the cubes. Coverage of Coop con 2020 cloud Native con Virtual This the cube Virtual. We are the cube. Virtual. Thanks for watching

>>from around the globe. It's the Cube with digital coverage of CONMEBOL. Future ready 2020. Brought to you by combo. >>Hi and welcome back. I'm Stew Minuteman, and we're at the Cube's coverage of Con Volt Future Ready. You've got the power panel to really dig in on the product announcements that happened at the event today. Joining me? We have three guests. First of all, we have Brenda Rajagopalan. He's the vice president of products. Sitting next to him is Don Foster, vice president of Storage Solutions. And in the far piece of the panel Mersereau, vice president of Global Channels and Alliances. All three of them with Conn Volt. Gentlemen, thanks all three of you for joining us. Exactly. All right, so first of all, great job on the launch. You know, these days with a virtual event doing, you know, the announcements, the engagement with the press and analyst, you know, having demos, customer discussions. It's a challenge to put all those together. And it has been, you know, engaging in interesting watch today. So we're going to start with you. You've been quite busy today explaining all the pieces, so just at a very high level if you put this really looks like the culmination of the update with Conn Volt portfolio new team new products compared to kind of a year, year and 1/2 ago. So just if you could start us off with kind of the high points, >>thank you still, yeah, absolutely exciting day for us today. You did comrade multiple reasons for that excitement and go through that we announced an exciting new portfolio today knows to not the culmination. It's a continuation off our journey, a bunch of new products that we launched today Hyper scaler X as a new integrated data protection appliance. We've also announced new offerings in data protection, backup and recovery, disaster recovery and complete data protection and lots of exciting updates for Hedwig and a couple of weeks like we introduced updates for metallic. So, yes, it's been a really exciting pain. Also, today happens to be the data, and we got to know that we are the leader in Gartner Magic Quadrant for the ninth consecutive. I am so a lot of goodness today for us. >>Excellent. Lots of areas that we definitely want to dig deep in to the pieces done. You know, we just heard a little bit about Hedvig was an acquisition a year ago that everybody's kind of looking at and saying Okay, you know, will this make them compete against some of their traditional partners? How we get integrated in So, baby, just give us one level deeper on the Hedvig piece on what that means to the portfolio? Yeah, sure, So I >>guess I mean, one of the key things that the random mentioned was the fact that had hyper scale that's is built off the head Day files. So that's a huge milestone for us. As we teased out maybe 10 months ago. Remember, Tomball, Go on the Cube and talking about, you know, kind of what our vision and strategy was of unifying data and storage management. Those hyper hyper scale X applying is a definite milestone improving out that direction. But beyond just the hyper scale ECs, we've also been driving on some of the more primary or modern workloads such as containers and the really interesting stuff we've come out with your recently is the kubernetes native integration that ties in all of the advanced component of the head to distribute storage architecture on the platform itself across multi cloud and on premise environments, making it really easy and policy driven. Um, for Dev, ops users and infrastructure users, the tie ins applications from a group, Friction >>Great and Mercer. There's some updates to the partner program and help us understand how all of these product updates they're gonna affect the kind of the partnerships and alliances beasts that you want. >>Absolutely. So in the time since our last meeting that go in the fall, which is actually right after I had just doing combo, we spent a good portion of the following six months really talking with partners, understanding the understand the impact of the partner program that we introduced last summer, looking at the data and really looking at barriers to evolve the program, which fell around three difference specific. Once you bet one was simplicity of the simplicity of the program, simplicity of understanding, rewards, levers and so forth. The second was paying for value was really helping, helping our partners to be profitable around things like deal registration on other benefits and then third was around co investment. So making sure that we get the right members in place to support our partners and investing in practices. Another training, another enablement around combo and we launched in over these things last week is a part of an evolution of that program. Today is a great follow on because in addition to all of the program evolutions that we we launched last week now we have an opportunity with our partners to have many more opportunities or kind of a thin into the wedge to open up new discussions with our customers now around all of these different use cases and capabilities. So back to that simplification angle, really driving more and more opportunities for those partners toe specific conversations around use cases. >>Okay, for this next question, I think it makes sense for you to start. Maybe maybe Don, you can get some commentary in two. But when he's firstly the announcements, there are some new products in the piece that you discuss but trying to understand, you know, when you position it, you know, do you call the portfolio? Is it a platform? You know, if I'm an existing Conn Volt customer, you know, how do I approach this? If I use something like metallic, how does that interplay with some of the new pieces that were discussed today. >>Sure, I can take the business. I'm sure Don and mostly will have more data to it. The simplest way to think about it is as a port for you. But contrary to how you would think about portfolio as independent products, what we have is a set off data management services granular. We're very aligned to the use case, which can all inter operate with each other. So maybe launched backup and recovery and disaster recovery. These can be handled separately, purchased separately and deployed standalone or for customers who want a combination of those capabilities. We also have a complete data protection are fine storage optimization, data governance E discovery in complaints are data management services that build on top off any of these capabilities now a very differentiating factor in our platform owners. All the services that you're talking about are delivered off the same software to make it simpler to manage to the same year. So it's very easy to start with one service and then just turn on the license and go to other services so I can understand the confusion is coming from but it's all the same. The customer simplicity and flexibility in mind, and it's all delivered off the same platform. So it is a portfolio built on a single Don. Would you like to add more to it? >>Yeah, I think the interesting thing due to add on top of that is where we're going with Hedvig Infrastructure, the head of distributed storage platform, uh, to to run this point, how everything is integrated and feed and work off of one another. That's the same idea that we have. We talked about unifying data and storage manager. So the intricate storage architecture components the way data might be maneuvered, whether it's for kubernetes for virtual machines, database environments, secondary storage, you name it, um, we are. We're quickly working to continue driving that level of of unification and integration between the portfolio and heads storage, distribute storage platforms and also deliver. So what you're seeing today going back to, I think wrong his first point. It's definitely not the culmination. It's just another step in the direction as we continue to innovate and integrate this >>product, and I think for our partners what this really does, it allows them to sell around customer use cases because it'll ask now if I have a d. Our use case. I can go after just PR. If I have a backup use case, I can just go after backup, and I don't have to try to sell more than that. Could be on what the customer is looking for in parallel that we can steal these things in line with the customer use case. So the customer has a lot of remote offices. They want to scale Hedvig across those they want to use the art of the cloud. They can scale these things independently, and it really gives us a lot of optionality that we didn't have before when we had a few monolithic products. >>Excellent. Really reminds me more of how I look at products if I was gonna go buy it from some of the public cloud providers living in a hybrid cloud. World, of course, is what your customers are doing. Help us understand a little bit, you know, Mercer talked about metallic and the azure partnership, but for the rest of the products, the portfolio that we're talking about, you know, does this >>kind >>of work seamlessly across my own data center hosting providers Public Cloud, you know, how does this fit into the cloud environment for your customer? >>Yes, it does. And I can start with this one goes to, um it's our strategy is cloud first, right? And you see it in every aspect of our product portfolio. In fact, I don't know if you got to see a keynote today, but Ron from Johns Hopkins University was remarking that comment has the best cloud native architectures. And that's primarily because of the innovation that we drive into the multi cloud reality. We have very deep partnerships with pretty much all the cloud vendors, and we use that for delivering joint innovation, a few things that when you think of it from a hybrid customers perspective, the most important need for them is to continue working on pram while still leveraging the cloud. And we have a lot of optimization is built into that, and then the next step of the journey is of course, making sure that you can recover to the cloud would be it work load. Typically your data quality and there's a lot of automation that we provide to our solutions and finally, Of course, if you're already in the cloud, whether you're running a science parents or cloud native, our software protects across all those use cases, either true sass with metallic auto downloadable software, backup and recovery so we can cover the interest victims of actual presence. You. We do definitely help customers in every stage of their hybrid cloud acceleration journey. >>And if you take a look at the Hedvig protect if you take a look at the head back to, um, the ability to work in a cloud native fast, it is essentially a part of the DNA of that storage of the storage, right? So whether you're running on Prem, whether you're running it about adjacent, set up inside the cloud head, that can work with any compute environment and any storage environment that you went to essentially then feed, we build this distributed storage, and the reason that becomes important. It's pretty much highlighted with our announcement around the kubernetes and container support is that it makes it really easy to start maneuvering data from on Prem to the cloud, um, from cloud to cloud region to region, sort of that high availability that you know as customers make cloud first a reality and their organizations starts to become a critical requirement or ensuring the application of and some of the things that we've done now with kubernetes in making all of our integration for how we deliver storage for the kubernetes and container environments and being that they're completely kubernetes native and that they can support a Google in AWS and Azure. And of course, any on premises community set up just showcases the value that we can provide in giving them that level of data portability. And it basically provides a common foundation layer, or how any sort of the Dev ops teams will be operating in the way that those state full container state workloads. Donna Oh, sorry. Go >>ahead, mark area >>because you mentioned the metallic and azure partnership announcement and I just want to get on that. And one thing that run dimension, which is we are really excited about the announcement of partnership with Microsoft and all the different news cases that opens up that are SAS platform with Azure with office 3 65 and all of the great application stack it's on. If you're at the same time, to run this point. We are a multi cloud company. And whether that is other of the hyper scale clouds Mess GC, P. Ali at Oracle and IBM, etcetera, or Oliver, Great service writer burners. We continue to believe in customer choice, and we'll continue to drive unique event innovations across all of those platforms. >>All right, Don, I was wondering if we could just dig in a little bit more on some other kubernetes pieces you were talking about. Let me look at just the maturation of storage in general. You know, how do we had state back into containers in kubernetes environments? Help us see, You know what you're hearing from your customers. And you know how you how you're ready to meet their needs toe not only deliver storage, but as you say, Really? You know, full data protection in that environment? >>Certainly it So I mean, there's been a number of enhancements that happened in the kubernetes environment General over the last two years. One of the big ones was the creation of what the visit environment calls a persistent volume. And what that allows you to do is to really present storage to a a communities application. Do it be typically through what's called a CSR container storage interface that allows for state full data to be written, storage and be handled and reattached applications as you leverage them about that kubernetes. Um, as you can probably imagine that with the addition of the additional state full applications, some of the overall management now of stateless and state collapse become very talent. And that's primarily because many customers have been using some of the more traditional storage solutions to try to map that into these new state. Full scenario. And as you start to think about Dev ops organization, most Dev ops organizations want to work in the environment of their choice. Whether that's Google, whether that's AWS, Microsoft, uh, something that might be on Prem or a mix of different on Prem environments. What you typically find, at least in the kubernetes world, is there's seldom ever one single, very large kubernetes infrastructure cluster that's set to run, Dev asked. The way and production all at once. You usually have this spread out across a fairly global configuration, and so that's where some of these traditional mechanisms from traditional storage vendors really start to fall down because you can apply the same level of automation and controls in every single one of those environments. When you don't control the storage, let's say and that's really where interfacing Hedvig and allowing that sort of extension distribute storage platform brings about all of this automation policy control and really storage execution definition for the state. Full statehood workloads so that now managing the stateless and the state full becomes pretty easy and pretty easy to maintain when it comes to developing another Dev branch or simply trying to do disaster recovery or a J for production, >>any family actively do. That's a very interesting response, and the reality is customers are beginning to experiment with business. Very often they only have a virtual environment, and now they're also trying to expand into continuous. So Hedwig's ability to service primary storage for virtualization as well as containers actually gives their degree of flexibility and freedom for customers to try out containers and to start their contingent. Thank you familiar constructs. Everything is mellow where you just need to great with continuous >>Alright, bring a flexibility is something that I heard when you talk about the portfolio and the pricing as to how you put these pieces together. You actually talked about in the presentation this morning? Aggressive pricing. If you talk about, you know, kind of backup and recovery, help us understand, You know, convo 2020 how you're looking at your customers and you know how you put together your products, that to meet what they need at that. As you said, aggressive pricing? >>Absolutely. And you use this phrase a little bit earlier is to blow like flexibility. That's exactly what we're trying to get to the reason why we are reconstructing our portfolio so that we have these very granular use case aligned data management services to provide the cloud like flexibility. Customers don't have the same data management needs all the time. Great. So they can pick and choose the exact solution that need because there are delivered on the same platform that can enable out the solution investment, you know, And that's the reality. We know that many of our customers are going to start with one and keep adding more and more services, because that's what we see as ongoing conversations that gives us the ability to really praise the entry products very aggressively when compared to competition, especially when we go against single product windows. This uses a lot of slammed where we can start with a really aggressively priced product and enable more capabilities as we move forward to give you an idea, we launched disaster recovery today. I would say that compared to the so the established vendors India, we would probably come in at about 25 to 40% of the Priceline because it depends on the environment and what not. But you're going to see that that's the power of bringing to the table. You start small and then depending on what your needs are, you have the flexibility to run on either. More data management capabilities are more workloads, depending on what your needs will be. I think it's been a drag from a partner perspective, less with muscle. If you want a little bit more than that, >>yes, I mean, that goes back to the idea of being ableto simply scale across government use functionality. For example, things like the fact that our disaster recovery offering the Newman doesn't require backup really allows us to have those Taylor conversations around use cases, applications >>a >>zealous platforms. You think about one of the the big demands that we've had coming in from customers and partners, which is help me have a D R scenario or a VR set up in my environment that doesn't require people to go put their hands on boxes and cables, which was one of those things that a year ago we were having. This conversation would not necessarily have been as important as it is now, but that ability to target those specific, urgent use cases without having to go across on sort of sell things that aren't necessarily associated with the immediate pain points really makes those just makes us ineffective. Offer. >>Yeah, you bring up some changing priorities. I think almost everybody will agree that the number one priority we're hearing from customers is around security. So whether I'm adopting more cloud, I'm looking at different solutions out there. Security has to be front and center. Could we just kind of go down the line and give us the update as to how security fits and all the pieces we've been discussing? >>I guess I'm talking about change, right, so I'll start. The security for us is built into everything that we do the same view you're probably going to get from each of us because security is burden. It's not a board on, and you would see it across a lot of different images. If you take our backup and recovery and disaster recovery, for instance, a lot of ransomware protection capabilities built into the solution. For instance, we have anomaly detection that is built into the platform. If we see any kind of spurious activity happening all of a sudden, we know that that might be a potential and be reported so that the customer can take a quick look at air Gap isolation, encryption by default. So many features building. And when you come to disaster recovery, encryption on the wire, a lot of security aspects we've been to every part of the portfolio don't. >>Consequently, with Hedvig, it's probably no surprise that when that this platform was developed and as we've continued development, security has always been at the core of what we're doing is stored. So what? It's for something as simple as encryption on different volume, ensuring the communication between applications and the storage platform itself, and the way the distributors towards platform indicates those are all incredibly secured. Lock down almost such for our own our own protocols for ensuring that, um, you know, only we're able to talk within our own, our own system. Beyond that, though, I mean it comes down to ensure that data in rest data in transit. It's always it's always secure. It's also encrypted based upon the level of control that using any is there one. And then beyond just the fact of keeping the data secure. You have things like immutable snapshots. You have declared of data sovereignty to ensure that you can put essentially virtual fence barriers for where data can be transported in this highly distributed platform. Ah, and then, from a user perspective, there's always level security for providing all seeking roll on what groups organization and consume storage or leverage. Different resource is the storage platform and then, of course, from a service provider's perspective as well, providing that multi tenanted access s so that users can have access to what they want when they want it. It's all about self service, >>and the idea there is that obviously, we're all familiar with the reports of increased bad actors in the current environment to increased ransomware attacks and so forth. And be a part of that is addressed by what wrong and done said in terms of our core technology. Part of that also, though, is addressed by being able to work across platforms and environments because, you know, as we see the acceleration of state tier one applications or entire data center, evacuations into service provider or cloud environments has happened. You know, this could have taken 5 10 years in a in a normal cycle. But we've seen this happen overnight has cut this. Companies have needed to move those I T environments off science into managed environments and our ability to protect the applications, whether they're on premises, whether they're in the cloud or in the most difficult near where they live. In both cases, in both places at once, is something that it's really important to our customers to be able to ensure that in the end, security posture >>great Well, final thing I have for all three of you is you correctly noted that this is not the end, but along the journey that you're going along with your customers. So you know, with all three of you would like to get a little bit. Give us directionally. What should we be looking at? A convo. Take what was announced today and a little bit of look forward towards future. >>Directionally we should be looking at a place where we're delivering even greater simplicity to our customers. And that's gonna be achieved through multiple aspects. 1st 1 it's more technologies coming together. Integrating. We announced three important integration story. We announced the Microsoft partnership a couple of weeks back. You're gonna see us more longer direction. The second piece is technology innovation. We believe in it. That's what Differentiators has a very different company and we'll continue building it along the dimensions off data awareness, data, automation and agility. And the last one continued obsession with data. What more can we do with it? How can we drive more insights for our customers We're going to see is introducing more capabilities along those dimensions? No. >>And I think Rhonda tying directly into what you're highlighting there. I'm gonna go back to what we teased out 10 months ago at calm Bolt. Go there in Colorado in this very on this very program and talk about how, in the unification of ah ah, data and storage management, that vision, we're going to make more and more reality. I think the, uh, the announcements we've made here today let some of the things that we've done in between the lead up to this point is just proof of our execution. And ah, I can happily and excitedly tell you, we're just getting warmed up. It's going to be, ah, gonna be some fun future ahead. >>And I think studio in the running that out with the partner angle. Obviously, we're going to continue to produce great products and solutions that we're going to make our partners relevant. In those conversations with customers, I think we're also going to continue to invest in alternative business models, services, things like migration services, audit services, other things that build on top of this core technology to provide value for customers and additional opportunities for our partners >>to >>build out their their offerings around combo technologies. >>All right, well, thank you. All three of you for joining us. It was great to be able to dig in, understand those pieces. I know you've got lots of resources online for people to learn more. So thank you so much for joining us. Thank you too. Thank you. Alright, and stay with us. So we've got one more interview left for the Cube's coverage of con vault. Future Ready, students. Mannan. Thanks. As always for watching the Cube. Yeah, Yeah, yeah, yeah, yeah, yeah

>>from around the globe. It's the Cube covering HP Discover virtual experience brought to you by HP. I'm stew minimum. And this is the Cube's coverage of HP Discover virtual experience rather than all getting together in one place. Life box, Vegas. We're getting people around the globe where they are digging into some of the partner discussions here. Happy to welcome to the program. Ricardo de Blasio. He is the chief revenue officer from Con Vault. Ricardo, Thanks so much for joining us. Great to see you. >>We lost you. Great to be here. >>Excellent. So, you know, obviously HP discover Conn Volt and B when you give us the latest on on the partner. >>Absolutely. Well, first of all, I would like to thank you H p e deal team, not only for this invitation, but for the great partnership that we have. Ah, since actually, many, many years. Well, things are going really, really well with HB. Ah, we're very happy with very proud. I mean, if I'm a chief revenue officer also, my idol said it all. You know, if I look at the performance is off our alliances in the last 18 months, um, as being a double digit row and in some quarter even a triple digit growth. So ah, our relationship engagement into the field are growing up on a weekly basis. And the amount of opportunity that we have in our forecasting in our pipeline with HB are growing more and more and more. And, um, I believe we found still a good thing. And young between ah Cos us being the leader off data protection in the market and in conjunction with one of the largest server infrastructure, um, service vendor, service provider like HP. You know, if you think about one of the the the the highest success that we had experience right now is is humble. True green A as a backup as a service, right? So so many angle our chip. It's working and we just feel we are crashing, really, that the people, the iceberg and the best is yet to come so super excited to be here, super excited for what's what's ahead of us. >>Alright, Ricardo, we'll last year and we've had the Cube at Kahn Volt go on for a couple of years. Ah, lot of discussion about the various consumption models, especially out you know, Cloud is fitting into things, whether it be a public cloud and backing up data or are, you know, SAS models. You know, obviously, Alex was the, you know, star of the show at combo go. Last year you mentioned the Green Lake offerings that you're doing with HP to give back up as a service. So bring us inside. You know what you're hearing from your customers? How they're managing these various cloud offering. >>Totally stupid. Well, um I mean, as you know, I mean the the adoption into cloud native APS or moving waters into, ah, cloud models. It is something that has been around for the last 10 years. Obviously, what the current situation is producing is a triggering event to really moving to a light speed, um, transformation and adoption off any type of cloud motors. And we believe that's up backup and data protection provider. Um, we are in the middle of it, experiencing a lot of benefits. I mean, at the end of the day, you know, if you look at our metallic offering, one of our blockbuster is backing up office 3 65 which is a cloud native app after that we got Salesforce or we've got service now and so on. Right before moving to more traditional and point out of management like that or ah, um, like mobile phone. But even if I look at, you know, from from an angle of our partnership with HP, But I see most off the grow and opportunity is being on the Green Lake platform. Um, a lot of the opportunity that we have in our pipe that have been built in the last six months, but I see a lot of potential to do business together. Um, 80% of them is with Green Lake. This always great legs in the middle. >>Excellent. Yeah. What? What do you hearing so much from customers, You know, with your you're the chief revenue officer. So is it Move from cap ex to op X. You know, bring us inside a little bit. The finance side. What you're hearing from customers is how they get ready. Obviously, with the global pandemic even more of a highlight on the cloud models, if I've done things right, I should be able to either, you know, scale up if needed, or if I need to dial things down for a little while. Hopefully, I haven't locked myself in tow some environment. So I love to hear a little bit more color on that piece of it. >>Absolutely. I believe you nail. It's do I mean ah, there's definitely an operational driver behind which he's Can I scale or down my data center without having the possibility to have people on the ground? And so how can I move into a virtual data center? Uh, what? I have computing storage networking that can follow my beach off. Uh, I o according to my business need and this d'etre angle in the current crisis, um, company often are not run, but CFO becomes more important. And, um, there's a huge ah, attention to us and, uh, and everything that can be moved from a perpetual into a credible and therefore cloud has a better fit for that. And, um, and then last but not least, is also, you know, the better integration that a lot of cloud models provide. You were the cloud native. That's right. I mean, um, and you run salesforce on Prem? Not really. Right. So how can you have Ah, a dashboard of different business application and operational applications that are better integrated with the cloud native. That's so the more you can offer your client I eat relates or metallic proponent Delta Cloud Native Services that he's a, um, naturally integrated with the parent cloud native app. So the more you're going to make their life easier. >>Excellent. Ricardo. You know, Con Volt works with many partners. What makes the HP partnership special? >>So I think you know what I said earlier. Definitely. I would say the first thing. These, um a market segmentation, overs and the price. We are experiencing a lot of success with our enterprise clients. You know, if I look at the joint pipeline that we built together, I would say 90% of the lines are global 2000 customers logo. And so that is everyone. Number number two. You know how much work with it collectively in integrating our product line and platform together. So if you look into the humble complete solution and very soon also mentality, but even that big that has been done a lot of effort on that side, they are natively integrated with open a P I so that our clients really will not feel the difference off having two different salad silos solution and and then last but not least, the same strategic goal and view off pushing our cloud based Motorola radical modeler Green Lake for H p e and metallic and a big for mobile. >>Excellent. So you mentioned you know, some of the shifting models to some some of the newer solutions. You know, obviously, you know, integrations partnership a little bit of time, but give us a little bit. What should we be expecting from, you know, calm bolt in the partnership with HP through the rest of 2020. >>Absolutely. Still. Well, um, definitely an acceleration. You know, we put the decision a combo too. Ah, focus on fewer partners are very relevant to us. We're very happy to say that Hve is one of them. And, um, we want to do more from a product integration perspective. So the next one in line with the metallic and how the metallic play and integration will play into green legs and into a lot of HB product. Um, but also, we want to do more with our field engagement. Right? So now we have weekly or monthly orderly. Ah, weekly engagement with our with our two fields organization. Ah, just in order to better serve our clients and often do business with the same channel partners that we have in our ecosystem. >>Excellent. Well, Ricardo, thank you so much for joining us. We really pleasure. >>Thank you. Thank you, Stew. And thank you, HP, for the great partnership opportunity. >>All right, Lots more coverage from the cube. HP discover virtual experience. I'm Stew Minimum. And thank you for watching the Cube. Yeah, yeah, yeah, yeah, yeah.

>>from New York. It's the Q covering Escape. 19. >>Welcome back to the Cube coverage here in New York City for the first inaugural multi cloud conference called Escape, where in New York City was staying in New York, were not escaping from New York were in New York. It's all about multi Cloud, and we're here. Lisa Marie Nancy, developer advocate for Port Works, and Eric Conn, vice president of Products Works. Welcome back. Q. >>Thank you, John. Good to see >>you guys. So, um, whenever the first inaugural of anything, we want to get into it and find out why. Multi clouds certainly been kicked around. People have multiple clouds, but is there really multi clouding going on? So this seems to be the theme here about setting the foundation, architecture and data of the two kind of consistent themes. What shared guys take Eric, What's your take on this multi cloud trend? Yeah, >>I think it's something we've all been actively watching for a couple years, and suddenly it is becoming the thing right? So every we just had ah, customer event back in Europe last week, and every customer there is already running multi cloud. It's always something on their consideration. So there's definitely it's not just a discussion topic. It's now becoming a practical reality. So this event's been perfect because it's both the sense of what are people doing, What are they trying to achieve and also the business sense. So it's definitely something that is not necessarily mainstream, but it's becoming much more how they're thinking about building all their applications. Going forward, >>you know, you have almost two camps in the world. Want to get your thoughts on this guy's Because, like you have cloud native and people that are cloud native, they love it. They born the cloud that get it. Everything's cracking along. The developers air on Micro Service's They're agile train with their own micro service's. Then you got the hybrid I t. Trying to be hybrid developer, right? So you kind of have to markets coming together. So to me, I see multi cloud as kind of a combination of old legacy Data center types of I t with cloud native, not just ops and dead. But how about like trying to build developer teams inside enterprises? This seems to be a big trend, and multi club fits into that because now the reality is that I got azure. I got Amazon. Well, let's take a step back and think about the architecture. What's the foundation? So that to me, is more my opinion. But I want to get your thoughts and reactions that because if it's true, that means some new thinking has to come around around. What's the architecture? What are you trying to do? What's the workloads behavior outcome look like? What's the work flows? So there's a whole nother set of conversations that happened. >>I agree. I think the thing that the fight out there right now that we want to make mainstream is that it's a platform choice, and that's the best way to go forward. So it's still an active debate. But the idea could be I want to do multi club, but I'm gonna lock myself into the Cloud Service is if that's the intent or that's the design architecture pattern. You're really not gonna achieve the goals we all set out to do right, So in some ways we have to design ourselves or have the architecture that will let us achieve the business schools that were really going for and that really means from our perspective or from a port works perspective. There's a platform team. That platform team should run all the applications and do so in a multi cloud first design pattern. And so from that perspective, that's what we're doing from a data plan perspective. And that's what we do with Kubernetes etcetera. So from that idea going forward, what we're seeing is that customers do want to build a platform team, have that as the architecture pattern, and that's what we think is going to be the winning strategy. >>Thank you. Also, when you have the definition of cod you have to incorporate, just like with hybrid I t the legacy applications. And we saw that you throughout the years those crucial applications, as we call them People don't always want them to refer to his legacy. But those are crucial applications, and our customers were definitely thinking about how we're gonna run those and where is the right places it on Prem. We're seeing that a lot too. So I think when we talk about multi cloud, we also talk about what What is in your legacy? What is it? Yeah, I >>like I mean I use legacy. I think it's a great word because I think it really puts nail in the coffin of that old way because remember, if you think about some of the large enterprises, these legacy applications, they've been optimized for hardware and optimize their full stack. They've been build up from the ground up, so they're cool. They're running stuff, but it doesn't always translate to see a new platform designed point. So how do you mean Containers is great fit for their Cooper names. Obviously, you know is the answer. We you guys see that as well, but okay, I can keep that and still get this design point. So I guess what I want to ask you guys, as you guys are digging into some of the customer facing conversations, what are they talking about? The day talking about? The platform? Specifically? Certainly, on the security side, we're seeing everyone running away from buying tools to thinking about platforms. What's the conversation like on the cloud side >>way? Did a talk are multiplied for real talk at Barcelona? Q. Khan put your X three on Sudden. Andrew named it for reals of Izzy, but we really wanted to talk about multiplied in the real world. And when we said show of hands in Barcelona, who's running multi cloud? It was very, very few. And this was in, what, five months? Four months ago? Whereas maybe our customers are just really super advanced because of our 100 plus customers. At four words, we Eric is right. A lot of them are already running multi cloud or if not their plan, in the planning stage right now. So even in the last +56 months, this has become a reality. And we're big fans of communities. I don't know if you know Eric was the first product manager for Pernetti. Hey, he's too shy to say it on Dhe. So yeah, and we think, you know, and criminal justice to be the answer to making all They caught a reality right now. >>Well, I want to get back into G, K, E and Cooper. Very notable historic moment. So congratulations, But to your point about multi cloud, it's interesting because, you know, having multiple clouds means things, right? So, for instance, if I upgrade to office 3 65 and I kill my exchange server, I'm essentially running azure by their definition. If I'm building it, stack on AWS. I'm a native, this customer. Let's just say I want to do some tensorflow or play with big table or spanner on Google. Now >>we have three >>clouds now they're not. So they have work clothes, specific objectives. I am totally no problem. I see that like for the progressive customers, some legacy be to be people who like maybe they put their toe in the cloud. But anyone doing meaningful cloud probably has multiple clouds. But that's workload driven when you get into tying them together and is interesting. And I think that's where I think you guys have a great opportunity in this community because if open source convene the gateway to minimize the lock in and when I say lock and I mean like locking them propriety respect if his value their great use it. But if I want to move my data out of the Amazon, >>you brought up so many good points. So let me go through a few and Lisa jumping. I feel like locking. People don't wanna be locked >>in at the infrastructure level. So, like you said, if >>there's value at the higher levels of Stack, and it helps me do my business faster. That's an okay thing to exchange, but it is just locked in and it's not doing anything. They're that's not equal exchange, right, So there's definitely a move from infrastructure up the platform. So locking in >>infrastructure is what people are trying to move away from. >>From what we see from the perspective of legacy, there is a lot of things happening in industry that's pretty exciting of how legacy will also start to running containers. And I'm sure you've seen that. But containers being the basis you could run a BM as well. And so that will mean a lot for in terms of how V EMS can start >>to be matched by orchestrators like kubernetes. So that is another movement for legacy, and I wanted to acknowledge that point >>now, in terms of the patterns, there are definitely applications, like a hybrid pattern where connect the car has to upload all its data once it docks into its location and move it to the data center. So there are patterns where the workflow does move the ups are the application data between on Prem into a public cloud, for instance, and then coming back from that your trip with Lisa. There is also examples where regulations require companies to enterprise is to be able to move to another cloud in a reasonable time frame. So there's definitely a notion of Multi Cloud is both an architectural design pattern. But it's also a sourcing strategy, and that sourcing strategy is more regulation type o. R. In terms of not being locked in. And that's where I'm saying it's all those things. I'd >>love to get your thoughts on this because I like where you're going with this because it kind of takes it to a level of okay, standardization, kubernetes nights, containers, everyone knows what that is. But then you start talking about a P I gateways, for instance, right? So if I'm a car and I have five different gateways on my device, I ot devices or I have multiple vendors dealing with control playing data that could be problematic. I gotta do something like that. So I'm starting. Envision them? I just made that news case up, but my point is is that you need some standards. So on the a p I side was seeing some trends there. One saying, Okay, here's my stuff. I'll just pass parameters with FBI State and stateless are two dynamics. What do you make of that? What, What? What has to happen next to get to that next level of happiness and goodness? Because Bernays, who's got it, got it there, >>right? I feel that next level. I feel like in Lisa, Please jump. And I feel like from automation perspective, Kubernetes has done that from a P I gateway. And what has to happen next. There's still a lot of easy use that isn't solved right. There's probably tons of opportunities out there to build a much better user experience, both from the operations point of view and from what I'm trying to do is an intense because what people aren't gonna automate right now is the intent. They automate a lot of the infrastructure manual tasks, and that's goodness. But from how I docked my application, how the application did it gets moved. We're still at the point of making policy driven, easy to use, and I think there's a lot of opportunities for everyone to get better there. That's like low priority loving fruitcake manual stuff >>and communities was really good at the local food. That's a really use case that you brought up. Really. People were looking at the data now and when you're talking about persistent mean kun is his great for stateless, but for state full really crucial data. So that's where we really come in. And a number of other companies in the cloud native storage ecosystem come in and have really fought through this problem and that data management problem. That's where this platform that Aaron was talking to that >>state problem. Talk about your company. I want to go back to to, um, Google Days. Um, many war stories around kubernetes will have the same fate as map reduce. Yeah, the debates internally at Google. What do we do with it? You guys made the good call. Congratulations on doing that. What was it like to be early on? Because you already had large scale. You were already had. Borg already had all these things in place. Um, it wasn't like there was what was, >>Well, a few things l say one is It was intense, right? It was intense in the sense that amazing amount of intelligence amazing amount of intent, and right back then a lot of things were still undecided, right? We're still looking at how containers or package we're still looking at how infrastructure kit run and a lot of service is were still being rolled out. So what it really meant is howto build something that people want to build, something that people want to run with you and how to build an ecosystem community. A lot of that the community got was done very well, right? You have to give credit to things like the Sig. A lot of things like how people like advocates like Lisa had gone out and made it part of what they're doing. And that's important, right? Every ecosystem needs to have those advocates, and that's what's going well, a cz ah flip side. I think there's a lot of things where way always look back, in which we could have done a few things differently. But that's a different story for different. Today >>I will come back in the studio Palop of that. I gotta ask you now that you're outside. Google was a culture shock. Oh my God! People actually provisioning software provisioning data center culture shock when there's a little >>bit of culture shock. One thing is, and the funny thing is coming full circle in communities now, is that the idea of an application? Right? The idea of what is an application eyes, something that feels very comfortable to a lot of legacy traditional. I wanna use traditional applications, but the moment you're you've spent so much time incriminates and you say, What's the application? It became a very hard thing, and I used to have a lot of academic debates. Where is saying there is no application? It's It's a soup of resources and such. So that was a hard thing. But funny thing is covered, as is now coming out with definitions around application, and Microsoft announced a few things in that area to so there are things that are coming full circle, but that just shows how the movement has changed and how things are becoming in some ways meeting each other halfway. >>Talk about the company, what you guys are doing. Take a moment. Explain in context to multi cloud. We're here. Port works. What's the platform? It's a product. What's the value proposition? What's the state of the company. >>So the companies? Uh well, well, it's grown from early days when Lisa and I joined where we're probably a handful now. We're in four or five cities. Geography ease over 100 people over 150 customers and there. It's been a lot of enterprises that are saying, like, How do I take this pattern of doing containers and micro service is And how do I run it with my mission? Critical business crinkle workloads. And at that point, there is no mission critical business critical workload that isn't stable so suddenly they're trying to say, How do I run These applications and containers and data have different life cycles. So what they're really looking for is a data plane that works with the control planes and how controlled planes are changing the behavior. So a lot of our technology and a lot of our product innovation has been around both the data plane but a storage control plane that integrates with a computer controlled plane. So I know we like to talk about one control plane. There's actually multiple control planes, and you mentioned security, right? If I look at how applications are running way after now securely access for applications, and it's no longer have access to the data. Before I get to use it, you have to now start to do things like J W. T. Or much higher level bearer tokens to say, I know how to access this application for this life cycle for this use case and get that kind of resiliency. So it's really around having that storage. More complexity absolutely need abstraction >>layers, and you got compute. Look, leading work there. But you gotta have >>software to do it from a poor works perspective. Our products entirely software right down loans and runs using kubernetes. And so the point here is we make remarries able to run all the staple workloads out of the box using the same comment control plane, which is communities. So that's the experiences that we really want to make it so that Dev Ops teams can run anywhere close. And that's that's in some ways been part of the mix. Lisa, >>we've been covering Dev up, going back to 2010. Remember when I first was hanging around San Francisco 2008 joint was coming out the woodwork and all that early days and you look at the journey of how infrastructures code We talked about that in 2008 and now we'll get 11 years later. Look at the advancements you've been through this now The tipping point. It's just seems like this wave is big and people are on it. The developers air getting it. It's a modern renaissance of application developers, and the enterprises it's happening in the enterprise is not just like the nerds Tier one, the Alfa Geeks or >>the Cloud native. It's happening in the >>everyone's on board this time, and you and I have been in the trenches in the early stages of many open source projects. And I think with with kubernetes Arab reference of community earlier, I'm super proud to be running the world's largest CNC F for user group. And it's a great community, a diverse community, super smart people. One of my favorite things about working for works is we have some really smart engineers that have figured out what companies want, how to solve problems, and then we'll go creative. It'll open source projects. We created a project called autopilot, really largely because one of our customers, every who's in the G s space and who's running just incredible application. You can google it and see what the work they're doing. It's all there publicly, Onda We built, you know, we built an open source project for them to help them get the most out of kubernetes. We can say so. There's a lot of people in the community system doing that. How can we make communities better halfway make commitments, enterprise grade and not take years to do that? Like some of the other open source projects that we worked on, it took. So it's a super exciting time to be here, >>and open source is growing so fast now. I mean, just think about how these projects being structured. Maur and Maur projects are coming online and user price, but a lot more vendor driven projects to use be mostly and used, but now you have a lot of vendors who are users. So the line is blurring between Bender User in Open source is really fascinating. >>Well, you look at the look of the landscape on the C N. C f. You know the website. I mean, it's what 400 that are already on board. It's really important. >>They don't have enough speaking slasher with >>right. I know, and it's just it. It is users and vendors. Everybody's in this community together. It's one of things that makes it super exciting. And it it's how we know this is This was the right choice for us to base this on communities because that's what everybody, you guys >>are practically neighbors. So we're looking for seeing the studio. Palo Alto Eric, I want to ask you one final question on the product side. Road map. What you guys thinking As Kubernetes goes, the next level state, a lot of micro service is observe abilities becoming a key part of it, Obviously, automation, configuration management things are developing fast. State. What's the What's the road map for you guys? >>For us, it's been always about howto handle the mission critical and make that application run seamlessly. And then now we've done a lot of portability. So disaster recovery has been one of the biggest things for us is that customers are saying, How do I do a hybrid pattern back to your earlier question of running on Prem and in Public Cloud and do a d. R. Pale over into some of the things at least, is pointing out that we're announcing soon is non series autopilot in the idea, automatically managing applications scale from a volume capacity. And then we're actually going to start moving a lot more into some of the what you do with data after the life cycle in terms of backup and retention. So those are the things that everyone's been pushing us and the customers are all asking for. You >>know, I think data they were back in recovery is interesting. I think that's going to change radically. And I think we look at the trend of how yeah, data backup and recovery was built. It was built because of disruption of business, floods, our gains, data center failure. But I think the biggest disruptions ransomware that malware. So security is now a active disruptor. So it's not like it after the hey, if we ever have, ah, fire, we can always roll back. So you're infected and you're just rolling back infected code. That's a ransomware dream. That's what's going on. So I think data protection it needs to be >>redefined. What do you think? Absolutely. I think there's a notion of How do I get last week's data last month? And then oftentimes customers will say, If I have a piece of data volume and I suddenly have to delete it, I still need to have some record of that action for a long time, right? So those are the kinds of things that are happening and his crew bearnaise and everything. It gets changed. Suddenly. The important part is not what was just that one pot it becomes. How do I reconstruct everything? What action is not one thing. It's everywhere. That's right and protected all through the platform. If it was a platform decision, it's not some the cattlemen on the side. You can't be a single lap. It has to be entire solution. And it has to handle things like, Where do you come from? Where is it allowed to go? And you guys have that philosophy. We absolutely, and it's based on the enterprises that are adopting port works and saying, Hey, this is my romance. I'm basing it on Kubernetes. You're my date a partner. We make it happen. >>This speaks to your point of why the enterprise is in. The vendors jumped in this is what people care about Security. How do you solve this last mile problem? Storage. Networking. How do you plug those holes in Kubernetes? Because that is crucial to our >>personal private moment. Victory moment for me personally, was been a big fan of Cuban is absolutely, you know, for years. Then there were created, talked about one. The moments that got me that was really kind of a personal, heartfelt moment was enterprise buyer. And, you know, the whole mindset in the Enterprise has always been You gotta kill the old to bring in the new. And so there's always been that tension of a you know, the shiny new toy from Silicon Valley or whatever. You know, I'm not gonna just trash this and have a migration za paying that. But for I t, they don't want that to do that. They hate doing migrations, but with containers and kubernetes that could actually they don't to end of life to bring in the new project. They can do it on their own timetable or keep it around. So that took a lot of air out of the tension in on the I t. Side because they say great I can deal with the lifecycle management, my app on my own terms and go play with Cloud native and said to me, that's like that was to be like, Okay, there it is. That was validation. That means this Israel because now they can innovate without compromising. >>I think so. And I think some of that has been how the ecosystems embrace it, right. So now it's becoming all the vendors are saying my internal stack is also based on community. So even if you as an application owner or not realizing it, you're gonna take a B M next year and you're gonna run it and it's gonna be back by something like awesome. Lisa >>Marie Nappy Eric on Thank you for coming on Port Works Hot start of multiple cities Kubernetes big developer Project Open Source. Talking about multi cloud here at the inaugural Multi cloud conference in New York City. It's the Cube Courage of escape. 2019. I'm John Period. Thanks for watching

>>from New York. It's the Q covering escape. 19. Hey, welcome back to the Cube coverage here in New York City for the first inaugural multi cloud conference called Escape. We're in New York City. Was staying in New York, were not escapee from New York were in New York. So about Multi Cloud. And we're here. Lisa Marie Nancy, developer advocate for report works, and Eric Conn, vice president of products. Welcome back with you. >>Thank you, John. >>Good to see you guys. So whenever the first inaugural of anything, we want to get into it and find out why. Multiplied certainly been kicked around. People have multiple clouds, but is there really multi clouding going on? So this seems to be the theme here about setting the foundation, architecture and data to kind of consistent themes. What's your guys take? Eric, What's your take on this multi cloud trend? >>Yeah, I think it's something we've all been actively watching for a couple years, and suddenly it is becoming the thing right? So every we just had a customer event back in Europe last week, and every customer there is already running multi cloud. It's always something on their consideration. So there's definitely it's not just a discussion topic. It's now becoming a practical reality. So this event's been perfect because it's both the sense of what are people doing, What are they trying to achieve and also the business sense. So it's definitely something that is not necessarily mainstream, but it's becoming much more how they're thinking about building all their applications Going forward. >>You know, you have almost two camps in the world to get your thoughts on this guy's because like you have a cloud native people that are cloud needed, they love it. They're born in the cloud that get it. Everything's bringing along. The developers are on micro service's They're agile train with their own micro service is when you got the hybrid. I t trying to be hybrid developer, right? So you kind of have to markets coming together. So to me, Essie multi Cloud as a combination of old legacy Data Center types of I t with cloud native not just optioned. It was all about trying to build developer teams inside enterprises. This seems to be a big trend, and multi cloud fits into them because now the reality is that I got azure, I got Amazon. Well, let's take a step back and think about the architecture. What's the foundation? So that to me, is more my opinion. But I want to get your thoughts and reactions that because if it's true, that means some new thinking has to come around around. What's the architecture, What we're trying to do? What's the workloads behavior outcome look like? What's the workflow? So there's a whole nother set of conversations. >>Yeah, that happened. I agree. I think the thing that the fight out there right now that we want to make mainstream is that it's a platform choice, and that's the best way to go forward. So it's still an active debate. But the idea could be I want to do multi club, but I'm gonna lock myself into the Cloud Service is if that's the intent or that's the design architecture pattern. You're really not gonna achieve the goals we all set out to do right, So in some ways we have to design ourselves or have the architecture that will let us achieve the business schools that were really going for and that really means from our perspective or from a port Works perspective. There's a platform team. That platform team should run all the applications and do so in a multi cloud first design pattern. And so from that perspective, that's what we're doing from a data plane perspective. And that's what we do with Kubernetes etcetera. So from that idea going forward, what we're seeing is that customers do want to build a platform team, have that as the architecture pattern, and that's what we think is going to be the winning strategy. >>Thank you. Also, when you have the death definition of cod, you have to incorporate, just like with hybrid a teeny the legacy applications. And we saw that you throughout the years those crucial applications, as we call them. People don't always want them to refer to his legacy. But those are crucial applications, and our customers were definitely thinking about how we're gonna run those and where is the right places it on Prem. We're seeing that a lot, too. So I think when we talk about multi cloud, we also talk about what what is in your legacy? What is your name? I mean, I >>like you use legacy. I think it's a great word because I think it really nail the coffin of that old way because remember, if you think about some of the large enterprises these legacy applications didn't optimized for harden optimize their full stack builds up from the ground up. So they're cool. They're running stuff, but it doesn't translate to see a new platform design point. So how do you continue? This is a great fit for that, cos obviously is the answer. You guys see that? Well, okay, I can keep that and still get this design point. So I guess what I want to ask you guys, as you guys are digging into some of the customer facing conversations, what are they talking about? The day talking about? The platform? Specifically? Certainly on the security side, we're seeing everyone running away from buying tools were thinking about platform. What's the conversation like on the outside >>before your way? Did a talk are multiplied for real talk at Barcelona. Q. Khan put your X three on son. Andrew named it for reals of busy, but we really wanted to talk about multiplied in the real world. And when we said show of hands in Barcelona, who's running multi pod. It was very, very few. And this was in, what, five months? Four months ago? Whereas maybe our customers are just really super advanced because of our 100 plus customers. At four words, we Eric is right. A lot of them are already running multi cloud or if not their plan, in the planning stage right now. So even in the last +56 months, this has become a reality. And we're big fans of your vanities. I don't know if you know, Eric was the first product manager for Pernetti. T o k. He's too shy to say it on dhe. So yeah, and we think, you know, And when it does seem to be the answer to making all they caught a reality right now. >>Well, I want to get back into G k e. And Cooper was very notable historical. So congratulations. But your point about multi cloud is interesting because, you know, having multiple clouds means things, right? So, for instance, if I upgrade to office 3 65 and I killed my exchange server, I'm essentially running azure by their definition. If I'm building a stack I need of us, I'm a Navy best customer. Let's just say I want to do some tensorflow or play with big table. Are spanner on Google now? I have three clouds. No, they're not saying they have worked low specific objectives. I am totally no problem. I see that all the progressive customers, some legacy. I need to be people like maybe they put their tone a file. But anyone doing meaningful cloud probably has multiple clouds, but that's workload driven when you get into tying them together. It's interesting. I think that's where I think you guys have a great opportunity in this community because it open source convene the gateway to minimize the locket. What locket? I mean, like locking the surprise respect if its value, their great use it. But if I want to move my data out of the Amazon, >>you brought up so many good points. So let me go through a few and Lisa jumping. I feel like locking. People don't wanna be locked in at the infrastructure level. So, like you said, if there's value at the higher levels of Stack and it helps me do my business faster, that's an okay thing to exchange. But if it's just locked in and it's not doing anything. They're that's not equal exchange, right? So there's definitely a move from infrastructure up the platform. So locking in infrastructure is what people are trying to move away from. From what we see from the perspective of legacy, there is a lot of things happening in industry that's pretty exciting. How legacy will also start to run in containers, and I'm sure you've seen that. But containers being the basis you could run a BM as well. And so that will mean a lot for in terms of how VM skin start to be matched by orchestrators like kubernetes. So that is another movement for legacy, and I wanted to acknowledge that point now, in terms of the patterns, there are definitely applications, like a hybrid pattern where connect the car has to upload all its data once it docks into its location and move it to the data center. So there are patterns where the workflow does move the ups are the application data between on Prem into a public cloud, for instance, and then coming back from that your trip with Lisa. There is also examples where regulations require companies to enterprise is to be able to move to another cloud in a reasonable time frame. So there's definitely a notion of Multi Cloud is both an architectural design pattern. But it's also a sourcing strategy and that sourcing strategies Maura regulation type o. R in terms of not being locked in. And that's where I'm saying it's all those things. >>You love to get your thoughts on this because I like where you're going with this because it kind of takes it to a level of Okay, standardization kubernetes nights containing one does that. But then you're something about FBI gateways, for instance. Right? So if I'm a car, have five different gig weighs on my device devices or I have multiple vendors dealing with control playing data that could be problematic. I gotta do something. So I started envisioned. I just made that this case up. But my point is, is that you need some standards. So on the A p I side was seeing some trends there once saying, Okay, here's my stuff. I'll just pass Paramus with FBI, you know, state and stateless are two dynamics. What do you make of that? What? What what has to happen next to get to that next level of happiness and goodness because Ruben is has got it, got it there, >>right? I feel like next level. I feel like in Lisa. Please jump. And I feel like from automation perspective, Kubernetes has done that from a P I gateway. And what has to happen next. There's still a lot of easy use that isn't solved right. There's probably tons of opportunities out there to build a much better user experience, both from operations point of view and from what I'm trying to do is an intense because what people aren't gonna automate right now is the intent to automate a lot of the infrastructure manual tasks, and that's goodness. But from how I docked my application, how the application did, it gets moved. We're still at the point of making policy driven, easy to use, and I think there's a lot of opportunities for everyone to get better there. >>That's like Logan is priority looking fruity manual stuff >>and communities was really good at the food. That's a really use case that you brought up really. People were looking at the data now, and when you're talking about persistent mean Cooney's is great for stateless, but for St Paul's really crucial data. So that's where we really come in. And a number of other companies in the cloud native storage ecosystem come in and have really fought through this problem and that data management problem. That's where this platform that Aaron was talking about >>We'll get to that state problem. Talk about your company. I wanna get back Thio, Google Days, um, many war stories around kubernetes. We'll have the same fate as map reduce. You know, the debates internally and Google. What do we do with it? You guys made a good call. Congratulations doing that. What was it like to be early on? Because you already had large scale. You already had. Borg already had all these things in place. Was it like there was >>a few things I'll say One is. It was intense, right? It was intense in the sense that amazing amount of intelligence, amazing amount of intent, and right back then a lot of things were still undecided, right? We're still looking at how containers are package. We're still looking at how infrastructure Kate run and a lot of the service's were still being rolled out. So what it really meant is howto build something that people want to build, something that people want to run with you and how to build an ecosystem community. A lot of that the community got was done very well, right? You have to give credit to things like the Sig. A lot of things like how people like advocates like Lisa had gone out and made it part of what they're doing. And that's important, right? Every ecosystem needs to have those advocates, and that's what's going well, a cz ah flip side. I think there's a lot of things where way always look back, in which we could have done a few things differently. But that's a different story for different >>will. Come back and get in the studio fellow that I gotta ask you now that you're outside. Google was a culture shock. Oh my God. People actually provisioning software. Yeah, I was in a data center. Cultures. There's a little >>bit of culture shock. One thing is, and the funny thing is coming full circle in communities now, is that the idea of an application, right? The idea of what is an application eyes something that feels very comfortable to a lot of legacy traditional. I wanna use traditional applications, but the moment you're you've spent so much time incriminates and you say, What's the application? It became a very hard thing, and I used to have a lot of academic debates wise saying there is no application. It's it's a soup of resources and such. So that was a hard thing. But funny thing is covered, as is now coming out with definitions around application, and Microsoft announced a few things in that area to so there are things that are coming full circle, but that just shows how the movement has changed and how things are becoming in some ways meeting each other halfway. >>Talk about the company. What you guys are doing. Taking moments explaining contacts. Multi Cloud were here. Put worse. What's the platform? It's a product. What's the value proposition? What's the state of the company? >>Yes. So the companies? Uh well, well, it's grown from early days when Lisa and I joined where we're probably a handful now. We're in four or five cities. Geography is over 100 people over 150 customers and there. It's been a lot of enterprises that are saying, like, How do I take this pattern? Doing containers and micro service is, and how do I run it with my mission? Critical business crinkle workloads And at that point, there is no mission critical business critical workload that isn't stable so suddenly they're trying to say, How do I run These applications and containers and data have different life cycles. So what they're really looking for is a data plane that works with the control planes and how controlled planes are changing the behavior. So a lot of our technology and a lot of our product innovation has been around both the data plane but a storage control plane that integrates with a computer controlled plane. So I know we like to talk about one control plane. There's actually multiple control planes, and you mentioned security, right? If I look at how applications are running way, acting now securely access for applications and it's no longer have access to the data. Before I get to use it, you have to now start to do things like J W. T. Or much higher level bear tokens to say I know how to access this application for this life cycle for this use case and get that kind of resiliency. So it's really around having that >>storage. More complexity, absolutely needing abstraction layers and you compute. Luckily, work there. But you gotta have software to do it >>from a poor box perspective. Our products entirely software right down loans and runs using kubernetes. And so the point here is we make remarries able to run all the staple workloads out of the box using the same comment control plane, which is communities. So that's the experiences that we really want to make it so that Dev Ops teams can run anywhere close. And that's that's in some ways been part of the mix. >>Lisa, we've been covering Jeff up. Go back to 2010. Remember when I first I was hanging around? San Francisco? Doesn't eight Joint was coming out the woodwork and all that early days. You look at the journey of how infrastructures code. We'll talk about that in 2008 and now we'll get 11 years later. Look at the advancements you've been through this now the tipping point just seems like this wave is big and people are on developers air getting it. It's a modern renaissance of application developers, and the enterprise it's happening in the enterprise is not just like the energy. You're one Apple geeks or the foundation. It's happening in >>everyone's on board this time, and you and I have been in the trenches in the early stages of many open source projects. And I think with kubernetes Arab reference of community earlier, I'm super proud to be running the world's largest CNC F for user group. And it's a great community, a diverse community, super smart people. One of my favorite things about working poor works is we have some really smart engineers that have figured out what companies want, how to solve problems, and then we'll go credible open source projects. We created a project called autopilot, really largely because one of our customers, every who's in the G s space and who's running just incredible application, you can google it and see what the work they're doing. It's all out there publicly. Onda we built, you know, we've built an open source project for them to help them get the most out of kubernetes we can say so there's a lot of people in the community system doing that. How can we make communities better? Half We make competitive enterprise grade and not take years to do that. Like some of the other open source projects that we worked on, it took. So it's a super exciting time to be here, >>and open source is growing so fast. Now just think about having project being structured. More and more projects are coming online and user profit a lot more. Vendor driven projects, too used mostly and used with. Now you have a lot of support vendors who are users, so the line is blurring between then their user in open source is really fast. >>Will you look at the look of the landscape on the C N. C. F? You know the website. I mean, it's what 400 that are already on board. It's really important. >>They don't have enough speaking slasher with >>right. I know, and it's just it. It is users and vendors. Everybody's in the community together. It's one of things that makes it super exciting, and it's how we know this is This was the right choice for us. Did they communities because that's what? Everybody? >>You guys are practically neighbors. We look for CNN Studio, Palo Alto. I wanna ask you one final question on the product side. Road map. What you guys thinking As Kubernetes goes, the next level state, a lot of micro service is observe. Ability is becoming a key part of it. The automation configuration management things are developing fast. State. What's the road for you guys? For >>us, it's been always about howto handle the mission critical and make that application run seamlessly. And then now we've done a lot of portability. So disaster recovery is one of the biggest things for us is that customers are saying, How do I do a hybrid pattern back to your earlier question of running on Prem and in Public Cloud and do a D. R fail over into a Some of the things, at least, is pointing out. That we're announcing soon is non Terry's autopilot in the idea of automatically managing applications scale from a volume capacity. And then we're actually going to start moving a lot more into some of what you do with data after the life cycle in terms of backup and retention. So those are the things that everyone's been pushing us, and the customers are all asking, >>You know, I think data that recovery is interesting. I think that's going to change radically. And I think we look at the trend of how yeah, data backup recovery was built. It was built because of disruption of business, floods, our games. That's right. It is in their failure. But I think the biggest disruptions ransomware that malware. So security is now a active disruptor, So it's not like it After today. If we hadn't have ah, fire, we can always roll back. So you're infected and you're just rolling back infected code. That's a ransomware dream. That's what's going on. So I think data protection needs to redefine. >>What do you think? Absolutely. I think there's a notion of how do I get last week's data last month and then oftentimes customers will say If I have a piece of data volume and I suddenly have to delete it, I still need to have some record of that action for a long time, right? So those are the kinds of things that are happening and his crew bearnaise and everything, it gets changed. Suddenly, the important part is not what was just that one pot it becomes. How do I reconstruct everything? Action >>is not one thing. It's everywhere That's right, protected all through the platform. It is a platform decision. It's not some cattlemen on the side. >>You can't be a single lap. It has to be entire solution. And it has to handle things like, Where do you come from? Where is it allowed to go? >>You guys have that philosophy? >>We absolutely. And it's based on the enterprises that are adopting port works and saying, Hey, this is my romance. I'm basing it on Kubernetes here, my data partner. How do you make it happen? >>This speaks to your point of why the enterprise is in the vendors jumped in. This is what people care about security. How do you solve this last mile problem? Storage, Networking. How do you plug those holes and kubernetes? Because that is crucial. >>One personal private moment. Victory moment for me personally, Waas been a big fan of Cuban, is actually, you know, for years in there when it was created, talked about one of moments that got me was personal. Heartfelt moment was enterprise buyer on. The whole mindset in the enterprise has always been You gotta kill the old to bring in the new. And so there's always been that tension of a you know, the shame, your toy from Silicon Valley or whatever. You know, I'm not gonna just trash this and have a migration is a pain in the butt fried. You don't want that to do that. They hate doing migrations, but with containers and kubernetes, they actually they don't end of life to bring in the new project they could do on their own or keep it around. So that took a lot of air out of the tension in on the I t. Side. Because it's a great I can deal with the life cycle of my app on my own terms and go play with Cloud native and said to me, I was like, That was to be like, Okay, there it is. That was validation. That means this is real because now they will be without compromising. >>I think so. And I think some of that has been how the ecosystems embraced it, right, So now it's becoming all the vendors are saying My internal stack is also based on company. So even if you as an application owner or not realizing it, you're gonna take a B M next year and you're gonna run it and it's gonna be back by something like >>the submarine and the aircon. Thank you for coming on court. Worse Hot started Multiple cities Kubernetes Big developer Project Open Source Talking about multi cloud here at the inaugural Multi Cloud Conference in New York City Secu Courage of Escape Plan 19 John Corey Thanks for watching.

>>Live from Denver, Colorado. It's the cube covering com vault go 2019 brought to you by Combolt. >>Hey, welcome back to the Q but Lisa Martin with men and men and we are coming to you alive from Conn logo 19 please to welcome to the cube, a gent from Microsoft Azure. We've got Ben Nichol, principal program manager. Ben, welcome. Thank you. Thanks for having me on. Thanks for coming on. So Microsoft combo, what's going on with the partnership? >>They wouldn't have have great storage pond is in data management space. We've been working with Convolt for 20 years now in Microsoft and and they've been working with us on Azure for about as long as I can remember not being on that the Azure business RET seven years now. So just a long time in cloud terms like doggies and it sort of, they'd been doing a huge amount of their around getting customer data into the cloud, reducing costs, getting more resiliency and then also letting them do more with the data. So they were a pretty good partner to have and they make it much easy for their customers to to go and leverage cloud. So Ben, you know, in my career I've had lots of interactions with the Microsoft storage team. Things have changed a little bit when you're now talking about Azure compared to, you know, more. >>It was the interaction with the operating system or the business suite had. So maybe bring us up to date as those people that might not have followed. You know, we're kind of the storage positioning inside of Microsoft is now that when we talk about Azure and your title. Yeah, we, we sort of look and just just briefly, we worked very heavily with our on premises brethren. They actually inside the O S team is inside of the Azure engineering old male, which is kind of funny, but we do a lot of things there. If he started looking at, firstly on that hybrid side, we have things like Azure files. It's a highly resilient as a service SMB NFS file share up to a hundred terabytes but that interacts directly with windows server to give you Azure file sync. So there is sort of synergies there as well. When I'm doing personally my team, we work on scale storage. >>The big thing we have in there is Al is out blood storage technology, which really is the underpinning technology, full Priya tool storage and Azure which is including our SAS offerings which are hosted on Azure too. So disc is on blood storage, our files on blood storage, you look at Xbox live, all these kinds of stuff is a customer to us. So we build that out and we, we are doing work there and that's really, really interesting and how we do it and that's not looking at going we're going to buy some compute, we're going to buy some storage, we're going to build it out, we're going to run windows or hyper V or maybe VMware with windows running on the VMware, whatever else. This is more a story about wigging to provide you storage as a service. You didn't get a minimum of like 11 nines at your ability and and be able to have that scale to petabytes of capacity in one logical namespace and give you multiple gigabytes, double digit gigabytes of throughput to that storage. >>And now we're even moving about to model multiple protocols. So rest API century today we've got Azure stack storage, you pay API, she can go and use, but we give me that consistency of the actual back end storage and the objects and the data available via more than just one protocol. You can go and access that via HDFS API. As we talk about data lakes all the time. For us, our blood storage is a data Lake. We turn on hierarchal namespace and you can go and access that via our other protocols like as I mentioned HDFS as well. So that is a big story about what we want to do. We want to make that data available at crazy scale, have no limits in the end to the capacity or throughput or performance and over any protocol. That's kind of our line in the Hill about what we want to get to. >>And we've been talking to vault team about some of the solutions that they are putting in the cloud. The new offering metallic that came out. They said if my customer has Azure storage or storage from that other cloud provider, you could just go ahead and use that. Maybe how familiar and how much, I know you've been having a run metallic. We were working, we were pretty tightly with the product team over Convolt around this and my team as well around how do we design and how do we make it work the best and we're going to continue working to optimize as they get beyond initial launch to go, wow, we've got data sets we can analyze, we know how to, we wanted out of tune it. Now really we love the solution particularly more because the default, if you don't select the storage type where you want to go, you will run on Azure. >>So really sort of be kudos to the relationship there. They chose us as a first place we'll go to, but they've also done the choice for customers. Say some customers may want to take it to another cloud. That's fine. It's reasonable. I mean, we totally understand it's going to be a multi-cloud world and that's a reality for any large company. Our goal is to make sure we're growing faster than the competitors, not to knock out the competitors all together because that just won't happen. So they've got that ability to go and yet, Hey, we'll use Azure as default because they feel that way, offering the best support and the best solution there. But then if they have that customer, same customer wants to turn around and use a competitor, Val's fine as well. And I see people talking about that today where they may want to mitigate risks and say, I'm going to do, I'm doing all of office three, six, five on a taken office, three, six, five backup. It's cool. Use metallic, it'll take it maybe to a different region in Asia and they're backing up and they still going, well I'm still all in on Microsoft. They may want to take it to another cloud or even take it back to on premises. So that does happen too because just in case of that moment we can get that data back in a different location. Something happens. >>So metallic talking about that is this new venture is right. It's a Combolt venture and saw that the other day and thought that's interesting. So we dug into it a little bit yesterday and it's like a startup operating within a 20 year old company, which is very interesting. Not just from an incumbent customer perspective, but an incumbent partner perspective. How have you seen over the last few years and particularly bad in the last nine months with big leadership and GTM changes for combo? How has the partnership with Microsoft evolved as a result of those changes? >>Um, it's always been interesting. I guess when you start looking at adventure and everything, since things change a little bit, priorities may change just to be fair, but we've had that tight relationship for a long time. At a relationship level and an exec leadership level, nothing's really changed. But in the way they're building this platform, we sit down out of my team, out of the Azure engineering group and we'll sit down and do things like ideations, like here's where we see gaps in the markets, here's what we believe could happen. And look back in July, we had inspire, which is our partner conference in Las Vegas. When we sat down with their OT, our OT in a room, we'll talking about these kinds of things and this is I think about two months after they may have started the initial development metallic from what I understand, but we will talking about exactly what they're doing with metallic offered as a service in Azure is, Hey, how bout we do this? So we think it's really cool. It opens up a new market to Convolt I think too. I mean they're so strong in the enterprise, but they don't do much in smaller businesses because with a full feature product, it also has inherent complexibility complexity around it. So by doing metallic, is it click, click, next done thing. They're really opening, I think, new markets to them and also to us as a partner. >>I was going to ask, you know, kind of click on that because they developed this very quickly. This is something that I think what student were here yesterday, metallic was kind of conceived design built in about six months. So in terms of like acceleration, that's kind of a new area for Combalt. >>Yeah, and I think, I think they're really embracing the fact about um, let's release our code in production for products, which are sort of getting, getting to the, Hey that product is at the viable stage now, not minimum viable, viable, let's release in production, let's find out how customers are using Atlin, let's keep optimizing and doing that constant iteration, taking that dev ops approach to let's get it out there, let's get it launched. And then let's do these small batches of changes based on customer need, based on tele telemetry. We can actually get in. We can't get the telemetry without having customers. So that's how it's going to keep working. So I think this initial product we see today, it's just going to keep evolving and improving as they get more data, as they get more information, more feedback. Which is exactly what we want to see. >>Well, what will come to the cloud air or something you've been living in for a number of years. Ben, I'd love to hear you've been meeting with customers. They've been asking you questions, gives us some of the, you know, some of the things that, what's top of mind for some of the customers? What kinds of things did they come into Microsoft, Dawn, and how's that all fit together? >>There's many different conferences of interrelate, many different conversations and they'll, we will go from talking about, you know, Python machine learning or AI PowerPoint. >>Yeah. >>It's a things like, you know, when are we going to do incremental snapshots from a manage disks? Get into the weeds on very infrastructure century staff. We're seeing range of conversations there. The big thing I think I see, keep seeing people call out and make assumptions of is that they're not going to be relevant because cloud, I don't know cloud yet. I don't know this whole coup cube thing. Containers. I don't, I don't really understand that as well as I think I need to. And an AI, Oh my gosh, what do I even do there? Because everyone's throwing the words and terms around. But to be honest, I think what's still really evident is cloud is still is tiny fraction of enterprise workloads. Let's be honest, it's growing at a huge rate because it is that small fraction. So again, there's plenty of time for people to learn, but they shouldn't go and try and slip. >>It's not like you're going to learn everything in a technology stack, from networking to development to database management to, to running a data set of power and cooling. You learn the things that are applicable to what you're trying to do. And the same thing goes to cloud. Any of these technologies, go and look at what you need to build for your business. Take it to that step and then go and find out the details and levels you want to know. And as someone who's been on Azure for like a cinema seven years, which is crazy long. That was a, that was literally like being in a startup instead of Microsoft when I joined and I wasn't sure if I wanted to join a licensing company. It's been very evident to me. I will not say I'm an Azure expert and I've been seven years in the platform. >>There are too many things throughout my for me to be an expert in everything on and I think people sort of just have to realize that anyone saying that it's bravado, nothing else. The goal is Microsoft as a platform provider. Hopefully you've got the software and the solution to make a lot of this easier for the customer, so hopefully they shouldn't need to become a Kubernetes expert because it's baked into your platform. They shouldn't have to worry about some of these offerings because it's SAS. Most customers are there some things you need to learn between going from, you know, exchange to go into oath bricks, these five. Absolutely. There are some nuances and things like that, but once you get over that initial hurdle, it should be a little easier. I think it's right and I think going back to that, sort of going back to bare principles going, what is the highest level of distraction that's viable for your business or that application or this workload has to always be done with everything. >>If it's like, well, class, not even viable, run it on premises. Don't, don't need to apologize for not running in cloud. If I as is what's happening for you because of security, because of application architecture, run it that way. Don't feel the need and the pressure to have to push it that way. I think too many people get caught up in the shiny stuff up here, which is what you know 1% of people are doing versus the other 99% which is still happening in a lot of the areas we work and have challenges in today. >>That's a great point that you bring up because there is all the buzz words, right? AI, machine learning cloud. You've got to be cloud ready. You've gotta be data-driven to customer, to your point going, I just need to make sure that what we have set up for our business is going to allow our business one to remain relevant, but to also be able to harness the power of the data that they have to extract new opportunities, new insights, and not get caught up with, shoot, should we be using automation? Should we be using AI? Everybody's talking about it. I liked that you brought up and I find it very respectfully, he said, Hey, I'm not an Azure expert. You'd been there seven, seven dog years like you said. And I think that's what customers probably gained confidence in is hearing the folks like you that they look to for that guidance and that leadership saying, no, I don't know everything. To know that giving them the confidence that they're true, they're trusting you with that data and also helping trusting you to help them make the right decisions for their business. >>Yeah. And that that's, we've got to do that. I mean, I, as a tech guy, it's like I've, I've loved seeing the changes. When I joined Microsoft, I, I wasn't lying. I was almost there go inf I really want to join this company. I was going to go join a startup instead. And I got asked to one stage in an interview going, why do you want to join Microsoft? We see you've never applied to that. I never wanted to, a friend told me to come in and it's just been amazing to see those changes and I'm pretty proud on that. Um, so when we talk about, you know, those, the things we're doing, I mean I think there is no shame going, I'm just going to lift and shift machines because cloud is about flexibility. If you're doing it just on cost, probably doing it for the wrong reason, it's about that flexibility to go and do something. >>Then change within months of slowly make steps to make things better and better as you find a need as you find the ability, whatever it may be. And some of the big things that we focus on right now with customers is we've got a product called Azure advisor. It'll go until people want one. You know, you don't build things in a resilient manner. Hey, do you know this is not ha because of this and you can do this. It's like great. Also will tell you about security vulnerabilities that maybe she had a gateway here for security. Maybe you should do this or this is not patched. But the big thing is that it also goes and tells you, Hey, you're overspending. You don't need this much. It provisions, you provision like a Ferrari, you need a, you just need a Prius, go and run a Prius because it's going to do what you need and need to pay a lot less. >>And that's part of that trust. Getting that understanding. And it's counterintuitive that we're now like it's coming out of my team a lot too, which is great. But seeing these guys were dropping contracts and licenses and basically, you know, once every three years I may call the customer, Hey, how bout a renewal now go from that to now being focused on the customer's actual success and focused on their growth in Azure as a platform of our vast services growth like utilization not in sales has been a huge change. It scared some people away but it's brought a lot more people in and and that sort of counterintuitive spin less money thing actually leads in the longterm to people using more. >>Absolutely. That's definitely not the shrink wrap software company of Microsoft that I remember from the 90s yeah, very might be similar to you know, just as volt to 2019 is not the same combo, but many of us know from with 15 >>years and a good mutual friend of ours, sort of Simon and myself before I took this job, he and I sat down, we're having a beer and discussing the merits, all the not evacuate and things like that. Same with. They are changing such, such a great deal with, you know, what they're putting in the cloud, what they're doing with the data, where they're trying to achieve with things like Hedvig for data management across on premises and cloud with microservices applications and stuff going, Hey, this won't work like this anymore. When you now are doing an on premises and we containers, it's pretty good to see. I'm interested to see how they take that even further to their current audience, which is product predominantly, you know, the it pro, the data center admin, storage manager. >>It's funny when you talked about, um, just the choice that customers have and those saying I, we shouldn't be following the trends because they're the trends. We actually interviewed a couple of hours ago, one of Combolt's customers that is all on prime healthcare company and said, he's like, I want to make a secret that says no cloud and proud and it just, what that was, we don't normally hear from them. We always talk about cloud, but for a company to sit down and look at what's best for our business, whether it's, you know, FedRAMP certification challenges or HIPAA or GDPR or other compelling requirements to keep it on prem, it was just refreshing to hear this customer say, >>yeah, I mean it's, it's appropriate for the do what's right for you. I, yeah, it's no shame in any of them. It's, I mean, you don't, you definitely don't get fans by, by shaming people and not doing something right. And I mean, I, I'm personally very happy with the feet, you know, see sort of hype around things like blockchain died down a little bit. So it's a slow database unless you're using for the specific case of that shared ledger, you know, things like that where people don't have to know blockchain. Now I have to know IOT. It's like, yeah. And that hype gets people there, but it also causes a lot of anxiety and it's good to see someone actually not be ashamed of and like, and they grade the ones when they do take a step and use cloud citizen may be in the business already. They're probably going to do it appropriately because have a reason, not just because we think this would be cool. >>Well not and how much inherent and complexity does that bring in if somebody is really feeling pressured to follow those trends and maybe that's when you end up with this hodgepodge of technologies that don't work well together, you're spending way more in as as business it folks are consumers, you know, consumers in their personal lives, they expect things to be accessible, visible, but also cost efficient because they have so much choice. >>Yeah, the choice choice is hard. It's just a, just the conversation is having recently, for example, just we'll take the storage cause of where we are, right? It's like I'm running something on Azure. I'm a, I'm using Souza. I want an office Mount point, which is available to me in Fs. Great. Perfect. what do I use? It's like, well you use any one of these seven options, like what's the right choice? And that's the thing about being a platform company. We give you a lot of choices but it's still up to you or up to harness. It can really help the customers as well to make the most appropriate choice. And I pushed back really hard on terms like best practices and things. I hate it because again, it's making the assumption this is the best thing to do. It's not. It's always about, you know, what are the patterns that have worked for other people, what are the anti-patterns and the appropriate path for me to take. >>And that's actually how we're building our docs now too. So we keep, we keep focusing at our Azure technology and we're bringing out some of the biggest things we've done is how we manage our documentation. It's all open sourced. It's all in markdown on get hub. So you can go and read a document from someone like myself is doing product management going, this is how to use this product and you're actually this bits wrong. This bit needs to be like this, and you can go in yourself, even now, make a change and we can go, Oh yeah, and take that committed in and do all this kind of stuff in that way. So we're constantly taking those documents in that way, in getting real time feedback from customers who are using it, not just ourself and an echo chamber. >>So you get this great insight and visibility that you never had before. Well, Ben, thank you, Georgie stew and me on the Q this afternoon. Excited to hear what's coming up next for Azure. May appreciate your time. Thank you for streaming event. I, Lisa Martin, you're watching the cue from convo. Go 19.

>> Live from Barcelona Spain it's theCUBE covering KubeCon CloudNativeCon Europe 2019. Brought to you by Red Hat. >> Live from Barcelona Spain it's theCUBE covering KubeCon CloudNativeCon Europe 2019. Brought to you by Red Hat. the Cloud Native Computing Foundation and ecosystem partners. >> Hola Barcelona I'm Stu Miniman and my guest host for this week is the one and only Corey Quinn, and you're watching theCUBE the leader in live tech coverage, actually the fourth year we've been doing the KubeCon and CloudNativeCon. This is KubeCon CloudNativeCon Barcelona 2019. We've got two days of wall to wall live coverage. Last year we were in Copenhagen it was outside a little bit windy and we had this lovely silk above us. This time we are inside at the Fira. We've got some lovely Cube branding. The store with all the t-shirts and the little plushies of Fippy and all the animals are right down the row for us, and there is 7,700 people here. So I have been, I did the Austin show in 2017 did the Seattle show last year 2018. We had done the Portland show in 2016, so it's my third time doing one of these, but Corey it is your first time at one of these shows. Wait this isn't an AWF show, so what are you doing here? >> I'm still trying to figure that out myself when people invite me to go somewhere "Do you know anything about insert topic here?" absolutely, smile and bluff your way through. Eventually someone might call you on it, but that's tomorrow's problem not quite today's. >> Yeah I have this general rule of thumb the less I know about something the more I overdress to overcompensate it. Oh so here's the guy in the three piece suit. >> My primary skill is wearing a suit everything else is just edging details. >> Alright, so let's set the stage for our audience here Corey. As I've said we've got the Foundation, we've got a lot of the big members, we've got some of the project people, but I'm really excited we actually have some excellent users here, because it is five years now since Kubernetes came onto the scene of course built off of Borg from Google, and as Dan Conn said in the opening key note, he actually gave a nice historical lesson. The term he used is simultaneous invention and basically those things that, you know, there are times where we argue, who created the light bulb first, or who did this and this? Because there were multiple times out there and he said look there were more than a dozen projects out there. >> Many of them open source or a little bit open as to these things like container orchestration, but it is Kubernetes that is the defacto standard today, and it's why so many people show up for this show, >> and there's such a large ecosystem around it. So you live in the Cloud world you know what's your general view on CloudNative and Kubernetes and this whole kind of space? >> Well going back to something you said a minute or two ago. I think there's something very strong to be said about this being defined by it's users. I've never yet seen a successful paradigm takeoff in the world of technology that was vendor defined. It's at some point you wind up with these companies doing the digital equivalent of here we've crafted you this amazingly precise wrench, and you hand it to a user and the first thing they say is wow it's kind of a crappy hammer, but it's at least good for a first attempt. Tools are going to be used as users want to use them and they define what the patterns look like. >> Yeah so I'll give you the counter point there because we understand if we ask users what they wanted they wanted better buggy whips so we can go faster. To compare and contrast we had done a few years ago was this openstack was user driven and it came out of NASA, and if it was good enough for the rocket scientist, it should be something we that can learn on, and Rackspace had done good and gave it to the open source community, and stepped back and let people use it. First of all openstack it's not dead it's being used in the Telco world it's being used outside of North America quite a bit, but we saw the kind of boom and bust of that. >> We are a long way passed the heyday. >> The vendor ecosystem of openstack was oh it's an alternative to AWS, and maybe some way to get off the VMY licensing, and I've actually said it's funny if you listen to what happens in this ecosystem. Well, giving people the flexibility not to be totally locked in to AWS, and oh it's built on Linux and therefore I might not want to have licensing from certain vendors. Still echos from previously but it is very different. >> Very much so, and I will say the world has changed. >> I was very involved in Eucalyptus which was a bit of a different take on the idea, or the promise of what openstack was going to be What if you had Cloud API's in your own data center in 2012 that seemed like a viable concern. The world we live in today of public cloud first for a lot of shops was by no means assured. >> Yeah, Martin Meikos, Cube alum by the way, fantastic leader still heavily involved in open source. >> Very much so >> One of those things I think he was a little bit ahead of his time on these. So Corey, one of the reasons, why are you here? You are here because I pulled you here, and we do pay you to be here as a host. You're not here for goodwill and that. Your customers are all users and tend to be decent sized users and they say Corey helps people with their Amazon bills no that's the AWS bills not the I have a pile of boxes of smiley faces on there, oh my God what did I do around Christmas time. >> Exactly >> So the discussion at the show is this whole hybrid and multi cloud world when I talk to users they don't use those words. Cloud strategy, sure, my pile of applications, and how I'm updating some of them, and keeping some of them running, and working with that application portfolio and my data. All hugely important but what do you hear from users, and where does the things like cloud and multi cloud fit into their world? >> There are two basic archetypes of user that I tend to deal with. Because I deal with, as you mentioned, with predominately large customers >> you have the born in the cloud types who have more or less a single application. Picture a startup that hits meteoric growth and now is approaching or is in the IPO stage. They have a single application. They're generally all in on one provider, and the idea of going multi cloud is for auxiliary things. If we take a step back, for example, they're saying things like oh PagerDuty is a service that's not run by one of our major public cloud providers. There are a bunch of SaaS applications like that that factor in, but their infrastructure is >> predominately going to be based in one environment. The other large type of customer you'll tend to see is one of those multinational very divisional organizations where they have a long legacy of being very data center first because historically that was kind of the only option. And you'll start to see a bunch of different popup cloud providers inside those environments, but usually they stop at the line of business boundary or very occasionally on a per workload basis. I'm not seeing people say, >> well we're going to build this one application workload, and we want to be able to put that on Oracle cloud, and Azure and GCP and AWS, and this thing that my cousin runs out of the Ozarks. No one wants to do that in the traditional sense because as soon as you go down that path you are constrained to whatever the lowest common denominator across all those things are, and my cousins data center in the Ozarks doesn't have a lot of frills. So you wind up trying to be able to deploy anywhere, but by doing that you are giving up any higher level offering. You are slowing yourself down. >> Yeah, the thing we've always been worried about is back in the day when you talk about multi vendor do we go by the standard, and then go to least common denominator and what has worked it's way through the environment? That's what the customers want. I want today if I'm the user, agility is really one of the things that seem to be top of mind. What IT needs to do is respond to the speed of what the business needs and a CloudNative environment that I look at is it has to be that lever to be able to help me deliver on the next thing, or change the thing, or update my thing to get that working. It was, so disclaimer Red Hat is our headline sponsor here we thank them for our presence, but actually it's a great conversation with open shift customers, and they didn't talk about open shift to open shift to open shift. They talk about their digital transformation. They talk about their data. They talk about the cool new things that they are able to do, and it was that platform happened to be built on Kubernetes. That was the lever to help them do this at the Google show where you were at. That was the same conversation we had whether it is in GCP or whether it was in my own data center. >> You know yes we can do it with containers and everything like that. It was that lever to be able to help me modernize and run new apps and do it faster than I would've done it in the past. So it's that kind of progression that is interesting for me to hear, and just there is not, there is this tendency now to be like oh look everybody is working together and it's wonderful open source ecosystem. It's like well look the world today is definitely coopetition. Yes you need to be up on stage and if a customer says, I need to work with vendors A, B, C, and D. A, B, C, and D, you better work with that or they will go and find an alternative, because there are alternatives out there. >> (Corey) Absolutely, and when a company embarks on a digital transformation and starts moving into public cloud, there are two reasons they are doing that. The first is for cost savings in which case (laughs), let's talk, and the other is for capability storing, and you're not going to realize cost savings for a lot longer than you think you will. In any case you are not going realize capability story if all you view public cloud is being, is another place to run your VAMS or now your containers. >> Yeah, so thank you, Corey your title in your day job You're a Cloud economist. >> I am, two words that no one can define. So no one calls me on it. >> Kubernetes it's magical and free right >> That's what everyone tells me. It feels like right now we are sort of peak heighth as far as Kubernetes goes, and increasingly, whenever you see a technology that has gotten this level of adoption. We saw it with openstack, we've seen it with cloud, we've seen it with a bunch of things. We are starting to see it with Serverless as well. Where, what problem are you trying to solve? I'm not going to listen to the answer, today that answer is Kubernetes, and it seems like everyone's first project is their own resume. Great, there has to be a value proposition, there has to be a story for it, >> and I'm not suggesting that there isn't, but I think that it is being used as sort of an upscale snake oil in some cases or serpen grease as we like to call it in some context. >> Yeah, and that's one of our jobs here is to help extract the sigma from the noise. We've got some good customers. We're going into the environment. One of the things I try to do in the open keynote is find that theme. Couple of years, for a couple of shows >> it's been service mesh is the new hotness. We're talking about Istio, we're talking about Helm, We're talking about all these all these environments that say okay how do I pull together all the pieces of the application, >> and manage that together? Because there's just, you know, moving up the stack, and getting closer to that application. We'll talk about Serverless in one of the other segments later this week I'm sure because you know there's the, okay here Knative can help bridge that gap, but is that what I need? We talk a lot about Kubernetes is how much does the public cloud versus in my data center, and some of the guys they talk to, Serverless is in the public cloud. We'll call it functions of the service if you put it in your own data center, because while yes there are servers everywhere. If you actually manage those racks and everything like that it probably doesn't make sense to call it Serverless. We try not to get into too many semantics arguments here on theCUBE. >> You can generally tend to run arbitrary code anywhere the premise of Serverless to my mind. >> Is more about the event model, and you don't get that on VRAM in the same way that you do in a large public cloud provider, and whether that is the right thing or not, I'm not prepared to say, but it's important for that to be understood as you are going down that path. >> So Corey, any themes that jumped out for you, or things that you want to poke at, at the show, for me, Kubernetes has really kind of crossed that Chasm, and we do have large crowds. You can see the throngs of people behind us, and users that have great stories to tell, and CNCF itself, you know has a lot of projects out there, we're trying to make some sense of all those pieces. There's six now that have graduated, and FluentD is the most recent, but a lot of interesting things from the sandbox, through that kind of incubating phase there, and we're going to dig into some of the pieces there. Some of them build on top of Kubernetes, some of them are just part of this whole Cloud Native Ecosystem, and therefore related but don't necessarily need it, and can play in all these various worlds. >> What about you? >> For me I want to dig a little bit more into the idea of multi cloud. I have been making a bit of a stink for the past year. With the talk called the myth of multi cloud. Where it's not something I generally advise as a best practice, and I'm holding that fairly well, but what I want to do is I want to have conversations with people who are pursuing multi cloud strategies and figure out first, are they in fact pursuing the same thing, so we're defining out terms and talking on the same page, and secondly I want to get a little more context, and insight into why they are doing that, and what that looks like for them. Is it they want to be able to run different workloads in different places? Great that's fair, the same workload run everywhere, on the lowest common denominator. Well lets scratch below the surface a bit, and find out why that is. >> Yeah, and Corey you're spot on, and no surprise because you talk to users on this. From our research side on our team, we really say multi cloud or hybrid cloud. Hybrid cloud means you've got your own data centers, as opposed to multi cloud could be any of them. There's a little bit of a Venn Diagram you could do between that. >> But I am prepared to be wrong as well. I'm a company of two people. I don't have a research department, that's called the spare time I get >> when I can't sleep at night. So I don't have data, I have anecadata. I can talk about individual use cases, but then I'm telling individual company stories that I'm generally not authorized to tell. So it's more a question now of starting to speak to a broader base. >> So just to finish on the thought from out team is everything from I have all of these pieces, and they're really not connected, and I'm just trying to get my arms around through some of the solutions. Like in the AWS world we're looking at the VMware on AWS, and the outpost type of solution. That pullout or what Azure does with Azure stack, and the like, or even company like IBM and Oracle, where they have a stack that can be both >> in the public cloud and the private cloud. Those kind of fully integrated pieces versus the right now I'm just putting applications in certain areas, and then how do I manage data protection, how do I manage security across all these environments. It is a heterogeneous mess that we had, and I spent a lot of my career trying to help us break down those silos, get away from the cylinders of excellence as we called them, and we worked more traditionalist. So how much are we fighting that? I will just tell you that most of the people we're going to have on theCUBE, probably aren't going to want to get into that. They'll be happy to talk about their piece, and how they work with this broad wonderful ecosystem, but we can drill into where Kubernetes fits. We've got the five year anniversary of Kubernetes. We'll be talking to some of the people that helped create this technology, and lots of the various pieces. So with that, Corey, want to give you the final take here, before we talk about the stickers, and some of the rest. >> Oh absolutely, I think it's a fascinating show. I think that they're the right people who are attending. To give valuable perspective that, quite frankly, you're not going to get almost anywhere else. It's just a fascinating blend of people from large companies, small companies, giant vendors, and of course the middleware types, who are trying to effectively stand between in many cases, customers and the raw vendors, for a variety of very good reasons. Partner strategies are important. I'm very curious to see what that becomes, and how that tends to unfold in the next two days. >> Okay, so theCUBE by the way, we're not only a broadcast, but we are part of the community. We understand this network, and that is why Corey and I, you know, we come with stickers. So we've got these lovely sticker and partnership with Women Who Go, that made this logo for us for the Seattle show, and I have a few left, so if you come on by. Corey has his platypus, last week in AWS. So come on by where we are, you get some stickers, and of course, hit us up on Twitter if you have any questions. We're always looking for the community, and the network to help us with the data, and help us pull everything apart. So for Corey Quinn, I'm Stu Miniman, two days of live wall to wall coverage >> will continue very soon, and thank you as always for watching theCUBE. (Fading Electronic Music)

why from nashville tennessee it's the hue covering CommVault go 2018 brought to you by CommVault welcome back we're a few miles down the road from the Jack Daniel's distillery I believe there's some whiskey flowing on the show floor here but we're gonna finish a couple more interviews you're watching the cube I'm Stu minimun this is Keith Townsend happy to welcome back to the program Don Foster is the senior director of solutions marketing with Conn volt Don great to see you hey great thanks for the invite all right so been really good energy at the show these second time at the program it's my first you've got 2000 of the loyal supporters here lots of breakouts you know the pavilions been hopping labs and everything yeah how's the show been for you so far I think it's been incredible I mean first hats off to our partners and customers for coming the buzz is great this year we try to do something maybe a little bit different than in years past and really make it all about the partner ecosystem and about how solutions are more than just combo software it's CommVault together with our partners really get the outcomes what the customers want so we've really integrated everything in as best we possibly can from the content and the theaters and who's doing presentations and even how we do some of the collaboration yeah one of the themes we've been poking at a bit is like okay what's the same and what's different about CommVault you've got obviously you know trusted brand got a lot of existing customers but you know this is not the CommVault of five years ago it was a really broad set of announcements this week yeah I want want you to say what what's been anything surprise you as to kind of what is resonating which things people are getting most excited about I'm sure yesterday when you showed off that bezel and a bunch of people were booing and I you're like really the bezels it's a bunch of geeks here yeah so you know sometimes the flashy lights still you know get us going for sure well like there's always a few things that kind of surprise you and some things that really don't I mean you say what's same what's different you know there's a few terms that we use one of them being powerful simplicity the fact that the power that comma offers for customers from technology perspective you know that's always a mainstay and I think our customers know that our partners absolutely know that and the fact that we can deliver these these solutions for our customers that are really interesting an integrated way is always powerful the simplicity side I don't know even listening to Al not too long ago talking about hey we need to make things more simplified that's really resonating well and it's not just a dashboard or an interface but it's all the automation that's coming behind the scenes that's really starting to change people's idea in my and their minds and I mean we know we know the customers are expecting more me a Bob and I'll talk to battle Don look on that on the keynote stage our partners are expecting more so we need to deliver more as well so I mean those are some really interesting things on the bezel you know it's interesting appliances you never think it's like people don't want to see the equipment I mean that people see servers and their server racks every day but you bring a piece of equipment you stick in our podium and everyone wants to touch it take a selfie with it it's the new appliance look I applaud your team for not you know smoke and you know music and everything and you know here's the unveiling yeah your software company and therefore one of the deployment models might be we make it nice and easy here it is that's great and everything yeah you have little design people do their thing but at the end of the day I don't want to think about it it's most of the stuff sticking in racks in my data center or in the cloud aren't things that I need to worry about right right I mean it appliance is cool but guess what what we're doing with partners like HP and Cisco on building even larger scale and appliance that's just as school if not maybe cooler so I mean it's just it's great kind of showcase that sort of a spectrum of what we can do for our customers so let's talk about the part of the ecosystem for the size so you guys have a really big show floor great announcements with Cisco HPE but 500 partners doing a partner portion of the show what are some of the under-the-radar announcements or even trends that you've seen that customers are excited about yeah sure so actually I just before I came out here I was a TBC with one of our large worldwide partners and one of the things we were talking about they're super excited about the CommVault activate a product and then did the portfolio of applications that were launching and they basically look you guys absolutely nailed it it's kind of the duh moment you know in fact the partner said three years ago we were trying to tell our customers it's it's the data stupid like the data it's that's what's most important deer is cool but it's the data and when they heard this came out it's a whole nother route for them to talk to customers about how they can do things smarter around their data without trying to sell them on necessarily swapping out back and recovery first so let's really understand what your environment looks like and I'm hearing a lot of buzz from our partner community just on how cool what this might be able to do for them and how they're building their business but more importantly the customers are starting to realize hey GDP are just isn't in an EU thing the California just brought their own regulations we're gonna see that probably come to a state near year before you know it so you're gonna have to have a need to act and really maintain and control that data that's really what activate does right going beyond just metadata and giving giving companies a chance to really understand what they have and how they might need to act against it either to meet their compliance requirements or maybe just be smarter with data yeah I love that be smarter with data I think I was saying you know half the customers that they're starting with compliance because that's something we have to do but then there's the opportunities as to what can I do with the data a great example in the keynote it was like oh well I can actually use intelligence too how do I call the data yes you want to save a lot of data but I don't necessarily need to save all the data and that could save me millions of dollars when I do that so yeah I mean the power of data I think we are still in the early days of you know how does CommVault help customers through that that's so I mean it's it's really kind of in the breath of how we crawl information and what we sort of unlock as we do that right so you probably saw we talked about the four dimensional index the 40 index and it's real it's to call it 4d just to try to make it sound super technical but there really are multiple dimensions that we pull together from information and the meta information and where it comes from and whatnot that's all super important from a starting point but once you start working through a review process you've been vent oriented you want to be able to start adding in some tags maybe some entity detail on where and how that fits the organization and then from that you can get deeper into context and content so the content indexing adding and those are tributes being able to really start to align different different sets of data against one another and then the next piece which we do a little bit ourselves and we also work with partners like lucid works like folks like brain space we can start driving context from that information so before we've even talked about moving or storing data we're crawling this information and really giving customers the chance to solve what really is probably a top-three issue for CIOs and that's what they do do I have where is it and is there value in it or is there risk in it or what is is what I don't know about my data bigger than I realize and that's what this helps to unlock and solve for so I think now we're at the beginning of just the beginning of where infrastructure traditional infrastructure companies like con vault are bleeding into data management specifically with 4d indexing where we're providing data outside of the traditional or what's the file size the data was created centered on recover backing up recovering today that actually providing business context and value that application is v's can pick up are you starting to see any movement in is v-space to leveraging the data that's provided by index 40 so we're definitely seeing interest you know so when people think about data they tend to go down this idea of a data Lake and I've talked I'm sure you guys have heard this oh yeah we just throw the data Lake we throw the data lake well what are you throwing in the data Lake now that's a good question we don't know what's in the data Lake anymore and it becomes a data swamp you probably heard those level of stories right well if you don't know what's in there if the integrity of the information then it becomes a major challenge well a lot of the partners the is V is the folks that want to build and work on solutions outside of you know on top of the data they need to know that they have a good source of truth from what they're working from so being able to showcase that we have sort of that virtual data layer the fact that we can crawl data it's not even under our own management and then be able to offer that information back up to another another partner that really starts to you know sparks and some ideas or maybe what could be next so action we're still working through that we still have some things to do around software development kits and make it easier for our partners to build and get that ecosystem going but it's absolutely right down the alley what we were we want to take this all right so Don I hear your data Lake and the data swamp and when we go to the world of multi cloud and edge components really what we get into is the data ocean because there are currents and weather patterns and you know challenges unforeseen the edge of the map you know don't go there things like that it's one of the things you know I've been looking at the last couple of years when I look at companies like comm vault is you know how do you play in the multi cloud world we had a good chat with AWS I stopped by the Microsoft Azure booth here and as things like multi cloud and edge computing fit in you know weirdoes comm bolt fit so on the cloud space I mean it really starts with how you're actually leveraging or moving data or using data in the cloud right and it seems seems minor but if you're not really using the cloud natively if you're not storing data in a way that an s3 blob expects it and you don't have the index behind it if you're just passing it out into containers so you're not really putting that rigor to what that information is then you start to lose a lot of the downstream capability and so taking advantage of all these different services that are inside of the cloud so I mean this is back in 2008 you know 2007 when AWS was starting to really hit cloud computing you started hearing about Microsoft and Microsoft as you're starting up we realized that we wanted to work with these blob based storage devices and from there we realized all right if we're gonna let customers go to the cloud we want to make sure that once their data goes there there's never a reason for them necessarily to have to pull it back let's be able to help them orchestrate the resource utilization and in order for us to do that that data has to be natively accessible really easy right there in that cloud so that's kind of been our vision so as we've supported AWS and there are many services as we supported Microsoft Azure there many services as we're working through in supporting Google cloud platform Oracle cloud we're tying into those back-end services to make sure that that native access is always available and the red thread there is really the way CommVault indexes it very similar what the 40 index is from an activate perspective that red thread is how we can help manage and information across those clouds so it gives customers an ability to know all right it can be in cold storage but I still know where it is what it's meant for and at any point in time I can use it to drive more insight or pull it up into a production compute resource in the cloud all right don't want to give you the final word as we're coming towards the end of our broadcast here CommVault go what what main takeaway you want customers to have when they think about CommVault and think about this event great so I want them to walk away and realize okay the CommVault maybe they thought we were you know five years ago or the cow bought that maybe they're hearing from other people that isn't from us give us a chance and really take a look the things we're doing around AI the way we're working in a delivery of cloud environments the fact that we have that reliability that dependability and all the modern technologies that you're looking for I bet they will be surprised if they just give us a chance they'll see that the power in our software has become something that's really simple and will actually help them get faster to achieve their outcomes than if they looked at buying point solutions and trying to piece it together on their own so that's really well that's really what we're looking for is start to learn and understand at the new con volt is I bet will surprise them all right Don Foster really appreciate you giving us the update we appreciate the opportunity to be able to dig in with your customers in this broad ecosystem for Keith Townsend Tom's to minimas we'll be doing a wrap-up here in a second and thanks so much for watching the Q [Music]

>> Announcer: Live, from Copenhagen, Denmark, it's theCUBE. Covering KubeCon and CloudNativeCon Europe 2018. Brought to you by the Cloud Native Computing Foundation and its Ecosystem Partners. >> Well everyone, welcome back to the live coverage of theCUBE here in Copenhagen, Denmark for KubeCon, Kubernetes Con 2018, part of the CNCF, Cloud Native Compute Foundation, part of the Linux Foundation. I'm John Furrier with Lauren Cooney, the founder of Spark Labs, breaking down day two, wrapping up our coverage of KubeCon and all the success that we've seen with Kubernetes, I thought it would be really appropriate to bring on the cofounder of KubeCon originally, Joseph Jacks, known as JJ in the industry, a good friend of theCUBE and part of the early formation of what is now Cloud Native. We were all riffing on that at the time. welcome back to theCUBE, great to see you. >> Thank you for having me John. >> So, for the story, for the folks out there, you know Cloud Native was really seen by the devops community, and infrastructure code was no secret to the insiders in the timeframes from 2010 through 2015, 16 timeframe, but really it was an open stack summit. A lot of people were kind of like, hey, you know, Google's got Kubernetes, they're going to open it up and this could be a real game changer, container, Docker was flying off the shelves. So we just kind of saw, right, and you were there and we were talking so there was a group of us. You were one of them. And you founded KubeCon, and bolted into the, at that time, the satellite Linux Foundation events, and then you pass it off as a good community citizen to the CNCF, so I wanted to just make sure that people knew that. What a great success. What's your impression? I mean, are you blown away? >> I am definitely blown away. I mean I think the size and scale of the European audience is remarkable. We had something like slightly less than half this in Austin last year. So to see more than that come here in Europe I think shows the global kind of growth curve as well as like, I think, Dan and someone else was asking sort of raise your hand if you've been to Kubecon Austin and very few actually, so there's a lot of new people showing up in Europe. I think it just shows the demand-- >> And Dan's been traveling around. I've seen him in China, some events I've been to. >> Joseph: All over. >> He's really working hard so props to him. We gave him some great props earlier. But he also told us Shanghai is coming online. >> Joseph: Yeah. >> So you got Shanghai, you to Barcelona next year for the European show, and of course Seattle. This is a community celebrating right now because there's a lot of high fives going on right now because there's a lot of cool, we've got some sort of core standard, defacto standard, now let's go to work. What are you working on now? You got a stealth startup? Share a little bit about it. I know you don't want to give the details out, but where is it kind of above the stack? Where you going to be playing? >> Sure, so we're not talking too much in terms of specifics and we're pretty stealthy, but I can tell you what I'm personally very excited about in terms of where Kubernetes is going and kind of where this ecosystem is starting to mature for practitioners, for enterprises. So one of the things that I think Kubernetes is starting to bring to bear is this idea of commoditizing distributed systems for everyday developers, for everyday enterprises. And I think that that is sort of the first time in sort of maybe, maybe the history of software development, software engineering and building applications, we're standardizing on a set of primitives, a set of building blocks for distributed system style programming. You know we had in previous eras things like Erlang and fault tolerant programming and frameworks, but those were sort of like pocketed into different programming communities and different types of stacks. I think Kubernetes is the one sort of horizontal technology that the industry's adopting and it's giving us these amazing properties, so I think some of the things that we're focusing on or excited about involve sort of the programming layer on top of Kubernetes in simplifying the experience of kind of bringing all stateful and enterprise workloads and different types of application paradigms natively into Kubernetes without requiring a developer to really understand and learn the Kubernetes primitives themselves. >> That's next level infrastructure as code. Yeah so as Kubernetes becomes more successful, as Kubernetes succeeds at a larger and larger scale, people simply shouldn't have to know or understand the internals. There's a lot of people, I think Kelsey and a few other people, started to talk about Kubernetes as the Linux kernel of distributed computing or distributed systems, and I think that's a really great way of looking at it. You know, do programmers make file system calls directly when they're building their applications? Do they script directly against the kernel for maybe some very high performance things. But generally speaking when you're writing a service or you're writing a microservice or some business logic, you're writing at a higher level of abstraction and a language that's doing some IO and maybe some reading and writing files, but you're using higher level abstractions. So I think by the same token, the focus today with Kubernetes is people are learning this API. I think over time people are going to be programming against that API at a higher level. And what are you doing here, the show? Obviously you're (mumbles) so you're doing some (mumbles) intelligence. Conversations you've been in, can you share your opinion of what's going on here? Your thoughts on the content program, the architecture, the decisions they've made. >> I think we've just, so lots of questions in there. What am I doing here? I just get so energized and I'm so, I just get reinvigorated kind of being here and talking to people and it's just super cool to see a lot of old faces, people who've been here for a while, and you know, one of the things that excites me, and this is just like proof that the event's gotten so huge. I walk around and I see a lot of familiar faces, but more than 80, 90% of people I've never seen before, and I'm like wow this has like gotten really super huge mainstream. Talking with some customers, getting a good sense of kind of what's going on. I think we've seen two really huge kind of trends come out of the event. One is this idea of multicloud sort of as a focus area, and you've talked with Bassam at Upbound and the sort of multicloud control plane, kind of need and demand out there in the community and the user base. I think what Bassam's doing is extremely exciting. The other, so multicloud is a really big paradigm that most companies are sort of prioritizing. Kubernetes is available now on all the cloud providers, but how do we actually adopt it in a way that is agnostic to any cloud provider service. That's one really big trend. The second big thing that I think we're starting to see, just kind of across a lot of talks is taking the Kubernetes API and extending it and wrapping it around stateful applications and stateful workloads, and being able to sort of program that API. And so we saw the announcement from Red Hat on the operator framework. We've seen projects like Kube Builder and other things that are really about sort of building native custom Kubernetes APIs for your applications. So extensibility, using the Kubernetes API as a building block, and then multicloud. I think those are really two huge trends happening here. >> What is your view on, I'm actually going to put you on test here. So Red Hat made a bet on Kubernetes years ago when it was not obvious to a lot of the other big wales. >> Joseph: From the very beginning really. >> Yeah from the very beginning. And that paid off huge for Red Hat as an example. So the question is, what bets should people be making if you had to lay down some thought leadership on this here, 'cause you obviously are in the middle of it and been part of the beginning. There's some bets to be made. What are the bets that the IBMs and the HPs and the Cisco's and the big players have to make and what are the bets the startups have to make? >> Well yeah, there's two angles to that. I mean, I think the investment startups are making, are different set of investments and motivated differently than the multinational, huge, you know, technology companies that have billions of dollars. I think in the startup category, startups just should really embrace Kubernetes for speeding the way they build reliable and scalable applications. I think really from the very beginning Kubernetes is becoming kind of compelling and reasonable even at a very small scale, like for two or three node environment. It's becoming very easy to run and install and manage. Of course it gives you a lot of really great properties in terms of actually running, building your systems, adopting microservices, and scaling out your application. And that's what's sort of like a direct end user use case, startups, kind of building their business, building their stack on Kubernetes. We see companies building products on top of Kubernetes. You see a lot of them here on the expo floor. That's a different type of vendor startup ecosystem. I think there's lots of opportunities there. For the big multinationals, I think one really interesting thing that hasn't really quite been done yet, is sort of treating Kubernetes as a first-class citizen as opposed to a way to commercialize and enter a new market. I think one of the default ways large technology companies tend to look at something hypergrowth like Kubernetes and TensorFlow and other projects is wrapping around it and commercializing in some way, and I think a deeper more strategic path for large companies could be to really embed Kubernetes in the core kind of crown jewel IP assets that they have. So I'll give you an example, like, for let's just take SAP, I'll just pick on SAP randomly, for no reason. This is one of the largest enterprise software companies in the world. I would encourage the co-CEOs of SAP, for example. >> John: There's only one CEO now. >> Is there one CEO now? Okay. >> John: Snabe left. It's now (drowned out by talking). >> Oh, okay, gotcha. I haven't been keeping up on the SAP... But let's just say, you know, a CEO boardroom level discussion of replatforming the entire enterprise application stack on something like Kubernetes could deliver a ton of really core meaningful benefits to their business. And I don't think like deep super strategic investments like that at that level are being made quite yet. I think at a certain point in time in the future they'll probably start to be made that way. But that's how I would like look at smart investments on the bigger scale. >> We're not seeing scale yet with Kubernetes, just the toe is in the water. >> I think we're starting to see scale, John. I think we are. >> John: What's the scale number in clusters? >> I'll give you the best example, which came up today, and actually really surprised me which I think was a super compelling example. The largest retailer in China, so essentially the Amazon of China, JD.com, is running in production for years now at 20,000 compute nodes with Kubernetes, and their largest cluster is a 5,000 node cluster. And so this is pushing the boundary of the sort of production-- >> And I think that may be the biggest one I've heard. >> Yeah, that's certainly, I mean for a disclosed user that's pretty huge. We're starting to see people actually talk publicly about this which is remarkable. And there are huge deployments out there. >> We saw Tyler Jewell come on from WSO2. He's got a new thing called Ballerina. New programming language, have you seen that? >> Joseph: I have, I have. >> Thoughts on that? What's your thoughts on that? >> You know, I think that, so I won't make any particular specific comments on Ballerina, I'm not extremely informed on it. I did play with a little bit, I don't want to give any of my opinions, but what I'd say, and I think Tyler actually mentioned this, one of the things that I believe is going to be a big deal in the coming years, is so, trying to think of Kubernetes as an implementation detail, as the kernel, do you interact directly with that? Do you learn that interface directly? Are you sort of kind of optimizing your application to be sort of natively aware of those abstractions? I think the answer to all of those questions is no, and Kubernetes is sort of delegated as a compiler target, and so frankly like directionally speaking, I think what Ballerina's sort of design is aspiring towards is the right one. Compile time abstraction for building distributed systems is probably the next logical progression. I like to think of, and I think Brendan Burns has started to talk about this over the last year or two. Everyone's writing assembly code 'cause we're swimming yaml and configuration based designs and systems. You know, sort of pseudodeclarative, but more imperative in static configurations. When in reality we shouldn't be writing these assembly artifacts. We should be delegating all of this complexity to a compiler in the same way that you know, we went from assembly to C to higher level languages. So I think over time that starts to make a lot of sense, and we're going to see a lot of innovation here probably. >> What's your take on the community formation? Obviously, it's growing, so, any observations, any insight for the folks watching what's happening in the community, patterns, trends you'd see, like, don't like. >> I think we could do a better job of reducing politics amongst the really sort of senior community leaders, particularly who have incentives behind their sort of agendas and sort of opinions, since they work for various, you know, large and small companies. >> Yeah, who horse in this race. >> Sure, and there's, whether they're perverse incentives or not, I think net the project has such a high quality genuine, like humble, focused group of people leading it that there isn't much pollution and negativity there. But I think there could be a higher standard in some cases. Since the project is so huge and there are so many very fast moving areas of evolution, there tends to be sort of a fast curve toward many cooks being in the kitchen, you know, when new things materialize and I think that could be better handled. But positive side, I think like the project is becoming incredibly diverse. I just get super excited to see Aparna from Google leading the project at Google, both on the hosted Saas offering and the Kubernetes project. People like Liz and others. And I just think it's an awesome, welcoming, super diverse community. And people should really highlight that more. 'Cause I think it's a unique asset of the project. >> Well you're involved in some deep history. I think we're going to be looking this as moment where there was once a KubeCon that was not part of the CNCF, and you know, you did the right thing, did a good thing. You could have kept it to yourself and made some good cash. >> It's definitely gotten really big, and it's way beyond me now at this point. >> Those guys did a good job with CNCF. >> They're doing phenomenal. I think vast majority of the credit, at this scale, goes to Chris Anasik and Dan Conn, and the events team at the Linux Foundation, CNCF, and obviously Kelsey and Liz and Michelle Noorali and many others. But blood, sweat, and tears. It's no small feat pulling off an event like this. You know, corralling the CFP process, coordinating speakers, setting the themes, it's a really huge job. >> And now they got to deal with all the community, licenses, Lauren your thoughts? >> Well they're consistent across Apache v2 I believe is what Dan said, so all the projects under the CNCF are consistently licensed. So I think that's great. I think they actually have it together there. You know, I do share your concerns about the politics that are going on a little bit back and forth, the high level, I tend to look back at history a little bit, and for those of us that remember JBoss and the JBoss fork, we're a little bit nervous, right? So I think that it's important to take a look at that and make sure that that doesn't happen. Also, you know, open stack and the stuff that we've talked about before with distros coming out or too many distros going to be hitting the street, and how do we keep that more narrow focused, so this can go across-- >> Yeah, I started this, I like to list rank and iterate things, and I started with this sheet of all the vendors, you know, all the Kubernetes vendors, and then Linux Foundation, or CNCF took it over, and they've got a phenomenal sort of conformance testing and sort of compliance versioning sheet, which lists all the vendors and certification status and updates and so on and I think there's 50 or 60 companies. On one hand I think that's great, because it's more innovation, lots of service providers and offerings, but there is a concern that there might be some fragmentation, but again, this is a really big area of focus, and I think it's being addressed. Yeah, I think the right ones will end up winning, right? >> Joseph: Right, for sure. >> and that's what's going to be key. >> Joseph: Healthy competition. >> Yes. >> All right final question. Let's go around the horn. We'll start with you JJ, wrapping up KubeCon 2018, your thoughts, summary, what's happened here? What will we talk about next year about what happened this week in Denmark? >> I think this week in Denmark has been a huge turning point for the growth in Europe and sort of proof that Kubernetes is on like this unstoppable inflection, growth curve. We usually see a smaller audience here in Europe, relative to the domestic event before it. And we're just seeing the numbers get bigger and bigger. I think looking back we're also going to see just the quality of end users and the end user community and more production success stories starting to become front and center, which I think is really awesome. There's lots of vendors here. But I do believe we have a huge representation of end users and companies actually sharing what they're doing pragmatically and really changing their businesses from Financial Times to Cern and physics projects, and you know, JD and other huge companies. I think that's just really awesome. That's a unique thing of the Kubernetes project. There's some hugely transformative companies doing awesome things out there. >> Lauren your thoughts, summary of the week in Denmark? >> I think it's been awesome. There's so much innovation happening here and I don't want to overuse that word 'cause I think it's kind of BS at some point, but really these companies are doing new things, and they're taking this to new levels. I think that hearing about the excitement of the folks that are coming here to actually learn about Kubernetes is phenomenal, and they're going to bring that back into their companies, and you're going to see a lot more actually coming to Europe next year. I also true multicloud would be phenomenal. I would love that if you could actually glue those platforms together, per se. That's really what I'm looking for. But also security. I think security, there needs to be a security seg. We talked to customers earlier. That's something they want to see. I think that that needs to be something that's brought to the table. >> That's awesome. My view is very simple. You know I think they've done a good job in CNCF and Linux Foundation, the team, building the ecosystem, keeping the governance and the technical and the content piece separate. I think they did a good job of showing the future state that we'd like to get to, which is true multicloud, workload portability, those things still out of reach in my opinion, but they did a great job of keeping the tight core. And to me, when I hear words like defacto standard I think of major inflection points where industries have moved big time. You think of internetworking, you think of the web, you think of these moments where that small little tweak created massive new brands and created a disruptor enabler that just created, changed the game. We saw Cisco coming out of that movement of IP with routers you're seeing 3Com come out of that world. I think that this change, this new little nuance called Kubernetes is going to be absolutely a defacto standard. I think it's definitely an inflection point and you're going to see startups come up with new ideas really fast in a new way, in a new modern global architecture, new startups, and I think people are going to be blown away. I think you're going to see fast rising growth companies. I think it's going to be an investment opportunity whether it's token economics or a venture backer private equity play. You're going to see people come out of the wood work, real smart entrepreneur. I think this is what people have been waiting for in the industry so I mean, I'm just super excited. And so thanks for coming on. >> Thank you for everything you do for the community. I think you truly extract the signal from the noise. I'm really excited to see you keep coming to the show, so it's really awesome. >> I appreciate your support, and again we're co-developing content in the open. Lauren great to host with you this week. >> Thank you, it's been awesome. >> And you got a great new venture, high five there. High five to the founder of KubeCon. This is theCUBE, not to be confused with KubeCon. And we're theCUBE, C-U-B-E. I'm John Furrier, thanks for watching. It's a wrap of day two global coverage here exclusively for KubeCon 2018, CNCF and the Linux Foundation. Thanks for watching. (techno music)

>> Announcer: Live from Las Vegas, it's the Cube, covering Dell EMC World 2017. Brought to you by Dell EMC. >> Hello everyone, welcome to the Cube special coverage of Dell EMC World 2017. This is the Cube Silicon Angle's flagship program where we go out to the events and extract the signal from the noise. This is our eighth year of covering EMC World, but now called Dell EMC World. I'm John Furrier, your co-host on our set one and with my co-host Paul Gillin this week as well as Kieth Townshend and John Walls and Rebecca Knight on set two. Double barrel shotgun of content here at Dell EMC World with you. Thanks for joining us for three days of wall to wall coverage. Paul, so much to talk about here this week. Digital transformation, little bit boring theme, it's being played out in real time. But this is a historic moment because one, the Cube started at EMC World in 2010, eight years ago. But, this is the first official EMC World where it's Dell EMC World, kind of a mini event in Austin, but since Michael Dell took over, or I'm sorry, merger of equals, a combination. >> Paul: Combination, as they call it. >> (chuckling) Combination. This is the first instantiation of EMC World as Dell EMC World. Jeremy Burton's now the CMO of Dell Technologies which is the holding company for all the companies. It's the same EMC World flair, now the integrated content. Notable absent Cube alumni and executives from EMC. We'll talk about that in the EMC Mafia segment shortly, but (chuckling) your thoughts because now Michael Dell's puttin' the rubber to the road. Kind of nothing earth shattering in his keynote, but certainly private company, all guns blaring, smiling and dialing, he's got the swagger on stage. >> Well, Michael is nothing if not an optimist. He's always good at seeing a brighter future, and at his keynote this morning, as you said it was blissfully free of content, but it did talk a lot about digital transformation which is of course the buzzword of the year in the IT industry. Little surprised that Dell adopted the same buzzword that HP and Cisco and all these other big companies are adopting. What happened in the keynote is less interesting than how the mood changes here, and this is the coming out party for Dell EMC. Yeah, there was a conference last October, a month after the merger, but this is really, things have finally settled out, now six months later and it's a chance for customers and for the partners to get a sense of how well this is all working out. >> And one of the things I'm watching is how the story's unfolding 'cause now you're starting to see the big companies, certainly in the consolidation side of the business market of infrastructure and data center and enterprise IT, it's a consolidating mature market. It is transforming, there is a cloud story requirement, there are new software requirements, software defined data center, as well as new growth opportunities, so what I'm looking at is what is the story? What is Michael packaging and how does that compare to the competition? We're going to hear from HPE at HPE Discover coming up, the Cube will be covering that for the seventh consecutive year. We're seeing Amazon's story playing out in real time. Oracle's story, everyone's got their story. And it's certainly digital transformation but what's interesting is Michael's got the packaging. He's packaging it up, your thoughts. >> And Michael kind of dissed the cloud this morning, actually in his presentation. He said, you can't have a successful business, or your business is not going to grow as quickly if you're 100% cloud based. He was very much making a pitch for data center infrastructure. Really not surprising coming from Michael. One thing that will be a sub-theme here I think is how this merger is working out, and as we wrote on Silicon Angle this week, if you go back to the history of big mega mergers, particularly in the hardware industry, going back to Burroughs Sperry, DEC Compaq, HP Compaq, Wellfleet Synoptics and NCR AT&T. I mean, it goes on and on and on. Pretty much all disasters, and we really haven't seen a merger anywhere near this scale between two IT companies that has worked well. All indications are now that they're doing the right things, they even have some people on board with Dell EMC who went through some of those mergers. But it's going to be interesting to see how they break a pattern that has been decidedly negative. >> Great point, I loved your post by the way, and I would add that interesting observation, at least from my perspective is, as we sit down with these billionaires and interview them one-on-one on the Cube is, you look at Amazon, Andy Jasse and Jeff Bezos, Bezos in particular. Larry Ellison and Michael Dell, you have essentially captains of industry at the helm. Michael Dell is no spring chicken, but he's also not over the hill either, he's 51 years old. >> Paul: He's a kid relative to most leaders in this industry. >> You know, you hear Jeff Bezos talk and I was watching his talk in DC just this week, he's saying we're taking the long view. If you look at Amazon.com's CEO, Bezos, look at Michael Dell, look at what Ellison's doing, they're all playing the long game card. Now I don't know if that's a hedge against we don't have our story right, or give us more time to bake out our stuff, but I think what's different about Dell Technologies is, Michael's 33 years into the business, one trillion dollars later in sales and he's young, so I think that is a wild card. Ellison's still running the show, Bezos is still running the show, Dell's certainly running the show. I think the wild card on this is the fact that you got a strong founder, and a privately held company. >> And Ellison, it's questionable how long Ellison will be able to run the show, I mean he is over 70 at this point. Dell certainly will be around for a long time. You have to take a long term strategy. If you're not Amazon, you have to take a long term strategy 'cause what other choice do you have? You've lost in the short term, so it's not surprising to hear these guys going that way. I'll be interested to hear from Michael and from his team about the cloud and how they really design and differentiate its strategy. I think IBM has staked its position in cloud out pretty well. Even HPE has got a differentiated position. HPE of course has the configurable hardware, that's a point that Dell I think has to come back on, and the big question is software. John, as you pointed out the other day, VMware is worth more than HPE, by a substantial margin at this point. They've got this huge asset in VMware, not to mention Virtuestream and Pivotal and the other good software assets they acquired. What are they going to do with them? Are they just going to let 'em go free like Michael has done in the past, or are they going to try to mold these into some kind of coordinated whole? >> Well, great point one is on the HPE valuation thing market cap, VMware's actually worth more on market cap and public markets than HPE. Interesting, but not significant in my mind yet, but it does point to the fact that Michael Dell's rhetoric on stage today, he didn't take any shots at HP. Last year he took a big shot at HPE. It's been his rival from day one. I used to work at HP when he was just a mail order company selling white boxes and then he grew that business, obviously the rest is history, but no shot at HP because VMware has to work with HP. Right, (chuckling) so that's interesting. Two is, on the software side, Dell is a hardware company, let's face it. But they have more software now than they've ever had before so that is a good point, we're going to be getting into this date software defined data center to find out how much they actually have. A couple core themes that I see already popping out of the keynote, one, Pivotal. Pivotal and Cloud Foundry's instrumental in the keynotes. NSX was mentioned, Pat Gelsinger's going to be on tomorrow. NSX is VMware's secret play. If you look at what NSX is doing with the Amazon public cloud deal that they did recently this year, NSX could be the real lever in that intellectual property, that lock in, that kind of differentiation. The cloud is not a place, it's a way of doing IT is another message we heard all day today. To me, and your point about bashing cloud, I actually think that's a stake in the ground to kind of hold the line, because they have no cloud strategy. Now, their cloud strategy is kind of hand waiving right now with multi-cloud, which I buy, but multi-cloud is still a fantasy in my mind. Latencies are too low, there just isn't the kind of plumbing yet in place on the clouds for multi-cloud, but certainly hybrid-cloud I think will be multi-cloud roll, so those are the key things and then I'm going to ask Michael directly. You blew 60 billion dollars on this deal. Is there any cash left for M&A? >> Paul: Acquisitions, yeah. >> M&A right now is hot market, you can do some nice tuck ins, fill in the white spaces on the products. Get those software assets and really start cobbling together a growth strategy. There's no doubt in my mind, Paul, that they're going to win the mature, classic business school move of consolidated market. Own the consolidated market, and try to get a growth strategy. To me, that's going to be the big question. What is Dell Technologies and Dell EMC's growth strategy? >> And you would have to think it's either through M&A, perhaps an acquisition of HPE if the valuation continues to go down. Or it's in software It's a good point you made about VMware. Vmware also has a strategic alliance with IBM, so if you're Michael Dell, it's hard to give a compelling keynote speech these days because you can't really offend anybody. His companies now are in cahoots with all these other firms, and of course dissing the cloud is even dangerous because Cloud Foundry is such a critical part of the Pivotal strategy. I think it's an important point, you've got a company that is almost trying to reassemble the old IBM, the old IBM of the '80s which dominated every segment that was important Dell is almost doing that now, I mean the only piece they really don't have is networking. To make a big play, to become the mongo IT company in the world, can they raise the kind of funds for that? >> Yeah, and we're also going to talk about the cloud transition as well as what I'm calling the EMC mafia, folks that have been on the Cube and big executives at EMC. We'll get to that in a minute, but I just want to talk about that cloud play, because you're right, the growth strategy has to come from software. I just don't see the cloud growth yet for these guys, although Michael, in the hallway, conversations are growth in the cloud is doing really well for EMC, not sure. But on the growth strategy, Pivotal, Boo-Mee, Vmware, Virtuestream, and Software Converge Infrastructure are interesting plays, so I think that's where we have to look here. I still think there's a lot of holes in the product line. To me that's important. Now, trends so far, and what we're expecting to hear at the show is, some of my notes Paul, I'll share with you, and get your reaction on. All flash arrays are going to be big, continuing to grow that. Hyperconverge VX rail, we heard that on stage today, claiming to be number one. Power edge 14G. Again, back to speeds and feeds, (chuckling) you know. Storage. Storage is the bread and butter of EMC and now Dell EMC I still think is going to be a real critical beachhead that they going to continue to expand, storage is not going away. Obviously the ice lawn all flash is coming out, and then SSD's, data protection in the cloud. You're starting to see them going where their roots are. Cloud stuff is coming out of the data domain, kind of their core storage first, make sense strategy wise, while they buy their time to fill in the cloud. >> Well, it's a good point about storage. They have a comfortable lead in storage. According to the latest IDC figures, they're a good 15 points ahead of their next biggest competitor. They have a comfortable lead in the hyper converge infrastructure. Four different product lines in that area. These are beachheads that they have to shore up. They have to be sure that their market share doesn't erode in those areas. The question is where does the growth come from? You look at a company that's going through a very similar transition right now, Cisco, which has finally really bought in to software defined networking and is remaking its company around it. That company is having to change the whole culture in response to a technology trend. Now the same thing's going on in the data center. Everything's being remade as virtualized and Vmware is at the center of that, so Michael Dell has the asset to be able to lead that conversion, but are they psychologically going to get there? >> Great point. One, I would agree with you that the whole Cisco example proves the same channel that Dell EMC is. Can they move up the stack? In this case, they're hardware guys, can they add software. Cisco, they're transforming themselves to be more cloud native. The classic move's happening. Cisco have been trying to move up the stack for over a generation. They're plumbing guys, they're networking guys. These guys are hardware guys. Can they get the DNA to truly become software providers, not in the sense of selling software, just providing a software fabric that's going to be the key differentiators, because digital transformation is about IT transformation. That is certainly the reality, what we're seeing when you start to peel back the onions. And that to me is going to be the big discussion because as David Gooldun said on stage, apps provide the value. As the enterprises build more apps, you got to have a platform, you got to have a cohesive horizontal end to end software fabric, and the question is, do they have it? >> Well, they certainly have the foundation for it, I mean they have Pivotal, there's a whole developer community around Pivotal. Dell itself doesn't have a developer community, nor does EMC but they have elements of that to build upon. The interesting thing about the conversion to software, about software defined infrastructure, is that it requires thinking from an application perspective and that's not something hardware companies have ever been inclined to do. So, how does Michael Dell make that transition, has he made it himself, is there other leadership he's going to have to bring in who are going to make it for him? The whole leadership of the Dell EMC company right now is ex-Dell and EMC people, it's hardware guys. >> I'm going to put pressure on Dell, the question on software. But you wrote a two part series on SiliconAngle.com, worth checking out, getting a lot of viral buzz around open source and the value of open source, because if you look at say Cisco for instance, what they're doing with the cloud native strategy, they have actually pivoted and Chuck Robbins, the CEO has acknowledged, actually re-tweeted one of my tweets the other day, with as we were talking about this new program called DevNet Create. They're taking the developer program from Cisco and moving it into an open community model, which basically is the toe in the water for saying, we have to figure out open source. All the critical, big vendors that are transforming from called the old guard, as Amazon calls 'em, Amazon Web Services, Andy Jasse. Dell's an old guard guy, but still young, but they got to get to open source. What are you finding is the success parameters there because you got to play in the open source, be a contributing member. Again, back to the DNA of the culture, and two, there's real value there. >> Well, there's no question that open source has won when it comes to infrastructure. I mean, the biggest IT companies in the world which are Google and Facebook, are both built on open source platforms. Game over. This is where IT infrastructure is headed. Cisco, interesting case because they are an infrastructure company, and they are being eroded, their traditional market is being eroded by open source, they've chosen to embrace it through their developer community. Cisco is one company I would never bet against. They're such a great company. If anyone's going to make the transition, they will. Open source is still an infrastructure play. I don't see open source in the applications area being a major driver, but Dell is an infrastructure company, so you have to assume that everything they're doing in managing, in securing storage and servers is going to be under pressure from open source at some point. They have to embrace that as Cisco is doing. >> Paul, we had thought leader chat with some experts on our digital panel, software crowd chat, everyone knows crowdchat.net, check it out. And comment and conversation was taking place among the influential folks saying, what is a software company? You go back to the web, shrink wrapped, download software, to now fully SAS based and Saas now platform, what is a software company? So, the question was, is Facebook a software company? Or are they an app company? Which begs the question, you have to be a software company, but it's not the classic software company category, business model. You need software (chuckling) to run stuff, so you can be a hardware guy, like Michael Dell, and have Dell Technologies. You can be a network company like Cisco, but you've got to be a software company in the new way. >> Well, I spoke to a Forester analyst in writing that piece on open source who had a great point, he said Facebook and Google are two big successful software companies, neither of which makes. >> Any money. >> Any money, a little bit in Google's case licensing software. They created business models that have nothing to do with the traditional software model, but that have leveraged their expertise in the software that they've developed. And maybe that is the business model, ultimately the business model is building software in order to do something else with it that customers will pay for. >> I think you're on to something. I think your post illuminates that. I think that this is going to be one of those things where in the history books of the tech generation, as we're on our whatever wave of open source generation, this is it, it's not about the business model of the software, it's how the software's being used in the business model of the transformation. That is really really key. Paul, I want to just talk about, really quickly about my observation at EMC. A little bit of editorial moment here. Because, Dell took over. Dell EMC. We've interviewed now eight years, pretty much all the executives at EMC over the years, but there's an EMC mafia developing. There's a lot of people who have left EMC, that we know, we're friends with. Guy Churchwood, CJ DeSai, Josh Conn, Rich DePellatano, Brian Gallagher, BJ Jenkins, Sanjay Murchandani, and many more have left because of the consolidation. Certainly you can't, EMC's going to get consolidated down, but no major layoffs but still enough that some eagles have flown from the nest, as they say and are running other companies. So you have this EMC culture out there of very sales oriented, very customer centric, now running other companies, and I want to give a shout out to all those EMC alumni and mafia out there. Good luck on your new ventures, but the impact here to Dell is a mashup of the two cultures. What's your observation, what's your reaction of that. Have you heard anything? I have some thoughts, but I want to get your reaction because okay, some eagles fly away, you still got the worker bees inside EMC, and now Dell coming together. Thoughts on the culture clash. >> Well, I live in Boston, and so I've been through the acquisition of Prime Computer, through EMC acquiring Data General, through the DEC acquisition by Compaq. All of which were disasters, and all of which where the cultural issues were much bigger than the technology issues. So, I think that that is something that Dell has to be front and center for Michael Dell, is how do you mash up these two cultures. As you pointed out, EMC, very aggressive, take no prisoners, enterprise-oriented sales force. Their sales people make a lot of money. I used to live in a neighborhood where everyone was EMC salespeople. >> John: Buying new houses. >> They were making a million dollars a year. And you've got Dell with its direct model, with its channeled model, and without a particularly strong roots in enterprise sales force and how do you coordinate those. It's not surprising to see people leaving. Of course, in the early days after an acquisition, choices get made, people get promoted and moved in new positions. Those who lose out tend to leave the company. But, I think the sales issue would be something to delve into too. Does Dell want to adopt EMC's sales style, or the other way around? Or is there some way that they can live both in harmony? >> You know, I follow a lot of companies in Silicon Valley as well, I'm out there on the west coast, left coast, as they say. Where all the crazy ones are, as they say. But I got to say, there's been some shrinkage on EMC, but for the most part, I haven't really heard any really negative horror stories. Actually, it's been going pretty well, and I think you bring up an issue of effectiveness with the sales folks. Dell's an efficiency guy, right so you got effectiveness and efficiency coming together. But I think they've handled it well. I really haven't heard any real horror stories. Again, I think that has to do with the founder being actively involved, they're a private company, so they have some room. And I think they've invested in making that happen, so I think generally, props to EMC folks and for the Dell folks on the acquisition. Still not clear the woods yet, it's going to surely be in the products and the revenue, but for the most part, we're going to unpack that. So Paul. >> But you can't, I just wanted to jump in just quickly. You can't minimize customer touch, and EMC was always a high touch company. Outstanding service, they put people on a plane in the middle of the night, charter a private jet in the middle of the night to get someone on site at a customer to fix a problem. As you mentioned, Dell is an efficiency company. That's not a very efficient way to operate. Can they absorb the best of EMC and the best of Dell at the same time? >> Yeah, well we'll certainly tell, I mean they got a lot of competition, Michael Dell saying on stage. (mumbling) startups, essentially what's he's saying is Amazon, there in my opinion, although that's not probly what he really meant but that's my interpretation. But I'm expecting to see the same old EMC world with a twist, and that is, we're doin' good, the messaging's out there, we're going to see how the products compare vis a vis the competition. I'm interested in Vmware piece. Paul, what are you looking forward to? >> I'm looking forward to hearing how this is all going, how this company is culturally, what kind of a cultural chimera they're putting together here that's going to make sense, that the market is going to understand. I also want to hear how they're going to differentiate in cloud, internet of things, we just heard a little bit about that this morning. That's something where I think you're seeing Cisco. The way Cisco's dealing with the cloud these days is to say, don't worry about it, it's all going IOT. It's all going to distributed intelligent devices, the cloud is already history, is what they're saying. So, does Dell have a similar differentiated position on that. I'm least interested in hearing about the new products because it's speeds and feeds. But really, how is this company going to dominate an industry, how is it going to get over some of the speed bumps that we've been talking about for the last 20 minutes that have foiled so many merger attempts in the past. >> One of the tell signs that I look at a conference when I see a lot of AI washing. The good news is, there's not a lot of AI being talked about here, 'cause usually that's just lipstick on the pig, as they say. Except for the case of Google and Amazon Web Services, they do have some AI story, with some real products to back it up. For the most part, you're not seeing EMC glob on the whole machine learning, rah rah. They did talk about it but it wasn't like a big theme. I think they really talked about the packaging of the value. Of the brands together, comments around costs for public cloud, nice little ding there. I'm going to dig into the story. I'm going to really test the story, and I'm going to look at the customer traction. I really want to see who they have on stage, I really want to hear who's really going down the road, how that growth strategy, 'cause I think they're going to win the data consolidation market pretty handily, and the question between HPE and Dell, for instance, 'cause that's really to me the two big horses on the track. Who's going to win the growth. Who's going to be able to lock in their beachhead on the core market, traditional market, and have access to the growth of what cloud will bring and IOT and among other things. >> I think at this point, HP has a better story in that area with their configurable infrastructure, with their pay as you go on site model, really interesting models. I was at HP World in Europe in December, and I came away from that feeling like these guys have some unique talking points here. At least they have a strategy that I think I understand and that is different. Dell is still working through this huge merger and that's a big catch. >> Bottom line is, Dave Donatelli, who's an executive at Oracle told me, he also was an EMC executive, and HPE. The business of provisioning servers and storage (laughing) is not going to be the growth strategy. Now, it might be a component of the overall business model, like software, but ultimately, that business is in decline, and that's a fact. Okay, this is the Cube, bringing you all the coverage of the kickoff from day one at Dell EMC World 2017. Our eighth year, three days of wall to wall coverage. We have two sets, the blue set and the white set. Go to SiliconAngle.tv to find the coverage, also go on Twitter, follow us on the Cube, I'm John Furrier with Paul Gillin, kickin' off Dell EMC World 2017, back with more, stay with us after this short break. (atmospheric instrumental music)