 for the party, so let's get this started. I'm going to tell you a little bit about StackOps. I don't know if we were the first open stack distribution in town. I can tell you that our first effort was in Bexar. So we've been in the arena for a while, although we are based in Europe, where things are kind of flat around the open stack. We do have some over 34,000 downloads of our distribution. It was Bexar, Cactus, and all that. We have a lot of deployments worldwide, and all this vision I'm going to tell you about comes directly from all the feedback we get from our users. So we're kind of one of the useful suspects in these kind of in the summits. You can find us at any time. We've also been speaking in different events worldwide. This is one of our partners made this event in Sao Paolo. We've spoken in Israel, in the States, and so everywhere. So we kind of also evangelize people on the use of open stack. And we get also the feedback, direct feedback, after our talk. And it's not like this event where we talk with open stack guys, so the feedback is usually positive. We also have some bad feedback as well from some people at some point. Okay, this is what we're going to cover. This is not a technical talk, so I'm going to just tell you what you already know about the open stack evolution. I'm going to give you a couple of hints on what we see. What is the goal of open stack in the coming year? What should be the goal? Why the ecosystem is relevant? What is this of the foundational tool which gives title to this session? And of course, our vision on how that is going to be, how that is taking place. So there is no doubt that open stack has evolved to a level of maturity no matter what Garner says. I missed the guy from Garner in the analyst panel, so. But these guys, I don't think they understand properly what open stack is. What I can tell you is that there is three letters ago in Cactus, there was a deployment called Mercado Libre who had a session before that had 400 physical servers running in production with Cactus, right? You know, if you're telling that it's immature, you're kind of insulting these guys, right? And they are brilliant. So they made it work. Maturity, it's something that you need to define. So we're going to talk about stability. Open stack is pretty stable. We have a few telcos working with open stack. In our case, we have Telefonica, the largest telco in the world, working with open stack in some services. So I guess it's stable because these guys demand a certain level of stability, OK? You know, I've been selling open stack for two years already. And I have to change my speech every six months. So initially it was like, I would challenge people, ah, that feature might not be important. You know, how often are you going to use that? Right now, I challenge them to find a tool that can do what open stack can do. You know, with no risk of losing that customer, it's like, hey, you go tell me who's doing this better than open stack. And they might find it, but then in six months' time, we're going to be there, all right? What's this about the data center colonization? This is the next challenge we have, OK? Prior to IT, I started biology. And there's some things I learned, some things I, most of the things I forgot, right? Then I had to get a real job and I joined IT. But I kept this with me because this applies to IT, to biology, and to other businesses. This is the principle of the theory for evolution of a species, stated by Darwin a long time ago. And it says that it is the ones who adapt better who will survive. When you look at the species taxonomy, the family that is best in doing this, in adapting to different ecosystems, is not the strongest, it's not the mammals, it's not the reptiles, it's the insects. So I'm sorry to say that open stack is the insect family and all the companies and all the people working on that are kind of insects. Sorry, but how is this happening? This data center colonization is based on the ecosystem, the different companies, the different insects that build open stack. There are different strategies, different locations, there are different targets, there are different businesses, different sectors, different industries that can run open stack. So there are many different ways of having open stack set up. So let's put a little bit of perspective into that. First of all, I want to clarify. I understand there are three different business strategies to deploy open stack. I'm talking about deployment only, to deploy open stack. You have the toolkit. Guys who have the time, the resources, the capabilities to get the open stack vanilla and start working on that and build a whole lot of things on top. Mercado Live is one of the examples, but there are some other people that actually don't need any distributions or any other products around open stack. So the amount of services you have to put on top, and you can measure that in time, in resources, or in consultancy from any of the companies around here, is, I don't know, 80%, something like that. Then you have the distros. I mean, we were the first, we led the way, and there are other companies doing that, and on the go followed, and then Red Hat and Rock Space and all the big guys are doing distributions as well, to help you deploy with their own reference architectures, helps you deploy open stack in an easier way. But it's still, you have a distro, but you don't have a solution or a real deployment. You need to work on that as well. You need to invest on integrating that into your specific, or the specific solution, building around that the specific solution you want to have. And then there's the product, which takes you one step forward, because it does already integrate some other components that are not specifically from open stack. With that, you still have to add some consultancy to that. So there's no magic here. There is no, I have open stack, I put it there, and everything works, okay? There's some work to do, prior to deploying open stack, and after you deploy open stack as well. That will condition also the adoption of open stack. And there are five different factors in which you're gonna be moving to find what is the adoption curve of open stack worldwide. So you have the cultural, legal, technology, business, and financial. Some of them are more flexible than others, right? Legal is something you're not gonna change in the short term. Financial is something you're not gonna change. Well, you have flexibility, but it's just in one way, all right? So you're not gonna be, the financial, the budget your company or your customer has is what it is, and then you cannot exceed that much, right? There are cultural factors as well. When you look at, for instance, the way in Europe, we like to control and have a better planning because we're more conservative if you want to look at that way. Then, for instance, in the US or Latin America, that will affect the adoption curve. This is mainly the reason why Europe is lacking in the open stack or the cloud computing in general adoption. Then there are different ways of doing business as well. You know, it's kind of a little, you have to go through when you want to make businesses in different parts of the world. I did it in Japan. I mean, you need to meet people there. You need to work your lead. It's not that, it's also conservative in that way. In Latin America, it might be easier just to get something tested or get something deployed. And also the technology, you know, you need to get people knowing the technology you're implementing also in your open stack clouds. So we're gonna move with these two variables to meet all those five different factors. One of them is the geographic proximity of the open stack vendor or the open stack cloud guy. Local does matter. You know, when you're doing business in some places, you need to see face-to-face people. So big clients like the Amazon cloud does not have the same success in some places because they don't have a face. In Europe, in Latin America, you need a face. You need people to go and visit your client if you want a big investment or a large deployment. You most likely have to go down there, have to go there and start visiting over. So geographically, we'll help you manage, for instance, the business, cultural and legal factors, okay? How we cover that in our specific way of putting that strategy into real life. We have partners, for instance, US, we have Microtech who will actually drive all the leads we get from the US because they're here, they know how to make business here. Same as in China, we're not gonna go all the way to China to make business there, not yet. We might do that in the long term. We get stack scale deploying, we get dual-tech in Brazil, Chile. So we get a bunch of partners that will get open stack close to you, right? The other factor is about flexibility. And as I said, it's flexibility, but you need to put that into specific, well, it's not flexibility in two ways, right? This is just in one way. What I mean with the flexibility is that you're gonna have to adapt to the existing technologies your customer has. So for instance, if they want to use some kind of storage that they have probably invested some money on already, you need to give them the choice to use that storage. You don't need to force them to use whatever you're using in your distribution or in your open stack deployment. You need to have solutions to match their specific technology. So in terms of storage, in terms of networking, monitoring or billing systems or hardware, right? The hardware bit, everybody understood that. But then that flexibility, when you're talking about reference architecture, it's not that clear for most of the players around. So with that, you're also gonna cover the rest of the factors and you're gonna be able to move on those five factors. Okay? What's this about the foundational tool? There is one more step, and we're ready to take that one more step to the graphic we saw before about the three different ways of deploying. There are four different ways to deploy and operate your open stack cloud. So you get the three we talked about and then you get the open stack on steroids or on vitamins, whatever you want to call it. This is the way we envision the foundational tool, the open stack of the future. It's the way you're gonna have all these choices we were talking about before. You're gonna give those choices to your customers, right? So they're gonna be selecting and configuring easily how their open stack cloud is gonna look like. What are they gonna use in their open stack cloud and the choice to have different flavors of open stack clouds is also something that will be of interest to them. They might have some storage solution with a quality of service, very low level, very cheap for specific services. They might have some other storage solutions with a higher quality of service backups and all that for high end services, all right? So the open stack on vitamins is just a configurator. You give your customers in which they are able to select one of the solutions that it's integrated in your whole panel. In order to have that, you need to keep in mind three things. You're gonna tell you don't make me spend. Use what I have. I already bought a NetApp filer and I spent $2,000 there. So I don't want to use whatever, right? Or I have my Dell hardware that I just bought or I have my Hyper-V hypervisor, which I use, or my VMware, which is, I'm fine with that. I'm fine paying that. So reutilize whatever these guys are using, you need to be able to make an open stack cloud out of that. Don't make me think. I mean, your guys probably don't care if it's open stack or not, right? They want it simple. They probably don't want to learn Chef, or sorry, Chef. If they know Chef, they might deploy with Chef, but if they don't, they don't want to invest in learning Chef or Puppet or Juju or whatever tool that deploys open stack. They want it simple. They want to have their cloud. Their business is not deploying open stack. Their business is whatever is running on top, okay? You need to keep that in mind. And don't make me change my business model. So basically, I want to do this. I've been doing this for years. I don't really want to start rethinking whatever you're suggesting, right? I'm buying off a cloud from you. I'm not buying off consultancy on my business stuff. If I do, well, you might also have that integrated into your full offer, but ideally, these guys want a cloud, right? And they're going to be running their business as they are. And very important, it needs to be non-disruptive. Any change you make in a data center needs to be non-disruptive for the businesses running on those data center and those servers. So they're not going to be a change. They're going to be a lower performance. It's not going to be a lower accessibility. It just needs to be as it is or better. If you want to change it, it needs to be better, okay? You just need to make sure you have that in place. Okay, how do we envision this? We have the open stack environments. We call the StackOps Enterprise Edition, which comes with a Metal as a Service solution. Probably you might be liking to use that, but you can integrate also. This is what we call the StackOps portal. It's a web desktop that allows you to integrate different solutions, different services that your system administers are going to use to manage their open stack cloud. It's not restricted to open stack. It extends to open stack. So if you want to add a monitoring system, you can add it easily as a plugin. If you want to add a reporting tool, you can add it easily. If you want to add your NetApp Manager, you can add it easily or whatever kind of manager you want to have for your storage. You can also add it easily here. So this is the way your system admin is going to have all the tools to manage the services in the data center within the same portal. If you don't want to use the head manager for deploying an open stack, we'll find with that as well. StackOps portal works on any open stack, right? So if you want to use the Succitive Configurator, you can use that. Or if you want to use Uge or Chef or Puppet, you can build plugins to that. Keep in mind that this tool, it helps you to deploy open stack, but deployment is not important anymore. I mean, the goal is to have open stack running in your data center for 10 years. So if you're having a deployment done in five days or in one month, when you compare it to the time, open stack is going to stay in your data center, it is just not relevant, all right? So you deploy it the way you want, then you need to find the right tools to manage your different services running on open stack or around open stack, or however you want to look at it, okay? So this is one of the tools that we'll actually, what we call the foundational tool of the data center. We want to have open stack as the plusc of the data center, plusc serves to do anything on the server, open stack is empowered to do anything you can think of in the data center, okay? So this is it. I would like to take questions that you have, ease of use, ease of access, integrations, you can build new applications, this is an SDK, you can build things on top, or you can integrate existing web applications or you can create them, it's all built in extension JavaScript. This is the way we think open stack will evolve in the future, being the center, the corner store of your data center. Right, so thank you very much. Any questions I can take now? Yes, we have our own components called the head manager that actually has, as long as you turn on your servers in the same network, it sends an agent, discovers the capacity of that, and you can add those into an open stack zone. You can manage with the head manager different open stack zones with different architectures, so it's actually a multi-zone, multi-tenant component, and it takes 15 minutes just to get a new zone deployed with the servers, it has a pool of servers that you allocate to one of the zones you have just created and it's up within minutes, and you also have high availability capabilities with those. You can configure the way to replace the broken server fairly easily. It's not open source, it's not open source, yeah. Questions, yes? That's it, that's it. That's the goal is to administer anything you have, anything you have, ideally, you're gonna be able to manage different open stack clouds with this, right? You're gonna be able to manage other things from here, so the goal is to have open stack base, it's all driven by Keystone, but again, you decide what you want to put inside here. Okay, thank you.