 All right. Looks like we're live. Thank you for joining us this morning. I can see the die-hards here. After all the parties, you're still able to get up in time to make a nine o'clock talk, so thank you for that. I appreciate it. My name is John Mark Walker. I'm the Managed IQ Community Leader, and with me is Chris Wells, and Chris, what do you do? I work at Red Hat, managing product marketing teams in our cloud management business unit. Excellent. And so today we're going to talk to you about open hybrid clouds and managing hybrid clouds, and specifically how you use Managed IQ to help manage hybrid clouds throughout your infrastructure, including OpenStack, but not just OpenStack. How many of you are here because you heard the Managed IQ announcement earlier this week? All right. A few. How many of you know about the Managed IQ announcement earlier this week? All right. Cool. So, yes, as you may have heard, we've announced the name of the project we're doing with it, and I'll get into all that later. But first, we kind of want to set the tone for what we're doing and why we're doing it. The first thing is about hybrid clouds in general, just a really simple question. Do you want hybrid clouds? The answer is pretty clear. The market is very clear in which way it prefers there. There's a very clear preference for hybrid cloud technology, the ability to manage multiple clouds, to integrate them into a single pane of glass, to manage them together side by side, to do workload management, all those things that we think of when we think of hybrid clouds or clouds in general. But that's a simple question. The more detailed question is what's the number one problem that you're facing that you want clouds to solve? And the resounding answer here, and you can see what this chart is, it's a summary of what's your top problem, number one, two, and three, when you list all three. And the interesting thing about this chart is for all of those, number one, two, and three, it's management. It is the sore point when you talk about clouds and what you're doing with clouds. You can see several others there as well that pop up. Certainly security is up there. How do you manage cloud security? It's still frankly kind of an open question. It's something that is still being addressed. It's something that we're dealing with as we go along. Some of these you'll see are software problems. Some of these are not software problems. And so when you really think about it, we've helped to isolate here the ones that can actually be controlled, the ones that can actually do something with software. Unfortunately, I don't think software can do anything about culture. If you have to solve a culture problem in your organization, we're probably not going to be able to address it. But you can see the ones we've highlighted. When you talk about management and operational processes, it's about how do you automate provisioning? How do you make a self-service portal? How do you deliver services? When you think about the financials, how do you find out how much you're being charged or how much are you charging? How much of your capacity is being utilized and by whom and where? All these things are questions that have to be addressed and can be addressed through software through a little work. And that's what we're going to talk about how a managed IQ fits into that whole. When you think about what is a cloud encompass, you think of the usual things. I think back in the day when Dave Nielsen came up with this for parts of a cloud, there was certainly a self-service bit. When I'm going to provision something, when I'm going to create a service, I should be able to do it in a point and click way. I should be able to do it myself without the aid of needing some admin on the back end to manually do it for me. I should be able to determine where my workloads are being deployed and managed. I should be able to determine who's using what and how much they're being charged. I should be able to put a meter on the different services that are being used. I should be able to limit how much of each service is being used. And then institute quotas for compute and RAM and storage. I should be able to broker between multiple cloud platforms. I should be able to burst to a separate cloud when the capacity utilization reaches a point where I can no longer fully service what is needed at any given time. So I should be able to leverage what I already have as opposed to having to do green field deployments all the time. These are the things we think about when we think of open hybrid clouds, or what people want to do with the cloud. This is kind of what, but the people don't always think about it. It's something that there are gaps in the market here that with an open source platform we're trying to address. And these are sort of the questions we want to answer with managed IQ. So when you think of the typical self-service model, when a user is more super user, because we're thinking of both the administrator as well as the end user. When they're presented with, well, I want to deploy a service in a cloud platform. You're faced with all these different choices. Ideally, you could just have a single pane of glass. But what usually happens is, well, I've got this thing and I want to do X. I have X, I want to do it in place Y. Well, how do you determine which platform you deployed on? How do you determine which is the best to suit your needs at any given time? How do you know what the latency is going to be in your application if deployed on AWS versus some OpenStack-based cloud? And furthermore, once you do deploy on one of those, how do you manage the application that you've deployed? How do you manage the service? Can you actually utilize all the different managed platforms to give you kind of a holistic view? And the answer usually is, each cloud platform also has its own management interface. And you have to look at them in siloed arrangements. You can't view them at once to give you a holistic view. You're depending on each platform to give you its specific interface. And this is what I would call suboptimal. And if you're a user or administrator and you're facing this task, it's kind of beyond the scope of what you want to do or what you can do. And it makes cloud management a whole lot more manual than it really should be. Because the whole point of clouds is to be self-service, to be automated, to be orchestrated. And when you're dealing with individual platforms, there's simply no way to do that. This is to say nothing of each individual cloud platform, because they all bring certain features to the market that are great and they're highly used and they're wonderful. But when you think of it in terms of the broader context, that's when you start running into problems. And the siloed arrangement here is something that probably needs to be addressed sooner rather than later. So let's think about what people would like to see when they're presented with the problem of cloud services or services deployed on cloud platforms. When you think of it, when someone mentally pictures what they're doing in the cloud, what they really want is to be able to go through from the beginning and say, I want to deploy this service. And there should be some logic that determines where that service goes and how it's managed. Obviously, there has to be some way to determine who can do what. So you need some sort of role-based access control to be able to delegate, to be able to delegate to different users, to be able to do a self-service portal. That doesn't necessarily know what happens on the back end. So to make it a seamless transaction. And there should be some sort of service catalog or portal that the user can go to, point click and say make it go. And then they don't care what happens to it after that. That's what people think of when they think of, well, I want to use the cloud. And this is, when you can see here, I have the managed IQ logo here. Because that's kind of what it's designed to do, to give you that holistic view, to give you that single point of interface into the cloud management back ends. And so when you look at this holistically, and you look at what managed IQ brings to the table. There are all these sort of cloud enablement pieces, the services that people think of with cloud management. Like the ability to do compliance management, the ability to do the self-service portal. All these good things that you think of with cloud management. In charge of facts, in quota management. But there has to be a way to integrate that with the infrastructure services below. It's not just the cloud services that you're managing. It's the infrastructure you have to be able to allocate and manage along with that. It's a total systems management picture. And what we're saying here is that the cloud services management has to be integrated with the holistic systems management piece. It's not separate from it's integrated with the infrastructure that you have already. So one of the things that we've seen this week at the conference I think is a pretty consistent theme is this rise of the super user. And what we've seen from our perspective, and I've talked to a lot of organizations and customers over the last couple of years, it's been a lot of focus on how do you take and actually build out the cloud infrastructure. And a lot of people will start with the self-service portal. They'll start with the underlying virtualization. How do you put the infrastructure together? And one of the things I've noticed this week at the conference talking to different customers and organizations, people are now actually starting to take OpenStack. They're starting to take their cloud infrastructure platforms. They're actually starting to put them into production. It's not just lab cases anymore. It's not just pilot projects. They're really starting to put into production. And now what they're finding is they have to kind of transition in the organization. And we see this rise of the super user, this rise of someone who's really responsible for that ongoing management, that ongoing IT operations of it. In order to be effective in their job, they really need to be able to do two things on this plane of management. Here at the top of the screen, they've got to be able to provide these cloud-like capabilities, not just things like self-service and compliance that John Mark talked about and the charge back and the quota enhancement. But they also have to be able to manage effectively the underlying infrastructure across multiple different cloud platforms to be able to do the resource management, the capacity planning. And what you'll see we're going to talk about here with Manage IQ is by open sourcing that we're really bringing a cloud management platform that is completely open sourced across multiple, managing across multiple different types of infrastructure to really help with these two different planes, to bring cloud capabilities across the top, but also being able to effectively and efficiently manage the resources across the bottom. So let's look back again at the self-service portal characterization. And look at it in a bit more detail and go behind just the interface and look at what's going into it. In order to be able to do the intelligent provisioning and management, you have to have a really good role-based access control mechanism in front. So you can control who has the privileges to do a specific service. You have to have quotas so that you don't have a couple of users dominating the existing resources and making things sluggish for everyone else. You have to be able to have some sort of approval workflow so that you can manage which resources are being allocated at any given time. Then you have to be able to determine where the workloads are being deployed, doing the whole workload management and capacity management piece in one on the back end. And you can see the way, so this is the way it should work. And this is the sort of functionality that Manage IQ gives you. This is what we allow you to do on the back end. So you can see sort of in a level of detail what a self-service portal actually means and what actually goes into it. It's not as simple as people, well, the end users should think it's simple, but there's a whole lot of logic that goes in the back end that you shouldn't see because it should be seamless. And so now we see the whole cloud service life cycle. It's not just about deployment. When you look at what we've been able to do with OpenStack thus far over the last four years, it's been all about deployment, building new services, it's about maybe administration. But there hasn't been a focus on the whole management life cycle piece, the whole cloud services life cycle. When you look at the whole picture from the provisioning to delegation and role-based access to the optimization according to performance, to scaling when you need it and the whole capacity management piece, to end of lifeing services in a way that doesn't interrupt service delivery. When you look at the whole picture, we're kind of venturing into new territory here with an open source managed IQ. And this is the picture that we want people to think about when you're going to be managing multiple cloud platforms. So let's look at where we are with respect to OpenStack and what this means in an OpenStack world. How does managed IQ fit into the picture of OpenStack? If you look at the breakdown of the typical OpenStack project or with all the different projects that comprise OpenStack, you can see a variety of pieces that have been developed over time, kind of in their own individual spheres with a little bit of management administration on top of it in the form of Verizon. When you look at the authentication management in Keystone, it's really good at providing authentication services for OpenStack users and for different OpenStack management. But what about for other services you have running on other platforms? When you look at the Verizon dashboard, what is it really giving you? It's giving you a look at various metrics that make up your OpenStack deployment, but it's not in the context of the broader infrastructure. And so when you look at the tangible pieces of OpenStack, is there a cohesive whole? Where is the orchestration? Where is the lifecycle management? Where is the broader picture? And that's kind of what we're aiming to fill with the managed IQ release. And so when you look at the broader topology, the broader taxonomy for cloud management, we want you to think of the whole picture. We want you to think of, virtualization management is a very important piece of it, obviously, and you'll see that isolated at the bottom left. But what about the pieces above that? What about everything else that we think of in terms of cloud management? This graphic is courtesy of our friends at Gartner, and they sort of highlighted in yellow here the pieces that make up cloud management platforms. And self-service provisioning is at the top, but there's a whole lot of other things going on in addition to that. When you think of charge backs, when you think of charge back management, when you think of capacity management, when you think of role-based access, when you think of all the different ways, the orchestration layers that you need to manage everything from a bird's eye view, to be able to give you the single pane of glass to your infrastructure. And that's really what we're driving at here, is you really see about the entire infrastructure, not just one specific cloud platform, but how does it work in context with everything else? We typically allow the organizations that I'll talk to, when I ask them, they're interested in building a private cloud, they want to get that agility, they want to get that self-service and innovation into their organization. They don't look at their cloud as having all these characteristics, so it's not just the underlying virtualization infrastructure, it's not just the self-service portal, but it's everything that has to go around that. Especially when I talk to people on the IT operations side, they want to make sure that they have the necessary controls in place for that private cloud so they can manage that capacity, they can offer charge back capabilities, be able to manage performance and all those kind of things. So one of the things that we've seen from the Red Hat perspective, when we did the acquisition of Manage IQ, is we realized if someone really wants to build out a private cloud, they need this entire stack. They need not just the underlying infrastructure, but they need all the management layers to go on top of that to really be effective and be efficient with their private cloud operations. I spoke with two different people this week, you kind of illustrated the whole problem. One of them has multiple OpenStack deployments in-house and they have no easy way to orchestrate between multiple deployments of multiple versions of OpenStack. And so they're looking for an easier way to do that. And so when I told them about Manage IQ, his eyes lit up because that's exactly the sort of thing they want. Another gentleman was talking about migrating from one version of OpenStack to the more recent Ice House release and finding that it requires a lot of manual intervention to make that happen. And wouldn't it be great if he could just add in the logic that allowed him to migrate services without disrupting existing services? And that sort of shows you where the gaps are that we're trying to fill. When you look at what we're trying to do, we're really just augmenting and extending what OpenStack can do. OpenStack is a great, wonderful cloud platform. I've been very excited to watch the growth of the OpenStack community over the last four years. I was very excited when RackSpace and NASA came together to start this community. And it's been wonderful to see it grow. You know, I was there a couple of years ago, three years ago in Boston when I think there were less than a thousand people there in attendance. And to see it now grow to about 5,000, it's been great. And so I think we're now at the point where we can think about growing functionality to include other things, to go up a level, to push things up a notch. And so when you look at the cloud, when you look at the Managed IQ, I guess, architecture you could say, these are the pieces that we bring to the table, the pieces of automation and management that we want you to think about for what Managed IQ does. And when you look at cloud governance, you look at the ability to add policies and rule-based mechanisms to automatically allocate services where they need to be. When you think of the automation orchestration piece so that you can go across multiple platforms with different services, when you think about financial management and the ability to tie into your financial resources, the ability to tie into the chargeback mechanisms and that sort of management piece, that ability to manage what services you deploy. When you talk about the storage management on the back end, when you think of instrumentation so that you can tie into whatever metrics and monitoring pieces you have on the back end, you know, in a minute we have the ability to tie into your salameter for that particular example. And then you talk about resource management, capacity management. Do you have the ability, do you have the resources currently to allocate for this particular service? And if not, can you shift it somewhere else to do the workload management piece? This is sort of like the holistic view of ManageIQ and where we fit into the picture. Yes, I mean ManageIQ functions really as an abstraction layer on top of all the various infrastructure providers in your environment. So it truly is hybrid, both hybrid across different types of hypervisors and virtualization platforms as well as public cloud providers like an Amazon. But let's talk specifically about the open stack examples since we're here at the summit. Oh yes, open stack. As you mentioned, we're really about abstracting above the tooling, so you're not tied to a specific platform. And so if you look at open stack as an example, this again, this is not an actual technical slide. This is sort of, this is conceptual. It's architecture. I hate that word, but so be it. But you can see in this instance how you can tie in cloud governance with the different open stack components that you can orchestrate at a higher level. Elevate the open stack piece to a higher level and lift it into a broader context. When you look at the image service of Glantz combined with the orchestration and automation templates of heat with the metrics of the salometer, that lets you define sort of a cloud governance model at the top and you can manage that from a level above and that gives you a bird's eye view of not just what's going on underneath the open stack but lets you orchestrate it as a whole and in context of other platforms. And I think one of the important things to understand here with the managed IQ platform, because it is at a higher level of abstraction, we're not trying to replace the components that are inside of open stack. That's not our intent at all. We know that there are some management components that go in at the open stack layer. That's not the intent of managed IQ. Rather, it's really designed to be a complementary tool that we integrate with those different components. So for example, we can take metrics out of salometer and integrate that up at a higher level like in a charge back model. I think if you go to the next slide, for example, we talk about charge back and kind of things. We can take those metrics out of the underlying open stack system, put them into the financial model. So now if you decide you want to like have different levels of charge back, you want to tear out your storage and you want to charge at a different level or you want to charge back to different divisions or organizations inside your particular type of company, you can do that by pulling that information out of open stack as well as pulling it out of Red Hat Enterprise Virtualation or other kinds of places, but it's allowing you to put it into a higher level model. So I do want to be clear that we're not trying to replace what's going on at the open stack layer because there is a need for those individual kind of elemental types of management tools, but we want to be able to bring them in a higher level so you do have that single pane of glass across all the various clouds in your organization. It's definitely one of the things that we've seen this week at the conference. There definitely is that theme that it's going to be a multiple hybrid cloud world. There will be cloud to rule them all. There will be different flavors, different types of infrastructure, and because you're going to have that you have to have a way to bring all that stuff into one common management layer to be able to have all the effective controls and to be able to be efficient around that and that's the idea behind Manage IQ. You know, I think my employer Red Hat has invested significantly in open stack. We want to see an open stack world. We want to see open stack grow and continue to flourish, but we also know that there are a whole lot of people that are going to be deploying open stack within context of, in conjunction with other platforms that are legacy that they're not going to move anytime soon. You know, if they're using public clouds already they're not going to stop using it. If they're using vSphere or some other VMware product or they're using something else, that's not going to go away either. And so open stack deployments are going to be in this broader context and there's really nothing that we can do about it for, you know, quite a while. It's going to continue to be a mixed environment and in fact, I don't see that ever changing. I think it's always going to be a mixed environment to some extent. We can go ahead. I was going to say the other part is, you're just talking to a lot of customers in different organizations. There's a lot of excitement around open stack. People are really interested in taking open stack and now transitioning it from these pilot projects into production workloads. But one of the consistent things that we hear back from people is that they really are worried about this management level. How do they put these controls? I mean, they have certain kinds of, let's say data or privacy concerns or compliance concerns. We heard the gentleman from Wells Fargo talk about that, you know, but they're really concerned about that in their infrastructure. How do they put those controls? What we're hoping, you know, from the Red Hat perspective is by taking managed IQ, by making that now an open source project, as John Mark will talk about in a moment, it's a fairly mature product that we're now turning into an open source project. It's got a lot of capabilities inside of it. What we are hoping is by putting that out in the community and getting it to grow, it will actually jumpstart and help accelerate open stack adoption in the enterprise because it will add that control layer in. And we could do this graphic for a lot of different platforms. Obviously, we did it for the open stack platform because it's the open stack summit. But we could, frankly, do a similar graphic for lots of different platforms, AWS, vSphere, some other virtualization or cloud platforms. It's the same story, although there's a slightly different architecture to each, but about us creating the piece, the management layers and orchestration layers above it. So now we get to the fun stuff. The managed IQ community. What do we want to do with the managed IQ community? Why did we make this open source and what are we trying to do with it? You may have noticed that when we released the announcement earlier this week, we said it's coming soon. Right now, it's a matter of weeks until we actually have a full featured code drop. We're going to be, in the coming weeks, we will be announcing some beta releases. We will be giving you more information about how to use managed IQ, and then we'll have the full project release coming up again in a matter of weeks. I wish I could give you a hard date on that, but not yet. Just understand it's coming soon. I swear. So what did we release? What we're doing is we're really fulfilling our promise to open source managed IQ that we made when we acquired the company. We made the acquisition in 2012. I was actually read it before then, so I'm coming to this project relatively new. But it's something that we had the intention of doing all along. There were just a lot of things we had to do along the way to get to that point. But when you do this, this whole taking a company and open sourcing its product and making it into a community project, this is part of our DNA. It's part of our commitment to open source development, the open source way, and to community-driven innovation, which is something that we're so accustomed to doing. We've been doing it since our inception in the early 90s. It's just something we do. In this case, we think it's, in this particular case with managed IQ, we think it's very beneficial to the broader community, very beneficial to those who have a real need and for whom this answers a real, solves a real pain point. And so we announced the name of the project, managed IQ. That was the name of the company. And so the name lives on in the form of the project and the community. Some of you may be familiar with the Red Hat Product Cloud Forms in much the same way that Fedora is upstream to REL and Gloucester Fast is the upstream to Red Hat Storage and I guess now CEP is also the upstream to Red Hat Storage. Managed IQ is the upstream to Cloud Forms. And so we're creating a branded community around managed IQ with its own identity. We're going in with, it's not just us. There's a whole lot of other people going in with you, with us and I'll go into some detail on that. But right now, if you go to Managed IQ.org, you'll see how you can sign up for more news. We'll be releasing more information and documentation as we get closer to the release. And if you sign up, you'll have some access to some early release betas that we'll be coming up with fairly shortly in probably a couple of weeks. And then when we actually do launch the community, it's going to be a full-featured community. It's going to be full-source code. It builds. It's going to be easy to use. And you should be able to get to what I call the aha moment relatively quickly once you download the community build. You should be able to understand fairly quickly what it's about and how it's useful to you. And that's really our goal, to make it simple for you and just resolve a real pain point that people face, you know, every day. We're going in Red Hat style in the open source way. We're going to develop transparently in the open. This is how we do projects. We don't just drop code over the wall. We actually develop in the open. We work with our communities. It's a truly symbiotic relationship. People will be able to contribute in various ways, whether it's code contributions, whether it's extending the platform, whether it's documentation or helping end users. There'll be a variety of ways for you to get involved and to participate in this community. And we're looking forward to that. It's something that I've been doing personally for 15 years as far as community management and community development. So this is really an exciting project for me. And we're open for business. We already have four partners. We're looking for more. If you want to sign up, we're certainly welcome to hear from you. It would be great to start that relationship. When you look at where this fits in the context or, I guess, in the history of Manage IQ, where did we start from? Manage IQ was a relatively small startup. I guess they started in 2006, 2007. And they grew and they matured over time. And so I think it's important to note here that Manage IQ is not just some recent project that just started to solve a problem. It's something that we've been working on for almost eight years now. It's a fairly mature set of code that we're bringing to the table and that we're open and sourcing. It's something that should be pretty usable to the end user. It's not just starting from scratch here. We're starting with something that's a pretty good product to begin with. And so when we acquired Manage IQ, we added more resources to it and we enlarged the picture. Red Hat, I think, doubled the engineering team. We added more resources to help them integrate with the rest of Red Hat services and stuff. And so it became a larger team, a larger community within Red Hat. And now we're taking the next step because we need to make it bigger. We need to go take it to the next level and become the open source cloud management platform. And so when you look at Manage IQ.org and what we want to do by open sourcing it, we want to get more people involved. We want to provide the leading cloud management platform for the industry. That's our goal and we're looking to do that in conjunction with you. We have to do that with you. It can't just be Red Hat. It has to be us and everybody else that needs to solve this problem. And so we want it to be a truly community-driven project and that's our ultimate aim. And so I mentioned that we have four founding community members or partners. I've listed them here. And when you look at Booz Allen, Booz Allen is not traditionally known as an open source agent. But when you look at the things that they've been able to do on top of CloudForms and now with the Manage IQ community, I think it's going to shock a lot of people. I think it's going to surprise you to see the things that they've done. And I can't wait to talk about that in more depth when we have the full project release later. Serba you may not be familiar with. They do capacity management. So you can do capacity management with Manage IQ. But what Serba fills is an ability to more easily do capacity management and to automate it more easily. And so we're excited to have them on board because that also fills a very important gap in the cloud management picture. Chef, most of you are probably familiar with Chef. When you think about setting policies and logic around the cloud governance piece, configuration management and IT automation play a huge role in that. And so we're working with Chef to use Chef as a provider for configuration management services for the other services you want to deploy to help you automate the process. And so they're going to be a large player in the development. Incidentally, just because I live Chef here and no one else doesn't mean that we're not also going to be integrated with other configuration management partners. But Chef is the one that stepped up to the plate first. And then Auto Trader Group, they've been a longtime customer of both Manage IQ and Cloud Forms. And they bring their years of expertise and familiarity and will be a tremendous help for end users and people that want to get started and being instrumental in shaping the form of the community for the user. But I think the bottom line here is when we looked at who to partner with and who to go, you know, who to release with, we were looking for a diversity of members, a diversity of companies that bring their backgrounds to play and help us to address the market and that are most importantly invested in the success of the project because our success is their success. If we're successful, that means they're more successful as companies and becomes this whole symbiotic whole. But we expect this list to grow. These are just the first four. There were many more between now and the project launch and probably more after that because as we grow, we're going to be looking to extending the platform and we're going to be doing that with the help of developers and end users and individuals around the world. And I think as John Mark mentioned, you know, we really do want this community to grow so we're hoping, you know, by you guys coming to this session, you'll go out and sign up at ManageIQ.org that once the bits are available in a few weeks, you'll start to take advantage of them. And we really are looking for a wide variety of partners. So you see there on that previous slide that we've got SIs in there. We've got end users. We've got ISVs. We really do want a wide variety. So we do encourage you to, you know, take a look at the community and join up. And when you look at, you know, I showed on a previous slide about the growth of ManageIQ from a small company to a larger group within Red Hat to the larger community. Well, this sort of shows how we're going to market in conjunction with a variety of individuals and partners to sort of create like that fully featured cloud management platform so that we can really make this, you know, the best open source cloud management platform in the world. And so, you know, when we think of cloud management, I want you to think of a little bit of a history, the history of computing. When you look at all the major areas of computing that we've seen, there's been a sort of repeatable trend, a repeatable cycle. You know, in the Unix Wars, you had a lot of companies trying to entrap customers on their specific platform, and so they created little hooks to keep people tied in. And when you saw the client server model, we saw proprietary software companies creating proprietary software that basically kept people on their platform and prevented them from going somewhere else. And now with cloud computing, we're seeing kind of a similar dynamic. Lots of platforms emerging that try to keep people tied to their platform and try to prevent them from moving somewhere else. And when we say you're gateway to the open cloud, we really mean that because in our view, you should be able to choose what cloud platforms are using and where and when. It should be according to what you need at any given time, not what your vendor tells you, not what your provider tells you. It should be your choice. And that's what Red Hat is all about and what we've always been about. And that is the driving reason for us releasing this project and making this community because we want to give the choice to you because you should have the ability to create your own open hybrid clouds. And that's something that in our minds, no one else is really driving at at this point. And so that's very important to us and that's very important to me and that's why I'm involved in this project. So thank you all for coming. I appreciate it. Anything you want to add? I think we have time for a few questions. Do you have any questions? Feel free to step up to the mic. We're happy to answer them. Step up to the mic. Going once, going twice. Oh, okay. One of the questions that we've got really around sort of where you manage different environments from a platform perspective, so VMware, OpenStack, et cetera, is around security, auditing, logging. Is that a consideration in relation to manage IQ? Does it have a component that sort of looks after that? Yeah, so when you talk about security, I mean one of the things that you can set up inside or like around a lot of the policies on end users, what they're allowed to access, what resources they're allowed to consume and such. More on sort of management tracking of change, activity. Like change management type of stuff? Well, provision of a VM, logging from a log perspective, you know, accessing to specific environments. There's a lot of general things that you need to sort of consider around auditing and security as an end to end really. Is that something, Zav, you want to comment on? I mean there's a lot of pieces around security specifically. As far as, sorry. As far as, you know, log analysis itself, I mean it's not, we don't have that in the community right now, but that's a normal extension, I would say, something that we can do. But we do a lot of things in terms of tracking drift, for instance, between, you know, instances, what's inside, what's running, when was it running, and providing that information. So in terms of what's changing in the environment, that's being tracked, and we can actually not only track it, but take remediation action based on that, so the compliance piece. There's always, you know, more than can be done, but you know, there's that side. In terms of actions initiated through directly cloud managed IQ, we also track that and, you know, clearly identify those, you know, those information. So the tendency aspect of that is, you know, well available, and you can track this information. But, you know, as far as logging itself, like lock tracking, such as Splunk, for instance, I mean, we had customers actually who have done some integration with it through cloud forms. So, and take that information, that feed, to be able to take the remediation actions. Does that answer your question? And so on a broader level, you can think of the recent heart bleed example, the ability to turn off services that are running on unpatched, you know, platforms, for example, and be able to migrate to platforms that are, you know, patched and compliant with recent security upgrades. That's something that you can add to the logic into the cloud managed piece. You mentioned that you will work with the management components in the open stack. Is that the vision or is managed IQ already has some work going on with heat, Iran or Mistral and various other orchestration management components in open stack? Well, so one of the things that we did last year with what the commercial product was cloud forms and now we open source is managed IQ is we added integration points in last year between the managed IQ or cloud forms managed with platform into open stack. So as I said earlier, we're not trying to replace that, but we're already building those integration points. And what we'll do over time is Red Hat, you know, we have our own engineers that will continue to build more integration points because we've got engineers both in the open stack projects and on the managed IQ side, but then we also want to work with other people inside the community to help build out those integration points as well. Thank you. Sure. For the cloud architecture, I know there's a market product already. For example, IBM already have smart cloud structure with a similar thinking, which but already been launching the market. The user glance for image library leverage leverage hate for the pet management to workflow parole and leverage higher zone for the dashboard. So it's quite similar concept but launched the product already. So my question is how do you differentiate with the managed IQ for the future or with the existing market? I don't know about specific competition. I know there are a variety of cloud management platforms out there, but what's really different about us at least at this point is that the fact that we're open source and we're going to bring hybrid cloud management to a whole new class of users that have not had the ability to do that before. We're bringing it to a much larger group of people than the proprietary cloud management products can because we're free and open source. Do you see the managed IQ as a future product or just community based? What do you see? This is kind of interesting because we're kind of going backwards because we actually have the commercial product already today. So the commercial product is known as Red Hat Cloud Forms and that's what we acquired from the managed IQ company about a year and a half ago. Our tent has always been to open source it and now we're going through that process. You would be amazed at how challenging it is to actually take a proprietary product and kind of reverse engineer it to make it open source. It takes a lot of time to pull out the libraries, the licensing and all that kind of stuff to do it. That's what we're just a couple of weeks from happening. So what you'll have is managed IQ is that upstream project that is truly open source. Anyone in the community can access it, download it, integrate with it, participate inside the community and then finally, if someone wants to then buy a commercial support subscription from Red Hat that's what we commercialize into Red Hat Cloud Forms. I think we... Do we have time for one more question? Okay, sorry. I guess that'll have to be it. Thank you guys for coming. Thank you. Thank you so much. If you have any additional questions, John Mark and I would be happy to talk to you out in the hallway or whatnot. But thank you very much for coming.