>>The queue presents Coon and cloud native con Europe, 2022, brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Valencia Spain and Coon cloud native con Europe, 2022. I'm Keith towns, along with Paul Gillon, senior editor, enterprise architecture, Silicon angle. We are going to talk to some amazing folks, especially in today's segment. Paul there's a lot of companies here, like what what's been the, the consistent theme you've heard so far in the show. >>Well, you know, one thing that's different from this show, it seems to me than others I've attended is it's all around open source. We're not seeing a lot of companies bringing new proprietary technology to market. We are seeing them try to piece together, open source components with some kind of, perhaps there's a proprietary element to it, but to create some kind of a, a common management interface or control plane, and that's quite different from what I think we've seen in the past and open source business models have been difficult to make work historically. And these companies are all taking their, their own approaches to it. But I think the, the degree to which this, the people here of coalesced around the importance of open source is building blocks to the future of, of applications is something I've not seen quite this way before. >>Well, with our current segment guests, we're gonna go deep into kind of these challenges and how enterprises are addressing, and their partners are addressing with those challenges we have with us, a flower head of cloud native HCL technologies. We'll get into how a system integrator is helping with this transition to Ramon neon, senior product manager, redhead. Welcome to the show. You're now cute. Alum. Welcome. >>Thanks for having us. >>So we're gonna get right off, off the bat. We're gonna talk about this. What are some of the trends you're seeing when it comes to application migration? You've done, I'm assuming at this point, thousands of them, what are some of the common trends? >>Well, it's a very good question. And clearly a C we've helped thousands of clients move tens of thousands of applications to what we would call a cloud native, you know, environment. I think the overwhelming trend that we're seeing of course is clients realize it's a particularly complex, sophisticated journey. It requires a certain set of skills and capability clients increasingly asking us for anything that we can do to simplify and accelerate the journey, cuz what's really important to clients. If you're on a transformation journey to cloud is you wanna see some value very quickly. So I don't wanna wait three to five years to transform my applications portfolio. If you can do something in three to five days, that would be perfect. Thank you. >>Well, three to five days, that sounds more akin to when we were doing P to V or V to V migrations, I'm sure HCL is at this point done in the millions of those types of migrations. What are some of the challenges or the nuance in doing a traditional migration from a traditional MI monolithic application to a cloud native? >>Well, it's another good question. Of course you notice that there's a general trend in the industry. Clients don't really want to lift and shift anymore. Lift and shift doesn't really bring any transformational value to my, to my company. So clients are looking for increasingly what we could call cloud native modernization. I want my applications to really take advantage of the cloud native environment. They need to be elastic and kind of more robust than maybe before now in particular, I think a lot of clients have realized that this state of Nirvana, which was we're gonna modernize everything to be a cloud native microservices based application. That is a tremendous journey, but no client really has the time patient or resources to fully refactor or rearchitect all of their applications. They're looking for more immediate kind of impact. So a key trend that we've seen of course is clients still want to refactor and modernize applications, but they're focusing those resources on those applications that will bring greater impact to their business. >>What they now see as a better replacement for lift and shift is probably what we would call replatforming, where they want all of the advantages of a cloud native environment, but they haven't necessarily got the time to modernize the code base. They wanna refactor to Kubernetes and re replatform to Kubernetes in particular, and they want us to take them there quickly. And that's why, for example, this week at cuon eight sellers announced a new set of tools called KMP based on conveyor, an open source project supported by red hat. And the key attraction of KMP is it lets me replatform my applications to Kubernetes immediately, right? Within two or three minutes, I can bring an application from a legacy platform directly onto Kubernetes and I can take it straight into production. That's the kind of acceleration that clients are looking for today. Isn't >>That just a form of lift and shift though? >>Well, no lift and shift typically of course, was moving virtual machines from one place to another. You know, the focus of Kubernetes of course is containerization of solutions. And it's not just about containerizing the solution and movement. It it's the DevOps tool chain around the solution as well. And of course, when I take that application into production in a Kubernetes based environment, I'm expecting to operate it in a different way as well. So that's where we see tremendous focus on what we would call cloud native operations clients expecting to use practices like site reliability engineering, to run these replatformed applications in a different way to, >>It sounds like you're saying, I mean, replatforming has been a, a spectrum of options. I think Gartner has seven different types of platforming. Are you seeing clients take more mature attitude now to replatforming? Are they looking more carefully at the characteristics of their legacy applications and, and try to try to make maybe more nuanced choices about what to replatform, what to just leave >>Alone? I think clients and I I'm sure Ramon's got some comments on this too, but clients have a lot more insight now in terms of what works for them. They they've realized that this, this promise of maybe a microservices based applications estate is a good one, but I can't do that for every application. If I am a large enterprise with several thousand applications in my portfolio, I can't refactor everything to become microservices based. So clients see replatforming possibly it's a middle ground. I, I get a lot of the advantages from a cloud native environment. My applications are inherently more efficient, hopefully a lot more performance. >>Yeah. It's, it's a matter of software delivery performance. Yeah. So legacy workloads will definitely benefit from being brought into Kubernetes in the software delivery per performance department. So it's a matter of somehow revamping your, your legacy applications and getting the benefits in, in life's application, life cycle management, a full tolerance and all that stuff. It's about leveraging the, what Kubernetes offers. >>When you say bringing legacy applications into Kubernetes. It's not that simple, right? I mean, what's involved in doing that. >>It, it, isn't, it's just a matter of taking a holistic view at your application portfolio and understanding the nuance sets of each application type within your organization and trying to come up with a suitable migration strategy for each one of these application types. And for that, what we're trying to do is provide a series of standardized tools and methodologies from a community perspective, we created this conveyor community. It, it was kick started by red hat and IBM, but we are trying to bring as many vendors and GSI as possible to try to set up these standards to make these road towards Kubernetes as easy as >>Possible. So we've done a little bit of app modernization in the CTO advisor hybrid infrastructure. And one of the things that we've found is there's plenty of Avan advantages. If I take a monolithic application that has that I've traditionally had to scale off to game performance, I can take selective parts of that, and now I can add autoscaling to it. Exactly. However, as I look at a landscape Allen of thousands of applications, I need to dedicate developer resources to get that done in my traditional environment. But my traditional environment is busy building new. My traditional or my developers are building new applications and new capabilities. I just don't have the resources to do that. How does HCL and red hat team together to kind of fast track that capability? >>Well, I'll comment on two things in particular, actually the, the first thing when it comes to skilling, I think the thing that's really surprised us at HCL is so many of our clients around the world have said, we are desperately short of skills. We cannot hire ourselves out of this problem. We need to get our existing developer community reskilled around platforms like OpenShift, conveyor, and other projects too. So the first thing that's happened to us at eight seal is we've been incredibly busy undertaken, probably what we would call developer workforce modernization, right? Where we have to help the client reskill their entire technical and developer community to give them the skills, right. So we will help the clients develop a community, build the cloud native understanding, help them understand how to modernize tools for example, or applications. But the second thing I mention is, and this comes back to a comment the Ram made around around conveyor. >>It's been really encouraging to see the open source community, start to invest in building the supporting frameworks around my kind of modernization journey, because if I'm a developer that's reskilling and I'm attempting to maybe modernize an application, being able to dip into an opensource project, I mean, a good example would be tackled part of the conveyor project. Exactly. You now have open source based tools that will help you analyze your applications. They will go into the source code and they will give the developer guidance in terms of what would be effective treatments to undertake. So perhaps a development team that are new to this modernization journey, they would benefit from a project like conveyor, for example, exactly because I need to know where can I safely modernize my application now for experience organizations like HCL that comes naturally to us, but for people who are just starting this journey, if I can take an open source tool like tackle or the rest of conveyor, for example, and use that to accelerate my journey, it takes a lot of pressure off, off my organization, but it also accelerates the journey too. And >>It's not just a matter of, of tooling. We we're also, opensourcing the, the modernization methodology that we've been using in red hat consulting for years. So this whole conveyor communities, it's all about knowledge sharing on one hand and building a set of tools together based on that knowledge that we are sharing to make it as easy as possible. >>And what role does red hat play in all that, I mean is your, your, you you've carved out this position for yourself as the, as the true open source company. Is that, does that position you for a leadership role in helping or companies make this >>Transition? I wouldn't say we should be leading the whole thing. We, we kick started it, but we want to get other vendors on board for this thing. One cool thing about the Camra community is that IBM is opensourcing a lot of their IP. So IBM research is on board. In this thing, we have some really crazy stuff related to a AI being applied to application analysis. We have some machine learning in place. We have very cool stuff that has been sitting on a, on a corner in IBM research for quite some years that now it's being open sourced and integrated in a unified user experience to streamline the modernization process as much as possible. >>So let's talk about the elephant of the room. HCL was leading the conversation around cloud Foundry circa five plus years ago. And as customers are thinking about their journey to cloud native, how should they think about that cloud Foundry to cloud native or Kubernetes replatform? >>Well with within the cloud Foundry community, we've, we've been quite staunched supporters of Kubernetes for quite some time, right? It's, it's quite a, a stated intent of the cloud Foundry foundation to, to move across to Kubernetes platform right now that is a significant engineering journey for cloud Foundry to take. Now we're in this position where a lot of large users of cloud Foundry have a certain urgency to their journey. They, they want to consolidate on a single Kubernetes based infrastructure. We, we see a lot of traction around OpenShift, for example, from red hat in terms of its market leadership. So a lot of clients are saying we would like to consolidate all of our platforms around a single kind of Kubernetes vendor, whether that's red hat or anyone else, you know, quite frankly. So what HCL is doing right now with the tools and the solutions we've announced this week is we're simply accelerating that journey for clients. If I've got a large installed base of applications running in my cloud Foundry environment, and I've also started to invest in standardize on Kubernetes place platforms like OpenShift, most clients would see it as quite a sensible choice to now try and consolidate those two environments into one. And that's simply what we're doing at HCL. We're making it very, very easy. In fact, we fully automated the journey so I can move all of my applications from cloud Foundry into for example, OpenShift pretty much immediately, and it just simplifies the entire journey. >>So the, as we start to wrap up the segment, I like to know customer stories. What, what, how customers either surprised or challenged when they get into, even with the help of an ACL in redhead, why are they seeing the most difficult parts of their migrations? >>Well, my, my simple comment would be maybe complexity, right? And the, the associated requirement for skilled people to undertake this modernization work, right? We spoke about this, of course, in terms of clients now are a lot more realistic. They understand that their ambition now needs to be somewhat tempered by their ability to sort of drive modernization quickly. So we see a lot of clients when they look at their very large global portfolios of applications, they're trying to invest their resources in the higher priority applications, the revenue generative applications in particular, but they have to bring everything else with them as well. Now, a common kind of separation point was we see a lot of clients who might say I'm gonna properly modernize and refactor, maybe five to 10% of my portfolio, but the other 90% also needs to come on the journey as well. And that's really where replatforming in particular kicks in. So, so the key trend again, is, is clients send to us, I've gotta take the entire journey. All right, I've got the resources and the skills to really focus on this much of my application base. Can someone simplify the overall journey so I can afford to bring everything on a cloud native journey? >>So the key to success here is having a holistic view at the application portfolio, segmenting the application portfolio in different application types and ordering the, the priorities of these application types and come up with suitable migration strategies for each one of them is >>Really necessary to move everything though. >>Not necessarily, no. Yeah. Or not necessarily. Yeah, absolutely not everything, but it would make sense. As we were saying before, it will definitely move, make sense to move legacy applications towards Kubernetes, to leverage all the software delivery. >>That's, that's a big project, right? >>It is. >>If you're gonna restructure the application around eight API and microservices, >>That it should be taken the way I've seen organizations succeeding the most in these road towards cloud native and Kubernetes in general is trying to address the whole portfolio. Maybe not move everything, but try to have this holistic view and not leave anything behind. Because if you try to do this isolated initiatives of bringing these or that application in, in isolation, you're Def you, you will miss part of the picture and you might be doomed to fail >>There. Yeah. It's been my experience that if you don't have a plan to migrate your applications to a cloud native operating model, then you're doomed to follow lift and shift examples to the public cloud. Yeah. Whether you're going to any other clouds, if you don't make that, that operational transition. Last question on operational transition, we've talked a lot about the replatforming process itself. What about day two at the I've landed to the cloud? What are some of the top considerations for, for compliance op observability? Just making sure my apps stay up in transitioning my workforce to that model. >>I think the over, you know, the overarching trend or theme that, that I see is clients now are, are asking for what I would call cloud native operations. Now in particular, there's a very solid theme around what we would call reliability engineering. So think about site reliability, engineering, SRE platform, reliability engineering, PR E. These are the dominant topics that clients now want to engage HCL on in particular, because the point you make is a valid one. I've modernized my application. Now I need to modernize the way that I operate the application in production. Otherwise I won't see those benefits. So that general theme of SRE is keeping us really busy. We're busy, re-skilling all of those operations teams around the world as well, because they need to know how to run these environments appropriately >>Too. And also being able to measure your progress while your transitioning is important. And that's one of the concerns that we are addressing as well in the community with a called polars to, to measure and to effectively measure the software delivery performance of, of the organization after the transition has been done. >>And this is a really good point by the way, cuz most, most people think it's a bit of a black art. How do I understand how I modernize my application? How do I understand how I've improved my kind of value chain around software creation and many people thought you needed to bring in very expensive consultants to advise you on these, on these black lives? No, >>Definitely >>Not. But in open source projects like conveyor from, from red hat, the availability of these tools available on an open source model means exactly any engineer, any developer can get these tools off the shelf and get that immediate benefit. >>Well, a flower head of creative labs at HCL at Ramon neon, senior product manager, redhead. Thank you for joining the Q you now cube alum. You'll have a nice profile like the profile pictures on here. Awesome. Absolutely. Thank you. From Valencia Spain. I'm Keith towns, along with Paul Gillon and you're watching the cue, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Valencia Spain and Coon cloud native con Europe, 2022. I'm Keith towns, along with Paul Gillon, senior editor, enterprise architecture and Silicon angle. We are going to talk to some amazing folks, especially in today's segment. Paul, uh, there's a lot of companies here, like what what's been the, the consistent theme you've heard so far in the show. >>Well, you know, one thing that's different from this show, it seems to me than others I've attended is it's all around open source. We're not seeing a lot of companies bringing new proprietary technology to market. We are seeing them try to piece together, open source components with some kind of, perhaps there's a proprietary element to it, but to create some kind of a, a common management interface or control plane, and that's quite different from what I think we've seen in the past open source business models have been difficult to make work historically. Uh, and these companies are all taking their, their own approaches to it. But I think the, the degree to which this, the people here of coalesced around the importance of open source is building blocks to the future of, of applications is something I've not seen quite this way before. >>Well, with our current segment, guess we're gonna go deep into kind of these challenges and how enterprises are addressing, and their partners are addressing with those challenges we have with us, a flower head of cloud native HCL technologies. We'll get into how a system integrator is helping with this transition to Ramon neon, senior product manager, redhead. Welcome to the show. You're now cube alum. Welcome. Thanks for having us. So we're gonna get right off, uh, off the bat. We're gonna talk about this. What are some of the trends you're seeing when it comes to application migration? You've done, I'm assuming at this point, thousands of them, what are some of the common trends? >>Well, it's a very good question. And clearly ACL we've helped thousands of clients move tens of thousands of applications to what we would call a cloud native, um, you know, environment. I think the overwhelming trend that we're seeing of course is clients realize it's a particularly complex, sophisticated journey. It requires a certain set of skills and capability clients increasingly us for anything that we can do to simplify and accelerate the journey, cuz what's really important to clients. If you're on a transformation journey to cloud is you wanna see some value very quickly. So I don't wanna wait three to five years to transform my applications portfolio. If you can do something in three to five days, that would be perfect. Thank you. >>Well, three to five days, that sounds more akin to when we were doing, uh, P to V or V to V migrations. I'm sure. Uh, HCL is at this point done in the millions of those types of migrations. What are some of the challenges or the nuance in doing a traditional migration from a traditional MI monolithic application to a cloud native? >>Well, it's another good question. Of course you notice that there's a general trend in the industry. Clients don't really want to lift and shift anymore. Lift and shift doesn't really bring any transformational value to my, to my company. So clients are looking for increasingly what we could recall, cloud native modernization. I want my applications to really take advantage of the cloud native environment. They need to be elastic and kind of more robust than maybe before now in particular, I think a lot of clients have realized that this state of Nirvana, which was we're gonna modernize everything to be a cloud native microservices based application. That is a tremendous journey, but no client really has the time patient or resources to fully refactor or rearchitect all of their applications. They're looking for more immediate kind of impact. So a key trend that we've seen of course is clients still want to refactor and modernize applications, but they're focusing those resources on those applications that will bring greater impact to their business. >>What they now see as a better replacement for lift and shift is probably what we would call replatforming, where they want all of the advantages of a cloud native environment, but they haven't necessarily got the time to modernize the code base. They wanna refactor to Kubernetes in re replatform to Kubernetes in particular, and they want us to take them there quickly. And that's why, for example, this week at cuon eight sellers announced a new set of tools called KMP based on conveyor, an open source project supported by red hat. And the key attraction of KMP is it lets me replatform my applications to Kubernetes immediately, right? Within two or three minutes, I can bring an application from a legacy platform directly onto Kubernetes and I can take it straight into production. That's the kind of acceleration that clients are looking for today. Isn't >>That just a form of lift and shift though? >>Well, no lift and shift typically of course, was moving virtual machines from one place to another. You know, the focus of Kubernetes of course is containerization of solutions. And it's not just about containerizing the solution and moving it. It's the DevOps tool chain around the solution as well. And of course, when I take that application into production in a Kubernetes based environment, I'm expecting to operate it in a different way as well. So that's where we see tremendous focus on what we would call cloud native operations clients expecting to use practices like site reliability engineering, to run these replatformed applications in a different way to, so >>It sounds like you're saying, I, I mean, replatforming has been a, a spectrum of options. I think Gartner has seven different types of re-platforming. Uh, are you seeing clients take more mature attitude now toward replatforming? Are they looking more carefully at the characteristics of their legacy applications and, and trying to try to make maybe more nuanced choices about what to replatform, what to just leave >>Alone? I think clients and I I'm sure Ramon's got some comments on this too, but clients have a lot more insight now in terms of what works for them. They they've realized that this, this promise of maybe a microservices based applications estate is a good one, but I can't do that for every application. If I am a large enterprise with several thousand applications in my portfolio, I can't refactor everything to become microservices based. So clients see replatforming possibly is a middle ground. I, I get a lot of the advantages from a cloud native environment. My applications are inherently more efficient, hopefully a lot more performance. >>Yeah. It's, it's a matter of software delivery performance. Yeah. So, uh, legacy workloads will definitely benefit from, uh, being brought into Kubernetes in the software delivery per performance department. So, uh, it's a matter of, uh, somehow Rebump your, your legacy applications and getting the benefits in, in life's application, life cycle management, a, uh, full tolerance and all that stuff. It's about leveraging the, what Kubernetes offers. >>When you say bringing legacy applications into Kubernetes. It's not that simple, right? I mean, what's involved in doing that. >>It, it, isn't, it's just a matter of taking a holistic view at your application portfolio and understanding the nuances of each application type within your organization and trying to come up with a suitable migration strategy for each one of these application types. And for that, what we're trying to do is provide a series of standardized, um, tools and methodologies, uh, from a community perspective, uh, we created this conveyor community. Uh, it, it was kick started by red hat and IBM, but we are trying to bring as many vendors and GSI, uh, as possible to try to set up these standards to make these, uh, road towards Kubernetes as easy as >>Possible. So we've done a little bit of, uh, app modernization in the CTO advisor hybrid infrastructure. And one of the things that we've found, there's plenty of Avan advantages. If I take a monolithic application that has, uh, that I've traditionally had to scale off to, uh, game performance, I can take selective parts of that, and now I can add auto-scaling to it. Exactly. However, as I look at a landscape Allen of thousands of applications, uh, I need to dedicate developer resources to get that done and my traditional environment, but my traditional environment is busy building new. My traditional or my developers are building new applications and new capabilities. I just don't have the resources to do that. How does HCL and red hat team together to kind of fast track that capability? >>Well, um, I'll comment on two things in particular, actually the, the first thing when it comes to skilling, I think the thing that's really surprised us at HCL is so many of our clients around the world have said, we are desperately short of skills. We cannot hire ourselves out of this problem. We need to get our existing developer community re-skilled around platforms like OpenShift, conveyor, and other projects too. So the first thing that's happened to us at eight still is we've been incredibly busy undertaken, probably what we would call developer workforce modernization, right, where we have to help the client reskill their entire technical and developer community to give them the skills, right. So we will help the clients develop a community, build the cloud native understanding, help them understand how to modernize tools for example, uh, or applications. But the second thing I mention is, and this comes back to a comment that Ramon made around around conveyor. >>It's been really encouraging to see the open source community start to invest in building the supporting frameworks around my kind of modernization journey, because if I'm a developer that's re-skilling and I'm attempting to maybe modernize an application, being able to dip into an open source project, I mean, a good example would be tackled part of the conveyor project. Exactly. You now have open source based tools that will help you analyze your applications. They will go into the source code and they will give the developer guidance in terms of what would be effective treatments to undertake. So perhaps a development team that are new to this modernization journey, they would benefit from a project like conveyor, for example, because I need to know where can I safely modernize my application now for experience organizations like HCL that comes naturally to us, but for people who are just starting this journey, if I can take an open source tool like tackle or the rest of the conveyor, for example, and use that to accelerate my journey, it takes a lot of pressure off, off my organization, but it also accelerates the journey too. >>And it's not just a matter of, of tooling. We we're also opensourcing, uh, the, the modernization methodology that we've been using in red hat consulting for years. So this whole conveyor communities, it's all about knowledge sharing on one hand and building a set of tools together, based on that knowledge that we are sharing to make it as easy as possible. >>And what role does red hat play in all that, I mean, is your you've carved out this position for yourself as the, as the true open source company. Is that, does that position you for a leadership role in helping companies make this >>Transition? I wouldn't say we should be leading the whole thing. Uh, we, we kick started it, but we want to get other vendors on board for this thing. One cool thing about the Camira community is that IBM is, uh, opensourcing a lot of their IP. So IBM research is on board. In this thing, we have some really crazy stuff related to a AI being applied to application analysis. We have some machine learning in place. We have very cool stuff that has been sitting on a, on a corner in IBM research for quite some years that now it's being open sourced and integrated in a, uh, unified user experience to streamline the, uh, modernization process as much as >>Possible. So let's talk about the elephant of the room. Uh, HCL was leading the conversation around cloud Foundry circa five plus years ago. And as customers are thinking about their journey to cloud native, how should they think about that cloud Foundry to cloud native or Kubernetes, uh, replatforming? >>Well within the cloud Foundry community, we've, we've been quite staunched supporters of Kubernetes for quite some time, right? It's, it's quite a, a stated intent of the cloud Foundry foundation to, to move across to Kubernetes platform right now that is a significant engineering journey for cloud Foundry to take. Now we're in this position where a lot of large users of cloud Foundry have a certain urgency to their journey. They, they want to consolidate on a single Kubernetes based, okay. Um, infrastructure. We, we see a lot of traction around OpenShift, for example, from red hat in terms of its market leadership. So a lot of clients are saying we would like to consolidate all of our platforms around a single kind of Kubernetes vendor, whether that's red hat or anyone else, you know, quite frankly. So what ATL is doing right now with the tools and the solutions we've announced this week is we're simply accelerating that journey for clients. If I've got a large installed base of applications running in my cloud Foundry environment, and I've also started to invest in standardize on Kubernetes based platforms like OpenShift, most clients would see it as quite a sensible choice to now try and consolidate those two environments into one. And that's simply what we're doing at HCL. We're making it very, very easy. In fact, we fully automated the journey so I can move all of my applications from cloud Foundry into for example, OpenShift pretty much immediately. And it just simplifies the entire journey. >>So the, as we start to wrap up the segment, I like to know customer stories. What, what, how customers either surprised or challenged when they get into, even with the help of an ACL in redhead, why are they seeing the most difficult parts of their migrations? >>Well, my, my simple comment would be maybe complexity, right? And the, the associated requirement for skilled people to undertake this modernization work, right? We spoke about this, of course, in terms of clients now are a lot more realistic. They understand that their ambition now needs to be somewhat tempered by their ability to sort of drive modernization quickly. So we see a lot of clients when they look at their very large global portfolios of applications, they're trying to invest their resources in the higher priority applications, the revenue generative applications in particular, but they have to bring everything else with them as well. Now, a common kind of separation point was we see a lot of clients who might say I'm gonna properly modernize and refactor, maybe five to 10% of my portfolio, but the other 90% also needs to come on the journey as well. And that's really where replatforming in particular kicks in. So, so the key trend again, is, is clients send to us, I've gotta take the entire journey. All right, I've got the resources and the skills to really focus on this much of my application base. Can someone simplify the overall journey so I can afford to bring everything on a cloud native journey? >>So the key to success here is having a holistic view at the application portfolio, segmenting the application portfolio in different application types and ordering the, the priorities of these application types and come up with suitable migration strategies for each one of them is >>Really necess necessary to move everything though. >>Not necessarily no, or, uh, not necessarily. Yeah, absolutely not everything. But, uh, it would make sense. Uh, as we were saying before, it will definitely move, make sense to move legacy applications towards Kubernetes, to leverage all the, uh, software delivery >>That's >>That's project, right? >>It is. If >>You're gonna restructure the application around APIs and microservices, >>That it should be taken the, the way I've seen, uh, organizations succeeding the most in this, uh, road towards cloud native and Kubernetes in general is trying to address the whole portfolio. Maybe not move everything, but try, try to have this holistic view and not leave anything behind, because if you try to do this isolated, uh, initiatives of bringing this or that applications in a, in isolation, you're Def you, you will miss part of the picture and you might be, uh, doomed to fail >>There. Yeah. It's been my experience that if you don't have a plan to migrate your applications to a cloud native operating model, then you're doomed to follow lift and shift examples to the public cloud. Yeah. Whether you're, uh, going to any other clouds, if you don't make that, that operational transition. Last question on operational transition, we've talked a lot about the replatforming process itself. What about day two, uh, at the I've landed to the cloud? What are some of the top considerations for, for compliance, uh, op op observability, just making sure my apps stay up and transitioning my workforce to that model. >>I, I, I think the over, you know, the overarching trend or theme that, that I see is clients now are, are asking for what I would call cloud native operations. Now in particular, there's a very solid theme around what we would call reliability engineering. So think about site reliability, engineering, SRE platform, reliability engineering, PR E. These are the dominant topics that clients and I want to engage, uh, HCL on in particular, because the point you make is a valid one. I've modernized my application. Now I need to modernize the way that I operate the application in production. Otherwise I won't see those benefits. So that general theme of SRE is keeping us really busy. We're busy, re-skilling all of those operations teams around the world as well, because they need to know how to run these environments appropriately too. >>And also being able to measure your progress while your transitioning is important. And that's one of the concerns that we are addressing as well in the premier community with a tool called polars to, to measure, to effectively measure the software delivery performance of, of the organization after the transition has been done. >>And this is a really good point by the way, cuz most, most people think it's a bit of a black art. How do I understand how I modernize my application? How do I understand how I've improved my kind of value chain around software creation and many people thought you needed to bring in very expensive consultants to advise you on these, on these black lives? No, >>Definitely >>Not. But in open source projects like conveyor from, from red hat, the availability of these tools available on an open source model means exactly any engineer, any developer can get these tools off the shelf and get that immediate benefit. >>Well, a flower head of creative labs at HCL at Ramon neon, senior product manager, redhead. Thank you for joining the QPI. Now Cuba alum, uh, you'll have a nice profile like the profile picture on here. Awesome. >>Absolutely. Thank you. >>From Valencia Spain. I'm Keith towns, along with Paul Gillon and you're watching the cue, the leader in high tech coverage.