 All right. I want to thank you guys for coming. My name is Jerry Rivera, so I'm a senior product marketing manager for Red Hat. And I'm kind of the marketing leader around all of our efforts around Red Hat OpenStack. What I'd like to do in my talk today is basically answer two questions for you. And that's the first one is, why is Red Hat involved with OpenStack? And then the second one is, how does OpenStack fit into Red Hat's cloud strategy? So first of all, why is Red Hat involved with OpenStack? To us, we thought it was a natural fit. We kind of think of ourselves as a leader in open source technologies, as well as cloud technologies. So when we look at OpenStack, we see that it's a perfect complementary fit to the stuff that we want to be able to do. Now, one of the things that we're always doing is we're taking a look at all the open source projects that are out there, and we evaluate them against five criteria to figure out if we want to start getting involved with that community and start making a commitment around getting our engineers to join that community and start making contributions to it. The first thing that we take a look at is, does that technology have the ability to deliver significant value to our enterprise customers? The second thing we look at is, is it a truly open source project in the way that it's governed, in the way that it accepts contributions, in the way that the community functions? The third thing that we look at is, is it an independent community that's not controlled by one single vendor? And then the fourth one is we look at, how is that technology licensed? How are the contributions licensed? Is it a license that gives people the freedom to use that intellectual property? And then finally, and the most important thing that we look at, is the community. And what we're looking for is a very vibrant and engaged community. Now, when we looked at OpenStack, started looking at it about a year and a half to two years ago, we started seeing that all the trends of it were very favorable, and we're getting to where we wanted to start putting engineers on it and start contributing to it and start embracing that project. And so one of the key things that we saw about it that made it very attractive for us was the community. And I mean, you guys all here are a testament to that and that there's 1,400 people here, and when we started looking at who's contributing and how many people are contributing to each one of the versions of OpenStack that's coming out, we found that that's very impressive, and that that made OpenStack a very special project and something that we wanted to take a close look at. Now, because we thought that OpenStack was a very special project and we wanted to get behind it, what I want to tell you is what we've been doing to get involved with OpenStack. So we had four goals for what we wanted to achieve with OpenStack and in our involvement with the OpenStack community. The first thing that we wanted to do is become influencers and leaders in the upstream OpenStack community. So what we did was, a little bit over a year ago, we quietly started getting some of our top engineers and asking them to start taking a look at the OpenStack community, join it, get in there, do stuff and start making contributions and give us feedback as to what's going on and to see if it's something that's appropriate for us to start making a much bigger investment in. And that's what we did. So the feedback that we got from our engineers was that this project was special and had a lot of community involvement, very vibrant, and it was something that we wanted to be involved in. So we started committing more and more resources and we've actually grown our OpenStack engineering team to where it's on track to being one of the largest engineering teams that we have inside our company. And if you look at what we've done over the past year, you know, we're proud to kind of say that if you look at the contributions that our engineers have done, is that we were the number three contributor to Essex and the number two contributor to Folsom. If you looked at the number of the people that we have on the team, it's actually pretty small but growing, but the people that we're putting on it, like I said, are our best and brightest. Now the second thing that we wanted to do was we were thinking about what are all the things that we've seen in other communities that we've embraced, such as like Linux, Jboss, that have made those open source projects successful. And one of the keys is around the government structure. So one of the things that we wanted to do was to work with Rackspace and to work with the corporate community that surrounds OpenStack to learn the best practices that we've seen in other communities and take that type of governance structure and wrap it around OpenStack. Now all that work kind of culminated back in April when there was the announcement that Rackspace was transferring control of the OpenStack project to the OpenStack Foundation. Now when that happened, we wanted to really make that foundation be successful. So that's why we signed up to be a platinum level member which and make the financial commitment that that entails as well as the commitment and the number of people that we were going to put on to OpenStack full time. Now our third goal was that we want to help build the ecosystem that's around OpenStack. So we have a lot of experience in doing this because that's one of the keys that we feel around the success that we've had around Red Hat Enterprise Linux and around our J Boss products. So one of the things that we've been doing is evangelizing to all of our ecosystem product partners around that they should be supporting OpenStack, that the future that they're going to see for their products is around running on infrastructures that are powered by OpenStack. Our fourth goal was that we obviously want to create an OpenStack product for demanding enterprise customers. So if you look at all the engineering efforts and the development efforts that we're doing, it's all around focusing in hardening OpenStack and putting in features that enterprise customers are going to demand. Now all of that work is being led to where we're going to have a release of our product early next year. So you'll see Red Hat OpenStack come out based on Folsom early next year. Now that product is actually available. We have a preview available. So if you'd like to download it, take a look at it, all you got to do is come by our booth and sign up for free access to it. So now I kind of told you why we're involved with OpenStack and why we think it's a special project and why we've made a large commitment around it. Now I'd like to show you how that fits into our cloud strategy. So Red Hat's cloud strategy, we have a fancy name for it. We call it the Open Hybrid Cloud. And all that means is that we want to provide our customers with the technology to be able to create a cloud that allows them to leverage both on-premise resources and resources that they rent from a public cloud provider. Now what we did was we went and talked to all of our customers and said, hey, this cloud computing stuff's coming along. What do you want from it? And what we found that the problem that we're trying to solve is the age-old problem that everybody in the IT industry is trying to solve, which is how do you help your customer to do more with less? And so I just want to show you two statistics here. The first one on the left-hand side is a survey that Gartner and Forbes Magazine conducts every year where they go survey the board of directors of the top 1,000 companies around the world. And one of the questions that they ask them, they ask them a bunch of questions around their IT. And one of the key questions that they ask them is they try to find out what percentage of them do they say that their IT shop, that their IT, is strategic to the success of their company. And what they found in 2010 was that 31% of those board members felt said that they either ranked it as being high or extremely high IT being strategic to the success of their company. When they did that same survey in 2011, they found that it almost had doubled in that now 65% of board members of these 1,000 large companies around the world believe that IT is what's going to be strategic to drive the success of their business. So again, it's showing that now the demands that the company, that the top leadership of companies are making and demanding of their IT shop is getting to be very high. Now the second thing on the right hand side is a survey that's done by Ernst and Young every year. So they have their consultants go out and they do a survey of finding out exactly what IT shops are doing on a day-to-day basis. And what they found out is that IT shops are spending 75% of their time on basically break fixed low-value added tasks. While only 25% of the time are they able to devote resources to high-value added tasks that allow them to help improve the competitiveness of their company. So it's just showing that what the leadership of these companies are demanding is that they get more out of their IT shop while the IT shop is actually hand strung in their ability to be able to deliver that. So what we're trying to do is put together solutions that allow our customers to be able to get that promise of the cloud, which is that they're gonna have the ability to do more with less and to make their IT shop vastly more efficient. So that's the problem that we're trying to solve. Now as I told you, our strategy for solving that is called open hybrid cloud. So what we did was is we've gone around and talked to all of our major customers and asked them what's the capabilities that you absolutely have to have to deploy this cloud that's gonna give you the functionality, the performance, and the savings that you expect to get. Now when we took all that feedback, we found that it basically boiled down into eight capabilities that they wanted. The first one at the highest level is they basically wanted some orchestration tools that allowed them to create a hybrid cloud where they could both manage, deploy and manage resources on-premise as well as in private cloud or public clouds. The second thing that they wanted was a governed self-service portal. So what they're looking to do is to allow their users to be able to independently and when they needed to be able to deploy IT resources on demand. But they also wanted to have a governance structure where IT sets the policies about how those resources can be consumed by these users. The third and fourth things that they wanted were around system and application management tools. While the fifth and sixth things had to do with their virtualization infrastructure and that they want virtualization management tools and a hypervisor. And then the seventh is that for all those virtual machines that they're gonna be managing inside their cloud, they wanna have a high-performance and secure operating system that they can use with the guests. And then finally one of the things that they wanna try to do is take out costs in their storage infrastructure and they wanna move to where it's a software-based type of storage. Now the way that we're meeting the demand of those capabilities with our customers and one of the key partitions of our cloud strategy is instead of doing it in one or two monolithic products, we're gonna do it with five. So here's the current five products that we offer. We're trying to take a portfolio approach and I'll show you on the next slide exactly why we're doing that. So the five products that we have in our cloud portfolio are Red Hat CloudForms, the soon-to-be-release Red Hat OpenStack, Red Hat Enterprise Virtualization, Red Hat Enterprise Linux, and Red Hat Storage. Now one of the key things that we've built our company on is around open-source technologies. And the reason that we believe in open-source technologies and the reason that we like it is it gives something to customers that they want, which is choice. It allows them to stay in control of their IT infrastructure. It gives them the ability to figure out what is the best way that they can deploy their infrastructure to meet the demands that their company has. So what we try to do by offering choice in our Red Hat Cloud strategy is that, again, instead of having one or two monolithic products that could either lock the customer in or strand them on some dead-end technology, what we do is offer this portfolio solution. So it starts at the bottom and that we have a product for the software-based storage. It's Red Hat Storage. Then as you go up, for the guest operating system, we have Red Hat Enterprise Linux. And then for the virtualization tools and the hypervisor, we have Red Hat Enterprise Virtualization. And then finally for all those higher-level functions around the orchestration tools, the governance self-service portal, the systems and application management tools, we have a product called Red Hat Cloud Forms. Now remember I told you that one of the things that we're trying to do is give our customers choice to allow them to have control of how they build their IT infrastructure. So, and one of the reasons why we really liked OpenStack and why we're getting behind it and going to offer an OpenStack product is that that allows us to give our customers another choice in how they build out their cloud infrastructure. Because what it allows them to do is there could be certain portions of this stack that they don't wanna use and that they can replace with the Red Hat OpenStack product. So like they can take out their virtualization management tools that we offer with Red Hat Enterprise Virtualization and instead use Red Hat OpenStack Nova. They can take out the software-based storage that we had which is our Red Hat Storage product which is what we got in the acquisition that we made of Gluster and instead replace it with Red Hat OpenStack Swift. Now again when we say that we offer choice we have to make sure that our portfolio of products all work together, that they work in combination, that they play well together. So we're looking to build our products so that they're modular so that you can plug and play. And not only do we do it with our products but again to give the greatest choice to our customers we make sure that they work if they decide to rip one of our products out and instead use a product from our competition. So if the customer's already invested in and wants to use virtualization management tools that they got from VMware they'll be able to plug that in and use it with all the rest of our products. If they decide that they want to rip out the guest operating system and use Microsoft Windows they have the ability to do that. Because again one of the things that we've done is partnered both with Microsoft and with VMware to make sure that all of our cloud products support them and work in a heterogeneous environment where a customer's running both our products and some of our competitors' products to build their cloud infrastructure. Now that's what we're doing on the IT infrastructure side. So the other side that we're trying to do and help enterprises with is a cloud that they build for development. So this is what we do around enterprise development. We have another product that we call OpenShift. And OpenShift is trying to provide it's an OpenShift platform as a service and what it's trying to do is to provide an enterprise development platform that enterprise customers can deploy as a cloud, as a platform as a service to their customers. And so our current OpenShift product is a hosted solution. So it's where you come to it, you go to our website and the resources that you run are being hosted and are not on premise to or inside your data center. So we've received a lot of feedback from our customers. They really like that product but they don't like that it's hosted. What they want us to do is to take that same technology and allow them to deploy it inside their data center. And in the next couple of months you're gonna see us release that product that does give our customers the ability to get all these advantages of our OpenShift platform as a service inside of their data center. And just one quick note. So if you see this graphic here we call this our Death Star graphic and the guy who did that who's my counterpart on the OpenShift side is super proud of this. It took him a long time and he doesn't have any graphics ability but he came up with this thing and he's kind of mandated that all of us that whenever we go and give a presentation he's incentivized us through a cash basis if we can get this graphic into our presentation. So I wanna thank all of you for seeing that cause this is an extra $20 for me. Okay, so finally here's just a summary. So all I wanted to do was just show you two things. I wanted to explain to you why we think that OpenStack is a special project and why we've decided to make this huge investment into it and get around it. And it's because we believe in its future. We believe that it really does have the possibility of being able to give our enterprise customers technology that can really give them significant savings. So we're proud to be a member of the community and we're also proud to be a platinum level member of the OpenStack Foundation. The second thing that I wanna leave you is just that what is our cloud strategy? And it's what we call the open hybrid cloud. And all that means is that we wanna give customers the ability to have a choice of the technologies that they use and put together to develop their cloud infrastructure. So instead of just relying on us to give them one monolithic or two monolithic products that could potentially lock them in or potentially strand them on some dead end technology, instead we wanna give them a choice of different technologies. And the way that OpenStack fits into this is we feel that it's complementary in that it gives our customers a choice of another technology that they can use when they deploy their cloud infrastructure. So that's basically all that I have for you. So I'll take any questions. Go ahead. Great question. And if you don't mind, Perry, could I have you answer that? So the question is what's our equivalent to Juju and Puppet? Any other questions? Right there, yeah. Not so much a question, but just a correction. Crowbar does support deploying onto Red Hat. It just doesn't support deploying OpenStack onto Red Hat right now, so. All right, thank you for that clarification. I really appreciate the settlement around openness and having a solution that's right for the particular enterprises. What are the requirements to have the Red Hat rel as the guest operating system on other OpenStack based solutions, whether by one of the other Linux vendors or whatnot? Sure, so the thing is that we have is we have ones that are certified. So obviously if you use it on ours, you get support and everything and it's certified. But if you wanna choose some other OpenStack distribution, you can do that and you can run rel on it. We don't do anything to prevent you from doing it. The only thing that we may ask, like if you call us with a problem, we're gonna do everything that we can help you. But it could be that the problem becomes so esoteric that one of the things that we ask you to do is if you could run it and try to reproduce it on the Red Hat solution so that we can isolate where the problem is. But again, we don't do anything to prevent you from using it on some other distribution. It's just at the level of how much support we can provide you may be somewhat affected, okay? One of the things that Ubuntu has done is provide Ubuntu Enterprise Cloud images that you can run on your OpenStack Cloud. They're very reliable and useful. I was wondering if Red Hat's gonna do something similar. Yeah, do you wanna? So we just deliver rel as a DVD ISO as well as through our repositories on our content delivery network and RHN. But we are talking internally about providing images. So right now we already do provide images for places like Amazon AWS, right? So there's rally images up there. But obviously those are specific to AWS and we'll be looking in the future to hopefully provide images that you can use in OpenStack environments. But those conversations are still ongoing with our product teams. Next question, over here. Can you just talk about the differentiators in your distribution compared to some of the others? In terms of our OpenStack distribution? Well, right now we don't have the product completely done yet, right? We're still working to have that ready by the beginning of next year. Perry, do you wanna say something around? So we're really looking to just mirror what the upstream is doing. So I don't know the details about the other distributions but I would say that what we're doing is providing pretty vanilla, fulsome, right? So you're gonna get all the core packages that are available and then as other packages or components of OpenStack become incubated then we'll pull those into the distribution but our initial idea, and I think Jerry touched on this a little bit earlier, is that we were focusing on the core infrastructure and making sure it's stable and ready for enterprise deployment. And we didn't wanna build a lot of other management infrastructure on top of it until we were sure that the base was stable. So we are gonna be looking in the future to provide some additional management tooling around it but for right now, especially for the fulsome release, we're just focused on the underlying components. So related to the last question, the, sorry, related to the last question, are you gonna be following the, you know, grizzly and the next releases or are you gonna be sticking with fulsome and backporting pieces? So there will be times probably where we'll need to selectively backport things because there's gonna be a little bit of a lag between the upstream release of, you know, for fulsome and grizzly versus when we're gonna have the productization out, especially in the case of fulsome, you know, it came out a couple of weeks ago and we're not gonna have a fully supported product until, you know, early next year. So there might be some selected things we'll have to backport from grizzly, certainly bug fixes and maybe some minor feature enhancements but one of the things we don't wanna do is cause API incompatibilities or database schema changes that might make it difficult for people to do upgrades. And in terms of our cadence for the product, right now we are going to base it on the same release cycle as upstream, probably shadowing it by a little bit. And the current plan is to provide support for the current version and the next version. So fulsome comes out, we'll support, when we get that productized, we'll support that. When grizzly comes out and we've released that as a product, we'll still support fulsome via the stable branches from upstream and provide updates, you know, security fixes, bug fixes and so forth. When the H release comes out, then we'll deprecate support for fulsome and, you know, hopefully by them people will have moved on to grizzly. So currently two releases simultaneously but that's gonna evolve over time because just like we saw with Red Hat Enterprise Linux, right, we have a support model right now where we support it for, you know, initially it was like five years then seven years, now it's even longer. And as OpenStack matures, we'll be able to provide a longer support life cycle and that's where we wanna get OpenStack too but we also recognize that the cadence right now is very quick and the features being added in are very crucial for people. So it'll be a shorter life cycle in the beginning and then eventually ramping up to longer life cycle. We had a question right here. Oh, good. I was wondering if and how DeltaCloud fits into your cloud strategy? Yeah. So DeltaCloud, actually we have David here. Yeah, I'll answer the question and then David can chime in if he's got anything he wants to override me on. But DeltaCloud is part of our cloud form solution. So we talked a little bit about cloud forms up there and how that sits on top of the open hybrid cloud, allows you to migrate your workloads between OpenStack and VMware and EC2 and so forth. So DeltaCloud provides that abstraction layer that allows you to communicate to multiple clouds over one single API. So it's a very important part of the overall cloud solution. It's not something that's specific to OpenStack though, it's something that sits on top of it. Is the intention for your OpenStack and OpenShift products to work together? Absolutely. Yeah, we have people looking at that today. OpenShift really only requires rel underneath it. It could be even run on bare metal rel. So we absolutely want it to be able to run on top of rel, guests that are running in an OpenStack cloud as well. Based on what you just said, I'm assuming multi-tenancy in OpenShift and multi-tenancy in OpenStack are now going to work together. So those two things are disjoint right now and there's probably gonna need to be some integration effort to map those together. But right now the users in OpenShift are completely separate from the users in OpenStack and Keystone. I was just wondering if there's any plans for integration of Gluster into this? Yeah, a couple different avenues there. The most simple way to use Gluster is if you just run a Gluster file system, so you have a bunch of Gluster storage bricks and from your Nova compute nodes you can have a Gluster file system and use that for storing your images as you retrieve them from Glance. Or you could use them to be the backend storage for Nova volumes or sender. But those are pretty light integration. Basically it's just a configuration thing. But there's some other areas we're looking at. The upstream QMU community is taking a look at providing Gluster native interface. So instead of going through Gluster file system which has slower performance, it could access Gluster directly and so get better performance and also I think the security model is a little better too. Can you just talk about how you would support quantum in the distribution and also just wondering if you've heard any requests from customers around virtual networking capabilities? Lots of requests for virtual networking capabilities. It's a very, all the customers we're talking to are very interested in quantum. So quantum will be provided as part of the Folsom release. And in fact, we have coming up in RHEL 6.4 which is coming out around the same time that we're gonna try to be productizing Folsom open V-switch support. So that'll be back ported into the RHEL 6.4 kernel and then we'll provide the user space for that as part of the Red Hat OpenStack product. Any other questions? All right, then I would like to thank you for your time.