>> from our studios in the heart of Silicon Valley, Palo Alto, California It is a cute conversation >> universe. And welcome to another cube conversation from our wonderful Palo Alta Studios in beautiful Palo Alto, California. As we do with every cute conversation, we're gonna talk about an important topic with smart people that can provide some good clues and guidance as to how the industry's gonna be forward. We're gonna do that today, too. Specifically, what we're gonna talk about is that there has been an enormous amount of interest in kubernetes is a technology for making possible the whole micro service's approached application development. But one of the challenges that kubernetes has been specifically built to be stateless, which means that it's not necessarily aware of its underlying data. Now that is okay for certain classes of application. But the typical enterprise does want to ensure that its data can remain state full. That does have a level of protection required, et cetera, which creates a new need within the industry for how do we marry state full capabilities, staple storage capabilities with kubernetes and have that conversation? We've got great guests here. Part of Ayatollah is a co founder and C t o of robin dot io and radish men on is the CMO Robin. I owe partner Radish. Welcome to the Cube. >> Great to be here. >> All right, so, reddish one, we start with you. Why don't you give us a quick update on Robin Donna? >> Sure. Robin. Daughter, You, as you were alluding to, is addressing super important problem that is in front of us, which is that you've got cloud. Native technologies, especially containers. And community is becoming the default way in which enterprises are choosing to innovate. But at the same time, there's a >> whole swath >> of applications which were architected just five years ago, which all need to get the same benefits off agility, portability and efficiency of cloud native technologies. Robin helps bridge that, and I hope to talk more about that. >> Excellent. So part of let's start with you and talk about this problem this impedance mismatch between applications that require some state full assurance about the data and kubernetes, which tends to be stateless. How does that How does that impact the way applications get built and deployed? >> Sure. So if you look at me as you mentioned that communities is a platform that has started our originated for stateless workloads, and people have adopted the fastest growing open source project. We know about that, but when you look at a stateless work lord, it actually depends on state from somewhere. It's basically computing something right. It's computing state that's coming either, for the network ordered. Is computing on state that store brother inside, big data data, data leak or inside a database? Now, if you look at the problem itself, developers have gotten used to the agility benefits that communities has to offer the mostly infrastructure as a court kind of construct centered offers, however, the agility is not complete if you do not bring the state full workload workloads also into the communities for so as an example, think about somebody who's trying to build on entire pipeline right across the in. Just process so visualized by plane. If you're saying that you know what, in order to put this entire stock together, our entire pipeline together are to still do something that is non agile by going out sorry communities and then marry that with something inside communities. That's not true, actually. So more and more we're seeing developers and the develops teams basically saying that. Okay, I want to have the entire stock developed on deployed on a child platform, like open these. And of course, that comes with a bunch of challenges that need to be addressed and hoping you talk about that today. >> Well, if we have a zoo said the state has to be maintained somewhere, state may be maintained somewhere up in the cloud, But there are gonna be circumstances where because of data locality issues on, you know you want local control. You have ah, Leighton. See, considerations a number of other issues that you want to be ableto locate state in the closer close to the kubernetes. Is that really what we're talking about here? >> That's one aspect of it which is essentially around the performance and maybe you in governance reasons why you want to call a Kate State and stateless, Right? But the other reason I was saying is, if you want to deploy a stack, stack is comprised of many too many competent, stateless as well estate full. And you're talking about the birth of an entire application that the developer is gonna push under this platform right, so there. It's not about just the data locality and all that. It's also that just enabling the entire stock to be deployed in one shot. >> So you just you just you want a simpler, more manageable stats at all, right? So what's the solution? What people, what people have to do to get access to both those performance more more performance state Full application. Cubans clusters that record, have some degree of day locality concerns or to sustain that dream of increasingly simple stacks. What has to happen differently? >> Sure, and there are two aspects to this. The 1st 1 I would say, is that a the platform that is going to offer this on top of communities has to guarantee the persistency needs, whether it is in terms of reliability, dumps of performances. Selous, it has to guarantee does so you have to get those onto the platform first. But beyond that, if you look at other issues talking about many, there are many, many data platforms or data applications of workloads that predict board docker and communities. Now, if you don't really bring them into the Ford, you really are not solving the real business challenges that people have today, right? So beyond just providing persistency layer to communities pods, you need to have a way in which you can take complex platforms such as Mongol, Cassandra Elastic, such article rack. Cloudera these kind of workload and bring them onto a platform that has architected for Microsoft. Just communities, right? Because these platforms are not. These workers are not designed for micro service's workloads. So how do you marry them onto a platform such as communities that is designed as a micro service's platform? So you go to solve that, and that is exactly what Robin has done. So we have taken this approach where you can take complex workloads, rear platforms and then make them run on on a Microsoft this platform like abilities, starting with the storage subsystem, which is where one of our course fences. >> So I could conceivably imagine an Oracle database being rendered as a container with inside a cougar and he's cluster and position as a service have been orchestrated by by that kubernetes instance. What >> if I could jump in? You don't have to imagine we have customers in production there. They have Oracle Rack as a service offered on robin right now. One thing I want to contextualize is that our roots are in problem solving this hard problem off applications that I haven't been designed for containers contain arising them and being able to manage that gracefully in carbonated right. It just gave the example off Oracle Rack as a service. Or we also have customers with, let's say, multiple petabytes of data with her new bastard service, um, covering big large enterprises as well. Now from that lineage. Now, what've you also offering is that there is a set of customers who, already picked, Committed is already right might be open shift. It might be P K, as it might be g k to do its customers. We also have an offering called Robbins Storage, which brings powerful data management capabilities right. So to offering the platform offering, which is communities plus storage plus networking. Bless application bundles for some of the demanding workloads. But we just talked about, and then Robin Storage is a new offering which can add the magic of data management and advanced data management capabilities to any community. Is that you? >> Well, let's talk about that just for one second the uh, when I think of data management capabilities, I'm thinking not just a Iot being written back and forth between some media and some application. I'm thinking in terms of, oh, data protection and security. So are there Give us a sense of the scope of the service? Is that our part off this solution that you're talking? >> Yeah, I'll start in part like and chime in as well. So the first context you need to have is that all these data management capabilities are in the context of a hybrid being the normed implementation, right? Nine or 10 customers are looking at implementing on Prem with Public Cloud, right? So in that context, any of the cable release that we're talking about being being able to take snapshots or being able to take, you know, move that snap short to be offer as a back up in the cloud or ability, the clone and rehydrate applications, these air own capabilities that need to operate in a hybrid cloud context, that's number one. The second thing is, rather than just solve the storage level problem off taking snapshots, being able to bring application and data together is a big game changer in partner. Can you add a little bit more on the apple is data? >> Absolutely. Because, I mean, if you look at the the dinner service is the radish doctor board snapshots and clones and things living backups. Those constructs have existed in the storage industries for almost three decades. So there's nothing new about dark, right? But if you look at applying them for work Lord that are running in communities, you gotta uplevel that, because when you look at a story little snapshot, it is still a volume orelon level snapshot. But what a developer develops team needs is the ability to take an entire workload. That's a Mongo TB cluster and the only snap, short and dark cluster. I want to keep different states, even if the topology of the application is changing. Correct. And that is something that Robin has innovated on because we recognized. And I come from a storage bag when I was a distinguishing. Jenna very does have Bean fortunate to be building many data platforms there on be recognized that just leaving that storage does not deliver the promise of agility that communities offers. They were uplevel it into applications and for the very first time. In fact, we're introducing concepts such as you go to a Mongo classroom. You say I want to go snapshot this cluster. We understand the apology that this cluster has. How many shards depositor for offering these things. The service is under Langston the volumes and we dark forms a snapshot. That's an application. Little snapshot of the benefit of application will snap Shirt is that if another developer wants to go clone and run queries on that, you don't have to go Dr Storage Admin inside. Just give me clones of these large volumes. They'll say, Just clone this Mongol Devi cluster on. Then within minutes, you have an up and running long body be cluster fully functional. You can start readies life. Exactly. Other thing would be draw the stock double portability. So you have this snapshot taken periodic snapshots. So let's say that you run out of capacity nor deer center, and you would like to go bust into a different cloud. That's your on premises, and you want to go and run a clone in geeky because that's where the capacities, our snapshots and the baby, a implemented and architect of this allow you to port an entire application along with topology? Medea on data so that he can go and stand up Fully functional, ready to use. That's among Would he be cluster and geeky in the club? >> Now you talk about UK a Google kubernetes engine on G C P Google Cloud Platform. Obviously, that's when you think about kubernetes. That's kind of the mother ship. When you come right down to it. How does your platform and G K E G. C P work together? >> So the first thing is >> that we have, ah, partnership, which is led by engineering to engineering engagement, that >> part eyes front, ending around a standard set of AP eyes whereby the advanced data management capabilities that we're talking about can be brought into communities world itself and, of course, geeky as the implementation footprint. Right? So that's one area that we've been collaborating on. The second is from, ah, Google perspective. The preferred storage for running enterprise workloads or state full workloads or the data intensive work clothes that be talking about is Robin Storage and that's ah that we definitely are pretty excited by the fact that through rigorous technical evaluation, after rigorous technical evaluation, Google is chosen Robyn stories as the preferred storage for these demanding workloads. So from both these standpoints off moving the state of the art of what does it mean to provide data management capabilities to communities, to providing a solution that works today for customers who are embracing G K both on Prem in in the cloud to be able to bring state full workloads? We're working with Google and pretty excited about that part. Anyone add further color on the engineering partnership? >> He absolutely, I think, as a radish mentioned. So Google perform. We are the purport storage solution for that. Now can we just rewind back a little bit there? About 25 30 different stories? When does providing stories for communities? Right. So what is this? I think that this move is something special that let us tow this thing at this point, right. We took a very fundamentally different approach when we when we saw this problem for G k r for communities you could have started with several open source story solutions, are there and build on top of that. When their companies that take barter effects, for example, pity orifice and build on that. The companies that takes seven belong there, right? Be formally said that. Listen, if you want to elevate the experience from storage onto applications, that the example that I took earlier off taking a snatcher, a mongo migrating and if your story, it's stackers underwear off the application, which means that the stories track is unaware of the topology of the application. Can you really do application consistent snapshots? You can't. All he can do is begin to snapshot individual Williams. Correct. Now, if the stories stock is not a rare off the application to polish, can you actually the application level quality? Also, this. If you can't do that, can you really guarantee noisy neighbor elimination? You had to >> do all >> those things right? If you really wanna run data platforms, those are the core things that you need to do right and Soviet took an approach is that it doesn't know it will not cut it if you build a story. Stack on top of border defense, for example, are on set, so we do a ground up approach and he said, Look, if you wanna build a story, started this cloud native communities native. How would that look like? And how would the perimeters exposed so that it can deliver the entire experienced applications? So architectural leave yard very superior compared to the other players out there, it's proof is that we've got picked. Now that's one aspect. The other aspect is the approach that were taken to expose these primitives, their own snapshots and backup on a portability and all that was very clean. Right on. Very pragmatic how it works with both the born in the cloud as well as the the prior boatloads right on. Because of that, we're also collaborating with the Google engineers is to come up with a set off a P eyes that were planning to standardize right around community so that you could have a very standard set off a p I through which you can trigger these data management calls. Right? So that's that's other like no other stock Borden engineering to engineering collaboration. So that's the other thing that we're collaborating on to create the stana riser of FBI's based on the knowledge that we have had, because we have have we have feel deployments off like rubbish. Talked about right article rack. We have field the Prime Minster. People are deploying multiple petabytes off starting in the single communities. Robin, cluster. Right? So all that learning all the experience that we have had its contributed towards this joint Engineering to engineering. Afford that you're going to create the standardized data management. >> So we've got Robin. I owe has delivered a piece of technology for handling state full kubernetes clusters that has been validated by Google I o. Today or you know, so that can be used now. And is the basis for further engineering work to move this Maur into the mainstream for the future? That's good. Very exciting stuff, Partha. Right, Dash. Thanks very much for being here in the Cube. Thank you. Thank you. And once again, I want to thank part uh Chautala, Who is the co founder and CEO of Robin I owe and radish men on Who's the CMO Robin don I owe once again. I'm Peter Bursts. Thanks very much for watching this cube conversation until next time

