>> 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)

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

>> Narrator: Live from Santa Clara, in the heart of Silicon Valley it's The Cube, covering Cloud Foundry Summit 2017. Brought to you by the Cloud Foundry Foundation and Pivotal. >> Hi, I'm Stu Miniman and welcome to Silicon Angle Media's production of The Cube, worldwide leader in live tech coverage, here at the Cloud Foundry Summit. We're in Santa Clara, California. Happy to have my cohost for a day of coverage, John Troyer. John, great to see ya. >> Glad to be here, Stu. >> So, we were reflecting back. The Cloud Foundry Summit has been going on for a few years. Last time I went to it in person, was I believe three years ago in San Francisco. It was actually the same year as the first DockerCon but reflecting back even further, Cloud Foundry was founded in 2009 at a little company called VMware, which you and I have some familiarity with. Back in 2009, I happened to be working for EMC which was the major majority-owner of VMware and where were you, John? Where were you in 2009? >> I was at VMware, doing that thing, preaching about virtualization. And Paul Baritz was there, there was a growing trend there in the company to be pulling out developer tools and I think this was one of the really bright ideas that came out of that time at VMware. >> Yeah, Derek Collison, who's a Cubalon we've had on many times there, was really the creator there. Back when we were talking about, when we talked about Cloud it was like oh, yeah it's about infrastructure today but in the future it's going to be as platform as a service. Fast forward, I mean boy the ebbs and the flows of Cloud Foundry got spun out into what became Pivotal. Cloud Foundry itself created a whole foundation. Paas, is kind of in the past now. We've said Paas is passe. Abby Kearns, who we're going to have on the program, with the Cloud Foundry foundation, said that it's not about Paas anymore. Seems to be, I hear multicloud, I hear, you know we're really about enabling developers in agility. What's your take on some of this journey that we've seen, John? >> Well, I think at this point in the journey, people are agreeing on the messaging and the needs and the things they want to be talking about. In fact, a lot of the messaging of Cloud Foundry, take my code, run it anywhere, I don't care how. The Cloud Foundry haiku is very similar to what you might hear from Cervalis, right? It's the same idea. Different level of abstraction, different kinds of apps, but the idea that developer productivity is enhanced by not worrying about the things underneath them, is a clear recognition across the industry today. >> Yeah. Absolutely, and it really goes back, a term that used to be thrown around a bunch of years ago is application modernization. And what does that mean? Number one is companies are becoming software companies so when you hear companies like GE, we're going to have Liberty Mutual on today and Liberty Mutual says we want to be a software company that happens to deliver insurance. So we've seen, car companies are going to become software companies that happen to have vehicles in some kind of manner. So it's this transformation, the software's eating the world meme, and right, that differentiation, I want my company to be able to focus on my applications and where that lives and what's underneath it doesn't matter enough. So right, whether it's Cervalis, Kubernetes, Cloud Foundry, OpenShift are all options to allow me to allow my people that write code to work on that stuff and make sure we get the operators and the infrastructure people involved. >> Right. And I want to consider Cloud Foundry and Cloud Foundry Summit in and of itself. I think it is interesting and people will compare it to things like DockerCon and we were both at DockerCon. I'm struck again by some of similar messaging about developer experience and agile. I think here though, the message is much more enterprise-ready, the scalability, the management, the business digital transformation was much more the conversation that's going on this week. The Docker experience, the container experience, is a lot more bottom-up, developer-up, one developer engaging in a different deployment and development pipeline. This is more about what does your business need to do to move faster. >> Absolutely. And this is a foundation show so what is the state of the ecosystem. Pivotal is the big player here. Pivotal's also our sponsor that allowed us to bring the program there. Really appreciate Pivotal's support to bring us here but three years ago, when I went to the show, it was IBM and HP, which is now HPE, very heavily involved, Cisco had a decent presence. Now, who's some of the headline companies here? Well big announcement with Microsoft. Google Cloud is on stage. How does that changing of who's involved, who's contributing, how many of users are actually part of the foundation and doing things are changing and as you brought up, very enterprise focused. One of the dynamics I've seen is Pivotal's done a really good job of getting to the C level decision makers and help them say, you want to do that whole digital transformation and become a software company? We can help. We have the labs group that will help you along that journey and then they pull the developers in and say hey okay, here's the tooling you've got. Let's go write this stuff and then they get on board and then they drive that change. >> You can't look at this stuff in isolation just for the foundation or the project or just Pivotal. The other companies have their own journeys. Some of the big ones, like HPE and Cisco have recently shifted a lot of their focus and their emphasis on open-source and pulled back from other things like OpenStack and so, I don't think you can put that solely on the success or failure of Cloud Foundry. I think you're also seeing another dynamic which is the cloud platforms, Google and Microsoft Azure, they want to be the best cloud platform for everything. They don't want to silo anything. They are welcoming. And so that's an example of them coming in and welcoming Cloud Foundry as one of the services that run great on their platform. >> Yeah. Yesterday, SAP and their Keynote put up this slide with all of these boxes and kind of made a joke, okay I'm going to walk you through how we built our stack and it actually, the entire audience cracked up. Chip Childers, this morning, said I've redone my Keynote, I'm just going to walk you through the stack and everybody laughed but it comes to a point that, what we discussed at OpenStack John, this is not a simple shrink-wrapped software. There are pieces of the proponent. How it all goes together. Kooboo is something we're going to dig into, which is, we take Bosch is the multicloud solution for Cloud Foundry and then it says, okay I've got my Cloud Foundry and I've got my Kubernetes and I can have them live side by side. Different from okay, we're going to take OpenStack and put Cloud Foundry and Kubernetes on top of it. Can I put Kubernetes on top of it? I was talking to some people from Google leading up to the show and they said well, yes you can put it on top, you can put it on the side, how deeply do you integrate it. It is still very early days for Kubernetes even though we've seen this real ground-swell especially in the developers' world. You mentioned we were at DockerCon. We're also going to have The Cube at CubeCon later this year so lots of shows. The maturity level, the adoption, who makes money, so many different angles to get in. I'm excited we're going to have some users on. What are you looking to take out of today's event, John? Some of our speakers or beyond. >> Well, we're here talking to people. So I'm looking at energy and I'm looking at people who, their vision of the future, what they actually have accomplished, the businesses and the business outcomes that they've achieved, I'm really looking forward to the customers. And also the ecosystem, right? Cloud Foundry Foundation is part of the Linux Foundation. How are the different open-source components working together because we are discovering in 2017 and beyond that all these open-source stacks do need to inter-operate and do need to talk with each other. And so that's something I'm very interested in as well. >> Yeah, absolutely. Our first guest, Chip Childers, is going to be able to go into a lot of them. As I mentioned, we've got a couple of guests from Pivotal. We've got a couple of Vend users. We've got people from the Foundation. Got a guest analyst, Stephen O'Grady's going to come on from RedMonk. So got a full day of coverage, in addition to some of the things you mentioned, right, that kind of multicloud, how do we differentiate, you know? Why Microsoft wants to be very open. Amazon seemed to actually get like denigrated a little bit by some of the comments of some of the speakers. Not by the Foundation or anything like that but Liberty Mutual, one of the guests we have on, they run on Amazon. Pivotal started Cloud Foundry on Amazon and Amazon of course is the juggernaut in the cloud world. We've actually got, one of our teams are out at the Amazon Public Sector show, digging into that ecosystem. So Amazon is always the elephant in the room if you will when we're talking about cloud. So how do all these pieces fit together? So I'm excited to dig in. Really glad we could bring The Cube to this event. Very much a t-shirt crowd that we've got the show for behind us. Everybody getting excited about some of those things. >> I think we're the only ones with jackets here. Maybe one or two. >> There are. There's the press and the analysts are here but absolutely. If we did this two days, we'd pick our favorite t-shirt and throw it on under the blazer. That's kind of the Valley way, as you know. Alright. So John, really appreciate you joining me. Please stay with us for the full day of coverage. As always check out siliconangle.tv for this and all the events. We're going to be back and we will be right back with our first guest here at the Cloud Foundry Summit. Thanks for watching The Cube.