>> From theCUBE Studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. >> After a two-year epic run in tech, 2022 has been an epically bad year. Through yesterday, The NASDAQ composite is down 30%. The S$P 500 is off 21%. And the Dow Jones Industrial average 16% down. And the poor holders at Bitcoin have had to endure a nearly 60% decline year to date. But judging by the attendance and enthusiasm, in major in-person tech events this spring. You'd never know that tech was in the tank. Moreover, walking around the streets of Las Vegas, where most tech conferences are held these days. One can't help but notice that the good folks of Main Street, don't seem the least bit concerned that the economy is headed for a recession. Hello, and welcome to this weeks Wiki Bond Cube Insights powered by ETR. In this Breaking Analysis we'll share our main takeaways from the first half of 2022. And talk about the outlook for tech going forward, and why despite some pretty concerning headwinds we remain sanguine about tech generally, but especially enterprise tech. Look, here's the bumper sticker on why many folks are really bearish at the moment. Of course, inflation is high, other than last year, the previous inflation high this century was in July of 2008, it was 5.6%. Inflation has proven to be very, very hard to tame. You got gas at $7 dollars a gallon. Energy prices they're not going to suddenly drop. Interest rates are climbing, which will eventually damage housing. Going to have that ripple effect, no doubt. We're seeing layoffs at companies like Tesla and the crypto names are also trimming staff. Workers, however are still in short supply. So wages are going up. Companies in retail are really struggling with the right inventory, and they can't even accurately guide on their earnings. We've seen a version of this movie before. Now, as it pertains to tech, Crawford Del Prete, who's the CEO of IDC explained this on theCUBE this very week. And I thought he did a really good job. He said the following, >> Matt, you have a great statistic that 80% of companies used COVID as their point to pivot into digital transformation. And to invest in a different way. And so what we saw now is that tech is now where I think companies need to focus. They need to invest in tech. They need to make people more productive with tech and it played out in the numbers. Now so this year what's fascinating is we're looking at two vastly different markets. We got gasoline at $7 a gallon. We've got that affecting food prices. Interesting fun fact recently it now costs over $1,000 to fill an 18 wheeler. All right, based on, I mean, this just kind of can't continue. So you think about it. >> Don't put the boat in the water. >> Yeah, yeah, yeah. Good luck if ya, yeah exactly. So a family has kind of this bag of money, and that bag of money goes up by maybe three, 4% every year, depending upon earnings. So that is sort of sloshing around. So if food and fuel and rent is taking up more, gadgets and consumer tech are not, you're going to use that iPhone a little longer. You're going to use that Android phone a little longer. You're going to use that TV a little longer. So consumer tech is getting crushed, really it's very, very, and you saw it immediately in ad spending. You've seen it in Meta, you've seen it in Facebook. Consumer tech is doing very, very, it is tough. Enterprise tech, we haven't been in the office for two and a half years. We haven't upgraded whether that be campus wifi, whether that be servers, whether that be commercial PCs as much as we would have. So enterprise tech, we're seeing double digit order rates. We're seeing strong, strong demand. We have combined that with a component shortage, and you're seeing some enterprise companies with a quarter of backlog, I mean that's really unheard of. >> And higher prices, which also profit. >> And therefore that drives up the prices. >> And this is a theme that we've heard this year at major tech events, they've really come roaring back. Last year, theCUBE had a huge presence at AWS Reinvent. The first Reinvent since 2019, it was really well attended. Now this was before the effects of the omicron variant, before they were really well understood. And in the first quarter of 2022, things were pretty quiet as far as tech events go But theCUBE'a been really busy this spring and early into the summer. We did 12 physical events as we're showing here in the slide. Coupa, did Women in Data Science at Stanford, Coupa Inspire was in Las Vegas. Now these are both smaller events, but they were well attended and beat expectations. San Francisco Summit, the AWS San Francisco Summit was a bit off, frankly 'cause of the COVID concerns. They were on the rise, then we hit Dell Tech World which was packed, it had probably around 7,000 attendees. Now Dockercon was virtual, but we decided to include it here because it was a huge global event with watch parties and many, many tens of thousands of people attending. Now the Red Hat Summit was really interesting. The choice that Red Hat made this year. It was purposefully scaled down and turned into a smaller VIP event in Boston at the Western, a couple thousand people only. It was very intimate with a much larger virtual presence. VeeamON was very well attended, not as large as previous VeeamON events, but again beat expectations. KubeCon and Cloud Native Con was really successful in Spain, Valencia, Spain. PagerDuty Summit was again a smaller intimate event in San Francisco. And then MongoDB World was at the new Javits Center and really well attended over the three day period. There were lots of developers there, lots of business people, lots of ecosystem partners. And then the Snowflake summit in Las Vegas, it was the most vibrant from the standpoint of the ecosystem with nearly 10,000 attendees. And I'll come back to that in a moment. Amazon re:Mars is the Amazon AI robotic event, it's smaller but very, very cool, a lot of innovation. And just last week we were at HPE Discover. They had around 8,000 people attending which was really good. Now I've been to over a dozen HPE or HPE Discover events, within Europe and the United States over the past decade. And this was by far the most vibrant, lot of action. HPE had a little spring in its step because the company's much more focused now but people was really well attended and people were excited to be there, not only to be back at physical events, but also to hear about some of the new innovations that are coming and HPE has a long way to go in terms of building out that ecosystem, but it's starting to form. So we saw that last week. So tech events are back, but they are smaller. And of course now a virtual overlay, they're hybrid. And just to give you some context, theCUBE did, as I said 12 physical events in the first half of 2022. Just to compare that in 2019, through June of that year we had done 35 physical events. Yeah, 35. And what's perhaps more interesting is we had our largest first half ever in our 12 year history because we're doing so much hybrid and virtual to compliment the physical. So that's the new format is CUBE plus digital or sometimes just digital but that's really what's happening in our business. So I think it's a reflection of what's happening in the broader tech community. So everyone's still trying to figure that out but it's clear that events are back and there's no replacing face to face. Or as I like to say, belly to belly, because deals are done at physical events. All these events we've been to, the sales people are so excited. They're saying we're closing business. Pipelines coming out of these events are much stronger, than they are out of the virtual events but the post virtual event continues to deliver that long tail effect. So that's not going to go away. The bottom line is hybrid is the new model. Okay let's look at some of the big themes that we've taken away from the first half of 2022. Now of course, this is all happening under the umbrella of digital transformation. I'm not going to talk about that too much, you've had plenty of DX Kool-Aid injected into your veins over the last 27 months. But one of the first observations I'll share is that the so-called big data ecosystem that was forming during the hoop and around, the hadoop infrastructure days and years. then remember it dispersed, right when the cloud came in and kind of you know, not wiped out but definitely dampened the hadoop enthusiasm for on-prem, the ecosystem dispersed, but now it's reforming. There are large pockets that are obviously seen in the various clouds. And we definitely see a ecosystem forming around MongoDB and the open source community gathering in the data bricks ecosystem. But the most notable momentum is within the Snowflake ecosystem. Snowflake is moving fast to win the day in the data ecosystem. They're providing a single platform that's bringing different data types together. Live data from systems of record, systems of engagement together with so-called systems of insight. These are converging and while others notably, Oracle are architecting for this new reality, Snowflake is leading with the ecosystem momentum and a new stack is emerging that comprises cloud infrastructure at the bottom layer. Data PaaS layer for app dev and is enabling an ecosystem of partners to build data products and data services that can be monetized. That's the key, that's the top of the stack. So let's dig into that further in a moment but you're seeing machine intelligence and data being driven into applications and the data and application stacks they're coming together to support the acceleration of physical into digital. It's happening right before our eyes in every industry. We're also seeing the evolution of cloud. It started with the SaaS-ification of the enterprise where organizations realized that they didn't have to run their own software on-prem and it made sense to move to SaaS for CRM or HR, certainly email and collaboration and certain parts of ERP and early IS was really about getting out of the data center infrastructure management business called that cloud 1.0, and then 2.0 was really about changing the operating model. And now we're seeing that operating model spill into on-prem workloads finally. We're talking about here about initiatives like HPE's Green Lake, which we heard a lot about last week at Discover and Dell's Apex, which we heard about in May, in Las Vegas. John Furrier had a really interesting observation that basically this is HPE's and Dell's version of outposts. And I found that interesting because outpost was kind of a wake up call in 2018 and a shot across the bow at the legacy enterprise infrastructure players. And they initially responded with these flexible financial schemes, but finally we're seeing real platforms emerge. Again, we saw this at Discover and at Dell Tech World, early implementations of the cloud operating model on-prem. I mean, honestly, you're seeing things like consoles and billing, similar to AWS circa 2014, but players like Dell and HPE they have a distinct advantage with respect to their customer bases, their service organizations, their very large portfolios, especially in the case of Dell and the fact that they have more mature stacks and knowhow to run mission critical enterprise applications on-prem. So John's comment was quite interesting that these firms are basically building their own version of outposts. Outposts obviously came into their wheelhouse and now they've finally responded. And this is setting up cloud 3.0 or Supercloud, as we like to call it, an abstraction layer, that sits above the clouds that serves as a unifying experience across a continuum of on-prem across clouds, whether it's AWS, Azure, or Google. And out to both the near and far edge, near edge being a Lowes or a Home Depot, but far edge could be space. And that edge again is fragmented. You've got the examples like the retail stores at the near edge. Outer space maybe is the far edge and IOT devices is perhaps the tiny edge. No one really knows how the tiny edge is going to play out but it's pretty clear that it's not going to comprise traditional X86 systems with a cool name tossed out to the edge. Rather, it's likely going to require a new low cost, low power, high performance architecture, most likely RM based that will enable things like realtime AI inferencing at that edge. Now we've talked about this a lot on Breaking Analysis, so I'm not going to double click on it. But suffice to say that it's very possible that new innovations are going to emerge from the tiny edge that could really disrupt the enterprise in terms of price performance. Okay, two other quick observations. One is that data protection is becoming a much closer cohort to the security stack where data immutability and air gaps and fast recovery are increasingly becoming a fundamental component of the security strategy to combat ransomware and recover from other potential hacks or disasters. And I got to say from our observation, Veeam is leading the pack here. It's now claiming the number one revenue spot in a statistical dead heat with the Dell's data protection business. That's according to Veeam, according to IDC. And so that space continues to be of interest. And finally, Broadcom's acquisition of Dell. It's going to have ripple effects throughout the enterprise technology business. And there of course, there are a lot of questions that remain, but the one other thing that John Furrier and I were discussing last night John looked at me and said, "Dave imagine if VMware runs better on Broadcom components and OEMs that use Broadcom run VMware better, maybe Broadcom doesn't even have to raise prices on on VMware licenses. Maybe they'll just raise prices on the OEMs and let them raise prices to the end customer." Interesting thought, I think because Broadcom is so P&L focused that it's probably not going to be the prevailing model but we'll see what happens to some of the strategic projects rather like Monterey and Capitola and Thunder. We've talked a lot about project Monterey, the others we'll see if they can make the cut. That's one of the big concerns because it's how OEMs like the ones that are building their versions of outposts are going to compete with the cloud vendors, namely AWS in the future. I want to come back to the comment on the data stack for a moment that we were talking about earlier, we talked about how the big data ecosystem that was once coalescing around hadoop dispersed. Well, the data value chain is reforming and we think it looks something like this picture, where cloud infrastructure lives at the bottom. We've said many times the cloud is expanding and evolving. And if companies like Dell and HPE can truly build a super cloud infrastructure experience then they will be in a position to capture more of the data value. If not, then it's going to go to the cloud players. And there's a live data layer that is increasingly being converged into platforms that not only simplify the movement in ELTing of data but also allow organizations to compress the time to value. Now there's a layer above that, we sometimes call it the super PaaS layer if you will, that must comprise open source tooling, partners are going to write applications and leverage platform APIs and build data products and services that can be monetized at the top of the stack. So when you observe the battle for the data future it's unlikely that any one company is going to be able to do this all on their own, which is why I often joke that the 2020s version of a sweaty Steve Bomber running around the stage, screaming, developers, developers developers, and getting the whole audience into it is now about ecosystem ecosystem ecosystem. Because when you need to fill gaps and accelerate features and provide optionality a list of capabilities on the left hand side of this chart, that's going to come from a variety of different companies and places, we're talking about catalogs and AI tools and data science capabilities, data quality, governance tools and it should be of no surprise to followers of Breaking Analysis that on the right hand side of this chart we're including the four principles of data mesh, which of course were popularized by Zhamak Dehghani. So decentralized data ownership, data as products, self-serve platform and automated or computational governance. Now whether this vision becomes a reality via a proprietary platform like Snowflake or somehow is replicated by an open source remains to be seen but history generally shows that a defacto standard for more complex problems like this is often going to emerge prior to an open source alternative. And that would be where I would place my bets. Although even that proprietary platform has to include open source optionality. But it's not a winner take all market. It's plenty of room for multiple players and ecosystem innovators, but winner will definitely take more in my opinion. Okay, let's close with some ETR data that looks at some of those major platform plays who talk a lot about digital transformation and world changing impactful missions. And they have the resources really to compete. This is an XY graphic. It's a view that we often show, it's got net score on the vertical access. That's a measure of spending momentum, and overlap or presence in the ETR survey. That red, that's the horizontal access. The red dotted line at 40% indicates that the platform is among the highest in terms of spending velocity. Which is why I always point out how impressive that makes AWS and Azure because not only are they large on the horizontal axis, the spending momentum on those two platforms rivals even that of Snowflake which continues to lead all on the vertical access. Now, while Google has momentum, given its goals and resources, it's well behind the two leaders. We've added Service Now and Salesforce, two platform names that have become the next great software companies. Joining likes of Oracle, which we show here and SAP not shown along with IBM, you can see them on this chart. We've also plotted MongoDB, which we think has real momentum as a company generally but also with Atlas, it's managed cloud database as a service specifically and Red Hat with trying to become the standard for app dev in Kubernetes environments, which is the hottest trend right now in application development and application modernization. Everybody's doing something with Kubernetes and of course, Red Hat with OpenShift wants to make that a better experience than do it yourself. The DYI brings a lot more complexity. And finally, we've got HPE and Dell both of which we've talked about pretty extensively here and VMware and Cisco. Now Cisco is executing on its portfolio strategy. It's got a lot of diverse components to its company. And it's coming at the cloud of course from a networking and security perspective. And that's their position of strength. And VMware is a staple of the enterprise. Yes, there's some uncertainty with regards to the Broadcom acquisition, but one thing is clear vSphere isn't going anywhere. It's entrenched and will continue to run lots of IT for years to come because it's the best platform on the planet. Now, of course, these are just some of the players in the mix. We expect that numerous non-traditional technology companies this is important to emerge as new cloud players. We've put a lot of emphasis on the data ecosystem because to us that's really going to be the main spring of digital, i.e., a digital company is a data company and that means an ecosystem of data partners that can advance outcomes like better healthcare, faster drug discovery, less fraud, cleaner energy, autonomous vehicles that are safer, smarter, more efficient grids and factories, better government and virtually endless litany of societal improvements that can be addressed. And these companies will be building innovations on top of cloud platforms creating their own super clouds, if you will. And they'll come from non-traditional places, industries, finance that take their data, their software, their tooling bring them to their customers and run them on various clouds. Okay, that's it for today. Thanks to Alex Myerson, who is on production and does the podcast for Breaking Analysis, Kristin Martin and Cheryl Knight, they help get the word out. And Rob Hoofe is our editor and chief over at Silicon Angle who helps edit our posts. Remember all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcast. I publish each week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com or DM me at dvellante, or comment on my LinkedIn posts. And please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for theCUBE's Insights powered by ETR. Thanks for watching be well. And we'll see you next time on Breaking Analysis. (upbeat music)

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Valencia Spain in co con cloud native con Europe, 2022. I'm Keith Townsend with my cohos on Rico senior. Etti senior it analyst at gig home. Exactly 7,500 people I'm told en Rico. What's the flavor of the show so far, >>It's a fantastic mood. I mean, I found a lot of people wanting to track talk about what they're doing with Kubernetes, sharing their, you know, stories, some word stories that meet tough. And you know, this is where you learn actually, because we had a lot of zoom calls, webinar and stuff, but it is when you talk a video, oh, I did it this way and it didn't work out very well. So, and, and you start a conversation like this that is really different from learning from zoom. When, you know, everybody talks about things that working well, they did it, right. No, it's here that you learn from other experiences. >>So we're talking to amazing people the whole week, talking about those experiences here on the queue, fresh on the queue for the first time, Chris Vos, senior software engineer at Microsoft Xbox, Chris, welcome to the queue. >>Thank you so much for having >>Me. So first off, give us a high level picture of the environment that you're running at Microsoft. >>Yeah. So, you know, we've got 20, well probably close to 30 clusters at this point around the globe, you know, 700 to a thousand pods per cluster, roughly. So about 22,000 pods total. So yeah, it's pretty pretty sizable footprint and yeah. So we've been running on Kubernetes since 2018 and well actually might be 2017, but anyways, so yeah, that, that's kind of our, our footprint. >>Yeah. So all of that, let's talk about the basics, which is security across multiple I'm assuming containers, work, microservices, et cetera. Why did you and the team settle on link or do >>Yeah, so previously we had our own kind of solution for managing TLS certs and things like that. And we found it to be pretty painful pretty quickly. And so we knew, you know, we wanted something that was a little bit more abstracted away from the developers and, and things like that that allowed us to move quickly. And so we began investigating, you know, solutions to that. And a few of our colleagues went to Cuban in San Diego in 2019 cloud native con as well. And basically they just, you know, sped it all up. And actually funny enough, my, my old manager was one of the people who was there and he went to the link D booth and they had a thing going that was like, Hey, get set up with MTLS in five minutes. And he was like, this is something we want to do, why not check this out? And he was able to do it. And so that, that put it on our radar. And so yeah, we investigated several others and Leer D just perfectly fit exactly what we needed. >>So, so in general, we are talking about, you know, security at scale. So how you manage security to scale and also flexibility, right. But you know, what is the you, this there, you told us about the five minutes to start using there, but you know, again, we are talking about word stories. We talk about, you know, all these. So what, what, what kind of challenges you found at the beginning when you start adopting this technology? >>So the biggest ones were around getting up and running with like a new service, especially in the beginning, right. We were, you know, adding a new service almost every day. It felt like. And so, you know, basically it took someone going through a whole bunch of different repos, getting approvals from everyone to get the SEARCHs minted, all that fun stuff, getting them put into the right environments and in the right clusters to make sure that, you know, everybody is talking appropriately. And just the amount of work that, that took alone was just a huge headache and a huge barrier to entry for us to, you know, quickly move up the number of services we have. So, >>So I'm, I'm trying to wrap my head around the scale of the challenge. When I think about certification or certificate management, I have to do it on a small scale and the, the, every now and again, when a certificate expires, it is just a troubleshooting pain. Yes. So as I think about that, it costs, it's not just certificates across 22,000 pods or it's certificates across 22,000 pods in multiple applications. How were you doing that before link D like, what was the, what and what were the pain points? Like? What happens when a certificate either fails or expired up not, not updated? >>So, I mean, to be completely honest, the biggest thing is we're just unable to make the calls, you know, out or, or in, based on yeah. What is failing basically. But, you know, we saw essentially an uptick in failures around a certain service and pretty quickly, I pretty quickly, we got used to the fact that it was like, oh, it's probably a cert expiration issue. And so we tried, you know, a few things in order to make that a little bit more automated and things like that, but we never came to a solution that like didn't require every engineer on the team to know essentially quite a bit about this, just to get into it, which was a huge issue. >>So talk about day two after you've deployed link D how did this alleviate software engineers and what was like the, the benefits of now having this automated way of managing >>Certs? So the biggest thing is like, there is no touch from developers, everyone on our team. Well, I mean, there are a lot of people who are familiar with security and certs and all of that stuff, but no one has to know it. Like it's not a requirement. Like for instance, I knew nothing about it when I joined the team. And even when I was setting up our newer clusters, I knew very little about it. And I was still able to really quickly set up blinker D, which was really nice. And, and it's been, you know, essentially we've been able to just kind of set it and not think about it too much. Obviously, you know, there are parts of it that you have to think about. We monitor it and all that fun stuff, but, but yeah, it's been pretty painless almost day one. It took a lot, a long time to trust it for developers. You know, anytime there was a failure, it's like, oh, could this be link or D you know, but after a while, like now we don't have that immediate assumption because people have built up that trust, but >>Also you have this massive infrastructure, I mean, 30 cluster. So I guess that it's quite different to manage a single cluster and 30. So what are the, you know, consideration that you have to do to install this software on, you know, 30 different cluster manage different, you know, versions probably etcetera, etcetera, et cetera. >>So, I mean, you know, the, the, as far as like, I guess, just to clarify, are you asking specifically with Linky or are you just asking in more in general? Well, >>I mean, you, you can take the, the question in the, in two ways, so, okay. Yeah. Yes. Link in particular, but the 30 cluster also quite interesting. >>Yeah. So, I mean, you know, more generally, you know, how we manage our clusters and things like that. We have, you know, a CLI tool that we use in order to like, change context very quickly and switch and communicate with whatever cluster we're trying to connect to and, you know, are we debugging or getting logs, whatever. And then, you know, with link D it's nice because again, you know, we, we, aren't having to worry about like, oh, how is this cert being inserted in the right node or, or not the right node, but in the right cluster or things like that. Whereas with link D we don't, we don't really have that concern when we spin up our, our clusters, essentially we get the root certificate and, and everything like that packaged up, passed along to link D on installation. And then essentially there's not much we have to do after that. >>So talk to me about your upcoming coming section here at Q con what's the, what's the high level talking points? Like what, what will attendees learn? >>Yeah. So it's, it's a journey. Those are the sorts of talks that I find useful. Having not been, you know, I, I'm not a deep Kubernetes expert from, you know, decades or whatever of experience, but I think >>Nobody is >>Also true. That's another story. That's a, that's, that's a job posting decades of requirements for >>Of course. Yeah. But so, you know, it, it's a journey it's really just like, Hey, what made us decide on a service mesh in the first place? What made us choose link D and then what are the ways in which, you know, we, we use link D so what are those, you know, we use some of the extra plugins and things like that. And then finally, a little bit about more, what we're gonna do in the future. >>Let's talk about not just necessarily the future as in two or three days from now, or two or three years from now. Well, the future after you immediately solve the, the low level problems with link D what were some of the, the surprises, because link D in service me in general has have side benefits. Do you experience any of those side benefits as well? >>Yeah, it's funny, you know, writing the, the blog post, you know, I hadn't really looked at a lot of the data in years on, you know, when we did our investigations and things like that. And we had seen that we like had very low latency and low CPU utilization and things like that. And looking at some of that, I found that we were actually saving time off of requests. And I couldn't really think of why that was, and I was talking with someone else and the biggest, unfortunately, all that data's gone now, like the source data. So I can't go back and verify this, but it, it makes sense, you know, there's the availability zone routing that linker D supports. And so I think that's actually doing it where, you know, essentially if a node is closer to another node, it's essentially, you know, routing to those ones. So when one service is talking to another service and maybe on they're on the same node, you know, it, it short circuits that, and allows us to gain some, some time there. It's not huge, but it adds up after, you know, 10, 20 calls down the line. Right. >>In general. So you are saying that it's smooth operations in, in ATS, very, you know, simplifying your life. >>And again, we didn't have to really do anything for that. It, it, it handled that for it was there. Yeah. Yep. Yeah, exactly. >>So we know one thing when I do it on my laptop, it works fine when I do it with across 22,000 pods, that's a different experience. What were some of the lessons learned coming out of KU con 2018 in San Diego was there? I wish I would've ran to the microphone folks, but what were some of the hard lessons learned scaling link D across the 22,000 nodes? >>So, you know, the, the first one, and this seems pretty obvious, but was just not something I knew about was the high availability mode of link D so obviously makes sense. You would want that in a, you know, a large scale environment. So like, that's one of the big lessons that like, we didn't ride away. No. Like one of the mistakes we made in, in one of our pre-production clusters was not turning that on. And we were kind of surprised. We were like, whoa, like all of these pods are spinning up, but they're having issues like actually getting injected and things like that. And we found, oh, okay. Yeah, you need to actually give it some, some more resources, but it's still very lightweight considering, you know, they have high availability mode, but it's just a few instances still. >>So from, even from a, you know, binary perspective and running link D how much overhead is it? >>That is a great question. So I don't remember off the top of my head, the numbers, but it's very lightweight. We, we evaluated a few different service missions and it was the lightest weight that we encountered at that point. >>And then from a resource perspective, is it a team of link D people? Is it a couple of people, like how >>To be completely honest for a long time, it was one person, Abraham who actually is the person who proposed this talk. He couldn't make it to Valencia, but he essentially did probably 95% of the work to get a into production. And then this was before we even had a team dedicated to our infrastructure. And so we have, now we have a team dedicated, we're all kind of Linky folks, if not Linky experts, we at least can troubleshoot basically. And things like that. So it's, I think a group of six people on our team, and then, you know, various people who've had experience with it >>On other teams, but I'm not dedicated just to that. >>I mean, >>No one is dedicated just to it. No, it's pretty like pretty light touch once it's, once it's up and running, it took a very long time for us to really understand it and, and to, you know, get like, not getting started, but like getting to where we really felt comfortable letting it go in production. But once it was there, like, it is very, very light touch. >>Well, I really appreciate you stopping by Chris. It's been an amazing conversation to hear how Microsoft is using a open source project. Exactly. At scale. It's just a few years ago, when you would've heard the concept of Microsoft and open source together and like, oh, that's just, you know, but >>They have changed a lot in the last few years now, there are huge contributors. And, you know, if you go to Azure, it's full of open source stuff, every >>So, yeah. Wow. The Cuban 2022, how the world has changed in so many ways from Licia Spain, I'm Keith Townsend, along with a Rico senior, you're watching the, the leader in high tech coverage.

