>> Announcer: From Boston, Massachusetts, it's theCUBE! Covering Cloud Foundry Summit 2018. Brought to you by the Cloud Foundry Foundation. >> I'm Stu Minamin and this is theCUBE's coverage of Cloud Foundry Summit 2018. Here in beautiful Boston, Massachusetts. Happy to welcome back to the program Chip Childers, who is the CTO of the Cloud Foundry Foundation. Chip, you started off this morning saying the runners this morning got a taste of the Boston Marathon. >> They did, they did! >> It's raining, it's cold, it's miserable. >> Yesterday was beautiful. >> At least there was less wind. >> Yesterday was absolutely beautiful. So we kicked off the summit, beautiful sun, but then we had our Fun Run this morning. >> As a local, I do apologize for the weather. Normally April's a great time. We want more tech coverage here in the area. More tech shows. We're in the center of a great tech hub, here in the Boston Seaport. We've talked to a couple of Boston startups, you know, here at the show. And, you know, great ecosystem if you go there. Thank you for bringing your show here. >> Absolutely, happy to be here. >> All right, so, last time we caught up was year ago at the show. And I think it was, what, 213 working days or something? I think Molly said >> Something like that Something like that yeah. >> The good thing is in our industry, nothings changing, we can talk about the same stuff as last year. >> Leisurely pace >> No concern, let's just sit back and you know, talk about our favorite pop culture references. Chip what's hot on your plate? And what are you hearing from the users in the community? >> Sure. So this year the theme Our events team came up with a very fun pun, which is Running at Scale. It means two things. One, the Boston Marathon was on Monday, but two it really does represent the stories that we're getting from our users, the customers, and the distributions, those that use the open source directly. So not only are we seeing a broadening of adoption across new organizations, but they're getting really deep into using it. We filled a survey, user survey, just did our second run of it. In fact we didn't have this data back in Santa Clara last year. So it's been less than a year since the 2017 one. And what we found was that there was a 21 point swing in those companies that were using Cloud Foundry with more than 50 developers, alright. So 50 developers and higher When you really talk to the interesting, large scale Fortune 500 companies, they're talking thousands of developers, that are working on the platform, being productive, and that truly is kind of what this event is about for us. >> I grew up around the infrastructure stuff, and scale means a lot of things to a lot of people, but had a great discussion with Dr. Nick, just before talking about how if you were to build your kind of utopian environment You look at some of the hyper-scale companies, the Facebooks and Googles of the world, and thing is they're such a scale that if they don't have good automation, and don't have you know really the distributive architectures that we're all talking about and things like that, there's no way that they could run their businesses. >> Yeah and the reality is a lot of the businesses that aren't Google, aren't Facebook, they have to be able to think about that level of scale. To me it really boils down to three basic principles, and to me this is the best definition of what Cloud native means. Whether you're talking about a platform, whether you're talking about how you design your applications, it's simple patterns, highly automated, which can be scaled with ease, right? And through that you can do really amazing things with software, but it has to be easily scaled, it has be easily managed, and you do that through the simplicity of the patterns that you apply. >> Yeah, and being simple is difficult. >> Yes >> How much we have arguments in the industry it's like well, let's throw an abstraction layer in there, do an overlay or underlay, but you know really building kind of distributed systems, is a little bit different. >> It is a little bit different. So one of the things that the Cloud Foundry ecosystem has, is a rich history of iterating towards a better and better developer experience. At its heart, the Cloud Foundry ecosystem of distribution, and tools, and the different products we have, they're all about helping the developer be a better developer in the context of their organization. So we've been iterating on that experience and just doing incremental constant improvement and change and we're very proud of that productivity, right? And that's really what drive these organizations to say look, this is a platform that is operated very easily with small teams. I think you've spoken with a couple companies, and if you ever ask them hot many operators do you have to handle thousands of engineers, tens of thousands of applications, they say, well, maybe ten. >> The T-Mobile example is >> Great example >> Ten to fifteen operators with 17000 developers so >> Chip: Yep, yep >> It's funny cause I remember we used to talk about you know in the enterprise how many servers can a single admin handle and then if you go to the hyper-scale ones it was three orders magnitude different. But in the hyper-scale ones they didn't really have server people, they had people that brought in servers, and people threw them in the wood chipper when they were done >> Chip: Absolutely >> And they didn't manage them. It was the old cattle versus pets analogy that we talked about in the other room, It's just totally different mindsets is how we think about this. I love, For me, it was in the enterprise you know, we harden the hardware, we think about this, and in the software world it's you know, No no, I built it in the application layer, because One of my favorite lines I use is you know, Hardware will eventually fail, and software will eventually work right? >> Absolutely. I think that's the difference between, So application centric thinking leads you to Necessarily, you have to have infrastructure to run it right? My favorite thing is this whole server-less term is absolutely ridiculous if anybody understands it, but there's a little bit behind it, which is, in fact I'd argue Cloud Foundry's fundamentally server-less because when you push code into it, you don't care what operating system's underneath it, right? All you care about is the fact that you've written some code in Java or in Nojass or in Ruby, you're handing it to a platform it deals with all of the details of building a container image, scaling it, managing it, pulling independencies, you don't care what underlying operating systems there, and then that ten person platform operations team, in the Cloud Foundry world, they have the benefit of upstream projects actually producing the operating system image that they can consume, within hours of major vulnerabilities being announced. >> I love actually, at this show you've got a containers and server-less track >> We do >> And I'm an infrastructure guy by background and when we went to virtualization we went little bit up the stack, I don't think about servers I'm trying to get closer to that application. Love you to comment on is Cloud Foundry helps gives some stability and control at that infrastructure level, but it still involved with infrastructure, from in my own data center, >> Chip: Yep >> or hosted data center or I know what could I'm on. When I start going up to like server-less, I'm a little bit higher up the stack, and that's why they can live together, >> Yeah, yeah >> And its closer tied to the application than it is to the infrastructure, so maybe you can tease that out for us a little. >> Yeah, so I think one of the main things that we've heard from the user community and this is actually coming from users of a number of the different distributions. They're saying, look there are roughly, today, roughly two different modes that we care about, cloud native application workloads. And this might expand to include functions and service but predominantly there's two. There's the custom software that we write, which the past experience is great for, and then there's the ISV delivered software, which today increasingly the medium of software delivery is becoming the container image, whether it's an OCI container, whether it's a Docker image, ISV ships software as container images, and you need a great place to land that, so those two abstractions, that paths, just hand the system your code, or the container service just hand it a container image, both of them work really well together, and part of what we're trying to do as a community, a technical community, is we're evolving those integrations so that we can work really well with the Kubernetes ecosystem. There are different options for how these things might be stacked, depending on the vendor that you're talking to, I think mostly that's immaterial to the customers, I think mostly the customers care about having those two experiences be unified from their developer or app owner prospective. >> When you come to this show, there's more than just Cloud Foundry. There's a lot of other projects >> Chip: For sure >> That are coming on to the space Gives us a little viewpoint as to how the foundation looks at this. What's the charter which it fits under Linux foundation There's so many different pieces, Some kind of bleed into what the CNCF is doing, and just try to help map out >> Chip: Yeah how some of these pieces and it's this great toolbox that we've talked about in open source. I love like the zip car guy got up and he's like, I use all the peripheral stuff, and none of the core stuff >> Right >> And that's okay >> Absolutely, that's the fun of open source. So there's a couple ways to look at this. So first, the open source communities collectively. There's a lot of innovations going on in this space, obviously What the Cloud Foundry ecosystem generally does, historically has done, and will continue to do, is that we are focused on the user needs, first and foremost. And what our technical project teams do is they look at what's available in the broader open source ecosystem. They adopt and integrate what makes sense, where we have to build something ourselves, simply because there isn't an equivalent, or it's necessary for technical reasons. We'll build that software. But our architecture has changed many times. In fact, since 2015, right. It hasn't been that many years, as you said, we move slow in this industry (Stu laughs) We've changed this architecture constantly. The upstream projects releasing at minimum of twice a month. That's a pretty high velocity. And it's a big coordinated release. So we're going to continue to evolve the architecture, to bring in new components, this is where CNCF relates. We've integrated Envoy, which is a CNCF project. We're now bringing in Kubernetes, in a couple of different ways. We're working closely with Istio, which is not a CNCF project, yet. But it looks like it might head that way. Service mesh capabilities, We were an early adopter of the container networking interface. Another Linux foundation effort was the open container initiative, right. Seeded from some code from Docker, again one of the earliest platforms to adopt that, outside of Docker. So we really look at the entire spectrum of open source software as a rich market of componentry that can be brought together. And we bring it together so that all these great users that you're talking to, can go along this journey, and think of it almost as a rationalization of the innovative chaos that's occurring. So we rationalize that. Our job is to rationalize our distributions, use that rationalization, and then all of the users get to take advantage of new things that come up. But also we take what gets integrated very seriously, because it has to reach a point of maturity. T-Mobile again, running their whole business on Cloud Foundry. Comcast, running their whole business on Cloud Foundry. US Air Force, fundamentally running their air traffic control, right, how do they get fuel to the jets, on Cloud Foundry. So we take that seriously. And so it's this combination of, harvesting innovation from where we can harvest it, bring it all together, be very thoughtful about how we bring it together, and then the distributions get the advantage of saying, here's a stable core that's going to evolve and take us into the future. >> Chip I've loved the discussion with real customers, doing digital transformation. What that means for them. How they're moving their business forward. Want to give you the final word, for those that couldn't come to the show, I know a lot of the stuffs online, there's a lot of information out there, anything particular do you want to call out, or say hey this is cool, interesting, or exciting you that you'd want to point to. >> Yeah, I actually. There are a lot of things but the one thing that I'll point to is as a US citizen, I'm particularly proud of some of the work that's happening in the US Government. Through 18F, with cloud.gov as an example, but if I step back even further, Cloud Foundry is serving as a vehicle for collaboration across multiple nations right now. We're seeing Australia, we're seeing the United Kingdom, Netherlands, Canada, South Korea, all of these national governments, are trying to figure out how to change citizen engagement to follow the lead of the startups, which are the internet companies, at the same time that these large Fortune 500 companies, are also trying to digitally transform. Governments are trying to do the same thing. So we had a, we're almost done for the day here, but there was almost a full day track of governments talking about their use of the tech, talking about that same digital transformation journey. So to me that's actually really inspiring to see that happen >> Alright well Chip Childers. He was a dancing stick figure >> Chip: I was in the keynote this morning, but here with us on theCUBE. Thank you so much for joining once again, and thank you to the foundation for helping us bring this program to our audience. >> Chip: We're happy to have you here. >> I'm Stu Miniman, and this is theCUBE. Thanks for watching (bright popping music)