>> Hey, welcome back. Your body, Jefe Rick here from the Cube were high atop San Francisco in the century innovation hub. It's in the middle of the Salesforce Tower. It's a beautiful facility. They think you had it. The grand opening about six months ago. We're here for the grand opening. Very cool space. I got maker studios. They've got all kinds of crazy stuff going on. But we're here today to talk about Cloud in this continuing evolution about cloud in the enterprise and hybrid cloud and multi cloud in Public Cloud and Private Cloud. And we're really excited to have a couple of guys who really helping customers make this journey, cause it's really tough to do by yourself. CEOs are super busy. There were about security and all kinds of other things, so centers, often a trusted partner. We got two of the leaders from center joining us today's Prasad Sankaran. He's the senior managing director of Intelligent Cloud infrastructure for Center Welcome and Larry Soccer, the global managing director. Intelligent cloud infrastructure offering from central gentlemen. Welcome. I love it. It intelligent cloud. What is an intelligent cloud all about? Got it in your title. It must mean something pretty significant. >> Yeah, I think First of all, thank you for having us, but yeah, absolutely. Everything's around becoming more intelligent around using more automation. And the work that, you know we delivered to our clients and cloud, as you know, is the platform to reach. All of our clients are moving. So it's all about bringing the intelligence not only into infrastructure, but also into cloud generally. And it's all driven by software, >> right? It's just funny to think where we are in this journey. We talked a little bit before we turn the cameras on and there you made an interesting comment when I said, You know, when did this cloud for the Enterprise start? And you took it back to sass based applications, which, >> you know you were sitting in the sales force builder. >> That's true. It isn't just the tallest building in >> everyone's, you know, everyone's got a lot of focus on AWS is rise, etcetera. But the real start was really getting into sass. I mean, I remember we used to do a lot of Siebel deployments for CR M, and we started to pivot to sales, for some were moving from remedy into service now. I mean, we've went through on premise collaboration, email thio 3 65 So So we've actually been at it for quite a while in the particularly the SAS world. And it's only more recently that we started to see that kind of push to the, you know, the public pass, and it's starting to cloud native development. But But this journey started, you know, it was that 78 years ago that we really started. See some scale around it. >> And I think and tell me if you agree, I think really, what? The sales forces of the world and and the service now is of the world office 3 65 kind of broke down some of those initial beers, which are all really about security and security, security, security, Always to hear where now security is actually probably an attributes and loud can brink. >> Absolutely. In fact, I mean, those barriers took years to bring down. I still saw clients where they were forcing salesforce tor service Now to put, you know, instances on prime and I think I think they finally woke up toe. You know, these guys invested ton in their security organizations. You know there's a little of that needle in the haystack. You know, if you breach a data set, you know what you're getting after. But when Europe into sales force, it's a lot harder. And so you know. So I think that security problems have certainly gone away. We still have some compliance, regulatory things, data sovereignty. But I think security and not not that it sold by any means that you know, it's always giving an ongoing problem. But I think they're getting more comfortable with their data being up in the in the public domain, right? Not public. >> And I think it also helped them with their progress towards getting cloud native. So, you know, you pick certain applications which were obviously hosted by sales force and other companies, and you did some level of custom development around it. And now I think that's paved the way for more complex applications and different workloads now going into, you know, the public cloud and the private cloud. But that's the next part of the journey, >> right? So let's back up 1/2 a step, because then, as you said, a bunch of stuff then went into public cloud, right? Everyone's putting in AWS and Google. Um, IBM has got a public how there was a lot more. They're not quite so many as there used to be, Um, but then we ran into a whole new host of issues, right, which is kind of opened up this hybrid cloud. This multi cloud world, which is you just can't put everything into a public clouds. There's certain attributes is that you need to think about and yet from the application point of view before you decide where you deploy that. So I'm just curious. If you can share now, would you guys do with clients? How should they think about applications? How should they think about what to deploy where I think >> I'll start in? The military has a lot of expertise in this area. I think you know, we have to obviously start from an application centric perspective. You go to take a look at you know where your applications have to live water. What are some of the data implications on the applications, or do you have by way of regulatory and compliance issues, or do you have to do as faras performance because certain applications have to be in a high performance environment. Certain other applications don't think a lot of these factors will. Then Dr where these applications need to recite and then what we think in today's world is really accomplish. Complex, um, situation where you have a lot of legacy. But you also have private as well as public cloud. So you approach it from an application perspective. >> Yeah. I mean, if you really take a look at Army, you look at it centers clients, and we were totally focused on up into the market Global 2000 savory. You know how clients typically have application portfolios ranging from 520,000 applications? And really, I mean, if you think about the purpose of cloud or even infrastructure for that, they're there to serve the applications. No one cares if your cloud infrastructure is not performing the absolute. So we start off with an application monetization approach and ultimately looking, you know, you know, with our tech advisory guys coming in, there are intelligent engineering service is to do the cloud native and at mod work our platforms, guys, who do you know everything from sales forward through ASAP. They should drive a strategy on how those applications gonna evolve with its 520,000 and determined hey, and usually using some, like the six orders methodology. And I'm I am I going to retire this Am I going to retain it? And, you know, I'm gonna replace it with sass. Am I gonna re factor in format? And it's ultimately that strategy that's really gonna dictate a multi and, you know, every cloud story. So it's based on the applications data, gravity issues where they gonna reside on their requirements around regulatory, the requirements for performance, etcetera. That will then dictate the cloud strategies. I'm you know, not a big fan of going in there and just doing a multi hybrid cloud strategy without a really good up front application portfolio approach, right? How we gonna modernize that >> it had. And how do you segment? That's a lot of applications. And you know, how do you know the old thing? How do you know that one by that time, how do you help them pray or size where they should be focusing on us? >> So typically what we do is work with our clients to do a full application portfolio analysis, and then we're able to then segment the applications based on, you know, important to the business and some of the factors that both of us mentioned. And once we have that, then we come up with an approach where certain sets of applications he moved to sass certain other applications you move to pass. So you know, you're basically doing the re factoring and the modernization and then certain others you know, you can just, you know, lift and shift. So it's really a combination off both modernization as well as migration. It's a combination off that, but to do that, you have to initially look at the entire set of applications and come up with that approach. >> I'm just curious where within that application assessment, um, where is cost savings? Where is, uh, this is just old. And where is opportunities to innovate faster? Because we know a lot of lot of talk really. Days has cost savings, but what the real advantages is execution speed if you can get it. If >> you could go back through four years and we had there was a lot of CEO discussions around cost savings, I'm not really have seen our clients shift. It costs never goes away, obviously right. But there's a lot greater emphasis now on business agility. You know, howto innovate faster, get getting your capabilities to market faster, to change my customer experience. So So it's really I t is really trying to step up and, you know, enabled the business toe to compete in the marketplace. We're seeing a huge shift in emphasis or focus at least starting with, you know, how'd I get better business agility outta leverage to cloud and cloud native development to get their upper service levels? Actually, we started seeing increase on Hey, you know, these applications need to work. It's actress. So So Obviously, cost still remains a factor, but we seem much more for, you know, much more emphasis on agility, you know, enabling the business on, given the right service levels of right experience to the user, little customers. Big pivot there, >> Okay. And let's get the definitions out because you know a lot of lot of conversation about public clouds, easy private clouds, easy but hybrid cloud and multi cloud and confusion about what those are. How do you guys define him? How do you help your customers think about the definition? Yes, >> I think it's a really good point. So what we're starting to see is there were a lot of different definitions out there. But I think as I talked more clients and our partners, I think we're all starting to, you know, come to ah, you know, the same kind of definition on multi cloud. It's really about using more than one cloud. But hybrid, I think, is a very important concept because hybrid is really all about the placement off the workload or where your application is going to run on. And then again, it goes to all of these points that we talked about data, gravity and performance and other things. Other factors. But it's really all about where do you place the specific look >> if you look at that, so if you think about public, I mean obviously gives us the innovation of the public providers. You look at how fast Amazon comes out with new versions of Lambda etcetera. So that's the innovations there obviously agility. You could spend up environments very quickly, which is, you know, one of the big benefits of it. The consumption, economic models. So that is the number of drivers that are pushing in the direction of public. You know, on the private side, they're still it's quite a few benefits that don't get talked about as much. Um, so you know, if you look at it, um, performance if you think the public world, you know, Although they're scaling up larger T shirts, et cetera, they're still trying to do that for a large array of applications on the private side, you can really Taylor somethingto very high performance characteristics. Whether it's you know, 30 to 64 terabyte Hana, you can get a much more focused precision environment for business. Critical workloads like that article, article rack, the Duke clusters, everything about fraud analysis. So that's a big part of it. Related to that is the data gravity that Prasad just mentioned. You know, if I've got a 64 terabyte Hana database you know, sitting in my private cloud, it may not be that convenient to go and put get that data shared up in red shift or in Google's tensorflow. So So there's some data gravity out. Networks just aren't there. The laden sea of moving that stuff around is a big issue. And then a lot of people of investments in their data centers. I mean, the other piece, that's interesting. His legacy, you know, you know, as we start to look at the world a lot, there's a ton of code still living in, You know, whether it's you, nick system, just IBM mainframes. There's a lot of business value there, and sometimes the business cases aren't aren't necessarily there toe to replace them. Right? And in world of digital, the decoupling where I can start to use micro service is we're seeing a lot of trends. We worked with one hotel to take their reservation system. You know, Rapid and Micro Service is, um, we then didn't you know, open shift couch base, front end. And now, when you go against, you know, when you go and browsing properties, you're looking at rates you actually going into distributed database cash on, you know, in using the latest cloud native technologies that could be dropped every two weeks or everything three or four days for my mobile application. And it's only when it goes, you know, when the transaction goes back, to reserve the room that it goes back there. So we're seeing a lot of power with digital decoupling, But we still need to take advantage of, you know, we've got these legacy applications. So So the data centers air really were trying to evolve them. And really, just, you know, how do we learn everything from the world of public and struck to bring those saints similar type efficiencies to the to the world of private? And really, what we're seeing is this emerging approach where I can start to take advantage of the innovation cycles. The land is that, you know, the red shifts the functions of the public world, but then maybe keep some of my more business critical regulated workloads. You know, that's the other side of the private side, right? I've got G X p compliance. If I've got hip, a data that I need to worry about GDP are there, you know, the whole set of regular two requirements. Now, over time, we do anticipate the public guys will get much better and more compliant. In fact, they made great headway already, but they're still not a number of clients are still, you know, not 100% comfortable from my client's perspective. >> Gotta meet Teresa Carlson. She'll change him, runs that AWS public sector is doing amazing things, obviously with big government contracts. But but you raise real inching point later. You almost described what I would say is really a hybrid application in this in this hotel example that you use because it's is, you know, kind of breaking the application and leveraging micro service is to do things around the core that allowed to take advantage of some this agility and hyper fast development, yet still maintain that core stuff that either doesn't need to move. Works fine, be too expensive. Drea Factor. It's a real different weight. Even think about workloads and applications into breaking those things into bits. >> And we see that pattern all over the place. I'm gonna give you the hotel Example Where? But finance, you know, look at financial service. Is retail banking so open banking a lot. All those rito applications are on the mainframe. I'm insurance claims and and you look at it the business value of replicating a lot of like the regulatory stuff, the locality stuff. It doesn't make sense to write it. There's no rule inherent business values of I can wrap it, expose it and in a micro service's architecture now D'oh cloud native front end. That's gonna give me a 360 view a customer, Change the customer experience. You know, I've got a much you know, I can still get that agility. The innovation cycles by public. Bye bye. Wrapping my legacy environment >> and percent you raided, jump in and I'll give you something to react to, Which is which is the single planet glass right now? How do I How did I manage all this stuff now? Not only do I have distributed infrastructure now, I've got distributed applications in the and the thing that you just described and everyone wants to be that single pane of glass. Everybody wants to be the app that's upon everybody. Screen. How are you seeing people deal with the management complexity of these kind of distributed infrastructures? If you will Yeah, >> I think that that's that's an area that's, ah, actually very topical these days because, you know, you're starting to see more and more workers go to private cloud. And so you've got a hybrid infrastructure you're starting to see move movement from just using the EMS to, you know, cantinas and Cuba needs. And, you know, we talked about Serval s and so on. So all of our clients are looking for a way, and you have different types of users as well. Yeah, developers. You have data scientists. You have, you know, operators and so on. So they're all looking for that control plane that allows them access and a view toe everything that is out there that is being used in the enterprise. And that's where I think you know, a company like Accenture were able to use the best of breed toe provide that visibility to our clients, >> right? Yeah. I mean, you hit the nail on the head. It's becoming, you know, with all the promises, cloud and all the power. And these new architectures is becoming much more dynamic, ephemeral, with containers and kubernetes with service computing that that that one application for the hotel, they're actually started in. They've got some, actually, now running a native us of their containers and looking at surveillance. So you're gonna even a single application can span that. And one of things we've seen is is first, you know, a lot of our clients used to look at, you know, application management, you know, different from their their infrastructure. And the lines are now getting very blurry. You need to have very tight alignment. You take that single application, if any my public side goes down or my mid tier with my you know, you know, open shipped on VM, where it goes down on my back and mainframe goes down. Or the networks that connected to go down the devices that talk to it. It's a very well. Despite the power, it's a very complex environment. So what we've been doing is first we've been looking at, you know, how do we get better synergy across what we you know, Application Service's teams that do that Application manager, an optimization cloud infrastructure. How do we get better alignment that are embedded security, You know, how do you know what are managed to security service is bringing those together. And then what we did was we looked at, you know, we got very aggressive with cloud for a strategy and, you know, how do we manage the world of public? But when looking at the public providers of hyper scale, er's and how they hit Incredible degrees of automation. We really looked at, said and said, Hey, look, you gotta operate differently in this new world. What can we learn from how the public guys we're doing that We came up with this concept. We call it running different. You know, how do you operate differently in this new multi speed? You know, you know, hot, very hybrid world across public, private demon, legacy, environment, and start a look and say, OK, what is it that they do? You know, first they standardize, and that's one of the big challenges you know, going to almost all of our clients in this a sprawl. And you know, whether it's application sprawl, its infrastructure, sprawl >> and my business is so unique. The Larry no business out there has the same process that way. So >> we started make you know how to be standardized like center hybrid cloud solution important with hp envy And where we how do we that was an example of so we can get to you because you can't automate unless you standardise. So that was the first thing you know, standardizing our service catalog. Standardizing that, um you know, the next thing is the operating model. They obviously operate differently. So we've been putting a lot of time and energy and what I call a cloud and agile operating model. And also a big part of that is truly you hear a lot about Dev ops right now. But truly putting the security and and operations into Deb said cops are bringing, you know, the development in the operations much tied together. So spending a lot of time looking at that and transforming operations re Skilling the people you know, the operators of the future aren't eyes on glass there. Developers, they're writing the data ingestion, the analytic algorithms, you know, to do predictive operations. They're riding the automation script to take work, you know, test work out right. And over time they'll be tuning the aye aye engines to really optimize environment. And then finally, has Prasad alluded to Is that the platforms that control planes? That doing that? So, you know what we've been doing is we've had a significant investments in the eccentric cloud platform, our infrastructure automation platforms, and then the application teams with it with my wizard framework, and we started to bring that together you know, it's an integrated control plane that can plug into our clients environments to really manage seamlessly, you know, and provide. You know, it's automation. Analytics. Aye, aye. Across APS, cloud infrastructure and even security. Right. And that, you know, that really is a I ops, right? I mean, that's delivering on, you know, as the industry starts toe define and really coalesce around, eh? I ops. That's what we you A ups. >> So just so I'm clear that so it's really your layer your software layer kind of management layer that that integrates all these different systems and provides kind of a unified view. Control? Aye, aye. Reporting et cetera. Right? >> Exactly. Then can plug in and integrate, you know, third party tools to do straight functions. >> I'm just I'm just curious is one of the themes that we here out in the press right now is this is this kind of pull back of public cloud app, something we're coming back. Or maybe it was, you know, kind of a rush. Maybe a little bit too aggressively. What are some of the reasons why people are pulling stuff back out of public clouds that just with the wrong. It was just the wrong application. The costs were not what we anticipated to be. We find it, you know, what are some of the reasons that you see after coming back in house? Yeah, I think it's >> a variety of factors. I mean, it's certainly cost, I think is one. So as there are multiple private options and you know, we don't talk about this, but the hyper skills themselves are coming out with their own different private options like an tars and out pulls an actor stack and on. And Ali Baba has obsessed I and so on. So you see a proliferation of that, then you see many more options around around private cloud. So I think the cost is certainly a factor. The second is I think data gravity is, I think, a very important point because as you're starting to see how different applications have to work together, then that becomes a very important point. The third is just about compliance, and, you know, the regulatory environment. As we look across the globe, even outside the U. S. We look at Europe and other parts of Asia as clients and moving more to the cloud. You know that becomes an important factor. So as you start to balance these things, I think you have to take a very application centric view. You see some of those some some maps moving back, and and I think that's the part of the hybrid world is that you know, you can have a nap running on the private cloud and then tomorrow you can move this. Since it's been containerized to run on public and it's, you know, it's all managed. That left >> E. I mean, cost is a big factor if you actually look at it. Most of our clients, you know, they typically you were a big cap ex businesses, and all of a sudden they're using this consumption, you know, consumption model. And they went, really, they didn't have a function to go and look at be thousands or millions of lines of it, right? You know, as your statement Exactly. I think they misjudged, you know, some of the scale on Do you know e? I mean, that's one of the reasons we started. It's got to be an application led, you know, modernization, that really that will dictate that. And I think In many cases, people didn't. May not have thought Through which application. What data? There The data, gravity data. Gravity's a conversation I'm having just by with every client right now. And if I've got a 64 terabyte Hana and that's the core, my crown jewels that data, you know, how do I get that to tensorflow? How'd I get that? >> Right? But if Andy was here, though, and he would say we'll send down the stove, the snow came from which virgin snow plows? Snowball Snowball. Well, they're snowballs. But I have seen the whole truck killer that comes out and he'd say, Take that and stick it in the cloud. Because if you've got that data in a single source right now, you can apply multitude of applications across that thing. So they, you know, they're pushing. Get that date end in this single source. Of course. Then to move it, change it. You know, you run into all these micro lines of billing statement, take >> the hotel. I mean, their data stolen the mainframe, so if they anyone need to expose it, Yeah, they have a database cash, and they move it out, You know, particulars of data sets get larger, it becomes, you know, the data. Gravity becomes a big issue because no matter how much you know, while Moore's Law might be might have elongated from 18 to 24 months, the network will always be the bottle Mac. So ultimately, we're seeing, you know, a CZ. We proliferate more and more data, all data sets get bigger and better. The network becomes more of a bottleneck. And that's a It's a lot of times you gotta look at your applications. They have. I've got some legacy database I need to get Thio. I need this to be approximately somewhere where I don't have, you know, high bandwith. Oh, all right. Or, you know, highlight and see type. Also, egress costs a pretty big deals. My date is up in the cloud, and I'm gonna get charged for pulling it off. You know, that's being a big issue, >> you know, it's funny, I think, and I think a lot of the the issue, obviously complexity building. It's a totally from building model, but I think to a lot of people will put stuff in a public cloud and then operated as if they bought it and they're running in the data center in this kind of this. Turn it on, Turn it off when you need it. Everyone turns. Everyone loves to talk about the example turning it on when you need it. But nobody ever talks about turning it off when you don't. But it kind of close on our conversation. I won't talk about a I and applied a Iot because he has a lot of talk in the market place. But, hey, I'm machine learning. But as you guys know pride better than anybody, it's the application of a I and specific applications, which really on unlocks the value. And as we're sitting here talking about this complexity, I can't help but think that, you know, applied a I in a management layer like your run differently, set up to actually know when to turn things on, when to turn things off when you moved in but not moved, it's gonna have to be machines running that right cause the data sets and the complexity of these systems is going to be just overwhelming. Yeah, yeah, >> absolutely. Completely agree with you. In fact, attack sensual. We actually refer to this whole area as applied intelligence on That's our guy, right? And it is absolutely to add more and more automation move everything Maur toe where it's being run by the machine rather than you know, having people really working on these things >> yet, e I mean, if you think you hit the nail on the head, we're gonna a eyes e. I mean, given how things getting complex, more ephemeral, you think about kubernetes et cetera. We're gonna have to leverage a humans or not to be able to get, you know, manage this. The environments comported right. What's interesting way we've used quite effectively for quite some time. But it's good at some stuff, not good at others. So we find it's very good at, like, ticket triage, like ticket triage, chicken rounding et cetera. You know, any time we take over account, we tune our AI ai engines. We have ticket advisers, etcetera. That's what probably got the most, you know, most bang for the buck. We tried in the network space, less success to start even with, you know, commercial products that were out there. I think where a I ultimately bails us out of this is if you look at the problem. You know, a lot of times we talked about optimizing around cost, but then performance. I mean, and it's they they're somewhat, you know, you gotta weigh him off each other. So you've got a very multi dimensional problem on howto I optimize my workloads, particularly. I gotta kubernetes cluster and something on Amazon, you know, sums running on my private cloud, etcetera. So we're gonna get some very complex environment. And the only way you're gonna be ableto optimize across multi dimensions that cost performance service levels, you know, And then multiple options don't do it public private, You know, what's my network costs etcetera. Isn't a I engine tuning that ai ai engines? So ultimately, I mean, you heard me earlier on the operators. I think you know, they write the analytic albums, they do the automation scripts, but they're the ultimate one too. Then tune the aye aye engines that will manage our environment. And I think it kubernetes will be interesting because it becomes a link to the control plane optimize workload placement. You know, between >> when the best thing to you, then you have dynamic optimization. Could you might be optimizing eggs at us right now. But you might be optimizing for output the next day. So exists really a you know, kind of Ah, never ending when you got me. They got to see them >> together with you and multi dimension. Optimization is very difficult. So I mean, you know, humans can't get their head around. Machines can, but they need to be trained. >> Well, Prasad, Larry, Lots of great opportunities for for centuries bring that expertise to the tables. So thanks for taking a few minutes to walk through some of these things. Our pleasure. Thank you, Grace. Besides Larry, I'm Jeff. You're watching the Cube. We are high above San Francisco in the Salesforce Tower, Theis Center, Innovation hub in San Francisco. Thanks for watching. We'll see you next time.

