 Josh, I'm getting some tweets from some folks who follow us, who aren't as geeky as us in the OpenStack world. Asked you to provide a OpenStack 101. Yeah, they're hearing Diablo, Novel, these kind of buzzwords. So just quickly, just give an OpenStack 101 for the audience. Sure. What do they need to know? I can do it in five numbers, okay? OpenStack is one community around two kinds of clouds. That would be public clouds and private clouds. So in your own data center, somebody else's data center. It has three kinds of interfaces. So you've got a command line interface, you've got a web dashboard, and you've got a programmatic API. All three of those work in the same way, and they service the same things. Now the fourth thing is you've got four kinds of resources exposed through those interfaces. So you've got two kinds of storage. That would be new object storage and old block storage. You've got virtual networks, and you've got virtual compute resources. So those are your four resource pools. And finally you have five actors. This is the most confusing part, okay? You have vendors. That would be folks like this. That's confusing. Who sell clouds or cloud software. You have operators, the folks that run clouds, either again, private or public. You have auditors. People forget about these guys. They're the ones who have to look under the covers, but they're actually not delivering value. You have users, cloud users, meaning they connect to those APIs or the command line tools. Then you have end users. That's somebody who actually uses an application that's hosted on a cloud. And they may not even know it's hosted on a cloud. So if you pull your phone out of your pocket and you connect to any app on your phone, you're an end user of cloud, whether you realize it or not. So that's OpenStack in five numbers. And then let me follow. Then what was either the event that created the desire to create OpenStack or what was kind of the mission, the really high level mission, when you guys got together with however many people you were five years ago and here in lovely Portland. So I was running a team at NASA and we had a mandate to do something about NASA's data and how they were building applications. And it was a very broadly defined mandate because it was Skunkworks' unfunded project. And we originally set out to build a platform as a service that the agency could use. And was it because their existing thing wasn't working well? Is it because they saw a new age of types of data or amount of applications? I mean NASA had at least 300 data centers. Didn't even know how to count them. Thousands of applications written in dozens of languages. So we had security concerns, we had cost concerns, we had legacy concerns. And really NASA's mandate is to collaborate. But we can't let people at our infrastructure because it's also one of the most secure government agencies. And so we were trying to build something on the inside of NASA that looked like things folks could run on the outside. That was the path to open source. Was to say if we build this as an open source technology, we can use it. Other people can use copies of it and we don't have to give them tunnels through our firewall every day. Which sounds ridiculously forward thinking for a big government agency to actually say here with the crown jewels and some of the most secretive stuff I'm sure we have, as a government let's use the open source model to drive the innovation to clean up the spaghetti right there. So if you look at the team, my team that built this at NASA, none of us who were at NASA before this project and none of us are still there. So it was a very rare window in time we had inspired leadership.