(upbeat music) >> Hi everyone. Welcome back to this Cube conversation here in Palo Alto, California. I'm John Furrier, host of "theCUBE." Got a great conversation around Cloud Native, Cloud Native Journey, how enterprises are looking at Cloud Native and putting it all together. And it comes down to operations, developer productivity, and security. It's the hottest topic in technology. We got Chris Jones here in the studio, director of Product Management for Platform9. Chris, thanks for coming in. >> Hey, thanks. >> So when we always chat about, when we're at KubeCon. KubeConEU is coming up and in a few, in a few months, the number one conversation is developer productivity. And the developers are driving all the standards. It's interesting to see how they just throw everything out there and whatever gets adopted ends up becoming the standard, not the old school way of kind of getting stuff done. So that's cool. Security Kubernetes and Containers are all kind of now that next level. So you're starting to see the early adopters moving to the mainstream. Enterprises, a variety of different approaches. You guys are at the center of this. We've had a couple conversations with your CEO and your tech team over there. What are you seeing? You're building the products. What's the core product focus right now for Platform9? What are you guys aiming for? >> The core is that blend of enabling your infrastructure and PlatformOps or DevOps teams to be able to go fast and run in a stable environment, but at the same time enable developers. We don't want people going back to what I've been calling Shadow IT 2.0. It's, hey, I've been told to do something. I kicked off this Container initiative. I need to run my software somewhere. I'm just going to go figure it out. We want to keep those people productive. At the same time we want to enable velocity for our operations teams, be it PlatformOps or DevOps. >> Take us through in your mind and how you see the industry rolling out this Cloud Native journey. Where do you see customers out there? Because DevOps have been around, DevSecOps is rocking, you're seeing AI, hot trend now. Developers are still in charge. Is there a change to the infrastructure of how developers get their coding done and the infrastructure, setting up the DevOps is key, but when you add the Cloud Native journey for an enterprise, what changes? What is the, what is the, I guess what is the Cloud Native journey for an enterprise these days? >> The Cloud Native journey or the change? When- >> Let's start with the, let's start with what they want to do. What's the goal and then how does that happen? >> I think the goal is that promise land. Increased resiliency, better scalability, and overall reduced costs. I've gone from physical to virtual that gave me a higher level of density, packing of resources. I'm moving to Containers. I'm removing that OS layer again. I'm getting a better density again, but all of a sudden I'm running Kubernetes. What does that, what does that fundamentally do to my operations? Does it magically give me scalability and resiliency? Or do I need to change what I'm running and how it's running so it fits that infrastructure? And that's the reality, is you can't just take a Container and drop it into Kubernetes and say, hey, I'm now Cloud Native. I've got reduced cost, or I've got better resiliency. There's things that your engineering teams need to do to make sure that application is a Cloud Native. And then there's what I think is one of the largest shifts of virtual machines to containers. When I was in the world of application performance monitoring, we would see customers saying, well, my engineering team have this Java app, and they said it needs a VM with 12 gig of RAM and eight cores, and that's what we gave it. But it's running slow. I'm working with the application team and you can see it's running slow. And they're like, well, it's got all of its resources. One of those nice features of virtualization is over provisioning. So the infrastructure team would say, well, we gave it, we gave it all a RAM it needed. And what's wrong with that being over provisioned? It's like, well, Java expects that RAM to be there. Now all of a sudden, when you move to the world of containers, what we've got is that's not a set resource limit, really is like it used to be in a VM, right? When you set it for a container, your application teams really need to be paying attention to your resource limits and constraints within the world of Kubernetes. So instead of just being able to say, hey, I'm throwing over the fence and now it's just going to run on a VM, and that VMs got everything it needs. It's now really running on more, much more of a shared infrastructure where limits and constraints are going to impact the neighbors. They are going to impact who's making that decision around resourcing. Because that Kubernetes concept of over provisioning and the virtualization concept of over provisioning are not the same. So when I look at this problem, it's like, well, what changed? Well, I'll do my scale tests as an application developer and tester, and I'd see what resources it needs. I asked for that in the VM, that sets the high watermark, job's done. Well, Kubernetes, it's no longer a VM, it's a Kubernetes manifest. And well, who owns that? Who's writing it? Who's setting those limits? To me, that should be the application team. But then when it goes into operations world, they're like, well, that's now us. Can we change those? So it's that amalgamation of the two that is saying, I'm a developer. I used to pay attention, but now I need to pay attention. And an infrastructure person saying, I used to just give 'em what they wanted, but now I really need to know what they've wanted, because it's going to potentially have a catastrophic impact on what I'm running. >> So what's the impact for the developer? Because, infrastructure's code is what everybody wants. The developer just wants to get the code going and they got to pay attention to all these things, or don't they? Is that where you guys come in? How do you guys see the problem? Actually scope the problem that you guys solve? 'Cause I think you're getting at I think the core issue here, which is, I've got Kubernetes, I've got containers, I've got developer productivity that I want to focus on. What's the problem that you guys solve? >> Platform operation teams that are adopting Cloud Native in their environment, they've got that steep learning curve of Kubernetes plus this fundamental change of how an app runs. What we're doing is taking away the burden of needing to operate and run Kubernetes and giving them the choice of the flexibility of infrastructure and location. Be that an air gap environment like a, let's say a telco provider that needs to run a containerized network function and containerized workloads for 5G. That's one thing that we can deploy and achieve in a completely inaccessible environment all the way through to Platform9 running traditionally as SaaS, as we were born, that's remotely managing and controlling your Kubernetes environments on-premise AWS. That hybrid cloud experience that could be also Bare Metal, but it's our platform running your environments with our support there, 24 by seven, that's proactively reaching out. So it's removing a lot of that burden and the complications that come along with operating the environment and standing it up, which means all of a sudden your DevOps and platform operations teams can go and work with your engineers and application developers and say, hey, let's get, let's focus on the stuff that, that we need to be focused on, which is running our business and providing a service to our customers. Not figuring out how to upgrade a Kubernetes cluster, add new nodes, and configure all of the low level. >> I mean there are, that's operations that just needs to work. And sounds like as they get into the Cloud Native kind of ops, there's a lot of stuff that kind of goes wrong. Or you go, oops, what do we buy into? Because the CIOs, let's go, let's go Cloud Native. We want to, we got to get set up for the future. We're going to be Cloud Native, not just lift and shift and we're going to actually build it out right. Okay, that sounds good. And when we have to actually get done. >> Chris: Yeah. >> You got to spin things up and stand up the infrastructure. What specifically use case do you guys see that emerges for Platform9 when people call you up and you go talk to customers and prospects? What's the one thing or use case or cases that you guys see that you guys solve the best? >> So I think one of the, one of the, I guess new use cases that are coming up now, everyone's talking about economic pressures. I think the, the tap blows open, just get it done. CIO is saying let's modernize, let's use the cloud. Now all of a sudden they're recognizing, well wait, we're spending a lot of money now. We've opened that tap all the way, what do we do? So now they're looking at ways to control that spend. So we're seeing that as a big emerging trend. What we're also sort of seeing is people looking at their data centers and saying, well, I've got this huge legacy environment that's running a hypervisor. It's running VMs. Can we still actually do what we need to do? Can we modernize? Can we start this Cloud Native journey without leaving our data centers, our co-locations? Or if I do want to reduce costs, is that that thing that says maybe I'm repatriating or doing a reverse migration? Do I have to go back to my data center or are there other alternatives? And we're seeing that trend a lot. And our roadmap and what we have in the product today was specifically built to handle those, those occurrences. So we brought in KubeVirt in terms of virtualization. We have a long legacy doing OpenStack and private clouds. And we've worked with a lot of those users and customers that we have and asked the questions, what's important? And today, when we look at the world of Cloud Native, you can run virtualization within Kubernetes. So you can, instead of running two separate platforms, you can have one. So all of a sudden, if you're looking to modernize, you can start on that new infrastructure stack that can run anywhere, Kubernetes, and you can start bringing VMs over there as you are containerizing at the same time. So now you can keep your application operations in one environment. And this also helps if you're trying to reduce costs. If you really are saying, we put that Dev environment in AWS, we've got a huge amount of velocity out of it now, can we do that elsewhere? Is there a co-location we can go to? Is there a provider that we can go to where we can run that infrastructure or run the Kubernetes, but not have to run the infrastructure? >> It's going to be interesting too, when you see the Edge come online, you start, we've got Mobile World Congress coming up, KubeCon events we're going to be at, the conversation is not just about public cloud. And you guys obviously solve a lot of do-it-yourself implementation hassles that emerge when people try to kind of stand up their own environment. And we hear from developers consistency between code, managing new updates, making sure everything is all solid so they can go fast. That's the goal. And that, and then people can get standardized on that. But as you get public cloud and do it yourself, kind of brings up like, okay, there's some gaps there as the architecture changes to be more distributed computing, Edge, on-premises cloud, it's cloud operations. So that's cool for DevOps and Cloud Native. How do you guys differentiate from say, some the public cloud opportunities and the folks who are doing it themselves? How do you guys fit in that world and what's the pitch or what's the story? >> The fit that we look at is that third alternative. Let's get your team focused on what's high value to your business and let us deliver that public cloud experience on your infrastructure or in the public cloud, which gives you that ability to still be flexible if you want to make choices to run consistently for your developers in two different locations. So as I touched on earlier, instead of saying go figure out Kubernetes, how do you upgrade a hundred worker nodes in place upgrade. We've solved that problem. That's what we do every single day of the week. Don't go and try to figure out how to upgrade a cluster and then upgrade all of the, what I call Kubernetes friends, your core DNSs, your metrics server, your Kubernetes dashboard. These are all things that we package, we test, we version. So when you click upgrade, we've already handled that entire process. So it's saying don't have your team focused on that lower level piece of work. Get them focused on what is important, which is your business services. >> Yeah, the infrastructure and getting that stood up. I mean, I think the thing that's interesting, if you look at the market right now, you mentioned cost savings and recovery, obviously kind of a recession. I mean, people are tightening their belts for sure. I don't think the digital transformation and Cloud Native spend is going to plummet. It's going to probably be on hold and be squeezed a little bit. But to your point, people are refactoring looking at how to get the best out of what they got. It's not just open the tap of spend the cash like it used to be. Yeah, a couple months, even a couple years ago. So okay, I get that. But then you look at the what's coming, AI. You're seeing all the new data infrastructure that's coming. The containers, Kubernetes stuff, got to get stood up pretty quickly and it's got to be reliable. So to your point, the teams need to get done with this and move on to the next thing. >> Chris: Yeah, yeah, yeah. >> 'Cause there's more coming. I mean, there's a lot coming for the apps that are building in Data Native, AI-Native, Cloud Native. So it seems that this Kubernetes thing needs to get solved. Is that kind of what you guys are focused on right now? >> So, I mean to use a customer, we have a customer that's in AI/ML and they run their platform at customer sites and that's hardware bound. You can't run AI machine learning on anything anywhere. Well, with Platform9 they can. So we're enabling them to deliver services into their customers that's running their AI/ML platform in their customer's data centers anywhere in the world on hardware that is purpose-built for running that workload. They're not Kubernetes experts. That's what we are. We're bringing them that ability to focus on what's important and just delivering their business services whilst they're enabling our team. And our 24 by seven proactive management are always on assurance to keep that up and running for them. So when something goes bump at the night at 2:00am, our guys get woken up. They're the ones that are reaching out to the customer saying, your environments have a problem, we're taking these actions to fix it. Obviously sometimes, especially if it is running on Bare Metal, there's things you can't do remotely. So you might need someone to go and do that. But even when that happens, you're not by yourself. You're not sitting there like I did when I worked for a bank in one of my first jobs, three o'clock in the morning saying, wow, our end of day processing is stuck. Who else am I waking up? Right? >> Exactly, yeah. Got to get that cash going. But this is a great use case. I want to get to the customer. What do some of the successful customers say to you for the folks watching that aren't yet a customer of Platform9, what are some of the accolades and comments or anecdotes that you guys hear from customers that you have? >> It just works, which I think is probably one of the best ones you can get. Customers coming back and being able to show to their business that they've delivered growth, like business growth and productivity growth and keeping their organization size the same. So we started on our containerization journey. We went to Kubernetes. We've deployed all these new workloads and our operations team is still six people. We're doing way more with growth less, and I think that's also talking to the strength that we're bringing, 'cause we're, we're augmenting that team. They're spending less time on the really low level stuff and automating a lot of the growth activity that's involved. So when it comes to being able to grow their business, they can just focus on that, not- >> Well you guys do the heavy lifting, keep on top of the Kubernetes, make sure that all the versions are all done. Everything's stable and consistent so they can go on and do the build out and provide their services. That seems to be what you guys are best at. >> Correct, correct. >> And so what's on the roadmap? You have the product, direct product management, you get the keys to the kingdom. What is, what is the focus? What's your focus right now? Obviously Kubernetes is growing up, Containers. We've been hearing a lot at the last KubeCon about the security containers is getting better. You've seen verification, a lot more standards around some things. What are you focused on right now for at a product over there? >> Edge is a really big focus for us. And I think in Edge you can look at it in two ways. The mantra that I drive is Edge must be remote. If you can't do something remotely at the Edge, you are using a human being, that's not Edge. Our Edge management capabilities and being in the market for over two years are a hundred percent remote. You want to stand up a store, you just ship the server in there, it gets racked, the rest of it's remote. Imagine a store manager in, I don't know, KFC, just plugging in the server, putting in the ethernet cable, pressing the power button. The rest of all that provisioning for that Cloud Native stack, Kubernetes, KubeVirt for virtualization is done remotely. So we're continuing to focus on that. The next piece that is related to that is allowing people to run Platform9 SaaS in their data centers. So we do ag app today and we've had a really strong focus on telecommunications and the containerized network functions that come along with that. So this next piece is saying, we're bringing what we run as SaaS into your data center, so then you can run it. 'Cause there are many people out there that are saying, we want these capabilities and we want everything that the Platform9 control plane brings and simplifies. But unfortunately, regulatory compliance reasons means that we can't leverage SaaS. So they might be using a cloud, but they're saying that's still our infrastructure. We're still closed that network down, or they're still on-prem. So they're two big priorities for us this year. And that on-premise experiences is paramount, even to the point that we will be delivering a way that when you run an on-premise, you can still say, wait a second, well I can send outbound alerts to Platform9. So their support team can still be proactively helping me as much as they could, even though I'm running Platform9s control plane. So it's sort of giving that blend of two experiences. They're big, they're big priorities. And the third pillar is all around virtualization. It's saying if you have economic pressures, then I think it's important to look at what you're spending today and realistically say, can that be reduced? And I think hypervisors and virtualization is something that should be looked at, because if you can actually reduce that spend, you can bring in some modernization at the same time. Let's take some of those nos that exist that are two years into their five year hardware life cycle. Let's turn that into a Cloud Native environment, which is enabling your modernization in place. It's giving your engineers and application developers the new toys, the new experiences, and then you can start running some of those virtualized workloads with KubeVirt, there. So you're reducing cost and you're modernizing at the same time with your existing infrastructure. >> You know Chris, the topic of this content series that we're doing with you guys is finding the right path, trusting the right path to Cloud Native. What does that mean? I mean, if you had to kind of summarize that phrase, trusting the right path to Cloud Native, what does that mean? It mean in terms of architecture, is it deployment? Is it operations? What's the underlying main theme of that quote? What's the, what's? How would you talk to a customer and say, what does that mean if someone said, "Hey, what does that right path mean?" >> I think the right path means focusing on what you should be focusing on. I know I've said it a hundred times, but if your entire operations team is trying to figure out the nuts and bolts of Kubernetes and getting three months into a journey and discovering, ah, I need Metrics Server to make something function. I want to use Horizontal Pod Autoscaler or Vertical Pod Autoscaler and I need this other thing, now I need to manage that. That's not the right path. That's literally learning what other people have been learning for the last five, seven years that have been focused on Kubernetes solely. So the why- >> There's been a lot of grind. People have been grinding it out. I mean, that's what you're talking about here. They've been standing up the, when Kubernetes started, it was all the promise. >> Chris: Yep. >> And essentially manually kind of getting in in the weeds and configuring it. Now it's matured up. They want stability. >> Chris: Yeah. >> Not everyone can get down and dirty with Kubernetes. It's not something that people want to generally do unless you're totally into it, right? Like I mean, I mean ops teams, I mean, yeah. You know what I mean? It's not like it's heavy lifting. Yeah, it's important. Just got to get it going. >> Yeah, I mean if you're deploying with Platform9, your Ops teams can tinker to their hearts content. We're completely compliant upstream Kubernetes. You can go and change an API server flag, let's go and mess with the scheduler, because we want to. You can still do that, but don't, don't have your team investing in all this time to figure it out. It's been figured out. >> John: Got it. >> Get them focused on enabling velocity for your business. >> So it's not build, but run. >> Chris: Correct? >> Or run Kubernetes, not necessarily figure out how to kind of get it all, consume it out. >> You know we've talked to a lot of customers out there that are saying, "I want to be able to deliver a service to my users." Our response is, "Cool, let us run it. You consume it, therefore deliver it." And we're solving that in one hit versus figuring out how to first run it, then operate it, then turn that into a consumable service. >> So the alternative Platform9 is what? They got to do it themselves or use the Cloud or what's the, what's the alternative for the customer for not using Platform9? Hiring more people to kind of work on it? What's the? >> People, building that kind of PaaS experience? Something that I've been very passionate about for the past year is looking at that world of sort of GitOps and what that means. And if you go out there and you sort of start asking the question what's happening? Just generally with Kubernetes as well and GitOps in that scope, then you'll hear some people saying, well, I'm making it PaaS, because Kubernetes is too complicated for my developers and we need to give them something. There's some great material out there from the likes of Intuit and Adobe where for two big contributors to Argo and the Argo projects, they almost have, well they do have, different experiences. One is saying, we went down the PaaS route and it failed. The other one is saying, well we've built a really stable PaaS and it's working. What are they trying to do? They're trying to deliver an outcome to make it easy to use and consume Kubernetes. So you could go out there and say, hey, I'm going to build a Kubernetes cluster. Sounds like Argo CD is a great way to expose that to my developers so they can use Kubernetes without having to use Kubernetes and start automating things. That is an approach, but you're going to be going completely open source and you're going to have to bring in all the individual components, or you could just lay that, lay it down, and consume it as a service and not have to- >> And mentioned to it. They were the ones who kind of brought that into the open. >> They did. Inuit is the primary contributor to the Argo set of products. >> How has that been received in the market? I mean, they had the event at the Computer History Museum last fall. What's the momentum there? What's the big takeaway from that project? >> Growth. To me, growth. I mean go and track the stars on that one. It's just, it's growth. It's unlocking machine learning. Argo workflows can do more than just make things happen. Argo CD I think the approach they're taking is, hey let's make this simple to use, which I think can be lost. And I think credit where credit's due, they're really pushing to bring in a lot of capabilities to make it easier to work with applications and microservices on Kubernetes. It's not just that, hey, here's a GitOps tool. It can take something from a Git repo and deploy it and maybe prioritize it and help you scale your operations from that perspective. It's taking a step back and saying, well how did we get to production in the first place? And what can be done down there to help as well? I think it's growth expansion of features. They had a huge release just come out in, I think it was 2.6, that brought in things that as a product manager that I don't often look at like really deep technical things and say wow, that's powerful. But they have, they've got some great features in that release that really do solve real problems. >> And as the product, as the product person, who's the target buyer for you? Who's the customer? Who's making that? And you got decision maker, influencer, and recommender. Take us through the customer persona for you guys. >> So that Platform Ops, DevOps space, right, the people that need to be delivering Containers as a service out to their organization. But then it's also important to say, well who else are our primary users? And that's developers, engineers, right? They shouldn't have to say, oh well I have access to a Kubernetes cluster. Do I have to use kubectl or do I need to go find some other tool? No, they can just log to Platform9. It's integrated with your enterprise id. >> They're the end customer at the end of the day, they're the user. >> Yeah, yeah. They can log in. And they can see the clusters you've given them access to as a Platform Ops Administrator. >> So job well done for you guys. And your mind is the developers are moving 'em fast, coding and happy. >> Chris: Yeah, yeah. >> And and from a customer standpoint, you reduce the maintenance cost, because you keep the Ops smoother, so you got efficiency and maintenance costs kind of reduced or is that kind of the benefits? >> Yeah, yep, yeah. And at two o'clock in the morning when things go inevitably wrong, they're not there by themselves, and we're proactively working with them. >> And that's the uptime issue. >> That is the uptime issue. And Cloud doesn't solve that, right? Everyone experienced that Clouds can go down, entire regions can go offline. That's happened to all Cloud providers. And what do you do then? Kubernetes isn't your recovery plan. It's part of it, right, but it's that piece. >> You know Chris, to wrap up this interview, I will say that "theCUBE" is 12 years old now. We've been to OpenStack early days. We had you guys on when we were covering OpenStack and now Cloud has just been booming. You got AI around the corner, AI Ops, now you got all this new data infrastructure, it's just amazing Cloud growth, Cloud Native, Security Native, Cloud Native, Data Native, AI Native. It's going to be all, this is the new app environment, but there's also existing infrastructure. So going back to OpenStack, rolling our own cloud, building your own cloud, building infrastructure cloud, in a cloud way, is what the pioneers have done. I mean this is what we're at. Now we're at this scale next level, abstracted away and make it operational. It seems to be the key focus. We look at CNCF at KubeCon and what they're doing with the cloud SecurityCon, it's all about operations. >> Chris: Yep, right. >> Ops and you know, that's going to sound counterintuitive 'cause it's a developer open source environment, but you're starting to see that Ops focus in a good way. >> Chris: Yeah, yeah, yeah. >> Infrastructure as code way. >> Chris: Yep. >> What's your reaction to that? How would you summarize where we are in the industry relative to, am I getting, am I getting it right there? Is that the right view? What am I missing? What's the current state of the next level, NextGen infrastructure? >> It's a good question. When I think back to sort of late 2019, I sort of had this aha moment as I saw what really truly is delivering infrastructure as code happening at Platform9. There's an open source project Ironic, which is now also available within Kubernetes that is Metal Kubed that automates Bare Metal as code, which means you can go from an empty server, lay down your operating system, lay down Kubernetes, and you've just done everything delivered to your customer as code with a Cloud Native platform. That to me was sort of the biggest realization that I had as I was moving into this industry was, wait, it's there. This can be done. And the evolution of tooling and operations is getting to the point where that can be achieved and it's focused on by a number of different open source projects. Not just Ironic and and Metal Kubed, but that's a huge win. That is truly getting your infrastructure. >> John: That's an inflection point, really. >> Yeah. >> If you think about it, 'cause that's one of the problems. We had with the Bare Metal piece was the automation and also making it Cloud Ops, cloud operations. >> Right, yeah. I mean, one of the things that I think Ironic did really well was saying let's just treat that piece of Bare Metal like a Cloud VM or an instance. If you got a problem with it, just give the person using it or whatever's using it, a new one and reimage it. Just tell it to reimage itself and it'll just (snaps fingers) go. You can do self-service with it. In Platform9, if you log in to our SaaS Ironic, you can go and say, I want that physical server to myself, because I've got a giant workload, or let's turn it into a Kubernetes cluster. That whole thing is automated. To me that's infrastructure as code. I think one of the other important things that's happening at the same time is we're seeing GitOps, we're seeing things like Terraform. I think it's important for organizations to look at what they have and ask, am I using tools that are fit for tomorrow or am I using tools that are yesterday's tools to solve tomorrow's problems? And when especially it comes to modernizing infrastructure as code, I think that's a big piece to look at. >> Do you see Terraform as old or new? >> I see Terraform as old. It's a fantastic tool, capable of many great things and it can work with basically every single provider out there on the planet. It is able to do things. Is it best fit to run in a GitOps methodology? I don't think it is quite at that point. In fact, if you went and looked at Flux, Flux has ways that make Terraform GitOps compliant, which is absolutely fantastic. It's using two tools, the best of breeds, which is solving that tomorrow problem with tomorrow solutions. >> Is the new solutions old versus new. I like this old way, new way. I mean, Terraform is not that old and it's been around for about eight years or so, whatever. But HashiCorp is doing a great job with that. I mean, so okay with Terraform, what's the new address? Is it more complex environments? Because Terraform made sense when you had basic DevOps, but now it sounds like there's a whole another level of complexity. >> I got to say. >> New tools. >> That kind of amalgamation of that application into infrastructure. Now my app team is paying way more attention to that manifest file, which is what GitOps is trying to solve. Let's templatize things. Let's version control our manifest, be it helm, customize, or just a straight up Kubernetes manifest file, plain and boring. Let's get that version controlled. Let's make sure that we know what is there, why it was changed. Let's get some auditability and things like that. And then let's get that deployment all automated. So that's predicated on the cluster existing. Well why can't we do the same thing with the cluster, the inception problem. So even if you're in public cloud, the question is like, well what's calling that API to call that thing to happen? Where is that file living? How well can I manage that in a large team? Oh my God, something just changed. Who changed it? Where is that file? And I think that's one of big, the big pieces to be sold. >> Yeah, and you talk about Edge too and on-premises. I think one of the things I'm observing and certainly when DevOps was rocking and rolling and infrastructures code was like the real push, it was pretty much the public cloud, right? >> Chris: Yep. >> And you did Cloud Native and you had stuff on-premises. Yeah you did some lifting and shifting in the cloud, but the cool stuff was going in the public cloud and you ran DevOps. Okay, now you got on-premise cloud operation and Edge. Is that the new DevOps? I mean 'cause what you're kind of getting at with old new, old new Terraform example is an interesting point, because you're pointing out potentially that that was good DevOps back in the day or it still is. >> Chris: It is, I was going to say. >> But depending on how you define what DevOps is. So if you say, I got the new DevOps with public on-premise and Edge, that's just not all public cloud, that's essentially distributed Cloud Native. >> Correct. Is that the new DevOps in your mind or is that? How would you, or is that oversimplifying it? >> Or is that that term where everyone's saying Platform Ops, right? Has it shifted? >> Well you bring up a good point about Terraform. I mean Terraform is well proven. People love it. It's got great use cases and now there seems to be new things happening. We call things like super cloud emerging, which is multicloud and abstraction layers. So you're starting to see stuff being abstracted away for the benefits of moving to the next level, so teams don't get stuck doing the same old thing. They can move on. Like what you guys are doing with Platform9 is providing a service so that teams don't have to do it. >> Correct, yeah. >> That makes a lot of sense, So you just, now it's running and then they move on to the next thing. >> Chris: Yeah, right. >> So what is that next thing? >> I think Edge is a big part of that next thing. The propensity for someone to put up with a delay, I think it's gone. For some reason, we've all become fairly short-tempered, Short fused. You know, I click the button, it should happen now, type people. And for better or worse, hopefully it gets better and we all become a bit more patient. But how do I get more effective and efficient at delivering that to that really demanding- >> I think you bring up a great point. I mean, it's not just people are getting short-tempered. I think it's more of applications are being deployed faster, security is more exposed if they don't see things quicker. You got data now infrastructure scaling up massively. So, there's a double-edged swords to scale. >> Chris: Yeah, yeah. I mean, maintenance, downtime, uptime, security. So yeah, I think there's a tension around, and one hand enthusiasm around pushing a lot of code and new apps. But is the confidence truly there? It's interesting one little, (snaps finger) supply chain software, look at Container Security for instance. >> Yeah, yeah. It's big. I mean it was codified. >> Do you agree that people, that's kind of an issue right now. >> Yeah, and it was, I mean even the supply chain has been codified by the US federal government saying there's things we need to improve. We don't want to see software being a point of vulnerability, and software includes that whole process of getting it to a running point. >> It's funny you mentioned remote and one of the thing things that you're passionate about, certainly Edge has to be remote. You don't want to roll a truck or labor at the Edge. But I was doing a conversation with, at Rebars last year about space. It's hard to do brake fix on space. It's hard to do a, to roll a someone to configure satellite, right? Right? >> Chris: Yeah. >> So Kubernetes is in space. We're seeing a lot of Cloud Native stuff in apps, in space, so just an example. This highlights the fact that it's got to be automated. Is there a machine learning AI angle with all this ChatGPT talk going on? You see all the AI going the next level. Some pretty cool stuff and it's only, I know it's the beginning, but I've heard people using some of the new machine learning, large language models, large foundational models in areas I've never heard of. Machine learning and data centers, machine learning and configuration management, a lot of different ways. How do you see as the product person, you incorporating the AI piece into the products for Platform9? >> I think that's a lot about looking at the telemetry and the information that we get back and to use one of those like old idle terms, that continuous improvement loop to feed it back in. And I think that's really where machine learning to start with comes into effect. As we run across all these customers, our system that helps at two o'clock in the morning has that telemetry, it's got that data. We can see what's changing and what's happening. So it's writing the right algorithms, creating the right machine learning to- >> So training will work for you guys. You have enough data and the telemetry to do get that training data. >> Yeah, obviously there's a lot of investment required to get there, but that is something that ultimately that could be achieved with what we see in operating people's environments. >> Great. Chris, great to have you here in the studio. Going wide ranging conversation on Kubernetes and Platform9. I guess my final question would be how do you look at the next five years out there? Because you got to run the product management, you got to have that 20 mile steer, you got to look at the customers, you got to look at what's going on in the engineering and you got to kind of have that arc. This is the right path kind of view. What's the five year arc look like for you guys? How do you see this playing out? 'Cause KubeCon is coming up and we're you seeing Kubernetes kind of break away with security? They had, they didn't call it KubeCon Security, they call it CloudNativeSecurityCon, they just had in Seattle inaugural events seemed to go well. So security is kind of breaking out and you got Kubernetes. It's getting bigger. Certainly not going away, but what's your five year arc of of how Platform9 and Kubernetes and Ops evolve? >> It's to stay on that theme, it's focusing on what is most important to our users and getting them to a point where they can just consume it, so they're not having to operate it. So it's finding those big items and bringing that into our platform. It's something that's consumable, that's just taken care of, that's tested with each release. So it's simplifying operations more and more. We've always said freedom in cloud computing. Well we started on, we started on OpenStack and made that simple. Stable, easy, you just have it, it works. We're doing that with Kubernetes. We're expanding out that user, right, we're saying bring your developers in, they can download their Kube conflict. They can see those Containers that are running there. They can access the events, the log files. They can log in and build a VM using KubeVirt. They're self servicing. So it's alleviating pressures off of the Ops team, removing the help desk systems that people still seem to rely on. So it's like what comes into that field that is the next biggest issue? Is it things like CI/CD? Is it simplifying GitOps? Is it bringing in security capabilities to talk to that? Or is that a piece that is a best of breed? Is there a reason that it's been spun out to its own conference? Is this something that deserves a focus that should be a specialized capability instead of tooling and vendors that we work with, that we partner with, that could be brought in as a service. I think it's looking at those trends and making sure that what we bring in has the biggest impact to our users. >> That's awesome. Thanks for coming in. I'll give you the last word. Put a plug in for Platform9 for the people who are watching. What should they know about Platform9 that they might not know about it or what should? When should they call you guys and when should they engage? Take a take a minute to give the plug. >> The plug. I think it's, if your operations team is focused on building Kubernetes, stop. That shouldn't be the cloud. That shouldn't be in the Edge, that shouldn't be at the data center. They should be consuming it. If your engineering teams are all trying different ways and doing different things to use and consume Cloud Native services and Kubernetes, they shouldn't be. You want consistency. That's how you get economies of scale. Provide them with a simple platform that's integrated with all of your enterprise identity where they can just start consuming instead of having to solve these problems themselves. It's those, it's those two personas, right? Where the problems manifest. What are my operations teams doing, and are they delivering to my company or are they building infrastructure again? And are my engineers sprinting or crawling? 'Cause if they're not sprinting, you should be asked the question, do I have the right Cloud Native tooling in my environment and how can I get them back? >> I think it's developer productivity, uptime, security are the tell signs. You get that done. That's the goal of what you guys are doing, your mission. >> Chris: Yep. >> Great to have you on, Chris. Thanks for coming on. Appreciate it. >> Chris: Thanks very much. 0 Okay, this is "theCUBE" here, finding the right path to Cloud Native. I'm John Furrier, host of "theCUBE." Thanks for watching. (upbeat music)