>> Hey, welcome back already, Jeffrey. Here with the Cube, we are high top San Francisco in the Salesforce Tower in the newest center offices. It's really beautiful and is part of that. They have their San Francisco innovation hubs, so it's five floors of maker's labs and three D printing and all kinds of test facilities and best practices Innovation theater and in this studio, which is really fun to be at. So we're talking about hybrid cloud in the development of cloud and multi cloud. And, you know, we're, you know, continuing on this path. Not only your customers on this path, but everyone's kind of on this path is the same kind of evolved and transformed. We're excited. Have a couple experts in the field. We got Larry Soccer. He's the global managing director of Intelligent Cloud Infrastructure Service's growth and strategy at a center. Very good to see you again. Great to be here. And the Jay Patel. He's the senior vice president and general manager, cloud provider, software business unit, being where enemies of the people are nice. Well, so, uh so first off, how you like the digs appear >> beautiful place and the fact we're part of the innovation team. Thank you for that. It's so let's just >> dive into it. So a lot of crazy stuff happening in the market place a lot of conversations about hybrid cloud, multi cloud, different cloud, public cloud movement of Back and forth from Cloud. Just wanted. Get your perspective a day. You guys have been in the Middle East for a while. Where are we in this kind of evolution? It still kind of feeling themselves out. Is it? We're kind of past the first inning, so now things are settling down. How do you kind of you. Evolution is a great >> question, and I think that was a really nice job of defining the two definitions. What's hybrid worse is multi and simply put hybrid. We look at hybrid as when you have consistent infrastructure. It's the same infrastructure, regardless of location. Multi is when you have disparate infrastructure. We're using them in a collective. So just from a level setting perspective, the taxonomy starting to get standardized industry starting to recognize hybrid is a reality. It's not a step in the long journey. It is an operating model that's gonna be exists for a long time, so it's no longer about location. It's a lot harder. You operate in a multi cloud and a hybrid cloud world and together, right extension BM would have a unique opportunity. Also, the technology provider Accenture, as a top leader in helping customers figure out where best to land their workload in this hybrid multicolored world, because workloads are driving decisions right and one of the year in this hybrid medical world for many years to come. But >> do I need another layer of abstraction? Cause I probably have some stuff that's in hybrid. I probably have some stuff in multi, right, because those were probably not much in >> the way we talked a lot about this, and Larry and I were >> chatting as well about this. And the reality is, the reason you choose a specific cloud is for those native different share capability. Abstraction should be just enough so you can make were close portable, really use the caper berry natively as possible right, and by fact, that we now with being where have a native VM we're running on every major hyper scaler, right? And on. Prem gives you that flexibility. You want off not having to abstract away the goodness off the cloud while having a common and consistent infrastructure. What tapping into the innovations that the public cloud brings. So it is a evolution of what we've been doing together from a private cloud perspective to extend that beyond the data center to really make it operating model. That's independent location, right? >> Solarium cures your perspective. When you work with customers, how do you help them frame this? I mean, I always feel so sorry for corporate CEOs. I mean, they got >> complexities on the doors are already going on >> like crazy that GDP are now, I think, right, The California regs. That'll probably go national. They have so many things to be worried about. They got to keep up on the latest technology. What's happening in containers away. I thought it was Dr Knight. Tell me it's kubernetes. I mean, it's really tough. So how >> do you help them? Kind of. It's got a shot with the foundation. >> I mean, you look at cloud, you look at infrastructure more broadly. I mean, it's there to serve the applications, and it's the applications that really drive business value. So I think the starting point has to be application lead. So we start off. We have are intelligent. Engineering guys are platform guys. You really come in and look And do you know an application modernisation strategy? So they'll do an assessment. You know, most of our clients, given their scale and complexity, usually have from 520,000 applications, very large estates, and they got to start to freak out. Okay, what's my current application's? You know, you're a lot of times I use the six R's methodology, and they say, OK, what is it that I I'm gonna retire. This I'm no longer needed no longer is business value, or I'm gonna, you know, replace this with sass. Well, you know, Yeah, if I move it to sales force, for example, or service now mattress. Ah, and then they're gonna start to look at their their workloads and say OK, you know, I don't need to re factor reform at this, you know, re hosted. You know, when one and things obviously be Emily has done a fantastic job is allowing you to re hosted using their softer to find a data center in the hyper scale er's environments >> that we called it just, you know, my great and then modernized. But >> the modern eyes can't be missed. I think that's where a lot of times you see clients kind of getting the trap Hammer's gonna migrate and then figure it out. You need to start tohave a modernisation strategy and then because that's ultimately going to dictate your multi and your hybrid cloud approaches, is how they're zaps evolve and, you know, they know the dispositions of those abs to figure out How do they get replaced? What data sets need to be adjacent to each other? So >> right, so a j you know, we were there when when Pat was with Andy and talking about, you know, Veum, Where on AWS. And then, you know, Sanjay has shown up, but everybody else's conferences a Google cloud talking about you know, Veum. Where? On Google Cloud. I'm sure there was a Microsoft show I probably missed. You guys were probably there to know it. It's kind of interesting, right from the outside looking in You guys are not a public cloud per se. And yet you've come up with this great strategy to give customers the options to adopt being We're in a public hot. And then now we're seeing where even the public cloud providers are saying here, stick this box in your data center and Frank, this little it's like a little piece of our cloud of floating around in your data center. So talk about the evolution of the strategy is kind of what you guys are thinking about because you know, you're cleared in a leadership position, making a lot of interesting acquisitions. How are you guys see this evolving? And how are you placing your bets? >> You know, that has been always consistent about this. Annie. Any strategy, whether it's any cloud, was any device, you know, any workload if you will, or application. And as we started to think about it, right, one of the big things be focused on was meeting the customer where he's out on its journey. Depending on the customer, let me simply be trying to figure out looking at the data center all the way to how the drive in digital transformation effort in a partner like Accenture, who has the breadth and depth and something, the vertical expertise and the insight. That's what customers looking for. Help me figure out in my journey. First tell me where, Matt, Where am I going and how I make that happen? And what we've done in a clever way, in many ways is we've created the market. We've demonstrated that VM where's the omen? Consistent infrastructure that you can bet on and leverage the benefits of the private or public cloud. And I You know, I often say hybrids a two way street. Now, which is you're bringing Maur more hybrid Cloud service is on Prem. And where is he? On Premise now the edge. I was talking to the centering folks and they were saying the mitral edge. So you're starting to see the workloads, And I think you said almost 40 plus percent off future workers that are gonna be in the central cloud. >> Yeah, actually, is an interesting stat out there. 20 years 2020 to 70% of data will be produced and processed outside the cloud. So I mean, the the edges about, you know, as we were on the tipping point of, you know, I ot finally taking off beyond, you know, smart meters. You know, we're gonna see a huge amount of data proliferate out there. So, I mean, the lines between public and private income literary output you look at, you know, Anthony, you know, as your staff for ages. So you know, And that's where you know, I think I am where strategy is coming to fruition >> sometime. It's great, >> you know, when you have a point of view and you stick with it >> against a conventional wisdom, suddenly end up together and then all of a sudden everyone's falling to hurt and you're like, This is great, but I >> hit on the point about the vertical ization. Every one of our client wth e different industries have very different has there and to the meeting that you know the customer, you know, where they're on their journey. I mean, if you talk to a pharmaceutical, you know, geekspeak compliance. Big private cloud started to dip their toes into public. You know, you go to minds and they're being very aggressive public. So >> every manufacturing with EJ boat back in >> the back, coming to it really varies by industry. >> And that's, you know, that's a very interesting here. Like if you look at all the ot environment. So the manufacturing we started see a lot of end of life of environment. So what's that? Next generation, you know, of control system's gonna run on >> interesting on the edge >> because and you've brought of networking a couple times where we've been talking it, you know, and as as, ah, potential gate right when I was still in the gates. But we're seeing Maura where we're at a cool event Churchill Club, when they had Xilinx micron and arm talking about, you know, shifting Maur that compute and store on these edge devices ti to accommodate, which you said, you know, how much of that stuff can you do at the adverse is putting in. But what I think is interesting is how are you going to manage that? There is a whole different level of management complexity when now you've got this different level of you're looting and security times many, many thousands of these devices all over the place. >> You might have heard >> recent announcements from being where around the carbon black acquisition right that combined with our work space one and the pulse I ot well, >> I'm now >> giving you a management framework with It's what people for things or devices and that consistency. Security on the client tied with the network security with NSX all the way to the data center, security were signed. A look at what we call intrinsic security. How do we bake and securing the platform and start solving these end to end and have a park. My rec center helped design these next generation application architectures are distributed by design. Where >> do you put a fence? You're you could put a fence around your data center, >> but your APP is using service now. Another SAS service is so hard to talk to an application boundary in the sea security model around that. It's a very interesting time. >> You hear a lot of you hear a >> lot about a partnership around softer to find data center on networking with Bello and NSX. But we're actually been spending a lot of time with the i o. T. Team and really looking at and a lot of our vision, the lines. I mean, you actually looked that they've been work similarly, agent technology with Leo where you know, ultimately the edge computing for io ti is gonna have to be containerized because you can need multiple middleware stacks supporting different vertical applications, right? We're actually you know what we're working with with one mind where we started off doing video analytics for predictive, you know, maintenance on tires for tractors, which are really expensive. The shovels, It's after we started pushing the data stream up it with a video stream up into azure. But the network became a bottleneck looking into fidelity. So we gotta process there. They're not looking autonomous vehicles which need eight megabits low laden C band with, you know, sitting at the the edge. Those two applications will need to co exist. And you know why we may have as your edge running, you know, in a container down, you know, doing the video analytics. If Caterpillar chooses, you know, Green Grass or Jasper that's going to co exist. So you see how the whole container ization that were started seeing the data center push out there on the other side of the pulse of the management of the edge is gonna be very difficult. I >> need a whole new frontier, absolutely >> moving forward. And with five g and telco. And they're trying to provide evaluated service is So what does that mean from an infrastructure perspective. Right? Right, Right. When do you stay on the five g radio network? Worse is jumping on the back line. And when do you move data? Where's his process? On the edge. Those all business decisions that need to be doing to some framework. >> You guys were going, >> we could go on. Go on, go. But I want to Don't fall upon your Segway from containers because containers were such an important part of this story and an enabler to the story. And, you know, you guys been aggressive. Move with hefty Oh, we've had Craig McCloskey, honor. He was still at Google and Dan great guys, but it's kind of funny, right? Cause three years ago, everyone's going to Dr Khan, right? I was like that were about shows that was hot show. Now doctors kind of faded and and kubernetes has really taken off. Why, for people that aren't familiar with kubernetes, they probably here to cocktail parties. If they live in the Bay Area, why's containers such an important enabler? And what's so special about Coburn? 80 specifically. >> Do you wanna go >> on the way? Don't talk about my products. I mean, if you >> look at the world is getting much more dynamics on the, you know, particularly you start to get more digitally to couple applications you started. You know, we've gone from a world where a virtual machine might have been up for months or years. Toe, You know, obviously you have containers that are much more dynamic, allowed to scale quickly, and then they need to be orchestrated. That's essential. Kubernetes does is just really starts to orchestrate that. And as we get more distributed workloads, you need to coordinate them. You need to be able to scale up as you need it for performance, etcetera. So kubernetes an incredible technology that allows you really to optimize, you know, the placement of that. So just like the virtual machine changed, how we compute containers now gives us a much more flexible portable. You know that, you know you can run on anything infrastructure, any location, you know, closer to the data, et cetera. To do that. And I >> think the bold movie >> made is, you know, we finally, after working with customers and partners like century, we have a very comprehensive strategy. We announced Project Enzo, a philosophy in world and Project tansy really focused on three aspects of containers. How do you build applications, which is pivotal in that mansion? People's driven around. How do we run these arm? A robust enterprise class run time. And what if you could take every V sphere SX out there and make it a container platform? Now we have half a million customers. 70 million be EMS, all of sudden that run time. We're continue enabling with the Project Pacific Soviets. Year seven becomes a commonplace for running containers, and I am so that debate of'em czar containers done gone well, one place or just spin up containers and resource is. And then the more important part is How do I manage this? You said, becoming more of a platform not just an orchestration technology, but a platform for how do I manage applications where I deploy them where it makes most sense, right? Have decoupled. My application needs from the resource is, and Coburn is becoming the platform that allows me to port of Lee. I'm the old job Web logic guy, right? >> So this is like distributed Rabb logic job on steroids, running across clouds. Pretty exciting for a middle where guy This is the next generation and the way you just said, >> And two, that's the enabling infrastructure that will allow it to roll into future things like devices. Because now you've got that connection >> with the fabric, and that's working. Becomes a key part of one of the key >> things, and this is gonna be the hard part is optimization. So how do we optimize across particularly performance, but even costs? >> You're rewiring secure, exact unavailability, >> Right? So still, I think my all time favorite business book is Clayton Christians. An innovator's dilemma. And in one of the most important lessons in that book is What are you optimizing four. And by rule, you can't optimize for everything equally you have to you have to rank order. But what I find really interesting in this conversation in where we're going in the complexity of the throughput, the complexity of the size of the data sets the complexity of what am I optimizing for now? Just begs for applied a I or this is not This is not a people problem to solve. This is this >> is gonna be all right. So you look at >> that, you know, kind of opportunity to now apply A I over the top of this thing opens up tremendous opportunity. >> Standardize infrastructural auditory allows you to >> get more metrics that allows you to build models to optimize infrastructure over time. >> And humans >> just can't get their head around me because you do have to optimize across multiple mentions. His performances cost, but then that performances gets compute. It's the network, I mean. In fact, the network's always gonna be the bottlenecks. You look at it even with five G, which is an order of magnitude, more bandwidth from throughput, the network will still lag. I mean, you go back to Moore's Law, right? It's Ah, even though it's extended to 24 months, price performance doubles. The amount of data potentially can kick in and you know exponentially grow on. Networks don't keep pays, so that optimization is constantly going to be tuned. And as we get even with increases in network, we have to keep balancing that right. >> But it's also the business >> optimization beyond the infrastructure optimization. For instance, if you're running a big power generation field of a bunch of turbines, right, you may wanna optimize for maintenance because things were running at some steady state. But maybe there's oil crisis or this or that. Suddenly the price, right? You're like, forget the maintenance. Right now we've got you know, we >> got a radio controlled you start about other >> than a dynamic industry. How do I really time change the behavior, right? Right. And more and more policy driven. Where the infrastructure smart enough to react based on the policy change you made. >> That's the world we >> want to get to. And we're far away from that, right? >> Yeah. I mean, I think so. Ultimately, I think the Cuban honeys controller gets an A I overlay and the operators of the future of tuning the Aye aye engines that optimizing, >> right? Right. And then we run into the whole thing, which we've talked about many times in this building with Dr Room, A child re from a center. Then you got the whole ethics overlay on top of the thing. That's a whole different conversation from their day. So before we wrap kind of just want to give you kind of last thoughts. Um, as you know, customers Aaron, all different stages of their journey. Hopefully, most of them are at least at least off the first square, I would imagine on the monopoly board What does you know, kind of just top level things that you would tell people that they really need just to keep always at the top is they're starting to make these considerations, starting to make these investments starting to move workloads around that they should always have kind of top >> of mind. For me, it's very simple. It's really about focused on the business outcome. Leverage the best resource for the right need and design. Architectures are flexible that give you a choice. You're not locked in and look for strategic partners with this technology partners or service's partners that alive you to guide because the complexities too high the number of choices that too high. You need someone with the breath in depth to give you that platform in which you can operate on. So we want to be the digital kind of the ubiquitous platform. From a software perspective, Neck Centuries wants to be that single partner who can help them guide on the journey. So I think that would be my ask. It's not thinking about who are your strategic partners. What is your architecture and the choices you're making that gave you that flexibility to evolve. Because this is a dynamic market. What should make decisions today? I mean, I'll be the one you need >> six months even. Yeah. And And it's And that that dynamic that dynamics is, um is accelerating if you look at it. I mean, we've all seen change in the industry of decades in the industry, but the rate of change now the pace, you know, things are moving so quickly. >> I mean, little >> respond competitive or business or in our industry regulations, right. You have to be prepared for >> Yeah. Well, gentlemen, thanks for taking a few minutes and ah, great conversation. Clearly, you're in a very good space because it's not getting any less complicated in >> Thank you. Thank you. All right. Thanks, Larry. Ajay, I'm Jeff. You're watching the Cube. >> We are top of San Francisco in the Salesforce Tower at the center Innovation hub. Thanks for watching. We'll see next time. Quick