>> Live from Barcelona, Spain, it's the Cube, covering KubeCon CloudNativeCon Europe 2019. Brought to you by Red Hat, the Cloud Native Computing Foundation, and Ecosystem Partners. >> Welcome back, this is theCube getting towards the end of two days live wall-to-wall coverage here at KubeCon, CloudNativeCon 2019 in Barcelona. I'm Stu Miniman, my co-host for this week has been Corey Quinn and happy to have on one of our hosts for this week from the Cloud Native Computing Foundation, Dee Kumar, the Vice President of Marketing, also helps with developer relations. Dee, welcome back to the program. >> Thanks for having me. >> And thank you for having us. We've been having a great time this week, a lot of buzz, a lot of people and obviously always a lot of enthusiasm at the show here. Thanks so much. Alright, so your team has been super busy. I've talked with a lot of them leading up to the show. >> That's right. >> Anybody that knows any show of this kind of magnitude know we're usually pretty exhausted before we get on planes and change all the time zones. So, you know, thank you for holding strong. Give us a little bit about, you know, when we talk marketing, you have a big annual report that came out recently from 2018. Give us some of the highlights of some of the things you've been seeing. >> Yeah, sure. Like you mentioned, you're seeing all the excitement and buzz here so this is our largest open-source developer conference, when compared to the last year we did in Copenhagen. So we have close to 8,000 attendees so we're really excited about that. And you're absolutely right, with that comes, we're so exhausted, but we really appreciate. I think the reason the conference has been so successful is primarily just because of the community engagement, which I highlight in the annual report. So it's a combination of our community, which is the developers, the contributors, also our end users, and the third significant portion of our ecosystem is our members. So we recently just announced that CNCF has crossed over 400 members, our end user community is growing, I think Sheryl mentioned this morning in the keynote, we have about 81 end users and this is phenomenal because end of the day, end users are companies who are not commercializing Cloud Native, but essentially they're using these products or technologies internally, so they are essentially the guinea pig of Cloud Native technologies and it's really important to learn from them. >> Well Dee, and actually it's interesting, you know, celebrating the five years of Kubernetes here, I happened to talk to a couple of the OG's of the community, Joe Beta, Tim Hawkin and Gabe Monroy. And I made a comment to Joe, and I'm like, "Well Google started it, but they brought in the Ecosync and pulled in a lot of other vendors too, it's people. And Gabe said, he's like "yeah, I started Deis and I was one of the people >> Absolutely. >> that joined in." So, we said this community is, it's people more than it's just the collection of the logos on the slides. >> Absolutely, I completely agree. And the other thing I also want to point out is a neutral home, like CNCF, it definitely increases contributions. And the reason I say that is, having a neutral home helps the community in terms of engaging and what is really interesting again, going back to the annual report is Google had a leadership role and most of the contributors were from Google, and now with having a neutral home, I think Google has done a phenomenal job to make sure that the contributors are not just limited to Google. And we're seeing all the other companies participating. We're also seeing a new little graph of independent contributors, who are essentially not associated with any companies and they've been again, very active with their comments or their engagement with overall, in terms of, not just limiting to Kubernetes, but all the other CNCF projects. >> So, this is sort of a situation of being a victim of your own success to some extent, but I've mentioned a couple of times today with various other guests, that this could almost be called a conference about Kubernetes and friends, where it feels like that single project casts an awfully long shadow, when you talk to someone who's vaguely familiar with the CNCF, it's "Oh you mean the Kubernetes people?" "Cool, we're on the same page." How do you, I guess from a marketing perspective begin to move out from under that shadow and become something that is more than a single project foundation? >> Yeah, that's a great question, and the way we are doing that is, I think, Kubernetes has become an economic powerhouse essentially, and what it has done is, it's allowed for other start-ups and other companies to come in and start creating new projects and technologies built around Kubernetes, so essentially, now, you're no longer talking about one single project. It's no longer limited to containers or orchestration, or just micro-services, which was the conversation 3 years ago at KubeCon, and today, what you will see is, it's about talking about the ecosystem. So, the way, from a marketing perspective, and it's actually the reality as well, is Kubernetes has now led to other growing projects, it's actually helped other developers come onboard, so now we are seeing a lot more co-ord, a lot more contributions, and now, CNCF has actually become a home to 35+ projects. So when it was founded, we had about 4 projects, and now it's just grown significantly and I think Kubernetes was the anchor tannin, but now we're just talking about the ecosystem as a whole. >> Dee, I'm wondering if it might be too early for this, but do you have a way of measuring success if I'm someone that has rolled out Kubernetes and some of the associated projects? When I talked to the early Kubernetes people, it's like, Kubernetes itself is just an enabler, and it's what we can do with it and all the pieces that go with it, so I don't know that there's spectrums of how are we doing on digital transformation, and it's a little early to say that there's a trillion dollars of benefit from this environm... but, do you have any measure today, or thoughts as to how we can measure the success of everything that comes out of the... >> Yeah, so I think there was Redmont, they published a report last year and it looks like they're in the process of updating, but it is just phenomenal to see, just based on their report, over 50% of fortune 100 companies have started to use Kubernetes in production, and then I would say, more than, I think, to be accurate, 71% of fortune 100 companies are using containers, so I think, right there is a big step forward. Also, if you look at it last year, Kubernetes was the first project to graduate, so one of the ways we also measure, in terms of the success of these projects, is the status that we have within CNCF, and that is completely community driven, so we have a project that's very early stage, it comes in as a sandbox, and then just based on the community growth, it moves onto the next stage, which is incubating, and then, it takes a big deal to graduate, and to actually go to graduation, so we often refer to those stages of the projects to Jeffery Moore, in terms of crossing the chasm. We've talked about that a lot. And again, to answer your question, in terms of how exactly you measure success is just not limited to Kubernetes. We had, this year, a few other projects graduates, we have 6 projects that have graduated within CNCF. >> How do you envision this unfolding in the next 5 years, where you continue to accept projects into the foundation? At some point, you wind up with what will only be described as a sarcastic number of logos on a slide for all of the included projects. How do you effectively get there without having the Cheesecake Factory menu problem of... the short answer is just 'yes', rather than being able to list them off coz no one can hold it all in their head anymore? >> Great question, we're still working on it. We do have a trail map that is a representation of 'where do I get started?', so it's definitely not prescriptive, but it kind of talks about the 10 steps, and it not only talks about it from a technology perspective, but it also talks about processes and people, so we do cover the DevOp, CICD cycle or pipeline. The other thing I would say is, again, we are trying to find other creative ways to move past the logos and landscape, and you're absolutely right, it's now becoming a challenge, but, you know, our members with 400+ members within CNCF. The other way to actually look at it is, back to my earlier point on ecosystems. So one of the areas that we are looking at is, 'okay, now, what next after orchestration?', which is all about Kubernetes is, now I think there's a lot of talks around security, so we're going to be looking at use cases, and also Cloud Native storage is becoming another big theme, so I would say we now have to start thinking more about solutions, solution, the terminology has always existed in the enterprise world for a long time, but it's really interesting to see that come alive on the Cloud Native site. So now we are talking about Kubernetes and then a bunch of other projects. And so now, it's like that whole journey from start to finish, what are the things that I need to be looking at and then, I think we are doing our best with CNCF, which is still a part of a playbook that we're looking to write in terms of how these projects work well together, what are some common use cases or challenges that these projects together can solve. >> So, Dee, we're here at the European show, you think back a few years ago it was a public cloud, there was very much adoption in North America, and starting to proliferate throughout the world. Alibaba is doing well in China and everything. CNCF now does 3 shows a year, you do North America, you do Europe and we've got the one coming up in China. We actually did a segment from our studio previewing the OpenStack Summit, and KubeCon show there, so maybe focus a little bit about Europe. Is there anything about this community and this environment that maybe might surprise people from your annual data? >> Yes, so if you look at... we have a tool called DevStart, it's open source, anyone can look at it, it's very simple to use, and based on that, we kind of monitor, what are the other countries that are active or, not just in terms of consuming, but who are actually contributing. So if you look at it, China is number 2, and therefore our strategy is to have a KubeCon in China. And then from a Euro perspective, I think the third leading country in terms of contributions would be Europe, and therefore, we have strategically figured out where do we want to host our KubeCon, and in terms of our overall strategy, we're pretty much anchoring to those 3 regions, which is North America, Europe as well as China. And, the other thing that we are also looking at is, we want to expand our growth in Europe as well, and now we have seen the excitement here at our KubeCon Barcelona, so we are looking to offer some new programs, or, I would say, new event types outside of KubeCon. Kind of you want to look at it as mini KubeCons, and so those would explore more in terms of different cities in Europe, different cities in other emerging markets as well. So that's still in the works. We're really excited to have, I would say 2 new event types that we're exploring, to really get the community to run and drive these events forward as well, outside of their participation in KubeCon because, oftentimes, I hear that a developer would love to be here, but due to other commitments, or, their not able to travel to Europe, so we really want to bring these events local to where they are, so that's essentially a plan for the next 5 years. >> It's fascinating hearing you describe this, because, everything you're saying aligns perfectly with what you'd expect from a typical company looking to wind up, building adoption, building footprints etc., Only, you're a foundation. Your fundamental goal at the end of it is user engagement, of people continuing to participate in the community, it doesn't turn into a 'and now, buy stuff', the only thing you have for sale here that I've noticed is a T-shirt, there's no... Okay, you also have other swag as well, not the important part of the story, I'm curious though, as far as, as you wind up putting all of this together, you have a corporate background yourself, was that a difficult transition to navigate, as far as, getting away from getting people to put money in towards something in the traditional sense, and more towards getting involved in a larger ecosystem and community. >> That was a big transition for me, just having worked on the classic B2B commercial software side, which is my background, and coming in here, I was just blown away with how people are volunteering their time and this is not where they're getting compensated for their time, it's purely based on passion, motivation and, when I've talked to some key community organizers or leaders who have done this for a while, one of the things that has had an impact on me is just the strong core values that the communities exhibit, and I think it's just based on that, the way they take a project and then they form a working group, and then there are special interest groups that get formed, and there is a whole process, actually, under the hood that takes a project from where Kubernetes was a few years ago, and where it is today, and I think it's just amazing to see that it's no longer corporate driven, but it's more how communities have come together, and it's also a great way to be here. Oftentimes... gone are the days where you try to set up a meeting, people look forward to being at KubeCon and this is where we actually get to meet face-to-face, so it's truly becoming a networking event as well, and to build these strong relationships. >> It goes even beyond just users, I mean, calling this a user conference would not... it would be doing it a bit of disservice. You have an expo hall full of companies that are more or less, in some cases, sworn enemies from one another, all coexisting peacefully, I have seen no fist-fights in the 2 days that we've been here, and it's fascinating watching a community effort get corporate decision makers and stakeholders involved in this, and it seems that everyone we've spoken to has been having a good time, everyone has been friendly, there's not that thousand yard stare where people are depressed that you see in so many other events, it's just something I've never experienced before. >> You know, that's a really amazing thing that I'm experiencing as well. And also, when we do these talks, we really make it a point to make sure that it's not a vendor pitch, and I'm not being the cop from CNCF policing everyone, and trying to tell them that, 'hey, you can't have a vendor pitch', but what I'm finding is, even vendors, just did a silverless talk with AWS, and he's a great speaker, and when he and I were working on the content, he in fact was, "you know, you're putting on that hat", and he's like, "I don't want to talk about AWS, I really want to make sure that we talk about the underlying technology, focusing on the projects, and then we can always build on top, the commercial aspect of it, and that's the job for the vendor. So, I think it's really great collaboration to see how even vendors put on the hat of saying, 'I'm not here to represent my products, or my thing', and of course they're here to source leads and stuff, but at the end of the day, the underlying common protocol that's already just established without having explicit guidelines saying, 'this is what you need to be following or doing', it's just like an implicit understanding. Everyone is here to promote the community, to work with the community, and again, I think I really want to emphasize on the point that people are very welcoming to this concept of a neutral home, and that really had helped with this implicit understanding of the communities knowing that it's not about a vendor pitch and you really want to think about a project or a technology and how to really use that project, and what are the use cases. >> It's very clear, that message has resonated well. >> Dee, thank you. We've covered a lot of ground, we want to give you the final word, anything else? We've covered the event, we've covered potential little things and the annual report. Any last words you have for us that you want people to take away? >> Not really, I think, like I said, it's the community that's doing the great work. CNCF has been the enabler to bring these communities together. We're also looking at creating a project journey it terms of how these projects come into CNCF, and how CNCF works with the communities, and how the project kind of goes through different stages. Yeah, so there are a lot of great things to come, and looking forward to it. >> Alright, well, Dee, thank you so much for all of the updates, and a big thank you, actually, to the whole CNCF team for all they've done to put this together. We really appreciate the partnership here. For Corey Quinn, I'm Stu Miniman. Back to wrap 2 days, live coverage, here at KubeCon, Cloud Native Con 2019, Thanks for watching the Cube. >> Thank you.

