 Good morning OpenStack community, thank you very much for traveling all the way to the fine city of Atlanta to be with us this morning. To kick things off today, please welcome Jonathan Brice. Good morning everyone. Thank you for joining us here in Atlanta for the OpenStack Summit. It's May 2014. It's quite a crowd we have here. This is very exciting. We are here in Atlanta and we have about 4,500 of you who are going to be joining us this week. So by far the largest OpenStack Summit yet. We work with a production crew to put these shows together and they started working with us a year and a half ago and at that event we had 1,200 people in San Diego. So in 18 months, from 1,200 to 1,400, quite a jump, bigger audience, they've got me hooked up with two mic packs now for some reason. So we're here in Atlanta and I actually used to live in Atlanta. I was thinking about this when I got into town. I lived here about 19 years ago and this was actually the place where I did my first professional software development work. I was young and dumb and I didn't charge enough money. But it was the mid-90s and the internet was just getting started and it was really exciting. And so now here we are back with a whole crew of OpenStack developers, operators, new users, potential users. It's really exciting. And our events are really fantastic because of the makeup that we have of who's here. We have a lot of great companies who sponsor the show and allow us to be able to do this and put it on. So we have over 90 companies who are sponsoring this summit this week. So thank you to all of our sponsor companies. And I want to call out specifically VMware who sponsored our OpenStack travel program. This is a new initiative that we started six months ago and we are continuing that thanks to again the strong support of some of our ecosystem companies. This is a program that allows us to fund travel for OpenStack community members who may not be able to make it to these events themselves on their own dime. And it's really important for us to make sure that if you contribute, if you participate, if you are part of the community and adding value to OpenStack, that we find ways to allow those people to be able to be here during these summits. So thank you VMware for sponsoring our OpenStack travel program this time around. A couple housekeeping items. You should have a badge. If you were not able to get a badge before we started and you jumped the rope line and ran down the stairs, please go back and get one later. You'll need it this week. The badge has obviously your info on it. On the back, a lot of information that you might need to connect to Wi-Fi, win the schedule of events. This actually pulls out and unfolds and has maps and all sorts of things. So useful information in your badge here. And just to talk a little bit about where things are, we are on the ground floor level here and we have several floors of content. It's a big space. There are maps. We have staff around, ask for directions if you need help. I think you'll find that the layout is pretty simple once you get your head wrapped around it. We have a new mobile app. If you go to openstack.org slash summit slash mobile, you can find our guidebook mobile app that has maps and schedules and a lot of information in there that will help you navigate your way around. And there's a web version as well. Something else that's happening this week that's exciting is our summit is really multiple events in one. We have conference sessions that talk about different technologies, different use cases, strategy, business concerns. We have the design summit, which is a really key part of this event. For those of you who are here for the first time, the design summit is a collection of working sessions where the developers get together. They discuss project issues, software issues. They plan out the roadmap and prioritize the work for the next six months for the next release. And those design summit sessions are really meant to be productive working events. If you want to go attend and participate, you're certainly welcome to do that. But please keep in mind that this is critical time for our development teams to focus on the work that they need to do to keep making OpenStack great. The other thing that's happening this afternoon and on Friday is an ops meetup. And these are similar sessions to those design summit sessions. They are working sessions for operators who are running OpenStack, making use of OpenStack so they can get together, share best practices, talk about how they are dealing with the different deployment models and the different things that they need to do to make their businesses successful with OpenStack. And that's new this time around. So if you are an OpenStack operator, please participate in that and give us feedback on it. We want to make sure that you're getting value out of that. I was looking through some of the registration numbers and I think we have somewhere around 600 or so operators here at this event. So that's a really good turnout and hopefully we can serve you better this time around with some good content. We just had our Icehouse software release and it was our really great software release. It was very much focused on operational issues, kind of maturing the software, maturing the processes around how it gets developed and tested. And it was really exciting to have Icehouse come out a few weeks ago. Tomorrow morning, Mark Collier is going to talk a little bit about some of what's in Icehouse and some of the technical details around it. And I wanted to actually focus a little bit on the people who built Icehouse. And there was some activity on Twitter last week and some people were saying that we should have contributors come up on stage for Icehouse. I think we might have too many of you to get you on and off stage in a timely fashion. But I do want to ask if you made your first contribution to OpenStack in the Icehouse release cycle, could you please stand? This is really exciting. Stay standing, actually. So the contribution process in OpenStack is actually something that is really excellent. Code comes in. It gets reviewed. It gets tested. It goes through this process. Just as important as those incoming contributions are the reviewers and the process for checking that code as it comes into our source trees. So if you are a first-time reviewer in Icehouse, please stand as well. Yes. Thank you. Now, not as many first-time reviewers. We need more people getting in and pitching in on the reviews. So that could be a goal. If you are a contributor to OpenStack and are looking to take the next step, maybe in the Juneau cycle, you can pitch in and start helping with code reviews. And finally, just anybody who got a contribution in Icehouse, please stand. Thank you, guys. This is part of what makes this event different. This is an event where the practitioners and the software developers are here together to make OpenStack better. And so thank you, guys, very much for your work in Icehouse. That was only about half of the people who contributed in Icehouse. So that's your software development team, OpenStack. So thank you, guys, very much. Talking a lot about Icehouse there, Icehouse is software. And OpenStack is software. But I wanted to talk a little bit about some larger concepts today and a little bit about how key software really is in our world. Software has completely changed the way that we communicate, that we make decisions, that we iterate. Even the way we build physical things is different now than it was a few decades ago. And it has changed not just how we work, but it changes what we work on. It changes the cost of working on those things. And it allows us to do new things that we haven't been able to do before. I was talking about the contribution process for OpenStack. The contribution process for OpenStack is software. It's a number of open source systems that our core infrastructure team has integrated, expanded on, created new tools. And it allows us to take in contributions from thousands of developers all over the world to test them, to review them, to maintain a high level of code quality as all of that comes in and to keep on hitting our release dates and bringing new features in. And it's very powerful when you think about that process. It's an incredible collaborative global process that's really made possible by software. And I was thinking about, you know, imagine if we were in a pre-software era. How would that work? You know, let's say that we're in the 1800s. And you know, this is just for hypotheticals. We need to do a code review in the 1800s. So you sit down, you're a developer, and you know, perhaps you are based in Asia. We have a lot of contributors in Asia. You take out your quill and your ink and you spend a couple hours and you write out your code submission. And then, you know, you put it on a ship because it needs to be reviewed by a core reviewer in Georgia. So your two hours turns into two months and two hours. It gets to the West Coast. They put it on a train, heads across the country, stage coach, makes its way to your reviewer. He looks at it and you had some trailing white space. So months later, you know, you finally get the notification. And you just, you know, you think about the turnaround cycle on something that simple. I mean, that is, it's a little bit of hyperbole, perhaps. But you know, that is really an incredible shift in how the world works today. And our code review system is something that is, that's really incredible. If you go to review.openstack.org, you can actually see how it works. It's real time. It's live. You can see code reviews coming through there. People are pushing changes up all the time, reviewing them, making comments. And the whole cycle just turns so much faster. And that's a, you know, a very small example. But that's the power of software. And I think, you know, kind of a concrete way. And this is not something that, you know, is brand new. People realize this. And if we think about the technology industry, what have we been hearing about? Software-defined networking, software-defined storage. It's expanded to the software-defined data center. But I think that really, even that, is kind of boxing it in too much. Because if you think about what all of this enables and where we're heading, we're really living in a software-defined economy. It touches every business, every industry. And in the software-defined economy, every company competes with a startup. The barrier to entry in every industry is dramatically lowered. And what this means is, you know, if you are a very large company, that isn't necessarily a benefit to you. That's not a competitive advantage. In fact, that can be a disadvantage. You know, if you are in the banking industry, you're having to compete with all kinds of technology companies now. Big media, having to compete with all kinds of startups and technology companies. I think Netflix recently won an Emmy. This is not just about delivering on-demand video. They are producing award-winning content. The automotive industry, you have Tesla. And you know, Elon Musk, I think, is an amazing innovator. He is not happy with just taking on the automotive industry. He is now taking on the Air Force. Even the Air Force has to compete with startups. And it's because, again, back to this technology shift, if you think about that first code review example, the expense and time and effort is extremely high. And when it's expensive to do that, it keeps experimentation. It keeps innovation low. When you can lower that expense, you can iterate so much more rapidly. And this is just, you know, it's kind of obvious. But when you can take a week and try something and find out if it works, you're much more likely to go out and make some bets and see how it works, see what works, what doesn't, than if it's going to take you a year to do that. What we're talking about is really increasing the velocity of money. So, you know, software is key to that. This is a little snippet from an OpenStack project. Can anyone recognize it? Swift, yes. It's the container server. So software is really key to that. And software is built by developers. We just saw a number of those who worked on the Ice House cycle. But it's not just about the software. You have to have an environment that can match the velocity of your software development to get that out in front of your users and your customers. This is just as important as the developers, as the software. You have to have the people and the systems that give them agile infrastructure. And if you have the software development practice and you have software developers who can turn out great code, but you don't have that agile infrastructure, it's kind of like having a Formula One car, a high performance vehicle that doesn't have any wheels on it. It's an amazing piece of machinery, but it's not going anywhere. And so in the last five years, six years, we've seen a lot of growth in the agile infrastructure space. You know, this started, of course, with Amazon and their web services offerings. They really, I think, have pioneered a lot of approaches that people have adopted and seen great value come out of that. And OpenStack, I think what's really incredible is we've gone from a model where six or seven years ago, basically the only place that you could get that kind of agile infrastructure was from Amazon or from these services, OpenStack has opened that up and made that possible for so many more organizations. So many, many, many more organizations are able to take advantage of these capabilities. And for many of those organizations, OpenStack is the engine of the software-defined economy. At our events, we often have users who come out and speak with us. We have users who participate throughout the week. And in between the release cycles, we have user meet-ups. We have operators who are doing all sorts of things to help build the community. But I think that what's interesting is it's not just about what these people are doing inside of OpenStack. And you'll see these illustrations all over the event this week. All of these illustrations are actual OpenStack users and operators who are doing real business on top of OpenStack today. And there are some different signage and light booth areas where you can go and you can read about some of their stories. But what I think is really amazing is that in addition to what they're doing in OpenStack, in addition to how they are embracing this agile infrastructure, they are really thinking at a higher, more strategic level and they're changing their businesses. They're thinking about things in a different way. It's a different consumption model. And I love to see this. It's no longer just passive consumption of software that some vendor sells you on a two or three year cycle. These users are getting involved and they're helping to drive OpenStack. They're helping to change their businesses. And they are really making a difference in the industries that they plan. And that's really exciting to see. We have seen more and more of these users and operators participate in OpenStack. And so one of the things that we wanted to focus on this year and at this event is getting them more involved and connecting them more and more. And when we were doing that, we wanted to think about some way to describe them, some way to talk about them. I used to run a lot of infrastructure. And one of my coworkers, he used to say I was basically the plumber of the internet. It's a very vital job, but it's not necessarily glamorous. And so we were thinking, what is a good description of these people? And what we have started to call them are super users. The super user on a system is the administrative user with the highest level of access. And in many cases, these OpenStack operators are people who are super users on their systems inside of their data centers. But I think the concept is bigger than that. Because if you look at what they're doing inside of their organizations, they are using their access, they're using their capabilities to bring about change and to make their organizations better and more competitive in the software-defined economy. And we've had some of these users who have spoken with us before. Last year in April, if you were at our event, you might have heard from Bloomberg, Praveer Chandra, who spoke about the work that Bloomberg was doing. Comcast came and did an awesome demo. In that time, Comcast has gone from their initial deployment to being one of the top 20 contributing companies in Icehouse, which I think is really impressive. And it speaks to their commitment to OpenStack. But you don't have to be a code contributor in order to be a super user, in order to have an impact. When we were in Hong Kong, we heard from a number of companies that are based in China and other places in Asia, including Eric Yi from C-Trip. And he talked about some of the changes that he was driving inside of his organization. In addition to applications, the traditional applications, he demoed a great mobile app for their online booking software. He talked about how they were using OpenStack to overhaul their desktop service inside of their help center with 16,000 agents. And they were looking at cutting their costs in half. So that's a big change for his organization. And we have many, many more of these super users. They're here this week. I hope that you can find some and meet them and get to know them. But I'm excited to have a couple who are here live and in person and who are going to be talking with us today and telling us a little bit more about what they do. And in the past, we've done some kind of rapid fire presentations with these users. But today, what we're going to do is sit down and we're going to have a little bit more of a conversation with a couple of users. So first of all, I'd like for you to help me welcome to the stage the head of Private Cloud Enablement at Wells Fargo Bank, Glenn Ferguson. Love the music. Ben Horwitz would be proud of that. I love Cool J. These shows have gotten so much more polished. I mean, did you see that? I walked over there and all of a sudden, bam, chairs on the stage. So, Glenn, thank you for joining us. Yeah, glad to be here. Could you tell us a little bit about your background? I know you've been involved in infrastructure for quite a while. Sure. History repeats itself. It's kind of a common term. If I rewind 15 years ago, I was probably like a lot of the contributors here in OpenStack, except I worked for a small startup called LoudCloud where we were trying to automate operations. At the time, it was data center, storage, cooling. But we really had a different approach than how we wanted to automate operations. And to your point about the super user, being an engineer, we would sit down with our network operation staff and say, show us what you do. How do you build machines? How do you monitor machines? How do you configure these machines? And it was our job to automate what they did. 15 years ago, VM, virtual machines weren't as prevalent. They were kind of in a test dev mode. And XML standards were kind of the open source of the day. The big focus is on. We tried starting DCML, which was data center market language, which was our version of open source, of trying to get everyone who played in the data center space a common way to describe infrastructure so we could perform that level of integration. So I picked up a lot of experience there, carried that through, spent some time at Netflix, director of cloud engineering, spent some time at HP Cloud Services. And what really attracted me to HP Cloud Services was their adoption of OpenStack. It reminded me of the early years in loud cloud and opsware and what we tried to accomplish. So I've had quite a bit of experience in this industry, and I'm looking forward to continue to be involved in it. Yeah, that's great. So you are a bank, obviously. Yes, we are. You're working there. And why do you think that the financial services industry and other organizations like yours are taking advantage of OpenStack? Yeah, well, I think you touched upon it a lot in the presentation. Your infrastructure has to keep speed with software. Without that, to your point, that the software isn't good. So there's nothing specific to the banks that a lot of other people aren't driving forward, except I would say compliance and risk. I'm a Facebook user. I use Twitter. For me, signing up is fairly simple. I give an email address. I give some voluntary information, and then I'm on my way. When you look at the financial institutions and what they do for the economy and the government as a whole, know your customer, the amount of information we must collect, tying someone's financial instruments to a financial system, there's just a different amount of risk that's involved with that, a different amount of focus. If you look at what's going on in the world today and what the president is doing with Russia and trying to put some sanctions on them, a lot of that is financial driven. So there's a lot of focus on compliance and risk mitigation in that environment. So for those reasons, I think having control of kind of below the line in what we do, below that cloud, has an effect to ensure that we're always compliant. Things are always backed up. They're securely stored, et cetera. So that might be the one difference from a financial services perspective. But the other drivers, why wouldn't you manage infrastructure this way? It's a better way of doing things. It's the consumerization of IT outside of work. These developers can use Amazon. They can use these public clouds. They're much more efficient with it. But yet when they come into this enterprise environment, they're just kind of bogged down and baffled as to why they can't get that same level of efficiency. Right. Yeah, so there's still the desire for that same level of kind of control and flexibility. But how do you balance that with the needs that you were talking about for compliance and the regulations? And where does OpenStack fit into bridging that divide? Yeah, OpenStack is a cornerstone. I mentioned the line. And what I mean by the line is the API. Above the line is where the developers are interacting and managing infrastructure through software and tools that they use today. But below that line is where the cloud operator plays. Below the line is where you define your quality of service, your racks of hardware, targeting workloads. But that's also where we build in compliance. We are fundamentally different than a public cloud provider. And I can say that because I've played in both worlds. Public cloud providers, I can give you a VM and you're on your way, here's what you need to do. In a highly compliant environment, it's much more than that. It's patching, it's auditing, it's reporting, it's compliance. So using OpenStack below the line to enforce some of these best practices and securities is great for us. The developers work above the line, they're using web services, they're managing infrastructure through software. But yet below the line is where we build in and bake in the compliance that's needed in this environment. So how has OpenStack, you talk about above the line and below the line, how has it changed your vendor interactions and how you sort of have vendor relationships and drive those decisions about that technology below the line? We certainly let our vendors know that we are deploying OpenStack is kind of our cloud operating platform for lack of a better term. And our desire for these vendors to fully embrace and support that. So I would say, if I had to sum it up, that's probably the way that we engage our vendors is being upfront, let them know where we're going, how we're using OpenStack, why we're using OpenStack. And that's the area that we wanna drive forward. Right. Now, we know that there are financial services organizations that are using OpenStack, but you are the first one to actually join us from a major bank and talk about what you're doing. Why are you doing that? Why are you here today? I mean, I'm glad you are, but... Yeah, I know, I'm glad. And I think it gets back to the previous question. This is a community. I was hired by Wells to run a business and bring the best solution forward. And it's in my best interest to be at these conferences and let the community know that this is what we're using, put our use cases out there. Everything that happens in parallel with Wells Fargo could happen in parallel with many other engagements and companies. So it's the collective mass of the community that everyone benefits from. I'm not a developer anymore. I couldn't have stood up earlier when it contributed to Ice House or anything. So this is my form of contribution. Letting the community know this is very valuable. Letting the community know what our use cases are. And we're trying to run a serious business on this technology. So that's the primary reason that I'm here. So my last question, as we look at this shift that's happening in the industry, do you feel like inside of Wells Fargo, the infrastructure, the backend systems, this technology stack that we're talking about is really becoming something that has strategic value to the larger organization? Most definitely. The agility, the speed, really allowing the developers to modify that software in lockstep with the infrastructure, speed to market. We have competitors. We're a large bank. We have targets on our back. There's disruption happening everywhere. We're doing our best to stay competitive on all levels. And this is certainly, technology is a key component of any business, certainly financial services. So this is something we have to do to remain competitive and be flexible and agile in this environment. Great. Well, thank you very much, Glenn, for joining us. All right, thank you. Appreciate it. Thanks, everyone. We have another user that is here to speak with us today. And he comes from a company that has one of the probably most beloved brands of all time, the Walt Disney Company. Please help me welcome the Director of Cloud Services and Architecture for Walt Disney Company, Chris Lonnie. Chris, thank you for being here with us. Could you tell us a little bit about what you're doing at Walt Disney Company? Sure. I normally actually tell a story in response to that question, but I'll give you the quick version. You can go home and go to WordPress and register and build out a little website. You can go register DNS, license art, buy some plugins. You can spend 20 minutes with a credit card and have a completely set up web presence. You can go to work and you can submit tickets and fill out process exception request forms and get your boss to respond to an email and click something and you can wait and wait and wait. As an entire industry of technologists, we have spent a long time empowering people much better when they go home than when they come to work with their technology. And what I've been trying to do is change that. Inside of Disney, outside of Disney, like many others I'm sure in the audience are trying to lead a revolution to help empower people when they come to work with technology. So we've talked a few times and you said something that was kind of funny and I actually made a couple of slides here. You said everybody's familiar with this triangle. Has everybody seen this before? You have the triangle, it's good, fast, cheap and you get to pick two. And what you said is that that triangle now looks like this. It's just fast, fast, fast. It's funny. If you look at what any business needs these days, if you're doing it all with information, you need speed. That's what everybody craves. If you give somebody enough fast, they can make their own cheap. They can get their product to market quickly. They can respond to market demands and changes. They can be the first candy game on Facebook instead of the second candy related game on Facebook. You know, you can make your own cheap by just increasing your revenue by just getting to market more quickly and being able to work faster. You can make your own good by shrinking your dev cycles. You can change things all the time by only changing little bits at each time. Move to more continuous integration, continuous delivery models. So product quality goes up. So if you just give somebody the faster lovers pizza with an extra helping of faster on top of it, they'll go make their own good and their own cheap. Yeah, I love that, faster lovers pizza with an extra helping of faster. That's one of my favorite descriptions of it. So you're talking earlier, you were talking a lot about how it shouldn't be easier for them to be more productive at home than at work. You're talking about lowering barriers and it actually reminds me of an interaction I had one time. This is a few years back when I was at the Rackspace Cloud and I had gone and spoken at a conference and very large corporation, one of their IT leaders walked up to me afterwards and he said, you're creating problems for me. I said, sorry, what's going on? And he said, my developers inside of my company are going and signing up with your service and putting workloads on your services. And I need you to stop letting them do that. And I was like, well, how would you like me to do that? And he said, I don't know, Blacklistxcompany.com email addresses from being able to sign up. And I was like, but they'll just use a personal one. And he's like, well, Blacklist IP blocks. And I said, well, it seems like they're looking for something. And maybe that's what the conversation we should have is figure out how can you deliver what they're looking for through a way that meets your requirements. Yeah, absolutely. Anytime you get technology people together, there's this discussion of shadow IT and how it's a bad thing and you need to shine the light into the corners and eliminate it. And that's crazy. It's like the little tablets that you chewed when you went to the dentist at age eight that showed you where you weren't brushing properly. Shadow IT is awesome because it shows you where your opportunities are, right? Where your service is not market competitive. Where are they not compelling? How are you not enabling people to do their jobs? We hire amazing, passionate, driven people and then we put mountains of obstacle course and process in front of them and we shouldn't do that. I don't mean we because we're trying to fix that but everybody should try to fix that. Yeah, it seems like there's a lot of stick out there. Yeah, exactly. We're a big IT world and if we change that more to care it, if we change that more to enablement, then we end up with a more empowered set of technologists. So I had the slide up earlier of the sponsors that are here and that's a portion of the ecosystem that participates in OpenStack. And one thing that I've heard before is people, if you look at OpenStack and they are concerned about how they're going to get started in OpenStack, how they're going to make use of it because it's a big set of technologies but there are a lot of people out there who are able to help you do that and I know that you have an interesting story about that as well. What has your experience been with kind of working with OpenStack and the vendor ecosystem? Yeah, I was our virtualization snake oil guy too back in 2007 and we had worked with our hypervisor for about six months before we felt confident enough to put our first production file server on it. And when we deployed OpenStack, we didn't have the time to do that. The whole point is let's go fast. So we engaged a company called MetaCloud that we've been working with and had great success with. They take OpenStack, they add to it, there's some things that aren't finished yet, they contribute back to the project and then they'll deploy and run it for you in your data center. So it gave us a very quick, we went from month one looking at technologies, month two POC, month three deployed. At the very end of that month, it was we launched a pilot and ran a pilot of OpenStack as infrastructure as a service. So it's, yeah, you can go very quick and you don't have to staff up a whole big department of people to do the operations and all that kind of stuff for you. So it's a nice model because if the whole point is speed and trying to deliver that to people, you wanna operate in that same agile model yourself. Right. Okay, last question. I wanna ask you the same thing that I asked Glenn. You know, when you look at this infrastructure and the way that your business is moving, the trajectory that it's on, does it feel to you like those backend systems and those servers and storage systems and everything, you know, all of that stuff that's, that used to just be in a closet somewhere is becoming more strategic and more recognized within your organization as providing value. I think there's not anybody who works with any sort of digital information that doesn't understand that it's important, all that stuff. I also don't know anybody who works with those things who wants to care about all that stuff, right? So, you know, it's becoming really important, but it also isn't something that people wanna spend time worrying about, right? It's more like the dial tone where it just has to be there and has to work, but you don't, you know, oh thank goodness the dial tone is still on, right, when you pick up your phone. That's an outmoded example because I haven't heard a dial tone in probably nine months, but yeah, so yes, it's obviously a strategic value, but it's also something that you wanna provide as a utility service, right, where when you plug something in, it just works and goes. Yep, okay, well great. Well thank you again for joining us and we're happy to have you here at the show this week. Thanks a lot. So, I'm glad we had Glenn and Chris join us and we have many, many other users that are here. If you are looking at getting involved in OpenStack and wanna speak with them, please, you know, track some down and find out about their experiences. It's a really great community to be part of. I'm actually going to take a little break now and we're gonna have a couple of our headline sponsors who are going to come up here and speak. I'm going to be back in a little bit and I have some announcements that I'm gonna be making about some new initiatives that the Foundation is launching this year. So, stick around for those. One of the things that we did before the event this time is we actually got a number of these super users to sit down with us and talk about their experiences on video and we're gonna be playing these videos throughout the general session this morning as well as tomorrow. And so, I wanna go ahead and play this first one where we hear super users talk about the advantages that they see with OpenStack. The primary impact of being part of and leveraging the OpenStack community is the reason we did it in the first place which is velocity of our application development. We are delivering new features, new products, far faster than we ever have done before. We have hard deadlines, we have hard air dates for TV shows so being able to shift and adapt that compute infrastructure, that storage infrastructure, that networking infrastructure was a tremendous advantage. One of the advantages that OpenStack allows us is for our developers to iterate faster and be able to get better products out to our customers quicker and that speed and agility is something that we find very important. We're in a highly volatile, highly competitive business I know everyone says that about their business but you're dealing with shows that only last for six months and you have to design a custom workflow for that show. So having an infrastructure that can change is means that we became more profitable as a business and hopefully the quality of life of our employees also went up as a result of that as well. It's pretty key to what we're doing both internally and externally and we're deploying our entire platform directly to OpenStack sort of all at once. So we're able to stand up an entire platform environment just with like one command. I think the big impact for Bloomberg in using OpenStack and looking to the future is going to be and how we're actually going to be able to expand the services that we deliver to our customers by using OpenStack infrastructure. Again, through the agility and the flexibility that it gives you, it actually allows us to start delivering new things to our customers. With OpenStack, we've deployed several OpenStack clusters which we're making available to internal developers to work on their new ideas and also in production to push out those ideas from the development side into their production side with sort of minimal amount of fuss and energy. OpenStack has given me a feature that three or four years ago I didn't think was going to exist. So I love hearing stories from our users and operators and Guillaume who you saw there at the end of the video, he's actually going to be here speaking on stage tomorrow morning so come back and you can hear some more from him.