(upbeat music) >> Good afternoon. theCUBE is live at VMware Explorer. Lisa Martin here in San Francisco with Dave Nicholson. This is our second day of coverage talking all things VMware and it's ecosystem. We're excited to welcome from DXC Technology, James Bion, Hybrid Cloud and Multi Cloud Offering manager to have a conversation next. Welcome to the program. >> Thank you very much. >> Welcome. >> Talk to us a little bit about before we get into the VMware partnership, what's new at DXC? What's going on? >> So DXC is really evolving and revitalizing into more of a cloud orientated company. So we're already driving change in our customers at the moment. We take them on that cloud journey, but we're taking them in the right way, in a structured mannered way. So we are really excited about it, we're kicking off our Cloud First type, Cloud Right sort of story and helping customers on that journey. >> Yesterday in the keynote, VMware was talking about customers are on this Cloud chaos phase, they want to get to Cloud Smart. You're saying they want to get to Cloud Right. Talk to us about what DXC Cloud Right is, what does it mean? What does it enable businesses to achieve? >> That's a very good question. So DXC has come up with this concept of Cloud Right, we looked at it from a services and outcome. So what do customers want to achieve? And how do we get it successfully? This is not a technology conversation, this is about putting the right workloads at the right place, at the right time, at the right cost to get the right value for your business. It's not about just doing it for the sake of doing it, okay. There's a lot of changes it's not technology only you've got to change how people operate. You've got to work through the organizational change. You need to ensure that you have the right security in place to maintain it. And it's about value, really about value proposition. So we don't just focus on cost, we focus on operations of it, we focus on security of it. We focus on ensuring the value proposition of it and putting not just for one Cloud, it's the right place. Big focus on Hybrid and Multi Cloud solutions in particular, we're very excited about what's happening with VMware Cloud on maybe AWS or et cetera because we see there a real dynamic change for our customers where they can transition across to the right Cloud services, at the right time, at the right place, but minimal disruption to the actual operation of their business. Very easy to move a workload into that place using the same skilled resources, the same tools, the same environment that you have had for many years, the same SLAs. Customers don't want a variance in their SLAs, they just want an outcome at a right price and the right time. >> Right, what are some of the things going on with the VMware partnership and anything you know, here we are at this the event called the theme is "The Center of the Multi Cloud Universe", which I keep saying sounds like a Marvel movie, I think there needs to be some superheroes here. But how is DXC working with VMware to help customers that are in Multi Cloud by default, not by design? >> That's a very good one. So DXC works jointly with VMware for more than a thousand clients out there. Wide diversity of different clients. We go to market together, we work collaboratively to put roadmaps in place for our clients, it's a unified team. On top of that, we have an extremely good VMware practice, joint working VMware team working directly with DXC dedicated resources and we deliver real value for clients. For example, we have a customer experience zone, we have a customer innovation zone so we can run proof of concepts on all the different VMware technologies for customers. If they want to try something different, try and push the boundaries a little bit with the VMware products, we can do that for them. But at the end of the day we deliver outcome based services. We are not there to deliver a piece of software, but a technology which show the customer the value of the service that they've been receiving within that. So we bring the VMware fantastic technologies in and then we bring the DXC managed services which we do so well and we look after our customers and do the right thing for our customers. >> So what does the go-to market strategy look like from a DXC perspective? We say that there are a finite number of strategic seats at the customer table. DXC has longstanding deep relationships with customers, so does VMware and probably over a shorter period of time, the Hyper scale Cloud Providers. How are you approaching these relationships with customers? Is it you bringing in your friends from the cloud? Is it the cloud bringing in their friend DXC? What does it look like? >> So we have relationships with all of them, but were agnostic. So we are the people who bring it all together into that unified platform and services that the customers expect. VMware will bring us certainly to the table and we'll bring VMware to the table. Equally, we work very collaboratively with all the cloud providers and we work in deals together. They bring us deals, we bring them deals. So it works extremely well from that perspective, but of course it's a multi-cloud world these days. We don't just deal with one cloud provider, we'll normally have all of the different services to find the right place for our customers. >> Now, one thing that that's been mentioned from DXC is this idea that Cloud First which has been sort of a mantra that scores you points if you're a CIO lately, maybe that's not the best way to wake up in the morning. Why not saying, Cloud First? >> So we have a lot of clients who who've tried that Cloud First journey and they've aggressively taken on migration of workloads. And now that they've settled in a few of those they're discovering maybe the ROI isn't quite what they expected it was going to be. That transformation takes a long time, a very long time. We've seen some of the numbers around averaging a hundred apps can take up to seven years to transition and transform, that's a long time. It makes you almost less agile by doing the transformation quite ironically. So DXC's Cloud Right program really helps you to ensure that you assess those workloads correctly, you target the ones that are going to give you the best business value, possibly the best return on investment using our Cloud and advisory practice to do that. And then obviously off the back of that we've got our migration teams and our run services and our application modernization factories and our application platforms for that. So DXC Cloud Right can certainly help our customers on that journey and get that sort of Hybrid Multi Cloud solution that suits their particular outcomes, not just one Cloud provider. >> So Cloud Right isn't just Cloud migration? >> No. >> People sometimes confuse digital transformation with Cloud migration. >> Correct. >> So to be clear Cloud Right and DXC has the ability to work with customers on not just, oh, here, this is how we box it up and ship it out, but what makes sense to box up and ship out. >> Correct, and it's all about that whole end to end life cycle. Remember, this is not just a technology conversation, this is an end to end business conversation. It's the outcomes are important, not the technology. That's why you have good partners like DXC who will help you on that technology journey. >> Let's talk about in the dynamics of the market the last couple of years, we saw so many customers in every industry race to the Cloud, race to digitally transform. You bring up a good point of people interchangeably talking about digital transformation, Cloud migration, but we saw the massive adoption of SaaS technologies. What are you seeing? Are you seeing customers in that sort of Cloud chaos as VMware calls it? That you're coming in with the Cloud Right approach saying, let's actually figure out, you may have done this because of the pandemic maybe it was accelerated, you needed to facilitate collaboration or whatnot, but actually this is the right approach. Are you seeing a lot of customers in that situation? >> We are certainly seeing some customers going into that chaos world. Some of them are still in the early stages of their journey and are taking a more cautious step towards in particular, the companies that would die on systems to be up available all the time. Others have gone too far, the other are in extreme are in the chaos world. And our Cloud Right program will certainly help them to pull their chaos back in, identify what workloads are potentially running in the wrong place, get the framework in place for ensuring that security and governance is in place. Ensuring that we don't have a cost spend blowout in particular, make sure that security is key to everything that we do and operations is key to everything we do. We have our own intelligent Platform X, it's called, our service management platform which is really the engine that sits behind our delivery mechanism. And that's got a whole lot of AI analytics engines in there to identify things and proactively identify workload placements, workload repairs, scripting, and hyper automation behind that too, to keep available here and there. And that's really some of our Cloud Right story, it's not just sorting out the mess, it's sorting out and then running it for you in the right way. >> So what does a typical, a customer engagement look like for a customer in that situation? >> So we would obviously engage our client right advisory team and they would come in and sit down with your application owners, sit down with the business units, identify what success needs to look like. They do all the discovery, they'll run it through our engines to identify what workloads are in the right place, should go to the right place. Just 'cause you can do something doesn't mean you should do something and that's an important thing. So we will come back with that and say, this is where I think your cloud roadmap journey should be. And obviously that takes an intuitive process, but we then can pick off the key topics early at the right time and that low hanging fruit that's really going to drive that value for the customer. >> And where are your customer conversations these days? I mean from a Cloud perspective, digital transformation, we're seeing everything escalate up the C-suite? Are you engaging the executives in this conversation so that they really want to facilitate, let's do things the right way that's the most efficient that allows us as a business to do what we're best at? >> So where we've seen programs fail is where we don't have executive leadership and brought in from day one. So if you don't have that executive and business driver and business leadership, then you're definitely not going to be successful. So to answer your question, yes, of course we are, but we also working directly with the IT departments as well. >> So you just brought up an insight executive alignment, critically important. Based on what you've experienced in the real world, contrast that with the sort of message to the world that we hear constantly about Cloud and IT, what would be the most shocking thing that you can share with us that people might not be aware of? It's like what shocks you the most about the disconnect between what everybody talks about and the reality on the ground? Don't name any names of anyone, but give us an example of the like, this is what's really going on. >> So, we certainly are seeing that big sort of move into Cloud quickly, okay. And then the big bill shock comes and just moving a workload across doesn't mean you're in Cloud, it's a transition and transformation to the SaaS and power services, it's where you get your true value out of cloud. So the concept that just 'cause it's in Cloud it's cheap is not always the case. Doing it right in Cloud is definitely going to have some cost value, but it's going to bring other additional values to their business. It's going to give them agility, it's going to give them resilience. So if you look at all three of those platforms cost, agility, and resilience and live across all three of those, then you're definitely going to get the best outcomes. And we've certainly seen some of those where they haven't taken all of those into consideration, quite often it's cost is what drives it, not the other two. And if you can't keep operations up working efficiently then you are in a lot of trouble. >> So Cloud wrong comes with sticker shock. >> It certainly does. >> What's on the horizon for DXC? >> We're certainly seeing a big drive towards apps modernization and certainly help our customers on that journey. DXC is definitely a Cloud company, may that be on Hybrid Cloud, Private Cloud, Public Cloud, DXC is certainly leading that edge and pushing it forward. >> Excellent, James, thank you so much for joining us on the program today talking about what Cloud Right is, the right approach, how you're helping customers really get to that right approach with the people, the processes, and the technology. We appreciate your time. >> Thank you very much. >> For our guest and Dave Nicholson, I'm Lisa Martin. You're watching theCUBE live from VMware Explorer, 2022. Our next guest joins us momentarily so don't change the channel. (upbeat music)