>> Hey, welcome back. Your body, Jefe Rick here from the Cube were high atop San Francisco in the century innovation hub. It's in the middle of the Salesforce Tower. It's a beautiful facility. They think you had it. The grand opening about six months ago. We're here for the grand opening. Very cool space. I got maker studios. They've got all kinds of crazy stuff going on. But we're here today to talk about Cloud in this continuing evolution about cloud in the enterprise and hybrid cloud and multi cloud in Public Cloud and Private Cloud. And we're really excited to have a couple of guys who really helping customers make this journey, cause it's really tough to do by yourself. CEOs are super busy. There were about security and all kinds of other things, so centers, often a trusted partner. We got two of the leaders from center joining us today's Prasad Sankaran. He's the senior managing director of Intelligent Cloud infrastructure for Center Welcome and Larry Soccer, the global managing director. Intelligent cloud infrastructure offering from central gentlemen. Welcome. I love it. It intelligent cloud. What is an intelligent cloud all about? Got it in your title. It must mean something pretty significant. >> Yeah, I think First of all, thank you for having us, but yeah, absolutely. Everything's around becoming more intelligent around using more automation. And the work that, you know we delivered to our clients and cloud, as you know, is the platform to reach. All of our clients are moving. So it's all about bringing the intelligence not only into infrastructure, but also into cloud generally. And it's all driven by software, >> right? It's just funny to think where we are in this journey. We talked a little bit before we turn the cameras on and there you made an interesting comment when I said, You know, when did this cloud for the Enterprise start? And you took it back to sass based applications, which, >> you know you were sitting in the sales force builder. >> That's true. It isn't just the tallest building in >> everyone's, you know, everyone's got a lot of focus on AWS is rise, etcetera. But the real start was really getting into sass. I mean, I remember we used to do a lot of Siebel deployments for CR M, and we started to pivot to sales, for some were moving from remedy into service now. I mean, we've went through on premise collaboration, email thio 3 65 So So we've actually been at it for quite a while in the particularly the SAS world. And it's only more recently that we started to see that kind of push to the, you know, the public pass, and it's starting to cloud native development. But But this journey started, you know, it was that 78 years ago that we really started. See some scale around it. >> And I think and tell me if you agree, I think really, what? The sales forces of the world and and the service now is of the world office 3 65 kind of broke down some of those initial beers, which are all really about security and security, security, security, Always to hear where now security is actually probably an attributes and loud can brink. >> Absolutely. In fact, I mean, those barriers took years to bring down. I still saw clients where they were forcing salesforce tor service Now to put, you know, instances on prime and I think I think they finally woke up toe. You know, these guys invested ton in their security organizations. You know there's a little of that needle in the haystack. You know, if you breach a data set, you know what you're getting after. But when Europe into sales force, it's a lot harder. And so you know. So I think that security problems have certainly gone away. We still have some compliance, regulatory things, data sovereignty. But I think security and not not that it sold by any means that you know, it's always giving an ongoing problem. But I think they're getting more comfortable with their data being up in the in the public domain, right? Not public. >> And I think it also helped them with their progress towards getting cloud native. So, you know, you pick certain applications which were obviously hosted by sales force and other companies, and you did some level of custom development around it. And now I think that's paved the way for more complex applications and different workloads now going into, you know, the public cloud and the private cloud. But that's the next part of the journey, >> right? So let's back up 1/2 a step, because then, as you said, a bunch of stuff then went into public cloud, right? Everyone's putting in AWS and Google. Um, IBM has got a public how there was a lot more. They're not quite so many as there used to be, Um, but then we ran into a whole new host of issues, right, which is kind of opened up this hybrid cloud. This multi cloud world, which is you just can't put everything into a public clouds. There's certain attributes is that you need to think about and yet from the application point of view before you decide where you deploy that. So I'm just curious. If you can share now, would you guys do with clients? How should they think about applications? How should they think about what to deploy where I >> think I'll start in? The military has a lot of expertise in this area. I think you know, we have to obviously start from an application centric perspective. You go to take a look at you know where your applications have to live water. What are some of the data implications on the applications, or do you have by way of regulatory and compliance issues, or do you have to do as faras performance because certain applications have to be in a high performance environment. Certain other applications don't think a lot of these factors will. Then Dr where these applications need to recite and then what we think in today's world is really accomplish. Complex, um, situation where you have a lot of legacy. But you also have private as well as public cloud. So you approach it from an application perspective. >> Yeah. I mean, if you really take a look at Army, you look at it centers clients, and we were totally focused on up into the market Global 2000 savory. You know how clients typically have application portfolios ranging from 520,000 applications? And really, I mean, if you think about the purpose of cloud or even infrastructure for that, they're there to serve the applications. No one cares if your cloud infrastructure is not performing the absolute. So we start off with an application monetization approach and ultimately looking, you know, you know, with our tech advisory guys coming in, there are intelligent engineering service is to do the cloud native and at mod work our platforms, guys, who do you know everything from sales forward through ASAP. They should drive a strategy on how those applications gonna evolve with its 520,000 and determined hey, and usually using some, like the six orders methodology. And I'm I am I going to retire this Am I going to retain it? And, you know, I'm gonna replace it with sass. Am I gonna re factor in format? And it's ultimately that strategy that's really gonna dictate a multi and, you know, every cloud story. So it's based on the applications data, gravity issues where they gonna reside on their requirements around regulatory, the requirements for performance, etcetera. That will then dictate the cloud strategies. I'm you know, not a big fan of going in there and just doing a multi hybrid cloud strategy without a really good up front application portfolio approach, right? How we gonna modernize that >> it had. And how do you segment? That's a lot of applications. And you know, how do you know the old thing? How do you know that one by that time, how do you help them pray or size where they should be focusing on us? >> So typically what we do is work with our clients to do a full application portfolio analysis, and then we're able to then segment the applications based on, you know, important to the business and some of the factors that both of us mentioned. And once we have that, then we come up with an approach where certain sets of applications he moved to sass certain other applications you move to pass. So you know, you're basically doing the re factoring and the modernization and then certain others you know, you can just, you know, lift and shift. So it's really a combination off both modernization as well as migration. It's a combination off that, but to do that, you have to initially look at the entire set of applications and come up with that approach. >> I'm just curious where within that application assessment, um, where is cost savings? Where is, uh, this is just old. And where is opportunities to innovate faster? Because we know a lot of lot of talk really. Days has cost savings, but what the real advantages is execution speed if you can get it. If >> you could go back through four years and we had there was a lot of CEO discussions around cost savings, I'm not really have seen our clients shift. It costs never goes away, obviously right. But there's a lot greater emphasis now on business agility. You know, howto innovate faster, get getting your capabilities to market faster, to change my customer experience. So So it's really I t is really trying to step up and, you know, enabled the business toe to compete in the marketplace. We're seeing a huge shift in emphasis or focus at least starting with, you know, how'd I get better business agility outta leverage to cloud and cloud native development to get their upper service levels? Actually, we started seeing increase on Hey, you know, these applications need to work. It's actress. So So Obviously, cost still remains a factor, but we seem much more for, you know, much more emphasis on agility, you know, enabling the business on, given the right service levels of right experience to the user, little customers. Big pivot there, >> Okay. And let's get the definitions out because you know a lot of lot of conversation about public clouds, easy private clouds, easy but hybrid cloud and multi cloud and confusion about what those are. How do you guys define him? How do you help your customers think about the definition? Yes, >> I think it's a really good point. So what we're starting to see is there were a lot of different definitions out there. But I think as I talked more clients and our partners, I think we're all starting to, you know, come to ah, you know, the same kind of definition on multi cloud. It's really about using more than one cloud. But hybrid, I think, is a very important concept because hybrid is really all about the placement off the workload or where your application is going to run on. And then again, it goes to all of these points that we talked about data, gravity and performance and other things. Other factors. But it's really all about where do you place the specific look >> if you look at that, so if you think about public, I mean obviously gives us the innovation of the public providers. You look at how fast Amazon comes out with new versions of Lambda etcetera. So that's the innovations there obviously agility. You could spend up environments very quickly, which is, you know, one of the big benefits of it. The consumption, economic models. So that is the number of drivers that are pushing in the direction of public. You know, on the private side, they're still it's quite a few benefits that don't get talked about as much. Um, so you know, if you look at it, um, performance if you think the public world, you know, Although they're scaling up larger T shirts, et cetera, they're still trying to do that for a large array of applications on the private side, you can really Taylor somethingto very high performance characteristics. Whether it's you know, 30 to 64 terabyte Hana, you can get a much more focused precision environment for business. Critical workloads like that article, article rack, the Duke clusters, everything about fraud analysis. So that's a big part of it. Related to that is the data gravity that Prasad just mentioned. You know, if I've got a 64 terabyte Hana database you know, sitting in my private cloud, it may not be that convenient to go and put get that data shared up in red shift or in Google's tensorflow. So So there's some data gravity out. Networks just aren't there. The laden sea of moving that stuff around is a big issue. And then a lot of people of investments in their data centers. I mean, the other piece, that's interesting. His legacy, you know, you know, as we start to look at the world a lot, there's a ton of code still living in, You know, whether it's you, nick system, just IBM mainframes. There's a lot of business value there, and sometimes the business cases aren't aren't necessarily there toe to replace them. Right? And in world of digital, the decoupling where I can start to use micro service is we're seeing a lot of trends. We worked with one hotel to take their reservation system. You know, Rapid and Micro Service is, um, we then didn't you know, open shift couch base, front end. And now, when you go against, you know, when you go and browsing properties, you're looking at rates you actually going into distributed database cash on, you know, in using the latest cloud native technologies that could be dropped every two weeks or everything three or four days for my mobile application. And it's only when it goes, you know, when the transaction goes back, to reserve the room that it goes back there. So we're seeing a lot of power with digital decoupling, But we still need to take advantage of, you know, we've got these legacy applications. So So the data centers air really were trying to evolve them. And really, just, you know, how do we learn everything from the world of public and struck to bring those saints similar type efficiencies to the to the world of private? And really, what we're seeing is this emerging approach where I can start to take advantage of the innovation cycles. The land is that, you know, the red shifts the functions of the public world, but then maybe keep some of my more business critical regulated workloads. You know, that's the other side of the private side, right? I've got G X p compliance. If I've got hip, a data that I need to worry about GDP are there, you know, the whole set of regular two requirements. Now, over time, we do anticipate the public guys will get much better and more compliant. In fact, they made great headway already, but they're still not a number of clients are still, you know, not 100% comfortable from my client's perspective. >> Gotta meet Teresa Carlson. She'll change him, runs that AWS public sector is doing amazing things, obviously with big government contracts. But but you raise real inching point later. You almost described what I would say is really a hybrid application in this in this hotel example that you use because it's is, you know, kind of breaking the application and leveraging micro service is to do things around the core that allowed to take advantage of some this agility and hyper fast development, yet still maintain that core stuff that either doesn't need to move. Works fine, be too expensive. Drea Factor. It's a real different weight. Even think about workloads and applications into breaking those things into bits. >> And we see that pattern all over the place. I'm gonna give you the hotel Example Where? But finance, you know, look at financial service. Is retail banking so open banking a lot. All those rito applications are on the mainframe. I'm insurance claims and and you look at it the business value of replicating a lot of like the regulatory stuff, the locality stuff. It doesn't make sense to write it. There's no rule inherent business values of I can wrap it, expose it and in a micro service's architecture now D'oh cloud native front end. That's gonna give me a 360 view a customer, Change the customer experience. You know, I've got a much you know, I can still get that agility. The innovation cycles by public. Bye bye. Wrapping my legacy environment >> and percent you raided, jump in and I'll give you something to react to, Which is which is the single planet glass right now? How do I How did I manage all this stuff now? Not only do I have distributed infrastructure now, I've got distributed applications in the and the thing that you just described and everyone wants to be that single pane of glass. Everybody wants to be the app that's upon everybody. Screen. How are you seeing people deal with the management complexity of these kind of distributed infrastructures? If you >> will Yeah, I think that that's that's an area that's, ah, actually very topical these days because, you know, you're starting to see more and more workers go to private cloud. And so you've got a hybrid infrastructure you're starting to see move movement from just using the EMS to, you know, cantinas and Cuba needs. And, you know, we talked about Serval s and so on. So all of our clients are looking for a way, and you have different types of users as well. Yeah, developers. You have data scientists. You have, you know, operators and so on. So they're all looking for that control plane that allows them access and a view toe everything that is out there that is being used in the enterprise. And that's where I think you know, a company like Accenture were able to use the best of breed toe provide that visibility to our clients, >> right? Yeah. I mean, you hit the nail on the head. It's becoming, you know, with all the promises, cloud and all the power. And these new architectures is becoming much more dynamic, ephemeral, with containers and kubernetes with service computing that that that one application for the hotel, they're actually started in. They've got some, actually, now running a native us of their containers and looking at surveillance. So you're gonna even a single application can span that. And one of things we've seen is is first, you know, a lot of our clients used to look at, you know, application management, you know, different from their their infrastructure. And the lines are now getting very blurry. You need to have very tight alignment. You take that single application, if any my public side goes down or my mid tier with my you know, you know, open shipped on VM, where it goes down on my back and mainframe goes down. Or the networks that connected to go down the devices that talk to it. It's a very well. Despite the power, it's a very complex environment. So what we've been doing is first we've been looking at, you know, how do we get better synergy across what we you know, Application Service's teams that do that Application manager, an optimization cloud infrastructure. How do we get better alignment that are embedded security, You know, how do you know what are managed to security service is bringing those together. And then what we did was we looked at, you know, we got very aggressive with cloud for a strategy and, you know, how do we manage the world of public? But when looking at the public providers of hyper scale, er's and how they hit Incredible degrees of automation. We really looked at, said and said, Hey, look, you gotta operate differently in this new world. What can we learn from how the public guys we're doing that We came up with this concept. We call it running different. You know, how do you operate differently in this new multi speed? You know, you know, hot, very hybrid world across public, private demon, legacy, environment, and start a look and say, OK, what is it that they do? You know, first they standardize, and that's one of the big challenges you know, going to almost all of our clients in this a sprawl. And you know, whether it's application sprawl, its infrastructure, sprawl >> and my business is so unique. The Larry no business out there has the same process that way. So >> we started make you know how to be standardized like center hybrid cloud solution important with hp envy And where we how do we that was an example of so we can get to you because you can't automate unless you standardise. So that was the first thing you know, standardizing our service catalog. Standardizing that, um you know, the next thing is the operating model. They obviously operate differently. So we've been putting a lot of time and energy and what I call a cloud and agile operating model. And also a big part of that is truly you hear a lot about Dev ops right now. But truly putting the security and and operations into Deb said cops are bringing, you know, the development in the operations much tied together. So spending a lot of time looking at that and transforming operations re Skilling the people you know, the operators of the future aren't eyes on glass there. Developers, they're writing the data ingestion, the analytic algorithms, you know, to do predictive operations. They're riding the automation script to take work, you know, test work out right. And over time they'll be tuning the aye aye engines to really optimize environment. And then finally, has Prasad alluded to Is that the platforms that control planes? That doing that? So, you know what we've been doing is we've had a significant investments in the eccentric cloud platform, our infrastructure automation platforms, and then the application teams with it with my wizard framework, and we started to bring that together you know, it's an integrated control plane that can plug into our clients environments to really manage seamlessly, you know, and provide. You know, it's automation. Analytics. Aye, aye. Across APS, cloud infrastructure and even security. Right. And that, you know, that really is a I ops, right? I mean, that's delivering on, you know, as the industry starts toe define and really coalesce around, eh? I ops. That's what we you A ups. >> So just so I'm clear that so it's really your layer your software layer kind of management layer that that integrates all these different systems and provides kind of a unified view. Control? Aye, aye. Reporting et cetera. Right? >> Exactly. Then can plug in and integrate, you know, third party tools to do straight functions. >> I'm just I'm just curious is one of the themes that we here out in the press right now is this is this kind of pull back of public cloud app, something we're coming back. Or maybe it was, you know, kind of a rush. Maybe a little bit too aggressively. What are some of the reasons why people are pulling stuff back out of public clouds that just with the wrong. It was just the wrong application. The costs were not what we anticipated to be. We find it, you know, what are some of the reasons that you see after coming back in house? Yeah, I think it's >> a variety of factors. I mean, it's certainly cost, I think is one. So as there are multiple private options and you know, we don't talk about this, but the hyper skills themselves are coming out with their own different private options like an tars and out pulls an actor stack and on. And Ali Baba has obsessed I and so on. So you see a proliferation of that, then you see many more options around around private cloud. So I think the cost is certainly a factor. The second is I think data gravity is, I think, a very important point because as you're starting to see how different applications have to work together, then that becomes a very important point. The third is just about compliance, and, you know, the regulatory environment. As we look across the globe, even outside the U. S. We look at Europe and other parts of Asia as clients and moving more to the cloud. You know that becomes an important factor. So as you start to balance these things, I think you have to take a very application centric view. You see some of those some some maps moving back, and and I think that's the part of the hybrid world is that you know, you can have a nap running on the private cloud and then tomorrow you can move this. Since it's been containerized to run on public and it's, you know, it's all managed. That >> left E. I mean, cost is a big factor if you actually look at it. Most of our clients, you know, they typically you were a big cap ex businesses, and all of a sudden they're using this consumption, you know, consumption model. And they went, really, they didn't have a function to go and look at be thousands or millions of lines of it, right? You know, as your statement Exactly. I think they misjudged, you know, some of the scale on Do you know e? I mean, that's one of the reasons we started. It's got to be an application led, you know, modernization, that really that will dictate that. And I think In many cases, people didn't. May not have thought Through which application. What data? There The data, gravity data. Gravity's a conversation I'm having just by with every client right now. And if I've got a 64 terabyte Hana and that's the core, my crown jewels that data, you know, how do I get that to tensorflow? How'd I get that? >> Right? But if Andy was here, though, and he would say we'll send down the stove, the snow came from which virgin snow plows? Snowball Snowball. Well, they're snowballs. But I have seen the whole truck killer that comes out and he'd say, Take that and stick it in the cloud. Because if you've got that data in a single source right now, you can apply multitude of applications across that thing. So they, you know, they're pushing. Get that date end in this single source. Of course. Then to move it, change it. You know, you run into all these micro lines of billing statement, take >> the hotel. I mean, their data stolen the mainframe, so if they anyone need to expose it, Yeah, they have a database cash, and they move it out, You know, particulars of data sets get larger, it becomes, you know, the data. Gravity becomes a big issue because no matter how much you know, while Moore's Law might be might have elongated from 18 to 24 months, the network will always be the bottle Mac. So ultimately, we're seeing, you know, a CZ. We proliferate more and more data, all data sets get bigger and better. The network becomes more of a bottleneck. And that's a It's a lot of times you gotta look at your applications. They have. I've got some legacy database I need to get Thio. I need this to be approximately somewhere where I don't have, you know, high bandwith. Oh, all right. Or, you know, highlight and see type. Also, egress costs a pretty big deals. My date is up in the cloud, and I'm gonna get charged for pulling it off. You know, that's being a big issue, >> you know, it's funny, I think, and I think a lot of the the issue, obviously complexity building. It's a totally from building model, but I think to a lot of people will put stuff in a public cloud and then operated as if they bought it and they're running in the data center in this kind of this. Turn it on, Turn it off when you need it. Everyone turns. Everyone loves to talk about the example turning it on when you need it. But nobody ever talks about turning it off when you don't. But it kind of close on our conversation. I won't talk about a I and applied a Iot because he has a lot of talk in the market place. But, hey, I'm machine learning. But as you guys know pride better than anybody, it's the application of a I and specific applications, which really on unlocks the value. And as we're sitting here talking about this complexity, I can't help but think that, you know, applied a I in a management layer like your run differently, set up to actually know when to turn things on, when to turn things off when you moved in but not moved, it's gonna have to be machines running that right cause the data sets and the complexity of these systems is going to be just overwhelming. >> Yeah, yeah, absolutely. Completely agree with you. In fact, attack sensual. We actually refer to this whole area as applied intelligence on That's our guy, right? And it is absolutely to add more and more automation move everything Maur toe where it's being run by the machine rather than you know, having people really working on these things >> yet, e I mean, if you think you hit the nail on the head, we're gonna a eyes e. I mean, given how things getting complex, more ephemeral, you think about kubernetes et cetera. We're gonna have to leverage a humans or not to be able to get, you know, manage this. The environments comported right. What's interesting way we've used quite effectively for quite some time. But it's good at some stuff, not good at others. So we find it's very good at, like, ticket triage, like ticket triage, chicken rounding et cetera. You know, any time we take over account, we tune our AI ai engines. We have ticket advisers, etcetera. That's what probably got the most, you know, most bang for the buck. We tried in the network space, less success to start even with, you know, commercial products that were out there. I think where a I ultimately bails us out of this is if you look at the problem. You know, a lot of times we talked about optimizing around cost, but then performance. I mean, and it's they they're somewhat, you know, you gotta weigh him off each other. So you've got a very multi dimensional problem on howto I optimize my workloads, particularly. I gotta kubernetes cluster and something on Amazon, you know, sums running on my private cloud, etcetera. So we're gonna get some very complex environment. And the only way you're gonna be ableto optimize across multi dimensions that cost performance service levels, you know, And then multiple options don't do it public private, You know, what's my network costs etcetera. Isn't a I engine tuning that ai ai engines? So ultimately, I mean, you heard me earlier on the operators. I think you know, they write the analytic albums, they do the automation scripts, but they're the ultimate one too. Then tune the aye aye engines that will manage our environment. And I think it kubernetes will be interesting because it becomes a link to the control plane optimize workload placement. You know, between >> when the best thing to you, then you have dynamic optimization. Could you might be optimizing eggs at us right now. But you might be optimizing for output the next day. So exists really a you know, kind of Ah, never ending when you got me. They got to see them >> together with you and multi dimension. Optimization is very difficult. So I mean, you know, humans can't get their head around. Machines can, but they need to be trained. >> Well, Prasad, Larry, Lots of great opportunities for for centuries bring that expertise to the tables. So thanks for taking a few minutes to walk through some of these things. Our pleasure. Thank you, Grace. Besides Larry, I'm Jeff. You're watching the Cube. We are high above San Francisco in the Salesforce Tower, Theis Center, Innovation hub in San Francisco. Thanks for watching. We'll see you next time.

