 Okay, I guess we'll get started. Thanks for attending. My name is Bill Mason, and I'm Director of Partner Strategy for Virtualization and OpenStack at Red Hat. And I'm doing a joint presentation today on Dell and Red Hat cloud solutions we've been collaborating on, and I'm here with my good friend and colleague, Joseph George, who's responsible for cloud and big data solutions at Dell. This is the requisite movie, steal a movie slide for your OpenStack presentation. The reason I call it back to the future seriously though is Red Hat's been working with Dell for 15 years. Dell was the first OEM to pre-install Red Hat Linux on servers and workstations and kind of anticipated this enterprise Linux market where we now find ourselves with lots of Unix to Linux migration. And in 2002 and 2003, Dell was one of the first to pre-install the Red Hat Enterprise Linux 3 release. And now we're collaborating on OpenStack. And the reason the partnership works really well for us, Dell's been doing OpenStack. I said they kind of anticipated what was going to happen with Linux in the enterprise and helped Red Hat be very successful there. They've been involved with OpenStack since the very beginning, since 2010. Red Hat does a little bit more of a late entry into the market, although we're a leading contributor over the last couple of three releases. So their domain expertise, working with many, many, many enterprise customers around private cloud deployments. And our expertise in making enterprise-grade, productizing open-source technologies with a subscription services approach that makes customers really happy because it's an open non-vendor lock-in solution is really an ideal combination of our partnership. And our approach and philosophy for open-source is also the same. We make everything open-source as soon as we can. We have had some acquisitions of companies like Manage IQ, our cloud-forms product that takes a little bit of time to get through legal, but it's Red Hat's intention to publish all of its source code for all of its products in all cases. And that's not necessarily what you get with some of the other competing OpenStack distributions. They tend to add proprietary extensions. That's just not, if you heard Sam Greenblatt's from Dell's keynote two days ago, or yesterday, you would know that that's just not the approach that Red Hat and Dell are going to take. We're going to make sure everything's open and everybody gets access to everything in the same way we do with our enterprise Linux and our JBoss middleware product lines. So what we announced three weeks ago, two weeks ago at Red Hat Summit, it's fun having back-to-back summits, kind of wears you out, words that were now open for business and that these joint solutions are available from Dell. And it's a collaboration not only on co-engineering, which I'll talk about in a future slide, but it's also collaborating around technical support, around professional services, providing high-touch engagements to end customers so they can have initial success with OpenStack and understand how all the moving parts fit together. And it's a goal of this partnership, these cloud solutions to build more, thank you, to kind of get to the mainstream enterprise. I think I called it yesterday, OpenStack for Mirror Morals, so that more customers can gain benefit from the technology platform that OpenStack has created and generated significantly greater utilization out of all their compute storage and networking resources. Joseph will talk about the solutions. They're predefined building blocks. And then we have a professional services person go out and install the software because what we're finding is that there's a lot of different use cases, certainly DevTest use case and content delivery. Joseph will talk more about those, but the building blocks are pre-designed and pre-configured so it takes the guesswork out of the solution for the customers. And this is a global initiative. We're going to operate in all the geographies in which Dell and Red Hat collaborate globally. Focus. As I mentioned, Red Hat's been a top contributor to the last three. The Grizzly, Havana, and Ice House releases. We give everything back to the community. We make sure that all our bug fixes, security, errata, anything that we work on goes as contributed back to the OpenStack community just like we do with Linux. And the goal of our partnership, as I said, is to try and get to more mainstream enterprise customers who maybe don't have the technical wherewithal that some of the new technology giants have when they're deploying their own private clouds. They have their own resources in-house and they can manage and maintain things. Contrary to popular relief, clouds don't just like stay up running all day long. They fall down all the time. Amazons fall down all the time. And so there are people that are knowledgeable about how to deal with elegant failover techniques and how to bring things back up and running and keep your applications rolling. So the origin for the bridge analogy is this is a two-way street. As we collaborate with enterprise customers and gather requirements from those customers, we're going to bring that feedback back to summits like this and have our engineers sit down in the blueprints in the design sessions and say, well, I talked to this customer in this vertical mark and I talked to this customer that has this kind of use case. And so we're really excited about the collaboration and what it's going to be able to bring not only to us as partners and as business entities, but more importantly, the feedback we're going to be able to provide back to the OpenStack community of real-world use cases across a wide range of enterprise customer types. So this is some of the areas where we're beginning to collaborate, storage for Cinder and Swift. And if you were here before, you saw the staff session, although that's not a specific OpenStack project, but it's something that Dell and Red Hat are increasingly involved in now as a result of recent announcements. Certainly making OpenStack more manageable and easier to provision and deploy through Triple O and Forman. When you see the Forman capability in Red Hat's Enterprise Linux OpenStack Platform 5, which will come out late June, early July, that's the commercial subscription version that we make available after doing quality engineering and bug fixing. You'll see how much easier we've made it to install and provision the initial cloud resources across compute storage and networking. Certainly collaborating on networking. Dell has a strong networking product line. You'll learn more about that from Joseph in a minute about what's included in these solution building blocks. And then also OpenStack telemetry and orchestration with Solometer and Heat. Customer expectations. I'll let you guys read the slide, and I'm sure the slides will be made available. The kind of customers that Red Hat's seen success with initially with OpenStack start with financial services where Red Hat Enterprise Linux was kind of born. Financial services companies wanting to see the benefits of commoditization across storage and networking as they've seen with X86 server hardware. Telecommunications companies that want to have elastic and scalable infrastructure, not only for mobile application and rapid application development, but for being able to deliver net new services to the end customers that they serve. And that's kind of for... Dell already has a very, very big business in the telecommunications business, and we've got some good Enterprise Linux exposure with telecommunications companies. But this initiative allows us to go even deeper and get to a point where we're actually touching the mobile users of those telecommunications companies with Red Hat technology. In the retail vertical market segment, we've seen some success with retailers that want to have elastic and scalable computer infrastructure just like Amazon.com has, and OpenStack brings some of that functionality. Public sector companies that are increasingly predisposed to non-lock in free open source licensed solutions because it's kind of a civic responsibility. And then educational institutions doing high performance computing and big data analysis of really complex projects are places where we've seen success. And as I mentioned, a real big part of this partnership isn't for us to just go out and sell stuff to customers. It's to get those requirements in feedback and drive it back into the OpenStack community development process. And with that, I will pass it to my colleague Joseph. Thank you, Bill. It's good afternoon, everybody. Once again, my name is Joseph George. I work for Dell and the emerging solutions business. So things like OpenStack, things like Hadoop, things like Ceph, things like NoSQL technologies fall into our group. And we really have a charter to go out to the Enterprise, the mainstream markets and figure out how we take these new emerging leading edge technologies and figure out how we bring it to our broad customer base. Before I go too far, let me kind of see a show hands here. And one of the questions will not be, are you awake? I will not ask that question. First question will be, how many in this room are developers for OpenStack, for the OpenStack community? How many developers do we have in here? Okay, just one. How many folks do here are operators or on the operator end of the cloud environment? Okay, we've got a few. How many are looking at building an OpenStack cloud for their own business? Okay, we've got a few more there. Okay. So this is about the right mix. Usually I see a little bit more developers in this type of an audience. But let me start out by saying one of the reasons we got into this space, and this is like Bill had said, this was a day one thing for Dell. 2010, July 19th, when the press release came out from Rackspace, we were full in on that day. So if you actually were to go back and look at the press release and on July 19th from Rackspace, you'll actually see Dell mentioned as a partner and a quote from Dell, our GM of our server division, fully endorsing this. And this went all the way up to the top at our company of getting in on day one. And the reason is that we actually came from a group within Dell called the DCS team, the Dell Data Center Solutions Team. And that team was tasked with building out some of the biggest clouds in the world. So we had a real sneak peek into how these distributed scale out environments were to run. And we know how cloud environments run, heavy automation, a lot of open source, configuration management tools, distributed architectures, a lot of things that our mainstream customers just don't see. So what we went in with is to try and figure out how we take this cool, new, emerging way of doing computing, which we believe everybody will do one day. How do we take that to the enterprise? And that is important for our community. I want to just highlight that for a second. For the OpenStack community, I myself have been a part of the community since day one. I've been fortunate to be on the board. I've been, you know, my team's helped spearhead the meetups in Austin as well as in Boston. We take the OpenStack community and the effort very, very, very seriously, as do our partners at Red Hat, which is why this partnership's really important. To drive this into the enterprise is what will bring more validity to what we as a community are doing, okay? Over the years as competitors, traditional competitors of ours got into this business, a lot of folks, especially the press, would like to come and say, hey, I'd like to get your take on, you know, so-and-so joining the community. You know, they're a competitor of yours. What do you think about this? My answer's always been that's fantastic because it's driving the community forward. Getting more people, more communities, more vendors in provides credibility to this. So my point here is that adoption by the enterprise of what we are doing, of what this distributed open source cloud is, adoption by the enterprise is critical so that we can continue to get the investments that we need into the project. We can continue to invent, as a community, we need that enterprise adoption. And that's why this is so important to me. It's why it's so important to Dell. It's why it's so important to Red Hat and why we've partnered together. We are trying to take what our community is developing, us being participants as well in that community, and Bill talked about some of the projects we're working on together. We want to build with you, but we also want to be those flag bears to the enterprise. We, Dell has lived there for a long time, Red Hat's done that lived there for a long time, specifically in the open source portions of it. We want to be those flag bears to the enterprise and that's really what we're going to be talking about today. So as an interest person yourself or as an influencers to others around you, that's really what's going to be important to me and what we're going to be working away with from today. So let's talk about a few things that come with the, and it's the Dell Red Hat Cloud Solution powered by Red Hat OpenStack. It's the actual solution. It's a packaged solution that if you talk to your Dell rep, they are going to know exactly what it is that you're talking about. And our goal here was to provide a very simple, easy to use, fully supported, hardware, software services solution for anybody to be able to pick up OpenStack and implement it using open source community components. That's what we are here to do. And that's, so with that in mind, there's a few things that we made sure that we were addressing. So number one was really certified end-to-end solutions. If you go back to what I said before about how these big cloud environments are running things and how traditional IT runs, if I look at traditional IT, I see a lot of administrators that are there certified by Pick Your Favorite vendor that are trained, that are given documentation, that are given certifications, that are given hands-on labs. So make sure that they know how to run and operate this. In general, that sort of packaging hasn't really existed in the OpenStack community, and that's something that Dell and Red Hat are partnering on to make sure that there's a full, certified, validated solution that we can hand to a customer who may be completely new to this. They don't have Python developers on staff. They don't have regular contributors to staff. What they do have are very smart technical people that want to figure out how they can make this applicable to their business. A good example, I was with a customer just about a month ago, and I talked about the different models of how you can make OpenStack relevant in your environment, and I referenced the model of, you know, going out and finding people like in our community that know how to develop towards sender or know how to develop and actually contribute toward the Glance project and bring them on staff and build that out. It's interesting. Some set of customers will actually say, that's our model, and a lot of you probably know some of the big names that do that. A lot of the customers that are mainly more in this enterprise type market will say, I'd rather not do that, and the reason is really two-fold. Number one, I want to support and endorse the community, let the community drive it, let that innovation happen there. But secondly, if I've got OPEX, if I've got dollars, I want to figure out how I make my business move forward. That's what I've got to do. I have limited OPEX, limited people. If I have additional OPEX, I want to figure out how my people can move the business forward, and that's where they're focused on. And Steve Stover mentioned that at the SolidFire keynote when Dell was on stage with them today. This is the customer where we actually can go to them and say, we have done this. Other things that are similar to you in your IT environment, other vendors where you have certified admins, you have support behind it. We have something like that for OpenStack that Dell and Red have put together. It gets them very excited about OpenStack, and that's what we need to drive here. Let's talk about enterprise use cases. Bill talked about this a second. A lot of our customers at this point in 2014 are not trying to pick up OpenStack because they want to pick up OpenStack. They have problems they're trying to solve. They have new applications they're trying to deploy. There's a pending change with applications coming. They want to get started now. So they're looking at things like building out test dev environments. They're looking at things like storage as a service, which is one of the most popular use cases right now in Kamesh who was just doing the last session on Cef. I mean, the people in the room, you could tell the interest level that's there. That is a very highly, a high base of interest among our customers, storage as a service. Platform as a service is another one. Bill mentioned content distribution. This is actually a really hot one among our telco customers where they want to start distributing content, images, videos on the web. And when they look at their traditional technologies that they have in their environment, it either can't scale to that level, it's not performant to that level, or it's cost prohibitive. And this is where OpenStack comes in and fits extremely nicely as long as they don't have to build it themselves from the ground up, okay? So another thing to note there that you'll see is that technologies existed in IT organization from one function that might be different from OpenStack, and they will sit. You'll see OpenStack and other technologies, my prediction the next few years, you'll see those standing next to each other in a public way as well as in a private way. That will continue to happen. There are use cases where it makes sense for traditional IT to keep applications there, but the new applications that are emerging that live on the public cloud as a first place, as a first home, they're going to need a cloud to live on on-premise, and that's really opportunity that OpenStack has. And then let's talk about the, you know, the risk that comes with this and the enterprise experience. Obviously Dell and Red Hat, we, like I said, we live in the enterprise. We understand how they operate. We understand what matters to them. We want to be the flag bearers from the OpenStack community to go to that group and say, here we have got OpenStack in a way for you, minimizing the risk for them. Because a lot of, and again, this comes from experience. You know, we've been in the OpenStack business for, you know, this will be four years this year, at least since day one. We have built reference architectures and solutions, and we have learned by doing over the last four years. That's one of the great things that history gives you. Being first has a lot of great accolades that come with it. Yeah, we were first. The unfortunate thing is that you get to learn really raw when there is nothing but two piles of code munched together, you get to figure out what you need to work on really to make it stable for a customer. So what is represented in our solution today with Red Hat is backed by history. We have had a track record of taking this to customer sites, deploying on customer sites, learning what works, learning what does not work, and coming out with a solution that we believe is going to fulfill a lot of the customer needs that are in the enterprise right now. And as a result, the risk level actually comes down. Because of the distribution that's hardened by Red Hat, and because of the reference architecture that's been validated over time, the risk level comes a lot lower for customers. And that's the threshold. That's what they need. They need a threshold lowered so they can get started. And that's really what we're all about. An enterprise, great, obviously, fits right into that. Our friends over at Red Hat, we're extremely happy to be working with them. And it's not just a thing where we just see each other at these summits. Whether Bill likes it or not, I like my face multiple times a week. We're on phone calls multiple times a week. Meeting, planning. Every day. Seriously, the line between us... Don't sound so enthusiastic. No, no, but the line between our two companies working together is becoming almost invisible. It really is. It's just that we're extensioning each other's teams. In fact, there have been a couple of instances this week where we've had executives from both companies meet some of our team. And we've had to say, this is Bill Mason. He works for Red Hat. This is Joseph. He works for Dell. Just because it gets really convoluted that way. It's a great way to drive enterprise grade solutions, which I should say is the expectation from the enterprise. They want something that is going to work, that's robust, that's supported, that's been tested. I won't spend too much time on this. This is kind of a view to what we had announced. As Bill said, there were two important announcements that came out about this relationship. Number one, we will be building a joint solution in market, the Dell Red Hat solution, which has now launched. It is now fully available. If you or your circle are interested in something like this, you can talk to a Dell person or a Red Hat person. They can do it today. You can get on the phone, start mapping this out. The second thing is a co-engineering, a collaborative element. So we have engineers that were just over at Red Hat last week, actually, that are working on collaborating with specific projects and where Dell and Red Hat will work together to contribute all of this back to the community. So everything that's going to come out in this distribution, it's going to be hardened and validated and supported. But anything that's new, that's generated in that distribution, 100% is going to be going to the upstream. That and Dell is going to be a participant in that today and will continue to be a participant in that going forward. Now, we'll spend a little bit of time on this. In the same vein of trying to make it simple, what Dell has done in partnership with Red Hat is actually pull together three configurations for our customers on how they want to buy. One would be a POC. And POC here means proof of concept. I had to clarify that yesterday and yesterday's session. People didn't know what POC. And apparently there's a lot of different definitions I'm finding. One point of contact was one, piece of crap was the other. But this is the proof of concept configuration. And really what this is for, it's a great first step for a customer that's never done this to really get a very small stamp and get started on working on OpenStack. It's a really nice, easy way to get seamlessly into that. And we'll go into detail about what's in those bundles. Secondly, for the pilot bundle, it's essentially a 2X of what the POC looks like. But it's got a deeper, more sophisticated networking area. It's actually gotten more around OpenStack storage. And actually can actually host more VMs as usual. So it makes it easier for a customer that may not be at the proof of concept level. Maybe they're a little bit more sophisticated. And it gives them a nice, good, beefy stamp to start with. And the beauty of this is that as a result, you know what, I should turn that off. Sorry about that, although I'm sure you guys enjoyed that. It actually also is a nice way to scale, right? So once you buy that pilot configuration, it's a nice way just to go get additional blocks of this configuration and just scale it out. One of the things that we've learned over the last few years has been there's a shift between going from something like a POC or a pilot to production scale. Traditionally, with a lot of our server infrastructure, customers will do a POC on site for whatever period of time. They'll make decisions. They'll say, you know what, love it. Love the POC. Went well. I'm now ready to buy production scale system. What we found in not just in OpenStack, but in other emerging technologies like Hadoop and NoSQL technologies is that the POC evolves into the production unit now, right? So a lot of our customers will start with the proof of concept, will bring workloads onto it, will tune it for their environment, make sure the right networking and authentication connections, all that happens, and then once they get it comfortably, and those of you that work with OpenStack understand how important this is, once you get it to where it's tuned really well, you don't really want to tear that apart and start over again, right? You want to use it. You want to be able to build on top of it, and that's really what this pilot configuration allows you to do, is to just start building right around it. And this is something our customers have done a lot of, is start with a very base kind of bundle and then start building around it based on the workloads that they've got and the horsepower that they need. The final one, which I won't spend too much time on, is the production scale. And the reason I won't spend too much time on it is it basically uses the main form factor behind the two bundles before it, but it's primarily a services engagement with Dell and with Red Hat. And the reason that is is because if anybody here has actually tried to deploy OpenStack at a large, large, massive scale, it's hard to do that out of a box, right? It's hard to do a thousand node, two thousand node OpenStack environment out of the box, take it in, plug it in the wall, and it just works. That's just not how it works. It does require a networking discussion. It does require discussions around who will be accessing and what their roles will be. It'll have discussions around what the specific applications that need to run on it. And Dell and Red Hat have actually figured out a way to actually manage this with every customer, have a conversation, work out what it is, and then implement it for their environment. It's part of our DNA, and it has been for a long time. So the production bundle really is around a very deep, specific engagement with every customer one-on-one and figuring out what's right for them. Okay? At a very high level, this is kind of what the bundles look like, and I'll do this for all three of the configurations. So first of all, the proof-of-concept bundle, I'm really careful about saying proof-of-concept now. I want to say that every time. The proof-of-concept bundle is actually a five-node stamp using our mainstream R720 server hardware. It is, you know, if there are Dell customers in the room, a lot of our customers use the R720. It's a model everybody's really familiar with, a standard X86 server. We have configurations and tunings based on a reference architecture that will tune it a certain way to optimize it for OpenStack. From a networking perspective, we're using our Dell networking S55 switch, which is a one-gig networking capability. And from a distribution perspective, we have brought in the Red Hat validated OpenStack platform and then services that come from Dell from consulting, deployment, and support. So as the customer is growing, as the customer is evolving, if there are issues that come up, they're able to pick up the phone, rather than go on it on their own or try and reach out to a community mailing list. They can pick up the phone and dial an 800 number. They have someone on the other end who knows what they're talking about. When you break it down, the nodes, you've got the first couple of nodes are kind of manager and controller nodes. And in particular, there's a few nodes dedicated for the Nova compute modules. Now, one thing that's missing here is there's not a storage component separate here. In this model, because it's a proof of concept, and again, this goes based on history, we found we've been able to give customers a very small stamp and leverage just the local disk with the Nova compute capabilities for them to be able to just get a taste of how OpenStack works. And this has proven time and time again to be adequate for kind of a first step into the OpenStack framework. Now, one thing that we are doing a little different here, a lot of our customers that are familiar with the public cloud model will be told this is the kind of virtual machine support you'll get. So in this particular configuration, we can support up to 90 virtual machines based on the specific configuration choices around memory and things like that that you make. But that's really what this stamp looks like. Five servers, one gig networking, basic Nova compute capabilities, and up to 90 virtual machines, and this is that proof of concept bundle. Now, when we go up to the pilot configuration, again, there actually are some customers who use this as their first step just because they don't see the need to just learn a little bit about OpenStack. They're ready to make some real commitments at this level and just want to start testing out applications and workloads. And I'll just spend some time on what's different here versus the proof of concept bundle. So here, you're actually getting a much bigger rack. I think it's a half rack as opposed to a quarter rack. So in terms of actual nodes, I think it's an 11-node configuration versus a five-node configuration. One difference here is that we actually include our 720XD server model. And really what that is, it's just like the R720 for familiar with that model, but it has capability for additional disks. So you can actually expand it out to have a very strong local storage footprint if that's for this configuration. It is one of the options that are available to you, but it allows you to have a very strong local disk capability there. Also in this configuration, we also up our networking to a 10-gig networking configuration, which we're including our S4810 switch from our Dell networking group, and it allows you to actually take advantage of extra bandwidth. Again, with this kind of horsepower, the applications change, and the requirements change a little bit, so we bump it up to a 10-gig platform there. The other difference here, in addition to just more horsepower on the actual gear, we do include sender capabilities here. And I think I saw Kamesh on the last slide, on the last session that it's actually Ceph nodes that are actually included in our part of that solution in the next release. So right now it's just sender capabilities with Red Hat storage, and then in the next release it will be our Ceph capabilities now that Red Hat has acquired Ceph. And in fore context, a single POC bundle can have up to 228 virtual machines, but bear in mind this is something that can scale. As you add more, your whole cluster can actually grow as a result. I won't spend too much time on this. The only one thing I would say here is that PowerEdge C servers are an option as well here in this case. PowerEdge C, I mentioned DCS before, the team that built out all these custom infrastructures for the biggest clouds. I can't name them obviously, but if you think of the biggest clouds in the world, those are our customers for their environment. PowerEdge C was actually a mainstream server line that came out of that. So if I talk about that for just a second, when we looked at all these large-scale, distributed clouds, we saw about 80 to 90% of what they wanted was about the same. They would come to us and want to buy several thousands of servers at a time. And these are companies that spend millions and billions of dollars a quarter just adding more and more power, and I should say compute power to their environment. What we found out was that density mattered to them. We found out that power management mattered to them. We found out that software, redundancy at the software level is what mattered to them. We found out that automation and open source mattered to them. So what we started doing was realizing that with that 90% that was about the same, we could actually build a server line that actually captured all that goodness, and we would still build the custom environments for the largest-scale customers. But for the customers that want to get to distributed scale that can't spend billions of dollars a quarter on gear, there's a model now, the PowerEdge C model that can actually enable that, and it is a model specifically for cloud and hyperscale solutions. So that is an option when you want to build out a production configuration, when you talk to our services teams, they can use that as an option as well. I think I've just got a couple of slides and then we'll open it up for any questions. Let's talk services for a second. And again, let's go back to who we're talking about. Our enterprise customers, again, generally are not heavy in writing code for the community, are not regular contributors. So in addition to us providing the guidance, whatever we can on a packaged basis, they need a lot of help in terms of services. So things like consulting, things like deployment, going on-site actually deploying it, while they have actually, once they've actually deployed it, ongoing maintenance and support, right? How do I grow it? How do I fix this problem that's sprung up? I need somebody behind me to actually pick up the phone and call somebody, and that's really what Dell and Red Hat are doing. And beyond that, this is now a group of people that we want to train, not just in the new capabilities of OpenStack. Remember, this is a new way of doing computing now. It's a very different way of doing things. And so as that company, as these customers start evolving that way, we've already started setting up training between Dell and Red Hat making that available for our customers that decide to go through this model. They've got training and certification on the Red Hat components. Those training sessions have items around DevOps, include items about new distributed architectures. All those things exist as part of the training. This is a really good example of the things that the enterprise has come to us and looked at what we're doing, Dell and Red Hat together, and given us a big thumbs up to say, this is what we have needed, something that is really important to our portfolio. I'm not going to spend too much time on this. Let me just say, this is not just something that's theoretical in our mind. As soon as we started working on this and starting announcing this, our customers have actually come to us and have actually said, yes, this and more and more and more and more, keep it open. Keep it open as much as you can. We want to see the innovation that's happening in the community to continue. There's an interesting survey that's done every year by Black Duck Software about sentiments toward open source. I Google it, you can find great information about it. Some interesting stats. A lot of the enterprise, and I think this last time around, 900-some enterprises participated in this survey, but a lot of these enterprises are now looking at open source, not just OpenStag, but open source as a way to drive higher innovation at a faster pace than we have traditionally with proprietary options. The attitudes toward open source are changing. The attitudes toward collaborating are changing. Us keeping ourselves open, us keeping ourselves up to speed with the community, us partnering with the community and participating in the community, that is the model that we're trying to drive here. One interesting stat may not really completely be related here, but it caught my eye. One interesting stat was at the end of those respondents actually said that they expect to collaborate with their competitors to drive innovation over the next three years. That, my friends, is a real shift in how our IT organizations are operating. Okay. I think this is my next to last slide, and then I'll buy Don here. Very, very high level roadmap. The V1 is really what we just announced here at the Red Hat Summit just a few weeks ago. Really to get a solution out there. In the June, late May, early June, July timeframe, we will have a version two that will be out focused on Ice House. If you look at the kind of things that we're trying to focus on here, you'll see it's a very storage centric type release. We want to make sure that those of our customers that are using our products like Equalogic that have been constantly bombarding us with help. We want to figure out how we include Equalogic We are answering that call here with this release. As well as some of the newer technologies around SEF, like you heard with the last session, it's a big part of our strategy. It has been for a long time. As well as the Red Hat Storage server that's coming out. Version three, my team that created this said it's a secret so I can't tell you too much. Based on the timing you can tell this is the June of timeframe. There are use cases that our customers are going to be using this for. I mentioned some of those things. Storage as a service, content delivery. These are the things that we're going to be focusing on to make sure that they are continued to be enabled to pick these technologies up, use them and have the support behind them that they need to drive it forward. Let me kind of end with this here. Hopefully you can tell that to Dell and to Red Hat driving innovation is what matters. For Dell in particular, this has been a part of our DNA for a long time. What can we as a company do to drive innovation forward? Not just in this space, but in every space. How do we drive innovation? How do we empower our customers to do more than they thought they could? OpenStack represents that. That's why we have the teams we have on OpenStack. That's why we invest in OpenStack the way we are. Really it is the community that we drive forward. That's where innovation is coming from and we continue to do that. Last slide here. Promise. Last slide. If there are questions or comments, if you have customers, if you have people in your circle that are looking that you know may not be at the caliber that a hardcore Python developer is, maybe they're not a PTL of one of the projects, but they're looking to get installed or they've tried OpenStack and it still remains to be a little science project there. We can help. Let me just give you a few ways to help let us get connected with the people that are out there. Websites, obviously you can learn way more about that, dell.com and then redhat.com slash dellcloud. We'll give you a lot of the information I shared here. Case studies. The first case study that we did is our own IT organization. Our IT organization at Dell represents the kind of customer we are going after. OPEX is spent on furthering the business, not on hiring a bunch of developers to be in the community, which is a strategy, but that's not how this customer wants to do it. We have a full documented customer reference on this website that you can download and read through what their problems were, how they're solving it and how they continue to actually evolve it over time. So check that out. I also want to mention the solution centers. If you or your customers are interested in doing a proof of concept, you can actually do it on Dell on a Dell site with an architect that's already stood up. There are staff, there are experts on site, there's gear already stood up. You can actually schedule time and bring your workloads to those centers and they're spread out all over the world. Obviously Austin, Texas, Chicago, New York, Shanghai, Europe, they're all over the place, so take advantage of it. Finally, I'll just leave it at this. If you don't remember any of these things about how to get in touch with somebody about this, OpenStack at Dell.com will always get you to the right place. You've got architects, marketing folks, sales people, executives looking at that inbox, making sure that customers that come in are serviced appropriately. So if you remember nothing else about how to get in touch with Dell or Red Hat on this, drop us a line at OpenStack at Dell.com and we'll get you there out of the right way. So with that, I think we've maybe got just a couple of minutes if there are any questions and I'll invite Bill to come on back with any questions that might be out there. I will say a little bit that Red Hat has actually done a great job in helping our Dell IT team actually stand up their first OpenStack Cloud in a real meaningful manner and we can have some questions about that if you'd like. We'll open it for any questions that might be out there. Okay. Yes, question. Okay, OpenStack manager and the controller. Hello? It's really just the OpenStack components, right? There's not a separate code path or anything like that. We use Foreman to do the provisioning and you have the horizon dashboard and the telemetry you get from Solometer, for example. So it's not meant to imply that it's something separate or different. Yeah, that bullet item refers to the Foreman provisioning capability which we've improved in our OpenStack Platform 5 which will be commercially available in the end of June, early July. It's a fair point. It doesn't necessarily need a separate node to run but that's the way the configuration was defined. I don't know. Right, so again, based on the deployments we've done in the past having something dedicated because Foreman is not really just about deployment. There's a lot of other things that are kind of tied into that. You could put it on one of the existing nodes but then you start taking cycles away from other things that it needs to run against. Any other questions? I think we are actually out of time so if you have any, feel free to come up. Thank you for your time.