>> Announcer: Live from Vancouver, Canada, it's theCUBE covering OpenStack Summit North America 2018, brought to you by Red Hat, The OpenStack Foundation, and its ecosystem partners. >> Welcome back to theCUBE's coverage of OpenStack Summit 2018 in beautiful Vancouver, British Columbia. It's Victoria Day, but we're working. So for John Troyer, I'm Stu Miniman. Happy to welcome back to the program, we've got Tim Burke who's the Vice President of Infrastructure and Cloud Engineering with Red Hat, and fresh off the keynote stage we have Mark McLoughlin who's the Senior Director of Engineering for OpenStack, also with Red Hat. Gentleman, thank you so much for joining us. >> Our pleasure, thank you. >> Thank you. All right, so Mark, I'll start with you. Keynote stage, you had a good discussion about, we were talking about open source, talking about community, is the themes that we heard at Red Hat Summit last weekend and again here at OpenStack. It's a nice couple of years in a row we've had the back-to-back of those two shows, so give us a little bit encapsulation of that message. >> Sure, I mean the key message of the keynote, really, was talking about the overlapping missions between the OpenStack and Kubernetes and really kind of showing how they come together for our customers and for users generally in terms of tackling that kind of broad, open infrastructure challenge of trying to give businesses the opportunity to be free from the infrastructure providers in terms of being able to switch between infrastructure providers and also OpenStack in terms of its role offering kind of on-premise infrastructure as an alternative to the public cloud. >> Yeah, Tim, I want to get your viewpoint on some things. It's interesting, we talk about we're at the OpenStack show but we're talking about containers, we're talking about edge computing. I think about one of the other foundations, The Linux Foundation does way more than Linux these days. They're doing all the cloud native things. Reminds me a lot of Red Hat themselves, broad spectrum of products. Sometimes it can almost get a little bit overwhelming for most people to say, "Oh my god, "there's so many projects, there's so many products. "How do you help me get to where I need to go "and where I need to go tomorrow?" What are you hearing from customers? How do you manage that? >> I think a lot of this mirrors Red Hat Enterprise Linux, and back when we started it was the day of the Unix wars, right? And in the early days of Linux it was this big challenge of getting your graphics drivers and putting all these pieces together, right? And now today it's more about broader infrastructure orchestration. And you see Mark Collier, for example, from The OpenStack Foundation started today showing a list of 30 different components that you have to piece together. And really, I think that that's what Red Hat focuses on, is two things. It's one, is where do we want to take the technology tomorrow through our open source fund, ranging from Linux to OpenStack and Ceph Filesystems, for example. But it's not just that. It's how do you get these pieces to work together? And I think that that's something that hasn't traditionally been the strength of the open source community because they may stick into these silos of operation. And I think that Red Hat's focus and strength right now is to do what we did for Red Hat Enterprise Linux in the OpenStack space by pulling all of these pieces together in a consumable and supported manner. >> Yeah, it's funny you mention getting graphics cards in. Come on, with the Queen's announcement we now have the virtual GPU support, so it feels like, but you know what, we've come so far yet. We're doing some of the same things over again. What are you hearing that's just massively different about kind of the state of open source today? And we just had one of your customers on talking about their digital transformation. >> I think what's really changed over the years in open source is I think it started out, honestly, as a clone. It was like can we compete with the likes of Solaris, right? And so it was, I'd call it catch up for innovation. Now you look at open source. It's not catching up, it's leading all the innovation today whether it's all the major public clouds are based on open source technologies. When we started open source was unproven and many customers were skeptical of consuming it. Now you're seeing customers, governments, all sorts of different businesses demanding open source because they want choice, they don't want to be locked into any one vendor, and they want to be able to work collaboratively to harness the power. And I think that collective collaborative model has really pretty proven its effectiveness. >> Mark, I wanted to talk a little bit about OpenStack itself. I think last year at OpenStack Summit there was a lot of talk. People seemed to be a little bit confused or at least there was a lot of interesting architectural conversations, containers on top, containers on the bottom, what sits on the bare metal. This year both at Red Hat Summit and here and even in the industry at large I think a lot of that conversation has clarified. There's the (laughs) application layer and there's an infrastructure layer which does very hard things that the application layer does not have to worry about. How are you looking at OpenStack as a citizen of the industry and of the Stack connections with other open source and taking care of that infrastructure piece in 2018, right, which is, we're pretty far from where we started. >> No, great points. To highlight those architectural discussions and really trying to figure out the kind of layering there obviously kind of approach OpenStack as kind of the best tool for managing your infrastructure, getting your infrastructure under control, making it scalable, making it automatable, and then building an application platform on top of that. I may have confused the architectural discussion a little bit this morning with the keynote because what we actually showed in the keynote was on the rack on stage we had an OpenStack cloud running on bare metal and then we would end deploying Kubernetes. Our open shift distribution, we were deploying that also on bare metal alongside OpenStack. Whereas I think often people would assume if you're going to do Kubernetes on OpenStack you're going to do it in virtual machines that are managed by OpenStack. But we were actually showing how you can use OpenStack to manage the bare metal, that you're actually running Kubernetes directly on the bare metal but that there's still integration between Kubernetes and OpenStack when they're side by side. So maybe confused the architectural discussion a little bit more but I think it's really trying to highlight that that assumption of running Kubernetes inside virtual machines isn't necessary. >> You used one of my favorite tools in your keynote. You used Venn diagrams because it is not a thing over here and a thing over here. There's overlap and there's decisions that you'll make, and lots of customers want a platform that will guide them down that path. And they also, oh wait, but I have this custom thing that I need to do. What's the biggest problem we have in IT, is it's not standardized and nothing ever gets thrown away. It's like I want to run my docker image on a z/VM in a mainframe. Oh, Walmart does that, but they also have an OpenStack deployment. So (laughs) you hear all of these discussions out there where it's like wait, is this, you know, (laughs) is this the main thing? Is this modified? What sits on what and where? So it's and, it seems to be, and there's a lot of choices. >> Absolutely, and I think one of the really, you know, one of the really interesting things when you're working in this space is you realize that customers are making really long-term strategic decisions appear. The example I used today was BBVA, and they realized that they needed to kind of keep up with a fast-changing market and they needed an internal platform to allow them to do that. And this is about them making a long-term decision about how they were going to build that platform into the, it's a really kind of long-term and basing their business on that and its future. So that's, it's kind of humbling in terms of having that responsibility of making that work. >> Yeah, Tim, maybe we can get your comments on the ecosystem. We sure have watched three years ago when we were here HP had a big army coming in here as to they doing their distribution. Well, HP's a hardware, HPE, I should say as they are now (laughs) is a hardware partner. Red Hat works across all of the traditional infrastructure companies. This ecosystem changed. Red Hat has a broad ecosystem. What are you seeing out there? What do you get from the partners that they're asking, and how does that play? >> Yeah, I think this really, again, mirrors our approach to Red Hat Enterprise Linux. And so if you look at all the different dimensions of compute, network, and storage, we have ecosystem partners in all of those. So we have the likes for storage, we have NetApp, EMC, IBM, many others. We have backup vendors like Trilio in on that. On the network front we have Cisco, Juniper, many others. We have ecosystem partners of all the major hardware OEMs. We have ecosystem partners in Innovee and Telco, all those spaces. So I think what really is the main driver of Red Hat Enterprise Linux is the ecosystem. It's not really the kernel anymore. It's like how do you run a consistent platform across multiple footprints? And that's what Red Hat is trying to provide because today I see there is a risk of vendor lock, and just like back in the day it was mainframe, right? Try to get everything from the lowest layer to the top layer on one platform. Many of the public cloud vendors are trying to be that one-stop shop, almost analogous to the mainframe. And what we're trying to do just like we did before for his ecosystem is to provide through leveraging the power of open source a platform that people can run, a hybrid platform that they can accelerate their business not only on all the different public clouds but also on-premise as well. >> It's interesting, last week of course big announcement with Red Hat is Microsoft's up on stage. It was like cats and dogs living together. Year before, Amazon you had a big announcement with. With Kubernetes and so many of these different tools, yes, there's that vertical integration but most of the companies understand that they're going to be in a customer environment and other people are. There's no longer, it's oh, IBM of 50 years ago where I'm going to be full in on that chop. >> Right, and I see Kubernetes is also, it's a huge open source project. So this is the difference between upstream and productization. It's what Red Hat does, is we do our maintenance, our support, our hardening, creation of this ecosystem, long life cycle support. The same thing's going to happen in Kubernetes where it's you don't just grab it upstream and run with whatever happens to be in it. And I think that there's a lot of companies that are claiming that just that Kubernetes is ubiquitous. And it's like the community innovation is ubiquitous and we're all in for advancing that. But it's really, if you're going to bet your business you want something that's productized and hardened by a contributor that you can trust. >> Well Tim, I want to connect that back with some of the other stuff that we've talked about on stage today. RHEL, super solid, history of engineering. The lower levels of your Stack need to be solid because you depend (laughs) on them. We talked a little bit about, on stage, about upgrades and things like that and how people are moving forward, the release schedule. I don't know, Mark, how are you approaching both upgrades and automation with Ansible? But other, OpenStack has other components too. How are you approaching that in the OpenStack day two to day 1000 scenario? >> Well absolutely, great question because today we've just announced our upcoming Red Hat OpenStack Platform 13 release, and that's our long life cycle release. So our last long life cycle release was version 10, and we've had a couple of shorter life versions in between. But when it comes to the upstream community what's supported in terms of upgrade is between those individual versions. When we came out with version 13, with this long life version, we have to support seamless upgrades between 10 and 13 in place without disrupting workloads that are running in your environment and make it completely smooth and seamless. And we're doing that with a feature called fast forward upgrades which is completely automated with Ansible. So that's been a big part of our focus with our engineering investment for open-- >> Ansible came up a couple of times on stage both with Zuul and also with the fast forward upgrades and it might have slipped in there a couple more times. It seems like Ansible is a big part of even this community. >> No, we're very happy with Ansible and it's a really powerful tool when it comes to automation. Got an amazing community around us. Kind of real, it's been a kind of an organic growth and we've been really happy with the team since they've joined Red Hat. It's a great foundation for everything we're doing. >> And Ansible's not just a foundation with an OpenStack. It's, for example, we have Ceph integration in with Ansible. We have OpenShift is how we deploy it using Ansible. It's how we're using NREL to what we call System Roles to be able to make it easier to upgrade from one to the other. So by combining a single technology it's making it easier for us to put together an integrated portfolio. >> Great, Tim, when people leave this show what are some of the key messages you want to make sure that they've heard from Red Hat as part of this community? >> I would say that it's Red Hat is bringing an integrated portfolio Stack because it's not just about components. It's really about how can you build, develop, and deploy applications rapidly and what's the most enterprise-ready dynamic environment that enables you to do that, and that's what we think that the power of Red Hat through its credibility in the open source community to bring all of those pieces of the Stack together from top to bottom. >> Stu: All right, and Mark, we'll give you the final word. >> Yeah, I'd actually reach for what we're reinforcing a lot on this summit. We're talking about innovate, empower, and accelerate, and that's really about these businesses that are our customers who are dealing with the challenge of trying to keep up with a rapidly changing market. And they need to innovate more. They need to move faster, need to accelerate. But they also need to empower their own application developers to do that innovation, to really kind of keep pace with the market. >> All right, well Tim Burke, Mark McLoughlin, thanks so much for all of the updates here. For John Troyer, I'm Stu Miniman. Back with much more coverage here at OpenStack Summit 2018 in Vancouver. Thanks for watching theCUBE. (upbeat music) (slow tones playing)