 Okay, we're back here live, day two, coming down to an end here at the OpenStack Summit. This is Silicon Angles theCUBE, our flagship program. We go out to the events and extract a signal from the noise. Go to siliconangle.com for all the latest, latest reference point of tech innovation. Go to wikibon.org for free research. This is theCUBE. We're here to extract a signal. I'm John Furrier, the founder of Silicon Angles. I'm joined with my coach, Jeff Frick here. And our next guest is Adrian Ionel, who's the CEO of the hottest company here in OpenStack, and a lot of buzz, really making great use case and traction with customers around your business. Welcome to theCUBE. John, thank you so much. Pleasure to be here. So a lot of people buzz, hey, Miranda's here. She had an announcement with a red hat. We had Horton works on earlier. There's just a lot of demand for OpenStack right now. It's moved from a continually growing community. The 3,000 people here, they predict fall will be a bigger show. There's a lot of demand from enterprises and service providers for scale-out open source, and they need help. So talk about your vision around OpenStack today and how it will evolve in the future, and then some of the things that you guys are doing and why you're so successful. Well, thanks so much for the setup. We're incredibly excited to be here at this show. We have 340 engineers at Mirantis who are focused on making OpenStack customers successful day in, day out. And one of the things that has made us different from the very beginning is the focus on huge companies, huge platforms, people like WebEx, Dell Cloud, PayPal, the Gap, NASA. These are all our customers who have successfully deployed OpenStack in production. What's driving that is incredibly exciting. As companies are moving to innovate faster and faster, they realize that having a very agile, soft-to-define infrastructure is absolutely key to making their developers successful. And the only way to get that done today is using cloud technology. And as people look at cloud technology, they are very careful to not avoid the mistakes of the past and lock themselves into a proprietary architecture. So the reason why you see 3,000 people at the OpenStack conference today versus 1,500 people just six months ago is because people absolutely want this freedom to innovate, to build these open source-based platforms with richer new features that they can't get anywhere else and at the same time, avoid the lock-in. And that's what Mirantis is all about. We are about providing these very, very open platforms that people are not locked into and can serve as a platform for innovation. You know, Adrian, one of the things we were talking about yesterday and today, again, just reiterating the amazing, the greatness of OpenStack is that this vendor-neutral model and choice allow people to build fast. That's great. Look, check the boxes, golf clap, good job. The reality is this huge pressure and growth opportunities in the marketplace around moving to a modern infrastructure. And that's cloud, right? It's okay, that's good. But now, the enterprises are sitting there going, wait a minute, for the past 15 years, I've been cutting everyone down to the bone. I got a skeleton crew of IT. I'm outsourcing this to this company, that to that company, and now I have to invest all this money, billions of dollars into new stuff with a healthy expertise. So a big problem that no one's talking about, I want to get your opinion on this, because you're really filling a big void here, is there's not a lot of talent yet out there. And they're all legacy talents. So the personnel issues are huge. So deploying and managing and constructing these clouds is extremely problematic in that regard. So can you comment on one, do you believe what I just said? Do you agree with it? And what are some of the things in the marketplace that you're seeing? Yeah, I think you're absolutely right on. And we have exactly the answer to the problem that you just described. And we do it in three different ways. One is, Mirantis has always provided, in addition to our professional services and to our technology, very well respected education program. So we have a bootcamp for OpenStack that's running multiple times a month that has seen huge adoption with students and enterprises worldwide. So we are doing whatever we can to share our own knowledge, our own expertise with a broader community and empower these enterprises to adopt OpenStack. That's one thing we do. The second thing that we do is we have released and open sourced our fuel automation platform, which is kind of the collective DNA and intellectual property that Mirantis has developed over the last three years. We just open sourced it and that allows people to deploy these OpenStack clouds using fuel much, much faster than previously before. So a lot of expertise. It's like a development kit. It's more than a development kit. It is a fully automated platform where you can build a cloud push button. It gets guys to develop fast and get to play with it. Is that what it is? It gets guys to essentially configure a cloud like you'd configure a car on the web and with a few clicks, stand up a reference architecture on a large scale infrastructure in your data center. And it's been proven out in production today with people like PayPal who have 60 some applications using the OpenStack clouds that we've built with fuel in production today. So fuels like chief architects dream. They get to play with some stuff as well as kind of lay out what preferred architecture they might want to move to. Is that what you're kind of saying? Exactly. So imagine a predefined set of fully automated reference architectures that have been fully tested against each other that you can take and deploy but tailor to your own needs. Great Adrian, hold on. I got this question from the Twitter feed. So thanks everyone to tweet me if you don't want to be publicly seen I'm getting DM so this was a DM this person didn't want to be named synonymous source. What features can users get on OpenStack that they can't get on Amazon? Well, there is one very important feature that they can get on OpenStack that they cannot get on Amazon. They can build their own services. So you can take what OpenStack already provides and for example, you can build a very advanced guaranteed SLA Elastic Block Service that will be much better than on Amazon because you can go into the code, you can choose your hardware, you can choose your storage architecture and you can build exactly what you want. You don't have that flexibility on Amazon. This is just one example. Great example. Anymore? I think that's good enough for now. That's good enough for now. If you want more than one example you've got to go to regular Twitter instead of a direct message and then they can get what they want. We'll earn the next question. We'll earn the next. But Adrian, I have a question for you on the decision behind open sourcing fuel. If it was your own proprietary IP. And then the impact of that decision on how the companies evolved changed grown. Right. It was a hugely debated topic inside Mirantis. I mean, we had some pillow fights over this, right? Should we open sources? Should we not open sources? Because you're absolutely right. A lot of our engineers spend an enormous amount of time building fuel. But in the end, we decided that open sourcing it is absolutely the right thing to do. It's the spirit of the OpenStack community. And we think that ultimately it's going to drive much more adoption for OpenStack and for our technology and for our services around OpenStack. And that's been the same guiding principle for us behind open sourcing Savanna. I think the previous speaker here that you had from Hortonworks spoke about Savanna, which is a project that we at Mirantis started. Our engineers created Savanna. And then we got Red Hat and Hortonworks behind it. And we open sourced it as well. And did it, and did what you expect to happen happen? Did it accelerate the adoption? Did it accelerate your own customer acquisition and the sales of your systems? Well, I can tell you that for fuel we've had about 900 registrations in the past three weeks. A lot of these customers are experimental, but many of these customers are also very, very serious adopters. So it's a bit too early to tell how successful fuel will be long term. But the initial take up, the initial interest level that we have seen has been terrific. Moreover, fuel is not a closed platform. It's an open platform that other partners can develop to. And they've already started to develop. So we've had some of the leading players in the SDN community approach us and commit to develop against fuel. We had some of the leading server players as well approach us. So we think that fuel can become this unifying open platform that makes open stack much easier to deploy and manage than it's been previously possible. So begs the question, as a technology company CEO, you guys are, you're participating in open stack, you're participating in the open community. But surely there's some code that's being written. Do you kind of philosophically say we're all in the open source and pretty much everything we're going to build is going to go down that path for all the benefits that we see that come. And there's going to be no proprietary stuff that you build, or is there still going to be maybe some stuff that you're going to build that you're going to keep as your own? I can imagine some of the CEOs watching are going, wow, this is a really interesting challenge that I never faced before. We built what we built and we would layer it on other stuff, but it was ours and you're saying and a lot of what we're hearing here is you can actually accelerate the growth of other parts of your business by really adopting and embracing and jumping in and putting your code out there in open source. So is it all in or can you be partially in or are you 50% in for new software that's developed, new tools that you guys develop? Well, right now we have open sourced everything that we've developed. I can predict the future, so I don't want to say that this will be always just open source but for the foreseeable future this is the path that we are taking. Wow, very innovative. So what worries you about OpenStack in terms of what's still fragile and in addition can you comment about some of the white spaces that are emerging that developers are going to have an opportunity to sink their teeth into? All right, so I think the most important thing for us as a community to get done around OpenStack is to make customers successful in production at scale. That's the one thing we have to get done. We have quite a few customers that have reached that point but we need many, many more to actually prove the robustness and the capability of the platform and help customers actually get business benefit out of it. That's very, very important. So what worries me is that whatever commitments we make to customers we live up to them, we deliver with exceptional quality and that they leave this OpenStack journey with a very, very positive feeling about the decisions that they've made. In terms of the white spaces these are the areas that we already started to work on that are application services on top of OpenStack. And what you've seen us do with Savanna is just the beginning. What you see emerging in the open source infrastructure world is a series of islands that have become quite successful. So you see the Hadoop community, you see the MongoDB community, you've seen the MySQL community, you're seeing now the OpenStack community. All these communities contribute to the new infrastructure for the enterprise. What you will see happening is that some of these communities will start to build relationships with each other, will start to build APIs with each other so that an enterprise can much more easily manage their entire open source portfolio, their entire open source infrastructure in some form of a unified control plane. And we believe that OpenStack can be that unifying control plane that ties other projects together and make them all work. Yeah, I think that's a very viable plan. I think OpenStack is a warm blanket to an enterprise to give them some comfort, some use of certification, they use to stability. With that, my question would be, what advice would you share with a CIO or a chief architect or a head enterprise person, and what they need to do now to get into the open source world in terms of taking this path whether it's OpenStack and beyond. And we heard from Hortonworks earlier about Hadoop. A lot of enterprises aren't prepared for open source. Now, so you guys are helping a lot of large scale customers out, but still this is the new normal open source scale out. So what can they do? Right. So first I want to set the record straight that open source of today is not open source of 10 years ago. So today, if you're looking at the OpenStack situation, you can get a very product like experience using a company such as Mirantis where it's a complete solution. It works out of the box. It's very robust. It's extremely well supported. So it's not a science experiment. But, having said that, most of our customers take a very, very rational, well thought out path to adopt open source. They typically start with what I would call a production grade pilot. They find a couple of very, very good use cases in their enterprise where OpenStack makes sense and they work with us to actually prove it out. To build it, to install it, to put some real application workloads on top of it and demonstrates that it works in production. And that's a very sensible path that I think customers can take to build their OpenStack and open source expertise. So that's what I recommend they do. Yeah, I would agree. I mean, it's a great way to get, kick the tires, but it's still, you need to evaluate and we're hearing it across the board. So now the next question I want to ask more philosophical question. So lean back, relax. Take your CEO hat off for a minute and just comment on, we talked about DevOps is now mindset everyone's talking about, which is cool. But the word infrastructure as code is a word that's now hitting the mainstream and that means something to a lot of different people. So I want you to tell us what, in your words, what infrastructure as code is and how would you describe that phenomenon for folks that aren't used to hearing that are understanding this new modern error? Well, to me, that means that an application can just self provision the resources it needs to run. So it's essentially computers asking for more computing resources is the idea of the completely soft to define data center where if I am an application and I know that I'm hitting the max capacity and so let's say I'm a search application on eBay and I see my response times going up for users and users being unhappy that I can automatically just ask for more computer resources and the infrastructure will give me those resources in on demand and when I don't need them anymore I can just absolutely release it. And when I ask for those resources I'm gonna get the right resources with the right security constraints with the right performance characteristics with the right SLA guarantees with the right economics fully automatically without having to have engineers work for weeks to make it happen. It will just happen in seconds. To me, that's infrastructure as a code. And that is a fundamental departure from the old way. Static provisioning, you know, switch his routers. There's some significant innovation needs to happen. Can you point to the key things going on now that are really propelling that mission? Sure. I mean, one of our largest customers today the reason they're moving to OpenStack into the fully software defined data center away from the proprietary software they have in place today is in order to reduce what they call the lifetime to site from 12 weeks down to 15 minutes. It takes them today, 12 weeks from the moment a developer has a feature ready to go until that feature is up and running onto the site. They will- That's not agile. That's not agile, exactly. 15 minutes. 12 days. And they will cut it down. They will cut that down to 15 minutes. That is the declared goal of the OpenStack initiative. And we will make it happen. By summer, it will be in place. And that's how companies like Facebook operate, right? I mean, I think, you know, we've been commenting and David Floyer was here from Wikibon, our analyst. And, you know, we were, you know, scale up commercial software is the thing in the past. And now, you know, with innovation and scale out open source, these things are in place. So, on the reality front, just share with the folks out there who are watching and might watch us on demand the reality of that vision because it's happening. And where are we in that quest to that programmatic, that software as code, infrastructure as code and vision? It's totally doable today. It takes some serious effort. It's not completely out of the box. There are some automation layers that you need to put in place on top of OpenStack to enable it, but it's absolutely doable. And it is no longer months, the project that takes years to complete. It's something that people can absorb in months and can actually make successful. Adrien, you're a great guest. I was asked to tell you, you're a tech athlete now, CEO of a company. Obviously, you've got the chops. It's a talk shop here in theCUBE. We appreciate it. Your company's doing extremely well. Congratulations. A lot of people buzzing about you guys. Just what's going on in your mind is the CEO. You're growing, you have growing pains. You guys are growing really fast. Growth is, you know, some companies can die by growth. What's your goals for next year and how are you going to manage the rocket ship? Well, my most important goal for this year and next year is to make sure that we deliver with exceptional quality for all customers. And I am perfectly prepared to sacrifice growth or speed of growth in order to make sure that the customers that we do have and that we do win are very, very successful with what we have promised we will do. And big part of the answer to that is automation. That's why we created fuel. That's why we open sourced fuel to make more and more of this process fully automated. And the other part is the company culture, right? The people that we hire at Mirantis, we hired 240 engineers over the last two years at Mirantis, we integrated them, we trained them, they're all productive. And to make sure that everyone shares these value about delivering an exceptional customer experience. Because if we make our customers successful, we will just grow from here. And a very interesting data point about Mirantis, you know, up until last week we had no sales people in the company whatsoever. So all these growth, all these customers, we actually won through just exceptional quality delivery and word of mouth. Well, it's working, you guys, good buzz here in theCUBE, extracting the signal from the noise. A lot of signal here at this show. Congratulations for your success. Adrienne with Mirantis, CEO of the company here at OpenStack. This is SiliconANGLE's exclusive coverage. Day two, coming to an end with our wrap up shortly after this break, we're going to get day three tomorrow. So stay tuned on siliconangle.com. We'll be right back with our day two wrap up after this short break.