 Good morning. How we doing? Everybody awake Well, those of you that are here right looks about 50% of the audience we had yesterday Must have been a lot of late nights. All right. Well, thanks for coming So I woke up this morning and I was inspired to change my entire talk Largely because Bjorn from SAP yesterday had such a wonderful eye chart of boxes and lines That make up the the cloud platforms. So should we pull that slide up and maybe walk through box by box? Yeah, yeah, no, I'm just kidding that I joke but there's there's a lot of complexity in Cloud Foundry and so what I want to talk to you today about is The combination of the enterprise readiness of this open source project and the innovation that's happening Both inside the project teams and around it in our ecosystem and our community Now I love starting talks with this, you know, really simple slide So those of you that are developers and hopefully about half of you are developers You recognize this right sort of a moment of anticipation. You wrote some code. You're ready to go It's time to push it into the platform and you know it's gonna be ready for production at that point Well, assuming you don't have any bugs it's a moment for developer where you get to Be free to release the software quickly and Anci from from Pivotal a while back wrote this awesome haiku Here's my source code run it on the cloud for me. I do not care how and There's a lot behind that promise So let's spend some time digging in underneath it Now I was an enterprise technology as a buyer for many many many years and There's one thing that I know that enterprise ready means it means there's a sales guy with a quote who wants me to sign But I kid and all of the account executives in the room I'm not talking about you if you're you know talking about cloud foundry, of course, right? This is enterprise ready software. So what is what is enterprise ready mean for the cloud foundry ecosystem? It really boils down to four key attributes and these are the themes that we're gonna talk about today The first is secure Cloud Foundry is being used in some of the most highly secure IT environments globally Second well integrated right because an application on its own is fairly useless You need great backing services. You need integration into the quote-unquote legacy IT systems, and I hate that I hate that term. What is legacy? But the thing that you already pushed to production yesterday, right? Being well integrated Third scalable right because we're not only being used heavily by large enterprises I mean you heard the numbers from Comcast yesterday. We're being used by large-scale public cloud providers to offer has So it needs to scale and last but not least is that great developer experience and that includes integration with IDEs That includes integration with developer workflows. So this is this is what enterprise ready means to cloud foundry ecosystem Now I was a web developer, but but if you imagine your user and you don't know much about how technology is built You know when you think about is this app that I'm using secure really? It comes down to the simple little icon that shows up in your browser, right? You're like, oh, yeah, sure. They must be a secure app But we all know that there's a lot more behind that and if we dig into what cloud foundry is We've got this control plane with lots and lots of components and they're all talking to each other And there's lots of communication going on and we've got all the applications being deployed They're talking to the components underneath it. They're talking to each other There's a lot of communication paths that have to be secured So our community has been doing two things So the first is that they've been going through each one of the components that make up our control plane and Ensuring that the communications from each component whether it's one of our services like UAA To the cloud controller or whether it's the cloud controller to its database is secure so that we can be trusted to run in public environments The second thing that's been happening is a lot of innovation around how do you secure the applications themselves make it really easy for a developer To secure communication between their two microservices So we've got a lot of great stuff happening and We're about 90% of the way there in terms of the control plane. At least that's the latest number that you a cow gave me So I think we're close to being completely Encrypted in all our internal communications And if we dig a little bit deeper into the platform we we go into a single Diego cell We run into garden. This is the lowest level container abstraction in inside our platform Now I love our garden team because they've they've really made it their mission and it's lofty goal Their mission is to be the most secure Container runtime for a multi-tenant application platform in the industry now. It's a great goal and They spent a lot of effort Adopting run see this is a place where our collaboration with another open-source ecosystem comes to bear run See is the project that came from Docker was brought to the open container initiative and it along with the open container Image format specification represent the building blocks for container-based platforms And our garden teams focused on security so they've of course you see groups of resource resource constraints But app armor username spaces in its set comp are all enabled by default These are really important kernel features that allow us to have a robust isolation between the different containers running in the system So now I want to step back a little bit and talk about a project called cred hub Some of you might have heard of cred hub. It's an incubating project recently joined the foundation Cred hub is solving a problem that emerges when you're dealing with these complex distributed systems And I think it solves it very elegantly. It thinks about credentials Really with four pillars. What are the things we need to do with any credential? We need to be able to generate new ones. We need to be able to of course encrypt it both for in transit as well as at Rest we need to be able to persist it and we want to make rotation really easy And we want to expose that through policy and make it an option for admins to use The apps themselves to use and the infrastructure to use. There's really great example of the applications themselves Our Diego team has been integrating cred hub and what they've done is they've said every application instance running on a Diego cell Could potentially have its own unique certificate, which would not only identify the instance or the container But also allow it to naturally secure its communication with all of the other app instances or micro other microservices that it might be using All right, so in in the software industry We really know one thing about software quality and that's the number of bugs that any software has, right? that equations n plus one where n equals the number of bugs you currently know about and Of course some of those bugs are going to be vulnerabilities. This is just the reality of complex software Software is difficult to build We do our best to have secure coding practices, but open-source software proprietary software There's a constant stream of new fixes that need to be rolled out into environments So imagine for a second you were going to go build a system just like Cloud Foundry yourself Not by using Cloud Foundry, but by building all of the pieces and parts necessary to create this level of a platform You'd probably start first by picking an operating system Now they have a constant stream of vulnerabilities and I'd argue having done this at a managed service provider We still really haven't figured out as an IT industry how to effectively patch manage at scale diverse operating systems Then these are building up a whole bunch more dependencies, right databases message brokers You've got the programming language that your developers are using in the frameworks things like no JS or the spring framework And last you've got the platform itself And whether that's a combination of open-source software you've pulled together or whether it's a bunch of Python scripts that somehow Deploy applications and manage them. There's a lot of risk In a platform like this Now what the Cloud Foundry open-source community does for the entire Ecosystem is bring a level of maturity that is really unparalleled in open-source software We release an entire platform from a base operating system all the way up to the build packs that support the custom apps that are being deployed This is incredibly important to our ecosystem all of the downstream distributions get the value of it and All of the direct open-source users get the same value We do it at a high velocity to our coordinated releases are averaging over twice a month and they can be kicked out extremely rapidly Has anybody here heard of cloud.gov? Few of you so we talk about it periodically at conferences. They've they've given given talks I think in one of our events in Berlin Cloud.gov is a online service that was created by a group inside the US federal government called 18f 18f's entire job is to find ways to allow Technology and some of the learnings we have around how you develop software more agile techniques devops practices How to how to support? That learning and support the adoption of technology that's much more modern in all the government departments agencies bureaus whoever's interested And so they launch cloud.gov. It's a pure open-source implementation of Cloud Foundry including backing services But what's really cool about it is that in order to be effectively adopted across the federal government They had to get what's called a Fed ramp authorization now That may be a very boring bureaucratic bureaucratic term, but if anybody here has done any government work You understand that that fed ramp authorization is exceptionally hard to get in February of this year they received that authorization and became the first open-source service to get fed ramp authorization Now they did that and I look at that and say that's a sign of the open source upstream Demonstrating the quality and its enterprise readiness number one, but number two they did in an extremely transparent way So if you're in a different industry financial services insurance Manufacturing you have your own regulatory scheme that you need to worry about you can go find 18f's Public documents that talk about how they deployed Cloud Foundry how they operated how those procedures and technologies map to their controls So go take a look. It's an amazing example of governments finding a way to be participants in the open-source world, but also Build up the possibility of better citizen engagement All right, so let's transition to scale now There are also mics over there 250,000 application instances That's containers for those of you that want to hear that word late last year the Diego team Reached the quarter million containers being deployed and managed by the Cloud Foundry platform But see here's the thing. It wasn't a false test This was a realistic performance and scale test. It included applications of varying sizes It also included applications that were purposefully designed to inject fault to shut themselves down That demonstrated that the system continued to keep its promise of the apps staying alive It demonstrated that we could drive massive throughput through the system and it also Gave us some opportunities for additional improvement now. I'm going to pick on one team mostly because they did really great work a Routing tier is part of the data path as a user of an application when I make a request view my web browser It's going to flow through the system. The first thing it's going to hit is the routing tier So obviously throughputs really important before they started their performance work The team pay attention to the five millisecond latency and throughput intersection the team measured and baseline at about a thousand Request per second is throughput for an instance They spent one release and managed to improve that all the way out to over three times the throughput Now that's good and that's impressive and it was amazing work But here's what's more important every single release they rerun the test and Look for continued incremental improvement to the scale now that is an incredibly mature open source project Now I love this image So those of you that might work in in the Cloud Foundry upstream you probably recognize it The the team was really looking forward to retiring the older DEA architecture They actually had a countdown timer of course This was a CF deployed application right and they had a countdown timer They counted down the minutes and seconds until we got to move the older architecture to the attic So make no mistake the DEA's are dead Well, they'll live on forever in read-only mode But the entire ecosystem has transitioned to the Diego architecture now Let's let's talk about Cloud Platform certification. You notice I've got your 2016 up there because in in December of 2015 we announced platform certification and we had a really lofty goal Our goal was to find a way to help ensure that the downstream distributions and services based on Cloud Foundry We're going to provide consistency So that we could have application and skill portability across the distributions and throughout the ecosystem now It's a bit of a lofty goal. We did not fully achieve it that year. We did launch the program and it was successful But fast forward to 2017 and we've done a few things so first The 2017 certification has eliminated the option for the older architecture where Diego only and the whole Ecosystems moved there To we've also decreased the age that A distribution that certified can use From something as old as a year back to less than six months. So now we're moving the entire ecosystem together Forward released by release The second thing we did though is to talk about application portability, you know The area of differentiation that the distros have is in the services along with a bunch of other wonderful things But you know the core platform is the same. It's really about the service capabilities So when we launched the open service broker API initiative That was designed to open up and free the services so that we could have a much more fluid service marketplace so their cloud provider a could offer their services to CF platforms that may or may not be running in their environment That's been successful and it's actually been successful across ecosystems And then of course as Abby mentioned we launched our Cloud Foundry certified developer program And that really was not possible without getting ecosystem consistency So we build off of this platform certification as a community and our training portfolio has grown dramatically We have been doing one-day summit training classes since the foundation started and I want to thank all of the the partner companies who have actually delivered that training and have created it And and cloud credo and pivotal specifically for open sourcing some of those courses for us But we also launched the introduction to Cloud Foundry class in the edX platform a team wonderful team from Stark and Wayne Worked really hard to get that done under a tight deadline We launched it and it's been a great success It sits there in in the edX platform right next to courses from MIT Stanford Harvard. It's a great audience to have Cloud Foundry for developers now This is the much more intense class is designed to be delivered really two ways one We're offering it in partnership with the Linux foundation as you learning material But two we have over 13 and growing authorized training partners that are ready to deliver this material It's common. It's multi-vendor It works across the distributions and it's a great baseline for all of the the different vendors in our ecosystem to build off And then of course last but not least the Cloud Foundry certified developers also Is also useful across the entire ecosystem Now I'm really happy to say that we had a soft launch that That program and we've already educated over 5,000 developers in less than three months without doing a ton of marketing. That's great, but it's just the start Okay, so let's transition now. I want to talk a little bit about innovation Now innovation Cloud Foundry comes from a number of different sources We of course have the Cloud Foundry community itself But we're deeply intertwined working with other open source ecosystems everything from the open container initiative with both Their image specification the RunSea library We've been actively working our Diego persistence project who's been finding ways to provide Attached storage to the containers have been working deeply with other Platforms to think about what does it mean to do volume management in a container system? Open tracing tracing is a very important CNCF project as well We can initiate Zipkin traces which is based in the open tracing API directly from a router all the way down through Microservices CNCF container networking interface, which I'm actually I'd like to make sure that everybody saw the announcement Our container-to-container networking project reached its 1.0 milestone Just a few days ago So if your distribution offers it give it a try if you're using the open source directly Give it a try if your district doesn't offer it feel free to ask them for it because it really is a great capability for the application developers Now Abby introduced that Microsoft has joined us I just want to spend a minute to talk about the Microsoft's technology and how we think about it related to Cloud Foundry so in 2015 We spent a lot of time talking about how the the Microsoft technology stack and dotnet in particular But also the windows operating system was really important right if you sort of squint You see that there's there's Roughly, you know when enterprise software is being built a large percentage of it is Java and another large percentage of it at net So the Microsoft technology stack is incredibly important to true enterprise adoption Now there was the iron foundry project, which was really the first effort And I think a few of those folks are here right years ago It's the first effort to do dotnet services on the windows operating system within the context of cloud foundry And we've evolved it. We have production systems that are running Network loads on Microsoft windows Now when Microsoft released the dotnet Language as open-source software that also allowed us to then say great. Let's have a dotnet core build pack for the Linux platform And that's available and that's that's being provided in the upstream at the same level of parity as all of the others But we also this year have unlocked the power of Bosch for the Windows platform The Bosch Windows project team has launched, you know, the initial release you could now get all the same operational value you get from managing Linux nodes Linux based distributed systems Using Windows based distributed systems And last thing I'll point out on Microsoft was I think Corey mentioned this very briefly yesterday The the CF command line tool and this is really neat the CF command line tool is now installed by default in the Azure cloud shell That makes it really easy for a developer using The Azure platform to get access to cloud foundry. They can I think one click deploy CF And then the command line is already installed in the cloud shell makes it really easy So so let's go back to this whole CF push thing I've actually heard from plenty of end users and in particular developers We do actually have some improvement that we need to make to this and The improvement is is in the flow of a developer now for those of you that write code, you know that there's there's a flow That you have local to your machine, you know You're local in your laptop You're doing a lot of tests and you know debugging and you're kind of you're looping you're looping and even though CF push is extremely easy and gets you all the value of the you know knowing that it's going to be well-operated That CF push process is a little bit slow for local development So Steven Levine our build packs project manager product manager He created on his own time a really neat project. So everybody should go check this out. It's called CF local CF local Uses the Docker container engine local to a laptop and it lets you do a stage That means build a container using a build pack It lets you run that container local and the really interesting thing here is that you can bind local database services To that instance so it looks and feels like it's running in the larger CF platform Or you can connect to a remote cloud foundry environment and proxy in the service instances that have been created for you You can also push and pull images. So a lot of possibility here, and I know he's got a really interesting Set of potential futures for this project. I encourage you to talk to him There's a there's an office hours that's dedicated to this particular project. So take the time go go learn about it It's got a great future for us Now completely orthogonal. Let's talk about something that isn't containers. There's a possibility Possibility that you know kernels might be an interesting alternative deployment model in the future There was a project that was created at Dell EMC called unique It's an orchestration platform for you know kernel based systems And it's been proposed to join the Cloud Foundry Foundation. So pay attention to that Engage in the conversation about whether it's a fit. We're excited that it's at least that community Which is already fairly diverse has expressed interest in joining us Okay, so I'm well over time with countdown clock is actually going up, but that's okay This is a lot of really interesting stuff at least to me So I want to say happy birthday to Bosch. Can we take a few minutes to sing happy birthday? No, no Don't really need to do that. But Bosch is five years old five years old And it's undergone an enormous amount of change in particular over the course of the last year It's gone through a set of changes that have been kind of termed a Bosch 2.0 Now we haven't released a Bosch 2.0, but they've been termed Bosch 2.0 because they've reduced the complexity of building Bosch releases they've reduced the complexity of deploying and managing environments using the Bosch platform so a lot of really great changes and That's why we believe the Kubo project which Abby introduced yesterday is so interesting because it's another demonstration of a complex distributed system a Platform focused on containers being managed by Bosch Right, so so what deploys your platform? That's a question. You should ask well. It turns out Bosch is the right answer for that But also Bosch is the multi-cloud story for Cloud Foundry make no mistake about it It's at the heart of it when we talk about multi-cloud and all the cloud provider interfaces that are supported by the upstream It's a wide variety We range from large-scale multi large-scale public clouds through to open-stores platforms like OpenStack The the on-premise software coming out of VMware with Photon and vSphere Don't forget of course Bluemix software and then even bare metal provisioning systems like Rack HD It's a wide range of options supported by the upstream community and in addition There are further CPIs that are out there for for other cloud providers or infrastructure options out in the open-source community but multi-cloud isn't just about CPIs it's actually It's about how do you ensure that the capabilities of these different public clouds are exposed in a way that can be used by developers and used by the platform So there's two other areas that I'll highlight The first is that the UA a module with its identity providers has added both Google and Microsoft's Identity providers. That's kind of me right so if you use Google apps in your enterprise you can tie that into your cloud platform The other is the open-service broker API now. I've mentioned this three times. This is the third time. There's a reason for that This is an important project It allows Microsoft it allows Google it allows Fujitsu To describe their cloud services in a way that can be consumed by other platforms Whether that's cloud foundry or whether that's Kubernetes or whether that's any of the Products that are building on top of Kubernetes or any other platform. It's extremely powerful Nice and simple, but extremely powerful And I have the pleasure actually announcing today that as of at some point really early this morning The the project team the cross ecosystem project team has their first release of the specification That's not intrinsically and directly tied to the cloud foundry platform release. So huge Hat tip to that that group. It's an amazing job And we're seeing it be adopted in the Kubernetes community and it's wonderful. It provides all kinds of flexibility for users So with that I'm done mostly talking to you and I actually want to introduce a few people up to the stage We're gonna we're gonna have a conversation for a few minutes here So I want to bring up first Frederick from TechCrunch who's gonna help moderate a conversation Areas all right Frederick and then we've got KY from Microsoft and Eric Johnson from Google Cloud