(upbeat music) >> Narrator: 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, here in Vancouver. Three days wall-to-wall coverage. I'm Stu Miniman with my cohost, John Troyer. Happy to welcome back to the program, Radhesh Balakrishnan, who is the general manager of OpenStack with Red Hat. Radhesh, great to see you. It's been a week since John talked to you, and always good to have you on at the show. >> Great to be on. Good to be here talking about OpenStack at OpenStack Summit. >> Yeah so, look, OpenStack is in the title of your job. I believe, did we have a birthday cake and a party celebrating a certain milestone? >> That is indeed true; so it's the fifth anniversary of that fact that we've had a product, Red Hat OpenStack Platform, on the market. And so, we've been doing a little bit of a look back at how far we have come in the last five years as well as looking ahead at, you know, how does the next three to five years shape as well. >> Yeah, Radhesh, I'm going to date myself and when I think back to, gosh it was 18 years ago, I was working with Linux, and there were kernels all over the place and things like that. And then, I worked for an enterprise storage company and was like, ugh, like keeping up with Chrome.org was a pain in the neck. There came out this thing called Red Hat Advanced Server that was like, oh wait, we can glom onto this, we can support this with our customers, and that eventually turned into RHEL, which, of course, kind of becomes the main standard for how to do Linux. I feel like we have a lot of similarities. >> Radhesh: Absolutely, absolutely. >> In how we did. RHOSP, I believe, is the acronym, so. >> That's exactly right, and we like to have long names. >> Which are very descriptive, but Red Hat OpenStack Platform, fundamentally, to your point brings the same valid proposition that RHEL brought to Linux, to OpenStack, with the twist that, it's not just curated OpenStack, but it's a co-engineered solution of Linux and Cavium and OpenStack. And along the way we learned that, look, it's not just OpenStack and the infrastructure solution. It's done in conjunction with the software-defined storage solution or it's done in conjunction with software-defined networking. Or, fast-forward all the way now, it's being done in conjunction with cloud-native applications running on top of it, right? But regardless, in five years we've been able to grow to address these different demands being placed at infrastructure level, and at the same time evolved to address new-use cases as well; Telco is an example of that. >> Radhesh, let's spend a couple of minutes, though, on the OpenStack Platform itself from Red Hat. Some of the things, guys, that you were bringing to market, I know we talked about, here at the show, fast-forward upgrades, for instance were, they were just introducing, and maybe some other things in the Queens release that you all are bringing forward and have engineered. >> Yeah, thanks for that question, very topical, in the sense that yesterday we launched OSP 13, which is the latest and greatest version based on Queens release. If you look at the innovation packed in that it fundamentally falls in three buckets. One is the bread part that you talked about, whereby, anybody who is standing on OSP 10, which was the prior, long-release lifecycle product, over to 13, how do you kind of get over there in a graceful manner is the first area that we have addressed. The second area is around security, because how do you make sure that OpenStack-based clouds are secure by default, from the day you roll out all the way to until you retire it, right? I don't know if there's going to be a retirement, but that's the intent of all the security enablements that we have in the product as well. And the third one, how do we make sure that containers in OpenStack can come together in a nice manner. >> Yeah, the container piece is something else that, so a lot of effort, here at the show. They announced Kata containers, which, trying to give the security of a VM, lightweight VM. How does Red Hat look at Kata containers? I know Red Hat, you know Linux's containers, you know, very strong position, fill us in on that. >> Yeah, to maybe pull back a little bit and then look at the larger picture of there is the notion of infrastructure or the open infrastructure that you need and OpenStack is a good starting point for that. And then, you overlay on top of that an application deployment management configuration, lifecycle management solution that's the container platform called OpenShift, right. These are the two centers of gravity for the stack. Now, aspects such as Kata containers or Hubbard, which is for again, similar concept of addressing how do you use virtualization in addition to containers to bring some of the value around security et cetera, right? So we are continuing to engage in all these upstream projects, but we'll be careful and methodical in bringing those technologies into our products as we go along. >> Okay, how about Edge is the other kind of major topic that we're having here, I know I've interviewed some Red Hat customers looking at NFV solutions, so some of the big telcos you know specifically that use various pieces. What do you hear from your customers and help us kind of draw that line between the NFV to the Edge. Yeah, so Edge has become the center is kind of the new joke in the sense that, from an NFV perspective, customers have already effectively addressed the CORD errors and the challenges, now it's about how do you scale that and deploy that on a massive scale, right? That's a good problem to have. Now the goodness of virtualization can be brought all the way down to the radio Edge so that a programmable network becomes the reality that a telco or a carrier can get into. So in that context, Edge becomes a series of use cases. You know, it's not just one destination. Another way to say it is there is Edge an objective and there is Edge as a noun. Edge as the objective is a set of technologies that are enabling Edge, Edge networking, right. Edge management, for example, and then Edge as a destination where you have a series of Edge locations starting from CORD error center going all the way to radio. Now, the technology answers for all these are just being figured out right now. So you can say, you know, put crudely, KBM, OpenStack, containers, and Ansible will be all good elements that will come into the picture when it comes to a solution for all these footprints. >> Nice. Radhesh, maybe let's switch over to talk about the summit here, and the people here, filled with people being productive with OpenStack, right? Either looking at it, upgrading it, inheriting it. We talked to people in a bunch of different scenarios Red Hat, huge installed base, and you are good at helping and supporting, and uplifting, and upskilling a set of operators who started with Linux and now have to be responsible for an entire cloud infrastructure. Plus, now, at this conference, we've been talking about containers, we've been talking about open dev, right. That's again broadening the scope of what an operator might have to deal with. How does Red Hat look at that? How are you and your team helping upskill and enhance the role of the operator? >> Yeah, so I think it comes down to, how do we make sure that we are understanding the journey that the operator himself or herself is taking from a career perspective, right, the skill set of evolving from Linux and core automation-related skills to going to being able to understand what does it mean to live with cloud implementation on a day-to-day basis. What does it mean to live with network function virtualization as the way in which new services are going to be deployed. So, our course curriculum has evolved to be able to address all these needs today. That's one dimension, the other dimension is how do we make sure that the product itself is so easy that the journey is getting to a point where the infrastructure is invisible, and the focus is on the application platform on top. So I think we have multiple areas of focus to get to the point where it's so relevant that it's invisible, if that paradox makes sense. That's what we're trying to make happen with OpenStack. >> Radhesh, Red Hat has a very large presence at the show here; we were noting in the keynote the underlying infrastructure didn't get a lot of discussion because it is more mature, and therefore, we can talk about everything like VGPUs and containers, and everything like that. But Red Hat has a lot in the portfolio that helps in some of those underlying pieces. So maybe you can give us some of the highlights there. >> Absolutely, so we aren't looking at OpenStack as the be-all end-all destination for customers, but rather an essential ingredient in the journey to a hybrid cloud. So when you have that lens it becomes natural to you that a portfolio of our offerings, which are either first-party or in conjunction with our partners --we have over 400 partners with whom we have joint solutions as well -- so you naturally take a holistic view and then say, "How do you optimize the experience of ceph plus OpenStack for example." So we were talking about Edge recently, right, in the context of Edge we realize that there is a particular use-case for hyperconverged infrastructure whereby you need to collocate, compute, and store it in a way that the footprint is so small and easy to manage plus you want to have one life-cycle both for OpenStack and ceph right, so to address that we announced, right at hypercloud infrastructure for cloud, as an offering that is co-engineered between ceph team, or our storage team, and the OpenStack team. Right, that's just an example of how, by bringing the rest of the portfolio, we're able to address needs being expressed by our customers today. Or you look forward in terms of use-case, one thing that we are hearing from all our large customers, such as the Amadeus's of the world is, make the experience of OpenShift on OpenStack, easy to deploy and manage, as well as reduce the penalty of running containers on VMs. Because we understand the benefits of security and all of that, but we want to be able to get that without having any penalty of using a virtual infrastructure so that's why we're heavily focused on OpenShift, on OpenStack, as the form-factor for delivering that while continuing to work on things such as Kata containers as well as, you know, Kuryrs, as technology is evolving to make communities much richer as well as the infrastructure management at OpenStack level richer. >> You brought up an interesting point, we spoke a little bit yesterday with John Allessio and Margaret Dawson, about really that kind of multi-cloud world out there, because pieces like Kubernetes and Ansible, aren't just in the data center with this one stack, it's spanning across multiple environments and when we talk to customers, they do cloud, and cloud is multiple things in multiple places and changing all the time. So I'd love to get your viewpoint on what you hear from customers, how Red Hat's helping them across all those environments. >> Absolutely, so the key differentiation we see in being able to provide to our customers is that unlike some of the other providers out there, they're where they are stitching you with a particular private cloud, with the particular public cloud, and then saying, "Hey, this is sort of the equivalent of the AOL walled gardens, if you will, right, that's being created for a particular private and public cloud. What we're saying is fundamentally three things. First is, the foundation of Linux skills from RHEL that you have is going to be what you can build on to innovate for today and tomorrow, that's number one. Secondly, you can invest in infrastructure that is 100% open using OpenStack so that you can use commodity hardware, bring in multiple use-cases which are bleeding it, such as data lags, big data, Apache Spark, or going all the way to cloud-native application, development on top of OpenStack. And then last but not least, when you are embarking on a multi-cloud journey it is important that you're not tied to innovation speed of one particular public cloud provider, or even a private cloud provider, for that matter, so being able to get to a container platform, which is OpenShift, that can run pretty much everywhere, either on PREM or on a public cloud, and give you that single pane of consistency for your application, which is where business and IT alignment is the focus right now, then I think you've got the best of all the worlds. You know, freedom from vendor-lock in, and a future-proof infrastructure and application platform that can take you to where you need to go, right. So pretty excited to be able to deliver on that consistently as of today, as well as in the coming years. >> All right, we just want to give you the final word, for people out there that ... you know, often they get their opinion based on when they first heard of something. OpenStack's been around for a number of years, five years now, with your platform. Give us the takeaway for 2018 here from OpenStack Summit as to how they should be thinking about OpenStack, in that larger picture. >> The key takeaway is that OpenStack is rock-solid, that you can bring into your environment, not just to power your virtual machine infrastructure, but also baremetal infrastructure on which you can bring in containers as well. So if you're thinking about an infrastructure fabric, either to power your telco network or to power your private cloud in its entirety OpenStack is the only place that you need to be looking at and our OpenStack platform from end to end delivers that value proposition. Now the second aspect to think about is, OpenStack is a step in the journey of a hybrid future destination that you can get to. Red Hat not only has the set of surround products and technologies to round-up the solution, but also have the largest partner ecosystem to offer you choice. So what's your excuse from getting to a hybrid cloud today if not tomorrow? >> Well, Radhesh Balakrishnan, thank you for all the updates appreciate catching up with you once again. For John Troyer, I'm Stu Minimam, getting near the end of three days wall-to-wall coverage here in Vancouver, thank you so much for watching theCUBE. (upbeat music)

