 Welcome to the OpenStack Summit, April 2013. This is, I think, a great example of the power of OpenStack, how many open source projects have their own hip-hop group. Not a lot. Although, you know, I do remember them before they went corporate. And I think, you know, some of their original stuff was really good. So, I'm Jonathan Brice, and I'm the executive director of the OpenStack Foundation. And I am going to cover a few things this morning and have some special guests up here. And I think we're going to have a really good morning with a lot of good speakers who are going to talk about what people are doing with OpenStack out in the wild. It's going to be really exciting. But first, a few housekeeping items. So, these are your badges. A lot of the information that you might have a question about is going to show up on the back of that badge if you are wondering how you get to the Wi-Fi. Where the parties are, everything is on there. You can see that a lot of that's on the badge here. This upper area, registration, general session hall, most of the events are happening downstairs. It's where the food is, the expo hall, the breakout sessions, and the design summit. And I think, you know, that's pretty much it. Keep it simple. How do you guys like the hoodies this time around? Yeah, it's a little different. We've done a lot of t-shirts, so we decided to do a hoodie. Did anybody find the Easter egg on the back? The OpenStack itself is made up of all of the places where we have OpenStack user groups. And I think this just goes to show that OpenStack is made of users. And this is, I think, you know, really an homage to what we're trying to do. We're trying to build great software as a community and get it deployed all around the world. You know, just one other thing before we get the day kicked off. We are a global community. And in the last day, there have been a couple of tragedies. You probably have all heard about Boston. And overnight, there were some earthquakes in India and Iran. And we have community members in all of those places. And I just wanted to take a moment just to pause and just kind of, you know, let them know that our hearts go out to all those who might be affected. So the OpenStack Foundation is a pretty new entity. We have been in existence for just a little over six months, actually. This is the first summit that we've put on and funded. And, you know, I think it's something that has grown incredibly. We have just about twice as many people here as we had in San Diego six months ago. And that's really amazing, you know, doubling in six months. And, you know, this venue is much bigger. We have a lot more space. I know that some of the rooms are still crowded. We're going to keep working on it and keep getting better and better at it. But, you know, this is something that's possible because of the support of all of you, all of the individual members, and also the corporate members of the Foundation and the sponsors of the summit itself. There have been a number of things that we've done and, you know, helped the community to execute on over the last six months. Can't talk about all of them, but I just wanted to highlight a few that I think are really excellent examples of the power of community, of harnessing this worldwide group of people who are passionate about OpenStack, who want to go out and do great things with it. One of the things that happened earlier this year was we got a group of people together and put them in a room for a week, and they wrote a book. They wrote the Operations Guide for OpenStack. And this was another great example of just global collaboration. We had authors from Australia, from Canada, from Germany, from the U.S. They all came together in Austin, Texas. And sometimes, you know, Texans think that's a country of its own as well. So you could add that to the count, perhaps. And in a week produced this book. So it was really, I think, a great thing that came out of this. And you can find this on our Doc site. You can find links to it. And we've had thousands of downloads from over 100 countries around the world. So this is already getting a lot of great information into the hands of users all over the planet. Another program that we started was the Nome Outreach for Women, which this is a program that the Nome Foundation organizes and they go out and they work with different projects to sponsor interns and to bring women into different technology projects. And we had three interns that have been working with OpenStack and it's been awesome to see them get involved in the project, make contributions to code, help with documentation. These three women are in locations around the world and they're here this week. So they're doing a session and I hope that you can find them and talk to them and hear about their experiences. It's also been helpful to hear what it's like for people to come and try to get involved in the community. So that was another thing that I think we did that was pretty great. And then for other news, to hear about what we're doing, to tell us what you think we should be doing, we're doing an open house on Thursday afternoon after we kind of wrap up the summit. It's going to be across the street at the spirit of 77. It's on the bottom of your badge. So we hope to see a lot of you there. Come and bring your questions, your suggestions. I think we're calling it the open mic night. So if you want to do a little poetry, you're welcome to do that too. And I think it'll be a good time. You know, about six months ago, we had a peaceful transition of power, so to speak, over to the foundation for the OpenStack project. And it was something that a lot of people said, you know, this is really risky to go create a foundation. This project has a lot of momentum. Is it going to throw it off? I think we've seen that that has not been the case. And I just wanted to take a moment to kind of mention another peaceful transition of power that just happened in the last month. We've had some technical leaders that have really helped to drive OpenStack forward over the last couple of years. And four of them in this last election for our project technical leads stepped aside, and they're still involved in the projects, but they allowed new leadership to step up. And I just wanted to take a moment to thank Vish, Brian, Dan, and Joe for the leadership on their respective projects. You can talk to any of them. You know, PTL is a busy task. It's not an easy job, and it's one that a lot of times happens behind the scenes. And we now have new leaders that are stepping up, and it really speaks to the depth of our technical bench and OpenStack that this transition has happened and we have great new leaders in these projects who are working with these four still. So thank you to you guys. So, I just have a few quick thoughts about what we're doing. You know, this is obviously something that's growing, that's big, that has a lot of interest around it and a lot of contribution around it. But, you know, what is it that we're really doing here? Because it's not just software. It's not just a great development community. It's not just about having a bunch of companies and vendors involved. You know, all of those things are important, but any one of them on their own is not enough. And I think that what we're really doing is we're building a new platform ecosystem for the cloud. And so what is that? You know, what is a platform ecosystem? Platform ecosystems are what develop when you have a base level of technology that is widely adopted and extensible and it allows for a lot of innovation to happen around it. There's still a little audience survey here. So... Somebody loves surveys. How many of you have a smart phone? All right, so this is most of the people. Keep your hand up. All right, so it's pretty much the whole audience. Now, put your hand down if that phone is an iPhone or an Android device. Those are platforms. You know, platforms develop in massive markets and they gain a very large share of those markets. You know, iPhone, Android, they both have half a billion devices in these incredibly large markets. And if we look at what OpenStack is doing, we are creating powerful general-purpose technology that's also in another massive market. We're talking about every data center and everything in that data center. All of the servers, all of the network devices, all of the storage devices, we're illustrating all of that, putting a common API on top of it, letting people extend it, build on top of it, make it more valuable. I mean, that's really incredible to think about what we're doing and what the opportunity is in front of us as we do that. When we think about platforms, there are some influencing factors for them. And I like to fly around in little planes. You know, they don't have jet engines. But, you know, if you've ever studied flight or aerodynamics, there are three forces that act on an airplane that determine, you know, if it stays in flight, if it climbs, if it descends, all of those kinds of things, lift, weight, thrust, and drag. And when we look at a platform ecosystem, we say there are three forces that act within a platform ecosystem. You have to have powerful software, powerful technology. You have to have an innovative ecosystem of people who are collaborating around it, who are extending it, infrastructure functionality, and then you have to have successful users and users who are out there making use of that platform and taking advantage of that ecosystem. We were talking about smartphones a minute ago. You know, that's phone. It comes with an operating system. It probably has the ability to make calls, to send text messages. But what makes it so powerful is, you know, you can get the SCED application on iPhone or Android and see what's going on here this week. You can get the applications that make you more productive or, you know, enjoy that downtime while you're sitting there waiting for the plane to come. And these three forces, really, the stronger they are, the more they're focused to the center, the more that platform grows and succeeds, and it's like gravity. It creates the center of gravity that continues to pull in more innovation, continues to pull in more development, making the software better, continues to pull in more users. That's the concept to think about and something that is really, really applies to what we're doing with OpenStack. So if we were to break this down a little bit and look at each of these forces and look at the way that OpenStack plays within powerful software, I'm assuming that most of you are familiar with this. If you're not, this is a good place to come and learn about OpenStack and what the software is. We have 250 plus sessions this week along with another couple hundred in the design summit. We're going to go ahead and learn about this. But OpenStack is software for building public and private clouds and doing it at large scale and at small scale. And it's really focused around compute, storage, and networking and interacting with those components, controlling them, making them more efficient and more agile. We just had our seventh release, Grisly. So this is exciting every time we have a release and then we get to gum together to these summits and celebrate them. Now, this is the seventh release that we've done on time with all of the major features. So for almost three years now we've been doing what we say and I think that's a really great mark, especially in the software industry. You know, if we were to look at Grisly just quickly, we've got some screenshots here. We have a video demo on our website if you go to OpenStack.org slash Grisly and you can check it out in action. But Grisly has a lot of cool features. I think the block storage environment is really great now. It's kind of a true service for storage in the data center. You can manage multiple types of storage behind a single block storage service and one API. You can manage networks now with a lot of new drivers for a lot of new networking companies, software-defined networking, and also kind of traditional networking appliances. The interface for this dashboard has improved and has a lot of new capabilities and instances when you're configuring networks. One of my favorite features is this network topology view where you can really see a multi-tier application laid out and graphed as you're creating these different resources inside of your cloud. So the software, you know, I think has come a really long way and the development team has come a long way as well. One year ago we were in San Francisco, same thing, you know, Summit after the Essex release we had about 250 developers. They don't all look the same. That was just the easiest way to represent them. If you go from Essex to Grizzly, we've gone from 250 to well over 500 developers. I mean, that's really amazing in a year and we've added new projects and we've had new talent come in and that's what's powering an open stack forward. So if you're in the room right now and you contributed to Grizzly, stand up. Let's give them a round of applause. Thank you, guys. I mean, you were making the software and I think that you're going to be excited to see what we have the rest of the day. So this is great progress on the software front and that's a really key pillar of the forces. If we move on, we're talking about the innovative ecosystem and when you think about open stack, one of the things that a lot of people say is, well, they have all those companies involved and there's a little bit of irony there because I remember when we were getting going we said, well, there's only one company involved. So we didn't have enough. It was all rack space but now we have too many and it's kind of... It's hard to make everybody happy, right? But the innovative ecosystem is really important in platforms because a platform is a general purpose technology and it has to have a good level of functionality that meets a lot of needs but there's never any technology that meets all needs and a platform enables different companies, different software to take that platform and make it really valuable for specific use cases and that's really very critical. So we go back to 2010. July of 2010 we were actually in this building on the south side the south side of the building and we were at OSCON and that was where we announced open stack and there was an exciting time people were really excited. There was a lot of code the day we launched but then there was also some skepticism. Does this sound familiar to anyone? This is something that if you followed OpenStack you've probably heard this kind of skepticism before. Well, we were talking about other things that happened around the same time frame and what's interesting is July of 2010, just a few days before OpenStack just before we made the decision to open source the software there was another group of industry heavyweights that came together and they made a decision as well to form up a team and it was met with the same level of skepticism. About three days before we announced OpenStack was when LeBron James announced he was going to the Miami heat with Dwayne Wade and Chris Bosch. That year they went to the finals the next year they won the finals and I have to say I think we've had some wins of our own and it's really exciting to see how we've come together. We were going to get everyone championship rings but too many of you came so we had to go with hoodies. Sorry. But really, I think that all of this noise about so many companies involved and the risk and all of that, it's really a red herring. That's driving innovation. We go back to compute storage and networking. There is a lot of work to do there and what those companies are doing is they're bringing in experts like those PTLs we saw. They're bringing in experts and their domain into OpenStack and they're contributing code and they're driving it forward and that is part of the amazing power of OpenStack. It's not just about the companies too and this is one of the things that I've loved to see over the last year or so. We have a lot of open source projects that are aligning themselves with OpenStack with the way that we do our releases, that we do our process. They are tying into our development tools our continuous integration our testing frameworks and I think that is, again, it shows the power of building a platform like this not just in the cloud but with our development processes and we get innovation all over the place. So that is such a key part of OpenStack and such a key part of platforms. And finally, the real key is successful users. And this is again an area that I love to talk about because we have great users and you know, we have a lot of them here this week and I love that they come to this because we have empowered users. We have users that are ready to come engage in a design summit talk to developers, work with the user committee and help us all make the software better based off of their experiences. But you know, one of the things that happens is people say when a lot. When are we going to have real companies using OpenStack? And I'm going to make a prediction right now. I'm feeling bold. I think that one day we're going to see companies in industries that we know about running services that we use every day on OpenStack. I mean, that's what this is doing. This is going into all of those areas and these companies are going to use OpenStack to power the services that we're using every day. And you know, we like to do time based releases. We like to put dates on things and we like to hit them. So I'm going to put a date on this. On when we're going to hear about these companies doing it. Yes. Right now we are extremely fortunate to have some users who have come to share their stories today. And I think that it's going to be really interesting to hear how they're using OpenStack. And again, these are brands that you know, that you interact with. So let's go ahead and get started with this. And what we're going to do is we're going to run through a couple of different users and customers here. They've got some great stuff to show. And so I'm going to go ahead and start bringing up Previer Chandra from Bloomberg. And Previer is going to tell us about what they are doing with OpenStack at Bloomberg. So Previer Chandra. Hey, what's up? So a little over a year and a half ago when I first got pinged by a recruiter from Bloomberg, my first thought was what does Bloomberg do? I've come to learn this, which is important. We're a services company. We're a services company that's incredibly focused on our customers. And the service that we provide is primarily financial data and analytics for people in the financial space. Primarily, we do a lot of other things too. We have a TV channel and a radio channel and all that kind of stuff. But just to give you an idea of kind of the scale of it, what it means really is that we're a technology company because we have to be a technology company in order to provide all these services. On a given day, we process about or send out about 22 million instant messages. That's not terribly interesting. We also do about 220 million messages, so like emails. Again, that's kind of interesting. Then I came to learn that we actually run one of the largest private networks in the world. We have around 20,000 routers that run across our private WAN. We also have the largest server-side deployment in the world. We have 22 million lines of JavaScript code that's in production running on our server-side. And we also, this is one of the more interesting stats, process tick data from financial markets. So when there's market feeds that are coming in, we process all that data. There's 45 to 50 billion ticks per day. For those counting along at home, if you were counting with a UN32, you would have overrun it 10 to 11 times every day. So that's what we do for what we do in terms of technology. So when we started looking at OpenStack, we had some interesting design goals that we had in mind for this kind of elastic infrastructure that we wanted to build. The first focus that we had was primarily on high availability. That's really important for us, and it's incredibly important also when it came to our architecture to make sure that we didn't have an architecture that would have opportunities for cascading failures. We didn't want to have a cloud infrastructure that we put up that would have one thing and then cascades down the line and takes the whole service down. That's, of course, it's not something that we can live with. In addition to that, another design goal that we had was to try to make sure that we were scaling down to small sizes, not only scaling up. We have a lot of node sites around the world, about 200 or so points of presence throughout the world. And the opportunity to actually have a programmatically defined infrastructure in those locations is huge. It actually saves us a lot of time, and it makes us very nimble when it comes to actually being able to deploy those kinds of services to different parts of the world. In addition to that, another design goal that we had was to try to keep our stack as open source as possible and in well-defined layers so that we could actually, if something went wrong, actually pull a layer out and replace it with a new piece. Looking forward into what we were when we started analyzing open stack and thinking about how we were going to actually implement it, we came across a few kinds of problems that we had to solve on our own. I'm going to put them into two categories. There's kind of problems that are below open stack and then problems that are sort of above open stack. So when it came to problems below open stack, we had to sort out how do we do highly available databases. We ended up settling on using the Glera plugin from iSQL to do kind of a multi-master setup. We had to figure out how to do availability of the message queue. So we did some rabid MQ clustering and had to play around with HA policies in addition to that. We also had to figure out even more basic things than that, which is what's the hardware platform that we're going to use, what kind of servers are we going to use, and it kind of related to that was also how are we going to do storage in a highly available fashion, to which we actually ended up using Cep with the awesome guys from Ink Tank that have helped us out tremendously with that. So those are kind of some of the problems that were below open stack that we had to solve, and then open stack of course plugged in really nicely a lot of our problems in terms of giving us the APIs and the programmatically definable infrastructure. But then there was another layer on top of open stack that we also had to work out. And that was how do we do some of the basic housekeeping things. So how do we do log aggregation and things like that from the hypervisor level. So we ended up putting together a system involving elastic search, logs, dash, Kibana. People have done that before, it's not really all that new. We also had to sort of define a layer for doing metrics for the hypervisor. So in terms of actually collecting information to make sure that our infrastructure was healthy. So we ended up using graphite and some tomfoolery with carbon relays and caches and things like that. In addition to that we also had some orchestration issues that we had to sort out. So when it comes to individual hypervisors or an individual instance of a service, we didn't care so much about how many nines of reliability we were getting out of that. What we wanted was the ability to have our five or six nines of availability on a service level, like an aggregate so that we could actually have an individual instance that dies and nobody cares and orchestration services sees that it dies and relaunches one of the new availability zone if necessary. And so we had to work on that and we ended up using Nojitsu and we're actually looking at a few other folks to actually help us sort out that kind of problem. In addition to that there's also what we wanted to do in terms of future things looking in terms of operational efficiencies. And one of the interesting technologies we're starting to play around with is the VMS technology from Grid Centric. So really the main thing that I kind of want to emphasize here is we had to solve a lot of these problems ourselves but we wanted other people to be able to learn from it. So go clicker. There we go. So what we're doing is actually, we just put this up today so I just wanted to announce it that we actually took all of the cookbooks that we've had to put together to solve some of the problems that we've had to deal with. So I think I'm available on GitHub. It's under an Apache license. And it's not that we're trying to actually go out there and make this like a huge project that we're trying to rally a big community around but really it's for folks that had to solve similar problems to us so that people can learn from it. And of course, comments, questions, flames always warmly accepted. But other than that, thank you very much. Thank you, Preveer. So I think you probably saw the flash there. How many of you have ever bought a charging cable an external hard drive a laptop washer dryer, a TV there's a good chance that you've been to Best Buy and perhaps you've used their in-store pickup perhaps you've bought something online and had it shipped to you. Well, today we have a couple of great guests from Best Buy who are going to tell us about what they're doing with OpenStack and how they're using cloud in general to really drive their industry. So please help me welcome Steve and Joel from Best Buy. Morning, Steve Eastum here director of Web Architecture with me. I'm Joel Krabb. I'm the chief architect for Best Buy.com. So Joel is going to cover kind of the background of Best Buy what we're doing in our program. Yeah. So let's just get started. We're presenting today in another breakout session and but today what we'd like to talk about first is just a little bit about Best Buy if you didn't know about us. We are considered the largest multi-channel consumer electronics retailer in the world 11th largest e-commerce site 1.6 billion visitors last year and we have a very large award program. So let's talk about our cloud re-architecture. Over the last year, Best Buy has gone on a quest to re-architect our e-commerce platform. And part of that was to move our browse and search to the cloud. So if you take a quick look at this graph in the corner here that's our traffic graph from Wolfram Alpha and as you can see we got a really large spike on Thanksgiving and it's about seven or eight times our normal traffic loads. And so if that doesn't scream out for elastic scaling I don't know what does. And over holiday this year which holiday for us is Thanksgiving we actually served 25% of our traffic off of our new cloud architecture and this is the first time we've actually even talked about the fact that we have a cloud architecture so we're rolling that out here really, really simply this is what our architecture looks like. We have a global traffic manager sitting in front of a couple different clouds from different vendors and then we have our data center in the background. But as consumers it's really what you see that matters to us. So on the left side you'll see our old, what we call our product detail page and on the right side is our new product detail page. So we have the cloud architecture and you can see the timings on the top the things that this really did for us and the value that it brought to Best Buy were that the old product detail pages took anywhere from seven to 30 seconds to load. Part of that was because a lot of the page was rendered post rendered JavaScripts on your client itself and we had no control over how fast our third parties responded. What we did as part of our cloud architecture is serve the entire page off the server so all those third parties now are integrated on our server side and we can serve that page out to you in about two and a half seconds. And then why we're actually here today is to talk about our continuous delivery cloud. So we built we have about 40 development teams or so that are developing at any particular time on Best Buy dot com and all those teams are using different integration and testing environments because our infrastructure for testing really wasn't that great and so what that caused us is lots of problems in teams using things that didn't quite correspond to production they were making their own test services and so what we wanted to do was make something that was consistent and easy for all of our teams to use so we created what we call the continuous delivery cloud so that our teams could have consistent architecture and Steve Eastum here will start talking about that. Cool. Alright so what our CDC as we call it internally provides us an innovation catalyst so all of our teams that are developing new NoSQL platforms or new caching platforms they have a place to go self service and we got out to everyone that was involved in Essex we launched this a little over a year ago it launched on a beta version of Essex along the way we did a few patches here and there but it's been rock solid we're going to talk about it in our breakout session today but just want to say thanks to all the development and testing that went into that our teams have a push button they've developed a push button development environment code named an omni tank I have no idea why it's omni tank but it's an awesome name self service api so teams can go in they can launch their own environments we're speaking yesterday about this we use Jenkins to actually launch Jenkins so teams can have their own push button Jenkins we have also use it for early integration one of the things you want to do in web development is not wait a really long time to integrate with the other teams you'll run into trouble and that kicks your development cycle way back it's all about speed and again automated testing at scale can run a lot of Jenkins executors and really reduce our automated testing time to just a few minutes we can run through a full regression suite and really getting away from manual touching and changing of our environments getting to the point where everything's automated and that reduces the variability so one more alright what we knew when we went into this we actually didn't know we were going to have our new platform approved and this is back in mid-circuit mid-2011 we ran a VSM or value stream mapping exercise and saw that our major release for bestbuy.com was consuming $500,000 mainly due to environment setup discrepancies availability problems and we talked about that parallel development really needed a way to support a lot of teams running on all in parallel and then the high cost of infrastructure, our current ecosystem of partners they were charging us upwards of $20,000 just a provision of managed VM with monitoring and everything so what we didn't know we were going to have the green light for a new platform that Joel covered didn't know how fast we're going to have to get to actually get it out the door before holiday and what it does for us as far as a culture we're building a culture at Best Buy around self-managed developer-driven teams and we really want to let them run do their own launch and run their own environments kind of get away from the blame game get away from that center of excellence what's missing in the center of excellence probably the excellence the parallel development we talked about that I don't know how many times about parallel development allowing the teams to innovate they want to test some new cache platform, some new NoSQL platform here's an API here's a Jenkins job you can run run your OmniTank and then finally it's about reducing that cycle that going through test dev, test dev release so really reducing the delta to get code complete to get all the way pushed out to release to world this is one of our teams it's a transformers team they are working on some of that complex middleware what we call aggregate services and they use a heck out of the CDC it's totally transformed their work cool here's another team customer graph you'll start seeing big changes in the way we deal with profiles, our personalization in the site and these guys are actively working on that and using the CDC cool alright thank you guys for coming and talking with us about this today one of the things you were telling me before was how you got started with the OpenStack this was really sort of a side project almost we have a lot of things to do and we were spending a lot of money we talked about that just to get a provisioned VM for our dev teams or to run a Jenkins executor and so we kind of put together that business case and it started with just one rack of servers and we took a couple of our dev teams mainly Java devs some of these guys are out here they learned Python we also use Chef so they learned the Ruby so some of them don't want to go back kind of converted that's great thank you guys for coming and talking about it this final user that we're going to bring up is another company that probably all are familiar with and have all interacted with in some way especially if you know you watch TV for instance and it's really exciting what we're going to hear about today is we're going to have Comcast out here and they're going to be talking about some of their new services that they're developing and how OpenStack plays a part in that so I'm going to go ahead and bring out SVP from Comcast, Mark Meal well good morning everybody let's get our slide up here I am Mark Meal from Comcast let me just tell you a little bit about Comcast since we have a very diverse international audience that may not be familiar to everyone we are a $60 billion media technology news and entertainment company and we have two primary businesses Comcast Cable which most people in the US I suspect are fairly familiar with and also NBCUniversal the Cable Company is the primary provider or is the largest provider in the US video, internet and telephone services and we do that primarily under this brand called Xfinity NBCUniversal operates 30 news and entertainment cable channels they two different broadcast channels with NBC and Telemundo and have TV production studio production groups, universal theme parks and universal studios movie production group so we have a lot of diverse businesses and we started our investigation of OpenStack maybe a year or so ago but let me tell you a little bit about where we were coming from when we started to look for some underlying infrastructure technology that could help us solve some problems one thing that might not be obvious to you since you don't live in the world that I live in every day is developing software in our current widely deployed cable service is somewhat difficult it's a very vertically integrated platform it is something that we typically buy the set top box some intermediate communication infrastructure and some servers all from the same company we have very little visibility into how that system works we really can't get into the software it takes us a long time to make changes on that platform all of the intelligence is in the box that's sitting in your house for that service there's very little that we can do outside of that box and that box is pretty limited so we decided that we needed to try to change the paradigm and so we've been building for the last few years this platform called X1 which we're going to demonstrate for you today here live and you'll see that this you won't be able to see because we don't want our customers to be able to see but I'll tell you that this platform all of the communication that we're sending back and forth from our set top box to our network is going through it's running on top of our OpenStack production cloud so this is a real world this is our real world next generation guide experience going to be demonstrated for you live and maybe I can get Jonathan to come out here and maybe he's willing to help do the demonstration we'll just pull out our little set top box here hopefully without breaking our remote there we go would you like the remote? sure we will so let me just set this up a little bit so our plan here was to move most of the intelligence out of this set top box which is hard for us to develop on and move it into the cloud so that's a pretty standard model for everybody we understand how that works I just want to also brag a little bit that we were able to build most of the stuff in this cloud on other OpenStack software so not only are we on OpenStack but we're doing a lot of what you're about to see with OpenSource software this lets us build a much more personalized experience that puts content in front of users and makes our experience much more about content and getting you to the content that you want faster alright so let's cut to our demo our time is here an 8 year old boy I think we can probably take the audio down if you want that way we can hear our little voice over alright so we are this is some live TV we're looking at right now one of the neat things we can do is just search by typing so you've got the remote you can just start typing for maybe serenity or something serenity? serenity fans out there? serenity of the movie a few there we go alright and so here you can see it was easy to find Jonathan just started typing and it sends all that information every single keystroke goes into the cloud we analyze the search that you're trying to conduct we figure out whether you're searching for a channel for a particular call sign for a network if you're searching for content like movies or maybe even actors and then we try to propose some search results and let me just mention you see the rotten tomatoes ratings up here we decided that consumers might be curious about what critics or other moviegoers thought about there thought about this movie that they're considering to purchase or watch so we integrated we did a deal with Flickster and we integrated their Rotten Tomatoes service and it took us about three weeks to do that in the old model where we have all the intelligence on the set top box it's impossible to load all this data first of all into the limited memory footprint in the set top box and here we can do it all in the cloud and just send the data back I'm playing around feel free so here we are in the DVR you cut the sound on the X1 okay so this is the DVR here this is all built in you can see scheduled recordings you can see the recordings that you've got we preserved deleted recordings deadliest catch in Phineas and Ferb that's quite a selection I have four kids Phineas and Ferb is big in my house and Big Bang Theory that's one of my favorites so here we see maybe hit the okay button there yeah that's perfect so once you want to look at Big Bang Theory you go over to the right a little bit as you saw Jonathan do and you can see that we've got six different seasons or episodes that are involved in six different seasons of Big Bang Theory available to you and we tell you whether it's available on our on-demand service or pre-recorded on your DVR or if it's on broadcast television then you can set recordings and do everything else that you want to do directly from this interface how about we show some apps sure okay back to the menu here so you've got your obligatory weather and traffic apps but sports I think is a good one so one of the frustrations that I have when I'm trying to figure out where the baseball game is or the football game or the NCAA game or whatever it's hard to remember sometimes which channel is actually carrying the game that you care about or whether maybe your team is playing today or what time the game is on so as Jonathan just went through you can see that we've got this application that comes up and helps you find the stuff that you care about you can find your team, you can set up a recording if the game is in session unfortunately we're here in the morning but we have a couple of set-top boxes that are scattered around the conference one for example is in the Cisco booth if you go and play with it while the baseball game is on you'll actually see the game in progress and so we're integrating that real-time sports feed with the program guide information and if you just walk into your house and you want to tune it up do you tune directly to the game or you can just get a quick update on the game by seeing what's on the app this would be impossible for us to do on our own platform what do you think? I think it's very cool cool so first of all that was very brave this is live on OpenStack this is probably the first time that we've had a set-top box demo up here this is not the normal way that we think of OpenStack and interaction with OpenStack so thank you for bringing that here today glad to do it, thanks a lot so we we had some great users there with Bloomberg, Best Buy Comcast and I really appreciate that they came and talked to us today and I think that it does help illustrate how critical it is to have all of those parts of a platform ecosystem I think it's also nice to see what you're building here and where is it going because you can sit there and write code you can check it in, I've written a lot of code in my lifetime and sometimes you wonder what's actually happening to this when I push it out and this is where it's going this is the software that you're building software that we're designing here this week it's going to all of these places and more and that is really impressive this is just a quick list of other organizations that are running OpenStack right now it's really, really incredible so I think the what this community has done together is nothing short of amazing and I love working on it every day so thank you all for making OpenStack great and I want to thank everyone who's involved in it it is a massive effort from developers from companies from people who are supporting it and also you might have known we had a little bit of a late start today sorry about that we've obviously thrown them some challenging items today I want to say a special thank you to the people who put this event together we all create a lot of work for a bunch of people and so thank you to fntac and thank you to the OpenStack Foundation team that has put this together so I hope you have a great summit there is one more thing that I wanted to mention here I know there's a question about where are we going to go next so last year we made a promise that we were going to be international sometime this year and we are in the stages of finalizing the next OpenStack summit in Hong Kong in November of 2013 and this is I think going to be a great opportunity for us to continue to spread OpenStack around the world so that's all the time I'm going to take