>> Live from San Francisco. It's the cue covering IBM thing twenty nineteen brought to you by IBM. >> Clever and welcome to the live coverage here. The Cube in San Francisco for IBM. Think twenty nineteen day Volonte where he with Urban Krishna, senior vice president of cloud and cognitive software at IBM. Man in charge of all the cloud products cloud everywhere. Aye, aye. Anywhere are great to see you. Thanks for spending time. Know you're super busy. Thanks for spending time. >> I'm ready to be here right >> now. So we talked at the Red Hat Summit last year. You essentially laid out the vision for micro Services. Coup Burnett is how this always kind of coming together than the redhead acquisition. And now you're seeing big news here at IBM. Think setting the stage here in San Francisco for a I anywhere, which is cognitive kind of all over the clouds, and then really clarity around cloud multi cloud strategy end to end workloads all kind of tied together on premise in the clouds. Super important for IBM. Explain and unpacked that force. What does it mean, >> Right? So I'm going to begin unpacking it from where actually I left off last year. So if I just for ten seconds, last year, we talked a lot about containerized platforms are going to become the future that'll be the fabric on which every enterprise is going to build their IT and their future. OK, we talked about that last year, and I think with the announced acquisition of Red Hat that gets cemented and that'll go further once that closes. Now you take that and now you take it to the next level of value. So take Watson. Watson runs as a containerized set of services. If it's a containerized set of services, it could run on what we call Cloud Private. Cloud Private in turn runs on top of OpenShift. So then you say, wherever OpenShift runs, I can run this entire stack. Where does OpenShift run today? It runs on Amazon. It runs on the IBM cloud and runs on Azure. It runs on your premise. So on the simple simple. I always like things that are simple. So Watson runs on Cloud Private runs and OpenShift runs on all these infrastructures I just mentioned that gives you Watson anywhere. You want it close to your data run it on-prem. You want to run it on Azure, run it there. You want to run it on the IBM cloud you run it there. And hence that's the complete story. >> says it was more important for you to give customers choice >> than it was to keep Watson to yourself. To try to sell >> more cloud. >> I think that every company that survives a long term learns that choice to a customer is really important and forcing customers to do things only one way is jelly in the long term. A bad strategy. So >> from a customer statement, just get the facts right on the hard news. Watson. Anywhere. Now I can run Watson via containers. Asian Open ship Things you mentioned on a ws as sheer Microsoft azure and IBM cloud cloud private. All that >> on on premise >> and on premise, all cohesively enter end. >> Correct in an identical way. Which means even if you do things one place you build up more than one place, you could go deploy a moral in another place gives you that flexibility also. >> So I'm Akash Mercy over This sounds too crazy Is too hard to do that. I've tried all this multi cloud stuff. Got all this stuff. Why is it easier? How do how do you guys make this happen? What's the key secret sauce for pulling that end to end a I anywhere on multiple clouds, on premises and through the workloads. >> Two levels. One. We go to a container infrastructure as that common layer that isolates out what is the bottom infrastructure from everything that runs on top. So going to the common services on a Cuban Eddie's in a container layer that is common across all these environments, does the isolation off the bottom infrastructure? That's hard engineering, but we do that engineering. The second piece is you've taken the Watson set of capabilities and also put them into just three pieces. What's in studio? What's an ML from water machine learning and what's an open scale? And there you have the complete set that you go need to run everywhere. So we have done that engineering as well. >> Congratulations. Get the cloud anywhere. I mean, it's cloud. It's essentially everything's every anywhere. Now you got data everywhere you got cloud everywhere. Cloud operations. Where's the multi cloud and hybrid fit in? Because now, if I could do a I anywhere via container ization, shouldn't I built? Run any workload on premise and in multiple clouds. >> So we fundamentally believe that when I was here last time, we talked about the container fabrics. And I do believe that we need to get to the point where these can run anywhere. So you take the container fabric and you can go run that anywhere, right? So so that's one piece of it, the next part of is but I now need to integrate. So I now need to bring in all my pieces. How I integrate this application with another? It's the old problem of integration back again. So whether you want to use MQ or you want to use Kafka or you want to use one of these technologies? How do we get them to couple one work flow to another work flow? How do I get them to be secure? How do I get them to be resilient in the presence of crashes in the presence of latency and all that? So that's another big piece of announcements that we're making. You can take that complete set off integration technologies, and those can run anywhere on any cloud. Again, using the same partner describes. I'm not going to go into that again. And on premise. So you can knit all of those together. >> How can you talk about the rationale for the Red Hat acquisition? Specifically in the context of developers, IBM over the years has made you know many efforts took to court developers. Now, with the redhead acquisition, it's eight million developers and talk about specifically the importance of developers and how that's changed >> your strategy or enhance your >> strategy. I'm an enhancement. It's not really a change. I think we all acknowledge developers have always been important and will remain important. I mean, IBM has done a great job, I think, over the last twenty years and both helping create the whole developer ecosystem, for example, around Job. We were a very big piece of that, not the only participant in there. There were others, but we were a big piece of that. So you not take red hat on Lenox and Open shit and Open source and J. Boss and all of these technologies. There's a big ecosystem of developers. You mentioned eight million number. But why did that set of people come along? They come along because they get a lot of value from developing on top of something that in turn has so many other people on top. I think there's half a million pieces of software which use redhead as the primary infrastructure on which they develop. So it's the network effect really. Is that value andan Africa can only come from you, keep it open, You keep it running on the widest possible base, and then they get the value that if they develop on that digger access to that and US base on which Red Hat Franz >> are, we have >> evidence that >> totally makes sense. But I want to get one dig deeper that we cover a lot of developer, the business side of developers. Not so much, no ins and outs, so developer tools and stuff. There's a lot of stack overflow. Variety of sources do that, So developers want to things they want to be in the right wave. You laying out a great platform for that, then this monetization Amazon has seen massive growth on their partner network. You guys haven't ecosystem. You mentioned that. How does this anywhere philosophy impact ecosystem because they want to party with IBM? Where's the white spaces? What's the opportunity for partners? How should they evolve with IBM? What's your What's your direction on that? >> Okay, so two kinds of partners one there's a set of partners will bring a huge set of value to their clients because they actually provide the domain knowledge. The application specify acknowledged the management expertise, the operational expertise, printable technologies, perhaps that we provide. That's what a partner's is always gonna have. Value talked yesterday at a portable conference about what, cognizant? Who's a bigger part. They do. They built a self service application for patients off a medical provider to be able to get remote access to doctors when they couldn't get enough. And that was not life threatening immediately. Well, that's a huge sort of valley that they provide built on top of our technologies and products. A second kind of partner you went on developers is people who do open those packages. I think we've been quite good. We don't tend to cannibalize our partners, unlike some others we can talk about. So for those partners who have that value, we can put our investment in other places. But we could help maybe give access to the enterprise market for those developers, which I think opens up. A lot of you >> guys make the martyr for developers. That's right. I want to ask you a question. You guys are all sleep in all in on Cooper Netease. Red hat made a great bed on Cooper Netease on. Now that you're harvesting that with the requisition, huge growth there containers. Everyone saw containers. That was kind of a no brainer. Technical world developers are. What's the importance of uber Netease? As you see Kou Bernetti starting to shrink the abstraction software overlay. In the end, this new complexity where Cooper needs a running great value. What does that mean? This trend mean for CEOs CTO CSOs as enterprise start to think, you know, cohesive set of services across on Prem multiple clouds. Cooper Nettie seems to be a key point. What is the impact of it? What does it mean? >> I think I'll go to the business. Benefit Secure binaries. In the end is an orchestration. Later takes over management complexity. It takes away the cost of doing operations in a large cluster ofthe physical resource is, I think the value for the CIA level is the following today, on average, seventy percent of the total cost and people are tied up in maintaining what you have. Thirty percent is on new. That's rough rule of Tom Technologies like communities have taken to where we wanted to go and flipped out to thirty seventy. We need to spend only thirty percent maintaining what you have. And he could then go spend seventy percent on doing innovation, which is going to make inclined, happier and your business happier. Your team's had a couple of announcements today. One was hyper protect, and the other is a lot of services to facilitate. Hybrid. Can you talk about those brats up to date on a quick one, so hyper protect means. So where do you put your data in the cloud everybody gets worried about? Well, if it's in the clear, it could get stolen. C Togo to encryption. Typically, encryption is then down with the key. Well, who manages that cake? The hyper protect services are all about that key. Management is comin across. Both are getting hybrid world across both your premise and in the cloud. And nobody in the cloud, not even our deepest system administrator in the cloud, can get access to the key. That's pretty remarkable when you think about it, and so that provide the level of safety and encryption that should give you a lot of reassurance that nobody can get hold of that data that's hyper protect. And then if I go to all of the other services were doing, sometimes I see a lot of help. Someone advice. Look, in the three client meeting I just had every one of them was asking what should keep regarded watching I slightly more nice. What should I write knew? That means a whole lot of advice that you need and how to assess what you have in what should be a correct strategy. Then once you do that, somebody will say will help me move it. Others will say, Help me manage it So all the services to go do that is a big piece of what we're announcing it end and to end in addition to but into end. But also you can cover it up. Not only give me advice, I know I got buying strategy laid out, helping move it on Oprah's do boards for me or help you manage it after I move it except >> armor. When you sit in customer meetings. Big clients write me, and when they say we want to modernize, what does that mean to you? And how do you respond to that? >> Well, some organizes. Normally today it means that you've got to bring cloud technologies. You gotta bring air technologies. You got to bring what is called digital transformation all to bear. It's got to be in the service of either client intimacy, or it's got to be in terms ofthe doing straight through processing, as opposed to the old way of doing all the business processes that you have and then you get into always got to begin with some easy wind. So I always say, Begin with the easy stuff, not begin with the harder stuff. What started the architecture that let you do the hardest off later? It's not throw away, and those are all the discussions that we have, which are always a mixture of this people process technology. That world has not changed. We need to worry about. All >> three are thanks for spending your valuable time coming on the Q. Bree. We appreciate the insight. I know you're super busy. Final question. Take take a minute. To explain this year. Think What's the core theme? What's the most important story people should pay attention to this year and IBM think in San Francisco? >> I think this two things and the borders. That is the evolution that is giving greater business value for using the word that is Chapter two off the cloud journey. And it's Chapter two off a cognitive enterprise. Chapter two means that you're not getting into solving really mission critical workloads, and that's what is happening there. And that's enabled through the mixture of what we're calling hybrid on multi cloud strategies and then the cognitive enterprises all around. How can you bring air to power every workflow? It's not a little shiny Tonda. Besides, it's in the very heart off every confirmation. >> The word of the day. Here's anywhere cloud anywhere, data anywhere. Aye, aye, anywhere that's a cube were everywhere and anywhere we could go to get the signal from the noise. Arvin Krista, senior vice president, cloud and cognitive software's new title man Architect in the Red Hat Acquisition in the cloud Multi cloud DNA. Congratulations on your success. Looking forward to following your journey. Thanks for coming on, thanks Thanks. Safe. Okay. More live coverage after this short break state with the cube dot net is where you find the videos were in San Francisco. Live here in Mosconi, North and south, bringing the IBM think twenty nineteen. Stay with us.