[Music] from San Francisco it's the covering Red Hat summit 2018 brought to you by Red Hat everyone welcome back is the cubes live coverage here in San Francisco Red Hat summit 2018 I'm Sean furry co-host of the cube with my coasts analyst this week John Troyer who's the co-founder of tech reckoning advisory and Community Development firm our next guess is red hash Balakrishnan is the general manager of OpenStack for Red Hat welcome to the cube good to see you ready to be here so OpenStack is very hot obviously with the with the with the trends we've been covering from day one been phenomenal to watch that grow and change but with kubernetes you seeing cloud native to robust communities you got application developers and you got under the hood infrastructure so congratulations and you know what's what's the impact of that what is how is OpenStack impacted by the cloud native trend and what is Red Hat doing they're the best epidermis ation of that is openshift on OpenStack if you had caught the keynotes earlier today there was a demo that we did whereby they were spawning open shifts on bare metal using OpenStack and then you run open shift on power that's what we kind of see as the normed implementation for customers looking to get - I want an open infrastructure on Prem which is OpenStack and then eventually want to get to a multi cloud application platform on top of it that makes up the hybrid cloud right so it's a essential ingredient to the hybrid cloud that customers that are trying to get to and open shifts role in this is what I'm assuming we are asked about openshift ownerships will be multi cloud from a application platform perspective right so OpenStack is all about the infrastructure so as long as you're worrying about info or deployment management lifecycle that's going to be openstax remet once you're thinking about applications themselves the packaging of it the delivery of it and the lifecycle of it then you're in openshift land so how do you bring both these things together in a way that is easier simpler and long-standing is the opportunity and the challenge in front of us so the good news is customers are already taking us there and there's a lot of production workflow is happening on OpenStack but I got to ask the question that someone might ask who hasn't been paying attention in a year or so it was thick hey OpenStack good remember that was what's new with OpenStack what would you say that person if they asked you that question about what's new with OpenStack the answer would be something along the lines of boring is the new normal right we have taken the excitement out of OpenStack you know the conversations are on containers so OpenStack has now become the open infrastructure that customers can bring in with confidence right so that's kind of the boring Linux story but you know what that's what we thrive on right our job as reddit is to make sure that we take away the complexities involved in open source innovation and make it easy for production deployment right so that's what we're doing with OpenStack too and I'm glad that in five years we've been able to get here I definitely I think along with boring gos clarity right last year the cube was that OpenStack summit will be there again in two weeks so with you and I enjoy seeing you again for it the last year there was a lot of you know containers versus there was some confusion like where people got sorted out in their head oh this is the infrastructure layer and then this is the a play I think now people have gotten it sorted out in their head open open shipped on OpenStack very clear message so a meaning of the community in two weeks in any comments on the growth of the open OpenStack community the end users that are there the the depth of experience it seemed like last year was great everywhere for OpenStack on the edge it ended you know set top devices and pull top devices all the way to OpenStack in in private data centers and and for various security or logistical reasons where is OpenStack today yeah I think that he phrased would be workload optimization so OpenStack has now evolved to become optimized for various workloads so NFV was a workload that people were talking about now people are in when customers are in production across the globe you know beat Verizon or the some of the largest telcos that we have in any and a pack as well the fact that you can actually transform the network using OpenStack has become real today now the conversation is going from core of the data center to the edge which is radio networks so the fact that you can have a unified fabric which can transcend from data center all the way to a radio and that can be OpenStack is a you know great testament to the fact that a community has rallied around OpenStack and you know delivering on features that customers are demanding pouring is the new normal of that is boring implies reliable no-drama clean you know working if you had to kind of put a priority in a list of the top things just that it are still being worked on I see the job is never done with infrastructure always evolving about DevOps certainly shows that with programmability what are the key areas still on the table for OpenStack that are that are key discussion points where there's still innovation to be done and built upon I think the first one is it's like going from a car to a self-driving car how can we get that infrastructure to autonomously manage itself we were talking about network earlier even in that context how do you get to a implementation of OpenStack that can self manage itself so there's a huge opportunity to make sure that the tooling gets richer to be able to not just deploy manage but fine-tune the infrastructure itself as we go along so clearly you know you can call it AI machine learning implementation you on OpenStack to make sure that the benefit is occurring to the administrator that's an opportunity area the second thing is the containers and OpenStack that we taught touched upon earlier OpenShift on OpenStack in many ways is going to be the cookie cutter that we're gonna see everywhere there's going to be private cloud if you've got a private cloud it's gotta be an open shift or on OpenStack and if it's not I would like to know why right it's a it becomes a de-facto standard you start to have and they enablement skills training for a few folks as you talk to the IT consumer right the the IT admins out there you know what's the message in terms of upskilling and managing say an OpenStack installation and and what does Red Hat doing to help them come along yeah so those who are comfortable with Braille Linux skills are able to graduate easily over to OpenStack as well so we've been nationally focused on making sure that we are training the loyal Linux installed based customers and with the addition of the fact that now the learnings offerings that we have are not product specific but more at the level of the individual can get a subscription for all the products that reddit has you could get learning access to learning so that does help make sure that people are able to graduate or evolve from being able to manage Linux to manage a cloud and the and face the brave new world of hybrid cloud that's happening in front of our eyes but let's talk about the customer conversations you're having as the general manager of the stack red hat what what are the what's the nature of the conversations are they talking about high availability performance or is it more under the hood about open shift and containers or they range across the board depending upon the use cases whose they do range but the higher or the bit is that applications is where the focuses well closes where the focus is so the infrastructure in many ways needs to get out of the way to make sure that the applications can be moving from the speed of thought to execution right so that's where the customer conversations are going so which is kind of ties back to the boring is the new normal as well so if we can make sure that OpenStack is boring enough that all the energy is focused on developing applications that are needed for the enterprise then I think the job is done self-driving OpenStack it means when applications are just running and that self-healing concepts you were talking about automation is happening exactly that's the opportunity in front of us so you know it's by N's code by code we will get there I think I love the demo this morning which showed that off right bare metal stacks sitting there on stage from different vendors right actually you're the you know OpenStack is the infrastructure layer so it's it's out there with servers from Dell and HP II and others right and then booting up and then the demo with the with Amadeus showing you know OpenStack and public clouds with openshift all on top also showed how it fit into this whole multi cloud stack is it is it challenging to to be the layer with with the hardware hardware heterogeneous enough at this point that OpenStack can handle it are there any issues they're working with different OEMs and if you look at the history of red add that's what we've done right so the rel became rel because of the fact that we were able to abstract multi various innovation that was happening at the so being able to bring that for OpenStack is like we've got you know that's the right to swipe the you know employee card if you will right so I think the game is going back to what you were only talking about the game is evolving to now that you have the infrastructure which abstracts the compute storage networking etc how do you make sure that the capacity that you've created it's applied to where the need is most right for example if you're a telco and if you're enabling Phi G IOT you want to make sure that the capacity is closest to where the customer fool is right so being able to react to customer needs or you know the customers customers needs around where the capacity has to be for infrastructure is the programmability part that we've you know we can enable right so that's a fascinating place to get into I know you are technology users yourself right so clearly you can relate to the fact that if you can make available just enough technology for the right use case then I think we have a winner at hand yeah and taking as you said taking the complexity out of it also means automating away some of those administrative roles and moving to the operational piece of it which developers want to just run their code on it kind of makes things go a little faster and and so ok so I get that and I but I got to ask the question that's more Redhead specific that you could weigh in on this because this is a real legacy question around red hats business model you guys have been very strong with rel the the the record speaks for itself in terms of warranty and and serviceability you guys give like I mean how many years is it now like a zillion years that support for rel OpenStack is boring is Red Hat bringing that level of support now how many years because if I use it I'm gonna need to have support what's the Red Hat current model on support in terms of versioning xand the things that you guys do with customers thank you for bringing that up what have you been consciously doing is to make sure that we have lifecycle that is meeting two different customers segments that we are talking about one is customers who want to be with the latest and the greatest closer to the trunk so every six months there is an openstack released they want to be close enough they want to be consuming it but it's gotta be production ready in their environment the second set of customers are the ones who are saying hey look the infrastructure part needs to stay there cemented well and then every maybe a couple of years I'll take a real look at you know bringing in the new code to light up additional functionality or on storage or network etc so when you look at both the camps then the need is to have a dual life cycle so what we have done is with OpenStack platform 10 which is two years ago we have a up to five year lifecycle release so obvious that platform 10 was extensible up to five years and then every two releases from there 11 and 12 are for just one year alone and then we come back to again a major release which is OSP 13 which will be another five years I know it can be and they get the full Red Hat support that they're used to that's right so there are years that you're able to either stay at 10 or you could be the one who's going from 10 to 11 to 12 to 13 there are some customers were saying staying at 10 and then I won't go over to 13 and how do you do that we'll be a industry first and that's what we have been addressing from an engineering perspective is differentiated - I think that's a good selling point guy that's always a great thing about Red Hat you guys have good support give the customers confidence or not you guys aren't new to the enterprise and these kinds of customers so right - what are you doing here at the show red hat summit 2018 what's on your agenda what some of the hallway conversations you're hearing customer briefings obviously some of the keynote highlights were pretty impressive what going on for you it's a Volvo OpenShift on OpenStack that's where the current and the future is and it's not something that you have to wait for the reality is that when you're thinking about containers you might be starting very small but the reality is that you're going to have a reasonably sized farm that needs to power all the innovation that's going to happen in your organization so given that you need to have an infrastructure management solution thought through and implemented on day one itself so that's what OpenStack does so when you can roll out OpenStack and then on top of it bring in openshift then you not only have to you're not only taking care of today's needs but also as you scale and back to the point we were talking about moving the capacity where is needed you have a elastic infrastructure that can go where the workload is demanding the most attention so here's another question that might come up from when I asked you and you probably got this but I'll just bring it up anyway I'm a customer of OpenStack or someone kicking the tires learning about deploying up a stack I say ritesh what is all this cloud native stuff I see kubernetes out there what does that mean for me visa V OpenStack and all the efforts going on around kubernetes and above and the application pieces of the stack right let's say if you looked at the rear view mirror five years ago when we looked at cloud native as a contract the tendency was that hey look I need to be developing net new applications that's the only scenario where cloud native would be thought thought off now fast forward five years now what has happened is that cloud native and DevOps culture has become the default if you are a developer if you're not sort of in that ploughed native and DevOps then you are working on yesterday's problem in many ways so if digital transformation is urging organizations to drive - as cloud native applications then cloud native applications require an infrastructure that's fungible inelastic and that's how openshift on OpenStack again coming back to the point of that's the future that customers can build on today and moving forward so summarize I would say what I heard you saying periphery if I'm wrong open ship is a nice bridge layer or an up bridge layer but a connection point if you bet on open ship you're gonna have best of both worlds that that's a good summary and you gotta be you know betting on open first of all is the first order a bet that you should be making once you've bet on open then the question is you gotta bet on an infrastructure choice that's OpenStack and you gotta bet on an application platform choice that's open shift once you've got both of these I think then the question is what are you going to do with your spare time okay count all the cash you're making from all the savings but also choice is key you get all this choice and flexibility is a big upside I would imagine British thanks for coming on sharing your insight on the queue appreciate it thanks for letting us know what's going on and best of luck see you in Vancouver thank you for having okay so the cube live coverage here in San Francisco for Red Hat summit 2018 John four with John Troy you're more coverage after this short break

