 Okay. Well, welcome. Thanks for coming to our session here. I'm Daniel Crook. This is my colleague, Manuel Salveira. Today we're going to talk. You heard, if you were at the earlier session, about some of the contributions that we've been putting into OpenStack over the years, particularly the technical focus. But there's a lot of other activities that IBM's part of in the OpenStack community. So we wanted to highlight a few of those and point out how you yourself might get involved in the community based on some of the lessons we've learned. So code, obviously, you can't have an open source project without code. So it's clearly the most obvious and clear indicator of both the vitality but also the contributions that are going into a community. And we've certainly done that. So we'll do a quick overview of those features that we've released over the past OpenStack releases and what's gone into Juno. And then we're going to work into the activities that surround that that help build out the OpenStack community. And as I mentioned, let you learn some of our lessons for getting involved in the community. And finally, because IBM is such a large part of the community, one of the eight Platinum sponsors, we want to hear what your opinion is for how OpenStack might better drive the next release. So looking forward to the next summit. If there's some features in particular that you think that we're well suited for, obviously we can come up with requirements and see what we want. But of course we want our customers to help us drive those requirements as well. Okay. And we do have quite the direct line into the OpenStack community. Manuel and I both work for OpenCloud and OpenStandards, open source and performance. So if you talk to us, find us at the session, we'll be here all week. Just informally or informally if you want to have a meeting with us or just chat with us, just find us. And we're of course on Twitter as well. So if you want to follow us and after the conference, find us, you can do that as well. Okay. So why are we at an OpenStack conference? Why are we involved in OpenStack to begin with? IBM has been rapidly adopting the cloud and we quickly realized in our early cloud efforts that OpenSource is really the way to go when it comes to cloud. There's just so many vibrant projects out there and there are so many communities that we can build on, which helps us focus on not so much the plumbing infrastructure of what we do, but focus on our customers. So we want to be able to build a foundation on which to help our customers innovate. So at the software-defined environment or data center, the infrastructure is a service level. We are quite involved, of course, in the OpenStack community, but also if you've seen some of the other organizations that have been part of this, also Open Daylight, OpenFlow and some of the other standards that go into defining the data center, OSLC and ISO for managing the life cycle of those cloud resources. You may have also heard about Cloud Foundry. There's been a couple sessions. That's another community that we're in. And around that, there's a lot of services and run times that run on top of Cloud Foundry or Bluemix, which is our distribution of it. So jQuery, Chef, MongoDB, Node, and of course Java, we have lines into all of these communities and we bring them into every part of our cloud infrastructure. And finally, in the software as a service here, what we call the API economy, we're deeply involved in defining the standards that are there for the mobile applications, for the web applications. So for example, the HTML5 standard, I believe just last week, that went gold. We've been a part of that for finally. We've been part of that for 20 years. That's something, of course, we have more deep roots into and a lot of folks on our team, too. So we're in these communities, not open stacking, but if you have any sort of interest in helping IBM guide our participation there, come talk to us. So all bringing it together, this is what we call our open cloud architecture. We're building the entire set of IBM offerings. You'll hear some more in the later sessions on top of open source. Everything we do. Okay, so I'm going to hand it over to my colleague Manuel. He's going to give us a summary of what we've been doing, particularly over the history of OpenStack and into Juno. Yeah, so we've been working with OpenStack for a couple years now, and what IBM has done is actually really interesting, right? We've moved from S6 where we had a single core contributor and a couple technical contributors, and we've been going to moving on, and as you can see, the number of IBMers working on this has been growing steadily every release. So we've gone from S6 where the big contributions were the storage enhancements, which we've always been a part of the Cinder work, the translation, and again from 54, then to Folsom, we almost doubled it, and we continued working with the Cinder work. We continued growing, so the core contributors went from one to four, and the number of commits started growing steadily, and at Grizzly you start seeing that we start picking up momentum within IBM, so we go up to 270 total IBMers working on this, and this is really if you look at the chart of contributors, these are technical contributors not really, this is in counting management and executives, this is actually like people working on the code, and the big contributions here were the Nova design features and the API stability, and again commit starts, jumps way up from 181 to almost a thousand commits, but then by Havana the IBMers again are jumping 100 more people are doing it, the core contributors goes to 13, the technical contributors go to 85, and we start seeing this momentum within the company, so now we have dedicated teams within actually organization that are doing that, Vince is here, Vince actually manages the open stack development team within IBM, and then when we got to Ice House we're now the technical contributors is 107, and the IBMers were reaching a steady state with the number of IBM contributors, but the number of commits actually continues growing, and now we're focusing on one of the big things for me is when we went to talk to customers, the big issues, the customers that IBM talks to are like the big existing enterprises and the issues that we hear, the questions that we hear aren't about the new cool features, the new cool things that the community is excited about, what they want is these boring things that they just need to work, so the big focus really was in authentication and security, so integration to LDAP, if you guys remember from Grisly and Folsom, integration with LDAP was nominal, and it technically was integration, but it really wasn't, basically it used your LDAP as a data store, and they treated it like a relational database, so nominally it was integration, but it really wasn't, well in Ice House all that stuff was brought in, so it was a real, you could actually use federated, you had user accounts, you had real integration, so IBM has been moving towards things that are important, the other big things that we're doing is the quality assurance, we're a company that really focuses on stuff like that, where it matters, where our customers expect reliability and they expect certain stability standards from us, so if we're working on something, we usually go in on two sides, on one side is exciting cool features that are coming out, leverage our technologies, leverage our other products that we have, but also on the other side, we're trying to make things more stable and make them better in general for the community. Speaking of Juno, in Juno, things again, we continued with this enterprise security with our contributions to Keystone, so this is sort of just a high level talk chart about what we did at Juno, but we continue to do these core key things that are very important to the open stack, but aren't really, sometimes people don't think about, they just assume that somebody will fix them, so we are doing that. With Block Storage, we continue to be the leaders in the Cinder development. With the user experience, if you remember with Horizon, we've been adding a lot of the JavaScript improvements, the user interface improvements, and again internationalization and simple usability, this is the stuff that we worry about and this is stuff that we get done. With the update management, the Nova APIs, that was actually a problem, as you were moving between releases and then the API was changing. So what we did is we actually spent a lot of time working on that. And then with the interoperability, I mean, with the rest stack, we don't often think about when a company or somebody releases something that's called open stack, what does that mean? There's so many variables, there's so many variations, how do we actually, how do we actually know that that's compatible? How do we know that your environment will work with my environment or my code that's written for open stack here? How do we prove? And so with the work that we've been doing with interop is stuff that's actually used, that will create an application that will actually verify that your stack is compatible. And so again, the total IBMers, like I said, we're getting, we were reaching a steady state. In Icehouse we had about 380, now we have 400 contributors. The number of commits went up again from 1500 to 1600 and the core contributors is up to 15 now. And the total technical contributors 109. Okay. Just go back a second. And the key point too is we heard all of these requirements from our customers. Some of it obviously was internally generated. So anything that you see missing in open stack, anything that prevents any sort of enterprise readiness for you, please let us know. Yeah, absolutely. And this can be anything. I mean earlier Sean and Phil gave a presentation about the interoperability between X86 and other platforms with open stack. And these are concerns that are valid and very real to a lot of customers. And the problem is that there's so many concerns, so many things that are out there we just want to focus on stuff that can help everyone. And so that's one of the areas where we're also working on. So IBM is really, I mean, I joined IBM 14 years ago and I've been working 12 years with Linux and Open Cloud. And in this time when I started IBM was when IBM made the $1 billion commitment to Linux. And at that point that was a big deal. And there wasn't a lot of companies, there was either a closed source or open source was beginning to get a lot of visibility and start grabbing some headlines. Well when IBM committed $1 billion to Linux, IBM basically made it clear that our commitment to this open technology, this open platform, the open base was really the future. And it was big news back then in around 2000, 2001. But now it's expected for big companies to contribute back and give back to the community. And so you see Apache, what was it, in 98? Yeah, that was one of the very first large enterprise open source collaborations. So this is really where we cut our teeth and set a lot of best practices for other open source communities as well. Around 2001 we open sourced the Eclipse framework and the other thing we started doing with Eclipse is that we formed a consortium and we created a foundation to manage to guide the open source work. And so this is something that you see that IBM starts doing, starts learning. And from that we've actually moved to this new open cloud environment. And in this open cloud world, we're taking those lessons, the lessons from Linux, the lessons from Apache, the lessons from Eclipse and we're moving forward because we think, well, we know that that's the right way to go forward, right? So recently we announced last year that we started working with Cloud Foundry. We started forming an advisory board and the foundation we recently announced that we're going to start creating. Next week or so that should be finalized. And again, specifically in our team we have an organization, a peer manager of Vince's that actually owns Cloud Foundry development within IBM. So we're serious about this. Again, Node.js, you can... Yeah, and in both these new emerging communities, we're now in a different phase starting with advisory boards for both communities. We've long supported Node.js within IBM on top of Bluemix which is our platform as a service built on Cloud Foundry. And we're also involved in the Docker community also working on an advisory board, bringing our lessons to these communities that we honed at Apache, Linux and Eclipse and more recently in Cloud Foundry. And we've got several contributors to Docker, Phil being our representative here. Yeah. So what are we doing with the OpenStack Foundation? And so really our commitment to OpenStack really goes beyond the development of the code. We've done platinum sponsorships. Man, it's hard to read from that side. Yeah, sorry about the glare. Do you want to talk about this one? Yeah, so this is really where we're talking about the OpenStack Foundation, right? So this model is repeating. And for OpenStack, we've been involved as the platinum sponsorship. We're one of the only eight platinum sponsors. There are also almost 20 gold sponsors and 80 corporate sponsors which is the gradation that if your company wants to be involved in OpenStack, you can start there and move upwards. Another key point that I think we didn't mention in the Linux community is that there is the advisory boards, the foundations, that repeating this model of making sure that the open source project, even if its provenance is one small company, one small developer, once it's been committed to open source you know that it will be guided towards a collaborative model that the one driving developer that may have produced the community will not just shut down development. So if you've made investments inside of that open source technology, you know that there's a long term view on it. So that's key to a lot of what our organization support is, is giving the enterprise guarantee of the lifetime of the project. And we also mentioned that there is a deep commitment as being part of a platinum sponsor that you must commit several resources in terms of developers and people working full time. And we've seen that now growing in the last few releases, being the number two contributor. If you go to that Stack Analytics page, if you want to go back a few slides, you can always kind of see these. It's the next one. Is it? Yeah, Stack Analytics always shows you. This will give you an open source, a view of open stack in terms of the company's contributing and where they're contributing. Why does Docker need a foundation? Why can't I understand in the key of open stack, I sort of understand because of the crowd found it is like how many of these foundations are going to come down to us? That's a good question. You're saying I'm learning from a factory name a lot. You're actually going off and reinventing it. And it's stupid. I'm saying it. Yeah, it's a good question. But now they're doing this to Docker. Well, yeah, and we should be talking probably Chris Ferris who's not with us. But the Apache Foundation, it's very good at what it does. But there are also different goals for each project that can be solved more by foundations. There's plenty of good projects there. It just seems nonsensical to keep adding new projects. I sort of get it with open stack and we don't get it with Docker. What I would add to that, the difference between, so there's so many technologies and IBM has spent a lot of time valuing these technologies and trying to think where is there a center for gravity, where is there a good ecosystem. We've seen that with Docker. The step to the foundation part is because with the foundation comes open governance, what do you think we have in Apache software foundation stands for? I mean, it's called the government you mean. But Docker does not have that same cover. You don't understand what I'm saying. Oh, yeah. I don't even follow up with foundation. I get that. I'm just saying why create another foundation. Part of that is the Docker ecosystem. Not for their own foundation. I guess the point is that IBM can't dictate to Docker what they decide to do. Certainly, you make a very valid point that the Apache community has served a vital role but didn't say it didn't. It serves a role. IBM is participating with Docker and trying to influence it to be open that we can't in just kind of influence Docker say you've got to go to Apache or else because that's not the role we... We have those discussions. We talk about it. We try to steer the conversation that way to kind of exit. That's an interesting point. But to Jeff's point, we can't force them to go that way. So if they're going to go it alone, then we say, well, if you're going to go it alone, then we think you're the best practices around it. So they're not going it alone, that's the old point. So if you want to go it alone, then you've got to create a foundation so you're not going it alone. It's a good argument. That's a good question. Well, I'm sure if we can probably follow up and find the detailed reasons for it. But it's probably not on one size fits all model for many of these communities. And we could take it back and see. Well, Linux is in part of the Apache foundation, right? Yeah, we'll take it offline. So and continuing with OpenStack, as the conferences have been moving on, as we've had more conferences, you can see that we've grown our presence at these conferences. And so the point isn't to say that we've gone, you know, and at Boston we had the Essex summit. We went from one attendee to today where we have over 100 attendees. But the point is that we it's really we feel it's really important for us to give back and the way we give back. And this is at a as a technologist talking on technical level, the way that we give back as you know through social media, through blog post stuff like that videos, we also give back through through the through the summits through the summits and through through meetups and we'll talk about that a little bit. But what we started doing is as you start as you see we start moving from Essex through Folsom through Grizzly. At Grizzly, we start being more than attendees. We start contributing. We start having providing sessions, contributing to the design summit at Havana. We go to seven sessions, Ice House 10 sessions. This one we 12 sessions. I've been going to these since since Hong Kong. We've had I've been lucky that in all of these I've had sessions accepted. Yesterday we did we did a docker one and basically what we're doing is we want to give back but the beauty of it is that when you when you give these sessions you get a chance to talk to so many people to get so many so many opportunities to hear what people are doing and more than that you're actually able to give them back some feedback. We can we share experiences this morning we spoke with Red Hat about some of the docker work that we're doing and it's an opportunity for us to work together or at least worst case we can at least get validation that we're both on a track that other people find valid. We get some validation. Want to see? Okay. Alright so and going beyond those formal involvements in the community actually signing contributor licenses and sponsoring conferences. We've also been deeply involved in setting up meetups in local areas and so we've developed a set of best practices around this. Here's just a couple of examples of what we've been doing in collaboration with several of the other platinum sponsors in New York. There's an open stack meetup group as well as in Philadelphia, Boston. Some of these are the ones that I've been involved in co-organizing myself. I'm based in New York area so we've had speakers from IBM. We've encouraged partners like Dell and HP and EMC to be part of these communities and help us really get developer mind share around this open source technologies and get people to learn how to use them, how they might leverage them instead of reinventing the wheel coming up with a different project. Well let me add that so we see two situations where for example in Connecticut Dan's from Connecticut. In Connecticut there really was a vacuum of these meetups and technical groups. So what he did is he actually started, he found a place where like minded individuals could get together. He organized it, set up a meetup page really informally and got people to sponsor some drinks and stuff for the evening and we got technical presenters to do. I'm in Austin. In Austin that already exists. There's a lot of all these open stack doc or cloud meetups so what we did, Vince and I actually presented a couple times at the meetups. We go talk to people hear what people are saying. So the point is that if something exists let's leverage it. We can work with the organizations present. If we can get a little bit of funding by some pizza awesome. If not there's always a chance to give sessions that they're always looking for help with that. And if that doesn't exist there's really no reason why we can't stop nothing stopping us from building these organizations. And then if you look at China there really was nothing there before the team people on the team started working on that. And so the point is that this is something that we feel is really productive to us because it gives us like feedback like specifically with Vince and I we can actually talk to people see what they're talking about and this isn't like the big enterprise customers. These are the real users of technical people and we can validate errors validate the things we're seeing. Exactly and a lot of these communities are very industry specific. So in New York we have a lot of financial input that comes into open stack versus in the Bay Area there's different workloads that they're more interested in and throughout the world they've got different focuses on what they want to do with open stack or cloud foundry. And the other side effect of this is every time we've come to these cloud foundry conferences or open stack conferences we've taken the talks we've done there. We've brought them almost on a road show to basically if you can't come to a large conference for example Travel to Paris we're able to take the talks there and also hone for the next conference. So for example he mentioned Austin. The HA talk on Docker we did yesterday was presented there got some feedback pulled that in. So it all contributes to the vibrancy of the community and this is some nice cross pollination too. Eric Vindish if you were at his Docker talk yesterday he came to one of our open stack meetups to talk about some integration that research has been doing in integrating Docker into the open stack community and at least technologically. Well and actually one last thing that at these meetups is also an opportunity to grow the community beyond what is usually considered the community right? You had a ladies night meetup where it was a chance to get people that women that typically aren't coming to these meetups for whatever reason we were able to get technical content. It was a really success over 70 attendees. Right. Reaching out to communities versus expecting them to come to. Absolutely. Yes. So to help if you want to get involved in the IBM community there's some suggestions and some of the actual for open stack specific. You know if your companies if you have technical interest in contributing to open stack get your individual employees allow them to join the foundation. It's free. It's straightforward. There was mention that there was a couple of boot camps that happened before every conference. I don't I think what are those called? Do you know Vince? It's on Sunday. On Sunday you can come and help you get onboarded, help you be able to do your development, keep your development environment set up. It's a lot of education in there. If you're calling it like open stack university or something. Yeah so you get your developers involved start to understand the community and start to see where there might be some gaps where open stack may not fit your needs starting there. They're getting involved with the community. Contributing in the small stuff to start. Translation is obviously something that's very important in the open stack community. Reporting bugs, improving documentation. And basically you want your developers to become known in that community as someone who's willing to give to get. So if you want to get something out of the open stack community you want to make sure that what you're putting in is something that's going to help you build on top of it and it could help what you want to commit in the future. And as we said meetups are a great way to initially get your company started. If you have somebody that's ready that wants to talk, wants to present something at an open stack summit, but they're not quite sure of the content and they want to get some feedback. Send your employees there, have them at least attend, maybe get some expertise, build up their own skills. And if you're also interested and you have a location that's a very good space in a particular city in your market, if you become the person or the organization that hosts those meetups, you can build a lot of your own mind share and your own support around open stack. And as you move up this participation, get more deeper, you know if you've honed a few presentations, get your developers to submit abstracts. Make sure that the content that other people are submitting are things that you want to see. And to start your own company's formal relationship with open stack you'll want to commit to some corporate sponsorship, maybe get a booth at a future summit or conference. And finally this is now where IBM has become, we kind of worked our way through this, is become an actual corporate member in the open stack foundation. So they have different tiers to start with. If you're less than three years old it's a smaller bar to get involved as a sponsor. And as you work up to gold sponsorship and ideally after that join us as a platinum sponsor. Okay. So thanks again guys. So really the core of this is that we really feel that it's really important to give back, but when you give back there's lots of ways to do it. Don't just feel that you have to commit code, that you have to write, get in there and do fixes or add new features. At the technical contribution level you can help with the test, well IBM helps with the testing, but you can help with the documentation, you can file bugs, you can help at that level. But then there's also this, there's a couple other things you can do, you can help with the evangelism, help with the meetups, help with the submissions. This is all valuable contributions. This is something that we really need, that if people say quiet, if people keep this to themselves it really defeats the purpose of the community. So we're really excited about that. And again if you're in New York, if you're in Connecticut you'll see him, if you're in Austin you'll see me, if you're in the West Coast, in the Valley you'll see the rest of the team. Brussels exactly. So we're all over the place guys. And if you feel that there's some area that's underserved, let us know. I guarantee you IBM has a presence there. And there's a big, within IBM the open part of IBM is big. And technologies like OpenStack and Cloud Foundry and Docker and all these, the cloud technologies are everywhere within the company. So this is something that even if they're not working directly with that, they're using it. This is exciting stuff for us. And so if you feel that there's an underserved area let us know and we'll help set that up. We have, Joanna and our team is setting up remote, Joanna and people under team or Joan, but no, but under your team they're setting up remote meetups. So this is stuff that we want to do. And there's the next one. So there's one more technical session today. And then this is everything we did. And there's two more sessions coming up in this room after this one. And that's it. Whoever didn't get a t-shirt, we have some extra larges and double extra larges here. And that's it guys. So thank you very much. Just one last point on the meetup. So I've published a blog a few months back, just on some tips that we've had. So if you go to thoughtsoncloud.com, that's the IBM cloud blog. You can find some details on how you might at least make that first step if you want to start hosting and participating in an area.