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

>>live from Atlanta, Georgia. It's the Q covering answerable Best 2019. Brought to you by Red Hat >>Hey, welcome back, everyone. This is the Cubes. Live coverage here in Atlanta, Georgia, for Ansel Fast, part of Red Hats Annual event with their customers, their community. I'm Chon hurry with the Cuban stupid men. My co host. Our next guest is Jason Smith, vice president. North America Service is for Red Hat. Jason, welcome to the Cube. >>Thanks. Thanks for having me. >>So mostly the service is wrapped around this or huge opportunity because of the impact that the automation is having the tasks people's jobs shift on the things they can do, more things. That service is opportunity, bigot. You just take us through kind of your strategy of how you look at answerable in context of the red hat portfolio. >>Sure, yeah. So from the service's perspective, we're really responsible for ensuring customer success and sex successful adoption of all of our technologies. So across the entire portfolio and so as opposed to a service. This company that's focused on surfaces were really focused on driving customers success and making sure that customers were successful so overall, from the service's perspective we have obviously are consulting, which really focused on working with customers. Implement solutions around red technology is expanding the use of redhead technologies. We have our training business, which is our education and certification business, which has on sites, open enrollment. But also over the last couple years we released our Red Hat Learning subscription, which is basically gives customers access to the entire portfolio of training on demand in the self paced way, which is been really fast growing part of our business. And then I think we've talked to you a little bit about this before, which is our open innovation labs, which is really focused on people in process and helping customers go through that digital transformation type of journey and focus around culture and things like that. >>It's interesting you look at the interviews we had yesterday with some of your customers. It's actually have a couple different profiles. You have the man. We nailed it. Now I gotta bring us across the entire organization, get a champion driving change. Other groups are standardized with that substrate for answerable. Others were like, Wow, I have other stuff. I need to really figure this out, take us through how you guys would approach those use cases because they're different. But all would want more. Service is some to accelerate either, say a champion, some to get a new prospect on board. >>Right? So, um, we've laid out We'll release is about 90 days ago, which is called Dark Automation Adoption Journey. And this is a five phased approach where we've worked with customers hundreds of customers around the world, in every phase of adoption of automation, obviously specifically around answerable. And this really looks at helping customers go from more of a tactical strategy, typically is what we're seeing today. A lot of customers have and school in different pockets, doing a lot of tactical things that are driving a lot of value. But how do you take that? And then really get two more of an enterprise strategy? So that's really what we've focused on taking what we've learned with customers at all of those phases and really taking those best practices and coming up with a standardized approach that we can really work with customers to be ableto get through that journey with him. >>Jason could bring us inside the customer base a little here. You know, what we hear is it's really easy to get started. But when you lay out those five steps is everybody looking to get to st five? Is that a, you know, year journey? Are some people okay? Just being at phase two or three. Help us understand a little bit, Kind of. And we know it varies greatly, but some of the characteristics as toe how fast they move along where the end journey is for most organizations, >>right. So as I mentioned this, customers are coming in. Some have been early adopters of answerable for a long time. So we've been working at more of a department departmental level with customers where they're driving value at that departmental level. Others were kind of coming to us for the first time, saying we're hearing all about this automation stuff. We know we need it, but we need to get started. And so we're really looking at, um, kind of starting out. We typically start with the Discovery session, and so we're bringing in our architects and consultants to come in and meet with their business and technical stakeholders to really understand where they are in that journey and really defined kind of their goals and objectives. So every customer is different, so really understanding what their goals and priorities are and then being able to help kind of craft that road map with, um to get through that journey. But I'd say most of our customers looking to figure out how to take it from kind of more of those tactical implementations to how do we leverage that in a more scalable, consistent way and be able to manage it more across the enterprise? >>Well, it's a direct software development often is different at different, different parts in an organization. If you look a kind of a dev ops movement, it's, you know, trying to get a little bit consistency across those, and it sounds like answerable plays well, toe help get collaboration and you know those playbooks that could be used across and know that I have something that is supported and works, and my organization buys into it >>exactly. So a lot of customers air doing great things in those pockets. But like you said, how do you take those and not reinvent the wheel every time but take them and kind of break them down into consumable chunks, kind of validate those and then publish them. So you have a standard set of playbooks that people can use and reuse versus developing them again for the first time. Because we know that answerable. You can do things quickly, but you don't want to redo them 10 different ways to do the same thing. So having that kind of blessed standardized way and then publishing them out managing them is really important. >>Great feedback from customers on that two on. Then they get more playbooks to get more. I gotta manage that. But one of the interesting things we talked about yesterday with Stephanie Cheers with on the rail side was connecting, answerable to rail the insights. Was the analytics certainly compelling? A lot of benefits scare coming into the rest of red hat. Well, where is that opportunity? How do you guys servicing those pieces? >>Yes, so we're really looking at answerable to be part of most of the red hat portfolio. So as we're working with customers and they're adopting more and more of the Red Hat technologies, answerable becomes a bigger part of that. So whether it's kind of bringing in our training to help train and enable customer associates on using answerable not only for automation but whether you're a real admin or open shift, or no matter what kind of product you're using, being ableto have the training enablement and service is around that to help everyone learn to understand how to use an school in leverage danceable across any area of the plot. >>You guys aren't new to platforms. Answer would have been a great product. Now the platform approach, any things you guys are gonna do different is going to the same Red Hat playbook dealing with other platforms like Open shift in other things. You guys been successful with similar playbook for you guys, or what's the? Is there a nuance with the platform of sensible automation? Ours business as usual? >>Yes. From the service's perspective, we've tried to really standardize on a set of offerings, um, and leverage kind of a consistent approach, whether it's with open shift for helping customers adopt containers or helping customers build a hybrid cloud. Or we've even got a adoption journey around huts for Tokyo's the leverage to create an NFI architecture. It's the same kind of process and framework. So we try to build a standardized process and no matter kind of what type of solution customers air building We look to follow those types of >>dreams. Nice glue layer kind of fits everywhere on a personal question for you. What's the show been like here for you share with the people watching who weren't here? Why is this year important? This seems to be an inflection point for answerable fest, the vibe, the number of attendees, the moment in history where the cloud journey on premises What's What's your take on? This is your personal view. It's >>been great. I mean, I think just the size talking a lot of people that have been coming here for many, many years, even prior to the redhead acquisition of Answerable. This is really community driven event, and it's still set up like a community driven event. You won't see a big red hat stuff everywhere. It's really kind of by the community for the community. And just to see the sheer size of on the number of attendees here, and really kind of the evolution of what customers are being able to talk about on stage with a value they're getting out of answerable is pretty tremendous. So just seeing the pure return on investment of leveraging, answerable and looking at all of the large customers they're here, speaking even on the panel last night was really incredible to see them talk about their journeys over the last couple of years, going from just starting to be work with, answerable to really kind of driving that across the enterprise and getting continually >>local on feedback. But they're also vocal on success. They have all these building in champions inside your inside the customer base, >>and they're all very, very excited about when you have excited customers. >>So, Jason, I'm wonder if you could help us connect the dots with how automation ties into the other journeys customers are going through. You know, the digital transformation, modernizing their applications, changing their hybrid and cloud hybrid and multi cloud environment. What's the role of automation to, you know, enable that and participate in those journeys? >>Yes, it's and it really has kind of a part in all of those journeys. So we work with lots of large customers that are going through a kind of different parts of those different journeys, and it seems like ants will becomes a part of it. And so, for instance, one of our customers that working we're working with right now through a large digital transformation, kind of across the entire enterprise from a both people process and technology perspective on this is leveraging things like open shift and modernizing all of their applications and breaking down things in the micro Service's and really transforming their business. But part of that is leveraging, answerable. And so one of the CEOs mottoes was, If we do something more than twice, we're gonna automate it. And so I hear that kind of over and over again, no matter what type of customer we're working with, no matter what type of kind of solution we're implementing, they're coming up with these monsters that they get really excited about around automation. Um, so we're not going to do things the old way with these new projects. We wanna automate everything, and I just seeing a ton of value and efficiency out of it. >>Awesome. What's the biggest surprise that you've seen over the past year on the service aside and just in terms of enterprise readiness Enterprise and appetite. Adoption, Any observations you could share around what's going on with automation, Observe, ability, a big part of the business. We're seeing that, too. Automation Observe ability to hot new sectors. Just exploding opportunity. >>Yeah, I think just continuing to see this kind of digital transformation effort across so many different customers and get everybody's really focused on not only the technology and the technology, especially things like open shift in Ansel and Rail. They're enabling all of this change in all of this movement to the cloud and the automation, but really working with customers to focus on the people in process so they can leverage those capabilities because just adopting the platforms doesn't give you all of the benefits without changing your people in process. So we spent a lot of time talking about really around the culture, and customers are looking at us saying Red Hat Service's Don't just come in with the technical experts would help us really understand how we transform our people in process along the way to really take advantage of the innovation that's going around right now with the cloud. >>So, Jason, uh, IBM Zach Wizard Read had been very clear keeping the brand, the products, the people of Red Hat. IBM knows a thing or two about service is though we think that, you know, service is really are the main focus that that will happen there. So give us a little insight as to how the scale of IBM will increase what redhead service is able to be able to dio. >>Yeah, So it's great for Red Hat, right? Because we now have a company the size of IBM out driving the adoption of our technologies. So everything that we're able to dio to date from a red hat perspective got us to one level of scale. But IBM is gonna take us to that next level of scale. And from a service's perspective, IBM already has service's departments around all of their different technologies. And so we really are gonna be treated kind of service department. So we're gonna continue to be the experts around Red Hat Technologies. But it really doesn't change that much for us because we worked with large s eyes. Um, since the time we started here and were always part of a lot of largess, I implementations so although IBM will be a very important partner of ours. They won't be on. The other part of the only partner will still work with all >>the flights. IBM That's right. And so we worked at >>IBM before the acquisition as a partner will work with him after the acquisition. But IBM What will change is on the IBM side, they will be building much larger delivery organizations around Red Hat Technologies, which will allow us to kind of get the the customer started on that journey. But when they look to really scale out than IBM can take in and kind of take that to the next level, that we would never have the scale to be able to get to that side. So it's good for us. It's good for our customers, and it's good for red hat driving adoption. >>Jim pointed this out on the many times on multiple calls around the broad portfolio. You guys have an IBM. They have somewhere broad portfolio. Thanks for coming on, sharing your insights. What's new for you? Take a quick minute to plug in what's going on your organization and what you're up to? >>Yes, So we're just continuing to scale. So, um The good news is IBM has a large service's organization, but that also drives a lot of demand for us. So we're continuing to scale, will continue to improve. Our offerings were continuing to help our customers reach those goals, moving to the cloud and everything they're looking to try to accomplish. >>Great. Thanks for coming. I appreciate it to Cuba. Coverage here. Danceable fast. I'm John for a student. Stay with us. More day, too. Live coverage after this short break.