 Good morning, and welcome OpenStack community. To kick things off, please welcome Jonathan Brice. Well, good morning everyone, and welcome to Vancouver. This is super exciting to be here. Vancouver is an amazing spot. It is so beautiful here, and it's awesome to have the summit. I was actually born in North Vancouver. So when you are walking around this beautiful venue, if you look across the inlet, that's North Vancouver. That's where I came from, and it's cool to come back here with about 6,000 of our closest friends and have a great week all focused on OpenStack. So before we get started, we still have some people coming in, but we're gonna go ahead and start rolling. We've got some housekeeping items to get through. Just to kind of, I want to get a little bit of a feel for how many of you are here for your first time? At an OpenStack summit. Wow. Okay. Well, welcome to the community. The OpenStack summits are really, really fun events. There's tons of work, tons of content. We have almost 500 sessions happening here this week. So there's something for everybody, and it's a great community that loves to bring new people in. If you are wondering how you find your way around this week, most of the information you need is around your neck right now. On that badge you have, there's an insert, and it folds out. It has the Wi-Fi information. It has venue maps. It has the overall schedule of events when lunch and break times are. But you know, just to really dive into the details, I recommend getting the mobile apps. And we have the mobile app available in both the Apple Store and the Android Store. And this has the schedule for every session throughout the week, where it is, maps again, so you can find your way around. We are in a very big venue. So just to help you orient yourself a little bit, we are in the lower level here, in this big blue square, which is a really large space that we're doing the keynotes in. At the back of this hall is the primary location for lunch that's served every day. There's also food available up on the main level, up by the marketplace, where we have our expo hall, and the marketplace this time around in the summit is pretty amazing. The location that we're in, the room that it's in is just fabulous. You should definitely go up there, check out our sponsors, check out the view, and really take it all in. And we also have box lunches available up on level two, if you just want something to grab quickly. The convention center is split into two buildings. We are in this building that has the grass roof on it. It's the West Building. And then the East Building is a short walk. There's actually a tunnel that goes over to it. It's about ten minutes. Most of the sessions are in the West Building. One of the things that we're doing this time is we actually have a lot of communities that work with OpenStack and a lot of other technologies, and we're doing some collaboration days where technologies like OpenNFV and CoreOS and others are holding sessions throughout the week. And so if you want to participate in those, a lot of those are happening in the East Building, and you can again reach that through that walkway. A couple of events today. We have lunch with our OpenStack Foundation board. If you want to meet the board members, meet the people who are involved in the governance of the OpenStack Foundation. You can go to lunch, 12.45 to 2 p.m. They're going to be wearing badges that are red, and there'll be some other signs. You can talk to them, you know, tell them what you care about, tell them what you think we should be working on for the foundation, and where you want to see OpenStack going. And then tonight, the Expo Hall opens up, and we're going to have a booth crawl and happy hour starting at 6 p.m. from 6 to 7.30 p.m. And I again recommend you go check that out and see our marketplace, see the sponsors that make this possible, see the companies who are innovating on top of OpenStack. Just the last few things before we start to dive into some content this morning. We have a women of OpenStack group that that is really starting to get active, and they had an event last night, but they have a couple of other sessions during this week that if you are interested in diversity and especially in gender diversity in tech and in OpenStack, we'd love for you to come and participate and help us, you know, improve the situation there and move the needle. So on a 7 a.m. Tuesday morning, there's a working session and breakfast with the women of OpenStack group that you can you can join. The design summit, you know, this is one of the main reasons that that we all get together every six months is to set the direction and decide, you know, where is OpenStack going? Technically, what are we going to do with the software? This design summit, we've combined both the developer sessions and the operator sessions into a single design summit and that takes place on the upper levels of this building here. You know, I think that that this is going to be really interesting to see as we get our developers and our operators together solving issues, setting the direction, setting the priorities. It's going to be awesome to see that collaboration happening. And, you know, as we do this, we're actually going to have more operator sessions and more design sessions than ever before. So it's going to be a really busy week for a lot of the developers in the audience who are here to work and plan the future of OpenStack. We have a couple of things for you to take with you. You might remember that a year ago, we launched Super User Publication, SuperUser.OpenStack.org, and we have the first print copy of that here. It's got a guide to the summit. It's got information about Vancouver. It has some feature articles about emerging technologies and also interviews with various OpenStack users. So make sure you get your copy, flip through it, and check it out. And of course, we always try to put together a great giveaway for our attendees. And this time around, we have a windbreaker, a rain jacket. It's really nice. I have actually seen hundreds of them already walking around the streets of Vancouver, which was pretty cool yesterday. But they are available in two colors. You go pick them up at our stacker swag store. That is up one level on level one. It's just outside the marketplace. And you get that with your registration. So make sure that you go pick up your jacket and join all of us as we wear it around Vancouver this week. So I want to talk about some different things that we've been working on. And this morning, I'm really excited about the keynotes this morning, because we've got some announcements, but we also have some old users who are coming back, some new users who are going to be talking. And we're also doing some demos. And these demos are pretty sweet, I think. I think we're going to be showing you some things you've probably never seen before. So that is what we're going to do this morning. But first, I want to set the stage a little bit. We've talked a lot at the OpenStack Summit about how critical software development is. You know, this software-defined economy concept. And it's something that is impacting every company and every organization out there. It's how we innovate, it's how we compete, it's how we move faster. And it is something that is across all geographies and across all industries. You know, this isn't just about high-tech, about technology software companies. You think about traditional, physical, capital-intensive businesses. And you've got the hotel industry. You know, they've got big physical footprint, the taxi industry, capital-intensive, physically located, the retail industry. All of these industries are being disrupted by software. Being disrupted by this application economy. If we just look at the taxi industry, you know, the ride-sharing services like Lyft, got Uber, they have had a dramatic impact on this industry. The price of a taxi medallion in New York City has dropped 20% since Uber was introduced. In San Francisco, the number of taxi rides has dropped 65% since Uber started service there. That is true disruption of an industry. And this is something that impacts everybody. You know, there's not a real walled garden anymore that isn't available to this. And so, companies who, you know, they may have a physical location, they may have a lot of physical locations, they have to deal with this too. And later this morning, we're going to be hearing from the largest company in the world, Walmart, about how they're approaching this. And so, I'm really excited to hear the Walmart keynote later. But before we get to that, I want to touch on some of these trends that we're seeing. You know, technology constantly driven by buzzwords. And this is one of those phrases right now, developer productivity. How many of you have heard this uttered repeatedly over the last couple of months? Something that gets said all the time, right? Developer productivity. You know, I've been a developer for a long time, and I guess I never realized how unproductive we were. I thought I was writing a lot of code. I thought it was, you know, building apps. But apparently, you know, we've been unproductive, and so everybody wants to make us productive now. And to do that, you know, it's tool after tool that comes out. Docker, Rocket, Mezos, Ansible, Kubernetes, you know, everything that comes out is oriented around this. But it can actually be pretty intimidating, this proliferation of tools. And ultimately, what it all comes down to, all of those applications, all of those tools, everything that happens is all about processing data, storing data, and moving data. You know, the basic foundation is still compute, storage, and networking. Now, ideally, our applications can get those building blocks quickly, securely, and in the location that's best for our users. So, you know, wouldn't it be great if you could have a global footprint that gave you access to those resources? You know, in a public cloud, where it made sense, in a private cloud where you might have security or regulatory requirements, or, you know, maybe even a cost profile that you can achieve better in a private cloud, or hosted private cloud if you want to avoid multi-tenancy, but don't want to take on all responsibility. You know, that would be a great vision if you could do something like that. And, you know, for those of you who have followed OpenStack, you know that that is the vision that we had when we kicked this off and that our community has worked towards for a long time. This global footprint of interoperable clouds that bring together compute, storage, and networking resources. So, you know, as we look at where we are now, we've reached a very big milestone for OpenStack. And I'm really excited to announce that we are now rolling out our first round of interoperability tests and requirements to define a common core that must be available in every OpenStack environment, private, public, or hybrid. And this is a huge step forward for us. It involves common code that's going to be available in every product or service that calls itself OpenStack and common APIs that work the same way. So, all of these OpenStack environments, they look the same, they act the same, and this is tested and validated. Now, we are just getting started with this. You know, we're announcing this today, but we've already worked with a few companies who have started to do this early. And if you go to the openstack.org slash marketplace URL, you can start to see this information being shared today. This is now live. You'll notice that with the OpenStack powered logo, there will also be an icon that displays when a product or service has been tested. If you drill into that, you can see exactly which capabilities they have, what they've enabled, what they're testing, what is validated, and what you know is going to be there. These 16 companies are live in the marketplace today with their testing results. And through the rest of 2015, we're going to go across all products and services that are OpenStack branded and put this in place. And you will know what you're getting, what is available, and this is really creating an OpenStack powered planet. When you see a product or service with that logo, you know what capabilities you're getting and you can count on this as your solid foundation to build your applications on. This is compute, storage, and networking. That's what that gives you. You know, this has been a cool process too as we've defined this. It's been a very community driven process. And I specifically want to thank Rob Hirschfeld and the deaf core committee and all of the people who put a lot of work into it because it has been a very massive effort to come to an agreement on what we need to have in these clouds, how to test it. And so I just want to thank the deaf core committee for putting this together for us. So this is what every application runs on top of. Compute, storage, networking. And you know, compute is not just virtualization. Sometimes people think of OpenStack as virtualization management, but OpenStack does virtualization, does containers, it does bare metal. And the keynote's tomorrow, we're actually going to get a peek at some of that when Mark Collier does a series of demos and shows off some of this. So come back tomorrow morning as we kind of expand beyond just these basic building blocks. You know, this is the base and the OpenStack development community has done an amazing job of producing a solid core. The summits come after our releases and we get ready to start planning for the next release. And Kilo is the 11th OpenStack release that we just had. It was a community effort. And I want to thank all of the contributors that submitted code in the Kilo cycle. If you contributed to Kilo and you're here, could you stand up? So thank you. And you'll notice a very large percentage of the attendees here are the people who are building the software. So if you are one of those first-time attendees, if you're new to OpenStack, that's why it's so important to come to these summits. Because it's not just about the sessions that we have in the conference, it's not just about the marketplace that we have. It's bringing together the whole community of products and services, developers, users, and that's what makes the OpenStack summits so powerful. So thank you to all the contributors in Kilo. Before we go farther, I did want to mention one other thing. During the Kilo cycle, we lost a member of our community. Chris Yo was a core committer and he had a very big impact on OpenStack and on his fellow contributors. And for the Kilo release, the technical committee and our community of contributors dedicated that to the memory of Chris Yo, which I thought was just a really great move. So I just wanted to take a minute to mention that and to remember Chris. And his family has asked for, if you want to do something for Chris, they've asked that contributions be made in his memory to free to breathe. Free to breathe. So just wanted to mention that because we are a community and I think that it's one of the things that makes OpenStack really special. So Kilo took a lot of work, a lot of effort from a lot of teams. There's one other person that I want to call out. We, for those of you that aren't familiar, OpenStack has broken up into different technical projects and each of those projects has a project team lead who is responsible for guiding the efforts of their community of developers and setting priorities and moving the work along. And we elect those leaders from the developers every six months. And a lot of times these PTLs, they'll come back and they'll serve multiple terms, but we have one that was a PTL since the very beginning and she has recently decided to let someone else take the lead on documentation and I just wanted to send out a special thanks and give some recognition to Ann Gentel who's been so key to making OpenStack happen. And I think she's over there, so thank you Ann. One of the really cool features that was in Kilo and that I'm really excited to get to show you this morning was around federated identity. You know, this is a feature that's been developed over a couple of releases, but it's one that shows the power of having an OpenStack-powered planet with a global footprint of clouds. You know, if you have a lot of clouds, they look and act the same, that's great. But once you have that, of course you're gonna wanna take advantage of it. You're gonna wanna find the cloud that fits your needs the best and you're gonna want to integrate with it easily to tie it into your application easily, basically to extend your footprint wherever you need to go. And so that is really what federated identity enables. And this isn't, you know, a theoretical need. We're going to dive deeply into one particular industry here. That's the TV and film industry. When you think of TV and film, you probably think of Hollywood. You think of, you know, L.A., Tinseltown, movie stars, all of that kind of thing. And the reality is that the way that TV and film is made is changing dramatically. This is data on the growth of production in various locations around the world over the last two years. And what you can see is that production globally is growing dramatically. And this is creating incredible shifts in their workflows and in how they make TV. But it's not just about this geographic distribution, which is a huge issue, but there are other things that they're dealing with. You know, going to digital has enabled them to do a lot of new things, but has also created new challenges. So an hour of TV is usually 44 minutes of content. Does anybody want to take a guess about how many minutes of footage they shoot for 44 minutes of content? Anyone? 10,000, I heard someone say 10,000 out there. That is a big guess. So they actually shoot 3,600 hours, 216,000 minutes of television, sometimes across 20 or more cameras, multiple takes, across days and days of shooting, hundreds of thousands of minutes of television. An hour of 4K content is 700 gigabytes, 3,600 hours to go to that 44 minutes of content. So this is, you know, a massive data problem and they're doing this all over the world. So it's distributed. It's really interesting to see the challenges that they're facing. And so we're gonna take a little time, we're going to, like I said, dive deep into this. To set this up, we have a video from an executive at TNT, Ron Vankowski. So let's roll the video over on. I'm Ron Vankowski, Vice President of Post-Production for Turner Broadcasting. When we were reliant on even file-based workflows, the movement of materials was somewhat clunky and not very cost-effective. Trying to figure out what particular file types for whomever, for whatever their needs are, was just cumbersome. I really like the evolution of cloud-based workflow. On our show AsianX, for example, we have all of our raw dailies stored in the cloud. And our promo department can access it. Our visual effects department can access it. Everybody can access it immediately. And the efficiency gained by having a cloud-based workflow is just far superior to anything so far. So Ron talked about some of these challenges that they're facing. And what he said is that there's an approach that they're using, which is that he called it a cloud-based workflow. And there's a company that has built a set of services and products on top of OpenStack to really address these needs and to create that cloud-based workflow. And that's Digital Film Tree. So to dig into this today, I want you to help me welcome from Digital Film Tree, Guillaume Obachan. Oh, thank you so much. It's so great to be back. I always enjoy coming to the OpenStack every time. So to touch a little bit on what we do and how we take that 216,000 minutes and whittle it down to 44, it's really indicative of the creative process. The creative process is a process of reduction. And I compare making television to sculpture. So you, which is a little ridiculous, granted. But you take a big block of marble and you chisel away and you get a statue. So there's so many people that contribute to this process of whittling down that material. You start with the editor who takes that content and really sort of trims the fat out of it and makes a small reduction. You have the director who has circle takes and gets it down to about 60 minutes, some sort of usable timeframe. You have producers that come in that further whittle that down about 50 minutes. You have the studio and network who give notes that make the content worse, but make the time shorter. So, and then you finally get to 44 minutes. You finally get to this magical number. So this is all a process and ultimately a problem of storage and accessibility. Having access for all these people and storing all this content to grant that access to them. So we have three challenges essentially. We have multiple regions. We shoot all over the world. We have highly paranoid clients. We have studios and networks who don't wanna be on CDN, so we have to go replicate content as close as possible to that production. So we need to be in multiple regions and therefore we need to be in multiple clouds. Not everyone is everywhere in this business. Some people have data centers closer than others. So we need to be on multiple clouds and we also need to completely ditch physical migration for the reasons of data loss and just the inefficiencies of physical migration. And to speak to sort of this interoperability, HBO asked us, they came to us and they said, can you run on top of AWS? And we, because they already trusted AWS. And so what we were able to do was actually boot up an open stack instance, running our applications on top of AWS for those purposes. So really just to prove the point of open stack interoperability for our business. So one of the shows we did this year was this great show called Unreal. Shot in Vancouver, six miles across the Inlet, which I was informed it is an Inlet. Cut in Los Angeles and all done on open stack. And really, this show could not have been done two or three years ago. And it needed to be done on Cloud Workflow. So the premise of Unreal is it's about the behind the scenes of making a reality show, okay, like The Bachelor. And so what that required us to do is they would shoot content in the morning in Vancouver. We would push that material down to Los Angeles, editorial would cut it, we would push it back up here, and they would play it back, and they would shoot a scene with the material they shot in the morning back here. So high res content, 4K content, back and forth within an eight hour period basically. So really undoable without the cloud. Fortunately, at the same time, like a true television coincidence, at the same time Unreal was getting started, we were contacted about a proof of concept that OpenStack wanted to do around federated identity. And they wanted to do it with two providers. They wanted to do it with HP and BlueBox. And what this proof of concept allowed on Unreal was for us to run our private instances of OpenStack, running our application in Vancouver and Los Angeles, and then instantly scale those workloads out to public cloud with HP and out to hosted private cloud with BlueBox. So instant scalability, on-demand scalability with two little files. But because I'm a doer and not a sayer, we wanted to prove to you how this works in practice. So Jonathan, if you wanna bring that Sony 4K camera out, let's show them how this works. All right, here's the camera. We're gonna make a little TV magic here. There you are, okay. So what are we gonna do here, Guillaume? Oh look, they're already waving, in anticipation. Everybody loves to see themselves on TV. Okay, so I think we're gonna shoot a little shot. Okay. Yeah, so everybody over here, we're gonna get a shot and pan a little bit, so wave. Wave, yeah. Yeah, I'll say hi to your mom. Woo, give me some energy, more energy. This is your TV moment. Yeah. All right, this section here especially, keep it going. Yeah. Keep it going, come on, energy, energy, energy. Five, four, three, two, one, cut. I think I could do this. You know, I think three more takes and we got it. Okay, so this is some footage now that we've captured, so what are you doing here? So we got the little card, it was shot. It's a tiny little card too. And this is a 4K camera. It is a 4K camera. Okay, it's cool. Newest and latest and greatest from Sony. So we're gonna take this footage now. And we've got our Aspera instance, which is running our critique cloud, which is backed by a Swift back end. And we're gonna create a new folder here, called new folder two. That's how lazy I am. And we're gonna go ahead and upload this content to digital film tree. All right, and this is the process that when you were here shooting Unreal, you take all this footage and you would go, I think you told me before that you had a Colo facility here and basically an upload node. Correct, we're actually still doing a show up here called Mistresses, which is done out of a Colo shot and it's transported and transcoded simultaneously to Los Angeles every night. Wow, okay, cool. And before you were doing this with the cloud, how would you get this footage to wherever the production office was? Either via some sort of courier service or a poor PA would get on a plane with a drive. And that's what PA... They would physically carry it. Physically carry it. It's digital data that you'd be using petroleum transport protocol. Absolutely. Okay, I think what we should do is a bake off. Okay. So we'll take this card and I think we should physically ship it to Los Angeles. Okay, can we try to get this shipped to LA as quickly as possible? We'll get a tracking number and share that later and we can see how it goes. So what happens now? We've uploaded some footage. Well, I think Thomas, who's one of our visual effects artists and Coloris in LA, should do some magic as quickly as possible to it. Hello, Thomas. Hi, Guillaume. Hi, Thomas. And hi, Jonathan. Hi, Thomas. Welcome to the OpenStack Summit. Thank you. I'm glad to be here. So you have that footage. So prove to the good people that you have that footage. I'm looking at it right now. Look at that. Wow, cool. The beauty of cloud. Now, how do we know he's in LA, though? Yeah, how do we know you're in LA? That was an excellent question. I'm in LA. Okay, we'll trust you. You know, if you only looked more like a hipster, it would prove it out, I'm just saying. Gotta look nice, gotta look nice. So I'll give you what? Like a four and a half to five minutes? Yeah, that sounds good. Yeah, you do that. And we'll check back in with you. All right, sounds good. Good luck. Okay, so we're doing this demo here, but I want you to talk a little bit more about the process. This, to go from camera through the production. So essentially what we just did is the first step of the process, which is a media acquisition, ingest process, transcoding that material, transporting that material simultaneously, and transcoding that material because we still need a proxy file. I mean, editorial, mobile viewing, all that accessibility I talked about, you're not gonna be doing that at all. You can't use the raw footage, yeah. Absolutely. So you still need that proxy file. And simultaneously we're doing metadata association because for us we need to go back to that 4K, we need to deliver in 4K, but you're gonna be working with the offline file, so you need to link them back up. And then obviously we're granting access to that material, removing access, all these things that go into security. But for us, the biggest thing that we're doing is, yes, we're enabling all this efficiency. But what we're doing is actually we're sort of applying big data analytics to this footage for the first time. So we're really sort of contributing back this new sort of efficiency and data model and information back to the studios that they haven't had before. In Ron's video, I saw a lot of paper, a lot of books. That was all tracked before, right? It was. And sometimes I have like a romantic, like I look back at that and I go, oh, that was cool. And then I snap back to reality and go, oh, wait, no. And so you guys have built apps to this, right, on top of OpenStack? Absolutely, we built Critique, which is our OpenStack-powered review and approval service, and then we built ProStack, which is basically our Swift instance for media. Okay, cool. So who uses these apps and these services as you go through the process? So really what this has enabled is us to stitch together for the professional and provide them access in the same way that they're accustomed to with, for instance, their baby videos. So we're providing that same level of access to the mobile, to the tablet, to the workstation, everywhere they are, through the web, to that content. Okay, you mentioned that you had expanded your workflow and done this with federated identity onto some other environments. So I wanna bring out the project team lead for the OpenStack Identity Service to talk a little bit more about that. So help me welcome Morgan Fainberg. How's it going, Morgan? It's going well. So, you know, big release with Kilo, federated identity. Can you tell us a little bit more about what it is, what it enables? Sure, well, let's be clear. We've had federated identity in OpenStack and Keystone since Icehouse. What's new is the ability to really use a Keystone-to-Keystone deployment. Okay, so linking OpenStack cloud. Yes, single source of identity, all controlled from one place. You don't have to worry about having every one of those sources of identity, every one of your partners, also having to have the data linked to every one of your clouds. So you can expand and contract dynamically, as needed. Much as digital film tree is done with HP and BlueBox and this proof of concept. So what are the protocols? What are the technologies? What's the process involved to make that happen? So you start by authenticating with your private cloud, just like you normally would. You have username, password, and you get a token back. You can act on the resources on the cloud. You can create instances, do Swift things, even manage Keystone assets, make changes. At that point, you decide, I wanna work with another provider. I wanna work with BlueBox. I wanna work with HP. And I hand Keystone token and say, give me my authentication that these provider can understand. In this case, we use SAML assertions, the SAML-to-Spec. The reason being is that it's a known quantity. It's a standard. The corporate security overlords, when they say, how are we going to do this? Yeah, they know it's a known quantity. We don't have to justify, this is a crazy new technology. It's fairly well understood. Okay, so this enables us to have a primary identity provider to take those resources and manage them in that instance but then also to take our identity and go manage resources somewhere else. Absolutely. And once you authenticate to the remote cloud and the SAML assertion really is just a bundle of attributes. You are in fact, Jonathan Brice and you're allowed to do these things. At that point, you're giving a Keystone token again but now on the remote cloud. Guess what? Works the same as on your private cloud. Everything is the same. So it sounds like it's easy to spread the resources out but how does that work in terms of security if I want to bring resources back in or control this kind of sprawl of everything and who has access to it? So there's two pieces with the security. The first piece is that when I am removing a partner cloud, just because I don't need the capacity right now, I can remove that from the service catalog and nobody can act and consume resources for it and that's a new feature in Kilo as well that the service providers are part of the service catalog. But more importantly, you have control of each individual user from a central source meaning that if we decide that we're going to not let Jonathan Brice access any of the content that's run real anymore because we're done with that. Yeah, we don't need you to do that. At that point, we remove your access at the central source, at the digital film tree private cloud and you no longer have access in HP, in Blue Box or any of the other clouds that have been expanded for this. And this is important for your industry especially because you were saying that the security and access is so critical but before you would have to go physically pick these devices up, pick these drives up. Absolutely, and we're firing people left and right. So, you know. Okay, well, so I want to see, you know, you have these services that you talked about and I want to see how you can expand them from, you know, your private cloud out. Absolutely, so let's go to the demo on Guillaume's laptop here. What we have here, proof of concept, not pretty, not pretty by any means, not styled. So, what we have here is, you know, we're already running a couple of instances. We're running private instances of our OpenStack. We're running some workloads on top of Brackspace. And we're going to go ahead and add a service to replicate and we're going to replicate that from DFT since we're the identity provider in this case. We're going to replicate our ingest and storage instances. So, basically that's Swift and Nova Compute. And we're going to replicate them to HP Cloud East. And we're going to hit submit. And we're going to start booting up those instances on HP Cloud East and transitioning that workload there. And if you were to look behind the scenes and really take a look at what was being run, it's the same commands, it's the same hooks into libraries that if you type Nova boot, if you told Nova client to create these instances, it looks the same, it really is the same, it uses the same tool chain that already exists within OpenStack. So, we don't have time to get into all of the details of how you made that happen. But I know that you guys have another session that's happening later today and it's the Federated Identity Deep Dive and it's going to be 340 today. So, if you want to go find out how they made it work and you're going to have all of the texts from the different companies that enabled this there, right? Yep. Then, you know, find this session, look it up in your app and go check out the Federated Identity Deep Dive. And definitely come ask your questions. We really want to answer your questions so that you can also make use of this technology. Cool. Thank you very much, Morgan. Thanks for having me. Thank you so much. Okay, so, what's next? So, I think we should check back with Thomas and figure out whether he's still employed with me. Thomas! Hello. Are you done? I am, yes. I have everything completed and it looks like we are up and ready for viewing. Ah, okay, so what do we do to view this? I think we should view it on my phone. It's very much like a Hollywood producer of you there. Absolutely. So, we're logged into Critique, which is our video streaming application. We're getting a little peek at some of the shows that you work on here. Again, that's going to peek at my password, too. Don't worry, I use that same password for everything. So, is it OpenStack 51815? Yes, sir. Great. Okay, so what do we have here? Okay, so we got the shot. That was the reserved seating section for a press and analyst. Can you put them back? Oh, really? I'll try and find them. Thank you so much, Thomas. Thank you very much, Thomas. No problem. So, that was pretty cool. I mean, we shot some footage here. We put it in a cloud, replicated it to LA. He did, what did he do to it? He did some color. He did some visual effects. I mean, and I have to be honest, the turnarounds on Rio were crazy, but they weren't six and a half minutes, which we just pulled off. Yeah, I mean, that was awesome. That was very, very cool. And none of this unreal or that shot would have been possible without OpenStack Cloud and without you guys in the OpenStack community and really driving this forward. So, what we wanted to show you as a last little piece is the end credit bed from the first episode of Unreal, that premieres in two weeks, and let's roll that video. Thank you so much. I am always in awe. Thank you. Thank you for helping. So, that is, that's the OpenStack community's first film and television credit. And we're gonna get to see that in two weeks when this show premieres. You know, Guillaume, he talked about going from camera to cloud. And how, you know, that is what they have to do right now in the film and television industry. And it's all powered by OpenStack. But there's actually another step that you can do with OpenStack, not just from camera to cloud. We can go all the way from camera to couch. So, help me welcome some friends from Comcast, Mark Mule, Sheila Saby, and Andrew Metri. Hi. How you doing? Good to see you. Good to see you, guys. Nice to see you. Thanks for having us. So, what can you show us here? Well, I thought we might at least try to see if we could get a preview of Guillaume's work. Okay. Unreal. Do our search here. There we go. Looks like we've got a trailer. Okay, so this is, yeah, that looks like the show that Guillaume was talking about. And this is, you know, we brought, you brought your couch, thank you. I know the hotel rooms are scarce here. You didn't have to sleep on the couch. I could have gotten your room. Got rooms. Okay, so let's see what the trailer is here for the show. Hello, ladies. If you haven't got problems, I feel bad for your son. Oh, nice. People are gonna hate her. Action. All right, so there's Guillaume's work. Maybe it's safer to stop there. And, you know, here we really see that OpenStack plays a part in the production of this all the way through to, you know, watching it in your home. Exactly right. So we were here in Portland, you know, a couple years ago, and we showed the X1 guide working on top of OpenStack. And we put a lot more stuff on our OpenStack infrastructure. You know, all of the applications that we showed the last time around, like the Weather app, runs on top of OpenStack today. There's a number of other challenging apps that we've moved over to the OpenStack infrastructure. And really let us do things like for the Super Bowl or for World Cup, you only have a few weeks from the moment when all of the people that are creative decide what they want to implement to when you actually have to have it ready for millions of users. And so in a period of about four weeks, we can create an app from scratch, get it running, and scale it up for millions of Comcast customers. Now, I know, you know, that was a really cool demo that you did before, but you just talked into your remote. I did. And I like to play with that. Oh, you like the toys, sure. So how does that work? This is our talking guide, which we have turned off, and this is the voice remote. So there's a little blue button there. Press it. You'll get a little audio prompt and then try a movie quote. Okay. We had an alien abductions. We could stay with the space theme. May the force be with you. Since I'm in the Weather app, hit exit to go all the way back out. Sorry. Here we go. Oh, it actually did it. And it did the search in the background. So there's Star Wars. So we've got a bunch of trailers. You can buy some movies to keep. Your app integrations. Yep. You know, we had Kilo, which our Kilo logo was a little spinal tap reference. This one goes to 11. Uh-oh, that one might be tough. Oh, okay. Oh, it was worth a try. So a lot of new apps in here and tight turnarounds on them, but Andrew, I know that you guys have also grown your infrastructure quite a bit during this time. Yeah, actually, so since Atlanta, we've tripled our infrastructure doubled since Paris. And the treatment's grown about five times since we last demoed in Portland. We now have, our cloud serves internal customers. It's our products and services that run on it. And we have almost 600 different internal projects or tenants running on our cloud and 1,700 users of our infrastructure today. 600 customers, 1,700 users. That's serious infrastructure. Apps like, or NFV voice apps, real-time video apps, all running on top of cloud today. Okay, well the thing that I really appreciate about you guys is how much you give back to the community. And we were just in Philly a couple of months ago for the operators meetup. Yes, we hosted the operators meetup in Philadelphia in March. We've also led the IPv6 sub team in Neutron. We've contributed to about, I want to say over 37,000 lines of code. And we'll continue to do more. And we're excited. Well that's awesome. Most OpenStack users are not going to be contributing like that. But when we get some users like Comcast, like Yahoo, who are doing that, it really helps keep the code base and the projects focused on the things that are critical for real-world use cases. And because of that, you guys are one of our finalists for our Super User Award. So congratulations for that. Thank you. And yes, tomorrow we are going to be announcing the winner of that. So thank you for joining us. And you'll have to come back tomorrow and see how you fare in the Super User Award. Thanks a lot, Jonathan. Thanks, Andrew and Sheila. Thanks.