 Well, thank you very much. It's great being here at the Foundry Summit. So I'd like to talk to you briefly a little bit about HP's vision for bringing Cloud to the enterprise. And then we'll talk some more about some customers and a little bit more about something at the end of the slide. So when we talk to our customers, a lot of things bubble up. And one of the major things that bubble up and has helped us think through, what do we believe about this Cloud Revolution? Is that we believe it's open and we believe it's hybrid. And that's one of the reasons we're so excited about being in the Cloud Foundry, participating in this community. Our customers are always telling us that we want to go faster and they want to move their application development teams and enable them to move faster and faster. When I talk with CIOs or talk with leaders of infrastructure for these large companies, they talk about the roadblocks that are in their way. And when a team wants to try and experiment or wants to try something innovative, it takes days and weeks to bring their infrastructure to place. And it takes a long time to get the CICD systems going. So when they hear about the application development processes that can get enabled by Cloud Foundry, they're very excited. And as we move forward in the industry, we think about open as being more than avoiding vendor lock-in. It means about getting embedded in an innovation cycle that is taking over the industry, whether it is other open source projects, whether it's an open stack, which we're deeply involved in. The amount of innovation and the amount of evolution that you see going on on a daily, weekly basis is truly amazing. And launching the foundation has really been exactly the right conditions for Cloud Foundry. It's really opened up this community and it's great to see the amazing growth we have here. And I can see that when we come back, we're going to have to open up the back part of the room and double the size again, which is truly awesome. So we've been at this about a year. And you know, version one, customers have some perceptions with that, right? So it's generated perceptions around lack of build packs, the ecosystem is still booting up. And so as we talk to folks, they're very excited to see what's going on in two. And when you talk about version three, people's eyes light up. And so all the work that's going on there, I think, is absolutely exciting. Now getting the foundation in place is enabling us to get better, clearer roadmaps. And from an enterprise adoption perspective, because I'm an ex-dev, tons of us are ex-devs in the room are devs, it's like, why do we need these roadmaps? They want to know what we care about. A roadmap is an expression of the kinds of problems that we want to solve or that we believe we're going to be solving for our customers. Some of our customers have got 10,000 application developers. And they've got huge teams. They're trying to help make those people more effective and productive. So they're trying to figure out, what do I need to do in the next year, 18 months, to intersect what this community is doing? Because they want to make investments that aren't right in our path. They want to make investments to integrate in, to make use of the kind of technologies that the teams here are building. And with that, we see there are going to be more clear cadence around roadmaps. So one of the things that we're excited about what we've been doing within HP is really strengthening the bindings between OpenStack and Cloud Foundry. Big believer in making sure that the infrastructure layer and the PASLA can work really well together. We believe that the interconnections, we offer Trove, which is the MySQL Database as a service, inside our Foundry offering. We believe that increasing those connections means that we can make better use of the hardware and infrastructure to move things forward. So one of the things that people ask about is, exactly, what is the definition of CF? Because this is, as a new thing, people are trying to understand, where is the definition lie? Is it within the implementation? Is it within the API? Where does the community want to take it? And I've spent my entire OpenStack life cycle, I was in the beginning of OpenStack, and we had exactly the same problems. OpenStack, the code is the definition of the product. So there's challenges to figure out, do we want to do that here? How important do we want to make the API definition versus the implementation definition? When I talk to customers, there's a bit of confusion, especially going on with the huge momentum that containers have. In containers, the container technologies, we have Kubernetes, Mezos, Docker, and many more, making sure we've got a clear perspective in this community is, what is the relationship? How do we act? How do we interact with them? What does it mean as both these communities evolve? And they're evolving very rapidly. Think about what Cloud Foundry was a year ago, where Docker and containers were a year ago. They're both on this tremendous development path to accelerate application developer productivity and to enable cloud native applications. And promoting the work of the foundation with more than 50 companies involved, it's absolutely a huge movement at this point. So one of the things I like to talk about is I spend a lot of time talking with our customers and talking with CIOs and VPs of infrastructure and application development. And I always start to ask, what problem are you trying to solve and why? And tell me what would make a great year for you and what is your CEO trying to ask you to do? And what I end up with is a lot of great conversations not about the technology and not about the product but about the problems we're trying to solve. Because I think that's half the work. And so some of the feedback that I've gotten is that the enterprises need features that are behind the firewall. They're completely isolated from the internet. They don't want to be able to download, build packs. They want to be isolated. They want to be able to build packs where they can integrate in their own systems in to make that a first class citizen within Cloud Foundry. They really, really like the fact that HA is taken care of for the application developer. But they want to make sure that the ops people have a good way to manage scaling and HA right out of the box. And those extensions, whether service packs or brokers, enabling them to tie into the hundreds of interesting algorithmic systems they've already built to make those things accessible into their own systems, they want to bring that to the application developer. Because that's right now what they've got to do is they're hand crafting the tools for the application devs. When we think about other aspects of it, with the Java development teams, with .NET teams, and as I look at that, probably 45% of our enterprise customers are running .NET. So it's a huge amount of effort. And so what we see in that is we've seen a moment where we've got the ability to bring .NET to Cloud Foundry. And that's what we've done today. So today, we've released development platform version 1.2. It's actually in production. It's on our public cloud. And you can try it out. Right now, enterprise developers can develop and deploy cloud-native applications on V2 natively. So we offer native .NET support with Windows DEA droplets, bring your own Windows license, Visual Studio integration, MySQL, I'm sorry, Microsoft SQL Server integration. Got to say something wrong. That's next week when I'm talking at OpenStack. And application development tools and technologies integrating in with your IDEs. So whatever ID you have, we connect into that. So we're very excited about how this is going to really bring that forward and enable the enterprise developers to make more full use of Cloud Foundry, of the applications we have. We've also tightened the integration between the OpenStack and the PAS layer of Cloud Foundry. So we make Trove as a first class citizen. We allow Cloud Foundry and OpenStack operators and admins to manipulate and control those technologies. And so it's a very nice tight binding between the application lifecycle management and the actual underlying PAS. So that allows us to really make sure that developers can work within SQL Server, provide self-service database and database resources, and basically eliminate the need for operators to be able to manage these containers. So the other last part about this is we've got all the SDKs and the .NET toolkits. So within Cloud Foundry, we have the Visual Studio Explorer, and within the IT operations side, we have the ability to basically have those managed very well. So with that, I'd like to just give you one more thing, but that's really not all we've got. So we've open sourced all of this work. It's on GitHub today. It has absolutely contributed all back to the community. You can do a quick developer trial on our public cloud, like I said. And we're really proud members of this community. We're proud to have this as part of being accepted into the Foundry. And really, I want to give a big thanks out to the HP development team, which I think some of you guys are back over there. Thank you so much for all the work that you guys have done. So really, thank you very much for all the time and effort. And I'm going to hand this over back to Sam.