>>lost myself. >>You know, one of the things that I love about the Cuba being doing it for 11 years now is that everyone that we interviewed years and years ago, they all getting promoted. So much fun to watch everyone grow and and now it's stews over there now so it's fun to get to do something. When >>are you gonna, are you gonna get to interview stew for? Way >>to put them on the hot seat? I think he's afraid actually >>throughout all the talking points. Right. 1st question. The way >>we do miss too. I will say that it is amazing. Okay, I'm ready to go. >>Red >>Hat Summit read. Pat Summitt, we're coming to you in. Hello and welcome back to the Red Hat Summit 2021 virtual coverage I'm john for is the cube coverage of Palo alto with the remote interviews for our virtual conference. You've got two great guests cube alumni's Tom Anderson VP of answerable automation platform and Robyn Bergeron who's the Senior manager and small community community architect and all the great things involved, Robyn great to see you tom. Thanks for coming back on red hat some of this year. Virtual. Good to see you. >>Thanks for having us. >>So since last summit, what's the updates on the answerable community and the automation platform? Tom we'll start with you automation platform. What's the big updates? >>Yeah. So since the last time a lot has happened in the unanswerable land. If you will also last time that we were talking about constant collections have given distribution format or the integrations that ends this close. So a lot of the content. Uh huh. As well as the commercial users we launched last year a fucking program certified contact program with our partners and including partners to certify the content collections today. Create co certify them where we work together to make sure that they're uh developed against and tested against a proper step so that both of us can provide them to our customer basis with confidence that they're going to be working informed broccoli and that we red hat and our partners co support those out in our customers production parts. That was a big deal. The other thing that we announced late last fall was the private automation hub. And that's the idea where our customers obviously appreciate the idea of being able to go to Ansel Galaxy or the answerable automation to go and grab these content collections. This these integrations and bring them down in their environment. They wanted a way that they wanted a methodology where there are a repository where they can curate content from different sources and then manager across the environment. The automation across their environment. Kind of leaning into a little bit of automation content as code if you will. And um, so we launched the automation of the private automation hub where that sits in our customers infrastructure, whether that's in the cloud or on premises with both, and allows them to grab content from Galaxy from the answer automation. Uh, the answer automation hub on cloud got red hat dot com as well as their internally developed content and to be able to manage and provide that across their organization governed by a set of policies. So lots of stuff is going on real advancement in the amount of content that we provide, uh, the amount of collections that we provide them certified up for customers and and the ability to manage that company across the teams. >>I want to do a drill down on some of the unification of teams, which is a big message as well as operating scale because that's the super value proposition you guys have and want to get that. But robert, I want to come back to you on the community so much has gone on, we are now into the pandemic for almost a year and a half now, um it's been a productivity boom. People, developers have been working at home for a long time, so it's not a new workflow for them, but you've seen a lot more productivity. What has changed in the community since last summit? Again, virtual to virtual again between the Windows here, event Windows, you guys have a lot going on. What's new in the community gets an update? >>Yeah, well, I mean if we go back to summit, you know, this time ish, you know, last year we were wrapping up more or less the, it was, you know, we used to have, you know, everything you would install answerable, you would get all the modules, you get everything, you know, it was all all all together, which, you know, is great for new users who don't want to have to figure things out. It helps them to really get up and started running quickly. Um and But, you know, for a from a community perspective, trying to manage that level of complexity turned out to be pretty hard. So the move to collection was actually great for, you know, not just, you know, for a user perspective, but also from a community perspective. Um and we came out with the answerable to 10 that was last fall, I believe, and that was the first real release advance. Well, where we had, you know, collections were fully in stan she hated uh you know, they were available on Galaxy, but you can also get them as part of the animal community distribution. Um, fast forward to now. You know, we just had the answer to all three point oh release here in february and we're looking to answer bill ford auto here in early May. So, you know, there's been a lot of activity, a lot has improved honestly as a result of the changes that we've made, it's made it a lot easier for contributors to get in with a smaller group that's more of their size and you know, be able to get start and identify, you know, who are, they're interested peers in the community. So that's been a boon for us honestly. Um, you know, the pandemic otherwise is, you know, I think taught all of us, you know, certainly you john about the, the amazing things that we can do virtually. So we've had a lot of our meetups pivot to being virtual meetups and, and things like that. And it's been great to see how, how easily the community's been able to pivot around. You know, this sort of event. Um, I hope that we don't have to just keep practicing it for forever, but in the meantime, you know, it's enabled us to continue to get things done. Thank goodness to every video platform on earth. Yeah, >>well we appreciate we're gonna come back and talk more about that in the future, but best practice what we all learned and stories. But I think I want to come back to you on the persona side of answerable because one of the things we talked about last time that seems to be getting a lot of traction is that multiple personas. So I want to just hold off that will come back tom back to back to you were red hat summit. You guys have an apple fest, which is your own event that you guys drill down on this. So users Washington, you know this, your own community, but now part of red hat part of IBM, which IBM thinks also happening soon as well. Red hat some, it still is unique event. How is answerable fitting into the big picture? Because the, the value proposition of unifying teams is really consistent now with red hats overall arching thing, which is operating at scale open shift Robin just mentioned, where is the automation platform going this year? What's the story here at red hat summit for the automation platform? >>Yeah, that's that's a great question. We've seen so kind of timeless, a little bit of dependent and how it has accelerated some existing trends that we already saw and one of those is really around the democratization of the application delivery teams, more people delivering infrastructure and applications independent of each other, which is right, faster and more agile, all of those other. Good, good uh, words that apply to that. But what that does bring up is the opportunity for um >>patient >>of work, replication of effort, uh not reusing necessary things that are in existence already that other things may have maybe not complying with all of the policies if you will, the configuration and compliance policies. And so it's really kind of brought danceable out into focus even more here because of the car comin back plane that provides a common language and common automation back plane across these different teams and across these different personas. The great thing about what we supply for these different personas, whether its application developers, infrastructure owners, network engineers set up teams, get ox teams, There's so many of these options out there now, All want independent access to infrastructure and deploying infrastructure. And Answerable has the kind of levers that each of those communities, whether it's API or Cli s or event based automation or uh web hooks, et cetera et cetera. You know, service catalog. He lies all of those um interfaces if you will or modalities are accessible into hands of water nations. What's really allowed us to be this sort of connective tissue or blue across these different silos or remains of the organization the time of the year? Open ship specifically one of the things that we talked about last fall and are answerable fest was our integration between Answerable to automation platform are advanced cluster management product and are open ship platform that allows native applications running on open ship. Be able to talk to a sensible automation operator that's running on that same platform to do things off platform for it that our customers are already using. Answer before. So connecting their cloud, native platforms with their existing ecosystems and infrastructures. Systems of records, network systems, uh, ticketing systems, you name it. So all of those sort of integrations and school has become the connected blew across all of these different environments time. Traditional, anti biotic native, you name it. So it's really been it's really been fun and it's been an exciting time for us inside the portfolio. And uh, >>that's a great point connective tissue is a great way to describe some of these platform benefits because you have been on this platform for a really long time and the benefits are kind of being seen in the market. Certainly as people have to move faster with the agility robert. I want to come back to you because you brought up this idea of personas. I mean we all know devops infrastructure as code has been our religion for over a decade more, but now the word DEv sec ops is more prevalent in all the conversations the securities now weaved in here. How are you seeing that play out in the community and then tom if you can give some color commentary to on the automation platform, how security fits in. So devops everything's being operationalized at scale, we get that that's one of the value problems You have. But def sec off as a persona, more people want more sex. Deb is great more ops and standardisation. More developers, agile standards and then security def sec ops. What's your? I >>thought it was dev net sec off. >>Okay. I've forgotten that they were putting that in their networks abstracted away, you know, As we say. Yeah. >>Well, you know, from, from my perspective, you know there are people and their jobs all over the place is right. Like they you know the more they can feel like they're efficient and doing great stuff at their work. Like they're happy to bring as many people into the fold as possible, right? And you know normally security has always been this you know it's sort of like networking right? It's always been this sort of isolated this special group over here that's the traditional you know one of the traditional I. T. Bottlenecks that causes us to not be able to get anything done. But you know on a community level we see folks who are interested in security you know all the time. I know we've certainly done quite a bit of work with some folks at IBM around one of their products which I assume tom will get more into here in just a moment, but from, you know, a community perspective, I mean, we've seen people who have been writing, you know, playbooks and roles and you know, now collections for uh you know, all the traditional government testing, you know, is are, you know, missed standards, all of that kind of stuff. Um and you know, it's one of those, it's part of network effects and it's a great place where actually automation hub, I think, you know, for folks who are on prem or you know, any of our customers are really going to start to see lots of value is how it will be able to connect folks inside the organization organically through just the place where I'm doing my answerable things, allows them to find each other really, and build those, you know, take it from being silos of automation everywhere into a really sort of networked, you know, internal network of of answerable friends and uh danceable power users that can work together and collaborate, you know, just the same way that we do an open source >>and tom so I. T. Modernization requires security. What's your take on this? Because, you know, you got cluster a lot of cluster advanced cluster management issues, you've got to deal with the modern apps, they're coming, I. T. S got to evolve. What's your take on all >>this? Yeah, not only does I have to call but it's it's an integration like the rest of the environment and be able to respond the spirit of that song on the areas that we put a lot of effort into advanced in terms of curating and solutions around national security automation. We talked about that in the past, the idea of connecting the SEc ops teams that are doing intrusion detection or threat hunting and then responding in an automated way to those threats protections. Right? So, connecting stepped up to the bike, which is traditionally been styled operations and silo teams. And now it is curated against the security automation uh, solution that we've got a market with our partners. It connects those two teams in a single sort of way. We've done a lot of work with our friends that idea around this area because they are big and that security area, a radar and other products in their portfolio. So we've done a lot of work with them but we don't want to work with lots of our partners for their side. There are Microsoft in those areas. Traditionally Danceable has done a great job on sort of compliance around configuration enforcement, right setting and enforcing configuration. Now we moved into connecting set pops with IT security automation. And now with our acquisition of staff blocks along with our advanced custom management immigration with Danceable were starting to say, what are the things inside that sack office workflow that may require integration or automation packaged? Automate automation with other parts of the environment, bringing all of those pieces together as we move forward to security for us. >>Okay. I gotta ask you guys the number one question that I get all the time and I see in the marketplace is kind of a combo question is how do I accelerate the automation of my cloud native development with my traditional infrastructure? Because as people put in green born the cloud projects, whether it's whether and then integrating able to cloud on premises with nutritional infrastructure, how do I accelerate those two environments? How I automate accelerate the automation? >>Yeah. So it's a great story for us and this is what we're talking about, small and special as we have bringing together of our advanced cluster management product, open ship platform and it's just, you know, widespread use through all the automation of both traditional and cognitive changes. Whether it's cloud infrastructure on premise, start network, you name it, customers are using answerable user, you're using answer to do all kinds of pieces in the system infrastructure. Being able to tie that to their new collaborative initiatives without having to redo all of that work that they've already done to integrate that existing um infrastructure automation with their cognitive accelerate substantial what I call the offer operationalization to say operated operationalization, their cloud native platforms that are existing infrastructure and existing I uh, ecosystem. I believe that that's where the answer the automation and plays a key role in connecting those students is together without having to redo all that work that's been done in investment >>robert. What's your take on this? This is what people are working on the trenches, they realized cloud benefits. They got some cloud native action, and also that they got the on the traditional environment, they got to get them connected and automated. >>Yeah, absolutely. I mean, you know, the beauty of answerable, you know, from an end user perspective is, you know, how easy it is to learn and how easy the languages to learn. And I think, you know, that that portability, you know, it doesn't matter like how much of a rocket scientist you are, you know, everybody appreciates simplicity, everybody appreciates being able to hand something simple to somebody else and letting other people get done and having it be more or less in a it's not quite english, but it's definitely, you know, answer is quite readable, right? Um, and you know, when we looked at, you know, when we started to work on all the answerable operators, you know, one of that, one of the main pieces there was, making sure that that simplicity that we have an answerable is brought over directly into the operators. So just because it's cloud native doesn't mean you suddenly have to learn, you know, a whole set of new languages and peoples just as portable there as it is to any other part of the your mighty organization, infrastructure or whatever it is that you have going on. >>Well, there's a lot of action going on here at red hat summit 2021 things I wanted to bring up in context of the show um is the successor and the importance of you guys having answerable collections. This has come up multiple times. Um as we talked about those personas and you've got these new contributors, you've got people contributing content. Um, as open source continues to grow and be phenomenal value proposition. Touch on this uh, concept of collections. What's the updates? Why is it important? Why should folks pay attention to it and continue to innovate with collection? >>This is from a commercial perspective of food products, questions and down has made a lot of these contributors to create an exploit, distribute content at the end, the problems mentioned earlier, these iterations announced, we'll have all of the documentation, all those collections, all within one. If you call the batteries included back at the time that day. Right. But that, that meant that contributors um, be able to deploy their content with the base, has the distribution. They have to wait for the next version. Events. Alright, that's when that content would get redistributed the next investment. He coupled content from the core engine, putting that into elections that are individual elements of related innovations closes can use at their own pace. So users and customers can get content baby a case that contributors like in public. So, uh, customers don't have to wait for the next evolution shipping products. You get a new version of the immigration is really like, you know, so again, a couple of those things that last into the different faces the engine or the platform itself is the state Department's here. It's going to be a certain website. Content itself, all the different content, the network providers ready platforms, all of those same pace. You girls have their own life cycle quite sweet. It allows us to get more functionality for customers hands like bigger and then launching our Certified can support that. Okay. Certified. Support that content tells me the values that we bring our customers with the subscription. Is that ecosystem and highest partners that we work with Certified and support the stuff that we should and support with possible superb benefits, both on the access to the technology as well as the access to the value of this. In terms of immigration testing and support >>Robin, What's your take on the community? I see custom automation with with the connector, a lot of action going on collections. >>Yeah, absolutely. Um, you know, it's been interesting, you know, tom just mentioned the, you know how everything previously all had to be released all at once. Right. And if you think about, you know sure I have answerable installed but you know, how often do I have to, you know, just even as a regular, I'm not a system administrator these days, type person like how often do I have to, you know, click that button to update, you know, my Mac or my Lennox machine or, you know, my Windows machine or, you know, the operating system on my telephone, right? Every time one of these devices that answerable connects to or a program or whatever it is, connects to something, those things are all operating and, you know, developing themselves at their own pace is right? So when a new version of, you know, uh, uh, well, we'll call Red Hat enterprise Linux when a new version of Red Hat enterprise Lennox comes out, uh, if there are new changes or new features that, you know, we want to be able to connect to it. That's not really helpful when we're not releasing for another six months. Right? So it's really helped us, you know, from a community angle to be able to have each of these collections working in concert with, you know, like for example, in real like the Lennox subsystems that are actually making things that will be turned into collections, right? Like Sc Lennox or System D right? Like those things move at their own pace, we can update those at our own pace in in collections and then people can update those collections without having to wait another six months or eight months or whatever it is for a new version of answerable to come out. It's really made it easier for all of those, you know, developers of content to work on their content and their, you know, answerable relationships almost in sync and make sure that, you know, but not, I'm going to do it over here and then I'm gonna come back over here and fix everything later. It's more of a continuous >>development. So they contribute experience is better than you'd say. >>I'm sorry, >>the contributor experiences better than. Oh, >>absolutely. Yeah, 100%. I mean, it's, >>it's, >>you know, there's something to be said for. I wouldn't say it's like instant satisfaction, but, but certainly the ability to have a little bit more independence and be able to release things as as you see fit and not be gated by the entire rest of the project is amazing for those >>votes. So I put you on the spot, Robin. So if I'm a, I'm a developer bottom line, me, what's in it for me? Why? Why should I pay attention to collections? What's the bottom >>line? Well, you know, answerable as a platform and, and for benefits from network effects. Um, you know, the reason that we've gotten as big as we have sort of like the snowball rolling downhill, right, the more people that latch on to what you're doing, the more people benefit and the more, you know, additional folks want to join in. So, you know, if I, if I was working on any other product that I would consider being able to have automated with answerable, um, you know, the biggest thing that I would look at is, well, you know, what are those people also using or they automating it with an apple and I can guarantee you 99% of the time, everything else that people are using is also being automated with answerable. So you'd be crazy to not, you know, want to participate and make sure that you're providing the best, you know, and experience for your application because for every Application or device that we can connect you, there's probably 20 other competitors that also make similar applications that folks might also consider in lieu of you if you're not using your not providing ample content >>for it. Hey, make things easier, simple to use and you reduce the steps it takes to do things. That's a winning formula. Tom. I mean when you make things that good, then you get the network effect. But this highlights what you mentioned earlier about connective tissue. When you use words like connective tissue, it implies an organizational is not a mechanism. It's not just software, it's people, there's a people experience here in the automation platform. This seems to be the bottom line. What's, what's your take? What's your bottom line of you? I'm a developer. What's in it for me? Why should I pay attention to the automation platform? >>States of the public developer. What excites me is using it? Yeah, I'm just composition department and crossing those domains in silence and sort of can issue across these tools and resolve this means those contributors is developed as a great denomination come embedded in the hands of more people across the organization. Absoluteal more simple. five way by using the explanation. Sometimes they get access right. You see those out the automation of South coast for so long as they get access to existing automation faster. They have to run into the expert on their part requirement a local hotel folks and the real in terms of automation and that kind of a patient. Excellently. When I'm getting on you about the details of what it takes them, you configure the network and figure the storage elements. They rely on those automation developers and contributors that would do that for them. You must really work powers of this Children across those news process of human. Again when I got kidnapped and sent cops, the idea of connecting to the network, being able to do all of these tasks with the same language and the same. In addition, funds had some money faster and get some of the kind of quote responsibilities without worrying. Line >>Robin, you wanted to talk about something uh, in the community. Any updates? I think navigator you mentioned you wanted to mention uh, plug for that. Absolutely. >>So, you know, um, much like any other platform in the universe. You know, if you don't have really great uh, tools for developing content, you're kind of, you know, dead in the water, right? Or you're leaving it to fate. So we've been working on a new project. I'm not part of the product yet, but you know, it's sort of in a community exploratory phrase released early release often or you know, minimum viable project I guess might be the other way to describe it currently. Uh it's a called Animal Navigator, it's a TUI which is like a gooey, but it's got a sort of a terminal user interface look to it that allows you to, you know, develop, its a sort of interface where you can develop content, uh you know, all in one window, have your, you know, documentation accessible to you have, you know, all of your test results available to you in one window, um rather than I'm going to do something here and then I'm gonna go over here and now, I'm not sure. So now I'm gonna go over here and look at docs instead. It's all, you know, it's all in one place, um which we think will actually, but I mean, I know the folks who have seen it have already been like, but you know, it's definitely an early community stages right now. It's, you know, we can give you the link github dot com slash answer slash danceable navigator, but >>versus a gooey versus a command line interface are how do you innovate on the command line? It's a kuwaiti uh it's >>um you know, there there's so many ideas out there and I think tom can probably talk to some of this, you know, how that might relate to V. S. Code or you know, many of the other traditional developer ideas that are out there, but you know, the goal certainly to be able to integrate with some of those other pieces. Um but you know, it's one of those things where, you know, if everybody is using the same tool, we can start to enforce higher levels of quality and standards through that tool. Uh there's benefits for everyone tom, I don't know if you want to add on to that in any way. >>Yeah, it's just kind of one of our focus areas religious making it as easy as possible to create things and a lot of nations. So part of that is essentially a kind of road map in the nesting table and spoke that that's not presented to the security is you don't build test deploy. So people are making a contributor that builders life job. >>Well, thanks for coming on tom and Robyn. Thanks for sharing the insight here. Redhead Summit 21 virtual. I'll see you guys do continue to do a great job with the success of the platform, which has been, you know, consistently growing and having great satisfaction with developers and now ops teams and sec teams and Net teams, you know, unifying these teams is certainly a huge priority for enterprises because the end of the day, cloud scale is all about operating a skill, which means more standards, more operations. That's what you guys are doing. So. Congratulations on the continued success. Thanks for sharing. >>Thanks for having us. >>Okay. I'm John for here in the queue, we are remote with Cube virtual for Reddit Summit 2021. Thanks for watching what?

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud, Native Computing Foundation and Ecosystem Partners. Hello, everyone. And welcome back to the cubes Ongoing coverage of Cuba con North America. Joe Fernandez is here. He's with Stephanie, Cheras and Joe's, the V, P and GM for core cloud platforms. That red hat and Stephanie is this s VP and GM of the Red Hat Enterprise. Lennox bu. Two great friends of the Cube. Awesome seeing you guys. How you doing? >>It's great to be here, Dave. Yeah, thanks >>for the opportunity. >>Hey, so we all talked, you know, recently, uh, answerable fest Seems like a while ago, but But we talked about what's new? Red hat really coming at it from an automation perspective. But I wonder if we could take a view from open shift and what's new from the standpoint of you really focus on helping customers, you know, change their operations and operationalize. And Stephanie, Maybe you could start, and then, you know, Joe, you could bring in some added color. >>No, that's great. And I think you know one of the things we try and do it. Red hat clearly building off of open source. We have been focused on this open hybrid cloud strategy for, you know, really years. Now the beauty of it is that hybrid cloud and open hybrid cloud continues to evolve right with bringing in things like speed and stability and scale and now adding in other footprints, like manage services as well as edge and pulling that all together across the whole red hat portfolio from the platforms, right? Certainly with Lennox and roll into open shift in the platform with open shift and then adding automation, which certainly you need for scale. But it's ah, it's continues to evolve as the as the definition of open hybrid cloud evolves. >>Great. So thank you, Stephanie jokes. You guys got hard news here that you could maybe talk about 46? >>Yeah. Eso eso open shift is our enterprise kubernetes platform. With this announcement, we announced the release of open ship 4.6 Eso eso We're doing releases every quarter tracking the upstream kubernetes release cycle. So this brings communities 1.19, which is, um but itself brings a number of new innovations, some specific things to call out. We have this new automated installer for open shift on bare metal, and that's definitely a trend that we're seeing is more customers not only looking at containers but looking at running containers directly on bare metal environments. Open shift provides an abstraction, you know, which combines Cuban. And he's, uh, on top of Lennox with RL. I really across all environments, from bare metal to virtualization platforms to the various public clouds and out to the edge. But we're seeing a lot of interest in bare metal. This is basically increasing the really three automation to install seamlessly and manage upgrades in those environments. We're also seeing a number of other enhancements open shifts service mesh, which is our SDO based solution for managing, uh, the interactions between micro services being able to manage traffic against those services. Being able to do tracing. We have a new release of that on open shift Ford out six on then, um, some work specific to the public cloud that we started extending into the government clouds. So we already supported AWS and Azure. With this release, we added support for the A W s government cloud as well. Azaz Acela's Microsoft Azure government on dso again This is really important to like our public sector customers who are looking to move to the public cloud leveraging open shift as an abstraction but wanted thio support it on the specialized clouds that they need to use with azure gonna meet us Cup. >>So, joke, we stay there for a minute. So so bare metal talking performance there because, you know, you know what? You really want to run fast, right? So that's the attractiveness there. And then the point about SDO in the open, open shift service measure that makes things simpler. Maybe talk a little bit about sort of business impact and what customers should expect to get out of >>these two things. So So let me take them one at a time, right? So so running on bare metal certainly performances a consideration. You know, I think a lot of fixed today are still running containers, and Cuban is on top of some form of virtualization. Either a platform like this fear or open stack, or maybe VMS in the in one of the public clouds. But, you know containers don't depend on a virtualization layer. Containers only depend on Lennox and Lennox runs great on bare metal. So as we see customers moving more towards performance and Leighton see sensitive workloads, they want to get that Barry mental performance on running open shift on bare metal and their containerized applications on that, uh, platform certainly gives them that advantage. Others just want to reduce the cost right. They want to reduce their VM sprawl, the infrastructure and operational cost of managing avert layer beneath their careers clusters. And that's another benefit. So we see a lot of uptake in open shift on bare metal on the service match side. This is really about You know how we see applications evolving, right? Uh, customers are moving more towards these distributed architectures, taking, you know, formally monolithic or enter applications and splitting them out into ah, lots of different services. The challenge there becomes. Then how do you manage all those connections? Right, Because something that was a single stack is now comprised of tens or hundreds of services on DSO. You wanna be able to manage traffic to those services, so if the service goes down, you can redirect that those requests thio to an alternative or fail over service. Also tracing. If you're looking at performance issues, you need to know where in your architecture, er you're having those degradations and so forth. And, you know, those are some of the challenges that people can sort of overcome or get help with by using service mash, which is powered by SDO. >>And then I'm sorry, Stephanie ever get to in a minute. But which is 11 follow up on that Joe is so the rial differentiation between what you bring in what I can just if I'm in a mono cloud, for instance is you're gonna you're gonna bring this across clouds. I'm gonna You're gonna bring it on, Prem And we're gonna talk about the edge in in a minute. Is that right? From a differentiation standpoint, >>Yeah, that That's one of the key >>differentiations. You know, Read has been talking about the hybrid cloud for a long time. We've we've been articulating are open hybrid cloud strategy, Andi, >>even if that's >>not a strategy that you may be thinking about, it is ultimately where folks end up right, because all of our enterprise customers still have applications running in the data center. But they're also all starting to move applications out to the public cloud. As they expand their usage of public cloud, you start seeing them adopted multi cloud strategies because they don't want to put all their eggs in one basket. And then for certain classes of applications, they need to move those applications closer to the data. And and so you start to see EJ becoming part of that hybrid cloud picture on DSO. What we do is basically provide a consistency across all those environments, right? We want run great on Amazon, but also great on Azure on Google on bare metal in the data center during medal out at the edge on top of your favorite virtualization platform. And yeah, that that consistency to take a set of applications and run them the same way across all those environments. That is just one of the key benefits of going with red hat as your provider for open hybrid cloud solutions. >>All right, thank you. Stephanie would come back to you here, so I mean, we talk about rail a lot because your business unit that you manage, but we're starting to see red hats edge strategy unfolded. Kind of real is really the linchpin I wanna You could talk about how you're thinking about the edge and and particularly interested in how you're handling scale and why you feel like you're in a good position toe handle that massive scale on the requirements of the edge and versus hey, we need a new OS for the edge. >>Yeah, I think. And Joe did a great job of said and up it does come back to our view around this open hybrid cloud story has always been about consistency. It's about that language that you speak, no matter where you want to run your applications in between rela on on my side and Joe with open shift and and of course, you know we run the same Lennox underneath. So real core os is part of open shift that consistently see leads to a lot of flexibility, whether it's through a broad ecosystem or it's across footprints. And so now is we have been talking with customers about how they want to move their applications closer to data, you know, further out and away from their data center. So some of it is about distributing your data center, getting that compute closer to the data or closer to your customers. It drives, drives some different requirements right around. How you do updates, how you do over the air updates. And so we have been working in typical red hat fashion, right? We've been looking at what's being done in the upstream. So in the fedora upstream community, there is a lot of working that has been done in what's called the I. O. T Special Interest group. They have been really investigating what the requirements are for this use case and edge. So now we're really pleased in, um, in our most recent release of really aid relate 00.3. We have put in some key capabilities that we're seeing being driven by these edge use cases. So things like How do you do quick image generation? And that's important because, as you distribute, want that consistency created tailored image, be able to deploy that in a consistent way, allow that to address scale, meet security requirements that you may have also right updates become very important when you start to spread this out. So we put in things in order to allow remote device mirroring so that you can put code into production and then you can schedule it on those remote devices toe happen with the minimal disruption. Things like things like we all know now, right with all this virtual stuff, we often run into things like not ideal bandwidth and sometimes intermittent connectivity with all of those devices out there. So we put in, um, capabilities around, being able to use something called rpm Austria, Um, in order to be able to deliver efficient over the air updates. And then, of course, you got to do intelligent rollbacks for per chance that something goes wrong. How do you come back to a previous state? So it's all about being able to deploy at scale in a distributed way, be ready for that use case and have some predictability and consistency. And again, that's what we build our platforms for. It's all about predictability and consistency, and that gives you flexibility to add your innovation on top. >>I'm glad you mentioned intelligent rollbacks I learned a long time ago. You always ask the question. What happens when something goes wrong? You learn a lot from the answer to that, but You know, we talk a lot about cloud native. Sounds like you're adapting well to become edge native. >>Yeah. I mean, I mean, we're finding whether it's inthe e verticals, right in the very specific use cases or whether it's in sort of an enterprise edge use case. Having consistency brings a ton of flexibility. It was funny, one of our talking with a customer not too long ago. And they said, you know, agility is the new version of efficiency. So it's that having that sort of language be spoken everywhere from your core data center all the way out to the edge that allows you a lot of flexibility going forward. >>So what if you could talk? I mentioned just mentioned Cloud Native. I mean, I think people sometimes just underestimate the effort. It takes tow, make all this stuff run in all the different clouds the engineering efforts required. And I'm wondering what kind of engineering you do with if any with the cloud providers and and, of course, the balance of the ecosystem. But But maybe you could describe that a little bit. >>Yeah, so? So Red Hat works closely with all the major cloud providers you know, whether that's Amazon, Azure, Google or IBM Cloud. Obviously, Andi, we're you know, we're very keen on sort of making sure that we're providing the best environment to run enterprise applications across all those environments, whether you're running it directly just with Lennox on Ralph or whether you're running it in a containerized environment with Open Chef, which which includes route eso eso, our partnership includes work we do upstream, for example. You know, Red Hat help. Google launched the Cuban community, and I've been, you know, with Google. You know, we've been the top two contributors driving that product that project since inception, um, but then also extends into sort of our hosted services. So we run a jointly developed and jointly managed service called the Azure Red Hat Open Shift Service. Together with Microsoft were our joint customers can get access to open shift in an azure environment as a native azure service, meaning it's, you know, it's fully integrated, just like any other. As your service you can tied into as you're building and so forth. It's sold by by Azure Microsoft's sales reps. Um, but you know, we get the benefit of working together with our Microsoft counterparts and developing that service in managing that service and then in supporting our joint customers. We over the summer announced sort of a similar partnership with Amazon and we'll be launching are already doing pilots on the Amazon Red Hat Open ship service, which is which is, you know, the same concept now applied to the AWS cloud. So that will be coming out g a later this year, right? But again, whether it's working upstream or whether it's, you know, partnering on managed services. I know Stephanie team also do a lot of work with Microsoft, for example, on sequel server on Lenox dot net on Lenox. Whoever thought be running that applications on Linux. But that's, you know, a couple of years old now, a few years old, So eso again. It's been a great partnership, not just with Microsoft, but with all the cloud providers. >>So I think you just shared a little little He showed a little leg there, Joe, what's what's coming g A. Later this year. I want to circle back to >>that. Yeah, eso we way announced a preview earlier this year of of the Amazon Red Hat Open ships service. It's not generally available yet. We're you know, we're taking customers. We want toe, sort of be early access, get access to pilots and then that'll be generally available later this year. Although Red Hat does manage our own service Open ship dedicated that's available on AWS today. But that's a service that's, you know, solely, uh, operated by Red Hat. This new service will be jointly operated by Red Hat and Amazon together Idea. That would be sort of a service that we are delivering together as partners >>as a managed service and and okay, so that's in beta now. I presume if it's gonna be g a little, it's >>like, Yeah, that's yeah, >>that's probably running on bare metal. I would imagine that >>one is running >>on E. C. Two. That's running an A W C C T V exactly, and >>run again. You know, all of our all of >>our I mean, we you know, that open shift does offer bare metal cloud, and we do you know, we do have customers who can take the open shift software and deploy it there right now are managed. Offering is running on top of the C two and on top of Azure VM. But again, this is this is appealing to customers who, you know, like what we bring in terms of an enterprise kubernetes platform, but don't wanna, you know, operated themselves, right? So it's a fully managed service. You just come and build and deploy your APS, and then we manage all of the infrastructure and all the underlying platform for you >>that's going to explode. My prediction. Um, let's take an example of heart example of security. And I'm interested in how you guys ensure a consistent, you know, security experience across all these locations on Prem Cloud. Multiple clouds, the edge. Maybe you could talk about that. And Stephanie, I'm sure you have a perspective on this is Well, from the standpoint of of Ralph. So who wants to start? >>Yeah, Maybe I could start from the bottom and then I'll pass it over to Joe to talk a bit. I think one of these aspects about security it's clearly top of mind of all customers. Um, it does start with the very bottom and base selection in your OS. We continue to drive SC Lennox capabilities into rural to provide that foundational layer. And then as we run real core OS and open shift, we bring over that s C Lennox capability as well. Um, but, you know, there's a whole lot of ways to tackle this we've done. We've done a lot around our policies around, um see ve updates, etcetera around rail to make sure that we are continuing to provide on DCA mitt too. Mitigating all critical and importance, providing better transparency toe how we assess those CVS. So security is certainly top of mind for us. And then as we move forward, right there's also and joke and talk about the security work we do is also capabilities to do that in container ization. But you know, we we work. We work all the way from the base to doing things like these images in these easy to build images, which are tailored so you can make them smaller, less surface area for security. Security is one of those things. That's a lifestyle, right? You gotta look at it from all the way the base in the operating system, with things like sc Lennox toe how you build your images, which now we've added new capabilities. There And then, of course, in containers. There's, um there's a whole focus in the open shift area around container container security, >>Joe. Anything you want to add to that? >>Yeah, sure. I >>mean, I think, you know, obviously, Lennox is the foundation for, you know, for all public clouds. It's it's driving enterprise applications in the data center, part of keeping those applications. Security is keeping them up to date And, you know, through, you know, through real, we provide, you know, securing up to date foundation as a Stephanie mentioned as you move into open shift, you're also been able to take advantage of, uh, Thio to take advantage of essentially mutability. Right? So now the application that you're deploying isn't immutable unit that you build once as a container image, and then you deploy that out all your various environments. When you have to do an update, you don't go and update all those environments. You build a new image that includes those updates, and then you deploy those images out rolling fashion and, as you mentioned that you could go back if there's issues. So the idea, the notion of immutable application deployments has a lot to do with security, and it's enabled by containers. And then, obviously you have cured Panetti's and, you know, and all the rest of our capabilities as part of open Shift managing that for you. We've extended that concept to the entire platform. So Stephanie mentioned, real core West Open shift has always run on real. What we have done in open shift for is we've taken an immutable version of Ralph. So it's the same red hat enterprise Lennox that we've had for years. But now, in this latest version relate, we have a new way to package and deploy it as a relic or OS image, and then that becomes part of the platform. So when customers want toe in addition to keeping their applications up to date, they need to keep their platform up to dates. Need to keep, you know, up with the latest kubernetes patches up with the latest Lennox packages. What we're doing is delivering that as one platform, so when you get updates for open shift, they could include updates for kubernetes. They could include updates for Lennox itself as well as all the integrated services and again, all of this is just you know this is how you keep your applications secure. Is making sure your you know, taking care of that hygiene of, you know, managing your vulnerabilities, keeping everything patched in up to date and ultimately ensuring security for your application and users. >>I know I'm going a little bit over, but I have I have one question that I wanna ask you guys and a broad question about maybe a trends you see in the business. I mean, you look at what we talk a lot about cloud native, and you look at kubernetes and the interest in kubernetes off the charts. It's an area that has a lot of spending momentum. People are putting resource is behind it. But you know, really, to build these sort of modern applications, it's considered state of the art on. Do you see a lot of people trying to really bring that modern approach toe any cloud we've been talking about? EJ. You wanna bring it also on Prem And people generally associate this notion of cloud native with this kind of elite developers, right? But you're bringing it to the masses and there's 20 million plus software developers out there, and most you know, with all due respect that you know they may not be the the the elites of the elite. So how are you seeing this evolve in terms of re Skilling people to be able, handle and take advantage of all this? You know, cool new stuff that's coming out. >>Yeah, I can start, you know, open shift. Our focus from the beginning has been bringing kubernetes to the enterprise. So we think of open shift as the dominant enterprise kubernetes platform enterprises come in all shapes and sizes and and skill sets. As you mentioned, they have unique requirements in terms of how they need toe run stuff in their data center and then also bring that to production, whether it's in the data center across the public clouds eso So part of it is, you know, making sure that the technology meets the requirements and then part of it is working. The people process and and culture thio make them help them understand what it means to sort of take advantage of container ization and cloud native platforms and communities. Of course, this is nothing new to red hat, right? This is what we did 20 years ago when we first brought Lennox to the Enterprise with well, right on. In essence, Carozza is basically distributed. Lennox right Kubernetes builds on Lennox and brings it out to your cluster to your distributed systems on across the hybrid cloud. So So nothing new for Red Hat. But a lot of the same challenges apply to this new cloud native world. >>Awesome. Stephanie, we'll give you the last word, >>all right? And I think just a touch on what Joe talked about it. And Joe and I worked really closely on this, right? The ability to run containers right is someone launches down this because it is magical. What could be done with deploying applications? Using a container technology, we built the capabilities and the tools directly into rural in order to be able to build and deploy, leveraging things like pod man directly into rural. And that's exactly so, folks. Everyone who has a real subscription today can start on their container journey, start to build and deploy that, and then we work to help those skills then be transferrable as you movinto open shift in kubernetes and orchestration. So, you know, we work very closely to make sure that the skills building can be done directly on rail and then transfer into open shift. Because, as Joe said, at the end of the day, it's just a different way to deploy. Lennox, >>You guys are doing some good work. Keep it up. And thanks so much for coming back in. The Cube is great to talk to you today. >>Good to see you, Dave. >>Yes, Thank you. >>All right. Thank you for watching everybody. The cubes coverage of Cuba con en a continues right after this.

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Hi, I'm Stew Minimum And and this is the Cube's coverage of Red Hat Summit 2020 course Digital event This year. We're not together at Mosconi, but we are bringing together many of the speakers thought leaders, customers in this very important ecosystem. Really excited to welcome back to our program. Stephanie Cheers. Who's the vice president and general manager of the Red Hat Enterprise Linux business unit inside of Red Hat. Stephanie. So great to see you have to give you a virtual hug high five year, but you know, always great to see and have you on the program. >>Oh, thank you. So it's great to be here, and this is what together means today. But it's great to be together with you >>again. Here it's limit. >>Yeah, the discussion is you talk on it together apart for for a time we talk in tact. That change is one of the only constants that we have, and there are more changes than ever happening right now. So before we get into kind of your B you talk a little bit about, You know, some of the big changes. There's organizational changes, you know, I know we spoke to you about in 2019 at IBM Think and Red Hat Summit because you've worked for both sides of the equation here, Uh, give us kind of the latest from your standpoint. >>Yes, certainly the leadership changes which have been public now for a couple weeks. Those were a big change >>for for us. I think one of the things that has come through is IBM has really been respecting what red hat is. What? Um, what we do. But also how we do it is very important and valued. And we at red Hat >>believe in it so strongly. We're sticking to what Red Hat does best. Everything is open source. Everything is collaborative. And honestly, I have to say it. It >>feels great as a red Hatter to see Jim in the position he's in at IBM Um, Paul's passion, >>which clearly comes across in his keynotes and >>his passion for how we do have an open source development model. It's great to have them now take over the CEO role for Red hat. So it's it's really exciting times. I think. Last year when we spoke, it was, um it was a bit of a wait and see and see what happens. And I think now the recent announcements really solidify this sort of synergy and partnership that IBM and Red Hat have and what our intentions are in the market. But at Red Hat, we still stay red hat, and we're still driving things the way we always have. And that's great. Feels that >>that that's great. And thank you so much for the update. So when we talk about your business unit that the Red Hat Enterprise, Linux, of course, Rehl, um, you know, I've got a little too much history, you know. I go back when it was, whereas, you know, before well and kind of wash the growth of Linux sto become really, you know, the underlying fabric of so much of what we see out there today for all of businesses, so many companies could not exist if it wasn't for Linux. And in the seven years we've been having the Cube, of course, we've really watched that that moved from Lennox to not only be some of the foundations of what's happening in customer's environments, but also a major piece of cloud and cloud. Native S O. You know, give us that up date as to, you know, here in 2020. You know why? You know Linux has been around for quite a long time, but, you know, it's still is relevant. >>Yeah, so that's it. That's a >>great leader and ties exactly to how we look at well in the red hat sort of entire portfolio. Um, when you look at Lenox of how it evolved, it started out as being a bit of a cheaper alternative to units. But it quickly became, because of the open source way and collaborative way it's developed. It quickly became sort of this springboard for innovation because you have all these incredible innovators collaborating upstream. All of that has fed to a whole different view of what Linux is. Is cloud exists because of Linux is containers are just a different deployment mechanism or Lennox workloads, artificial intelligence. All those APS are built on Linux, so it's become this standardized foundation upon which innovation is done today, And for me, that's the most exciting thing, because it red hat and rail. Our goal is to one. Have it just work right? It has >>to be the standard. And, um well, sometimes that can be misinterpreted. It >>is boring or a commodity. It is anything but a commodity. It's probably one of the most strategic decisions that someone makes. Is which Raoul Distribution? Which Red Hat, which Lennox distribution did they use and that really take real pride that it's built for the enterprise? It's build for security. It's built for resiliency, and all of that build it once deploy anywhere, translates into also using all the innovation, all the container ization capabilities, using it across multiple public clouds. So it's really that combination of having it just work, be the foundation of where you build once and then being able to leverage all the innovation that's coming out of the open source world today. >>Yeah, really interesting points. Stephanie, I think back to when we talked for years about the consumer nation consumers, consumer ization. Excuse me of I t and people thought that therefore, there wouldn't be differentiation, you know, just by white box things and everything will be off the shelf. But if you look at how most companies build things, they really hyper optimize that. I need to build what I need. I need to use the tools that are available, and I need to be able to be agile. You know, I want one of my highlights last year talking to a lot of companies going through their digital transformation and a number of them at Red Hat Summit last year where they talked about both the organization and technology changes that they're making to move faster. And, of course, your portfolio is a big piece of helping them move forward. >>And that's one thing we're seeing that that ability to consume, innovation and get the >>most and extract the most out of what they're running today in their data center. As customers transform and take on this digital transformation, it's not just a technology statement. In most cases, it's an organizational statement as well. And how do you bridge both those and move it forward? It's one thing we focus a lot on right with the open innovation labs, with a lot of customers as well, because it's not just about the technology, it's about the way we work in the way we do things as well. >>Yeah. So, Stephanie, you know, every every year or so I hear it's like, Oh, well, we've got a new way to To the operating system. There was the Jeff just enough operating system for for a while when container ization came out, there was little company named core Os. That was like, Oh, we're going to make a thin version or core OS is now Ah, piece of red hat. Um, so still, with the cloud, there's always, you know, we're going to change the way the operating system it's done. Um, we just love your viewpoint as to, you know, Red Hat has, you know, a few options and kind of a spectrum of offerings. But how do your customers think about the OS these days? And you know, how should we be thinking about rail specifically in that overall spectrum? >>No, it's so that's a great question, too. And we look at >>it as Lennox and Rehl is be one thing that stays the same and helps you get the value out of all the work you've already put in all the development work you've already put in. And make sure that that translates to the future, where everything is changing, how you deploy where you deploy what you deploy. All of that may change, but if you want to get the value out of the work in the development that has been done yesterday, you need something to stay the same. In our view, that's real. We build it with um in mind for the enterprise along lifecycle security support. We build all of that into it so that when you build on a rail monorail kernel, you can take that. If you want to deploy it in a container, you can deploy on Rehl itself. Or if you need orchestration, you can deploy it on open shift. And that's part of the reason why you mentioned Core OS. So we now have a rail core. OS is within open shift 4.0, on beyond, of course. But what we did was we tailor down what is. In reality, it's the same packages. It's the same certification, security, all of that work that we put in. We take the core OS piece of it, what's essential and really optimized for open shift. We build that into an immutable image, and it goes out as part of open shift. It's not available separately because it's really tailored. What we pick the life cycle is all matching open shift, >>and what that does >>is provide you on open shift experience. That's easy to update fully across the board, all the way down to the kernel. But you know, it's the same Lennox that you have in rail, >>and it's that consistency >>of technology that we really strive for. Um, same thing in public Cloud. So when you build an image on Prem on REL, you can take that image up into the public cloud. And no, it's the same level of security and it just will work, you know, part of part of my team. And we take a lot of pride in the fact that it will just work on. And while that >>may not sound super exciting, particularly in days >>like like right now, being dependable and being reliable and knowing that it's secure, all of that is really important when you run your business that those those features or anything but commoditized >>Well, yeah, I think one of the real volumes that customers see with real specifically is there's so much change going on there, and you look at the Linux community, you look at what open shifts doing in the Kubernetes community. There's so much coaches going on red hat packages that make sure that you don't need to think about the almost chaos that's going out there in all of those communities. But you packaged those together. So Stephanie rarely was, of course, one of the highlights of last year's Red Hat Summit. So we'd love to hear you know, if you've got any good customer stories, really, the momentum of relate as you've seen it, you roll out around the world as and then we'll talk about the new updates. You have this. >>Yeah, great. So Rehl eight was a big deal for us last year, as you remember, and partly because not >>only all the features and functions, of course, which we put into it, but also because we really wanted to reposition what the value of an operating system is within a data center and within their innovation future. So we really focus all the features and functions into two buckets. One is about how do we help you with the operating system? Run your business better, more efficiently If the most out of the systems you have in the critical workloads that you run today and how do we use the operating system to help you bridge into the next level of innovation? What's coming down the pipeline? Things like containers. >>And we really wanted to >>make sure that, as we see you know, most customers are looking to how they digitally transform. But of course, no one has the freedom to throw away everything they've done in the past. They want to build upon that and get value out of it. So we really focused on balancing those two things now, as we look at. In fact, one of the commitments we made because we heard it from customers was they wanted a more predictable deployment of our minor releases and our major releases. And we committed, um, at the REHL eight launch that we would be delivery minor releases every six months, major releases every three years, and we have held to that. We delivered 816 months after we delivered eight. And now you saw last week we delivered eight dot too. Um, this is what it means for us to stand by our world and be dependable as an operating system. And the beauty of the subscription with well is that if you're a customer and you're running REL seven, particularly in times right now, it's It's not that easy to get into your data center, perhaps. And so if you don't choose to update to eight now, you can stay on seven until that time works. That's to me. That's part of the beauty and the flexibility of the subscription model. We have course want to continue to bring your new capabilities and new features. But the subscription Our goal is to have a value subscription that you can you can get the most value from No matter when you decide to upgrade or no forward with, uh, with a different releases, we have >>Well, you can go. And congratulations on keeping the releases going on schedule. One of the nice things about open source is we can see the roadmap out there. You've made this Ah, this promise and you're keeping to it. So ah is you said the announcements we made has been talked about in the keynote. So give us a couple of highlights. Says what people to be looking at and looking to learn more when they dig into a thought to >>Yeah, great. So we really wanted to stick with a few key >>messages with it, and they do really tie to How do we help you run your business? And how do we help you grow your business? It's one thing that we announced and what we pivoted to, um, with the eight dot io is we >>really moved to? How do we How do we >>deliver what we called an intelligent OS, which means an OS that helps you bridge the gap and brings more value to you in your data center than you got before? One of the key aspects to this was adding in the capability of red hat insights, and we added insights capability into every single rail subscription that is under current support. So whether or not you moved to relate whether you have real seven, if you have a supported version of real six, all of those had insights added to it, and what insights is is a as a service on cloud at red hat dot com and link up your servers, and >>it will give you insight >>into operational capability. Is it configured correctly is it could be optimized for better performance. Where are you on your C V E updates and what it does is take all that knowledge that Red Hat has from all the support cases and things that we're seeing what's happening in the industry, what we're seeing other customers have, and we can even proactively help customers. The feedback on this capability has been huge. In fact, you'll see in the announcement last week we've added a lot of new capabilities into this specifically For that reason we've had customers, you know, it's like having it's like having more ops people on my team because I'm getting this input in directly from Red Hat for things to look at. And so that, to me, was probably one of the key aspects that, as we look from going to eight into eight dot too, how do we build up that capability? And of course, last week you saw we added a lot to that, and I think now more than ever, we want to make sure that everyone who has a real subscription is getting the most value out of that and I think insights is one of the places where if you have a subscription and, um, you can value or you can get more value from operational help, insights is a place where we want to help you. Um, we everything we had prior we have now bucket sized into a capability and insights called advisor is really about performance, stability and security and doing an analysis for you. We've added a new capabilities around vulnerability, Right. How do you re mediate common vulnerabilities and exposures, compliance aspect, patch aspect policies and drift? Um, kind of all of those we've now bucket it in into that insights capability. So this friends a lot more value to something that we have already seen. Customers say, You know, we didn't expect to get this amount of input and continuous growth because we constantly add new new rules into that engine. And so you know what? What we what we knew yesterday will be what we know tomorrow, and we look forward to sharing with that with everyone >>who has a subscription. So this is >>a place where I think it's ah, it's an important place for folks to look, particularly now because operational efficiency is really key. And security is really we have a lot of capabilities in both. What? Yes, Please, >>please, please, go ahead. Now, >>one other aspect on that that I wanted to mention >>was we also added a capability called subscription watch and subscription Watch helps you get a very simple, clean view of all the subscriptions you have and where they're running. And that was one thing that we saw. Customers say there was friction. And how do I know where my entitlements are? How I'm using them across my entire enterprise Corruption watch can help with that. So, um, this sort of cloud dot red hat dot com capability that we can assist with and is already part of your subscription. These are the kinds of things that we really want to help augment this to make Really intelligent os for the enterprise. >>Yeah. Stuff Stephanie. The comment I was gonna make is there's certain shows that I go to that every year. You go to it, You say Okay, it's a little bit bigger. They announce something. They made some progress on it. What has impressed me most about going to the red Hat show year after year is really the the growth of the of the portfolio, if you will. So when I first started going to it, it was, you know, a lot of the people there were, you know, the hard core Linux people. Um And then, you know, there's some storage people, some networking people is cloud containers really grew. It really blossomed into this really robust ecosystem. Oh, and growth there. So would love just to get your viewpoint on, you know, the skill set because, you know, I'm sure there's plenty of companies out there that are like, Well, you know, I've got some people that are, you know, my limits people, and they do things that aren't there. But, you know, how do you see kind of the skill set and what what Red Hat's doing really permeating more and more of, of companies, day to day activity. >>I think one of the things that I'm >>most proud of is even since last year's all the deeper collaborations we have between the various product lines. Certainly we'll talk with Joe Fitzgerald, and he and I work together very closely. Capabilities like insights. How do we add answerable capabilities directly into real. And what that does is really help. I think in any customer today, skills is probably one of the biggest concerns that they have. How do they grow those skills? How do they help folks grow and learn more and progress into the innovation areas? But clearly they still need their their mission critical applications to run and how do they span that? And I think what we're really trying to do is be able to bring the strength of the portfolio together to help a customer have more flexibility in how they leverage their skills and how they grow their skills. >>Because I think coming back to >>that statement that that you made earlier it's not just about technology. It's about how, if >>you really want to be, have agile, it's about >>how a company has organized. And I think we're hoping that we bring together the strength of the portfolio so that a customer is able todo leverage their organization and leverage their skills and the best way possible. I think another place where we worked hard on eight dot too. Some similar lines of bridging the portfolio was, you know, we announced back in eight dot io. We were putting container ization tools directly in Terrell with build a pod made in scope e 08 dot too. We brought in the newest versions of Scope EO and Build Up. In fact, in tech preview, you get containerized versions of those, and so we're continuing to add. What we are seeing is the container ization is a journey for customers. Many customers just want to deploy a single container on a server. Or they were. They want to deploy a single container in a VM Um, they're not ready for orchestration. We wanted to put the tools in so that a customer could do that on REHL. Get started, get those containers deployed on REHL. Put those tools directly, and we added it to old protocol, which is a tool built for security. It brings that security of SC Lennox and brings that up and adds value at the container level. It's those kinds of things as you see the bridge from well into open shift. How do we help a customer rich? That skill journey as well along that path and I think right now in kubernetes and Containers skills is a is a big, big area of focus, so the more we can help ease that across the portfolio and bring those things together is really important. And I know we're working very closely with the chefs in the, um and the team there in order to help bridge that. >>Excellent. Stephanie, I just want to give you the last word. We talked a lot about the ongoing journey that customers are going through. So give us your final take away as to how customers should be thinking about red hat in general and role specifically as their journey goes forward. >>I think I think one of the things >>we're very proud of here at Red Hat is that we always, particularly in the open source communities with our customers, with our partners, we want to roll up our sleeves and help, and that's we want. So, developer, we wanna work upstream with you. It's one of the things we're very proud of, and now, particularly in this time it's We want to make sure that folks understand we're here to help, and we want to make sure that you're getting the most out of the subscriptions you have, Um, and we help. We help you on that journey both to get the most out of you can out of your data center today. But also be ready for the innovation that you want to consume going forward. And we're collectively working across red Hat in order to make that happen. But it's, um >>even though this is different and it's there the virtual Experience edition of Red Hat Summit. It's >>great to be together and be able to share the whole message. >>Well, Stephanie, the open source community is definitely used to collaborating remotely. So thank you so much for joining us. It's a pleasure to see you. And we would hope to talk again soon. >>Great to see you too. Thank you for the time. >>Alright. You're watching the Cube's coverage of Red Hat Summit 2020 digitally with remote guests from around the globe. Instrument a man and thank you for watching the Cube. >>Yeah, yeah, yeah.