>> From Seattle. Washington. It's the key you covering Goob Khan and Cloud Native Con North America. Twenty eighteen. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partner. >> Okay. Welcome back. It runs the cubes. Live coverage of three days Wall to wall here at Koop Khan and Cloud Native Khan, twenty eighteen in Seattle, where day three only actions happening. Mr Keep John for was to Minuteman where you have bread. French Compton, Tina. Director, Technical Market had read, had breaking down the container storage trends and directions. Costly containers are super important. That's happened. Communities has happened. Now. New things were happening around a lot of innovation. Thanks for coming on the Q. Appreciate it. >> Thanks for having me back. >> So what's the state of the art of containers of trends? Some of the market directions? What's going on around containers? >> Well, here at this show, of course, it's been all about service mesh. Right is Theo. Service mesh, dynamically dynamic discovery, dynamic invocation of services. But all of those things Well, a certain percentage of those things, according to Keynote, require some type of persistent so eso yet service message, service meshes and persistence. >> So storage is a big part of the networking and compute all working together. The cloud that's been a big part of it. What's what's important here in this show? What's going on this week. That's really impacting that piece of it. That container in storage you mentioned state versus stateless work area stateless is to find people from persistence in state become important and applications. How much conversation's been here this week on that piece >> we'll talk about this week, and then I'll talk about the last couple of weeks this week. There, there. Couple of significant thing is going on. They're going to sort of unleash innovation in persistence as it pertains to the coup bernetti subsystem. First, of course, is a container storage inter. See, you know, today, all the all of the volume plug ins have been entry. You want to change. You know, some vendor wants to change their their storage capabilities. They need to re compile the binaries. Very slow. Very, very non agile. Of course, with the advent of the container storage interface, it's okay. Here's the common interface. All the all the volume plugging providers right to that interface so they could. Then they Khun Iterated to their heart's content without having to change the the entry >> source. So the impact is what? Speed, agility, >> agility of innovation, allowing all those guys t innovate Kind of the second thing. That's so that's man of discussion this week. Another thing's been a discussion you've seen in the in some of the sessions and stuff is the operator framework, you know, coming a champion by the Coral West guys, of course. Now part of Red hat, the operator framework in terms of effectively automating things that human operators would do for complex subsystems. Such a CZ storage. Eso basic installation based basic upgrades, you know, monitoring those services. So when you know something falls over, what do you do with that type of stuff? So I'd say C s I container storage interface as well as operator from me. Those are some of the things have been talked about this week. I still want to go back. Talk about last week, but go ahead. >> I wonder if you could tease this out a little before. So, you know, lost five years. You know, container ization, Cooper Netease. You know, massive change the way we think about architectures. Things like networking in storage. I have often been the anchor to kind of hold us down to be ableto make changes faster. Virtual ization helped some, but you know, container ization. We're gonna have to fix some of these same things. What conversations you're having with customers, You know, give us the latest on the, you know, the state versus state falls we heard in the keynote. It was They said forty percent of deployments have, you know, st full applications out there spending on numbers. And, you know, it's definitely has been growing. And at least I can do it as opposed to, you know, two years ago, it was like, Okay, we're doing containers, but we're just going to stateless for now, and we'll try to figure out what architectures goingto work. Even a year ago at this show, I heard in the back rooms there were lots of arguments as to which one of the storage projects was going to lead and seems seems like we're getting some maturity. I hope we hope to give us some visibility is where we are, and you know what's working and what still needs to be done. >> So although the industry talks about serve earless there, not yet talking about data lists, the or storage lists. I mean, you know, if we threw out the basic principle of data gravity data is the sun around which applications services rotate And so even I mean, even stateless aps stateless app Still do I owe frequently? The io of stateless apse is, you know, be arrest Will puts and gets to an object store that actually brings me. So let's let's talk about let's unpack the stateless and then let's go to St ful. So I'm gonna come back. Tio some of the conversations. A couple of weeks ago, Red had announced the acquisition of Nuba and Israeli Company. So when you think about what new Bob Plus sef due to provide stateless aps with a common set of Davis, a common set of David data services across the hybrid and multi cloud so those stateless app saying, Okay, I'm going to do I'm going to rest well puts and gets. But, man, it's complicated. If I'm gonna have to develop to various proprietary protocols I've got, you know, the is your blob protocol. I've got a W. S s three. I'm talking Teo Google persistent disc. And then if I want to run hybrid, I'm also talking to SEF objects storage on premises. And if I'm a developer I'm thinking, man, Wouldn't it be nice if I had a common set of David data services, including common protocol to talkto all of those different cloud storage back end? So, Nuba some people kind of call it a cloud storage controller provides that kind of common data services. So things like common FBI protocol? Um, things like mirroring. So you you want to write, right Once you're uprights once and it smeared across the various cloud object storage back ends to facilitate easy migration. The second one I wanna uproot to move over here. Your data is already there. So that's, uh that's a couple of reasons. And some of the conversation from a couple weeks ago about how Nuba plus self are helping stateless aps get Teo hybrid and multi cloud >> this. I think that is a great point. You have a hybrid cloud and multi cloud coming around the corner, which is about choice, Right? But see, I CD pipe lining of having a consistent developer environment clearly is one of the main benefits we're seeing in this community here. Okay, I got some sulfur developers with crank teams move around that consistency, no matter where were the environment is just really good goodness. Their storage is interesting and data is that because you're right, the sun is the data and every is orbiting around it. That's the Holy Grail. This is what people want. They want addressable data. They wanted real time. They wanna have an access. They don't want to do all this code to configure manage data, and it's complicate. Got data warehouses? You got time. Siri's data so date is getting more complicated, but it needs to be simple. So this is kind of challenge of the industry. How are you guys seeing that with open ship? How is your container piece fit in? How do you guys make that easy for customers to say? Look, I want to have that data like I wanted intelligent, that brick of access to data. So my abs don't have to do all the heavy lifting almost like Dev ops for data. It's like day tops, like I need to have programmable data on the absolutely which, which have thoughts on that. >> So first I wanna I wanna address that in two ways. The first is about open shipped itself that what you described is in fact, the sweet spot of what open shift is providing a common set of Cooper Nettie Services. Plus. See, I see the pipeline services for developers and operation staff independent of your cloud infrastructures. So whether open shift is running on top of a heavy west, whether it's running on top of his your whether it's running on top of the G, C. P. Whether it's running on premises on bare metal, you know, common set of cou bernetti services and CD pipeline services. Okay, that so what you described there's wanted to just highlight that That is open ship hybrid multi >> valuable check. That's awesome data >> now coming down. Coming down to data. So, in fact, open shift container storage is the mirror analog to open shift for that, providing a common set of Cooper Netease volume services. Independent of what? The storage substrate. ID. So think about it. If you're If you're inside of eight of us, you've got CBS is what's you know? When in Rome, act as the Romans. You've got E. B s there when you're inside of eight of us. Well, the type of communities volumes service of the CBS provides natively differed them for instance, when you're on premises and it's surfacing via and NFS plug in, maybe different. Likewise. We're inside of a CZ. You're with your persistent disco, so open shift container storage device the same type of abstraction Lee are providing a common set of cou bernetti communities volumes services independent of what? The storage server layer is so >> cool you guys was tracked away the complexity. So the APP developer doesn't do anything about storage on those discreet platforms, >> doesn't know anything about storage and provides a common set of services instead of Well, let's see, this is running on this cloud. I don't have the have a different set of services, so common set of services. >> So one of things I love about talking right out of the shows is you actually have a lot of customers that are doing this way. Actually, we spoke to one of your customers yesterday. Talk about how you know communities is helping them create sustainable data centers over in Europe. In the Nordics, especially so communities is awesome. But what's really awesome is the things that we can do on top of it. I wonder if you've got, you know, help connect some of this toe. You know, your customers really things, you know? How does this, you know, change the game? How does it change their teams? You know, what can you share with us? >> One of things that I can't. What's what's top of mind. So what's not top of mind for me at the moment is you know what kind of knew how their reinventing the world what is top of mind with me right now? We've just been studying. Our our results is we look back and this is a little bit of a A Okay? It's a trend, but it's a different kind of friend you're talking about. In the last six quarters, we've had six hundred percent growth with open ship container storage. Um, so And now we send last six quarters were also at a point. Now we're seeing some of those same folks from the Nordics here. You're describing that are coming back now, you know, they have experimented on, So there are some There are Cem Cem cruise ship. There's a cruise ship company that is deployed this on on ships. What we're now seeing. What's very gratifying for us is they're coming back now for a second pass. Now, a year into it, it's okay. Clearly, it must be providing enough value that you come back. Okay. I want to buy this for another ship or more shifts. That's gratifying for us. The first year was, let's see. Let's try this uber Netease, this open ship container store stuff out. But, you know, coming back to the trough for another take, It's good for us. >> And what's going around the corner? He opens shifting, doing great. I love this abstraction layer we're seeing for the first time in the industry, clear visibility and a real value proposition. When I were joking yesterday, you know, we were at open stack years ago, or even Cube con three years ago. We would ask the question If you had a magic wand, what would you hope to have happened? It's actually some of the things that are actually happening. I mean, clean, heavy lifting is gone, and all the developer side consistency, productivity, better advantage on the application development side and then taking away all the hassles of having that she trained people on multiple clouds. So this is kind of happening. What's next? So what's the next next, uh, bowling pin to fall down? What's the, you know, Hit the front ten. What's next? What's going on? How do you guys see the next innovation around Open ship and storage containers, >> cloud independent data services and mobility. So independent of the clouds. And again, it's hybrid, too. So you don't want to be locked into your own cloud either. So cloud independent data services and mobility. So he said, Listen, I want to be I want to have a common de doop compression mirroring, but I want to sit in the layer above my clouds back to the data gravity thing. I want to ensure that my data is where I need it on different clouds. So I'm elevating to a new layer this this cloud storage controller, this this cloud independent set of data services way. Think that's where the pucks going? >> Yeah, I think the data date is critical, I think. Way said years ago. Data ops. There's a Dev ops model for data. You look at that way's not just putting into a data lake actually making it useful. Yeah, Thanks. Come on. Cuba. Here. Bringing all the data here. The Cube. We're sharing it here. Live in Seattle. Is our third year coop coming there from the beginning? That's the cubes coverage of Cloud Native Khan and Coop gone. Bring all the action here. Was red hot on the Cube. Back with more live coverage. Stay with us. Day three, three days ago off the wall. Coverage will be back after this short break.

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