(upbeat music) >> Welcome back to Las Vegas Lisa Martin live here with David Nicholson. We're at AWS reinvent 2021, this an outstanding event. There's a lot of people here, tens of thousands. And this is probably one of the most important and largest hybrid tech events that we're doing this year with AWS and its massive ecosystem of partners. We're going to be covering this two live sets, two remote studios, over 100 guests on the CUBE at this re-invent and David and I are pleased to welcome Giorgio Vanzini next the vice president and global head of partners and alliances at DXC, Georgia Welcome to the program. >> Thank you for having me. >> Talk to us about what's going on at DXC, what are you in AWS doing together with what's the scoop? >> Yes Well, some exciting things are happening between AWS and DXC, which is we're really focusing on our customers that we have especially in the banking and capital markets, but also automotive. And then also we were a launch partner today with the AWS mainframe modernization right, and so we're focusing on mainframes as well. So exciting spaces for us to go collaborate and work with AWS, for our customers. >> Talk to me about some of the things you know the last 22 months have been quite challenging, quite dynamic and we've seen such a massive acceleration to the cloud. What have you seen from your perspective? Are you seeing customers in every industry that have really figured we've got to do this now because if we don't, we're going to be out of business? >> Yes, you're absolutely correct. We've seen a dramatic acceleration of people wanting or customers wanting to move to the cloud public and private, and an acceleration of assistance that they were requesting from a global systems integrator. So what we've seen is you know, part of our clouds ride strategy that we have, really understanding what does the customer need from a strategy perspective, from a business value perspective and the technology perspective, and AWS has been a great partner with us to actually accommodate all of these kinds of things and the announcements that you had today, you know, just substantiate kind of that fact as well. >> Can you double click on the Cloud Right approach, talk to us about what that is, why it's important and what are some of the outcomes that it's helping customers to generate? >> Absolutely love to Cloud Right is really DXC's strategy to take the customers on the journey from the mainframe to the cloud, and to customize this because every customer is different. They have different requirements, different environments, different business strategies. So therefore the Cloud Right approach is really customizing it for the customer. What is the right business strategy? What is the right technology strategy? And then migrating them over into the cloud as well. Keeping in mind that again, customers are specific, industries are specific. You know, data requirements are different analytics are different, you know, government requirements are different. So you need to those in mind when you transition customers over into the cloud space. >> Right, from a data residency, data sovereignty and all of the different rules and regulations that are popping up that are kind of similar to GDPR for example, that's a big challenge, but one of the things too that's happening Giorgio is that every company to be competitive these days has to become a data company, right? There's no choice, you've got to be data-driven, you've got to have a data strategy at the core of the business, otherwise there's a competitor in the rear view mirror, who's ready to take your place. >> That is absolutely correct, and so that's part of our Cloud Right strategy is understanding what are the business requirements from the customer? Understanding their competitive edge and migrating them over. Because in many instances, to your point, they have huge reams of data, petabytes of information of data, but really making sense of it, so running the analytics on it and having the business insights. So helping the customers understand that, but then also understanding of like, what are the key business requirements that they have? Which applications to migrate and which not to migrate? >> So I'm curious, you mentioned that you're a launch partner for mainframe modernization. That's sort of one slice of and very important slice of some organization's business and migration strategy to cloud. I'm curious what the DXC blend is between standardized offerings and bespoke services and how you manage that? Do you have a thought about that? Wouldn't it be great to have small, medium and large and have people click on it? >> Yes here's a T-shirt for you, which size are you? Now I'm actually glad you asked me that question because that's exactly going to the core of the Cloud Right strategy, and the Cloud Right really means that it's like, which T-shirt size is correct for you? Right. This is the question that we just addressed which is it has to be bespoke because one size does not fit all. And so understanding the customer requirements of do we need to move the data to the cloud? Or do we move to need a subset to the cloud? Do we need to move part of the business applications and which ones and in which order? Right? And so that's why I think we bring something to the table in the AWS mainframe modernization, which is unique because we have an end to end kind of approach from a planning to implementation, to execution and running as well. So I think DEX is uniquely positioned with our Cloud Right strategy. >> One of the things AWS Giorgio talks about is not being custom but being purpose-built. Talk to me about kind of compare contrast that with bespoke solutions, industry specific, obviously customers have specificities. Do you see a difference there between purpose-built under bespoke or are they aligned from your perspective? >> Yes, I do agree that a to technology layers are definitely common layers, horizontal layers, right Where I think you have bespoken limitations on the business strategy and the business rules. And so you have to understand what business is the customer really in and how to implement the business rules into the technology stack as well, and bringing it all together. So while the technology I think goes horizontal to your point right, you know, compute and storage is the same. Wherever you go the bits are the same, however how they're utilized and how you use them for your customers and your interaction is completely different from customer to customer and industry to industry, as you guys know as well. >> You know, it can be, it can be really disheartening working in this space when you think of 475 different kinds of instances and how important it is to get that right for a customer and how much they don't care. Ultimately they don't want to hear about it, they don't want to know, but they want you to get it right, so that it doesn't matter. So it's this irony of all of the work that people have to do like at DXC to make those details not matter. Any thoughts on that? Do you, are you a dejected because of that at all? >> Well, that is part of the value that we bring, right? >> David: Sure. >> To your point, absolutely the customer doesn't care in quotes, right? Just make it work for us and run it smoothly. On the other hand, we're on the hook to make sure that all the different partners that we have, that we integrate including AWS, right. Run smoothly and coherent and are up, you know, 99.999% of the time obviously right. And so the customers do care about our you know, interaction with them as well while AWS is always there. >> One of the things that we talked about a little bit ago is every industry had to pivot right. Dramatically the last 22 months or so. And we've seen every industry cloud is no longer a nice to have We've got to be able to get there, but you mentioned a focus in banking, and I think automotive, I'd love to get your perspectives on what some of the things are the opportunities that DXC sees in those particular industries, as opportunities to modernize. >> Yes, we latched on to banking and automotive because those are ripe for transition and the customers are willing to take the steps there as well. It doesn't mean that other industries are not relevant like, you know, consumer or retail or you know, technology and, and manufacturing. However, especially in automotive I think we have a unique positioning where we have the majority of the OAMs car manufacturers worldwide as customers, and when you think about AWS, you think about the utilization of the information that comes back from telematics information and customization, right. Petabytes of information that comes back from every device, which is a car and what kind of service you can provide there. So it's an industry you know, we talked about Tesla early on as well, right It's an industry that ripe for software and software updates. very similar you see a lot of things happening in the banking capital market space, where they're moving you know their customer base into new spaces as well. Just think about all the NFTs, those are happening, all the FinTech that's happening, right. So the, the banking capital markets companies have to, you know, have an evolution going on right, and assisting them in this evolution is as part of our strategy. >> So you're responsible for global partnerships and alliances DXC would be considered a large global systems integrator. The world is obviously moving in the direction of cloud. We've got the three big players AWS, and the other two I can't think of their names while I'm sitting here in Vegas right now, how do you balance what you do with those, with a variety of providers, for customers, and are you going to market primarily as DXC with the DXC relationship with the customer? Or in support of those cloud vendors that have essentially technology that if left unimplemented is essentially worthless, right I mean you, you bridge the divide between the technology and the true value of the technology, but are you the primary seat holder at the customer table, or is AWS the primary seat holder? Or is it a little of both? Long-winded question I apologize but I think you understand what I'm saying. It's an interesting world that we live in now. >> It definitely is, and if I wouldn't know you better I would say it's a trick question, but in all seriousness, we really are customer driven just like AWS as well right so, we really are trying to do the right thing for the customer. Hence our Cloud Right strategy, where we don't have a cookie cutter approach or saying just go do the following five things and you're going to be fine. We really want to look at the customer and say, what is important to you? What is the timeframe you're looking at? What is the strategic imperative that you have? What data do you have to move? You know, what system do you have to leave behind? And then do the right thing for the customer literally right. And so in this instance, absolutely you know, in my role AWS plays a huge role as you know is one of our core hyper scaler partners, a very good partner, we love AWS. And so making sure that they're always going to be there as part of that infrastructure is part of our strategy. >> You mentioned, oh sorry Dave >> No, I was just saying it makes sense. >> It does make sense in terms of being customer first, we talk with AWS, you can't kind of have an interview with, with one of their folks without talking about that. We work backwards from the customer first. This customer obsession, it sounds like from a cultural perspective, there's pretty strong alignment there with DXC. >> Exactly right, so I think from that perspective we share the same DNA where we look first to the customer and then say okay, how do we deduct what is right for the customer and implement it that way right, Because in many instances as you know, you mentioned the, the two other hyper scaler that we don't talk about, customers usually don't have a single source kind of approach, right They usually have a dual approach. And so while we have to work with that, there's preferred vendors that we engage with, right. And so clearly AWS is one of our preferred vendors that we engage with. >> Can you share an example? I'd love to know a customer that's taken the Cloud Right approach applied really kind of in a textbook way that you think really shows the value of DXC. Any customers, but even by industry if you don't want to name them, come to mind that really show the value of that approach. >> Yeah, So we, we just concluded a major migration from one of our leading insurance companies, a global big company that you know is similar with my birthplace. But what we really did is a Cloud Right approach of migrating them from their legacy mainframe and virtualized systems that they had, to a cloud approach. And in the process of doing this you know, we reduced their overall operating expenses, their cap X expenses obviously but also reduced their overall budget about 30% reduction by moving them to the cloud. Again during the Cloud Right approach of understanding what exactly to move in, which timeframe and what to leave behind right, Because in many instances, customers don't have an exit strategy. They rush to the cloud, but then leave their you know old legacy behind and like oh, what are you going to do with this? And so you need to have a comprehensive end to end system strategy of like, what do you want to leave behind? When do you want to sunset it? And when do you want to migrate certain things over as well? >> That's got to be quite challenging for I would assume a legacy historied insurance company been around for a long time, lots of data, but culturally very different than the cloud mindset. >> You bring up one of those soft skills, right. Which is the cultural aspect of talking with the customers of how do we migrate you? It's not just, and that's why I said it's not just a business decision or a technology decision. In many instances, you affect people's life as well. When you think about old systems administrators that were working on mainframes. Now if you move everything to the clouds, they become obsolete. So rescaling the workforce and having a comprehensive plan is part of the soft skills right, Where you think more comprehensive about the customer, it's not just technology it's really is the full experience right At 360 what happens to the people? How do we migrate the people? But also setting expectations with top management, for example right of saying, how is this going to change our business? What new opportunities are going to be there? So those are all the soft kind of skills as well. >> One of the things that struck me this morning during the AWS keynote is just all of the innovation that that goes on. But AWS really is a flywheel of the customer and all the opportunities that their customers create for AWS, and the opportunities then that AWS technologies create for the customers across industries I just thought that I just kind of really felt that flywheel this morning when Adam was talking about all of the things that they're revealing, you must feel the same as a partner. >> I do, and I I'm a tech geek, so I'm totally excited about this, and it you know it feeds my soul because I can remember when, you know, when we first had analytics with you know Redshift rights and then customers are coming back and going like, well could we do something that is real time? Because we have requirements in this, and then CAFCA came out right, as a new service and I'm like okay, great right, and so we're really there to embrace you know, every new service that comes out from AWS. Which is fantastic, right I mean the speed and agility that comes out with AWS and we totally embraced that for our customers. >> Awesome, Georgia thank you for joining David and me today talking about what's going on with DXC, your partnership with AWS, Cloud Right, and how you're helping customers get Cloud Right. We appreciate your insights and your time. >> Thank you, I appreciate it too, thank you. >> All right. For David Nicholson, I'm Lisa Martin. You're watching the cube, the leader in global alive tech coverage. (upbeat music)