>> Voiceover: Live from Boston, Massachusettts, it's the Cube covering the Red Hat summit 2017. Brought to you by Red Hat. >> Welcome back to the Cube's coverage of the Red Hat Summit here in Boston, Massachusetts. I'm your host Rebecca Knight, along with my cohost Stu Miniman. We are joined by Radesh Balakrishnan. He is the general manager at openstack.com. Thank you so much for joining us, Radesh. >> My pleasure. >> I want to hear a status report. Where are we with openstack? What does it look like? Before the cameras were rolling you were saying we're alive and well, we're better than that, we're thriving. Lay it out for us. >> Yeah you could look at it from three perspectives. First is, how are we doing on number of production deployments. So just from the red hat lens itself, we have over 500 customers across the globe, spanning across multiple verticals, be it financial, telco, education, research and development, academia, etc. >> Stu: Put a point on that, production you said. >> Production customers. >> That doesn't include all the tests, you know that kind of stuff. >> That's right. >> Please. >> So that's a healthy spot to be in. The second lens to bring in from an openstack health perspective is how is the partner ecosystem shaping up? This is a space where there have been probably misreading of some of the moves that have been happening here. From our perspective, what has happened is a very healthy consolidation and standardization of the different place that needs to happen in the space. If you look at the openstack ecosystem that red hat has been able to pull through, we have certified solutions across compute, storage, networking, as well as ISP solutions that today customers can deploy with peace of mind. That's another indication of the fact that the ecosystem is maturing as well. A dimension along which that I'm personally excited about the ecosystem maturing is the fact that managed service providers are also taking on openstack and delivering solutions on top of it. For example, rackspace, IBM, Cisco metacloud, etc. All of them have built their manage service offering based on their openstack platform. >> So let's stay big picture here and look at the industry five years down the road, you're talking about it maturing, consolidation a natural part of that. What do you see, as I said again, big picture? >> I think the largest picture here is that hybrid cloud has become the norm. Five years ago, is cloud going to be there, real, is it secure, all of those questions have been answered. Multi cloud has become a real possibility. Hybrid cloud is going to be the normed implementation. The role openstack has is two fold in that context. One is, clearly as a private cloud implementation for enterprises wanting lack of vendor locking when it comes to implementing a cloud infrastructure. The second perspective is how can you stitch together multiple clouds using an API at the infrastructure layer that openstack can provide. That's the value that openstack is providing. >> Radesh, I want to dig into that a little bit because there was a vision of openstack, we're going to have, it will be the open cloud, we can build lots of clouds on that. You mentioned a few service providers. Of course rackspace was there since the early days. Great to see IBM, Cisco still doing some even though Cisco kind of killed the intercloud piece. But when I heard multi cloud talked about this week it is AWS, big partnership announcement with open shift. Google, Microsoft Azure, hybrid pieces of that and stitches those together, so I wonder, how does openstack in general and specifically the red hat solution stitch together openstack components with some of those other public cloud components? Because that seemed to be a gap in what openstack did itself. >> Yeah, so from our perspective, if you think it as a ratage, 80% of the focus is on private cloud. The remaining 20% is on think about security, privacy, compliance requirements dictating country specific public cloud requirements. Say Servpro in Brazil, or UK Cloud which provides services for Garmin Cloud, or Swisscom, a standing up Swiss cloud. That's kind of the mix and match of it. The context that I was worrying about was even when you have a private cloud, you can use the API that openstack provides to manipulate the resources that are on AWS, Google, Azure, etc. That's where I see the future shaping up. >> Radesh, we're going to be covering openstack next week, we'll see lots of red hatters there, I know. My take is that we need to reset expectations a little bit. I think red hat's been pretty consistent with what they're doing, but many people are unclear. We talked about certain players pulling back or partially or shifting what they're working on. Maybe I'd like to see your viewpoint on that as to a little bit of overblown expectations, certain players that might've been trying to push certain agendas vs. where red hat has seen things go and you want to see the community go forward. >> I think the first perspective to take here is that openstack is not the destination in itself. Openstack is an ingredient in the destination that customers want to get to. I talked a little bit about the open hybrid cloud being the end destination that customers want to get to. The usual layer cake of, there's the infrastructure layer, there's the application layer and there's the management layer. You want to get to an infrastructure layer that's open and openstack provides that one. Now, what has happened in the last two years is the focus around digital transformation has brought the shining light on the application layer square and center. In other words, developers are the kingmakers. In other words, the speed from thought to executing code is what is going to make or break a business. Which is why containers and derops, etc. is where the action is. But that doesn't preclude the need to have an adjoined infrastructure at the bottom layer. Rather than reinvent the need to do plumbing and compute and storage and networking level, you build on top of openstack so that you have open shift on top of openstack, like a Waru or a FICO doing it so that you get the fungible infrastructure at the bottom and then you get the derops implementation running on top of that. That's what we are seeing as the path to future. >> Yeah, I think that's a great point because it felt like that was a big piece missing at openstack is yeah, we've talked about containers there for a couple years but it's not about the application. I've heard lots of discussion about applications, application modernization, all the middle ware pieces. The core to many of the things that you guys are doing at red hat here and do you see, expect us to talk a lot about that at openstack summit next week? As things like Kubernetes and the container ecosystem matures, will that pull people away from some of the core activities? Because the base pieces of openstack are set in a lot of ways and sure, there's development work that needs to continue, but we've gotten some of the base pieces working well. People have been worried about some of the scope creep and the big tent and everything that falls out. How do you reconcile some of those pieces? >> Right, so I think it's a given that the world of containers and the world of openstack are coming together. Now, the confusion stems from the fact that some people are taking the view that containers are going to eliminate the need for openstack itself. The lens to bring to the picture is, how can the customer graduate from what they have to what they want to get to? If you come from that perspective, then first is to bring rationalization of existing resources by bringing in openstack and infrastructure layer. Bring in culture change through derops, through open shift, and then when it comes to implementing the full solution, you run open shift on top of openstack. That's the ideal that we get to see. Now, is every customer going to go through these steps? Maybe not, but the majority of the customer if you look at the customers who are embarking on transmuneration over the next three to five years, they're going to be in that bucket is my view. >> Can we go back to what you were saying about the beginning, it begins with the infrastructure, then the culture shift. Unpack that a little bit for us. What do you mean by that and what are you saying in terms of how that will lead to the transformation that companies want to get to? >> Right, so all I'm saying is technology is the easy part. It's down to are we fundamentally rewiring the way in which we are thinking about applications? The way in which we are writing the applications, the way in which we are delivering the applications to an entirely potentially new set of customers and partners? >> Last piece I want to ask you about is the openstack community. Some shifts as to who's contributing, talk to us a little bit about red hat's contribution, the really health of the various projects. Where you see good stuff coming out and anything as you look forward to next week without giving away what announcements you have. What should the community be excited about going into the summit? >> The openstack summits are always exciting because it's twice a year, family reunion for the whole community to come together. As a community, we made tremendous journey in identifying new use cases, such as NFE, delivering against that, etc. The other dimension is that, back to the point about rationalization etc., now there is clarity around the role of openstack itself in an infrastructure. The journey ahead is to make sure that containers and openstack can come together in a seamless manner. Secondly, in the hybrid cloud adoption model, openstack engineering will provide the API stability across the multi cloud infrastructure. Those are the areas I think all the discussions are going to be centered around next week. >> Great, Radesh thank you so much for your time. It's always a pleasure to sit down with you. >> Thank you very much. >> I'm Rebecca Knight for Stu Miniman, we'll back with one last session from the Red Hat Summit 2017. (upbeat music)