>> Announcer: Live from Copenhagen, Denmark, it's the CUBE, covering KubeCon and Cloud Native Con Europe 2018. Brought to you by the Cloud Native Computing Foundation and its ecosystem partners. (busy music) >> Welcome back, everyone, live here in Copenhagen, Denmark, it's the CUBE's coverage of KubeCon 2018. I'm John Furrier, the host of the CUBE, along with Lauren Cooney, who's the founder of Spark Labs. She's been co-host with me two days, two days of wall to wall coverage. Stephan Fabel, Product Strategy Lead at Canonical, is here inside the CUBE, and from San Francisco. Again, welcome to the CUBE, thanks for coming. >> Thank you, thanks so much for having me. >> I've got to, you guys have been around the block, you know about open source software platforms, you get and do it for a while. Interesting time here at KubeCon. Kubernetes, Istio, Kubeflow, Cloud Native, they've still got the brand name CloudNativeCon and KubeCon. Modern application architecture's now in play. I see this notion of an interoperability model coming in that's certainly going to be a de facto standard. People are already kind of declaring it a de facto standard. It really shows a path to multi-cloud, but also frees up developers from a lot of the heavy lifting. Lou Tucker from Cisco was saying they don't want to do networking. Let's just have that be infrastructure as code, that's DevOps, that's what we want. >> Stephan: That is exactly right. >> What are you guys doing here? What's the story with Canonical and how does that fit into the megatrends? >> Yeah, I mean, there's a couple of things that we at Canonical always believe to be one of the core sort of tenets in our distribution of Kubernetes. As you know, we've been very active in this space fairly early on, and have been an active distributor of Kubernetes and a certified distributor of our version of Kubernetes. Pure upstream, remain conformant to the main public clouds, such as to enable that workload migration and mobility from on prem up to any of the other providers to accommodate all kinds of use cases, right. >> You guys made a bet on Kubernetes, obviously, good call. >> Stephan: Right. >> Right. What's the progress now, what's next? Because that's, the bets are paying off. I saw Red Hat had a great bet with what they did with Kubernetes, changed what OpenShift became. You guys had a bet in Kubernetes, what has that become for Canonical? >> Yeah, so based on the pure upstream distribution that we have, we really feel that enabling the ecosystem in a standards compliant way so that all of the landscape projects that are part of the CNCF can be deployed on top of Kubernetes, on top of our distribution of Kubernetes in just the same way that they would be developed or deployed in any of the large containers of service offerings that are out there is one of the big benefits that our customers would gain from using our Kubernetes. >> What's your differentiator for the distribution of Kubernetes that you have versus others? >> Well, there's two. The first one, I think, is the notion that deploying Kubernetes on premise is something that you want to do in a repeatable fashion, operationally efficient with the right capex opex mix, so we believe that there is a place for Kubernetes as a product, just deploy it, it works on any substrate that you've got available to you. But then also, for mainstream America, right, you may want to have a managed service on top of Kubernetes as well. We offer that, too, just a way to get started and kick the tires and see where that takes you as far as the developers are concerned. Now, on prem, you will find that there are a couple of challenges when deploying Kubernetes that are really the key differentiator. The first one, I would say, is things like integration into the storage that's local, integration into the network that's local, and integration into all of those services that should be available in the Cloud Native microservices architecture platform, such as low bouncers, right, elasticity, object store, etc. The second, and most importantly, because it is a key enabler for those next generation workloads, is the GPGPU enablement work that we're doing with partners such as NVIDIA. When you deploy the Canonical distribution of Kubernetes, you actually get the NVIDIA acceleration out of the box the way that NVIDIA envisions this on top of Kubernetes and the way that it is, by the way, being deployed on the public clouds. >> You bring a lot of your goodness to the table inside the Kubernetes distribution. OK, what are some customers doing? Give some use cases of some customers' Kubernetes, what are some of the things that they're doing with it, what's the early indication? What's the feedback? >> Sure. We have a ton of customers that are using our version of Kubernetes to do the machine learning applications and the AI of the next gen workloads in use cases such as smart cities or connected cars, where, when you look at self-driving cars, right, as the next gen that's coming out of the valley, they put in 300,000, 150,000, 400,000 miles a year on the road these days just optimizing the models that are being used to actually take over one day. Enabling those kinds of workloads in a distributed fashion requires DevOps expertise. Now, the people who are actually writing those applications are not DevOps people, they're data scientists, right. They shouldn't have to learn how to deploy Kubernetes, how to create a container and all those things. They should just be able to deploy the application on top an attractive substrate that actually supports that distributed application use case, and so that is where we come in. >> This is interesting, because what you're basically doing is making an application developer a DevOps developer overnight. >> Stephan: That's exactly right. >> That's really important. I was just talking with the co-chair of CNCF. We're talking about, Liz Rice and I were talking about why everyone's so, like, excited here. One of the things I said was, because people who are doing DevOps were hardcore, and they had to build everything from scratch, and all the scar tissue. But the benefits, once you got through the knothole there, the benefits were amazing, right. You go, okay, you don't want to do that again, but now there's a way to make it easier. There's kind of a shared experience even though no one's met each other, so there's kind of a joint community. >> I agree. I think it is increasingly about enabling developers who are experts in their field to actually leverage Kubernetes and the advantages that it brings in a more intuitive fashion. Just take it up a notch. >> How did the Kubernetes vibe integrate in with Canonical? I'm sure, given the background of the company, it probably was a nice fit, people embraced it. You guys were early. >> Stephan: Yeah. >> What's the internal scuttlebutt on the vibe with Kubernetes? >> Oh, we love Kubernetes as a technology. Ubuntu was always close to the developer and close to where the innovation happens. It was a natural fit to actually support all that workflow now in this new world of Kubernetes. We embraced OpenStack for the same reason, and in a similar fashion, Kubernetes has really driven the point home, containerist applications with a powerful orchestration framework such as Kubernetes are the next step for all the developers that are out there, and so as a consequence, this was a perfect match. >> It's also a no-brainer if you think about it, software methodology moving to the next level. This is total step up function for productivity for developers. That's really a key thing. What's your observation of that trend? Because at the end of the day, there's now Kubernetes, which does a lot of great things, but one of the hottest areas is Istio service meshes, and then you've got Kubeflow orchestration, a lot of other things that are happening around Kubernetes. What are you guys seeing that's important for Canonical's customers, what you're doing product wise. Where's the order of operations, what's next? What are you guys focused on, what's the priorities? >> Well, our biggest priority right now is enabling things like Kubeflow, which, by the way, are also using Istio internally, right, to actually enable those data scientists who actually deploy their I workload. We work very closely with Google to try and enable this in an on prem fashion out of the box which is something you can actually do today. >> John: You guys are doing this now inside this. >> We're doing this right now. This is also where we're going to double and triple down. >> This is actually your best practice, too, if you think about it, you want to take it in house, and then get a feel for it. What's the internal vibe on that, positive? >> Oh, absolutely. I mean, we always saw infrastructure as code and actually as intelligent infrastructure as something that we wanted to build our conceptual framework around, so very concretely, right. We've always had this notion of composable building blocks adding up to, sum of one being greater than two, right, like those types of scenarios. Actually using things like Kubernetes as an effective building block to then build out web applications that use things like machine learning algorithms underneath, that's a perfect use case for a next gen workload, and also something that we might use ourselves internally. >> Well, hey, that whole building block thing, it's happening. >> Stephan: Yeah. >> News flash. >> Stephan: Exactly, right? >> I mean, it's almost a pinch me moment for the people in the industry like, oh my god, it's going to go to a whole other level. How do you guys envision that next level going? Beyond the building blocks, is it, I mean, what's the vision that you guys have? Obviously, infrastructure as code programmability, but now, you're talking about infrastructure as code was great, but now you've got microservices growth coming on top of it, it's a services market now. >> It is, it is. I think that the biggest challenge will be the distribution of the workloads, right. You have edge compute coming along in the telco space, you have, like I said, smart cities, right, the sensors will be everywhere, and they will feed data back, and how do you manage that at scale, right? How do you manage that across various different hardware perspectives? We have hardware platforms such as ARM 64 picking up, right, and actually playing a very significant role at the edge, and increasingly, even in the core. We've always believed that providing that software and the distribution of IS such as Kubernetes and others on top of those additional architectures would make a huge difference, and that is clearly paying off. What we see is, the increased need of managing hybrid workloads across multi-cloud scenarios that could be composed of different architectures, not just x86, the future is not homogeneous at all. It'll be all over the place. All those use cases and all those particular situation require that building block principle, like all the way from the OS up to the application. >> John: That's a great use case for containers. Kubernetes, Istio, Kubeflow. >> Absolutely. >> All stacking in line beautifully from an evolution standpoint. I've got to ask you a personal question. I mean, I was at Canonical, great company, I want to thank Canonical for being a sponsor of the CUBE over the years. We've had Mark Shuttleworth on the CUBE had an OpenStack going way back when. You guys are a great participant in the community as a company and the people there been phenomenal. You're new. >> I'm new. >> What attracted you to Canonical? What was the motivating force? What drew you in? You're now running Products, a big job. You've got a lot in front of you. Obviously, it's a great market, so you're a great company. Just share, just color and why Canonical, what attracted you there? >> I've always been a user of Ubuntu, I've been a user since the first hour. I've used Ubuntu in my research. I did robotics based on Ubuntu way before it was cool. I built all kinds of things on top of Ubuntu throughout my entire career. Working for Canonical, which is a company that always exhibited great vision into the future and great predictions into trends that would prove to become true was just, for me, something that was very attractive. >> Their leadership has a good eye on the prize. They had good 20 mile stare, as we say, they can see the roadmap ahead and then make either course corrections or tweaks. >> Yeah. >> Great, awesome. Well, I mean, what's new there? What's your, take a minute to explain what's new at Canonical, role here at KubeCon, what are some of the conversations you're having? >> Yeah, so I mean, for us at KubeCon, it's always been an important part of our outreach to the community, great opportunity for us to have great conversations with our partners in the field. I think it is really about enabling the ecosystem in a more straightforward way. There's no better place to have those types of conversations than here, where everybody comes together and really establishes those relationships. For us, it is about, again, enabling the developer and really staying close to that innovation and supporting that in an optimal way. Yes, I mean, that, to us, is the role that we play. You've got a lot of end users here who are building stuff. >> Oh, absolutely, yeah. They, I mean, I had a talk today about Kubeflow with Google, and after the talk, lots of folks came up to me and said, hey, how can I use this at home, right? >> Sometimes with, whether it's timing, technology, all the above, Kubernetes really hit it strong with the timing, industry was ready for it. Containers had a nice gestation period. People know about containers. >> Stephan: Absolutely. >> Engineers know containers, know about those kinds of concepts. Now we're at a whole other operating environment. >> Stephan: Absolutely. >> You guys are at the forefront. Thanks for coming on the CUBE. >> Oh, thank you, I appreciate it. >> Stephan sharing the perspective, Stephan Fabel. Running Product and Strategy for Canonical, building stuff, this is what's going on in Kubernetes in KubeCon, end users are actually building and orchestrating workloads. Multi-cloud is what people are talking about and the tech to make it happen is here. I'm John Furrier with the CUBE. Stay with us for more live coverage here at KubeCon 2018, part of the CNCF CUBE coverage. We'll be right back after this short break. (busy music)

