 Good morning, everyone. Very, very excited to be here. I want to thank Mr. Daniel Lai for that welcome, and I want to add my welcome to all of you who have come to join us for the OpenStack Summit here in Hong Kong. We are thrilled to be here. This is our first OpenStack Summit that we've held outside of the United States, and it's looking to be an excellent one. We are going to have over 3,000 people here this week from 50 countries and 480 cities. So every summit that we've had has been an international summit and has had participants from dozens of countries, but this one by far tops them all in terms of the representation that we have from communities all across the world. And that's really, I think, such a great thing for OpenStack and really for the industry overall. One of the questions that I love to ask is, how many of you are here for the first time? Put your hand up if this is your first OpenStack Summit. Wow. I mean, that is a very large percentage of you. I think based off of the registration information, somewhere around two-thirds of you are here at your first OpenStack Summit, and that is a great thing for our community to be able to have new participants, new developers, new users come in and participate in this. A couple of housekeeping items. Your badge that you got at registration has a lot of useful information. Things like the Wi-Fi access information, OpenStack.org-slash-summit has information concerning where the different session locations are. There will be content in this room all day today and tomorrow. And then as you head back towards the entrance of the Asia World Expo, there are breakout rooms that have sessions in them, and upstairs is where the technical sessions for the active technical contributors will be taking place. The badge also contains information about the evening events, and there are always a lot of evening events in addition to these that take place at the OpenStack Summit. It's a great time to mix and mingle and meet up with other members of the community. In addition to the content that we're going to have in this room and in the breakout sessions, we are going to be having design summit sessions here to plan out the next release of OpenStack. And if this is your first design summit, please try to attend the design summit 101 session that takes place at 11.15. It's immediately after we finish the keynotes this morning. It's very important to attend that and understand how the design summit process works, so those sessions can be very productive and efficient through the remainder of the week. And there are also some OpenStack 101 sessions happening at that same time if you're trying to sort of get your teeth cut on OpenStack and understand exactly what this is all about. These events take a lot of effort from a lot of people and a lot of resources as well, and I want to thank our headline sponsors who provide a large portion of the funding that allows us to be able to put these events on. HP, Canonical, Red Hat, IBM are all companies who have been big supporters of OpenStack and are the headline sponsors of this summit. And you'll get an opportunity to hear from each of these companies over the next two mornings of keynotes. And then we had a new program this time around that I wanted to call out as well. We implemented a travel scholarship program to help attendees who might not otherwise be able to come to the summit because of the cost of traveling be able to make it here. And Intel graciously sponsored this and supported our efforts and allowed us to be able to bring a number of developers and community contributors from all over the world here to Hong Kong so they can participate in these important sessions. So we're thrilled to be here in Hong Kong, but in OpenStack we're always looking forward and I'm not going to hold you guys in suspense about where we're going to be for our next summit. I'm going to go ahead and get that out of the way. I kept it to the end last time, but we're just going to go ahead and put this up here. So May of 2014, we'll be back in the US in Atlanta. So I'm glad I heard some applause for that. I know Atlanta, you know, it's maybe not as exciting as Hong Kong, but it's a great city and we're going to make it even greater while we're there in May of 2014. But that's not all. I'm also going to tell you where we're going to be a year from now, which may be more exciting. So one year from now, in November of 2014, we will once again be taking the OpenStack summit on the road and we will be in the beautiful city of Paris, France. And hopefully we will be able to see many of you there and also a lot of new faces. So as we saw, many of you are new and that's really fantastic. This is the best place in the world to be if you want to get immersed in OpenStack and you want to learn about the software in the community. But just to sort of at a very high level, just kind of level set a little bit, OpenStack is software that's developed by an open source community and used to build clouds for service providers and enterprises all around the world. And it's very powerful software that's been developed by over 1,600 individual contributors and over the past three years. And we're going to hear from dozens of users this week who are using this software for a variety of workloads. At a very high level, it's made of different components to manage pools of resources, whether that's compute, storage, networking, and it ties them all together and provides a set of APIs and management tools so that you can manage those resources in an automated way as efficiently as possible, tie them into other systems, build new tools on top of them, make it all more valuable. And that in a nutshell is what OpenStack is. As I mentioned, there's OpenStack 101 sessions that are happening at 11.15. And there are sessions throughout the week that will dive into all of the details of the different components of OpenStack. So look at your badge, go to the schedule, and find the content that's going to be most useful for you. So you can really dig into this. As I mentioned, OpenStack is built by a global community. And in that community, we've seen phenomenal growth. We have an extremely large and diverse set of contributors who help build the software. But really, this mission that we're on, it's not just about building technology for technology's sake. This isn't a science project. It's about making a difference in businesses and organizations all over the world by providing them with software that can really have an impact for what they're trying to do. And in the technology industry, we've seen a few major shifts that have had incredible impact on our businesses and on our lives. And OpenStack, we're starting to see it have an impact at many levels in business, in the IT industry at large, in the way that software is developed. One of the things that I hope you can learn about is the process for how OpenStack software gets developed. This community has developed tools and a process that has scaled very rapidly and has provided an amazing capacity to add new contributors, new members, new features, and maintain a high level of testing and stability. And to me, it's one of the most exciting outputs of OpenStack. And so OpenStack is having an impact in a lot of different ways. In Portland, six months ago at our last OpenStack summit, we had some really great users who came and talked about what they were doing with OpenStack. And we had some very large brands in the US like Best Buy and Comcast and Bloomberg that came and talked about their usage of OpenStack. And we're very fortunate to have some more individuals who've come here today. And they're going to share their stories about what they're doing with OpenStack. And the thing that I love is in every case for all three of these users that we're gonna talk to, we have an individual here who's a leader in their organization. And they are taking OpenStack, and they're implementing it in the organization to have a positive impact on their business. So let's go ahead and get started with our spotlights this morning. Shutterstock is a company that if you work in the creative industry, you're probably familiar with it. And I'm very excited to have the VP of Technology Operations at Shutterstock here to talk with us today. So please help me welcome Chris Fisher. Morning, everybody. So a quick show of hands. How many folks in the audience are familiar with what Shutterstock does and what the business is? Great, so a fair amount of you. For those of you who aren't familiar, Shutterstock is a marketplace where photographers, videographers can upload their content. And we provide an opportunity for them to be able to sell that content to a broader market segment. People who need stock artwork for creating Christmas cards or a PowerPoint presentation, or doing something like creating a catalog. Before we kind of get into that a lot, I want to talk a bit about what OpenStack is doing for our business. And I'll give you a little bit of a brief background in myself, as well as Shutterstock's founding beginnings. So first a little bit about me, I've been building scalable systems for about 10 years, as well as the teams that are responsible with managing those systems. From the get go, I've always been someone that's been really interested in high levels of automation and being able to build a very strong operational organization that can add business impact, not just, you know, manage your environment. I'm a huge, huge open source enthusiast. I mean, there are very few times that you can get me to buy a black box solution unless it's really, really exceptional. And that comes from a real belief that, you know, if things really get tough, you can control your own fate, get into the source code, figure out what's going wrong, and really solve your own problems. One other key point is that I have a pretty deep systems and network engineering background. I'm an ops guy by trade. The only language that I've coded effectively in is C, which is pretty much irrelevant, you know, in a modern web company. But I'm going to talk a lot about building the type of stack that your developers want to interact with. I really believe in it. It's done great things at other companies I've been at and at Shutterstock. And effectively, I think that's one of the key cornerstones of why OpenStack is something that's super effective for us. As a quick aside, I now spend most of my time, it seems like, learning how to use Excel and PowerPoint and try and explain to the rest of the executives and, you know, people out in the industry, you know, why these cloud systems are so important and so efficient. So, a little bit on Shutterstock's founding beginnings. We were founded in 2003 by our CEO, John Oringer. He was our first developer, which from the beginning really created a dev-centric organization. It's pretty cool. From inception to our IPO last October and beyond, we've remained very focused on creating a great, great technology platform that developers really like interacting with. Our tech stack is another kind of note, predates the modern cloud. AWS was launched in 2006, maybe, I believe. And effectively, a lot of the modern technologies for building a cloud or interacting with the cloud just weren't there when we were already handling pretty large volumes of traffic. So, a lot of the needs that we have are solved by OpenStack that provide us an environment that we can create a super usable cloud for developers, but at the same point help us alleviate certain constraints that come from having an application that's been around since pre-cloud days. So, inside our organization, we have kind of this developer ethos. And this isn't it. I wish it was this simple. But if you read through that document, you'll find that there are a couple of key themes that just happen over and over again. One, we build things that are core to our business. A lot of organizations really focus on the product, and I think that's fantastic, but we really ask ourselves if this functionality is core to our business, orchestration, or deployment, or the ability to speed development, we want to be building that. We don't wanna buy an off-the-shelf solution. Secondly, we wanna stay open source. Again, I kind of talked a little bit about, when things get rough, it's nice to be able to read the source code. But beyond that, there are great recruiting efforts and great capabilities that come out of using community-supported software. It's just something I believe so much in, and it's treated us really, really well at Shutterstock so far. Three, we want to invest in things that create collaboration and innovation among all the individuals at our organization. People don't talk a lot about how much tooling or your platform is important in that. It's really easy to think about process, or being agile, or having can-band-style-type groups to really help foster collaboration and innovation. But if you get inside a lot of developers' heads, they think about collaboration and innovation via pull requests or working within a technology framework, everyone being able to write and read code. And this is another one of the key points why OpenStack is pretty great for our environment. And fourth, I think there's a lot of people out here who probably agree with this, just automate everything. If it's something you don't need a human to do it, don't. You'll find something better for that human to be doing other than sitting there and running scripts recurrently at midnight every night. So a little bit about the platform. It seems pretty easy to upload and download photos and videos, but it is a pretty large system that we've created at Shutterstock. It's got thousands of nodes across multiple data centers. We're managing several petabytes worth of storage in an open-source technology called MogulFS, which is backed by all kinds of heterogeneous disk from white-box servers to appliances that we buy from a company called Co-RAID using ATA over Ethernet. We also collect over a terabyte of logs every single day. That's about 70 times the volume that the Hubble telescope downloads to Earth. I realize it was put in space 15 years ago and it's in geosynchronous orbit, but still I like that stat a lot. And on the outside, as well as the dev side, we remain being pretty language agnostic. We code in multiple different languages. The key takeaway from our application stack is we really try to go fast. We're pushing code hundreds of times a week and we needed the type of platform that was gonna allow us to do this and get lots of dev interaction. So a couple of challenges, we were trying to work with creating an environment that worked in low-latencies, AWS. You can have pretty high latency between nodes. Open stack, being able to create a cloud environment where things are sitting right next to each other, we could kinda conquer a lot of network latency problems. We also wanted to create an environment where the culture and the workflow of both operations teams and dev teams really was identical. Read the code, the documentation is the code, and interact with each other in a way that developers really understand. The goals, of course, are the same as many of you guys have. Have it be resilient. And the other ones that we care about is keep it dev-centric, create an API-driven platform, and work as much as you can with being open source. So this is where everyone's kinda screams, like dev ops, oh, dev ops is the way to do this, and I disagree. I think dev ops is a great idea, but when you have a singular dev ops team, you've just moved responsibility to another group of people that can also write some code. What we really want is a platform that creates a culture and a workflow where everybody effectively plays that role of dev ops. We want our developers, as well as our operations folks, writing code, sharing code, sharing knowledge, whether it's application or the actual infrastructure platform. So, you know, ultimately, what these things kinda create for your business is an environment where you have a super, super strong staff. Everyone can contribute back to the org. Everyone can write applications. Everyone is able to triage the same, communicate the same. We go crazy collecting metadata from all of these instances to look at efficiencies and resource planning within the groups. And it's a really powerful system where you can get everyone really working with the same platform, application side and dev side. So, you know, that's effectively, you know, on this slide, when we really looked at what platform was gonna help us do this the most successfully, we went the route of OpenStack. It has great community support. We have the ability to get in the code and get 30. Everyone's building against an API as opposed to looking at using config management systems like Puppet and Chef, that may be a part of your environment, but, you know, building against an API is something that developers are gonna embrace a lot more. Everyone can read the code and effectively, it encourages both ephemeral use and things that don't have persistent data as well as allowing you to integrate with systems that do have persistent data. So, if, thanks, if everyone has any quick questions for me, you can tweet stuff at me or send me an email. It's just chris at shudderstock.com. And thank you very much. Thank you, Chris. So, don't leave yet. So, when we've talked, one of the things that I found really interesting is, you know, you're obviously a technologist and you were throwing out some great stats about the kind of environment you're running, but the thing that really hit me when we talked before was, you have a business need, which is you have this application that has specific requirements that maybe don't fit into a menu-driven type technology offering, but you have developers who are, you know, developers, and they want to have an agile environment to work in. And so, how does OpenStack kind of allow you to meet both of those needs in your business? Absolutely. So, one of the key points that's been OpenStack so successful for us is that at first, we thought we could solve this with just config management. We laid down a big puppet tree and tried to teach all the developers how to work with a DSL or write scripts to interact with controlling their environment. And it had some good success, but really, they kind of hated it. They were like, I just want an API to do this thing. And so, effectively, as we've been transitioning our provisioning systems over to using OpenStack, we're able to get everyone to really be excited about, I can just write code that's gonna call the OpenStack's API, interact with it, provision my VMs, do all this work that before, they had to do in a language that was a little foreign to them and didn't make a lot of sense. And at the same time, we keep our ops team very happy in that we know a lot about what the metal's doing. It's not completely abstracted into a way that we feel we're losing control. And so, it's really helped bring those groups together in just a common language via being API-driven. So, it lets you keep your application happy, your ops team happy, and your dev team happy. Correct. All right, well, thank you very much, Chris. Thanks. So, Shutterstock is focused on the needs of creative types and including individual creatives. The next user we're gonna bring up is a company called Digital Film Tree. And this is a move from individual creatives to big budget media. And this is gonna be an exciting session that we're going to have brought to us by the CTO of Digital Film Tree, Guillaume Obachan. So, I know it's an odd place to start, but I wanna talk about faith for a second. And I wanna talk about faith because we have an issue in our industry right now. And that fact is that we all have clouds. We as a post-facility have clouds as a VFX, and as we distribute content to a VFX facility or a sound facility, even back to a content owner like Warner Brothers or ABC or Disney, everyone has a cloud. The content owner, even individual companies, have siloed clouds within that company as they distribute back to archive and distribution. And then finally, once we get to digital distribution, we have Amazon, Hulu, Netflix, all these clouds that we're distributing feature films and television to. As content flows through all these clouds, these security needs are changing and the financial needs are changing. So, we have to have some faith that there's gonna be a fundamental change in our industry because in reality, none of these clouds are connected. So, we had to embrace an idea and not only look at our challenges as a business, but our challenges as the entertainment industry, as a community. So, we wanna talk about what our future cloud is because our future cloud isn't our siloed cloud. It's a community martini. So, as we looked for a solution to not only embrace cloud, but embrace cloud from a community perspective, we were looking for something that had open standards. So, we could incorporate multiple software vendors. We didn't feel like we needed to accelerate or push an ideology that was only our own, something that was open. We needed to share metadata through APIs with multiple software entities that were building their own clouds. And we did an easy way to have templating so that people who were not necessarily familiar with standing up their own clouds could share a common cloud infrastructure. Security was very important to us and it's very important to the entertainment industry as a whole. So, we wanted one user identity, this idea of federated identity so that we could have a single user, a single authenticated user. We would know that user from private cloud to public cloud and back to private cloud. And also, the idea that you could migrate that identity so that all these interconnected clouds could know who would have permission to a given asset. And we had to have ease of migration. So, once we started to talk about private cloud, public cloud and content flowing between private cloud and public cloud throughout a cycle of production on a television or film, we needed that ease of migration. For us, the key to our business is a files journey. A files journey from camera and acquisition through the creative process and editorial and manipulating that content into final distribution. So, really it's a files journey. And that files journey is important when you start to talk about public and private cloud and how that flows from one aspect to the next. And really in the end, it was deployment, deployment, deployment. We're the entertainment industry. We're not an industry of smart people like you in the audience. We're simple people with simple needs. And the bottom line is we're creative people. So, we needed a way to package deployment in a way that a studio or a content creator could deploy themselves. And really at the end of the day, what we ended up with was open stack as a private cloud and rack space as our public cloud. So, and we're sharing content between the two. And an example of that is a little unair clip from Modern Family. I didn't know what you wanted to drink, so I just got you the soda. That's fine, thank you. Cam, what did you do? I did exactly what you did because I know you so well. I didn't shake the soda. Then you have nothing to worry about, so go ahead and open it. I shook it, okay? I shook the soda, I shook it up. Are you happy? It was petty and stupid and awful. I'm sorry, damn it. So, currently we're running our video streaming software on both a private and public open stack. And Modern Family has done that way. We did a feature this year called Her, which also used our software. And really what this software is, is it's collaboration software. So, when we think about cloud or we go out to an individual or a studio and talk about what cloud means to us, cloud means collaboration. It means creative collaboration. And with that, I really wanna thank you, the developers, and I owe you all a big hug. Every single one of you who contributes to OpenStack, I owe you all a hug, so you have one free voucher for one hug from me, if you see me in the hallway. So, we are deeply indebted and are gratefully contributing back, and encouraging this idea of open source within the entertainment industry. Thank you very much. Thank you, Guillaume. So, a lot of people say that hybrid cloud is just a myth, but you guys are doing it. Absolutely. That's great. That clip, I didn't recognize that clip. What episode is that from? That's from episode, season five, episode six, which has yet to air this year. Wow, okay. So, you guys saw it here first. Unaired footage from Modern Family. So, thank you, Guillaume, and thank you, Fox, for letting us use that as well. Thank you very much. So, our third user that we're gonna 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 OpenStack storage in some interesting ways, and I'm really excited to bring up senior manager from Concur, Dan Wilson. Go get him. Thank you. Really excited to be here today and have the opportunity to share the story about how we brought OpenStack 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. 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 laws. 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 a 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's gonna 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 U.S. 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 wanna 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 gonna 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 in 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 their receipts. We plan on using this technology in other big business segments at 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 gonna hear from have found partners like Swiftstack 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. That was an interesting range of use cases with large scale compute services, large scale storage services, hybrid cloud across a number of different industries. And as we go through this week, there's going to be a lot more content that's delivered out there. We just heard from these users how OpenStack is having an impact in their business every day. And we're gonna hear that from dozens of other users. And tomorrow, Mark Collier, the COO of the OpenStack Foundation is going to be kicking off the keynotes in the morning with a session that spotlights some outstanding users from China specifically. And so come back tomorrow because that one's gonna be very interesting. But you know, if managing large scale data, if running application infrastructure or doing software development as strategic for your business, then OpenStack is a platform that can have an impact for your business as well. And we are seeing that over and over and over again. And at this event, at these summits, we come to learn, we come to meet and to spend time with the community, but we also come to plan the future. And I just wanna leave with a couple of thoughts on that, on the future. Because there's a lot of talk about the future and about what OpenStack is going to become. What is it going to be? And in a lot of those discussions, they're filled with industry jargon. You know, you see a lot of terms that get thrown around, a lot of acronyms. And ultimately, I think that the terms are the least important part. What really matters is that we are engaging users and we're solving their problems, we're meeting their needs, and we're building software that lets them go out and do the things they need to do in their business. And if we think back to the mission that OpenStack laid out years ago, it's to produce the ubiquitous open source cloud computing platform to meet the needs of public and private clouds regardless of size. And that is a very broad mission, it's a very big mission. But we are actually doing that. And that's really incredible. That's what this community has been able to do over the past three years. And there are gonna be debates about all kinds of things. You can look at any large community, whether it's Android or iOS or Linux, whatever it is, there are always debates about where they begin, where they end, what category they fit into. Every ambitious project is going to have those debates and it's going to evolve over time. But I think that as long as we can focus in on users and on their needs, on creating a platform and an ecosystem, then OpenStack is going to continue to grow and to have a lot of success. Because users, they don't obsess about SaaS and Pass and IaaS and those kinds of things. They obsess about solving their problems. And right now they're doing that through a combination of OpenStack software, of added services on top of that, of tools that they build, tools that the ecosystem builds. And so what we are seeing is that the community and the process that we have in place in OpenStack is really doing amazing things for our users out there. Because OpenStack is a place where individuals can come and have an impact and that is why OpenStack is having an impact. Anything that has an impact in this world, ultimately it comes down to the individuals who are taking part in that, driving it forward and making it happen. And this community has developed an amazing system for enabling people to do that. So this week, we're gonna have thousands of people from 50 countries that are going to be here building the software that's powering hundreds of clouds, doing millions of dollars of business and it's all going to be happening right here in Hong Kong. And that to me is extremely exciting. So I think that just in closing, what we are seeing is the power of open communities, open source, open platforms and open systems. Mr. Daniel Lai, who's the government CIO for Hong Kong that introduced us this morning, you might have noticed that he had his notes on a Nexus 7 and we met him last night at an event, a community event and walked up and shook his hands and he was really excited and he reached into his suit jacket pocket and pulled out his Nexus 7, which I was like, how does your suit jacket have a pocket that big? But he was very excited because he's on an open system now and he talked about how important open systems are from a government perspective, from an innovation perspective. They want to encourage startups and businesses to thrive in Hong Kong and they want to encourage open systems as an enabler for all of that. And that's what we see across these open systems. You think about Linux and Android, those are technologies that knowingly or not we interact with every single day and more and more, OpenStack is becoming a technology like that. It touches our lives almost every day, whether you're doing a transaction on PayPal, whether you're watching a network television show, whether you're filling out your expense report. And right now, this week, Hong Kong, the OpenStack Summit is the center of it all. So you are in the right place at the right time. So thank you for being here. We're all very excited to have you join us this week as part of the OpenStack community.