 We have a very serious discussion. I'm not comfortable for the audiences. So it's going to be a tough dialogue. Hey, thanks so much for joining. Hey, Todd, when you get a chance, can you close that door? Can you close the door when you get a chance? Can you close the door when you get next? It's a lot of background noise, you know? Thank you so much for joining. What I would hope we would do in the next, I believe it's only 40 minutes or so, is maybe kind of do a little journey together. It's always nice to do retrospectives, not just code, but in life, and kind of think about where we've been as a community and where as a community we are headed and also give some perspective from our clients where we think we might want to focus on. And so the way we're going to kind of divide this between myself and Dr. Moe here, we call him Dr. M, is I'll do kind of the community upfront stuff, little context setting, and then maybe get into some of the, you know, where we are and where we're headed. And then Moe will give a, I think, a very well-grounded perspective on a lot of our clients and what they're doing and how we're helping them, but also hopefully focus the aperture, right? Because in OpenStack, the past couple of years, it really has been about focusing that aperture. It's been about users, right, and developers. We used to call that the OpenStack way, right? Do you all remember back when, you know, for those of you who've been involved, how many of you have been involved with OpenStack for four years? OK, five years, or less of you, three years, two years, ah, very good, one year. Ah, very good, very good. So this will be good for everybody. Well, back when, you know, when we kind of, as a group, a collective of kind of OpenStackers started this, I remember, I walked in and I had a conversation with Jonathan at Rackspace, who's still at Rackspace, and Mark was there and said, hey, you know, let's do something special. You all got this great community, you know, Rackspace, a bunch of folks. Maybe we can kind of create a foundation and get a lot of energy around this. And, you know, at the time, there was a lot of things going on, right, you know, CloudStack, Eucalyptus, a whole bunch of stuff. And, you know, hats off to the Rackspace folks in the community, because they said, yeah, you know what, open governance, right, creating a meritocracy, a division between church and state, right, where perhaps vendors can support the organization, but the decisions are made by you all, the people, the community, right, that just might work. And then we can scale the so-called OpenStack way. And if you fast forward from that moment in time, where essentially it was basically six vendors tried to kind of help create this movement. And then you add all of you who entered. And where we are now, it's simply mind-blowing. And what we have done for society, for the industry, for technology is simply unbelievable, because OpenStack is the ubiquitous open source infrastructure as a service platform, period, hands down. I mean, so, round of applause to you all. Thank you for those of you who have been here. Now, but with great power comes what? Awesome responsibility, right? We have a responsibility, because when you think about what we've been designing in OpenStack, right, especially initially, you know, in those days, we were really thinking about on-premise, right, capability behind your four walls, compute, storage, networking. We had a really good architecture, right, Mo, you know, a very modular, you know, allowing an ecosystem of partners, allowing well-defined interfaces. Yes, I know we've got still lots to do in these places, but, you know, we kind of had that in mind. And then we kind of started to transition as a community into understanding what this meant in a public cloud context. And then most recently, right, what does this mean in the hybrid context? Connecting the left and right-hand side. But we never forgot about skills. You know, I walk through the floor, and you have companies like IBM, Mirantis, all of you, right, who have skills to help clients accelerate. This is hugely important. As a community, we need to be able to serve the hunger, right? Everyone wants a big Mac, so you've got to make those big Macs faster, right? And you do that by getting more people that could help implement things. So that's really important. But it's also very important that, for those of us in the community to understand, that we can't be siloed, right? So if you are focused on, where's Brad? I'm looking for Brad. He's hiding from me. If you're focused on Keystone, right? You can't just focus on Keystone. You have to know what's going on in Horizon, right? For example, we'll talk about that, right? You have to have T-shaped skills, right? And that, I think, as open-stackers, is what differentiates us. Because all of us in these projects understand what's happening to our left and our right. And by the way, I really do believe that the open-stack way is the future of open source, OK? And I'll get into that in a moment. So what's driving, then? What's driving a lot of the innovation that's happened in the last three to four, and certainly this last year? And it's the realization that, at the end of the day, what we're doing is providing a flexible canvas. Just hear me out for a second, right? Did you start laughing? You laughing at me, Brad? You're laughing, I'm kidding. I'm just joking. So think of a painting. The business folks want developers to build a beautiful painting. I want to lease off that, right? But in order to do that, you need to have many colors, right? Think of colors as APIs. And you also need to have brushes, lots of brushes. What are those brushes? I don't know, pieces of middleware that you use heat and hot to lay out, right? I don't know. And you also need a canvas. And that canvas can't be this small. It needs to be able to change. And different than a typical painting, you need to be able to take an X sketch, shake it, and change that painting, right? Change the size of the canvas. Change your colors. That is what's been driving us when you look at a flexible infrastructure as a service or a flexible platform as a service like what we're doing on Cloud Foundry and all the work that we're doing around APIs. That is the context. Because if you combine the ability to have that flexibility, that level of interoperability, whether it's IBM's cloud or anybody else's cloud, right? You give the power to your business folks to compete, be differentiated, and perhaps more importantly, help serve their clients, right? And that's really what's driving all this. And we've always had this kind of in the back of our heads, but the clarity is becoming, I think, much more crystal for all of us. So now, to this point around OpenStack and the future of open source. So for those of us who've been, and I'm young, I mean, I'm just 21, and so I'm kind of new to this, but why are you laughing at me? Does this have an email to Jonathan? You're telling me you're laughing at me, all right? You know, back in the early days of the web, does anyone know why HTML was created? Why, what was the use case for the extensible markup language XML? It wasn't for config files. Flexibility? No, sorry. I mean, that's what we're using for now. Documentation, yeah, very cool, SGML, right? Dissil. It was for actually disseminating math and physics information. Tim Berners-Lee worked on it to disseminate physics. I cared about math, I was at IBM Research. So I worked with Tim, co-authored a lot of these things, worked on CSS, all these beautiful, spend, where's Chris? Chris, I think, is here. Chris and I were doing lots of fun things. I have hair though, isn't that nice? I'm just saying. And, but see, so it was beautiful times, and I would argue that it was quite successful because all that we enjoy now is built on these protocols, right, HTTP. We helped create Apache, the Apache license. Who doesn't like the Apache license, right? Eclipse, there's so much that happened. It was in a renaissance, it was an IT renaissance, and here we are now, literally, 20 years later, I think. Wow, you know, in this renaissance again, but it's very different. And I would argue that if we as a community are not successful in OpenStack and the OpenStack way, we're gonna have a real hard time, okay, because what's different now is back then it was a bunch of academics. Now, it's end users involved in creating the open technology now. The use cases are much more aware. So when we create this stuff, right, you know, and we're in a horizon, you know, half my team's at, you know, these different sessions designing things, right? You know, when we're at the horizon session or the Keystone session or the Cinder or whatever, you've got end users, with developers, architects, talking about what needs to be built. That is the future of open source, okay? That is the future of open source. All open source efforts that I think that will be successful are those that combine those two things. Because the level of innovation you have, the level of ecosystem, the level of participation is unbounded, right? If not, you're simply creating garbage. I call it garbage code. You know, I used to teach computer science for graduate students and I go to GitHub. I literally just get a little ill because there's a lot of garbage, you know? And garbage is like, we take garbage to the curb, you know, if nobody uses it, it just piles up, right? That's useless. Hashtag what? No bueno. No bueno. Right, you don't want that. Not good, right? And so we don't want garbage code. So when you look at cloud, you look at data, mobile, analytics, all these areas that are kind of changing the world is digital disruption mode, right? All of these things is driven by open communities and I would argue linchpin open communities that have this kind of user open-source perspective to it. So now a little bit on OpenStack and IBM. First of all, man, that was a ton of code in this last release. Kilo, get it? It didn't work for you. It took you a second to get that? Wow. I was like, that was funny. At least at the time, I was like, Kilo, it's a time. When I'm in Europe. What? In Europe, they would get it. This is not America. I know. Oh, that's true, actually. That is true. Although there is a target five miles away from here, so. That is true. It's okay. I'm just saying. But someone shushed me. I'm saying you, Eric, you just shushed me. Those Germans. I know. They're so strict. I'm just kidding. Think about it. I mean, 13, of all the statistics here, the thing that blows my mind is 13% increase in Kilo contributors from Juneau. Ha, I mean, think about that. The community not only has grown in participants, but has grown in number of developers. I mean, if there's one picture, you're gonna take pictures of them, this is the one. Because this shows that we have arrived and that people are actually contributing real code. This kind of growth is just, I've never seen anything grow at this pace. And we've been real proud in IBM. When we helped start this, and we helped create the foundation, in fact, Todd, is Todd here? Like, I'm blind. What's that about? What's that about? Todd helped write the bylaws and all the American, that we all follow, right? All the rules and stuff, code of conduct and all that. And when we helped start this, you know how many contributors we got for writing a check to create, give Jonathan a job and create all this stuff? How much contributors we got for that? We got zero. Zero. We earned our stripes, just like everybody else does. That's beautiful, separation of church and state. And then, very, very proud of the initial work we did, which is mostly directed by our friend Chris at the time. Thank you. And to where we are now, right? We've gone from 50 folks in IBM to close to 500 developers in IBM fully focused on helping OpenStack. Yeah, it helps our products, for sure, right? We've got OpenStack and Mo will get into this on-premise, off-premise, right? Managed, dedicated, everyone in between. So yes, it helps us, but it helps everybody. It's about increasing the market, about increasing the share, right? I mean, the sheer number of blueprints, close to 70 blueprints, that we helped implement and deliver. That's just beautiful. So there's a couple of things in OpenStack that we worked on that I think I wanted to highlight, and then I have two challenges, okay? And one of them is a physical challenge, and I'm kidding. Just wanna see if you're awake still. Okay, so I'm gonna go a little deeper into some of these, and three more charts. And Mo, you're on in about four to five minutes, just so you can start. Okay, ready? Okay, to boot up? Start booting up, start the process, select your hypervisor. Uh-huh. All right. I'm starting. KVM. So, I'm not gonna call it Cinder, heat and hot. I absolutely love heat and hot, but there's so much confusion around orchestration. People think that the big O orchestration is the same thing. Orchestration's in the eye of the beholder. And what we're doing in heat and hot is incredibly important, because the ability to lay down the technology, manage it, deal with the life cycle, to be able to model real architectures, right? Not just toy applications, but something like SAP, right? Which is a real app business application. In OpenStack, using ideas from the Tosca working group is simply important for enterprise adoption. And the work the teams have done together around that, I'm very, very proud of. Because this helps accelerate the adoption of OpenStack within enterprises, right? Which helps us all. Another one is the CLI work, right? I don't know about you, I still use a lot of command lines myself. I get very frustrated with GUIs, although I'll say nice things about Horizon. But the work we did in the CLI, and finally having that out there, I think is quite important. And I think the most important one, which I don't have a slide dedicated to, which I should, is interoperability. And I'm very, very proud of all the work around Def Core and especially Ref Stack. Catherine got the plus one from our team to help lead that. And I'm really, really, really excited about that. For us to move to the next phase of OpenStack, we need to create that liquid canvas, right? Not just between IBM products, that's good, that works. But with our competitors, right? I mean, think about it. Let's imagine that you happen to be running OpenStack, I don't know, let's say Rackspace in the US, that's cool. But then all of a sudden you wanna go to Germany because all small companies wanna be big, right? All of a sudden they wanna sell something in Germany. But they can't because Rackspace doesn't have a data center in Germany. Oh, we've got 40 IBM data centers, software data centers across the world. Have a couple of days, a couple in Germany as well. OpenStack everywhere. Now it becomes easier to extend your canvas. Why would you wanna do that in Germany? Well, there's regulatory reasons, there's locality of data and applicators, lots of reasons to have, you know, not deal with networks, right? So that I think is probably between that and heat and hot, very, very important parts of where we IBM are gonna continue to help drive innovation and where I kind of think and challenge you all to look at. On the cinder side, you know, I think there was two really big things that we worked on and would love to get more feedback from you all as well. One is around replication and migration of information. I think that's very, very important. You know, it's a use case that we get from clients all the time. You know, I'm curious to see if you guys have more practical experience from where you've been and if there's any dialogue you wanna have around that. We've got some of the cinder folks here. Federated identity and, you know, I think we should give a slow clap to Brad, right? Everybody ready? Slow. Brad, Brad, oh, thank you, thank you. Brad in the back, you know, he's a nice guy, nice Southern, he's in Raleigh, a nice guy, but man, you have a big stick, you know. The work that he did with everybody around open ID, around CADF, around making sure that we don't think of security just as an open stack concept, right? Yeah, federated keystone and all of that stuff is really important, right? Being able to have security, you know, essentially seamlessly span on-premise to off-premise or manage dedicated, that's hugely important. But understanding that, well, how does this relate to security context in the platform layer? What are you doing in Cloud Foundry? Oh, and what about the device? Partnering with Yahoo, right? On the horizon side, for example. People input stuff in, right? It's about thinking across those layers. So I think that's some really cool stuff. And of course, Horizon. You know, I think there's the opportunity we have ahead of us for bringing in many, because, you know, user interfaces and ways of interacting with systems is like clothing. You know, some people dress very nicely like me. Some people not so nice. I'm not pointing out anything, I'm just saying. I don't know why I even looked in that direction, right? So it's in the eye of the beholder. You know, some people think they look good. He doesn't like your shoes. I wasn't looking at you, but that's very nice. So, but what's important here is the modularity. And frankly, the performance. This model view control decomposition, some of the stuff we're doing with Angular, and the ability to refresh pages, right? On the fly. So I think those are all very important things. So before I turn it over to Moe, I'd like to leave you with two very, very, very important challenges. If there's anything I've said, you know, that may be interesting, ignore it. Here we go. I'm kidding. All right, first thing, okay? When it comes to OpenStack and where we're headed, it's important that you look left and right. And we have been doing this as a community within OpenStack. Got it. But here we go to challenge number two. You gotta reach out beyond your community. Because what we are creating here, and what OpenStack started, is an open cloud architecture, right? Not just Compute Storage and Network. It's containers. It's platform as a service. It's open data with what we're doing with Hadoop. It's node. It's couch, right? It's all the different things that are coming together when people try to essentially build an open source based cloud platform. I mean, that's an IBM is how we're building our technology, right? All of this is in our cloud. When you use the IBM cloud, you are using this technology in the inside. Not some bolt on, not some API emulation. It's in there, okay? The web was successful. Because every modern day application server has the Apache HTTP code in it. When you type in SAP.com, you don't worry about whether you're gonna get the page. You're gonna get it. It's the same code, right? That's the point. When you use OpenStack, it's the same code. And you need to think beyond that and make sure that the work we're doing in Magnum, right? For working with Docker, right? The work that we're doing in Bosch and Cloud Foundry and getting those APIs and the OpenStack APIs. I'm looking at you now. Very closely, right? The work that we're doing higher up around the middleware. All need to kind of start coming together. And we, IBM, are doing that. We're in all of those communities, right? We've got lots of developers doing open source. But we're one company, right? All of you OpenStackers need to think about that too. So with that, Mo, ground us in reality. I'm still booking. Oh, okay. So, as I was... So, thank you, Angel. And I have to say that I want to share with the non-IBM folk in the audience that I definitely am not liked or loved at IBM, because they always give me 20-minute slots when they know that I can say nothing in less than 30. And they always put me before lunch. The good news is I haven't eaten lunch, so I'm starving and talking about Big Macs and steaks. That's all I can think of. Forget about the slides. In the next 15 minutes or so, what I'm going to do is think about that canvas and painting and give it a little bit of flavor based on the clients, the feedback, the work we've done. So when you're thinking about these paintings, not all paintings are created equal. Paintings could be portraits. They could be landscapes. They could be photographs and so on and so forth. But Angel put this in a good context, a context that says OpenStack is not just about building private clouds. OpenStack is not just about public clouds. OpenStack is really about a hybrid enterprise, a hybrid environment, a hybrid cloud that brings together new styles of applications, composition of infrastructure, connectivity into existing systems and so on and so forth. What we've learned over the years when we started to talk to many of our clients is that there are many styles of paintings, but four really stood out in the world of hybrid. The first is the one that we all relate to, understood and very much so early on. And it's really around DevTest. How can I go and leverage clouds in a context of quickly developing some applications no longer constrained the developer whether it's gonna take you three weeks to stand up servers, et cetera. And then once I've actually been able to create these DevTest environments, et cetera, how do I connect them back into my production systems? That use case continues to exist in a hybrid world. The second one is what we call spillover. Started to become people called cloud bursting and all sorts of names. But from a commercial point of view, people started to say, you know what? Standing up a data center is a problem, not just because of skills, but frankly, even simple things like real estate, you know, cooling, heating, energy costs, et cetera. And you know, I'm not entirely sure if my business venture right into Sydney is going to work out or not. So instead of doing any of this, let me try and use some additional capacity to spillover when I launch that new application in Sydney. And if I decide that it's not going to work, I'm gonna scale it back. Make sense so far? No, come on guys. Make sense so far? Woohoo! Man, that was good. The third one is what we are starting to see more and more of. And it's one that I'm personally excited about. It's called the distributed applications. People really start to think about applications in the cloud in the same way that they thought about them in the old days. I have an SAP applications, it's monolithic, it's top to bottom, it's bound to a certain environment, to a certain architecture. In a cloud world, that is no longer true. The real power of a cloud-based application is that you really start to be able to put some of your front end logic in a cloud, your back end logic maybe in your own data center on some hosted environment. There is a mix and match between run times and so on and so forth. This is becoming very much a real use case and we'll come and talk to about in a minute. And then finally, the new frontier where really people from a business point of view are starting to look at portability. Now everybody thinks of the word portability just like orchestration in many ways. But portability has real business meaning. Back to our great location, Sydney. It means that I launch an application in here and I want to now launch it in Sydney. The only things I want to be able to change is I want to store the data locally in Sydney or locally in Germany or locally wherever. But I really just want to lift it and get it running in there. So it's different stage. I'm having it in pre-production to production. I want to just port it. I have it different systems or have it different geos. How do we enable that? To start with, there are really two dimensions to solving this particular problem. That's where Team IBM has been focused along with the community. Everything we've been doing with the great contributions of the community members have been centered around solving that hybrid problem and enabling it in an enterprise context. The first side of that coin is infrastructure. Now, those of you who have heard me speak on this topic or attended our IBM sessions that prior you've known me to spend a lot of time talking about this. Today I'm going to shrink it and really get concise and to the point. Hybrid infrastructure is really where open stacks started. It became the de facto enabler towards if you like access, consistency, irregardless of where you are trying to build, deploy or manage your applications. Whether it is in your own local data center, whether it's in a dedicated environment to you that is off-premises or whether it's even in a public cloud where you're accessing discrete services as opposed to total environments. We're always used to thinking about environments as everything, a virtual machine with a storage network, et cetera, that is true. But also people are starting to leverage and access things like object stores or discrete block storage, et cetera, as services. So open stack really have enabled us and we've been working towards all of the type of capability, where is Angel, did he leave? Angel, oh, there he is, thank you. Sorry, you're like, you know, bowing. So I didn't. A lot of the stuff that Angel has talked about around Keystone, some of the work that you start to do in terms of Cinder, et cetera, becomes incredible in enabling that, if you like, from an open stack, core point of view, that consistency across environments. I'm not gonna go into more into this. What I'll tell you a little bit is commercially what IBM has done is taken it a step further. When we talk with a lot of our enterprise clients, we've heard a few things, and I think you heard them in the keynotes. Just make consuming open stack a little bit easier for me guys. It's still hard, et cetera. And there are a couple of additional features and functions that I really need when I'm starting to roll out an open stack based environment at scale, when I'm really trying to load many, many applications. That comes into two flavors. Number one, how can we take things like a horizon based cloud management and start to really add the type of features and functions that client wanted? Approvals, before you deploy things, a little bit of control, access, all that kind of stuff. So that's where we've invested in adding some value on top of the core open stack function. The other area is we took some of our intellectual property in what's known as platform computing. So this is resource scheduling and optimization around placement. And we also made that work and part and parcel of what's inside of open stack. That whole combination is a package that is called the IBM Cloud Manager with open stack. You pick up this, you build your own open stack environment locally. That stack, open stack, community addition, plus pluggable modules that allow you to do a lot of the optimization placement, et cetera, plus all of the workflows that really help a lot of these clients put this sort of control and governance they want is available. That core stack is what we use throughout the rest of our portfolio. What we introduced last year on Forester, kindly I would say, Rantus as a leader in, is the new category of dedicated. What we still observed is not every client is able to go and start up open stack by themselves. Even when they're starting small and they just want to be able to get going with an experiment or even a small workload. And that's where dedicated came in. We manage it for you, it's running off-premise, but it's isolated to your environment. This has been seeing a lot of traction. I believe, most personal opinion, that the future of private clouds are going to be very much dictated by those dedicated, remotely managed environments versus all of the cost and administration that people will put into standing up their own. It's going to be a hybrid world, but I still believe that's a growing piece. So, we've had a couple of clients. Now a lot of people, when I put that chart last summit, they told me, Mo, where do you think people are? Are they doing more of the build your own? Are they doing a little bit more of the dedicated? And my answer to them is actually no, they're doing hybrid. When you look at what our partners and colleagues at Verdata were doing, they quickly started with a dedicated environment, hosted, and they decided that they want to start to bring in some of the applications back within their data centers. They used some feature that we have around a hybrid connector, so they started that whole dedicated off-premise environment, enabled a little wizard, it configured the region down locally, and now they have a hybrid setup in there. Further, people like SAP are starting to think about OpenStack in a much more scalable fashion. I will tell you guys, I talk to press like Angel, I talk to analysts, the level of enthusiasm for what the community's done in terms of scale is incredible. It's great to see Walmart and TD banks and others, and what you'll start to see is others like SAP coming. Wouldn't it be awesome for OpenStack if one day we can come and say SAP Cloud runs on OpenStack? That's the work that we're actually doing with SAP. I will tell you offline, we know what their gaps are, and we're gonna be working with the community and all of our partners to advance those, and then we'll do some more even if required. And then last but not least is one that is exciting for me, because I just talked about context of local and dedicated, but even from a public cloud perspective, the work that we actually did with partners called Kaltura in TNT Go is the realization of how OpenStack is really built for the next generation cloud applications. So this whole, if you like, streaming service that we just launched in Latin America is taking advantage of OpenStack in a context of both hosted and public services that are starting to mix and match. So if you are in doubt, the intention here is to tell you people are doing hybrid. That's my answer from summit to summit. Now I actually mentioned and said that there are two sides to this coin. Infrastructure was one, and I chose to only spend a few minutes on it because that's where we major. The other is what I wanna spend a little bit, a few more minutes on today, because this is something that Team IBM is incredibly focused on as a result of our clients are going. To really solve hybrid, you have got to pay close attention to the workload. You can do all you want on the infrastructure, but until you start to think about a workload, you're not gonna solve the problem properly. This is a classical e-commerce application. Look at this application. Do we have laser on this thing? No, we don't, okay. Right up there, you have classical systems of record. ERPs, CRMs, records are sitting there. Do we really believe people are gonna throw those things out? Is it even prudent to do that? Absolutely not. They may choose to adopt some SaaS properties for their sales processes like Salesforce, et cetera. That's okay, but the truth of the matter, these types of large record systems exist. There is new data systems that are starting to build up in their data centers. There is new social applications, Twitter, Facebook, et cetera, that people are engaging in. There are new types of devices that are being connected into this e-commerce application. I wanna be able to actually carry certain devices and be able to collect data in terms of pricing metrics, consumption, et cetera. There are mobile applications in which these are being served. All of this is being connected. This is a hybrid application. How do you enable that? Think about this. Do you build all of this application on virtual machines? Do you build all of this application in a new foundry style where you can develop it quickly? Do you build this application in a classical, you know, old three tier application? Do you build it all in SAP? The answer is it's mixed, absolutely. I want to tell you this is a real blueprint of a client. And here's the beauty of what we learned through this work. If I can build the UI module, which you guys cannot see, so I'm gonna walk on point. If you can build this UI module in containers, then you're gonna be able to scale that first module at the pace that everything will hit it. You're gonna be able to start to do a red-black much faster, right at the UI where the customer is interacting with you. What about your inventory system? Well, you've already invested and written in that. Why don't you create services to integrate into it? What about my wish list or my cart? Well, I've already have a VM running that's built around that. The new style of application, like Angel said, in a cloud-rich environment is one that combines all of these things. And that's where TMIBM is focused. How do you take the work we've done with heat and hot, the work we've done with Foundry, the work we've done with Docker, and start to enable all of this through a single experience that you can build these cloud-rich applications? We call it a cloud fabric. Run it anywhere, sets of services that are developer, network, storage, compute, using OpenStack, combined with services that allow you to extend functionality, Twitter, pricing, HR, marketing, Watson, analytics, available to you to build those rich applications with two components that are critical, an integration on one side and the other is a whole DevOps tool chain that allows you to iterate on it. This is what is behind the open cloud architecture. This is where we see a lot of the enterprises moving towards. They want that environment that allows them to tie all these things together so they can get into it. Does that make sense? All right, very good. Let's explore this a little bit further. What you see in here, because I decided to put pictures versus words, is the realization of what I just described. This is IBM's Bluemix environment. If you have not seen it, I really encourage you to go and try it out. Everybody thinks of Bluemix as a Foundry-only environment. What you see in here is containers or virtual machines enabled in a context of that rapid application development. What you see in here is clients of ours who are now able to take their open stack and register it inside of that Foundry context, inside of that Bluemix framework, where they're saying, here is my object store, write your applications to it. Nothing speaks better to this than you actually going and seeing it. And what the guys have told me is we're running it in the booth, is that right? And we have some cards in here that if you go to run in the booth and you tweet about it, apparently they're going to give you, that's it, that's the man. If you tweet about it, you're gonna get some gifts. And the reason why we're so excited that we're giving give out is this is where we believe, to Angel's point, we're finally reached a level of maturity with that we're not worried about, does this thing work or not? But we're actually starting to innovate in terms of these applications. Take it a step further. Oh, did I lose a slide? I did. I lost a slide. I lost a slide. What I was going to say is in this particular context, it's not just IBM services, but it is services and connections that we're working with the rest of the community on. One of the main areas that we're starting to think through is how do we tackle some of the networking pieces? Because in that context, you're not just building everything inside of just a foundry or an IBM cloud. You're building something on your VMware cloud in here, you're putting it in SoftLayer in there. And that's, for example, a partnership that we're doing with the Juniper team. If you again, you want to see that it's in our expo and we can talk to you about it. And finally, which is where Angel really started, to do all of this means that each and every one of those things have to be contributing and part of this open cloud architecture that we're driving to. My time is up. You're giving me the look. With that, I hope I sort of gave you a quick flyover around where we're focused, where we're going and what we're trying to achieve. And hopefully you see that a lot of this is starting to come to life. If anybody wants to go into more client details or more functions, happy to do with that. And last but not least, this is what Angel does very well, the spiritual part. I've been with IBM. This is a little bit of a clue. Yeah, he's meditating. I've been with IBM a little bit over, actually a little under, then half of my living life that hit me yesterday. And I was like, wow, that's incredible. And what excites me about this time and people say, how can people continue to innovate in this type of environment? And I say to them, what's exciting about this particular time is that it's a time where speed is the currency and innovation matters the most. And in IBM, everybody in this room that I've been working with has been a great innovator. The good news is we're looking for some more folks to come and join us. We've been innovating for 100 years and I hope that we're gonna innovate for 100 years more to go. And we only do that when we bring amazing, passionate people to the table. So if you're not gonna go and try the VM in Bluemix, then certainly go and visit our recruitment booth. Thank you guys, appreciate it.