 How's everyone doing? Good? Excellent. Hey, thank you so much for coming. I need to watch the time, because I tend to lose track of the time, and Dave will get anxious. So first of all, thank you all for coming to the OpenStack Summit. I remember back when we had our first set of conferences 2011, even before that. And I used to say it was a dog, a pigeon, a parakeet, and a couple of developers. And that was pretty much OpenStack. And hats off to the Rackspace folks for understanding that to truly grow an ecosystem, to create a community, to empower users, developers, operators, you really have to create an open foundation. And I'm presenting today with Dave Lindquist, who's over here. By the way, I'm Angel Diaz. I'm with IBM. And Dave is also with IBM. Dave is our IBM fellow for cloud technologies. And I have responsibility for all the things that we do around open source and standards, as well as our cloud performance labs out in Silicon Valley. But I remember, Dave, when you and I, and Todd and some of us here in the front, met with Rackspace back in the 2011-ish time frame and said, there's a lot of stuff going on. If you look at Eucalyptus cloud stack, because guys ever hear of those things before? Do you still think about them? Probably not. No. And what we wanted to do was to see if we can take something which is good code, great people, great community, and explode it out, and try to get a de facto infrastructure as a service platform. I mean, that was our objective. It was very, very clear. And then what happened was, as I'm sure a lot of you know, who've been involved in this for a while, like us, it started with a humble, small group of founding sponsors to try to stand up this organization. Jonathan was so kind to take over the executive sponsorship role, which, by the way, he gets well compensated for. But we created a wonderful community, and the rest is history. I mean, here we are with yet another summit, another great location. Hong Kong was our last one. And we're upwards of 5,000 or so folks at this event, at an open source conference. It's simply amazing. So what I was hoping we could accomplish in the next, I think we have like 40 minutes or so, is to kind of give you a historical perspective of where we've been with OpenSAC. But I think, perhaps more importantly, where we, as a community, and where we, IBM, and where our clients view this heading. There's a couple of dimensions that I think that are kind of really important to understand. And that certainly reflects where we are doing a lot of our work in OpenSAC. We're very, very active, as you'll see. And then also try to introduce some concepts that are really important for the application side of the house. We always talk about DevOps, and we talk about the importance of developers and folks who do operations. But there is a equivalent kind of renaissance occurring in the application space, which is very, very synergistic and important to those of us who think about infrastructure or data centers. We are providing to the application people foundational technology, compute storage network. But it doesn't stop there. Why not provide data stores, messaging, all kinds of other types of reusable components, which then application folks can develop in this so-called polyglot world that they live in and be quicker and faster about what they do their business. There are open communities coming together there. So that's when you kind of read the abstract to this. We talked about kind of the new additional members to the band. I like to spend kind of half of this time talking about that. What are some of the technologies that are very synergistic? Because a lot of the original band members that helped kind of push along and fund and create and enable all of you in this ecosystem are doing the same thing at the platform layer. And I'm real proud of that. And I like to talk a little bit about that as well. And some of the importance of these things working together. So that's kind of what we got planned. Is that OK? I can change it. We had the NFL draft, right? I'm happy to talk about that. I am a Washington Reskins fan. I know, I'm sorry. But we can change topics. Are you OK with that? All right, we'll go. So first thing, what is amazing to me is that when we ask our CIOs, and we're going to have to bear with this thing flickering back and forth. I don't know what's going on, but don't pay attention to the screen. Just pay attention to me. See, watch my hands. Got it? OK. When you, we can go without charts if this is a problem. All right, so he told me to change charts, no? All right, I'll continue. When we talk to our CIOs, and we do surveys, and folks understand how our clients are thinking what they're doing, we should all feel really good. Because for the past couple of years, technology, and in particular what's happening in the open communities, is driving what they're doing. And then when you kind of look at the urgency that they have, in terms of how fast they need to adopt these new technologies like OpenStack, the majority of folks understand that the urgency is either past them, or they have to do it now. And that's why this conference we're so focused at users and case studies. You heard of the main tent today. It's all about what folks are doing with the technology. There is a small percentage, I think, four to five that don't believe that they need to be worried about anything. I don't want to be those people. But that's kind of how this breaks down. And the phenomenon of how we are all as a community developing code, not just in OpenStack, but all the open source projects that are dependencies and related to us here in OpenStack, is very similar to what happened in the early 90s but a very different set of things. So back in the early 90s, just to draw a couple of analogies, there was a big focus on creating the web around open technologies and participating and collaborating. But there was literally a handful of people doing that. And for the most part, end users weren't really involved. Now, there are thousands of people doing it, and the end users are first class citizens. That's really, really important. It is really important that for us as open communities to build the right software for the people using it, the end users need to be involved in a first class way. Now, these are beautiful charts. It's too bad you're not seeing them. So that's all right. There you go. You can see it briefly. It looks nice. So going back to what I was saying about this de facto open source infrastructure as a service platform, as a community, we were really focused on trying to bring together anyone who thought about this. So when we IBM were thinking about what was going on, Dave was leading a team that has something called High Scale Low Touch. Really, really fast infrastructure as a service technology, which we're trying to debate what to do with. Should we open it up? Should we create our own thing? Well, between now, then and now, we've contributed a lot of that intellectual property, probably, but also code where appropriate into OpenStack. It was the right thing to do. Our partners did the same. And I think when you look at metrics, and that's what this graph showed you, of other infrastructure as a service communities like Eucalyptus, or Cloud Stack, or other things, in terms of vibrancy of the population, in terms of code commits, et cetera, by far OpenStack is the most active hands down. And that's something we should all be very proud of. That's something, I'm just taking pictures of me in an empty screen, I'll pose for you. That's something we should all be very, very proud of. And specifically, for us in IBM, who've been steadily growing our participation. So the next chart that you're not seeing is a beautiful roadmap chart. Just kind of picture this in your head. But it starts back in 2011, or 2012, when we helped start the foundation. And IBM had literally one core contributor, a couple of technical contributors, no blueprints. We were earning our stripes. In fact, we were helping quite a bit in the testing aspects of this, as well as the internationalization. But like any other open community, although you help stand up a foundation, if you wanna have influence, you need to contribute. You need to show your value, you need to grow. So steadily from release to release to release, and this is on this picture you're not seeing, our contributions have been growing. And the different focus areas, oh, there it is, this is beautiful. The different focus areas of where we have contributed over time has been growing. To the point now where we've got, about for Icehouse, 14 core contributors, 99 technical contributors, a bunch of commits, tons of blueprints and projects, right? And kind of we're in the top three in terms of contributing to the OpenStack world. So we're very proud to be doing that. But what I'm even more excited about is to say, you know who's number one? You guys have a guess? Who's number one? The individual contributor is number one. The number of individual contributors make up the large percentage of code, right? And that is a healthy ecosystem. It's not some single vendor like us or someone else doing all, it's all of you. So thank you. So we're at the Icehouse release. I think at this point it's fair to say from an open source infrastructure as a service perspective, OpenStack is simply unstoppable. I don't think, I don't know if Jonathan will say that, but I will say it for him. It is simply unstoppable. We continue to have more contributions in the code. The individual membership has increased dramatically. Again, these are end users who are fanatics, who are writing code on top of their day job is increasing. And that little project that we started on translation has grown to 16, yeah, nine primary languages. So it's amazing kind of where this has gone. So with that, I'm gonna hand it over to Dave and I think the charts are working now, so you're all set. And we'll get into a little bit about specifically what we've been up to, all right, Dave. Thanks, Angel. In particular this morning, I really enjoyed the discussions in the keynote with the super users. Listening to the super users talk about what are some of the critical things to them in OpenStack? In particular, the operations making the system more robust, the developer experience, how can we accelerate the delivery and support the delivery of applications and the hybrid models? How can we really make OpenStack come to life in hybrid clouds with the interoperability and the ability to source services, resources across clouds, across the internet? Now starting with what Jonathan and Glenn from Wells Fargo discussed, they really put an emphasis on operations. They really put an emphasis on what was happening, particularly in Icehouse, with operations. And collectively in the community, I was really pleased to see that focus and then the emerging focus on the developers and IBM along with the community. Some of the key areas that we really focused on from an operations perspective were just basic services like notification for ops, for metering, monitoring, audit trails, high availability, upgrades. How do you do live upgrades? All pieces that are core to enterprises and service providers are like to provide a robust open cloud platform. So that has been our focus for the last couple of releases and will continue to be the focus for the community for the foreseeable future. And this is critical to accelerating the adoption and deployment of OpenStack. Now equally critical is the role OpenStack plays in accelerating the delivery of applications, of new applications, of new business processes, of new business models. And the tools that will emerge around this open ecosystem. If you consider what's going on in businesses across all industries around the world, what you'll see is that these businesses are leveraging mobility to extend their reach to their customers, to their partners, to their employees. They're pulling in social mechanisms, social applications to create very compelling interactions. And they're using big data and business analytics to really understand the behavior of communities and the behavior of their customers. What they're trying to do is understand what opportunities exist. What are some of the weaknesses? What are some of the new opportunities? That's what's going on with the analytics. And so why speed has become so critical is really the basics of business. Can I recognize what's happening in the market? Can I bring my idea, my new business application, my new business process to market faster than my competitors? Can I test the market? Can I understand if I'm achieving those business outcomes? If I'm achieving those business outcomes, iterating through that cycle to achieve those outcomes, then can I begin to scale this application? Then can I begin to monetize support, et cetera, this new application, this new business process? That's where the tools building up around OpenStack for the developers are so critical. Tools like Bluemix, a recent announcement that we've had in IBM, which leverages an open source community, Cloud Foundry, where we can rapidly compose services to build applications, compose application services, messaging services, data services, development tools, test tools, as well as management systems. Here, this composition allows developers to very rapidly put an environment together, deliver an application in market in minutes, test the market with their applications, understand if they're achieving that business outcome, iterate till they start moving towards that business outcome. To complement Bluemix system, Bluemix, we have DevOps services, a full life cycle from design, dev, test, right into production with the management systems. These are delivered as a service. These components are composable into the Bluemix environment, so you can have collaborative dev. You can have builds, the test, promotion, managing your application artifacts, as well as a management system for application performance management, for workload automation, for control desk, for asset management, et cetera, come together within this composable environment and that management system part is referred to as service engage. I strongly encourage you to go out to test out and try out Bluemix. It's open beta right now. It's very compelling environment to use. It's free and I think it'd be very impressed as a developer how these environments come together in this composition. Now, taking a moment to reflect on hybrid clouds, from a business perspective, I'd like you to think about is not hybrid necessarily just from sourcing of clouds from the infrastructure, but think about it in the context of what we just went through in the application space and how to rapidly deliver applications to market. What's happening in hybrid is really how can I begin to leverage the APIs, the services, the API economy that exists to rapidly pull together new applications where these services opened up to these APIs are available across the internet, across clouds? How can I rapidly compose the run times, the environment I need to run my application again with services that are running across clouds? And then how can I consume or compose the resources I need from compute, storage and networking at the infrastructure layers? That's what we mean by a dynamic cloud. That's what we mean by a composable business. That's the outcome that businesses are trying to achieve is how can I rapidly leverage APIs, services, infrastructure across the internet, across clouds to create this hybrid environment? Now, open technologies like OpenStack are absolutely critical to pulling this off. To me, it's the only way this will be pulled off is through these open standards and open source. OpenStack is a critical layer at the infrastructure layer, critical at the abstraction of the underlying compute, storage, networking. Then the next layer, elements like the platform as a service layer, this is where open foundations like Cloud Foundry are so important. This is where we can begin to create the composition of services in an open fabric running on OpenStack. And then standards like Tosca for pattern support and linked data to really accelerate how quickly we can integrate services and integrate data across a variety of systems. So this base level of open technologies and open standards is what will make the hybrid dynamic environment a reality, and they are a reality. Couple examples, I wanna go through just three quick examples that we see over and over again as patterns with customers in this open cloud environment, in the ability to rapidly construct applications to deliver in this hybrid environment. One of the patterns that comes up over and over again with enterprises in particular is how do I pull together the optimizations and the flexibility of the underlying infrastructure with the full life cycle of DevOps. And here what we see is the ability to, through OpenStack and orchestration and patterns, the ability to deploy patterns down into an open stack environment on public and private environments. And then the ability to integrate those optimizations of the infrastructure with the full life cycle. In this example, with Urban Code, which helps manage the application artifacts, helps you model your applications, helps you govern and track and deploy the application artifacts into these environments. So this really accelerates how quickly you can put together a DevOps model, the full life cycle, with the optimizations of the infrastructure. Great example of this is a company that I just met with last week and we had been working with him for a while now, Novatech. Novatech is a German company, consultants, and they work with a lot of clients and building this type of an environment. They also put together a very leading edge application, a mobile application for fleets and automobile manufacturers in Germany. What it does is optimize routes and scheduling of refilling at stations by bringing together the route schedules along with the price of fuel throughout the country. And they brought this together in a mobile application. And what they were after is, how could I very rapidly deploy this application into public clouds as well as into private environments for particular partners? And then how could I manage it through the life cycle? And here, what we worked with them on is how to model their application using TASCA, the Topology and Orchestration Specification Oasis, and interpret that through an orchestrator and then optimize that deployment into the various environments. In literally two days, they were able to use some of the open source technologies for modeling their application with TASCA and then use the orchestrator to successfully deploy and manage this application, this workload, in a public cloud. And then in the morning, they brought in our management systems as a service and they were able to get the full instrumentation and the monitoring instrumentation for that workload. So very compelling and a very common pattern. Another example is with telcos. Many telcos around the world, what they're looking at doing is creating an open cloud platform, but then making available to developers many of the core network patterns, many of the core network functions. So again, we spend a lot of time on the pattern technology and with orchestration running on OpenStack to make these types of capabilities available to their communities, to their customers, to their developers. Another example is within the heat and hot projects with TASCA. We have a lot of customers that are really focused on how to create interoperability and how to better manage their workloads across clouds. So a lot of interest in the specification in Oasis referred to as TASCA. This allows them to basically model the topology, the nodes and relationships, as well as the plans. How do I deploy this? How do I activate it? How do I add or remove nodes? How do I put in an HA or backup recovery mode? So this allows them to manage their workload across its life cycle and also a level of interoperability across clouds. So working collaboratively in the heat project, we've been working on how to use subsets of TASCA. What makes sense of TASCA in hot? And so that's one of the projects that we're actively engaged in. And one of the early technologies we developed was basically a translator from TASCA into the hot templates. And so it's open source technology, now available so that we can start accelerating the ecosystem in use of the hot pattern or heat pattern engine through the TASCA specification and the use of TASCA. So Angel, would you like to go on to what's next? Sure, absolutely, thank you. You guys hungry? Cause I'm actually pretty hungry. You're hungry, yeah. Anyone bring a sandwich or a protein bar or something? Coffee? You got something in there, Brad. You don't leave home without a protein bar. You got Chick-fil-A in that pocket, don't you? Anyone from North Carolina got Chick-fil-As? All right, sorry. This is not the topic of our dialogue, I digress. This is being recorded too, so we gotta tone it down, guys. So look, a couple of minutes here. About five minutes, 10 minutes or so just to close things out. But I want to put in perspective a couple of things that Dave mentioned, grounded in reality. When he was talking about the examples of how a lot of our clients and how you all are using OpenStack, it's amazing cause as Dave was speaking, I was thinking about different layers of this kind of cloud architecture that's emerging. Whether it's open hardware, software-defined environments through networking compute storage, whether it's infrastructure as a service with OpenStack, whether it's dealing with open platform as a service or architecturally dealing with how humans interact, I think Horizon, for example, with the technology. At each one of these layers, you want to make sure you have freedom of choice and freedom of interoperability. Cause the reality is in the DevOps example, you've got many different tools. You ain't gonna, if you've got something you've been using in your environment, instead of scripts for 10 years, you're not gonna change that. How do you bring that into your world to deal with your OpenStack environment, right? If you're in the platform layer and you're building an application, you've been doing J2EE development, well okay, fine, that works for you, but what happens if you wanna start bringing in something like Go or Ruby or, how do you bring those worlds together, right? Or if you're building an application in a world that is ever increasingly mobile, how many of you are holding your mobile phones right now this second? Raise your hand. Yeah, you see, you're like attached. It's like the pacifier, right? Trust me, for me, I don't have it next to me and I feel really anxious, right? But think about it. You're developing an app for your mobile phone, right? You wanna be able to develop an app that could be cross-device, HTML5, IBM Co-Chairs, HTML5, right? We care about these things. And I'll tell you why in a second. And if it takes two weeks to update your app, it's not a simple push of an HTML file, right? This is not good. You're not competitive in the marketplace. So you want interoperability across these layers, but the future is not just interoperability across those. It is, across each horizontal layer, it's vertically, okay? Going from top to bottoms. How do you start to set policies? So when you look at a lot of the work that we're gonna be doing in OpenStack moving forward, it's not just doing the good things that we're doing, but understanding how does an OAuth that comes in, Brad, right? In Keystone, that comes in from authentication. How does that impact not just OpenStack, but the hardware in our power systems that support it, right? How do you have those policies propagated? If you have an application that requires a certain amount of bandwidth, right? And you wanna secure that at the application layer. How do you specify that as a policy that goes into this definition that Dave talked about called TOSCA, right? Which then can go through Neutron into a software-defined environment so that the network could be stood up and support that. You see what I'm saying? Those are the use cases that we as an industry are now evolving to, and that's exciting, right? It's exciting because it's not just interoperability across here, it's interoperability from top to bottom. So one of the key pieces that we're really super excited about and proud about, if you haven't heard about it, please check it out and get involved is Cloud Foundry. The way I like to think about this is cookies and a cookie jar, okay? I asked you the question about mobile. Has anybody eaten a cookie like around eight or nine after dinner although they shouldn't have? You're lying, raise your hand. If not, you're just intense because I am constantly dipping, right? So Cloud Foundry is like a cookie jar, okay? Think of that as the fabric that holds cookies. Cookies are runtime, services, application code, and you have all kinds of different cookies in the cookie jar and you want to be able to bring cookies from other people's cookie jars into your cookie jar. So if you have an open cookie jar, then you can build applications that span on-premise, off-premise, and in between and allow an ecosystem of cookies to participate in that jar. And if that cookie jar, by the way, is able to communicate policy into something like, say, OpenStack, right? Then all of a sudden now you have an elastic environment, right, that spans compute, storage, and network that support your applications. Isn't that beautiful? That's beautiful. So that's kind of what we're trying to do. So if you look at the Platinum members, the folks that are helping stand up this organization, it's not up yet. This is kind of like what we do with OpenStack. We announce we're going to go do it, right? And there's a whole bunch of gold members that have just signed up just like in OpenStack and this kind of this momentum is growing. We have a conference coming up in June in San Francisco and then we've got the June 9th. And then hopefully around the September timeframe we'll kind of be up and running. But a lot of the folks here are the same folks that kind of helped with this OpenStack phenomenon. So if you're not involved and would like to, would love to have you because there's gonna be a lot of work that we're gonna try to do to make sure that this stuff works well with OpenStack. And then also the use cases that I just described, these policies, et cetera, needs to flow from the application down to these foundational services can actually be honored and dealt with in the OpenStack world. So as we look ahead, and that was really fast but hopefully you guys got those examples, right? As we look ahead to Juno, and by the way, Juno who rocks OpenStack? We have T-shirts, right? It says IBM, Juno who rocks OpenStack. Oh, there you go. So please take a T-shirt and way out. If we don't have them here, come to our booth. I'm sure we've got a ton of them. There's certain areas we're gonna focus on. So first of all, heat and hot, very important, right? Defining, you know, from an atomic level, workloads and being able to orchestrate workloads. But what's also very important about this is that this is the place where you start to set some of these policies as well, right? These policies that can propagate from the user to the platform developer down to the infrastructure to the hardware. Solometer, very important, keeping and logging and all that information so you can do this. And I think, you know, in my head, there's a strong synergy between horizon and solometer. Look, you need to have an open user interface to deal with an instrument and manage OpenStack. Because by the way, the only admin console, the only UI's ain't gonna be OpenStack. It's gonna be a whole heterogeneous set of stuff that's out there. So how do you create an open kind of world around that? I thought someone had a question, guys, in the back. They're scheming with ways to turn off my presentation. Again, I've had it too easy. Obviously, we'll continue with internationalization and also RefStack. Todd, who's on the board and with us from IBM over here, has done quite a bit of work in Andrew's team out in California building test suites. This is when you know a technology, right, has kind of entered its own. Where folks are willing to stand up and say, all right, bring it. Bring the test suites. Let's do some interoperability, right? Then you'll get that HTTP effect. You know what I mean by that? When you type in HTTP in a web browser, you're not worried about you whether or not you get the answer back. Because all application servers use the Apache HTTP code in it today, right? And they're not worried about that. They run the interoperability test. That's the effect you're gonna start to get here. So, couple sessions to guide you. And you're hurrying off to one, I'm sure. Todd is gonna talk quite a bit about what we specifically are doing in OpenStack and some of the different areas that we're in and some of the stuff that's happening at the board level as well. We have a great discussion around examples of what we're doing with clients. That is always very important to understand the enterprise characteristics that OpenStack serves well and some of the things that we're still working on. And also some of the stuff that we have going on in our software platform, which is our very robust and kind of public cloud. There's also a whole series of technical sessions that we're leading. They are packed to the gills and hopefully you all can find time to go through some of these. They are focused on the areas that I just spoke about. Heat, hot, salameter, keystone, et cetera. So those are a lot of the areas that you'll see. So let me just leave you with three instruments. Three thoughts here and it's about playing. The first thing, I always say this at every OpenStack summit, every conference back since 2011 or so. We love working with the community. Everything that we do, all of our contributions, we do with others, with you all. So if there's an area that we're working on that you're interested in, give us a call, right? And let's work together in the community. If there's an area that we're not in and that you think we should be, let us know. We'd love to hear the requirements in the use case. Don't be afraid if you're newer, right? To just pick up the code and use it. Get a distribution, whatever, right? Just use it, play with it, okay? That is the best way of getting started because you're not alone, okay? The ecosystem is very healthy. Folks are always willing to help, okay? And there's been many, many use cases of the stuff implemented as you've seen today. And so getting started and knowing where to start is not that hard. So with that, thank you so much for attending. I really, really appreciate it and I'll see you at the sessions in the week. Take care.