>> Narrator: TheCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) (logo background tingles) >> Hey everyone, it's so good to see you, welcome back to theCube's day two coverage of MWC 23. We are live in Barcelona, Lisa Martin with Dave Nicholson, Dave we have had no signage of people dropping out, this conference is absolutely jam packed. There's so much interest in the industry, you've had a lot of interviews this morning, before we introduce our guests and have a great conversation about the industry and challenges and how they're being solved, what are some of the things that stuck out to you in conversations today? >> Well, I think the interesting, kind of umbrella conversation, that seems to be overlapping you know, overlying everything is this question about Open RAN and open standards in radio access network technology and where the operators of networks and the providers of technology come together to chart a better path forward. A lot of discussion of private 5G networks, it's very interesting, I think I've said this a few times, from a consumer's perspective, we feel like 5G has been with us for a long time- >> We do. >> But it's very clear that this, that we're really at the beginning of stages of this and I'm super excited for our guests that we have here because we're going to be able to talk to an actual operator- >> Yes. >> And hear what they have to say, we've heard a lot of people talking about the cool stuff they build, but we're going to get to hear from someone who actually works with this stuff, so- >> Who actually built it, absolutely. Please welcome our two guests, we have Ihab Tarazi CTO and SVP at Dell Technologies, and Juan Carlos Garcia SVP Technology Innovation and Ecosystems at Telephonica, it's great to have you guys on the program. >> So, thank you very much. >> So the buzz around this conference is incredible, 80,000 plus people, 2000 exhibitors, it's standing room only. Lot of opportunity in the industry, a lot of challenges though, Juan Carlos we'd love to get your perspective on, what are some of the industry challenges that Telephonica has faced that your peers are probably facing as well? >> Well we have two kinds of challenges, one is a business challenge, I would say that we may find in other industries, like profitability and growth and I will talk about it. And the second challenge is our technology challenge, we need the network to be ready to embrace a new wave of technologies and applications that are, you know, very demanding in terms of network characteristics and features. On the efficiency and profitability and growth, the solution comes as a challenge from changing the way networks are built and operated, from the traditional way to make them become software platforms. And this is not just at the knowledge challenge, it's also changing the mindset of network operators from a network and service provider to a digital service provider, okay? And this means several things, your network needs to become software-based so that you can manage it digitally and on top of it, you need to be able to deliver detail services digitally, okay? So there are three aspects, making your network so (indistinct) and cloud and cloud waste and then be able to sell in a different way to our customers. >> So some pretty significant challenges, but to your point, Juan Carlos, you share some of those challenges with other industries so there's some commonality there. I wanted to bring Ihab into the conversation, from Dell's perspective, we're seeing, you know, the explosion of data. Every company has to be a data company, we expect to have access to data in real time, if it's a new app, whatever it is. What are some of the challenges that you're seeing from your seat at Dell? >> Yeah, I think Juan Carlos explained that really well, what all the operators are talking about here between new applications, think metaverse, think video streaming, going all the way to the edge, think all the automation of factories and everything that's happening. It's not only requiring a whole new model for delivery and for building networks, but it's throwing out enormous amount of data and the data needs to be acted on to get the value of it. So the challenge is how do I collect the data? How do I catalog it? How do I make it usable? And then how do I make it persistent? So you know, it's high performance data storage and then after that, how do I move it to where I want to and be able to use it. And for many applications that has to happen in milliseconds for the value to come out. So now we've seen this before with enterprise but now I would say this digital transformation is happening at very large scale for all the telcos and starting to deal with very familiar themes we've seen before. >> So Juan Carlos, Telephonica, you hear from partners, vendors that they've done this before, don't worry, you're in good hands. >> Juan Carlos: Yeah, yeah. >> But as a practical matter, when you look at the challenges that you have and you think about the things you'll do to address them as you move forward, what are the immediate short term priorities? >> Okay. >> Versus the longer term priorities? What's realistic? You have a network to operate- >> Yeah. >> You're not just building something out of nothing, so you have to keep the lights on. >> Yeah. >> And you have to innovate, we call that by the way, in the CTO trade, ambidextrous, management using both hands, so what's your order of priorities? >> Well, the first thing, new technologies you are getting into the network need to come with a detail shape, so being cloud native, working by software. On the legacies that you need to keep alive, you need to go for a program to switch (indistinct) off progressively, okay? In fact, in Spain we are going to switch up the copper network in two years, so in 2024, Telephonica will celebrate 100 years and the celebration will be switching up the copper network and we'll have on the fixed access only fiber, okay. So more than likely, the network is necessary, all this digitalization may happen only on the new technologies because the new technologies are cloud-based, cloud native, become already ready for this digitalization process. And not only that, so you need also to build new things, we need an abstraction layer on top of the physical infrastructure to be able to manage the network by software, okay. This is something that happened in the computing world, okay, where the servers, you know, were covered with a cloud stack layer and we are doing the same thing in the network. We are trained to abstract the network services and capabilities and be able to offer them digitally to our customers. And this is a process that we are ongoing with many initiatives in the market, so one was the CAMARA community that was opened in Linux Foundation and the other one was the announcement we made yesterday of the open gateway initiative here at Mobile World Congress where all telecom operators have agreed to launch in this year a set of service APIs that are common worldwide, okay. This is a similar thing to what we did with 2G 35 years ago, to agree on a standard way of delivering a service and in this case is digital services based on APIs. >> What's the net result of? What are the benefits of having those open standards? Is it a benefit that myself as a consumer would enjoy? It seems, I mean, I've been, I'm old enough to remember, you know, a time before cellular telephones and I remember a time when it was very, very difficult to travel from North America to Europe with a cell phone. Now I land and my provider says, "Hey, welcome-" >> Juan Carlos: Yes. >> "Welcome, we're going to charge you a little extra money." And I say, "Hallelujah, awesome." So is part of that interoperability a benefit to consumers or, how, what? >> Yeah, you touch the right point. So in the same way you travel anywhere and you want to still make a call and send an SMS and connect to the internet, you will like your applications in your smartphone to work being them edge applications, okay, and these applications, each application will have to work to be executed very close to where you are, in a way that if you travel abroad the visitor network is serving you, okay. So this means that we are somehow extending the current interconnection and roaming agreements between operators to be able also to deliver edge applications wherever you are, in whatever network, with whatever technology. >> We have that expectation on the consumer side, that it's just going to work no matter where we are, we want apps to be updated, whether I'm banking or I'm shopping for groceries, I want to make sure that they know who I am, the data's got to be there, it's got to be real time, it's got to be right, it's got to serve me personally, but it just has to work. You guys talked about some of the big challenges, but also the opportunities in terms of the future of networking, the data turning companies in the data companies. Walk us through the future of networking from Telephonica's lens, you talked about some of the big initiatives that you have by 2024. >> Yes. >> But if you had a crystal ball and you could look in there and go it looks like this for operators, what would you say? And I'd love to get your feedback too. >> Yeah, I liked how Juan Carlos talked about how the future is, I think I want to add one thing to it, to say, a lot of times the user is no longer a consumer, it's an automated thing, you know, AI think robots, so a lot of times, more and more the usage is happening by some autonomous thing and it needs to always connect. And more and more these things are extending to places where even cellular coverage doesn't exist today, so you have edge compute show up. So, and when you think about it, the things we have to solve as a community here and this is all the discussions is, number one, how you make it a fully open standard model, so everything plugs and play, more and more, there's so many pieces coming, software, hardware, from different components and the integration of all of that is probably one of the biggest challenges people want solved. You know, how it's no longer one box, you buy from one person and put it away, now you have a complex combination of hardware and software. Also the operational model is very important and that is one of the areas we're focused on at Dell, is that while the operational model works inside the data centers for certain application, for telcos, it looks different when you're out at the cell tower and you're going to have these extended temperature changes. And sometimes this may not be inside a cabinet, maybe outside and the person servicing it is not an IT technician. This is somebody that needs to know exactly how to plug it, to be able to place equipment quickly and add capacity, those are just two of the areas, the cloud, making it work like a cloud, where it's intuitive, automated and you can easily add capacity, you can, you know, get a lot of monitoring, a lot of metrics, those are some of the things that we're all solving in this community. >> Let's talk about exactly how you're achieving this, Telephonica and Dell have been working together for a couple of years, you said before we went live. Talk about, you're doing this, you talked about the challenges, the opportunities how are you solving them and why with Dell? >> Okay, well you need to go with the right partners, not to this kind of process of transforming your network into a digital platform. There are big challenges on creating the cloud infrastructure that you need to support the complex, functionality and network requires. And I think you need to have with you, companies that know about the processors, that know about the hardware, the server, that know about how to make an abstraction of that hardware layer so that you can manage that digitally and this is not something any company can do, so you need companies that are very specialized. Telecom operators are changing the way to work, we work in the past with traditionally, with network equipment vendors, now we need to start working with technology providers, hardware (indistinct) providers with cloud providers with an ecosystem that is probably wider than what we had in the past. >> Yes. >> So I come from a background, I call myself a "knuckle dragging hardware engineer" sort of guy, so I'm almost fascinated by the physical part of this. You have a network, part of that network includes towers that have transmitters, receivers, at the base of those towers and like you mentioned, they're not all necessarily in urban areas or easy to access. There's equipment there, let's say that, that tower has been there for 5 years, 10 years, in the traditional world of IT, we have this this concept of the "refresh cycle" >> Juan Carlos: Yeah. >> Where a server may have a useful life of 36 months before it's consuming more power than it should based on the technology. How do you move from, kind of a legacy more proprietary, all-inclusive stack to an open system? I mean, is this a, "Okay, we're planning for an outage for the tower and you're wheeling out old equipment and wheeling in new equipment?" >> Juan Carlos: Yeah. >> I mean that's not, that's what we say as a non-trivial exercise, it's something that isn't, it's not something that's just easy to do, but is that what progress looks like? Sort of, methodically one site at a time? >> Yeah, well, I mean, you have touched an important point. In the technology renewal cycles, we were taking an appliance and replacing that by another one. Now with the current technology, you have the couple, the hardware from the software and the hardware, you need to replace it only when you run out of processing capacity to do what you want, okay? So then we'll be there 2, 3, 4, 5 years, whatever, when you need additional capacity, you replace it, but on the software side you can make the replacement every hour, every week. And this is something that the new technologies are bringing, a flexibility for the telecom operator to introduce a new feature without having to be physically there in the place, okay, by software remotely and this is the kind of software network we want to build. >> Lisa Martin: You know- >> Yeah, I want to add to that if I can- >> Please. >> Yeah. >> I think this is one of the biggest benefits of the open model. If the stack is all integrated as one appliance, when a new technology, we all know how quickly selecon technology comes out and now we have GPU's coming out for AI more increasingly, in an appliance model it may take you two years to take advantage of some new selecon that just came out. In this new open model, as Juan Carlos was saying, you just swap out, you know, you have time to market CPUs launched, it can be put out there at the cell tower and it could double capacity instantly and we're going to need that in that world, that easily going to be AI enabled- >> Lisa Martin: Right. >> So- >> So my last question to you, we only got a minute left or so, is given everything that we've talked about, the challenges, the opportunities, what you're doing together, how would you Juan Carlos summarize how the business is benefiting from the Dell partnership and the technologies that you're enabling with this new future network? >> Well, as I said before, we will need to be able to cover all the characteristics and performance of our network. We will need the right kind of processing capacity, the right kind of hardware solutions. We know that the functionality of the network is a very demanding one, we need hardware acceleration, we need a synchronization, we need time-sensitive solutions and all these can only done by hardware, so you need a good hardware partner, that ensures that you have the processing capacity you need to be able then to run your software, you know, with the confidence that it will work and with the performance that you need. >> That confidence is key. Well it sounds like what Telephonica and Dell have achieved together has been quite successful. Congratulations on the first couple of years, sounds like it's really helping Telephonica's business move in the strategic direction that it wants. We appreciate you joining us on the program today, describing all this, thank you both so much for your time. >> Thank you very much. >> Thank you, this was fun. >> A pleasure. >> Good, our pleasure. For our guests and for Dave Nicholson, I'm Lisa Martin, you're watching theCUBE live day two from Barcelona, MWC 23. Don't go anywhere, Dave and I will be right back with our next guests. (cheerful bouncy music)