>> 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)

>> Live from Boston, Massachusetts. It's theCUBE covering Red Hat Summit 2017. Brought to you by Red Hat. {Electronic music} >> Welcome to the session wrap of the Red Hat Summit. I am your host, Rebecca Knight, along with my co-host Stu Miniman. Wrapping up three great days of open source talk. Where are we, Stu? Tell us the state of Red Hat, the state of open source. What have we learned? >> You mean, beyond we're in the seaport district of Boston, Massachusetts, you know, a couple blocks away from >> or the heart of open source the new open innovation lab coming from Red Hat. So, Rebecca it's been a lot of fun with you these last couple of days. >> I feel the same way. >> Did over thirty interviews: executives from Jim Whitehurst you know on down to many of the product teams many people participating greatly in open source, open innovation award winners, the women of open source award winners, open invest in lab participants. A lot of topics but okay Red Hat itself. I've worked with Red Hat in various roles in my career for quite a long time. We didn't talk a lot about Linux this week. >> Stu, Stu, Stu I've got to stop you Linux is containers, containers is Linux. So we're hearing so much about containers it's the same diff. >> Yeah, well I got the t-shirt "Linux is containers, containers are Linux" however, if I even look at Red Hat's messaging Red Hat Enterprise Linux is like the first platform what they built around and it's a little surprising that they didn't at least in the conversation we had, it was very much about some of the newer things coming into the show I said What's the progress that they've made around some of the cloud offerings, some of the management offerings, Ansible, weaving its way into a lot of the products. OpenShift really maturing and expanding the portfolio with things like the OpenShift io to be able to really help with application modernization. Middleware progressing even heard a little bit of the future where they are doing things like server lists. So Red Hat's making good progress. We love when we do these shows multiple years is they talk about it, they deliver on it, and in the way a couple guests talked about there's a little more transparency in open source and being part of all of these communities you have some visibility as to where you're going it doesn't mean that things don't slip every now and again and not every piece makes it into the product lease that they're expecting, but they've made great progress. Linux still is just a mainstay. It's a piece of lots of environments. The ecosystem reminds me of the same way I talk about OpenStack which we'll go into next week. We had a great session with Radhesh towards the end here talking about OpenStack in many ways is like that it's weaving its way into lots of infrastructure pieces some we'll dig into more this week, but let's focus on this week for now. >> Right, so you said we didn't talk a lot about Linux. I set you straight there. But what else did we, what else did you not hear? What do you remain skeptical of? As you said, Red Hat seems to be going from strength to strength. It had two point four billion in revenue this year. >> Yeah it did. For 2016, two point four billion in revenue and three billion in bookings >> Right And there was, I read a financial report that Jim Whithurst said Golda Company is five billion within five years. And you look at it and you say okay from two point four to five well, you know >> yeah actually if it was three billion in bookings and I think back to three years ago when we first started it was around two billion dollars that was almost a 50% growth rate in three years. So, if three years from now we do 50% growth rate we're going to have three to four point five. Of course the math is not linear, there's scaling of the company, there's lots of products in here, but they've got a big tam. >> Ambitious but achievable. >> Ambitious but achievable. The question we've had for a bunch of years is when I look at the cloud. Public cloud is affecting a lot of the traditional infrastructure companies. Red Hat is a software company. They're an open source company. We heard the cloud messaging. Microsoft and Google up on stage. Andy Jassy on video. That was a big question coming in. What about Amazon? How close will Red Hat do? Amazon actually has their own AMI for Linux which means I can get a package for Linux from Amazon not only that I could take that package outside of Amazon and put it in a data center so I could use the same type of Linux for AWS to work with Red Hat to take RedShift make what's deeper integration in the public cloud with AWS and if I put that on premises I'm going to have access to the AWS services so that tighter application integration for what they're laying out really the open hybrid cloud. Red Hat terminology, we'll see if other people take that up. But really it's a multi-cloud world and Red Hat has a good position to live in lots of those environments and provide and really help solutionize and give really almost that almost adult supervision that the enterprise wants for all of these open packages. So I was heartened to see the progress made. Strong ecosystem. As always, you know passionate customers, developers, and really just heartwarming stories of you know making the world a better place. What was your take on those pieces? >> Yes, absolutely. Those are really what you come away remembering. It is the story of a woman saving a man's life in a park in Singapore. It is the story of an emergency room doing a better job of serving its patients. It is scaling up technology use in the developing world. This is what you come away. And you say that is open source. >> Maybe next year that apple you get at the grocery store won't have been sitting there 18 months. >> Well maybe. But in a code climate. Boston going to be beautiful year round. No, but so I really do agree and that is I think what Red Hat did so brilliantly at this summit. Is really showcasing the ways in which this technology is having an impact at transforming industries obviously, helping businesses make more money, but also really doing a lot of good. >> Yeah, absolutely. And Rebecca I want a big shout out to the community here. This is a community show. Red Hat is a great participant of the community. We talked to Jim Whitehurst they want to help raise up the community it's not about Red Hat leadership. We don't hear number one at a show like this, we hear where they're participating and when they get involved they go deep. We heard about OpenPOWER. How excited they are that Red Hat you know getting involved and working in some of these pieces. So, we could not be here without Red Hat support. It's our fourth year doing the show. We had a blast with it. We see Red Hat at a lot of shows. They bring us great customers, their ecosystem partners and their executives. And it's been a pleasure to cover it. >> Yeah. No, I couldn't agree more and I do think, just in terms of what your talking about, the humility of the Red Hat folks is that they aren't going banging drums of we're number one in this and number one in that and you sort of think, "okay, blah, blah." No, they don't at all. They really are saying, "No we're about making our partners and our customers shine." >> Yeah, yeah. What's going to happen with the future of jobs? You know where are people going to work these days in the future? >> How will they work? >> Rebecca: What kind of processes will they work with? >> We've all said it's very much a global ecosystem here. Got to interview quite a few international guests here and hear how technology is spreading, how people are interacting, how innovation happens in a global environment. I'm sure ties back to a lot of the things that you write about. >> Absolutely. And I think, that Radhesh some of his words of wisdom was technology is the easy part what we need to be fundamentally rethinking is how we write these applications, how we develop these applications, how we design them, and how we deliver them. And, also really bearing in mind the end user. And, that is what we learned in a lot of our other sessions. Is really thinking about that. We heard from another person you know your competitor is maybe not necessarily the competitor you're thinking of it's the last app you opened or the last application that that company was using and what is drawing them toward that application or that technology or that infrastructure and not yours? [Stu]- Right. >> And so it's really thinking much more broadly about technology and who you're competing with and how you're working. >> Yeah, that was it was a bank. I loved that. They're like we're not competing against other banks it's like where's that other attention span that you have. >> Rebecca: Right, where are your eyeballs. >> One of my favorite lines is you know what you, Michelangelo, and Einstein have in common? You only have 24 hours in the day so you need to make sure you take advantage of that. That's the kind of thing that >> That's depressing Stu, when you leverage >> I don't know. the community. I thought it's inspiring. >> Okay. You know we can do >> Good great things when we work together and do that. So, we're always like oh I'm too busy or I don't have time it's like hogwash. >> Right. >> That's not the case. I'm inspired and fired up after all the conversations we had especially some of these great users here and looking forward to the next one. >> You're looking forward to the next one, you're looking forward to OpenStack coming up. >> Yeah, oh my gosh so right. >> Got to plug it. >> So Rebecca next week we're both going to be on theCUBE but in two different locales. Our team is in the midst of the sprint that is the spring tour. So we had the Micron event and we're here. Next week our team is at Service Now Knowledge, we're also at DELL EMC World in Vegas, we're at OpenStack Summit back in Boston. We've got some of our teams going to Microsoft Build. I'm sure we'll have analyst reports follow up from there. Boy do we have more shows than I can mention through the rest of May and June and beyond. Check out siliconangle.tv to catch all of them. Rebecca I'm going to let you do the close, but I have to say a big thanks to our team here and remote. >> Yes, yes. Leonard, Chuck, Alex, Ava. >> We love you all. Jeff and the team back there. You know we were doing some cool things playing with Facebook Live as part of this event, we always love playing around with some of the new technologies finding more ways that we can help reach you. We always appreciate your feedback. And Rebecca take us on home. >> Thank you so much for joining us here at theCUBE Red Hat Summit, Boston, Massachusetts. I'm Rebecca Knight for Stu Miniman, Thanks so much. {Electronic music}