 So, our third user that we're going to bring up is not in the media business. They are in something that probably many of us have to deal with on a regular basis as we go about our business. But they are making use of open-stack storage in some interesting ways, and I'm really excited to bring up Senior Manager from Concur, Dan Wilson. Go get them. Thank you. Really excited to be here today and have the opportunity to share the story about how we brought open-stack into our environment. But before I get into that too much, let me tell you a little bit about Concur. How many folks here today are traveling on business with a show of hands? Thank you, quite a few. And of those, how many of you are excited about the prospect of filling out your expense claim to get reimbursed? Just as I thought. Nobody. Nobody likes expense reports, and that's where Concur comes in. We automate expense reports and travel booking to make it easier for the business traveler, and at the same time, we give your businesses much better visibility into that spend so they can control costs before it happens. But don't take my word for it. Here's a short video from one of our customers. Shows you the anticipation of people, and that's important when you go to the sales department and the budget expenses for them. Great. Well, you saw in the video there how he was taking a picture of the receipt. That is a critical part of our system and how it works. In order to get that visibility into the spend, we have to store the receipts in our system. And I don't know about you, but I don't remember what I expensed seven years ago. Well, guess what? We have to at Concur. We have to store that data for seven to 11 years, depending on international tax loss. And that adds up to a lot of images. And what we saw is that with all of that data in our system and the growing adoption in mobile, that we need to make some changes to our environment to scale. One of the areas that we wanted to fix was our storage tier. We were relying on Windows file share technology, and we wanted to bring in an object-based storage system. We ended up choosing Swift, and I'll explain a little bit more about why we chose Swift in a few minutes. But before I do, here's the team at Concur that really made this a reality. Really proud to work with these developers and architects in our company. And this is the solution that we came up with, which gives us a lot more linear processing and the ability to scale every tier of the processing. So why did we pick Swift? Well, first of all, it gives us the ability to choose our own hardware for our data centers to run our storage system. What gives us better cost savings at that tier and gives us the performance that our customers need. And when we grow that system, all of the data gets spread equally across every node, so our customers have a very consistent performance experience. Another aspect that I love is the visibility into the code. There's nothing more frustrating to me than when I get an error message, I don't know what it is. I Google it. Google doesn't know what it is. And then I'm left to use enterprise support or customer support. And most of the time, it just leaves us very frustrated and not knowing the cause of an issue. And we have to find a way to architect around it. I'm looking forward to the opportunity to dig deep into the code and improve the code for the entire community. The last feature, which was really critical to us, and we couldn't deploy in our environment without, is global clusters. And Jonathan is going to come back up and tell us more about that. Jonathan? Thanks, Dan. Thank you. So we just had our eighth release of OpenStack, the Havana release. And there were about 400 features in there. But one of the biggest ones was in the object storage system. And this was an update to how replication and data is managed not just within a single cluster. The object storage system has always had a high level of durability within an OpenStack cluster that's in a region or a data center. But in Havana, this was really improved to where these clusters can now span multiple geographies. So you can have an object storage cluster that has nodes in Portland and nodes in Hong Kong. And replication is managed across both of those environments so that you get an even higher level of durability. But it goes even farther than that. And we have a little animation here, let's go ahead and play that, that demonstrates how this actually trickles down to the individual users. If you have an environment that spans multiple clusters, you can, as a user, just go about your normal daily use of your applications and using technologies like geo load balancing and geo DNS, be routed automatically to the location in your global Swift cluster that's closest to you. So I upload some data and it gets written to Portland because I'm in the US. The object storage system then automatically replicates that data to the other locations in the global cluster. And now we have durable copies in Hong Kong. What's great about it, though, is now if I am traveling, and let's say that I'm in Europe and I want to pull up something from the internet and we all know that what the internet is good for is silly cat photos, right? Then geo DNS is automatically going to route me to the closest location and pull that data, in this case, Hong Kong. So you end up with a higher level of durability. You end up with better performance for your end users. And you can also end up with lower cost for performance across this new feature that's actually built right into open stack object storage now. Thank you. Well, as you heard, it's a pretty incredible feature. I'm really excited about having it in our data centers. What we really like about it is a couple of things. One, it gives us that resiliency across multiple regions for our data. It's very important that we keep all of our images. But also it gives our customers better performance when they're accessing the receipts. We plan on using this technology and other big business segments that concur. And I would like to give our customers the option to choose which regions their data is stored in. So with that, and thanks to the efforts of the community to bring that feature into open stack Swift, and also thank you to Swift stack, we're able to now scale our architecture the way it needs to scale over the next year, or several years, I should say. Sorry. In fact, I did an analysis over what we're expecting for our scale. And within five years, we'll have over 10 billion images stored in our environment. And now we have an environment that can handle that. Great. Thank you, Dan. Thank you. So 10 billion images. And as you were pointing out, your customers are some of the biggest companies in the world. And there are rules and regulations around what you have to do with all of these artifacts to maintain them. And yet you're using something that's really kind of cutting edge technology from an open source project. How do you get the comfort level in deploying that kind of technology? Have you been able to find the partners and the support that you need from the community? Yeah, that was huge for us. I mean, we're not experts at this. We're still learning. And having a strong partner that knew it already made a big difference. And really, we had to trust that company quite a bit because it is such a critical part of our infrastructure. Yeah. And I think that many of these users that we're going to hear from have found partners like Swift stack and others in the ecosystem that have helped them to be able to meet those business needs. So thank you very much, Dan. Thank you. Thank you.