(bright music) >> "Supermetafragilisticexpialadotious." What's in a name? In an homage to the inimitable Charles Fitzgerald, we've chosen this title for today's session because of all the buzz surrounding "supercloud," a term that we introduced last year to signify a major architectural trend and shift that's occurring in the technology industry. Since that time, we've published numerous videos and articles on the topic, and on August 9th, kicked off "Supercloud22," an open industry event designed to advance the supercloud conversation, gathering input from more than 30 experienced technologists and business leaders in "The Cube" and broader technology community. We're talking about individuals like Benoit Dageville, Kit Colbert, Ali Ghodsi, Mohit Aron, David McJannet, and dozens of other experts. And today, we're pleased to welcome David Linthicum, who's a Chief Strategy Officer of Cloud Services at Deloitte Consulting. David is a technology visionary, a technical CTO. He's an author and a frequently sought after keynote speaker at high profile conferences like "VMware Explore" next week. David Linthicum, welcome back to "The Cube." Good to see you again. >> Oh, it's great to be here. Thanks for the invitation. Thanks for having me. >> Yeah, you're very welcome. Okay, so this topic of supercloud, what you call metacloud, has created a lot of interest. VMware calls it cross-cloud services, Snowflake calls it their data cloud, there's a lot of different names, but recently, you published a piece in "InfoWorld" where you said the following. "I really don't care what we call it, "and I really don't care if I put "my own buzzword into the mix. "However, this does not change the fact "that metacloud is perhaps the most important "architectural evolution occurring right now, "and we need to get this right out of the gate. "If we do that, who cares what it's named?" So very cool. And you also mentioned in a recent article that you don't like to put out new terms out in the wild without defining them. So what is a metacloud, or what we call supercloud? What's your definition? >> Yeah, and again, I don't care what people call it. The reality is it's the ability to have a layer of cross-cloud services. It sits above existing public cloud providers. So the idea here is that instead of building different security systems, different governance systems, different operational systems in each specific cloud provider, using whatever native features they provide, we're trying to do that in a cross-cloud way. So in other words, we're pushing out data integration, security, all these other things that we have to take care of as part of deploying a particular cloud provider. And in a multicloud scenario, we're building those in and between the clouds. And so we've been tracking this for about five years. We understood that multicloud is not necessarily about the particular public cloud providers, it's about things that you build in and between the clouds. >> Got it, okay. So I want to come back to that, to the definition, but I want to tie us to the so-called multicloud. You guys did a survey recently. We've said that multicloud was mostly a symptom of multi-vendor, Shadow Cloud, M&A, and only recently has become a strategic imperative. Now, Deloitte published a survey recently entitled "Closing the Cloud Strategy, Technology, Innovation Gap," and I'd like to explore that a little bit. And so in that survey, you showed data. What I liked about it is you went beyond what we all know, right? The old, "Our research shows that on average, "X number of clouds are used at an individual company." I mean, you had that too, but you really went deeper. You identified why companies are using multiple clouds, and you developed different categories of practitioners across 500 survey respondents. But the reasons were very clear for "why multicloud," as this becomes more strategic. Service choice scale, negotiating leverage, improved business resiliency, minimizing lock-in, interoperability of data, et cetera. So my question to you, David, is what's the problem supercloud or metacloud solves, and what's different from multicloud? >> That's a great question. The reality is that if we're... Well, supercloud or metacloud, whatever, is really something that exists above a multicloud, but I kind of view them as the same thing. It's an architectural pattern. We can name it anything. But the reality is that if we're moving to these multicloud environments, we're doing so to leverage best of breed things. In other words, best of breed technology to provide the innovators within the company to take the business to the next level, and we determine that in the survey. And so if we're looking at what a multicloud provides, it's the ability to provide different choices of different services or piece parts that allows us to build anything that we need to do. And so what we found in the survey and what we found in just practice in dealing with our clients is that ultimately, the value of cloud computing is going to be the innovation aspects. In other words, the ability to take the company to the next level from being more innovative and more disruptive in the marketplace that they're in. And the only way to do that, instead of basically leveraging the services of a particular walled garden of a single public cloud provider, is to cast a wider net and get out and leverage all kinds of services to make these happen. So if you think about that, that's basically how multicloud has evolved. In other words, it wasn't planned. They didn't say, "We're going to go do a multicloud." It was different developers and innovators in the company that went off and leveraged these cloud services, sometimes with the consent of IT leadership, sometimes not. And now we have these multitudes of different services that we're leveraging. And so many of these enterprises are going from 1000 to, say, 3000 services under management. That creates a complexity problem. We have a problem of heterogeneity, different platforms, different tools, different services, different AI technology, database technology, things like that. So the metacloud, or the supercloud, or whatever you want to call it, is the ability to deal with that complexity on the complexity's terms. And so instead of building all these various things that we have to do individually in each of the cloud providers, we're trying to do so within a cross-cloud service layer. We're trying to create this layer of technology, which removes us from dealing with the complexity of the underlying multicloud services and makes it manageable. Because right now, I think we're getting to a point of complexity we just can't operate it at the budgetary limits that we are right now. We can't keep the number of skills around, the number of operators around, to keep these things going. We're going to have to get creative in terms of how we manage these things, how we manage a multicloud. And that's where the supercloud, metacloud, whatever they want to call it, comes that. >> Yeah, and as John Furrier likes to say, in IT, we tend to solve complexity with more complexity, and that's not what we're talking about here. We're talking about simplifying, and you talked about the abstraction layer, and then it sounds like I'm inferring more. There's value that's added on top of that. And then you also said the hyperscalers are in a walled garden. So I've been asked, why aren't the hyperscalers superclouds? And I've said, essentially, they want to put your data into their cloud and keep it there. Now, that doesn't mean they won't eventually get into that. We've seen examples a little bit, Outposts, Anthos, Azure Arc, but the hyperscalers really aren't building superclouds or metaclouds, at least today, are they? >> No, they're not. And I always have the predictions for every major cloud conference that this is the conference that the hyperscaler is going to figure out some sort of a multicloud across-cloud strategy. In other words, building services that are able to operate across clouds. That really has never happened. It has happened in dribs and drabs, and you just mentioned a few examples of that, but the ability to own the space, to understand that we're not going to be the center of the universe in how people are going to leverage it, is going to be multiple things, including legacy systems and other cloud providers, and even industry clouds that are emerging these days, and SaaS providers, and all these things. So we're going to assist you in dealing with complexity, and we're going to provide the core services of being there. That hasn't happened yet. And they may be worried about conflicting their market, and the messaging is a bit different, even actively pushing back on the concept of multicloud, but the reality is the market's going to take them there. So in other words, if enough of their customers are asking for this and asking that they take the lead in building these cross-cloud technologies, even if they're participating in the stack and not being the stack, it's too compelling of a market that it's not going to drag a lot of the existing public cloud providers there. >> Well, it's going to be interesting to see how that plays out, David, because I never say never when it comes to a company like AWS, and we've seen how fast they move. And at the same time, they don't want to be commoditized. There's the layer underneath all this infrastructure, and they got this ecosystem that's adding all this tremendous value. But I want to ask you, what are the essential elements of supercloud, coming back to the definition, if you will, and what's different about metacloud, as you call it, from plain old SaaS or PaaS? What are the key elements there? >> Well, the key elements would be holistic management of all of the IT infrastructure. So even though it's sitting above a multicloud, I view metacloud, supercloud as the ability to also manage your existing legacy systems, your existing security stack, your existing network operations, basically everything that exists under the purview of IT. If you think about it, we're moving our infrastructure into the clouds, and we're probably going to hit a saturation point of about 70%. And really, if the supercloud, metacloud, which is going to be expensive to build for most of the enterprises, it needs to support these things holistically. So it needs to have all the services, that is going to be shareable across the different providers, and also existing legacy systems, and also edge computing, and IoT, and all these very diverse systems that we're building there right now. So if complexity is a core challenge to operate these things at scale and the ability to secure these things at scale, we have to have commonality in terms of security architecture and technology, commonality in terms of our directory services, commonality in terms of network operations, commonality in term of cloud operations, commonality in terms of FinOps. All these things should exist in some holistic cross-cloud layer that sits above all this complexity. And you pointed out something very profound. In other words, that is going to mean that we're hiding a lot of the existing cloud providers in terms of their interfaces and dashboards and things like that that we're dealing with today, their APIs. But the reality is that if we're able to manage these things at scale, the public cloud providers are going to benefit greatly from that. They're going to sell more services because people are going to find they're able to leverage them easier. And so in other words, if we're removing the complexity wall, which many in the industry are calling it right now, then suddenly we're moving from, say, the 25 to 30% migrated in the cloud, which most enterprises are today, to 50, 60, 70%. And we're able to do this at scale, and we're doing it at scale because we're providing some architectural optimization through the supercloud, metacloud layer. >> Okay, thanks for that. David, I just want to tap your CTO brain for a minute. At "Supercloud22," we came up with these three deployment models. Kit Colbert put forth the idea that one model would be your control planes running in one cloud, let's say AWS, but it interacts with and can manage and deploy on other clouds, the Kubernetes Cluster Management System. The second one, Mohit Aron from Cohesity laid out, where you instantiate the stack on different clouds and different cloud regions, and then you create a layer, a common interface across those. And then Snowflake was the third deployment model where it's a single global instance, it's one instantiation, and basically building out their own cloud across these regions. Help us parse through that. Do those seem like reasonable deployment models to you? Do you have any thoughts on that? >> Yeah, I mean, that's a distributed computing trick we've been doing, which is, in essence, an agent of the supercloud that's carrying out some of the cloud native functions on that particular cloud, but is, in essence, a slave to the metacloud, or the supercloud, whatever, that's able to run across the various cloud providers. In other words, when it wants to access a service, it may not go directly to that service. It goes directly to the control plane, and that control plane is responsible... Very much like Kubernetes and Docker works, that control plane is responsible for reaching out and leveraging those native services. I think that that's thinking that's a step in the right direction. I think these things unto themselves, at least initially, are going to be a very complex array of technology. Even though we're trying to remove complexity, the supercloud unto itself, in terms of the ability to build this thing that's able to operate at scale across-cloud, is going to be a collection of many different technologies that are interfacing with the public cloud providers in different ways. And so we can start putting these meta architectures together, and I certainly have written and spoke about this for years, but initially, this is going to be something that may escape the detail or the holistic nature of these meta architectures that people are floating around right now. >> Yeah, so I want to stay on this, because anytime I get a CTO brain, I like to... I'm not an engineer, but I've been around a long time, so I know a lot of buzzwords and have absorbed a lot over the years, but so you take those, the second two models, the Mohit instantiate on each cloud and each cloud region versus the Snowflake approach. I asked Benoit Dageville, "Does that mean if I'm in "an AWS east region and I want to do a query on Azure West, "I can do that without moving data?" And he said, "Yes and no." And the answer was really, "No, we actually take a subset of that data," so there's the latency problem. From those deployment model standpoints, what are the trade-offs that you see in terms of instantiating the stack on each individual cloud versus that single instance? Is there a benefit of the single instance for governance and security and simplicity, but a trade-off on latency, or am I overthinking this? >> Yeah, you hit it on the nose. The reality is that the trade-off is going to be latency and performance. If we get wiggy with the distributed nature, like the distributed data example you just provided, we have to basically separate the queries and communicate with the databases on each instance, and then reassemble the result set that goes back to the people who are recording it. And so we can do caching systems and things like that. But the reality is, if it's distributed system, we're going to have latency and bandwidth issues that are going to be limiting us. And also security issues, because if we're removing lots of information over the open internet, or even private circuits, that those are going to be attack vectors that hackers can leverage. You have to keep that in mind. We're trying to reduce those attack vectors. So it would be, in many instances, and I think we have to think about this, that we're going to keep the data in the same physical region for just that. So in other words, it's going to provide the best performance and also the most simplistic access to dealing with security. And so we're not, in essence, thinking about where the data's going, how it's moving across things, things like that. So the challenge is going to be is when you're dealing with a supercloud or metacloud is, when do you make those decisions? And I think, in many instances, even though we're leveraging multiple databases across multiple regions and multiple public cloud providers, and that's the idea of it, we're still going to localize the data for performance reasons. I mean, I just wrote a blog in "InfoWorld" a couple of months ago and talked about, people who are trying to distribute data across different public cloud providers for different reasons, distribute an application development system, things like that, you can do it. With enough time and money, you can do anything. I think the challenge is going to be operating that thing, and also providing a viable business return based on the application. And so why it may look like a good science experiment, and it's cool unto itself as an architect, the reality is the more pragmatic approach is going to be a leavitt in a single region on a single cloud. >> Very interesting. The other reason I like to talk to companies like Deloitte and experienced people like you is 'cause I can get... You're agnostic, right? I mean, you're technology agnostic, vendor agnostic. So I want to come back with another question, which is, how do you deal with what I call the lowest common denominator problem? What I mean by that is if one cloud has, let's say, a superior service... Let's take an example of Nitro and Graviton. AWS seems to be ahead on that, but let's say some other cloud isn't quite quite there yet, and you're building a supercloud or a metacloud. How do you rationalize that? Does it have to be like a caravan in the army where you slow down so all the slowest trucks can keep up, or are the ways to adjudicate that that are advantageous to hide that deficiency? >> Yeah, and that's a great thing about leveraging a supercloud or a metacloud is we're putting that management in a single layer. So as far as a user or even a developer on those systems, they shouldn't worry about the performance that may come back, because we're dealing with the... You hit the nail on the head with that one. The slowest component is the one that dictates performance. And so we have to have some sort of a performance management layer. We're also making dynamic decisions to move data, to move processing, from one server to the other to try to minimize the amount of latency that's coming from a single component. So the great thing about that is we're putting that volatility into a single domain, and it's making architectural decisions in terms of where something will run and where it's getting its data from, things are stored, things like that, based on the performance feedback that's coming back from the various cloud services that are under management. And so if you're running across clouds, it becomes even more interesting, because ultimately, you're going to make some architectural choices on the fly in terms of where that stuff runs based on the active dynamic performance that that public cloud provider is providing. So in other words, we may find that it automatically shut down a database service, say MySQL, on one cloud instance, and moved it to a MySQL instance on another public cloud provider because there was some sort of a performance issue that it couldn't work around. And by the way, it does so dynamically. Away from you making that decision, it's making that decision on your behalf. Again, this is a matter of abstraction, removing complexity, and dealing with complexity through abstraction and automation, and this is... That would be an example of fixing something with automation, self-healing. >> When you meet with some of the public cloud providers and they talk about on-prem private cloud, the general narrative from the hyperscalers is, "Well, that's not a cloud." Should on-prem be inclusive of supercloud, metacloud? >> Absolutely, I mean, and they're selling private cloud instances with the edge cloud that they're selling. The reality is that we're going to have to keep a certain amount of our infrastructure, including private clouds, on premise. It's something that's shrinking as a market share, and it's going to be tougher and tougher to justify as the public cloud providers become better and better at what they do, but we certainly have edge clouds now, and hyperscalers have examples of that where they run a instance of their public cloud infrastructure on premise on physical hardware and software. And the reality is, too, we have data centers and we have systems that just won't go away for another 20 or 30 years. They're just too sticky. They're uneconomically viable to move into the cloud. That's the core thing. It's not that we can't do it. The fact of the matter is we shouldn't do it, because there's not going to be an economic... There's not going to be an economic incentive of making that happen. So if we're going to create this meta layer or this infrastructure which is going to run across clouds, and everybody agrees on, that's what the supercloud is, we have to include the on-premise systems, including private clouds, including legacy systems. And by the way, include the rising number of IoT systems that are out there, and edge-based systems out there. So we're managing it using the same infrastructure into cloud services. So they have metadata systems and they have specialized services, and service finance and retail and things like doing risk analytics. So it gets them further down that path, but not necessarily giving them a SaaS application where they're forced into all of the business processes. We're giving you piece parts. So we'll give you 1000 different parts that are related to the finance industry. You can assemble anything you need, but the thing is, it's not going to be like building it from scratch. We're going to give you risk analytics, we're giving you the financial analytics, all these things that you can leverage within your applications how you want to leverage them. We'll maintain them. So in other words, you don't have to maintain 'em just like a cloud service. And suddenly, we can build applications in a couple of weeks that used to take a couple of months, in some cases, a couple of years. So that seems to be a large take of it moving forward. So get it up in the supercloud. Those become just other services that are under managed... That are under management on the supercloud, the metacloud. So we're able to take those services, abstract them, assemble them, use them in different applications. And the ability to manage where those services are originated versus where they're consumed is going to be managed by the supercloud layer, which, you're dealing with the governance, the service governance, the security systems, the directory systems, identity access management, things like that. They're going to get you further along down the pike, and that comes back as real value. If I'm able to build something in two weeks that used to take me two months, and I'm able to give my creators in the organization the ability to move faster, that's a real advantage. And suddenly, we are going to be valued by our digital footprint, our ability to do things in a creative and innovative way. And so organizations are able to move that fast, leveraging cloud computing for what it should be leveraged, as a true force multiplier for the business. They're going to win the game. They're going to get the most value. They're going to be around in 20 years, the others won't. >> David Linthicum, always love talking. You have a dangerous combination of business and technology expertise. Let's tease. "VMware Explore" next week, you're giving a keynote, if they're going to be there. Which day are you? >> Tuesday. Tuesday, 11 o'clock. >> All right, that's a big day. Tuesday, 11 o'clock. And David, please do stop by "The Cube." We're in Moscone West. Love to get you on and continue this conversation. I got 100 more questions for you. Really appreciate your time. >> I always love talking to people at "The Cube." Thank you very much. >> All right, and thanks for watching our ongoing coverage of "Supercloud22" on "The Cube," your leader in enterprise tech and emerging tech coverage. (bright music)