>> Narrator: Live, from Copenhagen, Denmark, it's theCube. Covering KubeCon and Cloud Native Con Europe 2018. Brought to you by the Cloud Native Computing Foundation and its ecosystem partners. >> Hello, everyone, welcome back to theCUBE exclusive coverage of CNCF. The Cloud Native Foundation, Compute Foundation, part of the Linux Foundation of KubeCon 2018 here in Copenhagen, Denmark. I'm John Furrier co-host of theCUBE here with analyst this week Lauren Cooney, who is the founder of Spark Labs, brand new start up that she founded to help companies bring innovation to Cloud Native, bring in all of her expertise to companies. Also, here on theCUBE, Lauren, great to have you this week. >> Thanks, John. >> Here in Europe, you've done so much work in the area of open source over the years. You've done, you were radical renegade, progressive, pushing PHP, bringing that to Microsoft. Doing a lot of great things, and now we're in a new modern era, and you're bringing that expertise, but you're also on the front lines of the new wave. >> Lauren: Definitely. >> Cloud Native, so what's your take? What's your analysis? I mean, there's so much going on. You can't just retrofit old school open source, but it's got to build on the next generation. What's your thoughts? >> It has to build on the next generation, but you also have to look back at what has happened in the past. I think what is incredibly important to see is the mistakes that have been made in the past, so that people don't repeat them. One of the things that I'm seeing here and hearing a lot about is multiple distributions of Kubernetes out there, and when I hear multiple distributions I get worried that they're going the open sack route and there is going to be too many distributions out there. I would rather see one or two standard become kind of more standard and people building on top of that. I think it's the right way to go versus the splintering of the community. If the community is going to stay together you're going to have to narrow that down. >> What's the rationale for the distribution? Because, we've seen this before. Certainly at Hadoop, we saw people come out with distros and then abandon them, and then people coalesce around. >> Oh, they'll just die on the vine. I mean, fundamentally they just will die on the vine. It won't be, if it's not de facto already you're probably not going to get it de facto. >> John: What should companies do? Should they have a distro down. >> They should map to one of the key distros right now. They should, basically, use what is out there already. The one that they feel is right, and for their users, and for their company long term. >> I really enjoyed a couple of interviews we had yesterday. I want to just kind of revisit a couple of them. Tyler and Dirk, we had Tyler on from the new programming language ballerina that was launched. He's part of WSO2. Dirk is from Vien, where former early Linux guy, Linux foundation guy, worked with Linux tarballs in the early days. These guys know up the source. So you look at some of those leaders, and they say, "Hey, this is about the people" What are the things that we can draw from the past that are still relevant today? As the new formula of Kubernetes horizontally scalable cloud, Cloud Native thousands and, potentially, millions of micro-services coming online, new kinds of dynamic policy based infrastructure software, everything's coming. >> Service mesh, can't forget service mesh. >> Service meshes are going to be huge. What do we have to keep and preserve, and what is being built out that's new? >> Well, I think that you need to preserve the feeling of the community and what's going on there. I mean, these communities, actually it's communities not community, and these folks are coming along for the wave right? And I think it's important to make sure that people are aware of that, and there's lots of different personalities and lots of different goodness that can be brought to the table with that and the recognition of that. I also think that, for the most part, I do believe that this is one of the strongest communities out there, and it will continue to be for a number of years. >> I want to get your thoughts on something Ed Warnicke said from Cisco because he was very complimentary of the CNCF as are other people, and we have been complimentary as well about keeping everything tight to the core and allowing people to innovate. So you have, and we have commented on theCUBE and other KubeCons about this, and they've been doing it, which is let the innovation foster on the technical side as well as let people flex their business model opportunities. >> Lauren: Definitely. >> Not so much just for the sake of commercialization because if you have too much commercialization you might stunt the community of growth organically so there's a balance, and I think CNCF has done a good job there, but they've kept the core of Kubernetes really tight which has allowed the de facto standard approach to be Kubernetes. That has created great opportunity, and people are super excited by that. What's your analysis of what happens next? What needs to happen? What's the momentum phase two of this? >> I think part of it is, how do you monetize, right? It's looking at, and this is part of what Spark Labs actually does, is we actually work with companies, some that are in the CNCF, and we work on them in different ways to monetize. Is it a services wrapper that's going to work? Is it additional features or functionality? The innovation comes with the technology, but with that technology you have to have the business model kind of in mind when you're building this out so you can figure out how to make money. As these smaller companies especially are looking to do and some of the bigger companies as well. >> I really think it's important for the CNCF and the Linux foundation and I know they're on this so its not critical analysis so much as it is more of an observation. You have a long tail of start ups and kind of a fat tail if you will, that are out there, and you have the big whales out there Google, Microsoft, Amazon, and others at the top. There was a comment in Austin, a snarky comment. I won't say by who, but I was looking at the logo board of the sponsors, and the guy said, "All those start-ups, they might be dead in 18 months" and it made me pause and say okay, that's an observation because they were brand new companies. >> Lauren: Mm hmm. >> That can't happen. We need to have a model of preservation for start-ups to experiment, to grow. This is something you're doing at Spark Labs so what's your view of this? And, reaction to the fact that this has to happen. What can we do as an industry and community to make sure the start ups-- >> I think the Linux foundation is doing one of the best things that can be done out there. Other open source foundations do too. Is they create the infrastructure so that folks have the support for marketing, or legal, or something along those lines, but so companies are allowed to innovate and then the Linux Foundation basically bets on the innovation and they bet on multiple innovations with multiple companies so they allow these companies to thrive while giving them the support inside of that. >> John: Yeah. >> And I think that's really helping a lot of these companies along. >> Well, Dave Collins always says is the membership organization, so no members no business model so I mean they're incented to make sure that, or hope, that these guys can survive, and certainly there's going to be some misfires and people will natural evolution. So what are you most excited about? I got to ask ya, I mean you're out on your own now. Congratulations, you started up. >> Thank you. >> Super exciting for you and I'm happy that you're going to go out on your own. What are some of the things you're excited about? What are you digging your teeth into, in terms of projects? Share what you're doing. >> I'm super excited about these companies that are coming out with true multi-cloud. So, allowing applications to run across multiple environments, public, private, et cetera. And we've been saying we can do it for a decade or something like that, but fundamentally that wasn't the case. You did have to re-write code. You did have to do a lot of underlying things to make that occur. One of the things that I'm super excited about is being able to take those companies and figure out how to actually get their product to market faster. Some of these guys are still in stealth. They need to move really fast if they want to catch up. I also love working with them on figuring out how to build out their teams, figuring out how to monetize. What are the next steps? What are the business plans, really, behind this? What is the one, three, five year model that they're going to use? I also love helping them get the money, of course. I think that's the fun part too. >> Yeah, it's always fun. Start-ups are great. What I'm excited about, I got to tell ya, I got to share with you just some personal feelings. I love this market right now because I've seen many waves of innovation and I think this wave of cloud native, whatever you want to call it this massive wave or sets of waves coming in and you got blockchain and other things going on behind it these centralized applications which I think is part of this set coming in, is that it's bigger than all the other waves combined and because there's so much value creation on the horizon and I think historically, this moment in time, historically is going to be a point we're going to look back and say the Kubernetes de facto standard galvanized a set of industry, a new card of players who are going to establish a new way methodology of doing things, and we're documenting it. Secondly, the role of community, as you pointed out, is so important here, and it's strong, but now we're living in a new age of digital. We're seeing formations of new kinds of community engagement digitally, not just the events, so I'm excited with theCUBE and what we're doing here, and what the Linux Foundation is doing because there's now going to be, potentially, exponential growth and acceleration around the combination of community. >> Yup. >> The community growth with this new modern commercialization on digital. >> It's definitely increasingly important, and you have to look at it from the technologies making it happen. The technology is looking at, edge computing is going to make digital happen really when you look at all the end points and things along those lines. And, I think that it's going to be great for everyone involved in that. >> Yeah, and we can learn a lot from looking at the Facebook example of how fake news swayed the election. How people were weaponizing content for bad things. There's also an opposite effect, we believe that you can do the for good. >> Lauren: Totally agree. >> I think digital will have a big role in the next generation community formations, community growth, short cuts to the truth, really that's what it's all about. It's about the people, so certainly we're going to be documenting it. Thanks for your commentary. >> Lauren: Definitely. >> Appreciate it, great to work with you this week. Day two of exclusive coverage, here at the Linux Foundation's Cloud Native Compute Foundation's, CNCF's KubeCon 2018. This is where Kubernetes, service mesh, Istio a lot of great projects, from a lot of smart people. We're here on the ground covering it live. Day two, we'll be back with more coverage. Stay with us for day two coverage, after this short break. (electronic music)

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