 My name is Nicholas Walker. I'm going to talk to you a little bit today about Cloud Foundry, OpenStack, and the Enterprise Developer. Talk a little bit about me first. Before I do, though, I'd like to know, just get a little feel for you guys, how many people in here know what Cloud Foundry is? You just raise your hands. OK, so a good chunk of you. And I assume, well, how many of you all know what Solom is? OK, fairly knowledgeable audience here. Well, so a little bit more about me again. My name is Nicholas Walker. I am a product manager for the HP Healing and Development Platform, which was just announced last week. My primary role on the team is to manage the Cloud Foundry efforts for the development platform. I have been with HP for just over a year now, so I've actually came from a very small company that I founded. It was a SaaS marketing provider of automation software, and I did that for about 12 years. So it's been an interesting last year going from a small company to a very large company. I've got a very technical background at the company that I founded. I basically served as CTO for a good chunk of the time. So I did everything from setting up bare metal to running databases to installing sands. I ran the QA department. I ran our DevOps department. So I've kind of done it all. I've got a broad perspective on development patterns and things that developers need to do to be successful in their jobs. And then on top of that, I also have an MBA. And so that's my business background. And as I like to say, I'm also a former recovering MCSE. So let's talk a little bit about the HP Healing and Development Platform's team and our objectives. So we basically have two missions in life. So one is to build a best-in-class developer experience on top of a highly available, scalable, open-stack foundation. And the second piece of that is to demonstrate leadership and bridging the gap between open-stack and Cloud Foundry. So these two goals go hand-in-hand. So first I'm going to talk about that first item there. So building the best-in-class developer experience. So enterprise developers have a need for more than just IaaS. So compute and storage are great, but you still need the tools on top of that to make yourself successful. And developers tend to spend a lot of time and effort building on top of the IaaS that they put together. So you still need to install database solutions. You still need to install runtimes. You still need to install message queues, all of these other tools. And as that expands in enterprises, you have more and more developers. There's more and more time collectively spent by development teams doing that. So the solution for an enterprise developer is a platform specifically designed for that developer. The platform would do such things like enable developers to quickly deploy, control applications, focus on the code, managing the code, and not managing the infrastructure, and really eliminate the needs for developers to be experts in many diverse technologies. So some of this would include instant provisioning and deployment of applications and supporting multiple frameworks, multiple languages, runtimes, and so on. So that diagram out there right there kind of simplifies how we look at the world. So we have an application runtime that sits in the middle. And then all of your other services that tie into that, your database, load balancing, DNS, and message queue as a service, facilitating the DevTest run cycle. So HP has chosen Cloud Foundry, which is that purple circle in the middle, application runtime, as what we are going to work with to develop that out on top of OpenStack. So let's talk a little bit more about specifically what Cloud Foundry is. So Cloud Foundry is a leading open source development platform software. So the technology was originally developed by VMware. And it was spun out to pivotal labs in 2011 and then subsequently open sourced. So it's what is referred to as a polyglot application runtime environment. And it basically simplifies the IaaS. So it's basically a cluster of VMs and services that work together to provide a platform on which developers can publish and run their code. So it's got multiple programming languages, multiple services are supported, languages like Java, Ruby, PHP, and then other non-OpenStack services, such as MySQL, PostgreSQL, RabbitMQ. All of these things kind of run inside of a cluster. And you can pick and choose, when you build your cluster, what you want Cloud Foundry to look like. And this diagram on the right shows the building blocks of Cloud Foundry. You've got your DEA pool, which is what runs the applications, you've got service broker nodes, which is what runs like their database and your message queuing, that type of application. And then at the bottom there, important thing to note is Cloud Foundry is cloud agnostic. So it can sit on top of VMware, it can sit on top of OpenStack, and it can sit on top of AWS. So let's talk a little bit about how HP and Cloud Foundry are working together and have been related in the past few years. So HP announced earlier this year that we're going to be a Platinum founding member of the Cloud Foundry Foundation. So in February of 2014, the formation of the foundation was announced. It's not actually formed yet, just the formation was announced. And it's in the process of organizing. And there are seven founding members. HP is leveraging, and proud to be leveraging, our OpenStack leadership experience to drive the creation of an open governance model. So the Cloud Foundry community and how code is contributed and pushed back upstream has really changed over the last year. And there's a tremendous amount of momentum going on right now around this organization and around the community. So on May 1st, there were actually eight additional members of the foundation announced. And in the last 12 months, there's been 113% increasing contributors. And there's been over 700,000 lines of code contributed. At the bottom there, you can see kind of a timeline on the progression of Cloud Foundry and how it's grown in the last three to four years. So back in 2011, it was open sourced and announced. And then in 2013, you can see there was a tremendous amount of activity, including HP's public cloud, actually has a beta, we call it APAS, Application Paz, Private Beta, that went into production in March of 2013. A big event last year was IBM announcing that they were joining Cloud Foundry. So kind of late in the summer of last year, IBM made a big announcement that they were going to get behind Cloud Foundry and really drive it forward. So that was a big turning point for the community. And then again, in 2014, we've got HP with our platinum sponsorship. There's an open governance model that's being developed. And a lot of other large organizations are moving to get behind Cloud Foundry. So I want to talk a little bit about Solom, because this is, after all, an open stack conference. And just a little bit about kind of where we are at Solom. So Solom is an incubator project that's designed to make cloud services easier to integrate into the application development process. So it's essentially a Paz that's competing with Cloud Foundry. This was announced in October of 2013. And we've looked at it and spent some time talking to the people involved with it. And we support the end goal of the development platform, tightly integrated with open stack. That's something we absolutely want to see and want to do. We've chosen to start with Cloud Foundry versus Solom. We're still tracking Solom and are interested in it. But we've chosen to start working with Cloud Foundry for a number of reasons. The biggest one probably was the time the market is shorter for us. So we've already have two years really working with Cloud Foundry. We understand it. And as of October, Solom was a brand new project that didn't really have any code behind it, whereas we had a whole bunch of code with Cloud Foundry. So we really felt that we could achieve our business goals, even if maybe it's not the most optimally integrated platform out there in terms of being integrated with open stack. But we still felt we could achieve our business goals with it. We also thought that we could take a top down approach rather than a bottoms up approach. So we think we can take what's existing Cloud Foundry and work backwards and integrate it very tightly with open stack, rather than having to start from scratch and build something from the ground up to integrate or to be native to open stack. So let's talk a little bit about that process and our thought process around doing that. So this is what Cloud Foundry and open stack look like today. So you have open stack on the bottom, and then you have a gap, and you have Cloud Foundry sitting on top of it. So those two dark blue boxes at the bottom are kind of your core open stack services. So you'd have your NOVA, your Neutron, so all of your compute and networking up into load balancing and DNS as a service. Other pieces of open stack that are kind of required to run applications and to run your VMs. And then on top of that, you start to get into the area where a developer is going to be concerned about. So these are going to be the building blocks for applications. So Trove, your D-Bass, your Q-ing, and then image marketplace and other pieces sit kind of at this layer. And then above that, you have Cloud Foundry. And so Cloud Foundry natively has support for the Java, Ruby, Node.js, on down the line into these different languages. And then it has unmanaged services. So I can install a Cloud Foundry cluster. And inside that cluster, I'll have MySQL, I'll have RabbitMQ, I'll have these other services. But they sit on top of VMs that are not necessarily set up in an HA way or to be optimized for speed and performance or that type of thing. So the philosophy we have is to really start taking each one of those things. For instance, MySQL. It makes a lot of sense to tie that back into Trove. So that when I create a cluster natively inside of OpenStack and I have D-Bass and Trove running on OpenStack, it knows, oh, here's my Trove. I'm going to go plug straight into that. And therefore, I have HA. I have this back-end service managed. And it makes a whole lot of sense. And it makes the Cloud Foundry application that much more stable and have that much more performance. So these are the integration points that we're looking at as we look out as to what we're going to build out for the Healing and Development Platform. Some really natural points. The first one, Keystone integration. So it makes a lot of sense to have shared security credentials. So if I've got security already set up in OpenStack and I'm going to be creating clusters on top of that, there's no reason that they can't share the security credentials so that I don't have to maintain these in two separate spots. The D-Bass integration, I just discussed a little bit. And then other key integration points, message queuing, load balancing, DNS. These are all things that Cloud Foundry has to do natively when you set up a cluster. So making connection points back to these and making that happen automatically when you create and set up a cluster is just a very natural thing to do. And then the big thing is that Cloud Foundry UI and conceptually how we would integrate that back in OpenStack. So this diagram is a little mock-up that we've brainstormed on the team that shows potentially how you could have an application host embedded inside of the Horizon UI, where it's listing out all the different clusters that you have available to you as you work through your building your application. So finally, just a quick note about the HP Healian Development Platform. So what is it? So on May 7th, we announced plans for a new development platform. And that's going to be based on Cloud Foundry. So it's going to be based on all the things that I just got done talking about. Obviously, we spent a lot of time thinking about these things. And it's going to be an open platform for developers to build, deploy, manage applications quickly and easily. It's going to integrate with the HP Healian OpenStack technology that we announced, both our community and our commercial addition. And there's going to be more details on this in Q3 of this calendar year. So that's all I had today. Thanks for coming. And I think the gentleman in the last presentation had this exact same slide, but we are hiring. So if you're interested in working on this or working on the OpenStack technology, there is someone down at your booth that you can speak with, or you can go to this URL, or feel free to come up and chat with me afterwards. Thank you.