>> Live from Seattle,Washington, it's theCUBE. Covering KubeCon andCloudNativeCon North America 2018 brought to you by Red Hat, the Cloud Native Computing Foundation, and it's ecosystem partners. >> Hey, welcome back everyone,live Cube coverage here at KubeCon, CloudNativeCon2018 in Seattle. I'm John Furrier with Stu Miniman hosting three days of coverage. Wall to wall, 8,000 people,double from last year, North America, expanding intoChina, Europe, everywhere. The CNCF is expanding, so is Kubernetes. The rise of Kubernetes has spawned the Cloud Native movement going mainstream that's ecosystem driven. We got a great guest here. Steven Bower, data andanalytics infrastructure lead at Bloomberg, featuredthem on siliconangle.com in one of our special reportsand user using Kubernetes and the variety of Cloud Native. Steven welcome to theCUBE. >> Thanks for having me. >> Thanks for coming on,award winning end user, given all the end users,everyone's kind of award winning. >> Yeah, yeah, yeah. >> Congratulations. Bloomberg's known, we've covered you guys, great development team. You guys have a lot ofengineers at Bloomberg as well as being a media company on cable, Bloomberg terminal, everything else. You've got a lot of datascience, you've got a lot of engineers, you're building stuff. What's the focus on Kubernetes? Where are you using it? How are you contributing? What's the dynamic? Why are you winning with Kubernetes? >> Sure, that's a good question. I think, well we're usingit all over the place in lots of different things. We have a huge engineeringteam that does all kinds of different things. So in the area that I manage,which is data and analytics infrastructure, we have been we basically managedatabases and search engines and all kinds of other tech like that. What we've ended uprealizing is that we built something that looks a lot like Kubernetes but doesn't work nearlyas well for all of those different systems, tomanage them at scale. You know, we're talkingthousands of instances of post cross and solar andall kinds of different things and having a singletool, or single platform which we can kind of levelup all of those things really makes a lot of sense in terms of not necessarily like cuttingcosts and things like that 'cause that's actuallynot as interesting to me as actually allowing theteams that manage those things to actually contribute to those projects, contribute to solar or postcross and stuff like that and free them from havingto spend a lot of time managing infrastructure. >> Tim Hopkins said, itwas just on theCUBE here before you came on,from Google, one of the co-leads on Kubernetesat gkegoogles@cloud. He said something interesting. I want to get your reaction to this. One of the benefits of Kubernetesis to give the confidence that deployments are going to be reliable and that confidence gets a flywheel and then people startshipping more as a matter of course of the business,not like oh my God we got to push a new code,oh my God, fingers crossed, press the button. The old model was fingers cross, go, QA, no, no, confidence, theconfidence and the iteration. Is that where you'reseeing the value, too? Does that relate to you? Does that make sense to you?Does that resonate with you? >> Yeah, it definitely does. A lot of the models thatwe're trying to move towards are really like declarative model of both how we develop software andthen how we deploy software and then how we manage it in production. Kubernetes offers that, thatecosystem across the board. That's been really, trying to think of a great way to put this. Being able to have that tooland being able to do that and the repeatability. In the world that I livein, everything we do we don't do one of it,we do, I think we run something like 2000 solar clusters. So all we're doing all daylong is just stamping out the same thing over and overagain and if I can build one system that doesthat very, really cleanly and simply and then I canuse that same system for running post tests orrunning something else that gives us the confidenceand we can test it, we can run it on our laptops. Our developers can developand do all that kind of stuff and it works the same everywherethey go and we can just rinse, lather, repeat kind of. >> So Steve, step back for a second. Your infrastructure, is thisall Bloomberg Data Center's? How does cloud fit into the discussion? >> Yeah, I mean, we dohave some infrastructure running in the cloud but primarily it's all on prem and data center. In my world it's all onmetal because we have all these data systemsthat need direct access to SSDs and MME andall this kind of stuff. >> Can you give us, withoutsharing state secrets, a little bit of the scaleof what you're doing? I love data's at the centerof what you're doing there. We can all understand howimportant data is to your business but talk aboutwhat the requirements are that why you have some special requirements that thetypical enterprise wouldn't. >> Sure, I think, youcan look at Bloomberg as a media company, wehave news, all that stuff. We obviously have the Bloomberg terminal and really what drives that terminal, it's all kinds of software but in the end it's data, right, andit's all kinds of data. What is that definition,big data and all these whatever stuff that everyonewas pitching five years ago. We have all of those problems. We have data that is movingat millions of ticks a second. We have enormous data sets. We have really complex data sets like people scanning courtfilings from tiny little courts all around thecountry and sending that data in and we have tonormalize that and put it in. So all these crazy differenttypes of information. They are both demanding interms of the complexities of parsing data and puttingthem and structuring them into those systems as wellas the scale so we have some pretty enormous andhigh performance systems that require us and kindof drive us to that need for metal and very focused on performance in all different aspects. >> Great, wonder, give us your engagement with this ecosystem here. One of the big questionscoming in is okay, Kubernetes, the thingwe here from the CNTF is well, it's getting kind of boring. I don't know that I agree with the term. I understand they'resaying it's becoming mature and therefore there's less drama around it which is good but this ecosystemis anything but boring. You ask a user like yourself, you've got complex requirements. There's more than 30different projects a year. What do you use out of here? What do you build yourself? What do you contribute to? How do you consideropen-source contributions? It's a big nut and wedon't have a ton of time but if you could scratch thesurface on some of those. >> I think the number onelesson that I've learned from this ecosystem isthat it's moving so rapidly that when we decide tobuild something on our own we have a talk tomorrow aboutour data science platform which we built about ayear-and-a-half, two-years ago. By the time we were ready to talk about it and everything like that,you have all the other different technologiesthat have moved forward. So it made us realize thatif we're going to start something internally,a new project, either A we should go look and seewhat's out there and contribute to that or we should juststart it in open source to begin with rather thanthat oh, let's build it and then we'll open source it. >> Chasing your tail kind of thing. >> Yeah, it's like we have tobecome part of the ecosystem in our entirety. >> That brings up a good question. I want to ask you this incontext of thinking about your peers that mightnot be as progressive as Bloomberg on the tech side. You guys certainly do a greatjob and it's well documented. Classic IT shop, racking andstacking servers and boxes and now we got the wholedigital transformation thing going on, same old, same old but now, 2019, real impact. The investments they'remaking on how to change their IT, their data isnow in front of them. They have to deal with them. This is right front andcenter 'cause companies are realizing they'regoing to go out of business if they don't actually make the adoption 'cause the data's super valuable. So how do you see the Kubernetesand the CNC of ecosystem changing the investment practices of a classic enterprise IT? You know, if your peerscalled you and said hey Steven, hey help me out,what's the secret playbook? Where do I go? I don't want to get, Igot to make some changes. What do they change? What's the impact of theinvestment with Kubernetes? What's the end game? What's the real impact? >> I think, it's a toughthing, right, 'cause Bloomberg is really notlike your typical IT shop. We are a software company at heart and so that makes us alittle bit different. When I talk to other people,I say that in the sense that not a lot of companiescan afford to decide to make a project open-- >> 'cause they outsource everything. >> Right, outsource it. Well, I mean-- >> They outsource everything. >> That's actually a huge change though. We're not sitting heretalking about hundreds of commercial products that are owned by a small handful of vendorsthat are multi-million dollar investments foreverything we're doing. We're talking about lotsof little tiny companies that have products thatare really, really valuable that are in the open sourceworld that we can get our hands on and startworking with before we even make a decision about talkingabout support or whatever. There's all kinds of technologies that, I walk into this room andthese are like friends all around 'cause we'veworked with all their software and we're like hey, theseguys have a company now. This was just a GitHubrepo a couple years ago and I think that that's abig change and embracing that, that's probablyreally hard for your typical kind of IT shop where theywant to have this clear line of I can call techsupport and get someone on the phone and that's like the main-- >> The classic old software model but it's changed. >> So Steve, one of thethings we're trying to get some insight on here isit's not just running Kubernetes in production,it's what am I doing with it. How does that change my business? I understand ML is a big pieceof what you're doing there. Give us some insight as to how does this transform your business? Does it transform your business? >> Specifically on the MLside and we'll talk about this actually that's kind of thefocus of our talk tomorrow so I don't want to stealtheir thunder too much but a lot of it was really about looking at okay, how did ML, deep ML people work? How did they want to work? If you ask an ML personwhat they really want they want an infinitely scalable cluster that it's just theirs and they want to an assay to manage all theinfrastructure for them and a data engineer to managecleaning up all the data and all these things and they wanted that all to themselves and not haveto share it with anyone else. So a lot of what we try tofigure out is how we can actually deliver that to themand it really has transformed. Once people realize that onour platform they had access to an enormous pool of GPUs,it went from oh, I want to work on my box and can you giveme GPUs on my one little box to wow, I can dohyper-parameter tuning across hundreds of GPUs overnight or during the day or whatever their needs are. It really unlocked people's capabilities and they're actuallylike, they went from being skeptical of a systemthat they had to share and things like that 'causeit actually just works and that's really the-- >> That's really thedopamine effect for them. They can see value withouthaving to go through the slogging of the configurationsand the normal stuff >> Yeah, exactly.>> that they had to do. >> Authentication. >> So we've been hearingthreads of the CICD pipeline is a big benefit,which you're kind of seeing as well but whatwe're also seeing people building below Kubernetes seeing storage and networking getting better. How do you see that holistically? Are you seeing is thenetwork more performant, that notion of programmabilitybecomes now part of it, automation, it's software. Everyone has to build software. In fact, I talked to theVP of Technology Innovation at Proctor and Gamble andhe's saying hey, we outsourced everything, I got to start hiring software so maybe not as big asBloomberg but the trend is let's get more software people on board but they still got networks,they still got storage, they still got the gear. What's the impact, the under-the-hood? >> Yeah, I think it'scomplex because you typically have these structures thatare built inside companies where you have a networkingteam and you have an infrastructure, ahardware team and whatever. One of the SREs on my team the other day, he was like, do you thinkwe can talk to the network team about puttingsoftware on their switches? That's a really interestingquestion to start asking and he actually had areally good use case. That makes a lot of sense, maybewe should think about that. And then dealing with, there'sobviously the technology aspect of that but there's also skillsets. Someone that's been workingwith a bunch of switches for a bunch of years isn'tnecessarily a programmer, used to a typical CICDprocess and things like that. >> On the flip side, I thinkthat's cool to recognize the networking guy butwe heard Tim Hopkins say there's a lot of policyknobs in Kubernetes that the networking guyscould potentially take advantage of so it mightwork the other way. Are the network guys looking at Kubernetes saying hey, or are theynot yet that sophisticated but they would love, they'd love policy. Network guys write policy. Wouldn't you want-- >> Yeah, yeah, oh absolutely. It's actually one of thebiggest draws of using Kubernetes in our ecosystem. We've made heavy use ofapplying network policy down to the workload level which means that from a securityperspective, if I know that I'm transmittingdata between two different places and I've only openedup assets for that one application, for thatone particular use case, rather than saying well,I know that I'm running the same workload on thesame box and I got to open it up for everyoneon that box but maybe someone might use thatthing but maybe they won't and like worrying about stuff like that, it's like no, I can runa workload and I know that these are the only two end points that it can talk to. >> Oh, that's a relief. That's like, hey, we're done. >> So for them this is their panacea. I know exactly whatworkloads are doing exactly what on the network andwhat they're capable of so that's been-- >> That's real progress. That's progress. >> Oh, it's huge progress, yeah. And we've been able todo things that we used to not be able to do for years. >> Talk about the-- >> I just had a quicklittle question there. You mentioned you've gotten SREs. When did you pick that up asa term that you called there and how do you see if you talk a little bit to the skill set and the jobs of peoplethat you have inside. >> Bloomberg's a big companyso the terminology of it and what actuallyindividual teams are doing is probably a little bitvaried across the organization. It's been something that'scome in over probably the last two to three years at Bloomberg. In my organization, it wasactually really interesting 'cause when I started off with, you know, you read the Google book and whatever. What I did is I wentto the guys on my team that were going to becomethe SREs for the organization and I had them write thismanifesto about how we should build and deploy and managesoftware and I didn't tell them necessarily up front thatthis is what was going to happen but when they finishedwriting that and agreed that this is how thingsshould work and they argued for a while, I said, okay,now go build all the tooling to make this easy forpeople to do, all right. And that's what we, and thenthey've just been building off their tooling. Turns out when you're workingwith a lot of the tools and the CNTF and then with Kubernetes, that's actually not that hard. There's lots of thingsthere that are just easy when you get to that place and so that's the kind of journey we'vebeen on to really try to build that infrastructure andthey've done a good job. The engineers downstream of them the speed that they're able to develop and the assurance that there was a CVE forKubernetes two weeks ago and we patched it theafternoon the CVE came out. Being able to do that in anysort of company of scale is I've worked a lot ofbanking and stuff like that in my past and it's unheard of to be able to deploy things in that speed. >> And that's really, Imean this is the goodness of clouds, the goodnessof having that kind of consistency operationally. It's funny you use SRE,that's a Google term. It's a great term andyou've got developers, you got operations kindof working together now. That's the magic. Well Steven, thank you so much for sharing this great insight on theCUBE. Certainly great valuefor the folks watching. Lot of traction, a lot ofpeople, end users contributing and consuming Kubernetes,building around it. Great trend, it's really fun to watch. A lot of composable servicesup and down the stack so congratulations. Steve Bower, Data andAnalytics Infrastructure Lead at Bloomberg. This is theCUBE bringingyou all the action, sharing the data here at KubeCon. This is theCUBE. We'll be right back withmore after this short break. (electronic music)