>>The cube presents, Coon and cloud native con Europe, 2022, brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Valencia Spain in Coon cloud native con Europe, 2022. I'm your host Keith Townsend. And we're continuing the conversation with community, with startups, with people building cloud native, a cube alum joint by a CTO. And not as the CTO advisor. I really appreciate talking to CTOs Capel. Th Lou don't forgive me if I murder the name, that's a tough one. I'm I'm, I'm getting warmed up to the cubey, but don't worry. When we get to the technical parts, it's gonna be fun. And then a cube alum, Umer K director of marketing Capel. You're the CTO. So we we'll start out with you. What's the problem statement? What, what, what are you guys doing? >>So, uh, we're building on top of an open source project podcast, custodian, uh, that is in CNCF. And that I built when I was at capital one and just as they were going, they're taking those first few steps. It's a large regulated enterprise into the cloud. And the challenge that I saw was, you know, how do we enable developers to pick whatever tools and technologies they want, if they wanna use Terraform or cloud formation or Ansible? I mean, the cloud gives us APIs and we wanna be able to enable people to use those APIs through innovative ways. Uh, but at the same time, we wanna make sure that the, regardless of what choices those developers make, that the organization is being is being well managed, that all those resources, all that infrastructure is complying to the organizational's policies. And what we saw at the time was that what we were getting impediments around our velocity into the cloud, because we had to cover off on all of the compliance and regulation aspects. >>And we were doing that them as one offs. And so, uh, taking a step back, I realized that what we really needed was a way to go faster on the compliance side and clock custodian was born out of that effort side of desk that we took through enterprise wide. And it was really about, um, accelerating the velocity around compliance, but doing it in the same way that we do application and infrastructure is code. So doing policy as code in a very simple readable YAML DSL, um, because, you know, PO you have, we, anytime we write code, we're gonna more people are gonna read that code than, than are going to need to be able to write it. And so being able to make it really easy to understand from both the developers that are in the environment from the compliance folks or auditors or security folks that might wanna review it, um, it was super important. And then instead of being at the time, we saw lots of very under products and they were all just big walls of red in somebody's corner office and getting that to actually back the information back in the hands of developers so that they can fix things, um, was problematic. So being able to do time remediation and real time collaboration and communication back to developers, Hey, you put a database on the internet. It's okay. We fixed it for you. And here's the corporate policy on how to do it better in the future. >>So this is a area of focus of mind that people, I think don't get right. A lot, the technology hard enough by itself. The transformation cloud is not just about adopting new technologies, but adopting new processes, the data, and information's there automatically. But when I go to an auditor or, or, uh, compliance and say, Hey, we've changed the process for how do we do change control for our software stack? I get a blank stare. It's what do you mean we've been doing it this way for the past 15, 20 years, that's resistance, it's a pain point and projects fail due to this issue. So talk to me about that initial customer engagement. What's what's that conversation like? >>So we start off by deploying our, our platform on top of buck custodian. Um, and as far as our customers, and we give them a view of all the things that are in their cloud, what is their baseline, so to speak. Um, but I think it's really important. Like I think you bring up a good point, like communication, the challenge, larger challenge for enterprises in the cloud, and especially with grocery compliance is understanding that it is not a steady state. It's always, there's always something new in the backlog. And so being able, and the, one of the challenges for larger orgs is just being able to communicate out what that is. I remember changing a tag policy and spending the next two years, explaining it to people what the actual tag policy was. Um, and so being able to actually inform them, you know, via email, via slack, via, you know, any communication mechanism, uh, as they're doing things is, is so powerful to be able to, to help the organization grow together and move and get an alignment about what, what the, what the new things are. >>And then additionally, you know, from a perspective of, uh, tooling that is built for the real world, like being able to, as those new policies come into play, being able to say, okay, we're going to segment into stopping the bleeding on the net new and being able to then take action on what's already deployed that now needs to become into compliance is, is really important. But coming back to your question on customer engagements, so we'll go in and we'll deploy, uh, a SAC platform for them. We'll basically show them all of the things that are there already and extent. Um, we provide a real time SQL interface that customers can use, um, that is an asset inventory of all their cloud assets. Uh, and then we provide, uh, policy packs that sort of cover off on compliance, security, cost, optimizations, and opportunities for them. Uh, and then we help them through, uh, get ops around those policies, help deploy remediation activities and capabilities for their environment. >>So walk me through some of the detail of, of, of the process and where the software helps and where people need to step in. I'm making I'm, I'm talking to my security auditor, and he's saying, you know what, Keith, I understand that the Aw, that the, uh, VM talking to the application, VM talking to the Oracle database, there is a firewall rule that says that that can happen. Show me that rule in cloud custodian. And you're trying to explain, well, well, there's no longer a firewall. There's a service. And the service is talking to that. And it, it is here and clouds, custodian and St is whether Stant help come to either help with the conversation, or where do I inject more of my experience and my ability to negotiate with the auditor. >>So stalet from the perspective, uh, and if we take a step back, we, we talk about governances code and, and the four pillars around compliance, security, cost, optimization operations, uh, that we help organizations do. But if we take a step back, what is cloud custodian? Cloud custodian is really a cloud orchestrator, a resource orchestrator. What <inaudible> provides on top of that is UI UX, um, policy packs at scale execution, across thousands of accounts, but in the context of an auditor, what we're really providing is here's the policy that we're enforcing. And here's the evidence, the attestation over time. And here's the resource database with history that shows how we, how we got here, where we compliant last year to this policy that we just wrote today. >>So shifting the conversation, you just mentioned operations. One of the larger conversations that I have with CIOs and CTOs is where do I put my people? Like this is a really tough challenge. When you look at moving to something like a SRE model, or, uh, let's say, even focus on the SRE, like what, where does the SRE sit in an organization? How does stack, like if at all, help me make those types of strategic decisions if I'm talking about governance overall. So, >>So I think in terms of personas, if you look at there's a cloud engineer, then SRE, I think that what at its core Stackler and cloud custodian does is a centralized engine, right? So your cost policies, your compliance policies, your security policies are not in a silo anymore. It's one tool. It's one repository that everyone can collaborate on as well. And even engineering, a lot of engineering teams run custodian and, and adopt custodian as well. So in terms of persona stack, it really helps bring it together. All teams have the same simple YAML DSL file that they can write their policies, share their policies and communicate and collaborate better as well. >>Yeah. So I mean, cloud transformation for an enterprise is a deeper topic. Like I think, you know, there's a lot of good breast practices establishing a cloud center of excellence. Um, I, I think, you know, investing in training for people, uh, getting certification so everyone can speak the same language when it comes to cloud is a key aspect. When it comes to the operations aspect, I very much believe that you should have, you know, try to devolve and get the developers writing, uh, some of the DevOps. And so having SREs around for the actual application teams is, is valuable, but you still have a core cloud infrastructure engineering group that's doing potentially any of your core networking, any of your, you know, IM authentication aspects. And so, uh, what we found is that, you know, SLA and cloud custodian get PR primarily get deployed by one of three groups. >>The, uh, you know, you've got the, the CIO buyer within that cloud infrastructure engineering team. And what we found is that group is because they're working with the application teams in a read right way. Uh, they're very much more, um, uh, used to doing and open to doing remediation in real time. Um, and so, and then we also have the CISO teams that want to get to a secure compliance state, be able to do audit and, and validate that all the environments are, um, you know, secure, frankly. And then we get to the CFO groups. Uh, and so, and this sometimes is part of the cloud center of excellence. And so it, it has to be this cross team collaboration. And they're really focused on the, that, that cost optimization, finding the over provision, underutilized things, establishing workloads for dev environments to turn them off at night. Um, and of course, respective of time zones, cause we're all global these days. Uh, and so those are sort of the three groups that we see that sort of really want to engage with us because we can provide value for them to help their accelerate their business goals. >>So that's an expansive view, cost compliance, security operations. That's a lot, I'm thinking about all the tools, all the information that feeds into that, where does cloud custodians start and stop? Like, am I putting cloud custodian agents on servers or, uh, pods, like how, how am I interacting with this? >>So the core clock suiting is just to see lot it's stateless, it's designed to be operationally simple. Um, and so you can run it in Kubernetes, in Jenkins. We've seen people use GitLab. We've seen people run just as a query interactive tool just from, um, investigations perspective on their laptop. But when you write a policy, a policy really consists of, you know, a couple of core elements. Uh, you identify a resource you want to target say an S3 bucket or, uh, a Google cloud VM. And then you say establishes that a filters. I want to look for all the C two instances that are on public subnets with an IM roll attached that has the ability to, uh, create another IM user. And so that, you know, you filter down, you ask the arbitrary questions to filter to the interesting set of things you want, and then you take a set of actions on them. >>So you might take an action, like stop an C two instance, and you might use it as an incident response. Um, you might, uh, use it for off hours in a, in that type of policy. So you get this library of filters and actions that you can combine to form, you know, millions of different types of policies. Now, we also have this notion of an execution mode. So you might say, uh, let's operate in real time. Whenever someone launches this instance, whenever there's an API call, we want to introspect what that API I call is doing and make sure that it's compliant to policy. Now, when you do that, custo will, when you, and you run it with the COI, cause you will actually provision a Lambda function and hook up the event sources to it. Uh, and sorry, Lambda really the serverless we bind into the serverless native capabilities of the underlying cloud provider. So Google cloud function, Azure serverless functions, uh, and native AWS Lambda native us. And so now that policy is effectively hermetically sealed, running, uh, in the Seus runtime of that cloud and responding to API calls in real time, all with, you know, structured outputs and logs and metrics to the native cloud provider capabilities around those. Um, and that really ensures that, uh, you know, it's effectively becomes operation free from the perspective of the user of having to maintain infrastructure >>For it. So let's talk about >>Agent agent list and API based. >>Let's talk about like the a non-developer use case specifically finance. Absolutely. We, you have to deploy the ability to deploy, uh, um, uh, SAP in a, uh, E C two instance, but it's very expensive. Do it only when you absolutely need to do it, but you have the rights to do it. And I wanna run a, uh, a check to see if anyone's doing it like this is this isn't a colder developer, what is their experience? So, >>So primarily we focus on the infrastructure. So low balancers, VMs, you know, encryption and address on discs. Um, when we get into the application workloads running on those instances, we spend, we don't spend that that's on our target focus area. Mm-hmm <affirmative>, we can do it. Uh, and it really depends on the underlying cloud provider's capabilities. So in Amazon, there's a system called systems manager and it runs, and it's basically running an agent on the box. We're not running the agent, but we can communicate with that agent. We can, I inspect the, the inventory that's running on that box. We can send commands to that box, through those serverless functions and through those policies. And so we see it commonly used for like incident response and a security perspective where you might wanna take a memory snapshot of, of, of the instance before, uh, um, yeah, putting it into a forensic cloud and adding >>To that, like these days we're seeing the emerging personas of a fops engineer or a fops director as well, because cost in cloud is totally different. So what custodian and Stackler allows to do is again, using the simple policy files. Even if they have a non-developer background, they can understand this DSL, they can create policies, they can better, uh, target developers, better get them to take actions on policy as well. If they're overspending in the cloud or underspending in the cloud, uh, especially with St. You get, they get a lot of, out of the box dashboards and policy packs too. So say they can really understand how the cost has been consumed. They can have the developers take actions because a lot of the fops finance people complain like my developers does not understand it. Right. How do we get them to take action and make sure we are not over spending? Right. So with custodian policies, they're able to send them, uh, educational messages on slack or open a J ticket and really enforce them to take action as well and start saving cost. Like >>If you, uh, if you imagine cloud custodian as, um, you know, cleaning staff for, for the, your, your cloud environment, like it, it's, uh, you know, if you go to a typical, you know, cloud account, you're gonna see chairs that are 10 feet tall sitting at the table. You're gonna, because it's been over provision and obviously, you know, one can use it. Um, you're gonna find like the trash is overflowing because no one set up a log retention policy on the log group or set up S3, uh, life cycle rules on their buckets. And so you just have this, um, sort of this, uh, this explosion of things that people now, you know, beyond application functioning, like beyond, you know, getting to, you know, high performance, Dr. Capable, uh, SLAs around your application model, you now have to worry about the life cycle of all those resources and helping people manage that life cycle and making sure that they're using the, the, just the resources and consumption that they need, because we're all utilization based, uh, in the cloud. And so getting that to be more in line with what the application actually needs is really where we can help organizations and the CFO cost context. >>So, Emil, you got 10 seconds to tell me why you brought me a comic book. >><laugh> we created this comic book, uh, to explain the concept of governance scored in a simplified fashion. I know Keith, you like comic books, I believe. Uh, so it's a simple way of describing what we do, why it's important for pH ops for SecOps teams. And it talks about custodian and St. It as well. >>Well, I'm more of an Ironman type of guy or Batman cloud governance or governance cloud native governance is a very tough problem. I can't under emphasize how many projects get stalled or fail from a perception perspective, even if you're technically delivered what you've asked to deliver. That's where a lot of these conversations are going. We're gonna talk to a bunch of startups that are solving these tough problems here from Licia Spain, I'm Keith Townsend, and you're watching the cube, the leader in high tech coverage.

>>Hi, this is Dave Volonte. We're winding down Day two of the Cubes coverage of Vim on 2022. We're here at the area in Las Vegas. Myself and Dave Nicholson had been going for two days. Everybody's excited about the VM on party tonight. It's It's always epic, and, uh, it's a great show in terms of its energy. Danny Allen is here. He's cto of in his back. He gave the keynote this morning. I say, Danny, you know, you look pretty good up there with two hours of sleep. I >>had three. >>Look, don't look that good, but your energy was very high. And I got to tell you the story you told was amazing. It was one of the best keynotes I've ever seen. Even even the technology pieces were outstanding. But you weaving in that story was incredible. I'm hoping that people will go back and and watch it. We probably don't have time to go into it, but wow. Um, can you give us the the one minute version of that >>long story? >>Sure. Yeah. I read a book back in 2013 about a ship that sank off Portsmouth, Maine, and I >>thought, I'm gonna go find that >>ship. And so it's a long, >>complicated process. Five >>years in the making. But we used data, and the data that found the ship was actually from 15 years earlier. >>And in 20 >>18, we found the bow of the ship. We found the stern of the ship, but what we were really trying to answer was torpedoed. Or did the boilers explode? Because >>the navy said the boilers exploded >>and two survivors said, No, it was torpedoed or there was a German U boat there. >>And so >>our goal was fine. The ship find the boiler. >>So in 20 >>19, Sorry, Uh, it was 2018. We found the bow and the stern. And then in 2019, we found both boilers perfectly intact. And in fact, the rear end of that torpedo wasn't much left >>of it, of course, but >>data found that wreck. And so it, um, it exonerated essentially any implication that somebody screwed >>up in >>the boiler system and the survivors or the Children of the survivors obviously appreciated >>that. I'm sure. Yes, Several >>outcomes to it. So the >>chief engineer was one >>of the 13 survivors, >>and he lived with the weight of this for 75 years. 49 sailors dead because of myself. But I had the opportunity of meeting some of the Children of the victims and also attending ceremonies. The families of those victims received purple hearts because they were killed due to enemy action. And then you actually knew how to do this. I wasn't aware you had experience finding Rex. You've >>discovered several of >>them prior to this one. But >>the interesting connection >>the reason why this keynote was so powerful as we're a >>team, it's a data conference. >>You connected that to data because you you went out and bought a How do you say this? Magnanimous magnetometer. Magnetometer, Magnetometer. I don't know what that >>is. And a side >>scan Sonar, Right? I got that right. That was >>easy. But >>then you know what this stuff is. And then you >>built the model >>tensorflow. You took all the data and you found anomalies. And then you went right to that spot. Found the >>wreck with 12 >>£1000 of dynamite, >>which made your heart >>beat. But >>then you found >>the boilers. That's incredible. And >>but the point was, >>this is data >>uh, let's see, >>a lot of years after, >>right? >>Yeah. Two sets of data were used. One was the original set of side scan sonar >>data by the historian >>who discovered there was a U boat in the area that was 15 years old. >>And then we used, of >>course, the wind and weather and wave pattern data that was 75 years old to figure out where the boiler should be because they knew that the ship had continued to float for eight minutes. And so you had to go back and determine the models of where should the boilers >>be if it exploded and the boilers >>dropped out and it floated along >>for eight minutes and then sank? Where was >>that data? >>It was was a scanned was an electronic was a paper. How did you get that data? So the original side scan sonar data was just hard >>drive >>data by the historian. >>I wish I could say he used them to >>back it up. But I don't know that I can say that. But he still had >>the data. 15 years later, the >>weather and >>wind and wave data, That was all public information, and we actually used that extensively. We find other wrecks. A lot of wrecks off Boston Sunken World War Two. So we were We were used to that model of tracking what happened. Wow. So, yes, imagine if that data weren't available >>and it >>probably shouldn't have been right by all rights. So now fast forward to 2022. We've got Let's talk about just a cloud >>data. I think you said a >>couple of 100 >>petabytes in the >>cloud 2019. 500 in, Uh, >>no. Yeah. In >>20 2200 and 42. Petabytes in 20 2500 Petabytes last year. And we've already done the same as 2020. So >>240 petabytes >>in Q one. I expect >>this year to move an exhibit of >>data into the public cloud. >>Okay, so you got all that data. Who knows what's in there, right? And if it's not protected, who's going to know in 50 60 7100 years? Right. So that was your tie in? Yes. To the to the importance of data protection, which was just really, really well done. Congratulations. Honestly, one of the best keynotes I've ever seen keynotes often really boring, But you did a great job again on two hours. Sleep. So much to unpack here. The other thing that really is. I mean, we can talk about the demos. We can talk about the announcements. Um, so? Well, yeah, Let's see. Salesforce. Uh, data protection is now public. I almost spilled the beans yesterday in the cube. Caught myself the version 12. Obviously, you guys gave a great demo showing the island >>cloud with I think it >>was just four minutes. It was super fast. Recovery in four minutes of data loss was so glad you didn't say zero minutes because that would have been a live demos which, Okay, which I appreciate and also think is crazy. So some really cool demos, Um, and some really cool features. So I have so much impact, but the the insights that you can provide through them it's VM one, uh, was actually something that I hadn't heard you talk about extensively in the past. That maybe I just missed it. But I wonder if you could talk about that layer and why it's critical differentiator for Wien. It's >>the hidden gem >>within the Wien portfolio because it knows about absolutely >>everything. >>And what determines the actions >>that we take is the >>context in which >>data is surviving. So in the context of security, which we are showing, we look for CPU utilisation, memory utilisation, data change rate. If you encrypt all of the data in a file server, it's going to blow up overnight. And so we're leveraging heuristics in their reporting. But even more than that, one of the things in Wien one people don't realise we have this concept of the intelligent diagnostics. It's machine learning, which we drive on our end and we push out as packages intervene one. There's up to 200 signatures, but it helps our customers find issues before they become issues. Okay, so I want to get into because I often time times, don't geek out with you. And don't take advantage of your your technical knowledge. And you've you've triggered a couple of things, >>especially when the >>analysts call you said it again today that >>modern >>data protection has meaning to you. We talked a little bit about this yesterday, but back in >>the days of >>virtualisation, you shunned agents >>and took a different >>approach because you were going for what was then >>modern. Then you >>went to bare metal cloud hybrid >>cloud containers. Super Cloud. Using the analyst meeting. You didn't use the table. Come on, say Super Cloud and then we'll talk about the edge. So I would like to know specifically if we can go back to Virtualised >>because I didn't know >>this exactly how you guys >>defined modern >>back then >>and then. Let's take that to modern today. >>So what do you >>do back then? And then we'll get into cloud and sure, So if you go back to and being started, everyone who's using agents, you'd instal something in the operating system. It would take 10% 15% of your CPU because it was collecting all the data and sending it outside of the machine when we went through a virtual environment. If you put an agent inside that machine, what happens is you would have 100 operating systems all on the same >>server, consuming >>resources from that hyper visor. And so he said, there's a better way of capturing the data instead of capturing the data inside the operating system. And by the way, managing thousands of agents is no fun. So What we did is we captured a snapshot of the image at the hyper visor level. And then over time, we just leverage changed block >>tracking from the hyper >>visor to determine what >>had changed. And so that was modern. Because no more >>managing agents >>there was no impact >>on the operating system, >>and it was a far more >>efficient way to store >>data. You leverage CBT through the A P. Is that correct? Yeah. We used the VCR API >>for data protection. >>Okay, so I said this to Michael earlier. Fast forward to today. Your your your data protection competitors aren't as fat, dumb and happy as they used to be, so they can do things in containers, containers. And we talked about that. So now let's talk about Cloud. What's different about cloud data protection? What defines modern data protection? And where are the innovations that you're providing? >>Let me do one step in >>between those because one of the things that happened between hypervisors and Cloud was >>offline. The capture of the data >>to the storage system because >>even better than doing it >>at the hyper visor clusters >>do it on the storage >>array because that can capture the >>data instantly. Right? So as we go to the cloud, we want to do the same thing. Except we don't have access to either the hyper visor or the storage system. But what they do provide is an API. So we can use the API to capture all of the blocks, all of the data, all of the changes on that particular operating system. Now, here's where we've kind of gone full circle on a hyper >>visor. You can use the V >>sphere agent to reach into the operating system to do >>things like application consistency. What we've done modern data protection is create specific cloud agents that say Forget >>about the block changes. Make sure that I have application consistency inside that cloud operating >>system. Even though you don't have access to the hyper visor of the storage, >>you're still getting the >>operating system consistency >>while getting the really >>fast capture of data. So that gets into you talking on stage about how synapse don't equal data protection. I think you just explained it, but explain why, but let me highlight something that VM does that is important. We manage both snapshots and back up because if you can recover from your storage array >>snapshot. That is the best >>possible thing to recover from right, But we don't. So we manage both the snapshots and we converted >>into the VM portable >>data format. And here's where the super cloud comes into play because if I can convert it into the VM portable data format, I can move >>that OS >>anywhere. I can move it from >>physical to virtual to cloud >>to another cloud back to virtual. I can put it back on physical if I want to. It actually abstracts >>the cloud >>layer. There are things >>that we do when we go >>between clouds. Some use bio, >>some use, um, fee. >>But we have the data in backup format, not snapshot format. That's theirs. But we have been in backup format that we can move >>around and abstract >>workloads across. All of the infrastructure in your >>catalogue is control >>of that. Is that Is >>that right? That is about >>that 100%. And you know what's interesting about our catalogue? Dave. The catalogue is inside the backup, and so historically, one of the problems with backup is that you had a separate catalogue and if it ever got corrupted. All of your >>data is meaningless >>because the catalogue is inside >>the backup >>for that unique VM or that unique instance, you can move it anywhere and power it on. That's why people said were >>so reliable. As long >>as you have the backup file, you can delete our >>software. You can >>still get the data back, so I love this fast paced so that >>enables >>what I call Super Cloud we now call Super Cloud >>because now >>take that to the edge. >>If I want to go to the edge, I presume you can extend that. And I also presume the containers play a role there. Yes, so here's what's interesting about the edge to things on the edge. You don't want to have any state if you can help it, >>and so >>containers help with that. You can have stateless environment, some >>persistent data storage, >>but we not only >>provide the portability >>in operating systems. We also do this for containers, >>and that's >>true if you go to the cloud and you're using SE CKs >>with relational >>database service is already >>asked for the persistent data. >>Later, we can pick that up and move it to G K E or move it to open shift >>on premises. And >>so that's why I call this the super cloud. We have all of this data. Actually, I think you termed the term super thank you for I'm looking for confirmation from a technologist that it's technically feasible. It >>is technically feasible, >>and you can do it today and that's a I think it's a winning strategy. Personally, Will there be >>such a thing as edge Native? You know, there's cloud native. Will there be edge native new architectures, new ways of doing things, new workloads use cases? We talk about hardware, new hardware, architectures, arm based stuff that are going to change everything to edge Native Yes and no. There's going to be small tweaks that make it better for the edge. You're gonna see a lot of iron at the edge, obviously for power consumption purposes, and you're also going to see different constructs for networking. We're not going to use the traditional networking, probably a lot more software to find stuff. Same thing on the storage. They're going to try and >>minimise the persistent >>storage to the smallest footprint possible. But ultimately I think we're gonna see containers >>will lead >>the edge. We're seeing this now. We have a I probably can't name them, but we have a large retail organisation that is running containers in every single store with a small, persistent footprint of the point of sale and local data, but that what >>is running the actual >>system is containers, and it's completely ephemeral. So we were >>at Red Hat, I was saying >>earlier last week, and I'd say half 40 50% of the conversation was edge open shift, obviously >>playing a big role there. I >>know doing work with Rancher and Town Zoo. And so there's a lot of options there. >>But obviously, open shift has >>strong momentum in the >>marketplace. >>I've been dominating. You want to chime in? No, I'm just No, >>I yeah, I know. Sometimes >>I'll sit here like a sponge, which isn't my job absorbing stuff. I'm just fascinated by the whole concept of of a >>of a portable format for data that encapsulates virtual machines and or instances that can live in the containerised world. And once you once you create that common denominator, that's really that's >>That's the secret sauce >>for what you're talking about is a super club and what's been fascinating to watch because I've been paying attention since the beginning. You go from simply V. M. F s and here it is. And by the way, the pitch to E. M. C. About buying VM ware. It was all about reducing servers to files that can be stored on storage arrays. All of a sudden, the light bulbs went off. We can store those things, and it just began. It became it became a marriage afterwards. But to watch that progression that you guys have gone from from that fundamental to all of the other areas where now you've created this common denominator layer has has been amazing. So my question is, What's the singer? What doesn't work? Where the holes. You don't want to look at it from a from a glass half empty perspective. What's the next opportunity? We've talked about edge, but what are the things that you need to fill in to make this truly ubiquitous? Well, there's a lot of services out there that we're not protecting. To be fair, right, we do. Microsoft 3 65. We announced sales for us, but there's a dozen other paths services that >>people are moving data >>into. And until >>we had data protection >>for the assassin path services, you know >>you have to figure out how >>to protect them. Now here's the kicker about >>those services. >>Most of them have the >>ability to dump date >>out. The trick is, do they have the A >>P? I is needed to put data >>back into it right, >>which is which is a >>gap. As an industry, we need to address this. I actually think we need a common >>framework for >>how to manage the >>export of data, but also the import of data not at a at a system level, but at an atomic level of the elements within those applications. >>So there are gaps >>there at the industry, but we'll fill them >>if you look on the >>infrastructure side. We've done a lot with containers and kubernetes. I think there's a next wave around server list. There's still servers and these micro services, but we're making things smaller and smaller and smaller, and there's going to be an essential need to protect those services as well. So modern data protection is something that's going to we're gonna need modern data protection five years from now, the modern will just be different. Do you ever see the day, Danny, where governance becomes an >>adjacency opportunity for >>you guys? It's clearly an opportunity even now if you look, we spent a lot of time talking about security and what you find is when organisations go, for example, of ransomware insurance or for compliance, they need to be able to prove that they have certifications or they have security or they have governance. We just saw transatlantic privacy >>packed only >>to be able to prove what type of data they're collecting. Where are they storing it? Where are they allowed to recovered? And yes, those are very much adjacency is for our customers. They're trying to manage that data. >>So given that I mean, >>am I correct that architecturally you are, are you location agnostic? Right. We are a location agnostic, and you can actually tag data to allowable location. So the big trend that I think is happening is going to happen in in this >>this this decade. >>I think we're >>scratching the surface. Is this idea >>that, you know, leave data where it is, >>whether it's an S three >>bucket, it could be in an Oracle >>database. It could be in a snowflake database. It can be a data lake that's, you know, data, >>bricks or whatever, >>and it stays where >>it is. And it's just a note on the on the call of the data >>mesh. Not my term. Jim >>Octagon coined that term. The >>problem with that, and it puts data in the hands of closer to the domain experts. The problem with that >>scenario >>is you need self service infrastructure, which really doesn't exist today anyway. But it's coming, and the big problem is Federated >>computational >>governance. How do I automate that governance so that the people who should have access to that it can have access to that data? That, to me, seems to be an adjacency. It doesn't exist except in >>a proprietary >>platform. Today. There needs to be a horizontal >>layer >>that is more open than anybody >>can use. And I >>would think that's a perfect opportunity for you guys. Just strategically it is. There's no question, and I would argue, Dave, that it's actually >>valuable to take snapshots and to keep the data out at the edge wherever it happens to be collected. But then Federated centrally. It's why I get so excited by an exhibit of data this year going into the cloud, because then you're centralising the aggregation, and that's where you're really going to drive the insights. You're not gonna be writing tensorflow and machine learning and things on premises unless you have a lot of money and a lot of GPS and a lot of capacity. That's the type of thing that is actually better suited for the cloud. And, I would argue, better suited for not your organisation. You're gonna want to delegate that to a third party who has expertise in privacy, data analysis or security forensics or whatever it is that you're trying to do with the data. But you're gonna today when you think about AI. We talked about A. I haven't had a tonne of talk about AI some >>appropriate >>amount. Most of the >>AI today correct me if you think >>this is not true is modelling that's done in the cloud. It's dominant. >>Don't >>you think that's gonna flip when edge >>really starts to take >>off where it's it's more real time >>influencing >>at the edge in new use cases at the edge now how much of that data >>is going to be >>persisted is a >>point of discussion. But what >>are your thoughts on that? I completely agree. So my expectation of the way >>that this will work is that >>the true machine learning will happen in the centralised location, and what it will do is similar to someone will push out to the edge the signatures that drive the inferences. So my example of this is always the Tesla driving down the road. >>There's no way that that >>car should be figuring it sending up to the cloud. Is that a stop sign? Is it not? It can't. It has to be able to figure out what the stop sign is before it gets to it, so we'll do the influencing at the edge. But when it doesn't know what to do with the data, then it should send it to the court to determine, to learn about it and send signatures back out, not just to that edge location, but all the edge locations within the within the ecosystem. So I get what you're saying. They might >>send data back >>when there's an anomaly, >>or I always use the example of a deer running in front of the car. David Floyd gave me that one. That's when I want to. I do want to send the data back to the cloud because Tesla doesn't persist. A tonne of data, I presume, right, right less than 5% of it. You know, I want to. Usually I'm here to dive into the weeds. I want kind of uplevel this >>to sort of the >>larger picture. From an I T perspective. >>There's been a lot of consolidation going on if you divide the >>world into vendors >>and customers. On the customer side, there are only if there's a finite number of seats at the table for truly strategic partners. Those get gobbled up often by hyper >>scale cloud >>providers. The challenge there, and I'm part of a CEO accreditation programme. So this >>is aimed at my students who >>are CEOs and CIOs. The challenge is that a lot of CEOs and CIOs on the customer side don't exhaustively drag out of their vendor partners like a theme everything that Saveem >>can do for >>them. Maybe they're leveraging a point >>solution, >>but I guarantee you they don't all know that you've got cast in in the portfolio. Not every one of them does yet, let alone this idea of a super >>cloud and and and >>how much of a strategic role you can play. So I don't know if it's a blanket admonition to folks out there, but you have got to leverage the people who are building the solutions that are going to help you solve problems in the business. And I guess, as in the form of >>a question, >>uh, do you Do you see that as a challenge? Now those the limited number of seats at >>the Table for >>Strategic Partners >>Challenge and >>Opportunity. If you look at the types of partners that we've partnered with storage partners because they own the storage of the data, at the end of the day, we actually just manage it. We don't actually store it the cloud partners. So I see that as the opportunity and my belief is I thought that the storage doesn't matter, >>but I think the >>organisation that can centralise and manage that data is the one that can rule the world, and so >>clearly I'm a team. I think we can do amazing things, but we do have key >>strategic partners hp >>E Amazon. You heard >>them on stage yesterday. >>18 different >>integrations with AWS. So we have very strategic partners. Azure. I go out there all the time. >>So there >>you don't need to be >>in the room at the table because your partners are >>and they have a relationship with the customer as well. Fair enough. But the key to this it's not just technology. It is these relationships and what is possible between our organisations. So I'm sorry to be >>so dense on this, but when you talk about >>centralising that data you're talking about physically centralising it or can actually live across clouds, >>for instance. But you've got >>visibility and your catalogues >>have visibility on >>all that. Is that what you mean by centralised obliterated? We have understanding of all the places that lives, and we can do things with >>it. We can move it from one >>cloud to another. We can take, you know, everyone talks about data warehouses. >>They're actually pretty expensive. >>You got to take data and stream it into this thing, and there's a massive computing power. On the other hand, we're >>not like that. You've storage on there. We can ephemeral e. Spin up a database when you need it for five minutes and then destroy it. We can spin up an image when you need it and then destroy it. And so on your perspective of locations. So irrespective of >>location, it doesn't >>have to be in a central place, and that's been a challenge. You extract, >>transform and load, >>and moving the data to the central >>location has been a problem. We >>have awareness of >>all the data everywhere, >>and then we can make >>decisions as to what you >>do based >>on where it is and >>what it is. And that's a metadata >>innovation. I guess that >>comes back to the catalogue, >>right? Is that correct? >>You have data >>about the data that informs you as to where it is and how to get to it. And yes, so metadata within the data that allows you to recover it and then data across the federation of all that to determine where it is. And machine intelligence plays a role in all that, not yet not yet in that space. Now. I do think there's opportunity in the future to be able to distribute storage across many different locations and that's a whole conversation in itself. But but our machine learning is more just on helping our customers address the problems in their infrastructures rather than determining right now where that data should be. >>These guys they want me to break, But I'm >>refusing. So your >>Hadoop back >>in their rooms via, um that's >>well, >>that scale. A lot of customers. I talked to Renee Dupuis. Hey, we we got there >>was heavy lift. You >>know, we're looking at new >>ways. New >>approaches, uh, going. And of course, it's all in the cloud >>anyway. But what's >>that look like? That future look like we haven't reached bottle and X ray yet on our on our Hadoop clusters, and we do continuously examine >>them for anomalies that might happen. >>Not saying we won't run into a >>bottle like we always do at some >>point, But we haven't yet >>awesome. We've covered a lot of We've certainly covered extensively the research that you did on cyber >>security and ransomware. Um, you're kind of your vision for modern >>data protection. I think we hit on that pretty well casting, you know, we talked to Michael about that, and then, you know, the future product releases the Salesforce data protection. You guys, I think you're the first there. I think you were threatened at first from Microsoft. 3 65. No, there are other vendors in the in the salesforce space. But what I tell people we weren't the first to do data capture at the hyper >>visor level. There's two other >>vendors I won't tell you they were No one remembers them. Microsoft 3 65. We weren't the first one to for that, but we're now >>the largest. So >>there are other vendors in the salesforce space. But we're looking at We're going to be aggressive. Danielle, Thanks >>so much for coming to Cuba and letting us pick your brain like that Really great job today. And congratulations on >>being back >>in semi normal. Thank you for having me. I love being on all right. And thank you for watching. Keep it right there. More coverage. Day volonte for Dave >>Nicholson, By >>the way, check out silicon angle dot com for all the written coverage. All the news >>The cube dot >>net is where all these videos We'll we'll live. Check out wiki bond dot com I published every week. I think I'm gonna dig into the cybersecurity >>research that you guys did this week. If I can >>get a hands my hands on those charts which Dave Russell promised >>me, we'll be right back >>right after this short break. Mm.

>>Welcome to this exclusive discussion. IBM, the next three years of life sciences, innovation, precision medicine, advanced clinical data management and beyond. My name is Dave Volante from the Cuban today, we're going to take a deep dive into some of the most important trends impacting the life sciences industry in the next 60 minutes. Yeah, of course. We're going to hear how IBM is utilizing Watson and some really important in life impacting ways, but we'll also bring in real world perspectives from industry and the independent analyst view to better understand how technology and data are changing the nature of precision medicine. Now, the pandemic has created a new reality for everyone, but especially for life sciences companies, one where digital transformation is no longer an option, but a necessity. Now the upside is the events of the past 22 months have presented an accelerated opportunity for innovation technology and real world data are coming together and being applied to support life science, industry trends and improve drug discovery, clinical development, and treatment commercialization throughout the product life cycle cycle. Now I'd like to introduce our esteemed panel. Let me first introduce Lorraine Marshawn, who is general manager of life sciences at IBM Watson health. Lorraine leads the organization dedicated to improving clinical development research, showing greater treatment value in getting treatments to patients faster with differentiated solutions. Welcome Lorraine. Great to see you. >>Dr. Namita LeMay is the research vice-president of IDC, where she leads the life sciences R and D strategy and technology program, which provides research based advisory and consulting services as well as market analysis. The loan to meta thanks for joining us today. And our third panelist is Greg Cunningham. Who's the director of the RWE center of excellence at Eli Lilly and company. Welcome, Greg, you guys are doing some great work. Thanks for being here. Thanks >>Dave. >>Now today's panelists are very passionate about their work. If you'd like to ask them a question, please add it to the chat box located near the bottom of your screen, and we'll do our best to answer them all at the end of the panel. Let's get started. Okay, Greg, and then Lorraine and meta feel free to chime in after one of the game-changers that you're seeing, which are advancing precision medicine. And how do you see this evolving in 2022 and into the next decade? >>I'll give my answer from a life science research perspective. The game changer I see in advancing precision medicine is moving from doing research using kind of a single gene mutation or kind of a single to look at to doing this research using combinations of genes and the potential that this brings is to bring better drug targets forward, but also get the best product to a patient faster. Um, I can give, uh, an example how I see it playing out in the last decade. Non-oncology real-world evidence. We've seen an evolution in precision medicine as we've built out the patient record. Um, as we've done that, uh, the marketplace has evolved rapidly, uh, with, particularly for electronic medical record data and genomic data. And we were pretty happy to get our hands on electronic medical record data in the early days. And then later the genetic test results were combined with this data and we could do research looking at a single mutation leading to better patient outcomes. But I think where we're going to evolve in 2022 and beyond is with genetic testing, growing and oncology, providing us more data about that patient. More genes to look at, uh, researchers can look at groups of genes to analyze, to look at that complex combination of gene mutations. And I think it'll open the door for things like using artificial intelligence to help researchers plow through the complex number of permutations. When you think about all those genes you can look at in combination, right? Lorraine yes. Data and machine intelligence coming together, anything you would add. >>Yeah. Thank you very much. Well, I think that Greg's response really sets us up nicely, particularly when we think about the ability to utilize real-world data in the farm industry across a number of use cases from discovery to development to commercial, and, you know, in particular, I think with real world data and the comments that Greg just made about clinical EMR data linked with genetic or genomic data, a real area of interest in one that, uh, Watson health in particular is focused on the idea of being able to create a data exchange so that we can bring together claims clinical EMR data, genomics data, increasingly wearables and data directly from patients in order to create a digital health record that we like to call an intelligent patient health record that basically gives us the digital equivalent of a real life patient. And these can be used in use cases in randomized controlled clinical trials for synthetic control arms or natural history. They can be used in order to track patients' response to drugs and look at outcomes after they've been on various therapies as, as Greg is speaking to. And so I think that, you know, the promise of data and technology, the AI that we can apply on that is really helping us advance, getting therapies to market faster, with better information, lower sample sizes, and just a much more efficient way to do drug development and to track and monitor outcomes in patients. >>Great. Thank you for that now to meta, when I joined IDC many, many years ago, I really didn't know much about the industry that I was covering, but it's great to see you as a former practitioner now bringing in your views. What do you see as the big game-changers? >>So, um, I would, I would agree with what both Lorraine and Greg said. Um, but one thing that I'd just like to call out is that, you know, everyone's talking about big data, the volume of data is growing. It's growing exponentially actually about, I think 30% of data that exists today is healthcare data. And it's growing at a rate of 36%. That's huge, but then it's not just about the big, it's also about the broad, I think, um, you know, I think great points that, uh, Lorraine and Greg brought out that it's, it's not just specifically genomic data, it's multi omic data. And it's also about things like medical history, social determinants of health, behavioral data. Um, and why, because when you're talking about precision medicine and we know that we moved away from the, the terminology of personalized to position, because you want to talk about disease stratification and you can, it's really about convergence. >>Um, if you look at a recent JAMA paper in 2021, only 1% of EHS actually included genomic data. So you really need to have that ability to look at data holistically and IDC prediction is seeing that investments in AI to fuel in silico, silicone drug discovery will double by 20, 24, but how are you actually going to integrate all the different types of data? Just look at, for example, diabetes, you're on type two diabetes, 40 to 70% of it is genetically inherited and you have over 500 different, uh, genetic low side, which could be involved in playing into causing diabetes. So the earlier strategy, when you are looking at, you know, genetic risk scoring was really single trait. Now it's transitioning to multi rate. And when you say multi trade, you really need to get that integrated view that converging for you to, to be able to drive a precision medicine strategy. So to me, it's a very interesting contrast on one side, you're really trying to make it specific and focused towards an individual. And on the other side, you really have to go wider and bigger as well. >>Uh, great. I mean, the technology is enabling that convergence and the conditions are almost mandating it. Let's talk about some more about data that the data exchange and building an intelligent health record, as it relates to precision medicine, how will the interoperability of real-world data, you know, create that more cohesive picture for the, for the patient maybe Greg, you want to start, or anybody else wants to chime in? >>I think, um, the, the exciting thing from, from my perspective is the potential to gain access to data. You may be weren't aware of an exchange in implies that, uh, some kind of cataloging, so I can see, uh, maybe things that might, I just had no idea and, uh, bringing my own data and maybe linking data. These are concepts that I think are starting to take off in our field, but it, it really opens up those avenues to when you, you were talking about data, the robustness and richness volume isn't, uh, the only thing is Namita said, I think really getting to a rich high-quality data and, and an exchange offers a far bigger, uh, range for all of us to, to use, to get our work done. >>Yeah. And I think, um, just to chime, chime into that, uh, response from Greg, you know, what we hear increasingly, and it's pretty pervasive across the industry right now, because this ability to create an exchange or the intelligent, uh, patient health record, these are new ideas, you know, they're still rather nascent and it always is the operating model. Uh, that, that is the, uh, the difficult challenge here. And certainly that is the case. So we do have data in various silos. Uh, they're in patient claims, they're in electronic medical records, they might be in labs, images, genetic files on your smartphone. And so one of the challenges with this interoperability is being able to tap into these various sources of data, trying to identify quality data, as Greg has said, and the meta is underscoring as well. Uh, we've gotta be able to get to the depth of data that's really meaningful to us, but then we have to have technology that allows us to pull this data together. >>First of all, it has to be de-identified because of security and patient related needs. And then we've gotta be able to link it so that you can create that likeness in terms of the record, it has to be what we call cleaned or curated so that you get the noise and all the missing this out of it, that's a big step. And then it needs to be enriched, which means that the various components that are going to be meaningful, you know, again, are brought together so that you can create that cohort of patients, that individual patient record that now is useful in so many instances across farm, again, from development, all the way through commercial. So the idea of this exchange is to enable that exact process that I just described to have a, a place, a platform where various entities can bring their data in order to have it linked and integrated and cleaned and enriched so that they get something that is a package like a data package that they can actually use. >>And it's easy to plug into their, into their studies or into their use cases. And I think a really important component of this is that it's gotta be a place where various third parties can feel comfortable bringing their data together in order to match it with other third parties. That is a, a real value, uh, that the industry is increasingly saying would be important to them is, is the ability to bring in those third-party data sets and be able to link them and create these, these various data products. So that's really the idea of the data exchange is that you can benefit from accessing data, as Greg mentioned in catalogs that maybe are across these various silos so that you can do the kind of work that you need. And that we take a lot of the hard work out of it. I like to give an example. >>We spoke with one of our clients at one of the large pharma companies. And, uh, I think he expressed it very well. He said, what I'd like to do is have like a complete dataset of lupus. Lupus is an autoimmune condition. And I've just like to have like the quintessential lupus dataset that I can use to run any number of use cases across it. You know, whether it's looking at my phase one trial, whether it's selecting patients and enriching for later stage trials, whether it's understanding patient responses to different therapies as I designed my studies. And so, you know, this idea of adding in therapeutic area indication, specific data sets and being able to create that for the industry in the meta mentioned, being able to do that, for example, in diabetes, that's how pharma clients need to have their needs met is through taking the hard workout, bringing the data together, having it very therapeutically enriched so that they can use it very easily. >>Thank you for that detail and the meta. I mean, you can't do this with humans at scale in technology of all the things that Lorraine was talking about, the enrichment, the provenance, the quality, and of course, it's got to be governed. You've got to protect the privacy privacy humans just can't do all that at massive scale. Can it really tech that's where technology comes in? Doesn't it and automation. >>Absolutely. >>I, couldn't more, I think the biggest, you know, whether you talk about precision medicine or you talk about decentralized trials, I think there's been a lot of hype around these terms, but what is really important to remember is technology is the game changer and bringing all that data together is really going to be the key enabler. So multimodal data integration, looking at things like security or federated learning, or also when you're talking about leveraging AI, you're not talking about things like bias or other aspects around that are, are critical components that need to be addressed. I think the industry is, uh, it's partly, still trying to figure out the right use cases. So it's one part is getting together the data, but also getting together the right data. Um, I think data interoperability is going to be the absolute game changer for enabling this. Uh, but yes, um, absolutely. I can, I can really couldn't agree more with what Lorraine just said, that it's bringing all those different aspects of data together to really drive that precision medicine strategy. >>Excellent. Hey Greg, let's talk about protocols decentralized clinical trials. You know, they're not new to life silences, but, but the adoption of DCTs is of course sped up due to the pandemic we've had to make trade-offs obviously, and the risk is clearly worth it, but you're going to continue to be a primary approach as we enter 2022. What are the opportunities that you see to improve? How DCTs are designed and executed? >>I see a couple opportunities to improve in this area. The first is, uh, back to technology. The infrastructure around clinical trials has, has evolved over the years. Uh, but now you're talking about moving away from kind of site focus to the patient focus. Uh, so with that, you have to build out a new set of tools that would help. So for example, one would be novel trial, recruitment, and screening, you know, how do you, how do you find patients and how do you screen them to see if are they, are they really a fit for, for this protocol? Another example, uh, very important documents that we have to get is, uh, you know, the e-consent that someone's says, yes, I'm, well, I understand this study and I'm willing to do it, have to do that in a more remote way than, than we've done in the past. >>Um, the exciting area, I think, is the use of, uh, eco, uh, E-Pro where we capture data from the patient using apps, devices, sensors. And I think all of these capabilities will bring a new way of, of getting data faster, uh, in, in this kind of model. But the exciting thing from, uh, our perspective at Lily is it's going to bring more data about the patient from the patient, not just from the healthcare provider side, it's going to bring real data from these apps, devices and sensors. The second thing I think is using real-world data to identify patients, to also improve protocols. We run scenarios today, looking at what's the impact. If you change a cut point on a, a lab or a biomarker to see how that would affect, uh, potential enrollment of patients. So it, it definitely the real-world data can be used to, to make decisions, you know, how you improve these protocols. >>But the thing that we've been at the challenge we've been after that this probably offers the biggest is using real-world data to identify patients as we move away from large academic centers that we've used for years as our sites. Um, you can maybe get more patients who are from the rural areas of our countries or not near these large, uh, uh, academic centers. And we think it'll bring a little more diversity to the population, uh, who who's, uh, eligible, but also we have their data, so we can see if they really fit the criteria and the probability they are a fit for the trial is much higher than >>Right. Lorraine. I mean, your clients must be really pushing you to help them improve DCTs what are you seeing in the field? >>Yes, in fact, we just attended the inaugural meeting of the de-central trials research Alliance in, uh, in Boston about two weeks ago where, uh, all of the industry came together, pharma companies, uh, consulting vendors, just everyone who's been in this industry working to help define de-central trials and, um, think through what its potential is. Think through various models in order to enable it, because again, a nascent concept that I think COVID has spurred into action. Um, but it is important to take a look at the definition of DCT. I think there are those entities that describe it as accessing data directly from the patient. I think that is a component of it, but I think it's much broader than that. To me, it's about really looking at workflows and processes of bringing data in from various remote locations and enabling the whole ecosystem to work much more effectively along the data continuum. >>So a DCT is all around being able to make a site more effective, whether it's being able to administer a tele visit or the way that they're getting data into the electronic data captures. So I think we have to take a look at the, the workflows and the operating models for enabling de-central trials and a lot of what we're doing with our own technology. Greg mentioned the idea of electronic consent of being able to do electronic patient reported outcomes, other collection of data directly from the patient wearables tele-health. So these are all data acquisition, methodologies, and technologies that, that we are enabling in order to get the best of the data into the electronic data capture system. So edit can be put together and processed and submitted to the FDA for regulatory use for clinical trial type submission. So we're working on that. I think the other thing that's happening is the ability to be much more flexible and be able to have more cloud-based storage allows you to be much more inter-operable to allow API APIs in order to bring in the various types of data. >>So we're really looking at technology that can make us much more fluid and flexible and accommodating to all the ways that people live and work and manage their health, because we have to reflect that in the way we collect those data types. So that's a lot of what we're, what we're focused on. And in talking with our clients, we spend also a lot of time trying to understand along the, let's say de-central clinical trials continuum, you know, w where are they? And I know Namita is going to talk a little bit about research that they've done in terms of that adoption curve, but because COVID sort of forced us into being able to collect data in more remote fashion in order to allow some of these clinical trials to continue during COVID when a lot of them had to stop. What we want to make sure is that we understand and can codify some of those best practices and that we can help our clients enable that because the worst thing that would happen would be to have made some of that progress in that direction. >>But then when COVID is over to go back to the old ways of doing things and not bring some of those best practices forward, and we actually hear from some of our clients in the pharma industry, that they worry about that as well, because we don't yet have a system for operationalizing a de-central trial. And so we really have to think about the protocol it's designed, the indication, the types of patients, what makes sense to decentralize, what makes sense to still continue to collect data in a more traditional fashion. So we're spending a lot of time advising and consulting with our patients, as well as, I mean, with our clients, as well as CRS, um, on what the best model is in terms of their, their portfolio of studies. And I think that's a really important aspect of trying to accelerate the adoption is making sure that what we're doing is fit for purpose, just because you can use technology doesn't mean you should, it really still does require human beings to think about the problem and solve them in a very practical way. >>Great, thank you for that. Lorraine. I want to pick up on some things that Lorraine was just saying. And then back to what Greg was saying about, uh, uh, DCTs becoming more patient centric, you had a prediction or IDC, did I presume your fingerprints were on it? Uh, that by 20 25, 70 5% of trials will be patient-centric decentralized clinical trials, 90% will be hybrid. So maybe you could help us understand that relationship and what types of innovations are going to be needed to support that evolution of DCT. >>Thanks, Dave. Yeah. Um, you know, sorry, I, I certainly believe that, uh, you know, uh, Lorraine was pointing out of bringing up a very important point. It's about being able to continue what you have learned in over the past two years, I feel this, you know, it was not really a digital revolution. It was an attitude. The revolution that this industry underwent, um, technology existed just as clinical trials exist as drugs exist, but there was a proof of concept that technology works that this model is working. So I think that what, for example, telehealth, um, did for, for healthcare, you know, transition from, from care, anywhere care, anytime, anywhere, and even becoming predictive. That's what the decentralized clinical trials model is doing for clinical trials today. Great points again, that you have to really look at where it's being applied. You just can't randomly apply it across clinical trials. >>And this is where the industry is maturing the complexity. Um, you know, some people think decentralized trials are very simple. You just go and implement these centralized clinical trials, but it's not that simple as it it's being able to define, which are the right technologies for that specific, um, therapeutic area for that specific phase of the study. It's being also a very important point is bringing in the patient's voice into the process. Hey, I had my first telehealth visit sometime last year and I was absolutely thrilled about it. I said, no time wasted. I mean, everything's done in half an hour, but not all patients want that. Some want to consider going back and you, again, need to customize your de-centralized trials model to, to the, to the type of patient population, the demographics that you're dealing with. So there are multiple factors. Um, also stepping back, you know, Lorraine mentioned they're consulting with, uh, with their clients, advising them. >>And I think a lot of, um, a lot of companies are still evolving in their maturity in DCTs though. There's a lot of boys about it. Not everyone is very mature in it. So it's, I think it, one thing everyone's kind of agreeing with is yes, we want to do it, but it's really about how do we go about it? How do we make this a flexible and scalable modern model? How do we integrate the patient's voice into the process? What are the KPIs that we define the key performance indicators that we define? Do we have a playbook to implement this model to make it a scalable model? And, you know, finally, I think what organizations really need to look at is kind of developing a de-centralized mature maturity scoring model, so that I assess where I am today and use that playbook to define, how am I going to move down the line to me reach the next level of maturity. Those were some of my thoughts. Right? >>Excellent. And now remember you, if you have any questions, use the chat box below to submit those questions. We have some questions coming in from the audience. >>At one point to that, I think one common thread between the earlier discussion around precision medicine and around decentralized trials really is data interoperability. It is going to be a big game changer to, to enable both of these pieces. Sorry. Thanks, Dave. >>Yeah. Thank you. Yeah. So again, put your questions in the chat box. I'm actually going to go to one of the questions from the audience. I get some other questions as well, but when you think about all the new data types that are coming in from social media, omics wearables. So the question is with greater access to these new types of data, what trends are you seeing from pharma device as far as developing capabilities to effectively manage and analyze these novel data types? Is there anything that you guys are seeing, um, that you can share in terms of best practice or advice >>I'll offer up? One thing, I think the interoperability isn't quite there today. So, so what's that mean you can take some of those data sources. You mentioned, uh, some Omix data with, uh, some health claims data and it's the, we spend too much time and in our space putting data to gather the behind the scenes, I think the stat is 80% of the time is assembling the data 20% analyzing. And we've had conversations here at Lilly about how do we get to 80% of the time is doing analysis. And it really requires us to think, take a step back and think about when you create a, uh, a health record, you really have to be, have the same plugins so that, you know, data can be put together very easily, like Lorraine mentioned earlier. And that comes back to investing in as an industry and standards so that, you know, you have some of data standard, we all can agree upon. And then those plugs get a lot easier and we can spend our time figuring out how to make, uh, people's lives better with healthcare analysis versus putting data together, which is not a lot of fun behind the scenes. >>Other thoughts on, um, on, on how to take advantage of sort of novel data coming from things like devices in the nose that you guys are seeing. >>I could jump in there on your end. Did you want to go ahead? Okay. So, uh, I mean, I think there's huge value that's being seen, uh, in leveraging those multiple data types. I think one area you're seeing is the growth of prescription digital therapeutics and, um, using those to support, uh, you know, things like behavioral health issues and a lot of other critical conditions it's really taking you again, it is interlinking real-world data cause it's really taking you to the patient's home. Um, and it's, it's, there's a lot of patients in the city out here cause you can really monitor the patient real-time um, without the patient having coming, you know, coming and doing a site visit once in say four weeks or six weeks. So, um, I, and, uh, for example, uh, suicidal behavior and just to take an example, if you can predict well in advance, based on those behavioral parameters, that this is likely to trigger that, uh, the value of it is enormous. Um, again, I think, uh, Greg made a valid point about the industry still trying to deal with resolving the data interoperability issue. And there are so many players that are coming in the industry right now. There are really few that have the maturity and the capability to address these challenges and provide intelligence solutions. >>Yeah. Maybe I'll just, uh, go ahead and, uh, and chime into Nikita's last comment there. I think that's what we're seeing as well. And it's very common, you know, from an innovation standpoint that you have, uh, a nascent industry or a nascent innovation sort of situation that we have right now where it's very fragmented. You have a lot of small players, you have some larger entrenched players that have the capability, um, to help to solve the interoperability challenge, the standards challenge. I mean, I think IBM Watson health is certainly one of the entities that has that ability and is taking a stand in the industry, uh, in order to, to help lead in that way. Others are too. And, uh, but with, with all of the small companies that are trying to find interesting and creative ways to gather that data, it does create a very fragmented, uh, type of environment and ecosystem that we're in. >>And I think as we mature, as we do come forward with the KPIs, the operating models, um, because you know, the devil's in the detail in terms of the operating models, it's really exciting to talk these trends and think about the future state. But as Greg pointed out, if you're spending 80% of your time just under the hood, you know, trying to get the engine, all the spark plugs to line up, um, that's, that's just hard grunt work that has to be done. So I think that's where we need to be focused. And I think bringing all the data in from these disparate tools, you know, that's fine, we need, uh, a platform or the API APIs that can enable that. But I think as we, as we progress, we'll see more consolidation, uh, more standards coming into play, solving the interoperability types of challenges. >>And, um, so I think that's where we should, we should focus on what it's going to take and in three years to really codify this and make it, so it's a, it's a well hum humming machine. And, you know, I do know having also been in pharma that, uh, there's a very pilot oriented approach to this thing, which I think is really healthy. I think large pharma companies tend to place a lot of bets with different programs on different tools and technologies, to some extent to see what's gonna stick and, you know, kind of with an innovation mindset. And I think that's good. I think that's kind of part of the process of figuring out what is going to work and, and helping us when we get to that point of consolidating our model and the technologies going forward. So I think all of the efforts today are definitely driving us to something that feels much more codified in the next three to five years. >>Excellent. We have another question from the audience it's sort of related to the theme of this discussion, given the FDA's recent guidance on using claims and electronic health records, data to support regulatory decision-making what advancements do you think we can expect with regards to regulatory use of real-world data in the coming years? It's kind of a two-parter so maybe you guys can collaborate on this one. What role that, and then what role do you think industry plays in influencing innovation within the regulatory space? >>All right. Well, it looks like you've stumped the panel there. Uh, Dave, >>It's okay to take some time to think about it, right? You want me to repeat it? You guys, >>I, you know, I I'm sure that the group is going to chime into this. I, so the FDA has issued a guidance. Um, it's just, it's, it's exactly that the FDA issues guidances and says that, you know, it's aware and supportive of the fact that we need to be using real-world data. We need to create the interoperability, the standards, the ways to make sure that we can include it in regulatory submissions and the like, um, and, and I sort of think about it akin to the critical path initiative, probably, I don't know, 10 or 12 years ago in pharma, uh, when the FDA also embrace this idea of the critical path and being able to allow more in silico modeling of clinical trial, design and development. And it really took the industry a good 10 years, um, you know, before they were able to actually adopt and apply and take that sort of guidance or openness from the FDA and actually apply it in a way that started to influence the way clinical trials were designed or the in silico modeling. >>So I think the second part of the question is really important because while I think the FDA is saying, yes, we recognize it's important. Uh, we want to be able to encourage and support it. You know, when you look for example, at synthetic control arms, right? The use of real-world data in regulatory submissions over the last five or six years, all of the use cases have been in oncology. I think there've been about maybe somewhere between eight to 10 submissions. And I think only one actually was a successful submission, uh, in all those situations, the real-world data arm of that oncology trial that synthetic control arm was actually rejected by the FDA because of lack of completeness or, you know, equalness in terms of the data. So the FDA is not going to tell us how to do this. So I think the second part of the question, which is what's the role of industry, it's absolutely on industry in order to figure out exactly what we're talking about, how do we figure out the interoperability, how do we apply the standards? >>How do we ensure good quality data? How do we enrich it and create the cohort that is going to be equivalent to the patient in the real world, uh, in the end that would otherwise be in the clinical trial and how do we create something that the FDA can agree with? And we'll certainly we'll want to work with the FDA in order to figure out this model. And I think companies are already doing that, but I think that the onus is going to be on industry in order to figure out how you actually operationalize this and make it real. >>Excellent. Thank you. Um, question on what's the most common misconception that clinical research stakeholders with sites or participants, et cetera might have about DCTs? >>Um, I could jump in there. Right. So, sure. So, um, I think in terms of misconceptions, um, I think the communist misconceptions that sites are going away forever, which I do not think is really happening today. Then the second, second part of it is that, um, I think also the perspective that patients are potentially neglected because they're moving away. So we'll pay when I, when I, what I mean by that neglected, perhaps it was not the appropriate term, but the fact that, uh, will patients will, will, will patient engagement continue, will retention be strong since the patients are not interacting in person with the investigator quite as much. Um, so site retention and patient retention or engagement from both perspectives, I think remains a concern. Um, but actually if you look at, uh, look at, uh, assessments that have been done, I think patients are more than happy. >>Majority of the patients have been really happy about, about the new model. And in fact, sites are, seem to increase, have increased investments in technology by 50% to support this kind of a model. So, and the last thing is that, you know, decentralized trials is a great model and it can be applied to every possible clinical trial. And in another couple of weeks, the whole industry will be implementing only decentralized trials. I think we are far away from that. It's just not something that you would implement across every trial. And we discussed that already. So you have to find the right use cases for that. So I think those were some of the key misconceptions I'd say in the industry right now. Yeah. >>Yeah. And I would add that the misconception I hear the most about is, uh, the, the similar to what Namita said about the sites and healthcare professionals, not being involved to the level that they are today. Uh, when I mentioned earlier in our conversation about being excited about capturing more data, uh, from the patient that was always in context of, in addition to, you know, healthcare professional opinion, because I think both of them bring that enrichment and a broader perspective of that patient experience, whatever disease they're faced with. So I, I think some people think is just an all internet trial with just someone, uh, putting out there their own perspective. And, and it's, it's a combination of both to, to deliver a robust data set. >>Yeah. Maybe I'll just comment on, it reminds me of probably 10 or 15 years ago, maybe even more when, um, really remote monitoring was enabled, right? So you didn't have to have the study coordinator traveled to the investigative site in order to check the temperature of the freezer and make sure that patient records were being completed appropriately because they could have a remote visit and they could, they could send the data in a via electronic data and do the monitoring visit, you know, in real time, just the way we're having this kind of communication here. And there was just so much fear that you were going to replace or supplant the personal relationship between the sites between the study coordinators that you were going to, you know, have to supplant the role of the monitor, which was always a very important role in clinical trials. >>And I think people that really want to do embrace the technology and the advantages that it provided quickly saw that what it allowed was the monitor to do higher value work, you know, instead of going in and checking the temperature on a freezer, when they did have their visit, they were able to sit and have a quality discussion for example, about how patient recruitment was going or what was coming up in terms of the consent. And so it created a much more high touch, high quality type of interaction between the monitor and the investigative site. And I think we should be looking for the same advantages from DCT. We shouldn't fear it. We shouldn't think that it's going to supplant the site or the investigator or the relationship. It's our job to figure out where the technology fits and clinical sciences always got to be high touch combined with high-tech, but the high touch has to lead. And so getting that balance right? And so that's going to happen here as well. We will figure out other high value work, meaningful work for the site staff to do while they let the technology take care of the lower quality work, if you will, or the lower value work, >>That's not an, or it's an, and, and you're talking about the higher value work. And it, it leads me to something that Greg said earlier about the 80, 20, 80% is assembly. 20% is actually doing the analysis and that's not unique to, to, to life sciences, but, but sort of question is it's an organizational question in terms of how we think about data and how we approach data in the future. So Bamyan historically big data in life sciences in any industry really is required highly centralized and specialized teams to do things that the rain was talking about, the enrichment, the provenance, the data quality, the governance, the PR highly hyper specialized teams to do that. And they serve different constituencies. You know, not necessarily with that, with, with context, they're just kind of data people. Um, so they have responsibility for doing all those things. Greg, for instance, within literally, are you seeing a move to, to, to democratize data access? We've talked about data interoperability, part of that state of sharing, um, that kind of breaks that centralized hold, or is that just too far in the future? It's too risky in this industry? >>Uh, it's actually happening now. Uh, it's a great point. We, we try to classify what people can do. And, uh, the example would be you give someone who's less analytically qualified, uh, give them a dashboard, let them interact with the data, let them better understand, uh, what, what we're seeing out in the real world. Uh, there's a middle user, someone who you could give them, they can do some analysis with the tool. And the nice thing with that is you have some guardrails around that and you keep them in their lane, but it allows them to do some of their work without having to go ask those centralized experts that, that you mentioned their precious resources. And that's the third group is those, uh, highly analytical folks that can, can really deliver, uh, just value beyond. But when they're doing all those other things, uh, it really hinders them from doing what we've been talking about is the high value stuff. So we've, we've kind of split into those. We look at people using data in one of those three lanes and it, and it has helped I think, uh, us better not try to make a one fit solution for, for how we deliver data and analytic tools for people. Right. >>Okay. I mean, DCT hot topic with the, the, the audience here. Another question, um, what capabilities do sponsors and CRS need to develop in-house to pivot toward DCT? >>Should I jump in here? Yeah, I mean, um, I think, you know, when, when we speak about DCTs and when I speak with, uh, folks around in the industry, I, it takes me back to the days of risk-based monitoring. When it was first being implemented, it was a huge organizational change from the conventional monitoring models to centralize monitoring and risk-based monitoring, it needs a mental reset. It needs as Lorraine had pointed out a little while ago, restructuring workflows, re redefining processes. And I think that is one big piece. That is, I think the first piece, when, you know, when you're implementing a new model, I think organizational change management is a big piece of it because you are disturbing existing structures, existing methods. So getting that buy-in across the organization towards the new model, seeing what the value add in it. And where do you personally fit into that story? >>How do your workflows change, or how was your role impacted? I think without that this industry will struggle. So I see organizations, I think, first trying to work on that piece to build that in. And then of course, I also want to step back for the second to the, uh, to the point that you brought out about data democratization. And I think Greg Greg gave an excellent point, uh, input about how it's happening in the industry. But I would also say that the data democratization really empowerment of, of, of the stakeholders also includes the sites, the investigators. So what is the level of access to data that you know, that they have now, and is it, uh, as well as patients? So see increasingly more and more companies trying to provide access to patients finally, it's their data. So why shouldn't they have some insights to it, right. So access to patients and, uh, you know, the 80, 20 part of it. Uh, yes, he's absolutely right that, uh, we want to see that flip from, uh, 20%, um, you know, focusing on, on actually integrating the data 80% of analytics, but the real future will be coming in when actually the 20 and 18 has gone. And you actually have analysts the insights out on a silver platter. That's kind of wishful thinking, some of the industries is getting there in small pieces, but yeah, then that's just why I should, why we share >>Great points. >>And I think that we're, we're there in terms that like, I really appreciate the point around democratizing the data and giving the patient access ownership and control over their own data. I mean, you know, we see the health portals that are now available for patients to view their own records, images, and labs, and claims and EMR. We have blockchain technology, which is really critical here in terms of the patient, being able to pull all of their own data together, you know, in the blockchain and immutable record that they can own and control if they want to use that to transact clinical trial types of opportunities based on their data, they can, or other real world scenarios. But if they want to just manage their own data because they're traveling and if they're in a risky health situation, they've got their own record of their health, their health history, uh, which can avoid, you know, medical errors occurring. So, you know, even going beyond life sciences, I think this idea of democratizing data is just good for health. It's just good for people. And we definitely have the technology that can make it a reality. Now >>You're here. We have just about 10 minutes left and now of course, now all the questions are rolling in like crazy from the crowd. Would it be curious to know if there would be any comments from the panel on cost comparison analysis between traditional clinical trials in DCTs and how could the outcome effect the implementation of DCTs any sort of high-level framework you can share? >>I would say these are still early days to, to drive that analysis because I think many companies are, um, are still in the early stages of implementation. They've done a couple of trials. The other part of it that's important to keep in mind is, um, is for organizations it's, they're at a stage of, uh, of being on the learning curve. So when you're, you're calculating the cost efficiencies, if ideally you should have had two stakeholders involved, you could have potentially 20 stakeholders involved because everyone's trying to learn the process and see how it's going to be implemented. So, um, I don't think, and the third part of it, I think is organizations are still defining their KPIs. How do you measure it? What do you measure? So, um, and even still plugging in the pieces of technology that they need to fit in, who are they partnering with? >>What are the pieces of technology they're implementing? So I don't think there is a clear cut as answered at this stage. I think as you scale this model, the efficiencies will be seen. It's like any new technology or any new solution that's implemented in the first stages. It's always a little more complex and in fact sometimes costs extra. But as, as you start scaling it, as you establish your workflows, as you streamline it, the cost efficiencies will start becoming evident. That's why the industry is moving there. And I think that's how it turned out on the long run. >>Yeah. Just make it maybe out a comment. If you don't mind, the clinical trials are, have traditionally been costed are budgeted is on a per patient basis. And so, you know, based on the difficulty of the therapeutic area to recruit a rare oncology or neuromuscular disease, there's an average that it costs in order to find that patient and then execute the various procedures throughout the clinical trial on that patient. And so the difficulty of reaching the patient and then the complexity of the trial has led to what we might call a per patient stipend, which is just the metric that we use to sort of figure out what the average cost of a trial will be. So I think to point, we're going to have to see where the ability to adjust workflows, get to patients faster, collect data more easily in order to make the burden on the site, less onerous. I think once we start to see that work eases up because of technology, then I think we'll start to see those cost equations change. But I think right now the system isn't designed in order to really measure the economic benefit of de-central models. And I think we're going to have to sort of figure out what that looks like as we go along and since it's patient oriented right now, we'll have to say, well, you know, how does that work, ease up? And to those costs actually come down and then >>Just scale, it's going to be more, more clear as the media was saying, next question from the audiences, it's kind of a best fit question. You all have touched on this, but let me just ask it is what examples in which, in which phases suit DCT in its current form, be it fully DCT or hybrid models, none of our horses for courses question. >>Well, I think it's kind of, uh, it's, it's it's has its efficiencies, obviously on the later phases, then the absolute early phase trials, those are not the ideal models for DCTs I would say so. And again, the logic is also the fact that, you know, when you're, you're going into the later phase trials, the volume of number of patients is increasing considerably to the point that Lorraine brought up about access to the patients about patient selection. The fact, I think what one should look at is really the advantages that it brings in, in terms of, you know, patient access in terms of patient diversity, which is a big piece that, um, the cities are enabling. So, um, if you, if, if you, if you look at the spectrum of, of these advantages and, and just to step back for a moment, if you, if you're looking at costs, like you're looking at things like remote site monitoring, um, is, is a big, big plus, right? >>I mean, uh, site monitoring alone accounts for around a third of the trial costs. So there are so many pieces that fall in together. The challenge actually that comes when you're in defining DCTs and there are, as Rick pointed out multiple definitions of DCTs that are existing, uh, you know, in the industry right now, whether you're talking of what Detroit is doing, or you're talking about acro or Citi or others. But the point is it's a continuum, it's a continuum of different pieces that have been woven together. And so how do you decide which pieces you're plugging in and how does that impact the total cost or the solution that you're implementing? >>Great, thank you. Last question we have in the audience, excuse me. What changes have you seen? Are there others that you can share from the FDA EU APAC, regulators and supporting DCTs precision medicine for approval processes, anything you guys would highlight that we should be aware of? >>Um, I could quickly just add that. I think, um, I'm just publishing a report on de-centralized clinical trials should be published shortly, uh, perspective on that. But I would say that right now, um, there, there was a, in the FDA agenda, there was a plan for a decentralized clinical trials guidance, as far as I'm aware, one has not yet been published. There have been significant guidances that have been published both by email and by, uh, the FDA that, um, you know, around the implementation of clinical trials during the COVID pandemic, which incorporate various technology pieces, which support the DCD model. Um, but I, and again, I think one of the reasons why it's not easy to publish a well-defined guidance on that is because there are so many moving pieces in it. I think it's the Danish, uh, regulatory agency, which has per se published a guidance and revised it as well on decentralized clinical trials. >>Right. Okay. Uh, we're pretty much out of time, but I, I wonder Lorraine, if you could give us some, some final thoughts and bring us home things that we should be watching or how you see the future. >>Well, I think first of all, let me, let me thank the panel. Uh, we really appreciate Greg from Lily and the meta from IDC bringing their perspectives to this conversation. And, uh, I hope that the audience has enjoyed the, uh, the discussion that we've had around the future state of real world data as, as well as DCT. And I think, you know, some of the themes that we've talked about, number one, I think we have a vision and I think we have the right strategies in terms of the future promise of real-world data in any number of different applications. We certainly have talked about the promise of DCT to be more efficient, to get us closer to the patient. I think that what we have to focus on is how we come together as an industry to really work through these very vexing operational issues, because those are always the things that hang us up and whether it's clinical research or whether it's later stage, uh, applications of data. >>We, the healthcare system is still very fragmented, particularly in the us. Um, it's still very, state-based, uh, you know, different states can have different kinds of, uh, of, of cultures and geographic, uh, delineations. And so I think that, you know, figuring out a way that we can sort of harmonize and bring all of the data together, bring some of the models together. I think that's what you need to look to us to do both industry consulting organizations, such as IBM Watson health. And we are, you know, through DTRA and, and other, uh, consortia and different bodies. I think we're all identifying what the challenges are in terms of making this a reality and working systematically on those. >>It's always a pleasure to work with such great panelists. Thank you, Lorraine Marshawn, Dr. Namita LeMay, and Greg Cunningham really appreciate your participation today and your insights. The next three years of life sciences, innovation, precision medicine, advanced clinical data management and beyond has been brought to you by IBM in the cube. You're a global leader in high tech coverage. And while this discussion has concluded, the conversation continues. So please take a moment to answer a few questions about today's panel on behalf of the entire IBM life sciences team and the cube decks for your time and your feedback. And we'll see you next time.

>>Hey, welcome to this continuing coverage of the H P E Aruba. Pensando announcement. I'm lisa martin. Hopefully you've seen by now the announcement from john and Antonio, we're going to get into some technical details. Now I've got two guests joining me. Please welcome Krishna Otopeni, the VP of engineering at Pensando and frank Reich stein, senior Director platform engineering from HP Aruba guys welcome to the program. >>Hi lisa. >>Hi lisa. Thanks for having us. >>Sure. So we're going to, we're going to dig in here. You guys are tasked with bringing these two worlds together, christian. Let's go ahead and start with you talk to me about the announcement why this is so significant and then we'll dig into the technical details. >>Yeah. So as you know, right, Pensando has been in the market for a couple of years right now. Um, and we heard a lot of success with the cloud providers and we're also working with be a million project Montreat. Um, so what we learned in the last couple of years, we're trying to take all the lessons and I was a little bit going to what, what we learned with the crop, your providers. So we took a dsC card, which is a B C, a form factor, the customer takes dsC card inserts into the, into server with various forces and hypervisors. So it's really exciting that the BSE is in production with some of the providers already and some of them were taking to production in this calendar quarter and we also have in connection with that first generation BSC cards a couple of years and some of the biggest banks and storage platform providers. So, so this is kind of a big deal for us because we are starting with what we call a D P U. Uh that Pensando is bailing which is the latest generation of it is called code named Alba which delivers the software in silicon program ability while matching the performance of hardware. So internally the DPU has the tight integration between special purpose processors that consent of what we call mps and a general purpose processor like arm course where we do the management and control software and with tied together with offload engines like encryption and compression. The key takeaway from this platform. Their consent of belt. It's it's programmable at all layers Either by Pensando or our customers whether it's in data plane using P four or control and management plane. All right. So what we learned while developing this platform and taking this production with the public cloud providers, we realize that the platform and architecture is not only very highly scalable with very high performance with respect to, you know, packets per second or stable connections per second or NBA me I ops but it's also adaptable like a very rapid paced. And another key lesson that we learn from our cloud partners is that the new devoPS model operations is as important as functionality. For example, the importance of creating the DPU pipeline the subsequent guarantees or providing Hatch uh first fateful connections so that in some cases the component fails, there is hardware or software customer doesn't have any disruption in his network or storage operations. So we took all the ski lessons that we learned over the last few years. And then we are building a new platform partnering with Aruba team which is very high scale with very high performance at the same time, tied with very good operations um that you know it comes the best of both both platforms from the pew side and from the Aruba side frank they want to add on the Aruba platform side. >>Sure, yeah. So the Aruba networking team has been building network switches for the past 25 years and we've been following all of the trends and evolutions over that time frame. And as we've gone through a few years ago we decided to make an evolution of our operating system to scale it up for the modern needs of the modern world. And this included doing things like designing with a micro services oriented architecture to provide for a high degree of resiliency throughout the product line. And then being able to extend that single network operating system from the core to the edge of the network. As we've been partnering with Pensando, it came very clear that the evolution of the network the next step was this form of a deep, you integrated into that top of rack switch to provide a deeper and richer feature set and what has traditionally been available in your top of rack switch. And so this partnership has enabled us to leapfrog but has been traditional top of rack functionality and add to it. Things that previously were not attainable in that layer of the network >>frank. Continuing on with you. Talk to me about some of the technology requirements and challenges of designing and engineering and delivering the industry's first distributed service switch. What were some of those? >>Sure, sure. So a lot of the challenges around integrating this type of solution come down to how to ensure that you have the highest performance possible and maintaining high speed of performance when you're now introducing an additional pay hop within the network topology inside of the switch, a lot of that came down to integrating the background and skill setting capabilities that come along with osc x that were made it quick for us to enable a new piece of functionality within the architecture and then a lot of credit has to go to the Pensando team for the richness of the feature setting capability set that they have within that DPU product as it stands >>christian, let's go ahead and dig through some of those core features and capabilities that are really going to be benefiting customers. >>Yeah, so basically right, uh taking a little bit of step back, we started with the dsc market from Pensando perspective where we wanted to put gPU in every survey and we obviously have success in enterprise customers and cloud customers that we discussed earlier. But we also learned a few lessons while deploying DSC and enterprise markets in the sense that enterprise markets do not need the performance of every DSC at 200 G full duplex network services for every survey. And also you know what makes historic key is that you know, there are a lot of brownfield service in current enterprise data centers where customers do not want to open up a server to put the DSC in. So we wanted to give a product with the form factor that frank is talking about and technology that's very familiar to every IT department given the Aruba Lois uh in a deployment in data centers. And also as I said earlier, what we lessons that we learned, we came up with this taking this production very deep you software and hardware which is deployed in public clouds. And combined with those features that that have been rapidly evolving uh through multiple Aruba releases into enterprise data centers in a switch form factors. So what we think is by doing this taking the best of both worlds. We're creating a new product category that is not that is for the features and capabilities are not available in the market from any vendor specifically providing state full services at every tour without the complexity of the service redirection because today's data centers if you want to install services. It's a it's a lot of effort operator to bring in those services. This obviously also has a great operational model, great TCO and the functionality that customers that you never see in tar before. For example, in the first release we are providing state full firewall with the visibility at every floor level that goes through the tower which never existed in the market before. >>New product category. That's a big deal christian. Talk to me a little bit about how long you guys have been at this, you were in stealth mode crack that open for us. >>I mean it has been a less than a year but of development that both teams have been doing and we work very closely together and we meet I mean for sure at least more than a week uh you know, more than once the once a week between uh frank's team and you know, and send it to them and there's a coordination between the sales team and the marketing team and the go to market team and then how we sell it and the manufacturing team, there's a lot goes on in building this product. I mean we believe this is the fastest uh tard new generational product that we built because because we could do that because the experience of both the teams trying they want anything more to this one. >>Yeah, I think that that really goes to the point here. The capabilities and maturity of the deep you solution that Pensando was bringing into the solution really allowed for a very fast and seamless integration on top of that Aruba, OsC X and the platform that we built there with automated Api generation and integration with our Aruba fabric composer orchestration layer really created the capability to make things go as fast as possible for this development effort And so to really take a new product and define a new product space within a 12 month time frame has been a really exciting and impressive feat by both teams. >>Very impressive considering the challenges and the dynamics in the market and the global market that we've had frank. How big of a lead do you think you have on incumbents here? >>I think we have a substantial lead on the incumbents here. I think what we're doing is a fundamentally different take on how you do a top of rack switch and the capabilities that we're bringing to bear at the top of rack are fundamentally new and differentiated from what the competition has been thinking about. So I believe we have a substantial lead on the competition. >>Excellent chris to talk to me about what's next? What's the future? I have some secret sources that tell me that john and Antonio are meeting regularly pushing you guys, what does the future hold. >>Yeah. So I mean obviously this is the start of an exciting journey. There's a first platform you're bringing to the market jointly and obviously we like a bunch of form factors without upcoming road map. So additionally I mean the software in silicon performance that with all the services that we deliver a software means that scope and scale of the state will services that we can deliver and evolve over time whether you talk about security or encryption or state flat or load balancing or d does all of the services and then you know hybrid connectivity. So obviously you know there's a lot that we can do with this platform that will be driven by with the partnership with our customers. We also see that you know the market of all where you know all the customers we'll have some customers will have deep us in the service and some customers will use the new platform that we're bringing together. So we won't have all the management start to make sure all of them can be managed uniformly and any time you know you this is a major step for a new category of platform and architecture we're developing jointly with the rubber and I believe this will be a huge opportunity for both the companies and our customers and this is exciting times ahead for us >>and talk to me both of your opinions here where can customers go to find more information, how can they get started frank will go ahead and start with you. >>Yeah you can jump straight to Aruba networks dot com and dig into the feature sets and packages that we have available with the Aruba 10-K product line direct from there. >>Fantastic christian anything to add >>that is correct actually. So we are treating it as one product coming from both the companies. All the documentation is where you know, frank pointed out in Aruba website, we put all the documentation at the same place and we're supporting it as one unified product from both the companies. >>Are you seeing any? We've seen so much change in the last year and a half. Last question. I'm just wondering if if either of the HPV riverside or the pence underside is seeing any industries that might be really prime to take advantage of knowing how many industries all have been affected by the events of the last year and a half christian any thoughts there? >>Yeah, I mean if you look at it right and obviously all of us are working from home and now everything happens, you know, mostly at the edge, right? You know, and we are in that this platform will help us get there where we get security to the edge and we get more visibility and more services to the edge. Right? So I mean that's what you know Pensando is all about and hoping that you know, this is uh this journey that we started with the D. P us, we go with this platform and it will ever all and it will help customers, our customers and our partners leverage all the functionality that, you know, Pensando and the rubber can bring together. >>Well guys, congratulations on an enormous feat accomplished in not just a 12 month time period, but a very challenging 12 month time period. We appreciate you guys breaking down the HP Aruba Pensando announcement and more technical detail. Those can go to learn more information and again, congratulations. >>Thank you. >>Thank you very much lisa >>for my guests. I'm lisa martin. You're watching this HP Aruba Pensando announcement. Thanks for watching. >>Mhm >>mm.

>>mm we are back and we're continuing the coverage on H P E. Aruba's news today around the D S X six S C X 10-K with Pensando. Now we want to get the perspective of a system Integrator because they're in the front lines, they understand how to put the pieces together where you're happy to bring john Galatea of Dasher technologies dashes and in the end I. T solutions provider, they gotta focus a lot of expertise on infrastructure, jOHn welcome. Good to see you. >>Thank you for having me. Good to be here. >>That's our pleasure. So I wonder if you could give us a little bit more color on Dasher where you focus what your core companies competencies are, what industries you focus on etcetera. >>Yeah, absolutely. So a dasher, we assess architect implement and manage I. T. Solutions that digitally transform businesses. Our practice areas include cybersecurity, networking, cloud data center and we also offer pro professional services around those practice areas. We partner with all the major tech companies in the space. Some of the examples are HP, Cisco, Aruba Palo Alto eight Ws and many others that fill out the, you know that practice area. >>Well that's great. So you have a very wide observation space, that's why we like talking to SA as you have an independent mindset and you can kind of tell it like it is. But so what are you seeing with customers? It's exactly, we hear a lot about digital transformation, you mentioned security, you're obviously doing cloud that's it's almost like john these pieces are all coming together to power Digital and digital transformation and we were forced into it over the past 18 months. And now people are stepping back saying hey okay we have all these resources, how do we put them together and really transform our business? What do you see? >>Yeah, seeing similar things. So you know, our customers are telling us that they're looking for more speed, more agility, um you know, limited complexity because they're trying to do more every single day with less staffing and a sophistication of integrating functionality that breaks down I. T. Silos. Um there also evaluating security span versus effectiveness And they're moving towards zero trust. >>Yeah. So I want to, I'm gonna come back and ask you about that. So I've written a lot about this is that you look at how much we spend versus as you say the effectiveness and there's sort of an imbalance there, it's like we can't spend enough, it budgets they're not infinite. And even though security is top of top priority for ceos, they've got other things that they have to fund and then zero trust, you know, before the pandemic john that was a buzzword and now it's become a mandate. Any thoughts on that >>in terms of zero Trust? Absolutely yeah it is a mandate, we've seen more and more of our customers moving toward in this direction and defending themselves against cyber threats and yeah absolutely. It accelerated during the pandemic and is continuing to accelerate today. >>Right? And I think there's some things that were reported now going to be permanent with regard to obviously hybrid and the like, cloud security and so forth. So, okay, let's get into some of the news here. What's the big trend, john can you explain the relevance of the H P E, Aruba and Pensando news? >>Yeah, I mean when I first heard of it, you know, I I looked at it as a whole new category because it's a category that's going to deliver cloud scale distributed services closer to where applications are. It's going to simplify. One of the things we mentioned earlier was limiting complexity. So it simplifies the network um, by putting security provisions and operations in a unified management platform and it helps improve your security posture around moving towards zero trust and limits the appliance and vendor sprawl that you might ordinarily have in a in a existing network today. >>Okay, so that's kind of the business cases, you're consolidating a lot of piece parts and that's, you know, from a system integrator standpoint. You know, it's funny people often say, well, isn't that bad for the s I'm like, no, they don't want to be in the business of plumbing, they want to be in the business of, you know, more strategy if they if they just end up bolting stuff together, they're going to go out of business, They need to extend their value. So as a strategic partner, you got an early preview of this launch? The D S S D S S C X 10,000, what was your initial impression reaction you called it? A new category? What do you mean by that? >>Well, it's a new category of of of a data center switch in the digital infrastructure because it includes or incorporates security. Um And more specifically it includes security around east west traffic, which is it doesn't eliminate your perimeter firewall but it actually incorporates more functionality which leads to better simplicity and easier use of management of a platform. So for us, I'm really excited to go position and talk to our clients about this. >>Yes. So we're seeing the flattening of that network, that's even it's obviously been accelerated by the pandemic, everybody talks about that. But if you think about the traditional headquarter hierarchical network and now all of a sudden everybody's working remotely using more cloud. Using more distributed infrastructure that flattens the network. That creates security challenges because you can't just build a perimeter and say, okay, we're safe. You now have to go to where the adversary is and that's everywhere. So what's your sense as to how customers are going to react to this new category of switch? >>I think really my sense is that I've got a really positive outlook on this product. I mean hardware, firewalls are costly and deploying software agents can be very disruptive and when you're integrating it into the switch layer. So um I think the C X 10,000 provides a great alternative to an embedded accelerated services embedded in accelerate service into the D C fabric. Um, it's great for brownfield migration, um, rack pod and you know, and the standards based leaf, you know, L two, L three um, and it doesn't necessarily replace, as I mentioned earlier the perimeter security, but um, it can cap and grow with DSS and east west firewall traffic. >>Yeah. And I think we've seen when we talked to see so, so like you said, it does, it doesn't replace the traditional perimeter security but you're going to see a shift and spending priorities obviously to a comedy because as I said earlier, there's not infinite budget but john give us the big takeaway, Bring us home. What what, what do you want to leave our audience with? >>Yeah, I think, you know, the number one takeaway is that it's a massive opportunity to reduce complexity, enhanced security and lower costs in the data center by eliminating dedicated devices and embedding services through software capability in the network closer to where workloads are are moving. So that's the big takeaway for me and for, I think for our clients, um, you know, other things are, you know, you're the data center perimeter is no longer confined and open an on prem location but extends out, right. We're seeing customers extend out to the cloud and across uh, you know, disparate locations, co locations. So The traditional architecture isn't going to be well suited for this, and I think the CX- 10,000 and its feature set are going to be really great for addressing the changing market. >>Yeah, that's, that's all. I mean, again, we're seeing the democratization of everything and and networking is, is no exception. The notion of simplify simplification, john really appreciate your time. Thanks for coming on. >>Thank you for having me. >>You're welcome. Okay, keep it right. There were unpacking the changing trends in networking generally, and specifically switch networking with HP, Aruba and Pensando and the cube. Keep it right there.

>>Hello and welcome to the power of and where H P E Aruba and Pensando are changing the game the way customers scale at the cloud and what's next in the evolution in switching everyone. I'm john ferrier with the Cuban. I'm here with Shane Corbyn, Director of Technical Product management. Pensando Williams show vice president Product management, Aruba HP Gentlemen, thank you for coming on and doing a deep dive and and going into the big news. So the first question I want to ask you guys is um, what do you guys see from a market customer perspective that kicked this project off? Amazing results over the past year or so. Where did it all come from? >>It's a great question, John So when we were doing our homework, there were actually three very clear customer challenges. First, security threats were largely spawned with from within the perimeter. In fact, four star highlights that 80% of threats originate within the internal network. Secondly, workloads are largely distributed, creating a ton of east west traffic and then lastly, network services such as firewalls load balancers. VPN aggregators are expensive. They're centralized and then ultimately result in service changing complexity. So everyone, >>so go ahead. Change. >>Yeah. Additionally, when we spoke to our customers after launching initially the distributed services platform, these compliance challenges clearly became apparent to us and while they saw the architectural value of adopting what the largest public cloud providers have done by putting a smart making each compute note to provide these state full services. Enterprise customers were still were struggling with the need to upgrade fleets and Brownfield servers and the associated per node cost of adding a spark nick to every compute node. Typically the traffic volumes for on a personal basis within an enterprise data center are significantly lower than cloud. Thus we saw an opportunity here to in conjunction with Aruba developed a new category of switching product um, to share the crossing capabilities of our unique intellectual property around our DPU across a rack of servers that Net Net delivers the same set of services through a new category of platform, enabling a distributed services architecture and ultimately addressing the compliance and uh, TCO generating huge TCO and ri for customers. >>You know, one of the things that we've been reporting on with you guys as well as the cloud scale, this is the volume of data and just the performance and scale I think the timing of the, of this partnership and the product development is right on point. You got the edge right around the corner more, more distributed nature of cloud operations, huge, huge change in the marketplace. So great timing on the origination story there. Great stuff. Tell me more about the platform itself. The details what's under the hood, the hardware. Os, what are the specs? >>Yeah, so we started with a very familiar premise, Ruba customers are already leveraging C X with an edge to cloud, common operating model and deploying Leaf and spy networks. Plus we're excited to introduce the industry's first distributed services switch where the first configuration has 48 25 gig ports with 100 gig uplinks running Aruba C X cloud native operating system. Pensando A six and software inside enabling layer four through seven staple services you want to elaborate on. >>Let me elaborate on that a little further. Um, you know, as we spoke, existing platforms and how customers were seeking to address these challenges were inherently limited by the diocese and that thus limited their scale and performance and ability in traditional switching platforms to deliver truly stable functions in in a switching platform. This was, you know, architecturally from the ground up. When we developed our DPU 1st and 2nd generation, we delivered it or we we we built it with staples services in in mind from the Gecko. We we leverage to clean state designed with RP four program with GPU, we evolved to our seven nanometer based DPU right now, which is essentially enabling software and silicon and this has generated a new level of performance scale flexibility and capability in terms of services this serves as the foundation for or 200 gig card where we're taking the largest cloud providers into production for. And the DPU itself is designed inherently to process state track state connections and state will flow is a very, very large scale without impacting performance. And in fact, the two of these deep you component service, their services foundation of the C X 10-K And this is how we enable states of functions in a switching platform. Functions like stable network network fire walling, stable segmentation, enhance programmable telemetry. Which we believe will bring a whole lot of value to our customers. And this is a, a platform that's inherently programmable from the ground up. We can we can build and and leverages platform to build new use cases around encryption, enabling state for load balancing, stable nash to name a few. But the key message here is this is this is a platform with the next generation of architecture is in mind is programmed but at all levels of the stack and that's what makes it fundamentally different than anything else. >>I want to just double click on that if you don't mind before we get to the competitive question because I think you brought up the state thing, I think this is worth calling out if you guys don't mind commenting more on this state issue because this is big cloud. Native developers right now want speed, they're shifting left at the Ci cd pipeline with program ability. So going down and having the program ability and having state is a really big deal. Can you guys just expand on that a little bit more and why it's important and how hard it really is to pull off. >>I I can start I guess. Well um it's very hard to pull off because of the sheer amount of connections you need to track when you're developing something like a state, full firewall or state from load balancer. A key component of that is managing the connections at very, very large scale and understanding what's happening with those connections at scale without impacting application performance. And this is fundamentally different. A traditional switching platform regardless of how it's deployed today in a six don't typically process and manage state like this. Memory resources within the shape aren't sufficient. Um the policy scale that you can implement on a platform aren't sufficient to address and fundamentally enable deployable fire walling or load balancing or other state services. >>That's exactly right. So the other kind of key point here is that if you think about the sophistication of different security threats, it does really require you to be able to look at the entire packet and more so be able to look at the entire flow and be able to log that history so that you can get much better heuristics around different anomalies. Security threats that are emerging today. >>That's a great great point. Thanks for bringing that extra extra point out, I would just add to this, we're reporting this all the time when silicon angle in the cube is that you know, the you know, the the automation wave that's coming with around data, you know, it's the center of data now, not date as soon as we heard earlier on with the presentation data drives automation having that enabled with state is a real big deal. So I think that's really worth calling out now. I got to ask the competition question, how is this different? I mean this is an evolution, I would say it's a revolution you guys are being humble um but how is this different from what customers can deploy today >>architecturally, if you take a look at it? So we've, we've spoken about the technology and fundamentally in the platform, what's unique in the architecture but foundational e when customers deploy stable services, they're typically deployed leveraging traditional big box appliances for east west or workload based agents which seek to implement stable security for each East west architectural, what we're enabling is staples services like fire walling, segmentation can scale with the fabric and are delivered at the optimal point for east west which is through the Leaf for access their of the network and we do this for any type of workload. Being deployed on a virtualized compute node being deployed on a containerized, our worker node being deployed on bare metal agnostic of topology. It can be in the access layer of a three tier design and a data center. It can be in the leaf layer of the excellent VPN based fabric. But the goal is an all centrally managed to a single point of orchestration control which William we'll talk about shortly. The goal of this is to to drive down the TCO of your data center as a whole by allowing you to retire legacy appliances that are deployed in in east west role, not utilized host based agents and thus save a whole lot of money. And we've modeled on the order of 60 to 70% in terms of savings in terms of the traditional data center pod design of 1000 compute nodes which will be publishing and as as we go forward, additional services as we mentioned like encryption, this platform has the capability to terminate up to 800 gigs of line, right encryption, I P sec VPN per platform state will not load balancing and this is all functionality will be adding to this existing platform because it's programmable as we mentioned from the ground up. >>What are some of the use cases lead and one of the top use case. What's the low hanging fruit? And where does this go? Service providers enterprise, what are the types of customers you guys see implementing? >>Yeah, that's what's really exciting about the C X 10,000 we actually see customer interest from all types of different markets, whether it be higher education service providers to financial services, basically all enterprises verticals with private cloud or edge data centers for example, could be a hospital, a big box retailer or Coehlo. Such as an equity. It's so it's really the 6 10,000 that creates a new switching category enabling staple services in that leaf node, right at the workload, unifying network and security automation policy management. Second, the C X 10,000 greatly improved security posture and eliminates the need for hair pinning east west traffic all the way back to the centralized plants. Lastly, a Shane highlighted there's a 70% Tco savings by eliminating that appliance brawl and ultimately collapsing the network security operations. >>I love the category creation vibe here. Love it. And obviously the technical and the cloud line is great. But how do the customers manage all this? Okay. You got a new category. I just put the box in, throw away some other one. I mean how does this all get down? How does the customers manage all this? >>Yeah. So we're looking to build on top of the ribbon fabric composer. It's another familiar sight for our customers which already provides for compute storage and network automation with a broad ecosystem integrations such as being where the sphere be center as with Nutanix prison And so aligned with the c. x. 10,000 at G. A. now the aruba fabric composer unifies security and policy orchestration and management with the ability to find firewall policies efficiently and provide that telemetry to collectors such a slump. >>So the customer environments right now involve a lot of multi vendor and new frameworks cloud native. How does this fit into the customer's existing environment? The ecosystem. How do they get that get going here? >>Yeah, great question. Um our customers can get going is we we built a flexible platform that can be deployed in either Greenfield or brownfield. Obviously it's a best of breed architecture for distributed services were building in conjunction with the ruble but if customers want to gradually integrate this into their existing environments and they're using other vendors, spines or course this can be inserted seamlessly as a leaf or an access access to your switch to deliver the exact same set of services within that architecture. So it plugs seamlessly in because it supports all the standard control playing protocols, VX, Lenny, VPN and traditional attitude three tier designs easily. Now for any enterprise solution deployment, it's critical that you build a holistic ecosystem around it. It's clear that this will get customer deployments and the ecosystem being diverse and rich is very, very important and as part of our integrations with the controller, we're building a broad suite of integrations across threat detection application dependency mapping, Semen sore develops infrastructure as code tools like ants, Poland to answer the entire form. Um, it's clear if you look at these categories of integrations, you know XDR or threat detection requires full telemetry from within the data center. It's been hard to accomplish to date because you typically need agents on, on your compute nodes to give you the visibility into what's going on or firewalls for east west flaws. Now our platform can natively provide full visibility in dolphins, East west in the data center and this can become the source of telemetry truth that these Ml XT or engines required to work. The other aspects of ecosystem are around application dependency mapping the single core challenge with deploying segmentation. East West is understanding the rules to put in place right first, is how do you insert the service uh service device in such a way that it won't add more complexity. We don't add any complexity because we're in line natively. How do we understand that allow you to build the rules are necessary to do segmentation. We integrate with tools like guard corps, we provide our flow logs a source of data and they can provide rural recommendations and policy recommendations for customers around. We're building integrations around steve and soar with tools like Splunk and elastic elastic search that will allow net hops and sec ops teams to visualize, train and manage the services delivered by the C X 10-K. And the other aspect of ecosystem from a security standpoint is clearly how do I get policy from these traditional appliances and enforce them on this next generation architecture that you've built that can enable state health services. So we're building integrations with tools like toughen analgesic third party sources of policy that we can ingest and enforcing the infrastructure allowing you to gradually migrate to this new architecture over time >>it's really a cloud native switch, you solve people's problems pain points but yet positioned for growth. I mean it sounds that's my takeaway. But I gotta ask you guys both what's the takeaway for the customers because it's not that simple for that. We have a complicated >>Environment. I think, I think it's really simple every 10 years or so. We see major evolutions in the data center in the switching environment. We do believe we've created a new category with the distributed services, distributed services, switch, delivering cloud scale distribute services where the local where the workloads were side greatly simplifying network security provisions and operations with the Yoruba fabric composer while improving security posture and the TCO. But that's not all folks. It's a journey. Right. >>Yeah, it's absolutely a journey. And this is the first step in in a long journey with a great partner like Aruba, there's other platforms, 100 or four gig hardware platforms we're looking at and then there's additional services that we can enable over time allowing customers to drive even more Tco value out of the platform and the architectural services like encryption for securing the cloud on ramp services like state for load balancing to deploy east west in the data center and you know, holistically that's that's the goal, deliver value for customers and we believe we have an architecture and a platform and this is the first step in a long journey. It's >>a great way. I just ask one final final question for both of you. As product leaders, you've got to be excited having a category creation product here in this market, this big wave. What's what's your thoughts? >>Yeah, exactly. Right. It doesn't happen that often. And so we're all in, it's it's exciting to be able to work with a great team like Sandu and chain here. And so we're really excited about this launch. >>Yeah, it's awesome. The team is great. It's a great partnership between and santo and Aruba and you know, we we look forward to delivering value for john customers. >>Thank you both for sharing under the hood and more details on the product. Thanks for coming on. >>Thank you. Okay, >>the next evolution of switching, I'm john furrier here with the power of An HP, Aruba and Pensando, changing the game the way customers scale up in the cloud and networking. Thanks for watching. Mhm.

>>Okay, okay, we're back, you're watching the cubes, continuous coverage of HBs Green Lake announcement. One of the things that we said on the Cuban. We first saw Green Lake was let's watch the pace at which H P E delivers new servants is what's that cadence like? Because that's a real signal as to the extent that the company's leading into the cloud and today we're covering that continued expansion. We're here with Tom Black, who was the general manager of HPC storage and Omar assad, who's the storage platform lead for cloud data services at Hewlett Packard Enterprise gentlemen welcome. It's good to see you. >>Thanks Dave. Thanks for having us today. Good to see you. >>Happy to be here. Dave. >>So obviously a lot has changed globally, but when you think of things like cyber threats, ransomware, uh, the acceleration of business transformation, uh, these are new things, a lot of it is unknown a lot of it was forced upon us tom what are you guys doing to address these trends? How are you helping customers? >>Sure, thanks for the question. So if you think back to what we launched in early May, kind of the initial cloud transformation of what was our traditional storage business. Um, we really focused on one key theme. Very customer and customer driven theme that the cloud operational model has one and that customers want that operational model, whether they're operating their workload in the cloud or whether they're operating that workload in their own facility or Nicolo kind of the same thing. So that was kind of our true north and that's what we launched out of the gate in May. But we did allude in May to the fact that we would have an ongoing series of new services coming out on the uh H B Green Lake edge to cloud platform. And just really excited today to be talking about somewhat that expansion looks like um we will continue uh through this month and through the quarters ahead to really add more and more services in that vein of focusing on bringing that true cloud services model to our customer. So we're really excited today to unveil kind of, we've entered the data protection as a service market with HP Green Lake. So this is really our expansion into a very top of mind topic and set of problems and solutions or headaches and aspirins, to quote an old friend um that Ceos faces, they think about how to manage data through its life cycle in their organization. >>When I talked to see IOS during the pandemic. Not that we're out yet, but really in the throes of it and asked them about things like business resilience that they said, you know, we really had to rethink our disaster recovery strategy. It was it was sort of geared toward a fire or a hurricane and we we just didn't even imagine this type of disaster if you will. So we really needed to rethink it. So when I, I see your disaster recovery as a service and capabilities like that. Is that the Xarelto acquisition? >>Yes. Dave thanks you. So we're super happy to have the Xarelto team now as part of our family. Um, just a brilliant team, a well respected technology, uh, kind of a blue chips at our customers and partners that really appreciate what zero has to offer. Um, as we looked at the data protection as a service market, one of the hardest problems is really in that disaster recovery space, I think Omar's gonna talk a little bit more about today. Um, but sort of really does bring the leading industry, what's called continuous data protection um, capability into our green lake platform. Um, we've just recently closed the acquisition and we're working on kind of integration plan as we speak now that we can actually talk to each other post close. Um, but you'll uh, you'll continue to see, you know, some really exciting milestones each and every quarter as we march forward with certain now as part of the family. >>So we all talk about how data is, is so important. We certainly learned during the pandemic that that if you weren't a digital business, you were out of business and a digital business is a data business. So things like backup data protection as a service become increasingly critical. I know you have some capabilities there maybe you could share with us. >>Absolutely. So you know, one of the things that we noticed was as we took the storage business through its transformation and we started can work you know, with the launch of the electron 90 and the six K platform. We really really brought the cloud operational model to our customers. So one of the things that you know, feedback that was coming loud and clear to us is that as we look at the storage portfolio where we look at file block and object, which are now being transformed into a cloud operational experience, data protection, disaster recovery coming back into business after a disaster snapshot management. All of those capabilities, we still have to rely on our partner technologies in order to do that now. It's not bad that we have great partners in the data protection world, but what we're really focused on is that cloud operational model and cloud operational experience and to and as tom mentioned through the data management life cycle. So as a result of that, we talked to a lot of our customers, we talked to a bunch of partners and one of the things that was coming back was that yes, there are many data protection backup offerings on the market. But that true as a service experience that is completely integrated to the services experience of the storage that the customers is experiencing that is not there. So what we looked at was especially to the largest ecosystem, which is the VM ware ecosystems. So we're launching data protection as a service or backup as a service for our VM ware customers offered from data services, cloud console as a SAAS portal. 100% SAs service, nothing to install. No media servers, no application servers, no catalog servers, no backup targets, no patching, no expansion, no capacity planning. None of that is needed. All that's needed is sign on click. Give your V center credentials and off you go, that's it. That is it three clicks and you're in business. So currently, you know, in our, in our analysis we offer five x faster recovery from any of the competitive offerings that there there there are 3.5 better de doop ratios. But for our customers is as simple as this. VM is protected as this many dollars per gig per month. That's it. No backup target, no media server, no catalogs are nothing nothing to manage total Turkey off of the portal. So that's the cadence of services that if you promise and this is one of the first ones when it comes to data management that is coming out into the open. >>So you may have just answered this question, but I want to pose it and get you maybe just summarize it because tom was talking earlier about the customer mandate for cloud in a cloud operational model. So I want you to explain to the audience how you're making that real >>actually can I start that one should be the test was monday morning. Getting ready for this chat with you Dave they got me on console and I'm not kidding three clicks, I got back up and running off the lab VM ware instance so I'll pass it off to you the real answer. But if I could do it three clicks >>as well as a convenience of this service, even tom can be your back, you might be able to do with this. Uh again, you know, a very important question the when you, when you look at the cloud operational model as you abstracts the hardware and and take the management model up into a SAS service, it gives our customers that access to that continuous delivery access that we have. We're going to continue to make the service medal better in the cloud model and automatically customers get the value of it without even reinstalling or going through a patch cycle or an upgrade cycle. But as we get into this cloud operational model, one of the things that was missing was uh if you if you if you if you start to talk about applications, how our application workloads going to be deployed, how are they going to be protected and how are they going to be expanded? So what we did was we, we expanded our info site offerings by merging them into the data services, cloud console and we're releasing a new service called app insects. It is going to be available to our customers at the end of the month. Uh It is, nothing has to change. They don't have to install any sort of agents or or host modifications, nothing like that. If their customers of electra nimble primary boxes and they're using info site and data services, cloud console, they will automatically get app insights. What Athens sites does is it really teases apart all that data that we have been collecting within foresight and now with the acquisition of HPV cloud physics, we're merging them together and relating the operational stacked top to bottom. So discovering all the way from your application usage, network usage, storage, use it. IOP usage VM values cross, collaborating them and presenting that to a customer from an app or an outcome perspective all in the data services, cloud console. So what this does for our customers is it really really transforms not only their operational experience but also buying experience. Because if you remember in one of the earlier releases of data services cloud console we released this application called, you know, intelligent intent based provisioning in which you just describe your workload and we go ahead and we provision that app insights and info site, feed that information directly into that and cloud physics generates and results and displays those analytics back to us to your partner of record and to the H. B. So we can all come together on a common data driven discussion point with our customers to continue to make their journey better >>tom where's all the boxes, traditional storage is changing. I've actually been waiting for this day for a long, long time. We've certainly seen glimpses of it from the cloud players, but they don't have, you know, super rich portfolio storage portfolio. They're growing now, but this is a really good strong example of a company with a large storage portfolio. That's, I mean I haven't heard the word three power once today. Right. And so what that says to me, that's an indication that you're thinking like a cloud player, can you maybe talk >>to that? Sure. Yeah, we're just tremendously excited about this transformation and really the reception we've got in the market from analysts, from partners, from customers because you're right, you haven't heard us talk about a box at all today. It's really about a block service, a file on the object service, a backup and recovery service, disaster recovery service. That that's that is the the language, if you will of the business problems of our customers not, do they need to pick this widget or that widget. And how many apps can I get here and there? And which did the h a cage protection scheme be that, is that, is our job to manage underneath are true North, which is the cloud operational model. And so that's going to be really how we we've set our course and how we will uh kind of deliver products solutions offers into the market underneath that umbrella, Ultimately, um getting our customers wherever their data is Dave to be able to interact at that service level instead of at that infrastructure box >>level, you've got my attention wherever the data. So that's the north star here is this is, you know, you're not done today obviously, but you've got a vision to bring that to the cloud across clouds on prem out to the edge. That's the abstraction layer that you're gonna build, your hiding all that complexity. That's correct. And that's cloud. The definition of cloud is changing. >>Yeah, >>it's no longer started, it's no longer a remote set of services. Somewhere up in the cloud. It's expanding on prem hybrid across clouds edge >>everywhere. You're exactly right. Dave it is, cloud is more about the experience and the outcome. It gives a customer than actually where the compute or storage is. We've chosen to take a very customer an agnostic position of whether it's, you know, data in your premise, data in your cloud. We're going to help you manage that data and deliver, you know, that data to workloads and analytics, uh, wherever the, wherever the compute needs to be, where the data needs to be. Again, technologies like Xarelto giving instability and move data across clouds from facilities and clouds back and forth. So it's a really exciting new day for HP. Green Lake were just so super happy to bring these technologies out and really continue to follow on the course of doing what we said, we would do >>the new mindset starts there, I guess it's obviously knew certainly new technologies, uh, you're talking about machine intelligence is a metadata challenge. Absolutely. Big time, you know, long term that North Star that we talked about and applying that machine intelligence, all the experience that you gather data that you're gathering is, I think ultimately how customers want you to solve this problem >>in the middle of info site data services, cloud console and the instrumentation that is already shipping on our appliances, both in edge appliances and the data center appliances were collecting more than a trillion data points over the period of a quarter. Right at the end of the day. So it's harnessing that at the back end to cross relate and then using the cloud physics accusation. What we're doing is we can now simulate these things on behalf of our customers into the future timeline. So at the end of the day, it's really about listening to the customer and what outcomes that they want to achieve with their data storage is there we provide excellent persistence layers where customers can store their data safely. But at the end of the day it's customers choice, They can store their data out of the edge in compute servers, commodity servers, X 86 servers, they can have their data in the data center which they are privately owned or their data can be in a service provider or it can be in a hyper secular. The infrastructure of the persistence layer is independent from the data services. Cloud console data services. Cloud console provides our customers with a SAS based industry leading metadata rich management experience, which then allows you to draw conclusions. So services like cloud physics services like uh enforce it, provide the analytics and richness of the metadata, backup and recovery service allows us to index our customers data and add a rich metadata to that and then combine that with xylitol, which is our disaster recovery as a service offering. Going to start over here. That gives the customer a very simple slider as to where they want their protection levels to be, they want their protection to be instant or they want their protection to be lazy eight hours window. But the thing is at the end of the day, it's about choice without managing the complexities of the hardware >>underneath because programmable completely right I come in, what I'm hearing is file object blocks of your multi protocol. I got a full stack so data data reduction, my snaps might replicate whatever whatever I need it in there as a service. I can I can access latency sensitive storage if I need to or I can push it out to cheaper stores. I could push it out to the cloud, presumably I could someday I air gap it uh and it's all done as infrastructure as code and then different protection levels where I see this going. It really gets exciting is you're now a data company and you're bringing ai machine intelligence and driving data products, data services for your customers who are going to monetize that at their end of the value >>chain. That's right. That's right. And safely insecurity. Keeping in mind that was their toes technology. We can give you, you know, small second recovery points to protect against ransomware. So all of that operational elegance, all those insights and intelligence to help you build a more agile, um you know, workloads centric organization, but then to do it safely and securely against ransomware, that's kind of the storm, if you will. That's brewing. And we're just really excited to be at the eye of it. >>I'm excited to. This is uh I've been waiting for this day for a long time and we're not talking about envy, Emmy and Atomic Rights and I love that stuff by the way and I'm sure it's all under the covers, but that's not what drives business value guys. Thanks so much for coming on the Cuban. David. >>Thanks for having us. It's been great. Thank you. >>All right. We're seeing a transformation all through the stack and keep it right there. This is Dave Volonte for the Cuban. Our coverage of HBs Green Lake announcements right back mm mhm

>>the idea of cloud is changing from a set of remote services somewhere out there in the cloud to an operating model that supports workloads on prem across clouds and increasingly at the near and far edge moreover, workloads are evolving from a predominance of general purpose systems to increasingly data intensive applications, developers are a new breed of innovators and kubernetes is a linchpin of creating new cloud native workloads that are in the cloud but also modernizing existing application portfolios to connect them to cloud native apps. Hello, we want to welcome back to HPD discovered 2021 the cubes ongoing coverage. This is Dave Volonte and with me are scott. Buchanan is the vice president of marketing at VM ware and Toby Weiss, who is the vice president of global hybrid cloud practice at HP gents. Welcome to the Q. Great to see you. Thanks for coming on. >>Thank you. Day agreed to be here. >>Okay, thanks for having >>us. So you heard my little narrative upfront. Um and so let's get into it. I want to start with with some of the key trends that you guys see in the marketplace and maybe scott you could kick us off from VM ware's perspective. What are you seeing that's really driving? Uh I. T. Today. >>Well, Dave you started with a conversation around cloud, right, and you can't really have a conversation around cloud without also talking about applications. And so much of the interaction that we're having with customers these days is about how we bring apps and clouds together and modernize across those two dimensions at the same time. And that's a pretty complex discussion to have and it's a complex journey to navigate. And so we're here to talk to customers and to work with h Pe to help our customers across those two dimensions. >>Great, so Toby I mean, it's always been about applications, as scott said, but but the application, the nature of applications is changing how we develop applications. The mentioned it sort of data intensive applications were injecting ai into virtually everything the apps, the process, the the people even um uh from a from the perspective of really a company that supports applications with infrastructure, what are you seeing in the marketplace? What can you add to that discussion? >>Yes. Great point. Dave you know, with the scent with applications becoming more central, think about what that means uh and has been for developer communities and developers becoming uh more important customers for I. T. Uh We have to make it easier for these developers uh to speed their innovations to market. Right? The business demands newer and faster capabilities of these applications. So our job in the infrastructure and was called the platform layer is to help we need to build these kinds of platforms that allow developers to innovate more quickly. >>So we talked earlier about sort of modernizing apps. I mean, it seems to me that the starting point there is you want to containerized and obviously kubernetes is the, is the key there, But so okay, so if that's the starting point, where is the journey, what does that look like? Maybe scott you could chime in there >>Sure. A couple of quick thoughts there, Dave and Toby to build on first is if you look at the Cloud Native Computing Foundation, Landscape today, what you can do at landscape dot c n c f dot io Holy Smokes, is that a jungle? So a lot of organizations need a guide through that CN cf landscape, they need a partner that they can trust to show them the way through that landscape. And then secondly, there needs to be ways to make these technologies easier to adopt and to use in practice, kubernetes being the ultimate example of that. And so we've been hard at work to try and make it easy and natural to make kubernetes part of one's existing infrastructure, so that building with and working with containers can be done on the same platform that you're using for virtual machines. >>So let's talk a little bit about cloud. Um and how you guys are thinking about cloud, remember told me that Back in VM World 2010, it was the very first vm world for the Cube. All we talked about was a cloud, but it was a private cloud, was really what we were talking about, which at the time largely met the virtualized data center. Um it was kind of before the software defined data center and today we're still talking about cloud, but it's it's hybrid cloud. It's kind of the narrative that I set up front data center. It's become for the most part software to find. And so how do you see this changing the I. T. Operating model? >>I think it's a great question. And look today you will see us talk a lot about this notion of cloud everywhere. So less differentiation about private and public and more about the experience of cloud. Right. Public. Cloud brought great innovations and what better than to bring those innovations to on premise workloads that we have chosen to operate and work there. So as we think about cloud more as an experience we want for our developers and our end users and our I. T. Organizations. We begin to think about how can we replicate that experience in an on premise environment. And so part of that is having the technologies that enable you to do that. The other part is um we most of us have evolved right the organization operating models to operate our cloud infrastructures off premises. Well now expanding that more holistically across our organization so we don't have to operating models but a single operating model that bridges both and and brings the ability of both of those together to get the most benefit as we really become to integrate and become truly hybrid in our organization. So I think the operating model is critical and the kinds of experiences we deliver to the users of that I. T. Uh infrastructure and operating model is critical as well. >>Are you guys are both basically in the infrastructure business but scott maybe we can start with you. There's a lot of changes that we're talking about in it. Generally the data center specifically especially big changes in workloads, with a lot more data intensive apps ai being injected into everything kubernetes, making things more fassel. And in many ways it simplifies things, but it also puts stress on the system because you've got to protect this. They they're no longer stateless apps right there, state full and you gotta protect them and and so they've got to be compliant. Um now you've got the edge coming in. Uh So my question is, what does infrastructure have to do to keep pace with all this application innovation? >>Uh one of the conversations that we are having increasingly with our customers is how can they embrace a dev sec ops mindset in their organization and adopt some of these more modern patterns and practices and make sure that security is embedded in the life cycle of the container. And and so I think that this is part of, the answer is equipping the operator through infrastructure to set guard rails in place so that the development organization can work with freedom inside of those guard rails. They can draw on a catalogs of curated container. Images, catalogs of apps start from templates. Those are the building blocks that allow developers to work faster and that allow an operator to ensure the integrity and compliance of the containers and the applications of the organizations building. >>Yeah, So, so that's kind of uh when I hear scott talked about that Toby I think infrastructure as code designing security and governance in right? We always we always said I was an afterthought. We kind of bolted it on second. The security team had to take care of that. This is always the same thing with backup. Right? So we got an app. It's all ready to go. How do we back it up? And so that's changing that whole notion of, of infrastructure as code. Um, I want to talk about Green lake in a minute, but, but before we get there, I wonder if you could talk about how HP E thinks about VM ware and how you guys are partnering. I'm specifically interested and where each of you sees the value that you bring to the table for your joint customers. >>Yeah, great question. You know, and, and starting to think about history like you did 2010 being the start of a cube journey. I, I remember in 2003 when we first partnered with VM ware in the very first data center consolidations and we built practices around this has been quite a long partnership with VM ware and I'm excited to see this. This partnership evolved today, especially into this cloud native space and direction. Uh It's critical we need you know uh you know customers have choices and we need great partners like VM ware uh to help satisfy the many different use cases and choices that our customers have. So while we bring you know good depth when it comes to building these infrastructures that become highly automated uh managed in some cases and consumable like on a consumption basis and automated like we help clients automate their ci Cd pipeline. We depend on technologies and partners like them where to make these outcomes real for our customers. >>Yeah I think there's a way to connect a couple of the points that we've been talking about today. Got some data from a state of kubernetes study that we just ran And this is 350. IT. decision makers who said uh that they're running kubernetes on premise, 55% of respondents are running kubernetes on premise today. And so Vm ware and HP gets worked together to bring kubernetes to those enterprises, 96% of them said that they're having a challenge selecting the right kubernetes distribution, 60 of them in that C. N. C. F. Landscape and the # one criteria that they're going to use to choose the right distribution uh set them on a path forward is that it's easy to deploy and to operate and to maintain in production. And so I think that this is where VM ware and HP get to come together to help try and keep things as simple as possible for customers as they navigate. A fairly complex world. >>That's interesting scott. So who are those um those on prem users of containers and kubernetes? Is it the is it the head of you know the the application team and an insurance company whose kind of maintaining the claims about? Is it is a guy's building new cloud native apps to help companies get digital first. Who are those, What's the persona look like >>in our conversations? You know, this is the infrastructure and operations team seen that there's energy around kubernetes and maybe there's some use in test and development and parts of the organization. And by centralizing over ownership of that kubernetes footprint, they can ensure that it's compliant if policy is set properly to your point earlier that it's meets the security standards for the organization. And so it's increasingly that SRE or site reliability engineer or platform operator who's taking ownership of that kubernetes footprint for the organization to ensure that consistency of management and experience for the development teams across the larger organs. Toby, is that what you're seeing? >>2? We see uh we see quite a few we engage with quite a few developer teams in business leads that have ambitions to speed their application development processes And uh you know, they want help and often, as I stated, the intro, they might be coming off of a much older deployment uh maybe from 2015 where there there were an early adopter of a container platform methodology and wanting to get to some newer platform or they they may be in charge of getting a mobile banking application and its features to market much more quickly. So and often when we get a quote maybe from a client and might come from, you know, the VP of a business unit. But often as we engage, it's, you know, the developers are pretty much our customers and their developer leaders and teams, >>so you're running into container technical debt. Already you're seeing that out there. It sounds like your legacy >>container. It takes some expertise to, to come off those older. You know, the first instance creations of these container platforms were pretty much open source and yeah, you want to bring it to something that's more modern and has the kinds of features, enterprise grade features you might need. >>So is it not so problematic for for customers? Because as I said before, a lot of those apps were sort of disposable and stateless and, and, and now they're saying, hey, we can actually use kubernetes to build, you know, mission critical apps. And so there, that's when they sort of decide to pivot to a new modern platform or is there a more complex migration involved? What are you seeing? >>Okay, I'll give my hot, take your Toby and then uh, ask you for yours. But I guess, uh, I feel like the conversations that I'm involved in with customers is, you know, always begins with their broader application portfolio. These enterprises have hundreds thousands of applications and job one is to figure out how to categorize them into those which need to be re hosted or platform or re factored or reimagined entirely. And so they're looking for help figuring out how to categorize those applications and ultimately how to attack each category of application. Some should be re platforms on environments that make best use of kubernetes, some need to be re factored, some need to be reimagined. And so they are again looking for that expert guide to show them the way >>right. And when we engage in those early discussions, we call it right Mix advisory. Um, you know, you're trying to take a full, a broad scope as you said, scott down to a few and uh you know determine kind of the first movers if you will also you know clients will engage you know for very specific applications that are or suite of applications. Again like mobile applications for banking. I think you're a good example because you know they have an ambition. I mean the leader of that kind of application may very well think that is the mission critical application for the company, right? But of course finance, they have a different point of view. So you know that that application to them is the center of their business getting you know, their customer access to the core banking features that they have and you know they want to zero in on the kind of ecosystem it takes in in the speed at which they can push new features through. So we see both as well um you know the broader scope application, weaning down to the few discovery application, uh and then of course a very focused effort to help a particular business unit speed development on their mobile app, for example, >>it's interesting scott you were talking about sort of, the conversation starts with the application portfolio and there have been there have been these sort of milestones around, you know, major application portfolio, I'll call him rationalizations, I mean there's always an ongoing, but y two K was one of those, this is sort of the big move to SAS was another one, obviously cloud and it feels like kubernetes, I mean it's like the cloud to Dato coming on. Prem is another one of those opportunities to rationalize applications. We all know the stats right, we always see 85% of the spend is to keep the lights on and the other the only small portion of innovation and you know, there's always a promise we can change that. It reminds me of the heavy year, I would go to the boston marathon, it was this guy would run and he had a hat on with the extension and it was a can of Budweiser way out there and he couldn't reach it and so he would run. It was almost the same thing here is they never get there because they have so many projects coming online and the project portfolio and and then and then the C I O has got to maintain those in the application heads and so it's this this ongoing thing. But you do see spikes in rationalization initiatives and it feels like with this push to modernization and digitization maybe the pandemic accelerated that too. Is that a reasonable premise? You're seeing sort of a milestone or a marker in terms of increased effort around rationalization and modernization today because of kubernetes? >>Yeah, I definitely think that there are a couple of kubernetes is a catalyzing technology and the challenges of the pandemic or a catalyzing moment. Right. And I feel like uh Organisations have seen over the past 18 months now that those enterprises that have a way to get innovation to market to customers faster, not once a quarter, but many times a day, are the ones that are separating themselves in competitive marketplaces and ultimately delivering superior customer experiences. So it comes back to some of the ideas full circle that Toby started with around delivering a superior developer experience so that those developers can get code to production and into the hands of customers on a much more rapid basis. Like that's the outcome that enterprises really care about at the end of the day. And kubernetes is part of the way to get there, but it's the outcome that's key. Great thank >>you. And one of our practices dave there was uh you know, that's been our bread and butter for so many years. This, you know, this broad based discovery, narrowing down to a strategy and a plan for migrating and moving certain workloads. We see a slight twist today in that clients and organizations want to move quicker too. The apps, they know that, you know, they want to focus on, they want to prove it by through the broad based discovery and kind of a strategic analysis but they want to get quicker right away to the workloads. They are quite sure that need re factoring or leverage the benefit of a modern developer environment. >>Yeah. And they don't want to be messing around with the provisioning, lungs and servers and all that stuff. They want that to be simplified. So we're gonna end on Green Lake and I want to understand how you guys are thinking about Green Lake in terms of your partnership and, and how you're working together, you know, maybe Toby you could sort of give us the update from your perspective, you can't have a conversation with HP today without talking about Green Lake. So give us the kool aid injection. And then I really interested in how VM ware thinks about participating in that. >>Absolutely. And, and thank you for uh, yeah, for helping us out here. You know, I see more and more of our engagements with clients that ask for and, and, and want to sign a Green Life based contract, >>but, >>and that is one very important foundational element. Uh and there's there's so much more because remember we talked about the cloud experience in cloud everywhere and Green Lake brings us an opportunity to bring dimensions to that, especially on the consumption model because that's that's an important element if we begin adding partners such as VM ware to this equation, especially for clients that have huge investments in VM where there's an opportunity here to really bring a lot of value with this cloud experience to our customers through this partnership. >>All right scott, we're gonna give you the last word. What's your take on this? >>Hey listen hard for me to to to add much to what Toby said, he nailed that you see a ton of energy in this space. I think we've covered a bunch of key topics today. Their ongoing conversations with our customers in Green Lake is a way to take that conversation to the next level. >>Guys really appreciate you coming on and give us your perspectives on kubernetes and and and and thank you scott for that data. 55% of I. T. Decision makers out of 350 said they're doing on prem kubernetes. That's a new stat. I hadn't I would have expected to be that high but I guess I'm not surprised it's the rage the developers want the latest and greatest guys. Thanks so much for sharing your knowledge and I appreciate you coming on the cube. >>Thank you. Dave. >>Thanks Dave. >>Thank you for watching the cubes ongoing coverage. Hp es discover 2021. The virtual version will be right back.

>>Please >>welcome back to HP discover 2021 the virtual version. My name is Dave Volonte and you're watching the cube and we're here with Guido appenzeller who's the C. T. O. Of the data platforms group at Intel. Guido. Welcome to the cube. Come on in. >>Thanks. Dave. I appreciate it's great to be here today. So >>I'm interested in your role at the company. Let's talk about that. Your brand new. Tell us a little bit about your background. What attracted you to intel and what's your role here? >>Yeah. So I'm, you know, I grew up in the startup ecosystem of Silicon Valley came from my PhD and and and never left and uh you know, built software companies, worked at software companies worked at the embassy for a little bit and I think my, my initial reaction when the intel recruiter called me, it was like you got the wrong phone number, right? I'm a software guy that's probably not who you're looking for. And uh you know, we had a good conversation I think at Intel, you know, there's a, there's a realization that you need to look at what intel builds more as an overall system from novel systems perspective right, that you have the software stack and then the hardware components that we're getting more and more intricately linked and you know, you need the software to basically bridge across the different hardware components that intel is building. So I'm here now is the CEO for the data platform school. So that builds the data center for Arts here at Intel. And it's a really exciting job. These are exciting times that intel, you know, with, with Pat, you got a fantastic uh you know, CEO at the home, I worked with him before at december, so a lot of things to do. Um but I think a very exciting future. >>Well, I mean the data center is the wheelhouse of intel. I mean of course you, your ascendancy was a function of the pcs and the great volume and how you change that industry. But really data centers is where they, I mean I remember the days of people that until will never be the data center, it's just a toy and of course your dominant player there now. So your initial focus here is is really defining the vision. Uh and and I'd be interested in your thoughts on the future, what the data center looks like in the future, where you see intel playing a role. What what are you seeing is the big trends there. You know, Pat Pat Gelsinger talks about the waves. He says if you don't ride the waves you're gonna end up being driftwood. So what are the waves you're driving? What's different about the data center of the future? >>That's right. You want to surf the waves? Right? That's the way to do it. So look, I like to look at this in sort of in terms of major macro trends. Right? And I think the biggest thing that's happening um in the market right now is the cloud revolution. Right? And I think we're halfway through or something like that and this transition from the classic uh client server type model, uh you know that we're with enterprises running their own data centers to more of a cloud model where something is, you know, run by by hyper scale operators or it may be run you know by uh by an enterprise themselves that message to the absolute there's a variety of different models, but the provisioning models have changed, right? The it's it's much more of a turnkey type service. And when when we started out on this journey, I think the we build data centers the same way that we built them before. Although you know the way to deliver it had really changed. Right? That's going to morph a service model and we're really now starting to see the hardware diverge right there actually. Silicon that we need to build or to address these use cases diverge. And so I think one of the things that is kind of the most interesting for me is really to think through how does intel in the future build silicon? That's that's built for clouds. You know, like on prem clouds. Edge clouds, hyper scale cloud but basically built for these new use cases that have emerged. So >>just kind of quick aside, I mean to me, the definition of cloud is changing. It's evolving. It used to be this set of remote services in a hyper scale data center. It's now, you know, that experience is coming on prem it's connecting across clouds. It's moving out to the edge, it's supporting, you know, all kinds of different workloads. How do you see that? It's evolving Cloud. >>Yeah, I think, I mean, there's the biggest difference to me is that sort of a cloud starts with this idea that the infrastructure operator and the tenant are separate, right? And that is actually has major architectural implications. I mean, just to, you know, this is a perfect analogy, but if I build a single family home, right, where everything is owned by one party, uh you know, I want to be able to walk from the kitchen to the living room pretty quickly, if that makes sense? Right, sorry. In my house here has actually open kitchen, it's the same room essentially. If you're building a hotel where your primary goal is to have guests, you pick a completely different architecture, right? The kitchen from from your restaurants where the cooks are busy preparing the food and the dining room where the guests are sitting there separate. Right? I mean, the hotel staff has a dedicated place to work and the guests have a dedicated places to mingle, but they don't overlap typically. I think it's the same thing with architecture in the clouds. Right? That's you know, initially the assumption was it's all one thing. And now suddenly we're starting to see, you know, like a much much cleaner separation of these different different areas. I think a second major influences that the type of workloads we're seeing. It's just evolving incredibly quickly. Right? I mean, you know, 10 years ago, you know, things were mostly monolithic today. You know, most new workloads are micro service base and that that has a huge impact in uh you know, where where CPU cycles are spent, you know, a way we need to put in accelerators, you know, how we how we build silicon for that too. Give you an idea, I mean there's some really good research out of google and facebook where they run numbers. For example, if you just take a a standard system and you run a micro service based application, written a micro service based architecture, you can spend anywhere from, I want to say 25 in some cases over 80% of your CPU cycles. Just an overhead. Right. And just on marshalling the marshaling the protocols and uh the encryption and decryption of the packets and your service match that sits in between all these things. So I created a huge amount of overhead so for us, 80% go into these, into these overhead functions. Really our focus suddenly needs to be uh how do we enable um, that kind of infrastructure? >>Yeah, So let's talk a little bit more about workloads if we can. I mean the overhead, there's also sort of as the software, as the data center becomes software defined, you know, thanks thanks to your good work at VM where there's a lot of cores that are supporting that software defined data center and then >>that's exactly right as >>well. You mentioned micro services, container based applications, but but as well, you know, aI is coming into play and what it is, you know, a i is this kind of amorphous, but it's really data oriented workloads versus kind of general purpose CRP and finance and HCM So those workloads are exploding and then we can maybe talk about the edge. How are you seeing the workload mix shift and how is intel playing there? >>Look, I think the trend you're talking about is definitely Right, Right. We're getting more and more data centric, you know, shifting the data around becomes a larger and larger part of the overall workload in the data center. Ai is getting a ton of attention. Right? It's look, if I talked to the most operators, aI is still emerging category. Right. I mean, we're seeing, I'd say five, maybe 10% percent of workloads being A. I. Um it's growing the very high value workloads right now, very challenging workloads. Um but you know, it's still a smaller part of the overall mix. Now, Edge edge is big and it's too big. It's big. And it's complicated because of the way I think about edges. It's not just one homogeneous market, it's really a collection of separate sub markets, right? It's very heterogeneous, you know, it runs on a variety of different hardware. All right. It can be everything from, you know, a little a little server that's families that's strapped to a phone, telephone pole with an antenna on top of, you know, to greater micro cell. Or it can be, you know, something that's running inside a car, Right. I mean, you know, uh, modern cars has a small little data center inside, it can be something that runs in the industrial factory floor, right. The network operators, there's a pretty broad range of verticals that all looks slightly different in, in their requirements. And uh, you know, and it's, I think it's really interesting, right? It's one of those areas that really creates opportunities for, for vendors like, like HPV right to, to, to really shine and and address this, this heterogeneity with a, with a broad range of solutions. Very excited to work together with them in that space. >>Yeah, I'm glad you brought HP into the discussion because we're here at HP discover I want to connect them. But so my question is, what's the role of the data center in this, this world of edge? How do you see it? >>Yeah. Look, I think in a sense, what the cloud revolution is doing is that it's showing us a leads to polarisation of a classic data into edge and clout. That makes sense. Right. It's splitting right before this was all mingled a little bit together. If my data centers in my basement anyways, you know what the edge, what's data says the same thing. Right? At the moment I'm moving some workloads in the clouds. I don't even know where they're running anymore than some other workloads that have to have a certain sense of locality. I need to keep closely. Right. And there's some workloads, you just just can't move into the cloud, right? I mean, there's uh if I'm generating a lot of time on the video data that I have to process, it's financially completely unattractive to shift all of that, you know, to, to essential location. I want to do this locally. Right? Will I ever connect my smoke detector with my sprinkler system via the cloud? No, I won't write just for if things go bad, right, they may not work anymore. So I need something that does this locally. So I think as many reasons, you know, why, why you want to keep something on, on premises And I think it's, I think it's a growing market, right? It's very exciting. You know, we're doing some some very good stuff with friends at hp. You know, the they have the pro line dl 1, 10, 10, 10 plus server with our latest third generation z johnson them uh, the open ran, you know, which is the radio access network for the telco space HP Edge Line service. Also, the third generation says it's a really nice products there that I think can really help addressing enterprises carriers, a number of different organizations. You know, these these alleged use cases, Can you >>explain you mentioned open randy rand. So we essentially think of that as kind of the software to find telco. >>Yeah, exactly. It's a software defined cellular. Right. I mean, actually, I learned a lot about that of the recent months, You know, when, when, when I was taking these classes at stanford, you know, these things were still dying down in analogue, Right. That basically a radio signal will be processed in a long way and, and digested. And today, typically the radio signal is immediately digitized and all the processing of the radio signal happens happens digitally and uh, you know, it happens on servers, right? Um, something HP servers and uh, you know, it's, it's a really interesting use case where we're basically now able to do something in a much, much more efficient way by moving it to a digital, more modern platform. And it turns out you can actually visualize these servers and, you know, run a number of different cells inside the same server. Right? It's really complicated because you have to have fantastic real time guarantees, very sophisticated software stack. But it's, it's really fascinating news case. >>You know, a lot of times we have these debates and it may be somewhat academic, but I'd love to get your thoughts on the debate is about, okay, how much data that that is, you know, processed and inferred at the edge is actually gonna come back to the cloud most of the day, is going to stay at the edge. A lot of it's not even gonna be persisted. And the counter to that is so that's sort of the negative for the data center. But the counter that is, they're gonna be so much data. Even a small percentage of all the data that we're going to create is going to create so much more data, you know, back in the cloud, back in the data center. What's your take on that? >>Look? I think there's different applications that are easier to do in certain places. Right? I mean, look, going to a large cloud has a couple of advantages. You have a very complete software ecosystem around you, you know, lots of different services. Um, you have four. If you need very specialized hardware. If I want to run a big learning task where something need 1000 machines. Right. And then this runs for a couple of days and then I don't need to do that for for another month or two. Right. For that is really great. There's on demand infrastructure, right? Having having all this capability up there, uh you know, at the same time it costs money to send the data up there, Right. If I just look at the hardware cost is much, much cheaper to to build myself, you know, in my own data center or in the edge. Um so I think we'll we'll see, you know, customers picking and choosing what they want to do. Where. Right. And and there's a role for both. Right. Absolutely. And so, you know, I think there's there's certain categories, I mean, at the end of the day, um, why do I absolutely need to have something at the edge? And there's a couple of, I think good, good use cases. I mean one is, let me ask you a few phrases, but I think it's three primary reasons. Right? Um, one is simply a bandwidth, Right? What I'm saying? Okay, my my video data, like I have have 100 and four K video cameras, you know, with 60 frames a second feet, there's no way I'm going to move into the cloud. It's just cost prohibitive. I have a hard time getting a line that allows you to do this right. Um, there might be latency, right. If I don't want to reliably react in a very short period of time, I can't do that in the cloud. I need to do this locally with me. Um, I can't even do this in my data center. This has to be very, very closely coupled. And then there's this idea of faith sharing, I think, you know, that if I want to make sure that if things go wrong right, uh, the system is still intact, right. You know, anything that's an emergency kind of backup, emergency type procedure, right? If things go wrong, I can't rely on there'll be a good internet connection, I need to handle things things locally. Like, you know, that's the smoke detector and sprinkler system. Right? And so for for, for all of these, right, there's good reasons why we need to move things close to the edge. So I think there'll be a creative tension between the two, Right? But both are huge markets and I think there's, there's great opportunities for, for hp ahead to uh, you know, to, to work on these two cases. >>Yeah, for sure. Top brand in that compute business. So before we wrap up today, you know, thinking about your, your role, I mean part of your role is the trend spotter. You're right, you gotta, you're, you're kind of driving innovation, riding, surfing the waves as you said, you know, skating to the park, all >>the all my perfect crystal ball right here, Yeah, got all the cliches. >>Right? Yes, yeah. Right foot's a little pressure on you. But so what are some of the things that you're overseeing that you're, you're looking towards in terms of innovation projects, particularly obviously in the data center space, what's really exciting you >>look, I mean there's a lot of them and I pretty much all the, you know, the interesting ideas I get from talking to customers, right? You talk to to the sophisticated customers, you try to understand the problems that are trying to solve that they cancel right now and that that gives you ideas to just to pick a couple. Right? I mean, one thing, what area I'm probably thinking about a lot is how can we built in a sense, better accelerators for the infrastructure functions. Right. So, so no matter if I run an edge cloud or I run a big public cloud, I want to find ways how I can, I can reduce the amount of CPU cycles I I spent on, you know, Microsoft's marshalling the marshaling service mesh, you know, storage acceleration and these things like that. Right? So clearly, if this is a large chunk of the overall uh cycle budget, right? We need to find ways to, to to shrink that right to to make this more efficient. Right? So that I think so this basically infrastructure function acceleration, it sounds probably as unsexy as any topic could sound, but I think this is actually really, really interesting area. One of the big levers we have right now in the data set. >>I would agree. I think that's actually really exciting because you actually can pick up a lot of the wasted cycles now and that's that drops right to the bottom line. But >>exactly. I mean it's you know, it's kind of funny. I mean we're still measuring so much with speck and rates of Cpus right performances like, well, They may actually make measuring the wrong thing, right? If 80% of the cycles of my upper spent an overhead right then the speed of the CPU doesn't matter as much. Right? It's other functions that end. So that's one um the second big one is memory is becoming a bigger and bigger issue. Right? And and it's it's memory cost because you know, memory prices, they used to have declined the same rate that, you know, our core counts and and and you know, Fox speeds increased. That's no longer the case. That we've run to some scaling limits there some physical scaling limits where memory prices are becoming stagnant and this is becoming a major pain point for everybody was building servers. Right. So I think we need to find ways how we can leverage memory more efficiently. Right, share memory more efficiently. We have some really cool ideas and in that space that we're working on. >>Yeah, let me just sorry to interrupt. But Pat hinted to that and your big announcement, I mean you talk about system on package I think is what he used to talk about what I call disaggregated memory and better sharing of that memory resource. And I mean that seems to be a clear benefit of value creation for the industry. >>Exactly, right. I mean, if this becomes a larger for our customers, this becomes a larger part of the overall cost, right? We want to help them address that issue. And you know, and then the third one is um, you know, we're seeing more and more data center operators effectively power limited. Right? So we need to reduce the overall power of systems or, you know, uh maybe to some degree, just figure out better ways of cooling these systems. But I think there's a there's a lot of innovation that can be done their right to both make these data centers more economical, but also to make them a little more green today, data centers have gotten big enough that if you look at the total amount of energy that we're spending in this world is mankind. Right. A chunk of that is going just to data centers. Right. And so if we're spending energy at that scale, right. I think we have to start thinking about how can we build data centers that are more energy officials? I'll do the same thing with less energy in the future. >>Well, thank you for for laying those out. I mean you guys have been long term partners with with HP and now of course H P E. I'm sure Gelsinger's really happy to have you on board Guido. I would be and thanks so much for coming on the cube. >>It's great to be here. Great to be at the HP show. Thanks >>For being with us for HP Discover 2021 the virtual version. You're watching the Cube, the leader in digital tech coverage. Right back.

>>Welcome back to HP discover 2021 My name is Dave Volonte and you're watching the cubes, virtual coverage of H. P. S. Big customer event. Of course, the virtual edition, we're gonna dig into transformations the role of technology in the role of senior technology leadership. Look, let's face it, H P. E. Has gone through a pretty dramatic transformation itself in the past few years. So it makes a great example in case study and with me is rashmi kumari who is the senior vice president and C. I. O. At HP rashmi welcome come on inside the cube. >>Dave Nice to be here. >>Well, it's been almost a year since Covid changed the world as we know it. How would you say the role of the CEO specifically and generally it has changed. I mean you got digital Zero Trust has gone from buzzword to >>mandate >>digital. Everybody was complacent about digital in many ways and now it's really accelerated remote work hybrid. How do you see it? >>Absolutely. As I said in the last discover that Covid has been the biggest reason to accelerate digital transformation in the company's I. C. C. I O. S role has changed tremendously in the last 15 months. It's no more just keep the operations running that's become a table stick. Our roles have become not only to create digital customer experience engaged with our customers in different ways, but also to transform the company operations from inside out to be able to give that digital experience from beginning to end off the customer engagement going forward. We have also become responsible for switching our strategies around the companies as the Covid. Covid hit in different parts of the world at different times and how companies structured their operations to go from one region to another. A global company like H. B had to look into its supply chain differently. Had to look into strategies to mitigate the risk that was created because of the supply chain disruptions as well as you go to taking care of our employees. How do you create this digital collaboration experience where teams can still come together and make the work happen for our end customers? How do we think about future employee engagement when people are not coming into these big buildings and offices and working together, But how to create the same level of collaboration coordination as well as delivery or faster uh goods and services which is enabled by technology going forward. So see I. O. And I. T. S. Role has gone from giving a different level of customer experience to a different level of employee experience as well as enabling day to day operations of the company's. Ceos have realized that digital is the way to go forward. It does not matter what industry you are in and now see a as have their seat at the table to define what the future of every company now, which is a technology company respective you are in oil and gas or mining or a technical product or a card or a mobility company. End of the day you have to act and behave like a technology company. >>So I want to ask you about that because you've you've been a Ceo and uh you know, leading technology provider now for the last three years and you've had previous roles and where you know non technical technology, you know, selling to I. T. Companies and as you point out those worlds are coming together, everybody is a technology company today. How do you think that changes the role of the C. I. O. Because it would always seem to me that there was a difference between A C. I. O. And a tech company. You know what I mean by that? And the C. I. O. It's sort of every other company is those two worlds converging. >>Absolutely. And it's interesting you pointed out that I have worked in many different industries from healthcare and pharma to entertainment to utilities. Um And now at a technology company end of the day um The issues that I. T. Deals with are pretty similar across the organization. What is different here is now my customers are people like me in other industries and I have a little bit of an advantage because just having the experience across various ecosystem. Even at H. B. Look I was fortunate um at H. B. Because of Antonio's leadership, we have topped out mandate to transform how we did business. And I talked about my next gen IT program in last year's cube interview. But at the same time while we were changing our customer partners experience from ordering to order processing to supply chain to finance. Uh We decided this pivot of becoming as a service company. And if you think about that pivot it's pretty common if it was a technology company or non technology company at HP. We were very used to selling a product and coming back three years later at the time of refresh of infrastructure or hardware. That's no more true for us now we are becoming as a service or a subscription company and I. T. Played a major role to enable that quote to cash experience. Which is very different than the traditional experience around how we stay connected with our customer, how we proactively understand their behavior. I always talk about this term. Um Digital exhaust which results into data which can result into better insight and you can not only Upsell cross l because now you have more data about your product usage, but first and the foremost give what your customer wants in a much better way because you can proactively understand their needs and wants because you are providing a digital product versus a physical product. So this is the change that most of the companies are now going through. If you look at Domino's transition, there are pills a sellers but they did better because they had better digital experience. If you look at Chipotle, these are food service companies I. K which is a furniture manufacturer across the board. We have helped our customers and industries to understand how to become a more digital provider. And and remember when uh hp says edge to cloud platform as a service edges the product, the customers who we deal with and how do we get that? Help them get their data to understand how the product is behaving and then get the information to cloud for further analysis. Um and understanding from the data that comes out of the products that gets up, >>I think you've been HP now think around three years and I've been watching of course for decades. Hp. Hp then HP is I feel like it's entering now the sort of third phase of its transformation, your phase one was okay, we gotta figure out how to deal or or operate as a separate companies. Okay. That took some time and then it was okay. Now how do we align our resources and you know, what are the waves that we're gonna ride? And how do we how do we take our human capital, our investments and what bets do we place and and all in on as a service. And now it's like okay how do we deliver on all those promises? So pretty massive transformations. You talked about edge to cloud as a service so you've got this huge pivot in your in your business. What's the technology strategy to support that transformation? >>Yeah that's a that's a great question. So as I mentioned first your second phase which was becoming a stand alone company was the next N. I. T. Program very broad and um S. Four and 60 related ecosystem application. We're even in the traditional business there was a realization that we were 100 20 billion company. We are 30 billion company. We need different types of technologies as well as more integrated across our product line across the globe. And um we I'm very happy to report that we are the last leg of next in I. T. Transformation where we have brought in new customer experience through low touch or not touch order pressing. A very strong as four capabilities. Where we are now able to run all global orders across all our hardware and services business together. And I'm happy to report that we have been able to successfully run through the transformation which a typical company of our size would take five or six years to do in around close to three years. But at the same time while we were building this foundation and the capabilities to be able to do other management, supply chain and data and analytics platforms. We also made the pivot to go to as a service now for as a service and subscription selling. It needs a very different quote to Kazakh cash experience for our customers and that's where we had to bring in um platforms like brim to do um subscription building, convergent charging and a whole different way to address. But we were lucky to have this transformation completed on which we could bolt on this new capability and we had the data and another X platform built which now these as a service products can also use to drive better insight into our customer behavior um as well as how they're using our product a real time for our operations teams. >>Well they say follow the money in the cube. We love to say follow the day to day is obviously a crucial component of competitive advantage business value. So you talk a little bit more about the role of data. I'm interested I'm interested in where I. T. Fits uh you know a lot of companies that have a Chief data officer or Ceo sometimes they're separate. Sometimes they they work you know for each other or Cdo works for C. I. O. How do you guys approach the whole data conversation? >>Yeah that's a that's a great question and has been top of the mind of a lot of C E O C I O S. Chief digital officers in many different companies. The way we have set it up here is do we do have a chief data officer and we do have a head of uh technology and platform and data within I. T. Look. The way I see is that I call the term data torture if we have multiple data lakes, if we have multiple data locations and the data is not coming together at one place at the first time that it comes out of the source system, we end up with data swamps and it's very difficult to drive insights. It's very difficult to have a single version of truth. So HP had two pronged approach. First one was as part of this next gen i. T. Transformation we embarked upon the journey first of all to define our customers and products in a very uniform way across the globe. It's called entity Master Data and Product Master Data Program. These were very very difficult program. We are now happy to report that we can understand the customer from code stage to servicing stage beginning to end across all our system. It's been a tough journey but it was a effort well spent at the same time while we were building this message capability, we also invest the time in our analytics platform because we are generating so much data now globally as one footprint. How do we link our data link to R. S. A. P. And Salesforce and all these systems where our customer data flows through and create analytics and insight from it from our customers or our operations team. At the same time, we also created a chief data officer role where the responsibility is really to drive business from understanding what decision making an analytics they need around product, around customer, around their usage, around their experience to be able to drive better alignment with our customers and products going forward. So this creates efficiencies in the organization. If you have a leader who is taking care of your platforms and data building single source of truth and you have a leader who is propagating this mature notion of handling data as enterprise data and driving that focus on understanding the metrics and the insight that the businesses need to drive better customer alignment. That's when we gain those efficiencies and behind the scenes, the chief data officer and the data leader within my organization worked very, very closely to understand each other needs sometimes out of the possible where do we need the data processing? Is it at the edge? Is it in the cloud? What's the best way to drive the technology and the platform forward? And they kind of rely on each other's knowledge and intelligence to give us give us superior results. And I have done data analytics in many different companies. This model works where you have focused on insight and analytics without because data without insight is of no value, but at the same time you need clean data. You need efficient, fast platforms to process that insight at the functional nonfunctional requirements that are business partners have and that's how we have established in here and we have seen many successes recently. As of now, >>I want to ask you a kind of a harder maybe it's not harder question. It's a weird question around single version of the truth because it's clearly a challenge for organizations and there's many applications workloads that require that single version of the truth. The operational systems, the transaction systems, the HR the salesforce. Clearly you have to have a single version of the truth. I feel like however we're on the cusp of a new era where business lines see an opportunity for whatever their own truth to work with a partner to create some kind of new data product. And it's early days in that. But I want to and maybe not the right question for HP. But I wonder if you see it with in your ecosystems where where it's it's yes, single version of truth is sort of one class of data and analytics gotta have that nail down data quality, everything else. But then there's this sort of artistic version of the data where business people need more freedom. They need more latitude to create. Are you seeing that? And maybe you can help me put that into context. >>Uh, that's a great question. David. I'm glad you asked it. So I think tom Davenport who is known in the data space talks about the offensive and the defensive use cases of leveraging data. I think the piece that you talked about where it's clean, it's pristine, it's quality. It's all that most of those offer the offensive use cases where you are improving company's operations incrementally because you have very clean that I have very good understanding of how my territories are doing, how my customers are doing how my products are doing. How am I meeting my sls or how my financials are looking? There's no room for failure in that area. The other area is though, which works on the same set of data. It's not a different set of data, but the need is more around finding needles in the haystack to come up with new needs, new ones and customers or new business models that we go with. The way we have done it is we do take this data take out what's not allowed for everybody to be seen and then what we call is a private space. But that's this entire data available to our business leader, not real time because the need is not as real time because they're doing more what we call this predictive analytics to be able to leverage the same data set and run their analytics. And we work very closely with business in its we educate them. We tell them how to leverage this data set and use it and gather their feedback to understand what they need in that space to continue to run with their with their analytics. I think as we talk about hindsight insight and foresight hindsight and insight happens more from this clean data lakes where you have authenticity, you have quality and then most of the foresight happens in a different space where the users have more leverage to use data in many different ways to drive analytics and insights which is not readily available. >>Thank you for that. That's interesting discussion. You know digital transformation. It's a journey and it's going to take many years. A lot of ways, not a lot of ways 2020 was a forced March to digital. If you weren't a digital business, you were out of business and you really didn't have much time to plan. So now organizations are stepping back saying, okay let's really lean into our strategy the journey and along the way there's gonna be blind spots, there's bumps in the road when you look out what are the potential disruptions that you see maybe in terms of how companies are currently approaching their digital transformations? That's a great question. >>Dave and I'm going to take a little bit more longer term view on this topic. Right in what's top of my mind um recently is the whole topic of E. S. G. Environmental, social and governance. Most of the companies have governance in place, right? Because they are either public companies or they're under some kind of uh scrutiny from different regulatory bodies or what not. Even if you're a startup, you need to do things with our customers and what not. It has been there for companies. It continues to be there. We the public companies are very good at making sure that we have the right compliance, right privacy, right governance in in in place. Now we'll talk about cyber security. I think that creates a whole new challenge in that governance space. However, we have the set up within our companies to be able to handle that challenge. Now, when we go to social, what happened last year was really important. And now as each and every company, we need to think about what are we doing from our perspective to play our part in that. And not only the bigger companies leaders at our level, I would say that Between last March and this year, I have hired more than 400 people during pandemic, which was all virtual, but me and my team have made sure that we are doing the right thing to drive inclusion and diversity, which is also very big objective for h P E. And Antonio himself has been very active in various round tables in us at the world Economic forum level and I think it's really important for companies to create that opportunity, remove that disparity that's there for the underserved communities. If we want to continue to be successful in this world too, create innovative products and services, we need to sell it to the broader cross section of populations and to be able to do that, we need to bring them in our fold and enable them to create that um, equal consumption capabilities across different sets of people. Hp has taken many initiatives and so are many companies. I feel like uh, The momentum that companies have now created around the topic of equality is very important. I'm also very excited to see that a lot of startups are now coming up to serve that 99% versus just the shiny ones, as you know, in the bay area to create better delivery methods of food or products. Right. The third piece, which is environmental, is extremely important as well as we have seen recently in many companies and where even the dollar or the economic value is flowing are around the companies which are serious about environmental HP recently published its living Progress report. We have been in the forefront of innovation to reduce carbon emissions, we help our customers, um, through those processes. Again, if we do, if our planet is on fire, none of us will exist, right. So we all have to do that every little part to be able to do better. And I'm happy to report, I myself as a person, solar panels, battery electric cars, whatever I can do, but I think something more needs to happen right where as an individual I need to pitch in, but maybe utilities will be so green in the future that I don't need to put panels on my roof, which again creates a different kind of uh waste going forward. So when you ask me about disruptions, I personally feel that successful company like ours have to have E. S. G. Top of their mind and think of products and services from that perspective, which creates equal opportunity for people, which creates better environment sustainability going forward. And, you know, our customers are investors are very interested in seeing what we are doing to be able to serve that cause uh for for bigger cross section of companies, and I'm most of the time very happy to share with my C I. O cohort around how are H. P E F s capabilities creates or feeds into the circular economy, how much e waste we have recycled or kept it off of landfills are green capabilities, How it reduces the evils going forward as well as our sustainability initiatives, which can help other, see IOS to be more um carbon neutral going forward as well. >>You know, that's a great answer, rashmi, thank you for that because I gotta tell you hear a lot of mumbo jumbo about E S G. But that was a very substantive, thoughtful response that I think, I think tech companies in particular are have to lead in our leading in this area. So I really appreciate that sentiment. I want to end with a very important topic which is cyber. It's obviously, you know, escalated in, in the news the last several months. It's always in the news, but You know, 10 or 15 years ago there was this mentality of failure equals fire. Now we realize, hey, they're gonna get in, it's how you handle it. Cyber has become a board level topic, you know? Years ago there was a lot of discussion, oh, you can't have the sec ops team working for the C. I. O. Because that's like the Fox watching the Henhouse, that's changed. Uh it's been a real awakening, a kind of a rude awakening. So the world is now more virtual, you've gotta secure physical uh assets. I mean, any knucklehead can now become a ransomware attack, er they can, they can, they can buy ransomware as a services in the dark, dark web. So that's something we've never seen before. You're seeing supply chains get hacked and self forming malware. I mean, it's a really scary time. So you've got these intellectual assets, it's a top priority for organizations. Are you seeing a convergence of the sea? So roll the C. I. O. Roll the line of business roles relative to sort of prior years in terms of driving security throughout organizations. >>This is a great question. And this was a big discussion at my public board meeting a couple of days ago. It's as as I talk about many topics, if you think digital, if you think data, if you think is you, it's no more one organizations, business, it's now everybody's responsibility. I saw a Wall Street Journal article a couple of days ago where Somebody has compared cyber to 9-11-type scenario that if it happens for a company, that's the level of impact you feel on your on your operations. So, you know, all models are going to change where C so reports to see IO at H P E. We are also into products or security and that's why I see. So is a peer of mine who I worked with very closely who also worked with product teams where we are saving our customers from a lot of pain in this space going forward. And H. B. E. Itself is investing enormous amount of efforts in time in coming out of products which are which are secured and are not vulnerable to these types of attacks. The way I see it is see So role has become extremely critical in every company and the big part of that role is to make people understand that cybersecurity is also everybody's responsibility. That's why in I. T. V. Propagate def sec ups. Um As we talk about it, we are very very careful about picking the right products and services. This is one area where companies cannot shy away from investing. You have to continuously looking at cyber security architecture, you have to continuously look at and understand where the gaps are and how do we switch our product or service that we use from the providers to make sure our companies stay secure The training, not only for individual employees around anti phishing or what does cybersecurity mean, but also to the executive committee and to the board around what cybersecurity means, what zero trust means, but at the same time doing drive ins, we did it for business continuity and disaster recovery. Before now at this time we do it for a ransomware attack and stay prepared as you mentioned. And we all say in tech community, it's always if not when no company can them their chest and say, oh, we are fully secured because something can happen going forward. But what is the readiness for something that can happen? It has to be handled at the same risk level as a pandemic or earthquake or a natural disaster. And assume that it's going to happen and how as a company we will behave when when something like this happen. So I'm here's believer in the framework of uh protect, detect, govern and respond um as these things happen. So we need to have exercises within the company to ensure that everybody is aware of the part that they play day today but at the same time when some event happen and making sure we do very periodic reviews of I. T. And cyber practices across the company. There is no more differentiation between I. T. And O. T. That was 10 years ago. I remember working with different industries where OT was totally out of reach of I. T. And guess what happened? Wanna cry and Petra and XP machines were still running your supply chains and they were not protected. So if it's a technology it needs to be protected. That's the mindset. People need to go with invest in education, training, um awareness of your employees, your management committee, your board and do frequent exercises to understand how to respond when something like this happen. See it's a big responsibility to protect our customer data, our customers operations and we all need to be responsible and accountable to be able to provide all our products and services to our customers when something unforeseen like this happens, >>Russian, very generous with your time. Thank you so much for coming back in the CUBA is great to have you again. >>Thank you. Dave was really nice chatting with you. Thanks >>for being with us for our ongoing coverage of HP discover 21 This is Dave Volonte, you're watching the virtual cube, the leader in digital tech coverage. Be right back. >>Mm hmm, mm.

>>the idea of cloud is changing from a set of remote services somewhere out there in the cloud to an operating model that supports workloads on prem across clouds and increasingly at the near and far edge moreover, workloads are evolving from a predominance of general purpose systems to increasingly data intensive applications, developers are a new breed of innovators and kubernetes is a linchpin of creating new cloud native workloads that are in the cloud but also modernizing existing application portfolios to connect them to cloud native apps. Hello, we want to welcome back to HPD discovered 2021 the cubes ongoing coverage. This is Dave Volonte and with me are scott. Buchanan is the vice president of marketing at VM ware and Toby Weiss, who is the vice president of global hybrid cloud practice at HP gents. Welcome to the Q. Great to see you. Thanks for coming on. >>Thank you. Day agreed to be here. >>Okay, thanks for having >>us. So you heard my little narrative upfront. Um and so let's get into it. I want to start with with some of the key trends that you guys see in the marketplace and maybe scott you could kick us off from VM ware's perspective. What are you seeing that's really driving? Uh I. T. Today. >>Well, Dave you started with a conversation around cloud, right, and you can't really have a conversation around cloud without also talking about applications. And so much of the interaction that we're having with customers these days is about how we bring apps and clouds together and modernize across those two dimensions at the same time. And that's a pretty complex discussion to have and it's a complex journey to navigate. And so we're here to talk to customers and to work with h Pe to help our customers across those two dimensions. >>Great, so Toby I mean, it's always been about applications, as scott said, but but the application, the nature of applications is changing how we develop applications. The mentioned it sort of data intensive applications were injecting ai uh into virtually everything the apps, the process, the people even um uh from a from the perspective of really a company that supports applications with infrastructure, what are you seeing in the marketplace? What can you add to that discussion? >>Yes. Great point. Dave you know, with the scent with applications becoming more central, think about what that means uh and has been for developer communities and developers becoming uh more important customers for I. T. Uh We have to make it easier for these developers uh to speed their innovations to market. Right? The business demands newer and faster capabilities of these applications. So our job in the infrastructure and uh it was called the platform layer is to help we need to build these kinds of platforms that allow developers to innovate more quickly. >>So we talked earlier about sort of modernizing apps. I mean, it seems to me that the starting point there is you want to containerized and obviously kubernetes is the, is the key there, but so okay, so if that's the starting point, where's the journey, what does that look like? Maybe scott you could chime in there >>Sure. A couple of quick thoughts there, dave and Toby to build on first, is if you look at the Cloud Native Computing Foundation Landscape today, which you can do at landscape dot c n c f dot io Holy Smokes, is that a jungle? So a lot of organizations need a guide through that CN cf landscape, they need a partner that they can trust to show them the way through that landscape. And then secondly, there needs to be ways to make these technologies easier to adopt and to use in practice kubernetes being the ultimate example of that. And so we've been hard at work to try and make it easy and natural to make kubernetes Part of 1's existing infrastructure. So that building with and working with containers can be done on the same platform that you're using for virtual machines. >>So let's let's talk a little bit about cloud and how you guys are thinking about cloud. Remember told me that Back in VM World 2010, it was the very first vm world for the Cube. All we talked about was a cloud, but it was a private cloud was really what we were talking about, which at the time largely met the virtualized data center. Um it was kind of before the software defined data center and today we're still talking about cloud, but it's it's hybrid cloud, it's kind of the narrative that I set up front data center. It's become for the most part software to find. And so how do you see this changing the I. T. Operating model? >>I think it's a great question. And and look today you will see us talk a lot about this notion of cloud everywhere. So less differentiation about private and public and more about the experience of cloud. Right public. Cloud brought great innovations and what better than to bring those innovations to on premise workloads that we've chosen to operate and work there. So as we think about cloud more as an experience we want for our developers and our end users and our I. T. Organizations. We begin to think about how can we replicate that experience in an on premise environment. And so part of that is having the technologies that enable you to do that. The other part is um We most of us have evolved alrighty organization operating models to operate our cloud infrastructures off premises. Well now expanding that more holistically across our organization so we don't have to operating models but a single operating model that bridges both and brings the ability of both those together to get the most benefit as we really become to integrate and become truly hybrid in our organization. So I think the operating model is critical and um the kinds of experiences we deliver to the users of that I. T. Uh infrastructure and operating model is critical as well. >>Are you guys are both basically in the infrastructure business scott? Maybe we can start with you there's a lot of changes that we're talking about in it. Generally the data center specifically especially big changes in workloads with a lot more data intensive apps ai being injected into everything Kubernetes, making things more facile. And in many ways it simplifies things, but it also puts stress on the system because you've got to protect this, they're no longer stateless apps right there, state full and you gotta protect them and and so they've got to be compliant. Um Now you've got the edge coming in. Uh So my question is, what does infrastructure have to do to keep pace with all this application innovation? >>Uh One of the conversations that we are having increasingly with our customers is how can they embrace a dev sec ops mindset in their organization and adopt some of these more modern patterns and practices and make sure that security is embedded in the life cycle of the container. And and so, you know, I think that this is part of, the answer is equipping the operator through infrastructure to set guard rails in place so that the development organization can work with freedom inside of those guard rails that it can draw on a catalogs of curated container images, catalogs of apps start from templates. Those are the building blocks that allow developers to work faster and that allow an operator to ensure the integrity and compliance of the containers and the applications that the organizations building. >>Yeah, So, so that's kind of uh when I hear scott talking about that Toby I think infrastructure as code designing security and governance in we always we always said I was an afterthought, we kind of bolted it on second. The security team had to take care of that. This is always the same thing with backup. Right? So we got an app. It's all ready to go. How do we back it up? And so that's changing that whole notion of infrastructure as code. Um, I want to talk about Green lake in a minute, but, but before we get there, I wonder if you could talk about how HP E thinks about VM ware and how you guys are partnering. I'm specifically interested and where each of you sees the value that you bring to the table for your joint customers. >>Yeah, great question. You know, and, and starting to think about history like you did 2010 being the start of a cube journey. I, I remember in 2003 when we first partnered with VM ware in the very first data center consolidations and we built practices around this. It's been quite a long partnership with VM ware and I'm excited to see this. This partnership evolved today, especially into this cloud, native space and direction. Uh, it's critical we need you know uh you know customers have choices and we need great partners like VM ware uh to help satisfy the many different use cases and choices that our customers have. So while we bring you know good depth when it comes to building these infrastructures that become highly automated um and managed in some cases and consume consumable like on a consumption basis and automated like we help clients automate their ci Cd pipeline. We depend on technologies and partners like them where to make these outcomes real for our customers. >>Yeah I think there's a way to connect a couple of the points that we've been talking about today. Got some data from a state of kubernetes study that we just ran and this is 350 I. T. Decision makers who said uh that they're running kubernetes on premise, 55% of respondents are running kubernetes on premise today and so VM ware and HP get to work together to bring kubernetes to those enterprises, 96% of them said that they're having a challenge selecting the right kubernetes distribution, 60 of them in that C. N. C. F. Landscape and the number one criteria that they're going to use to choose the right distribution, you know set them on a path forward is that it's easy to deploy and to operate and to maintain in production. And so I think that this is where the m wear and HP get to come together to help try and keep things as simple as possible for customers as they navigate. A fairly complex world. >>That's interesting scott. So who are those um those on prem users of containers and kubernetes? Is it the is it the head of you know the the application team and an insurance company whose kind of maintaining the claims about? Is it is a guy's building new cloud native apps to help companies get digital first. Who are those? What's the persona look like >>in our conversations? You know, this is the infrastructure and operations team seen that there's energy around kubernetes and maybe there's some use in test and development and parts of the organization. And by centralizing over ownership of that kubernetes footprint, they can ensure that it's compliant if policy is set properly to your point earlier that it's meets the security standards for the organization. And so it's increasingly that SRE or site reliability engineer or platform operator who's taking ownership of that kubernetes footprint for the organization to ensure that consistency of management and experience for the development teams across the larger order Toby, is that what you're seeing? Two, >>yeah, we see uh we see quite a few, we engage with quite a few developer teams in business leads that have ambitions to speed their application development processes And uh you know, they want help and often as I stated, the intro, they might be coming off of a much older deployment uh maybe from 2015 where there there were an early adopter of a container platform methodology and wanting to get to some newer platform or they they may be in charge of getting a mobile banking application and its features to market much more quickly. So, and often when we get a quote maybe from a client, it might come from, you know, the VP of a business unit. But often as we engage, it's, you know, the developers are pretty much our customers and their developer leaders and teams, >>so you're running into container technical debt already. You're seeing that out there. It sounds like your legacy >>container. It takes some expertise to, to come off those older. You know, the first instance creations of these container platforms were pretty much open source. And yeah, you want to bring it to something that's more modern and has the kinds of features, enterprise grade features you might need. >>So is it not so problematic for for customers? Because as I said before, a lot of those apps were sort of disposable and stateless. And, and, and now they're saying, hey, we can actually use kubernetes to build, you know, mission critical apps. And so there, that's when they sort of decide to pivot to a new modern platform or is there a more complex migration involved? What are you seeing? >>Okay, I'll give my hot, take your Toby and then uh, ask you for yours. But I guess I feel like the conversations that I'm involved in with customers is, you know, always begins with their broader application portfolio. These enterprises have hundreds thousands of applications and job one is to figure out how to categorize them into those which need to be re hosted or platforms or re factored or reimagined entirely. And so they're looking for help figuring out how to categorize those applications and ultimately how to attack each category of application. Some should be re platforms on environments that make best use of kubernetes, some need to be re factored, some need to be reimagined. And so they are again looking for that expert guide to show them the way >>right. And when we engage in those early discussions, we call it right Mix advisory. Um, you know, you're trying to take a full of broad scope as he said, scott down to a few and uh you know, determine kind of the first movers if you will also, you know, clients will engage you know, for very specific applications that are or suite of applications. Again like mobile applications for banking I think are a good example because you know they have an ambition. I mean the leader of that kind of application may very well think that is the mission critical application for the company, right? But of course finance, they have a different point of view. So you know that that application to them is the center of their business getting, you know, their customer access to the core banking features that they have and you know, they want to zero in on the kind of ecosystem. It takes in in the speed at which they can push new features through. So we see both as well um you know, the broader scope application, weaning down to the few discovery application, uh and then of course a very focused effort to help a particular business unit speed development on their mobile app, for example, >>it's interesting scott you were talking about sort of the conversation starts with the application portfolio and there have been there have been these sort of milestones around, you know, major application portfolio, I'll call him rationalizations, I mean there's always an ongoing but y two K was one of those, this is sort of the big move to SAS was another one, obviously cloud and it feels like kubernetes, I mean it's like the cloud to Dato coming on Prem is another one of those opportunities to rationalize applications. We all know the stats right, we always see 85% of the spend is to keep the lights on and the other the only small portions innovation and you know, there's always a promise we can change that. It reminds me of the every year I would go to the boston marathon, it was this guy would run and he had a hat on with the extension and it was a can of Budweiser way out there and he couldn't reach it and so he would run, it was almost the same thing here is they never get there because they have so many projects coming online and the project portfolio and and then and then the C I O has got to maintain those in the application heads and so it's this, this ongoing thing but you do see spikes in rationalization initiatives and it feels like with this push to modernization and digitization maybe the pandemic accelerated that too. Is that a reasonable premise? You seeing sort of a milestone or a marker in terms of increased effort around rationalization and modernization today because of kubernetes? >>Yeah, I definitely think that there are a couple of kubernetes is a catalyzing technology and the challenges of the pandemic or a catalyzing moment. Right. And I feel like uh Organisations have seen over the past 18 months now that those enterprises that have a way to get innovation to market to customers faster, not once a quarter, but many times a day are the ones that are separating themselves in competitive marketplaces and ultimately delivering superior customer experiences. So it comes back to some of the ideas full circle that Toby started with around delivering a superior developer experience so that those developers can get code to production and into the hands of customers on a much more rapid basis. Like that's the outcome that enterprises really care about at the end of the day. And kubernetes is part of the way to get there. But it's the outcome that's key. Great, thank >>you. And one of our practices dave there was uh you know, that's been our bread and butter for so many years. This, you know, this broad based discovery, narrowing down to a strategy and a plan for migrating and moving certain workloads. We see a slight twist today in that clients and organizations want to move quicker too. The apps, they know that, you know, they want to focus on, they want to prove it by through the broad based discovery and kind of a strategic analysis, but they want to get quicker right away to the workloads. They are quite sure that need re factoring or leverage the benefit of a modern developer environment >>and they don't want to be messing around with provisioning lungs and servers and all that stuff. They want that to be simplified. So we're gonna end on Green Lake and I want to understand how you guys are thinking about Green Lake in terms of your partnership and how you're working together, you know, maybe Toby you could sort of give us the update from your perspective, you can't have a conversation with HP today without talking about Green Lake. So give us the kool aid injection. And then I really interested in how VM ware thinks about participating in that. >>Absolutely. And, and thank you for uh, yeah, for helping us out here. You know, I see more and more of our engagements with clients that ask for and, and, and want to sign a Green Life based contract, >>but, >>and that is one very important foundational element. Uh and there's there's so much more because remember we talked about the cloud experience in cloud everywhere and Green Lake brings us an opportunity to bring dimensions to that, especially on the consumption model because that's that's an important element if we begin adding partners such as VM ware to this equation, especially for clients that have huge investments in VM where there's an opportunity here to really bring a lot of value with this cloud experience to our customers through this partnership. >>All right scott, we're gonna give you the last word. What's your take on this? >>Hey listen hard for me to to to add much to what Toby said, he nailed that you see a ton of energy in this space. I think we've covered a bunch of key topics today. Their ongoing conversations with our customers in Green Link is a way to take that conversation to the next level. >>Guys really appreciate you coming on and give us your perspectives on kubernetes and and and and thank you scott for that data. 55% of I. T. Decision makers out of 350 said they're doing on prem kubernetes. That's a new stat. I hadn't I would have expected to be that high but I guess I'm not surprised it's the rage the developers want the latest and greatest guys. Thanks so much for sharing your knowledge and I appreciate you coming on the cube. >>Thank you. Dave. >>Thanks Dave. >>Thank you for watching the cubes ongoing coverage. Hp es discover 2021. The virtual version will be right back. >>Mm.

>>mhm Yes, everyone, welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. Got a great segment here. One of the big supporters and open source amazon web services returning back second year. Dr khan virtual Deepak Singh, vice president of the compute services at AWS Deepak, Great to see you. Thanks for coming back on remotely again soon. We'll be in real life. Reinvent is going to be in person, we'll be there. Good to see you. >>Good to see you too, john it's always good to do these. I don't know how how often I've been at the cube now, but it's great every single time your >>legend and getting on there, a lot of important things to discuss your in one of the most important areas in the technology industry right now and that is at the confluence of cloud scale and modern development applications as they shift towards as Andy Jassy says, the new guard, right. It's been happening. You guys have been a big proponent of open source and enabling open source is a service creating business models for companies. But more importantly, you guys are powering, making it easier for folks to use software. And doctor has been a big relationship for you. Could you take a minute to first talk about the doctor, a W S relationship and your involvement and what you're doing? >>Yeah, actually it goes back a long way. Uh you know, Justin, we announced PCS had reinvented 2014 and PCS at that time was very much managed orchestration service on top of DACA at that time. I think it was the first really big one out there from a cloud provider. And since then, of course, the world has evolved quite a bit and relationship with DR has evolved a lot. The thing I'd like to talk to is something that we announced that Dr last year, I don't remember if I talked about it on the cube at that time. But last year we started working with DR on how can we go from doctor Run, which customers love or DR desktop, which customers love and make it easy for people to run containers on pcs and Fergie. Uh so most new customers running containers and AWS today start with this Yes and party or half of them and we wanted to make it very easy for them to start with where they are on the laptop which is often bucket to stop and have running services the native US. So we started working with DR and that that collaboration has been very successful. We want to keep you look forward to continuing to work on evolving that where you can use Docker compose doctor, desktop, doctor run the fuel that darker customers used and the labour grand production services on the end of your side, which is the part that we've got that on. So I think that's one area where we work really well together. Uh, the other area where I think the two companies continue to work well together. It's open source in general as some of, you know, AWS has a very strong commitment to contain a. D uh, EKS our community service is moving towards community. Forget it actually runs all on community today and uh, we collaborate dr Rhonda on the Ocr specification because, you know, the Oc I am expect is becoming the de facto packaging format idea. W S. This morning we launched yesterday, we launched a service called Opera. And the main expected input for opera is an Ocr image are being in this Atlanta as well, where those ci images now a way of packaging for lambda. And I think the last one I like to call out and it has been an amazing partnership and it's an area where most people don't pay attention is amid signing. Uh, there's a project called Notary. We do the second version of the Notary Spec for remit signing and AWS Docker and a couple of other companies have been working very closely together on bringing that uh, you know, finalizing no tv too, so that at least in our case we can start building services for our customers on top of that. You know, it's it's a great relationship and I expect to see it continue. >>Well, I think one of the themes this year is developer experience. So good. Good call out there in the new announcements on the tools you have and software because that seems to be a great developer integration with Docker question I have for you is how should the customers think about things like E C. S and versus E K. S. App, Runner lambda uh for kind of running their containers. How do they understand the difference is, what's there? What's the, what's the thought process there? What's >>that? It's a good question actually been announced after. And I think there was one of the questions I started getting on twitter. You know, let's start at the very beginning. Anyone can pick up a Docker container and run it on easy to today. You can run it on easy to, we can run a light sail, but doc around works just fine. It's the limits machine. Then people want to do more complex things. They want to run large scale orchestrated services. They won't run their entire business and containers. We have customers will do that today. Uh, you know, you have people like Vanguard who runs a significant portion of the infrastructure on pcs frg or you have to elope with the heavy user of chaos, our community service. So in general, if you're running large scale systems, you're building your platforms, you're most likely to use the csny Chaos. Um, if you come from a community's background, you're, you're running communities on prem or you want the flexibility and control the communities gives you, you're gonna end up with the chaos. That's what we see our customers doing. If you just want to run containers, you want to use AWS to its fullest extent where you want the continue a P I to be part of the W A S A P. I said then you pick is yes. And I think one of the reasons you see so many customers start with the CSN, Forget is with forget to get the significant ease of use from an operational standpoint. And we see many start ups and you know, enterprises, especially security focus enterprises leaning towards farming. But there's a class of customers that doesn't want to think about orchestration that just wants. Here's my code, here's my container image just run my service for me and that's when things like happen, I can come and that's one of the reasons we launched it. Land is a little bit different. Lambda is a unique service. You buy into an event driven architecture. If you do that, then you can figure our application into this. That's they should start its magic. Uh, the container part, there is what land announced agreement where they now support containers, packaging. So instead of zip files, you can package up your functions as containers. Then lambda will run them for you. The advantage it gives you with all the tooling that you built, that you have to build your containers now works the land as well. So I won't call and a container orchestration service in the same sense of the CSC cso Afrin are but it definitely allows the container image format as a standard packaging format. I think that's the sort of universal common theme that you find across AWS at this point of time. >>You know, one of the things that we're observing at this at this event here is a lot of developers Coop con and Lennox foundations. A lot of operators to kubernetes hits that. But here's developers. And the thing is I want to ease of use, simplicity experience, but also I want the innovation. Yeah, I want all of it. When I ask you what is amazon bring to the table for the new equation, what would you say? >>Yeah, I mean for me it's always you've probably heard me say this 100 times. Many 1000 times. It's foggy fog. It's unique to us. It takes a lot of what we have learned about operating infrastructure scale. The question we asked ourselves, you know, in many ways we talk about forget even before belong pcs but we have to learn on what it meant and what customers really wanted. But the idea was when you are running clusters of instances of machines to run containers on, you have to start thinking about a lot of things that in some ways VMS but BMS in the car were taken away capacity. What kind of infrastructure to run it on? Should have been touched. Should have not been back. You know, where is my container running? Those are things. They suddenly started having to think about those kind of backwards almost. So the idea was how can we make your containerized bundles? So TCS task or community is part of the thing that you talk to and that is the main unit that you operate on. That is the unit that you get built on and meet it on. That's where Forget comes in and it allows us to do many interesting things. We've effectively changed the engine of forget since we've launched it. Uh, we run it on ec two instances and we run it on fire cracker. Uh, we have changed the forget agent architecture. We've made a lot of underneath the hood, uh, changes that even take the take advantage of the broader innovation, the rate of us, We did a whole bunch more to launch acronym trans on top of family customers don't have to think about it. They don't have to worry about it. It happens underneath the hood. It's always your engine as as you go along and it takes away all the operational pain of managing clusters of running into picking which instances to use to getting out, trying to figure out how to bend back and get efficiency. That becomes our problem. So, you know, that is an area where you should expect to see a Stuart done more. It's becoming the fabric of so many things that eight of us now. Uh, it's, you know, in some ways we're just talking a lot more to do. >>Yeah. And it's a really good time. A lot more wave of developers coming in. One of the things that we've been reporting on on Silicon England cube with our cute videos is more developers keep on coming on, more people coming in and contributing to the open source community. Even end users, not just the normal awesome hyper scholars you're talking about like classic, I call main street enterprises. So two things I want to ask you on the customer side because you have kind of to customers, you have the community that open source community and you have enterprise customers that want to make it easier. What are you seeing and hearing from customers? I know you guys work backwards from the customer. So I got to ask you work backwards from the community and work backwards from the enterprise customer. What's going on in their environment? What's the key trends that they're riding? What's the big challenges? What's the big opportunities that they're facing and saying for the community? >>Yeah, I start with the enterprise. That's almost an easier answer. Which is, you know, we're seeing increasingly enterprises moving into the cloud wholesale. Like in some ways you could argue that the pandemic has just accelerated it, but we have started seeing that before. Uh they want to move to the cloud and adult modern best practices. Uh If you see my talk agreement last few years, I've talked about modernization and all the aspects of modernization, and that's 90% of our conversation with enterprises, I've walked into a meeting supposedly to talk about containers, whatever half a conversation is spent on. How does an organization modernize? What does an organization need to do to modernize and containers and serverless play a pretty important part in it, because it gives them an opportunity to step away from the shackles of sort of fixed infrastructure and the methods and approaches that built in. But equally, we are talking about C I C. D, you know, fully automated deployments. What does it mean for developers to run their own services? What are the child, how do you monitor and uh, instrument uh, your services? How do you do observe ability in the modern world? So those are the challenges that enterprises are going towards, and you're spending a ton of time helping them there. But many of them are still running infrastructure on premises. So, you know, we have outpost for them. Uh, you know, just last week, you're talking to a bunch of our customers and they have lots of interesting ideas and things that they want to do without both, but many of them also have their own infrastructure and that's where something like UCS anywhere came from, which is hey, you like using Pcs in the cloud, You like having the safety i that just orchestrates containers for you. It does it on on his in an AWS region. It will do it in an outpost. It'll do it on wavelength, it'll do it on local zone. How about we allow you to do it on whatever infrastructure you bring to us. Uh you want to bring a raspberry pi, you can do that. You want to bring your on premises data center infrastructure, we can do that or a point of sale device, as long as you can get the agent running and you can connect to an AWS region, even though it's okay to lose connectivity every now and then. We can orchestrate a container for you over there and, you know, the same customer that likes the ease of use of Vcs. And the simplicity really resonated with that message really resonates with them. So I think where we are today with the enterprise is we've got some really good solutions for you in eight of us and we are now allowing you to take those a. P. I. S and then launch containers wherever you want to run them, whether it's the edge or whether it's your own data center. I think that's a big part of where the enterprise is going. But by and large, I think yes, a lot of them are still making that change from running infrastructure and applications the way they used to do a modern sort of, if you want to use the word cloud native way and we're helping them a lot. We've done, the community is interesting. They want to be more participatory. Uh that's where things like co pilot comes from. God, honestly, the best thing we've ever done in my order is probably are open road maps where the community can go into the road map and engage with us over there, whether it's an open source project or just trying to tell us what the feature is and how they would like to see it. It's a great engagement and you know, it's not us a lot. It's helped us prioritize correctly and think about what we want to do next. So yeah, I think that's, that >>must be very hard to do for opening up the kimono on the road map because normally that's the crown jewels and its secretive and you know, and um, now it's all out in the open. I think that is a really interesting, um, experiment and what's your reaction to that? What's been the feedback on the road map peace? Because I mean, I definitely want to see, uh, >>we do it pretty much for every service in my organization and we've been doing it now for three years. So years forget, I think about three years and it's been great. Now we are very we are very upfront, which is security and availability. Our job 000 and you know, 100 times out of 100 at altitudes between a new feature and helping our customers be available and safe. We'll do that. And this is why we don't put dates in that we just tell you directionally where we are and what we are prioritizing Uh, there every now and then we'll put something in there that, you know, well not choose not to put a feature in there because we want to keep it secret until it launches. But for the most part, 99% of our own myself there and people engaged with it. And it's not proven to be a problem because you've also been very responsible with how we manage and be very transparent on whether we can commit to something or not. And I think that's not. >>I gotta ask you on as a leader uh threaded leader on this group. Open source is super important, as you know, and you continue to do it from under years. How are you investing in the future? What's your plan? Uh plans for your team, the industry actually very inclusive, Which is very cool. It's gonna resonate well, what's the plans? Give us some details on what you're investing in, what your priorities? What's your first principles? >>Yeah, So it goes in many ways, one when I I also have the luxury also on the amazon open source program office. So, you know, I get the chance to my team, rather not me help amazon engineers participate in open source. That that's the team that helps create the tools for them, makes it easy for them to contribute, creates, you know, manages all the licenses, etcetera. I'll give you a simple example, you know, in there, just think of the cr credential helper that was written by one of our engineers and he kind of distorted because he felt it was something that we needed to do. And we made it open source in general, in in many of our teams. The first question we asked is should something the open why is this thing not open source, especially if it's a utility or some piece of software that runs along with services. So they'll step one. But we've done some big things also, I, you know, a couple of years ago we launched Lennox operating system called bottle Rocket. And right from the beginning it was very clear to us that bottle Rocket was two things. It was both in AWS product. But first it was an open source project. We've already learned a little bit from what we've done at Firecracker. But making bottle rocket and open source operating system is very important. Anyone can take part of Rocket the open source to build tooling. You can run it whatever you want. If you want to take part of Rocket and build a version and manage it for another provider. For another provider wants to do it, go for it. There's nothing stopping you from doing that. So you'll see us do a lot there. Obviously there's multiple areas. You've seen WS investing on the open source side. But to me, the winds come from when engineers can participate in small things, released little helpers or get contributions from outside. I think that's where we're still, we can always have that. We're going to continue to strive to make it better and easier. And uh, you know, I said, I have, you know, me and my team, we have an opportunity to help their inside the company and we continue to do so. But that's what gets me excited. >>Yeah, that's great stuff. And congratulations on investing in the community, really enjoys it and I know it moves the needle for the industry. Deepak, I gotta ask you why I got you here. Dr khan obviously, developers, what's the most important story that they should be paying attention to as a developer because of what's going on shift left for security day two operations also known as a I ops getups, whatever you wanna call it, you know, ongoing, you get server lists, you got land. I mean, all kinds of great things are going on. You mentioned Fargate, >>um >>what should they be paying attention to that's going to really help their life, both innovation wise and just the quality of life. >>Yeah, I would say look at, you know, in the end it is very easy developers in particular, I want to build the buildings and it's very easy to get tempted to try and get learn everything about something. You have access to all the bells and whistles and knobs, but in reality, if you want to run things you want to, you want to focus on what's important, the business application, that and you the application. And I think a lot of what I'll tell developers and I think it's a lot of where the industry is going is we have built a really solid foundation, whether it's humanity, so you CSN forget or you know, continue industries out there. We have very solid foundation that, you know, our customers and develop a goal of the world can use to build upon. But increasingly, and you know, they are going to provide tools that sort of take that wrap them up and providing a nice package solution After another great example, our collaboration, the doctor around Dr desktop are a great example where we get all the mark focus on the application and build on top of that and you can get so much done. I think that's one trend. You'll see more and more. Those things are no longer toys, their production grade systems that you can build real world applications on, even though they're so easy to use. The second thing I would add to that is uh, get uh, it is, you know, you can give it whatever name you want. There's uh, there's nuances there, but I actually think get up is the way people should be running the infrastructure, my virus in my personal, you know, it's something that we believe a lot in homicide as hard as you go towards immutable infrastructure, infrastructure, automation, we can get off plays a significant role. I think developers naturally gravitate towards it. And if you want to live in a world where development and operations are tightly linked, I think it after the huge role to play in that it's actually a big part of how we're planning to do things like yes, anywhere, for example, a significant player and that it would be a proton. I think get up will be a significant in the future of proton as well. So I think that's the other trend. If you wanted to pick a trend that people should pay attention. That's what I believe in a lot. >>Well you're an expert. So I want to get you a quick definition. What is get Ops, how would you define it? Because that's a big trend. What does it, what does that mean? >>Electricity will probably shoot me for getting this wrong. I tell you how I think about it. Which is, you know, in many cases, um, you when you're doing deployments are pushing a deployment getups is more of a full deployment. When you are pushing code to get depository, you have a system that knows that the event has happened and then pulls from there and triggers the thing as opposed to you telling it take I have this new piece of code now go deployed everywhere. So to me, the biggest changes that Two parts one is it's more for full mechanism where you're pulling because something has changed. So it needs systems like container orchestrators to keep them, you know, to keep them in sync. And the second part of the natural natural evolution of infrastructure score, which is basically everything is called the figures code. Infrastructure as code, code is code and everything is getting stored in that software repo and the software repo becomes your store of record and drives everything. Uh So for a glass of customers, that's going to be a pretty big deal. >>Yeah, when you're checking in code, that's again, it's like a compiler for the compiler, a container for the container, you've got things for each other. Automation is ultimately what we're talking about here. And that's to me where machine learning kicks in. So again, having this open source foundational fabric, as you said, forget out the muck or the undifferentiated heavy lifting. This is what we're talking about automation, isn't it? Deepak? >>Yes. I mean I said uh one thing where we hang our hat on is there's such good stuff out there in the world which we like to contribute to, but the thing we like to hang our hat on is how do you run this? How do you do it this in ways that you can uniquely bring capabilities to customers where there's things like nitro or things are nitro open stuff. Well, the fact that we have built up this operational infrastructure over the last in a decade plus or in the container space over the last seven years where we really really know how to run these things at scale and have made all the investments to make it easy to do. So that's that's where we have hanger hard keeping people safe, helping them only available applications, their new startup, that just completely takes off in over the weekend. For whatever reason, because, you know, you're the next hot thing on twitter and our goal is to support you whether you are, you know, uh enterprise that's moving from the main train or you are the next hot startup, that's you know, growing virally and uh, you know, we've done a lot to build systems help both sides and yeah, it's >>interesting if you sing about open source where it's come from, I mean I remember that base wouldn't open source wasn't open, I would be peddling software, there's a free copy of Linux, UNIX um in college and now it's all free. But I mean just what's changed now. It used to be just free software, download software. You got it now, it's a service. Service now can be monetized quickly. And what you guys are offering with AWS and cloud scale is you've done all these things as I don't have to have a developer. I get the benefits of the scale, I can bring my open source code to the table, make it a service integrated in with other services and be the next snowflake, be the next, you know, a company that could scale. And that is that's the that's the innovation, right? That's the this is a new phenomenon. So it also changes the business model. >>Yeah, actually you're you're quite right. Actually, I I like one more thing to it. But you look at how a lot of enterprises use containers today. Most of them are using something like this year, Symphony or GS to build an internal developer platform and internal developer portal. And then the question then becomes this hard to scale this modern and development practices to an entire organization. What is your big bank that's been around as thousands and thousands of ID stuff That may not all be experts are running communities running container is when you scale it out different systems that proton come into play. That was actually the inspiration is how do you help an organization where they're building these developer Portholes and developer infrastructure, developer platforms, How do you make it easy for them to build it? Be almost use it as a way to get these modern practices into the hands of all the business units, where they may not have the time to become experts at the modern ways of running infrastructure because they're busy doing other things. And I think you'll see the a lot more happening that space that's not happening in the open source community. There's proton, there's a bunch of interesting things happening here and be interesting to see how that evolves. >>And also, you know, the communal, communal aspect of not just writing code together, but succeeding, right, building something. I mean, that's when you start to see the commercial meets open kind of ethos of communal activity of working together and sharing a big part of this year's. Dakar Con is sharing not just running and shipping code but sharing. >>Yeah, I mean if you think about it uh Dockers original value was you build run and shit right? You use the same code to build it, you use the same code to ship it, the same sort of infrastructure interface and then you run it and that, you know, the fact that the doctor images such a wonderfully shareable entity uh that can run every girl is such a powerful and it's called the Ci Image. Now I still call him Dr images because it's just easier. But that to me like that is a big deal and I think it's becoming and become an even bigger deal over the years. I came from something before, Amazon has to work in The sciences and bioinformatics and you know, the ability to share codeshare dependencies, package all of that up in a container image is a big deal. It's what got me one of the reasons I got fascinated with container 78 years ago. So it will be interesting to see where all of systems. >>It's great, great stuff. Great success. And congratulations. Deepak, Great to always talk to you got a great finger on the pulse. You lead a really important organizations at AWS and you know, doctor has such a huge success with developers, even though the company has gone through kind of a uh change over and a pivot to what they're doing now. They're back to their open source roots, but they have millions and millions of developers use Docker and new developers are coming in dot net developers are coming in. Windows developers are coming in and and so it's no longer about Lennox anymore. It's about just coding. >>Yeah. And it's it's part of this big trend towards infrastructure, automation and and you know development and deployment practices that I think everyone is going to adopt faster than we think they will. But you know, companies like Doctor and opens those projects that they involved are critical in making that a lot easier for them. And then you know, folks like us get to build on top of that orbit them and make it even easier. >>Well, great testimony the doctor that you guys based your E C. S on Docker Doctor has a critical role in developing community. I run composed in their hub with dr desktop and we'll be watching amazon and and the community activity and see what kind of experiences you guys can bring to the table and continue that momentum. Thank you Deepak for coming on the >>cube. Thank you, john. That's always a pleasure. >>Okay. Mr cubes. Dr khan 2021 virtual coverage. I'm john for your host of the cube. Thanks for watching.

>>mhm, mm. All right. Mhm. Mhm, mm mm. Mhm. Yeah, mm. Mhm. Yeah, yeah. Mhm, mm. Okay. Mm. Yeah, Yeah. >>Mhm. Mhm. Yeah. Welcome to future cloud made possible by Cisco. My name is Dave Volonte and I'm your host. You know, the cloud is evolving like the universe is expanding at an accelerated pace. No longer is the cloud. Just a remote set of services, you know, somewhere up there. No, the cloud, it's extending to on premises. Data centers are reaching into the cloud through adjacent locations. Clouds are being connected together to each other and eventually they're gonna stretch to the edge and the far edge workloads, location latency, local laws and economics will define the value customers can extract from this new cloud model which unifies the operating experience independent of location. Cloud is moving rapidly from a spare capacity slash infrastructure resource to a platform for application innovation. Now, the challenge is how to make this new cloud simple, secure, agile and programmable. Oh and it has to be cloud agnostic. Now, the real opportunity for customers is to tap into a layer across clouds and data centers that abstracts the underlying complexity of the respective clouds and locations. And it's got to accommodate both mission critical workloads as well as general purpose applications across the spectrum cost, effectively enabling simplicity with minimal labor costs requires infrastructure i. E. Hardware, software, tooling, machine intelligence, AI and partnerships within an ecosystem. It's kind of accommodate a variety of application deployment models like serverless and containers and support for traditional work on VMS. By the way, it also requires a roadmap that will take us well into the next decade because the next 10 years they will not be like the last So why are we here? Well, the cube is covering Cisco's announcements today that connect next generation compute shared memory, intelligent networking and storage resource pools, bringing automation, visibility, application assurance and security to this new decentralized cloud. Now, of course in today's world you wouldn't be considered modern without supporting containers ai and operational tooling that is demanded by forward thinking practitioners. So sit back and enjoy the cubes, special coverage of Cisco's future cloud >>From around the globe. It's the Cube presenting future cloud one event, a world of opportunities brought to you by Cisco. >>We're here with Dejoy Pandey, a VP of emerging tech and incubation at Cisco. V. Joy. Good to see you. Welcome. >>Good to see you as well. Thank you Dave and pleasure to be here. >>So in 2020 we kind of had to redefine the notion of agility when it came to digital business or you know organizations, they had to rethink their concept of agility and business resilience. What are you seeing in terms of how companies are thinking about their operations in this sort of new abnormal context? >>Yeah, I think that's a great question. I think what what we're seeing is that pretty much the application is the center of the universe. And if you think about it, the application is actually driving brand recognition and the brand experience and the brand value. So the example I like to give is think about a banking app uh recovered that did everything that you would expect it to do. But if you wanted to withdraw cash from your bank you would actually have to go to the ATM and punch in some numbers and then look at your screen and go through a process and then finally withdraw cash. Think about what that would have, what what that would do in a post pandemic era where people are trying to go contact less. And so in a situation like this, the digitization efforts that all of these companies are going through and and the modernization of the automation is what is driving brand recognition, brand trust and brand experience. >>Yeah. So I was gonna ask you when I heard you say that, I was gonna say well, but hasn't it always been about the application, but it's different now, isn't it? So I wonder if you talk more about how the application is experience is changing. Yes. As a result of this new digital mandate. But how should organizations think about optimizing those experiences in this new world? >>Absolutely. And I think, yes, it's always been about the application, but it's becoming the center of the universe right now because all interactions with customers and consumers and even businesses are happening through that application. So if the application is unreliable or if the application is not available is untrusted insecure, uh, there's a problem. There's a problem with the brand, with the company and the trust that consumers and customers have with our company. So if you think about an application developer, the weight he or she is carrying on their shoulders is tremendous because you're thinking about rolling features quickly to be competitive. That's the only way to be competitive in this world. You need to think about availability and resiliency. Like you pointed out and experience, you need to think about security and trust. Am I as a customer or consumer willing to put my data in that application? So velocity, availability, Security and trust and all of that depends on the developer. So the experience, the security, the trust, the feature, velocity is what is driving the brand experience now. >>So are those two tensions that say agility and trust, you know, Zero Trust used to be a buzzword now it's a mandate. But are those two vectors counter posed? Can they be merged into one and not affect each other? Does the question makes sense? Right? Security usually handcuffs my speed. But how do you address that? >>Yeah that's a great question. And I think if you think about it today that's the way things are. And if you think about this developer all they want to do is run fast because they want to build those features out and they're going to pick and choose a piece and services that matter to them and build up their app and they want the complexities of the infrastructure and security and trust to be handled by somebody else is not that they don't care about it but they want that abstraction so that is handled by somebody else. And typically within an organization we've seen in the past where this friction between Netapp Sec ops I. T. Tops and and the cloud platform Teams and the developer on one side and these these frictions and these meetings and toil actually take a toll on the developer and that's why companies and apps and developers are not as agile as they would like to be. So I think but it doesn't have to be that way. So I think if there was something that would allow a developer to pick and choose, discover the apis that they would like to use connect those api is in a very simple manner and then be able to scale them out and be able to secure them and in fact not just secure them during the run time when it's deployed. We're right off the back when the fire up that I'd and start developing the application. Wouldn't that be nice? And as you do that, there is a smooth transition between that discovery connectivity and ease of consumption and security with the idea cops. Netapp psych ops teams and see source to ensure that they are not doing something that the organization won't allow them to do in a very seamless manner. >>I want to go back and talk about security but I want to add another complexity before we do that. So for a lot of organizations in the public cloud became a staple of keeping the lights on during the pandemic but it brings new complexities and differences in terms of latency security, which I want to come back to deployment models etcetera. So what are some of the specific networking challenges that you've seen with the cloud native architecture is how are you addressing those? >>Yeah. In fact, if you think about cloud, to me that is a that is a different way of seeing a distributed system. And if you think about a distributed system, what is at the center of the distributed system is the network. So my my favorite comment here is that the network is the wrong time for all distribute systems and modern applications. And that is true because if you think about where things are today, like you said, there's there's cloud assets that a developer might use in the banking example that I gave earlier. I mean if you want to build a contact less app so that you get verified, a customer gets verified on the app. They walk over to the ATM and they were broadcast without touching that ATM. In that kind of an example, you're touching the mobile Rus, let's say U S A P is you're touching cloud API is where the back end might sit. You're touching on primary PS maybe it's an oracle database or a mainframe even where transactional data exists. You're touching branch pipes were the team actually exists and the need for consistency when you withdraw cash and you're carrying all of this and in fact there might be customer data sitting in salesforce somewhere. So it's cloud API is a song premise branch. It's ass is mobile and you need to bring all of these things together and over time you will see more and more of these API is coming from various as providers. So it's not just cloud providers but saas providers that the developer has to use. And so this complexity is very, very real. And this complexity is across the wide open internet. So the application is built across this wide open internet. So the problems of discovery ability, the problems of being able to simply connect these apis and manage the data flow across these apis. The problems of consistency of policy and consumption because all of these areas have their own nuances and what they mean, what the arguments mean and what the A. P. I. Actually means. How do you make it consistent and easy for the developer? That is the networking problem. And that is a problem of building out this network, making traffic engineering easy, making policy easy, making scale out, scale down easy, all of that our networking problems. And so we are solving those problems uh Francisco. >>Yeah the internet is the new private network but it's not so private. So I want to go back to security. I often say that the security model of building a moat, you dig the moat, you get the hardened castle that's just outdated now that the queen is left her castle, I always say it's dangerous out there. And the point is you touched on this, it's it's a huge decentralized system and with distributed apps and data, that notion of perimeter security, it's just no longer valid. So I wonder if you could talk more about how you're thinking about this problem and you definitely address some of that in your earlier comments. But what are you specifically doing to address this and how do you see it evolving? >>Yeah, I mean, that's that's a very important point. I mean, I think if you think about again the wide open internet being the wrong time for all modern applications, what is perimeter security in this uh in this new world? I mean, it's to me it boils down to securing an API because again, going with that running example of this contact lists cash withdrawal feature for a bank, the ap wherever it's it's entre branch SAs cloud, IOS android doesn't matter that FBI is your new security perimeter. And the data object that is trying to access is also the new security perimeter. So if you can secure ap to ap communication and P two data object communication, you should be good. So that is the new frontier. But guess what software is buggy? Everybody's software not saying Cisco software, everybody's Softwares buggy. Uh software is buggy, humans are not reliable and so things mature, things change, things evolve over time. So there needs to be defense in depth. So you need to secure at the API layer had the data object layer, but you also need to secure at every layer below it so that you have good defense and depth if any layer in between is not working out properly. So for us that means ensuring ap to ap communication, not just during long time when the app has been deployed and is running, but during deployment and also during the development life cycle. So as soon as the developer launches an ID, they should be able to figure out that this api is security uses reputable, it has compliant, it is compliant to my to my organization's needs because it is hosted, let's say from Germany and my organization wants appears to be used only if they are being hosted out of Germany so compliance needs and and security needs and reputation. Is it available all the time? Is it secure? And being able to provide that feedback all the time between the security teams and the developer teams in a very seamless real time manner. Yes, again, that's something that we're trying to solve through some of the services that we're trying to produce in san Francisco. >>Yeah, I mean those that layered approach that you're talking about is critical because every layer has, you know, some vulnerability. And so you you've got to protect that with some depth in terms of thinking about security, how should we think about where where Cisco's primary value add is, I mean as parts of the interview has a great security business is growing business, Is it your intention to to to to add value across the entire value chain? I mean obviously you can't do everything so you've got a partner but so has the we think about Cisco's role over the next I'm thinking longer term over the over the next decade. >>Yeah, I mean I think so, we do come in with good strength from the runtime side of the house. So if you think about the security aspects that we haven't played today, uh there's a significant set of assets that we have around user security around around uh with with do and password less. We have significant assets in runtime security. I mean, the entire portfolio that Cisco brings to the table is around one time security, the secure X aspects around posture and policy that will bring to the table. And as you see, Cisco evolve over time, you will see us shifting left. I mean, I know it's an overused term, but that is where security is moving towards. And so that is where api security and data security are moving towards. So learning what we have during runtime because again, runtime is where you learn what's available and that's where you can apply all of the M. L. And I models to figure out what works what doesn't taking those learnings, Taking those catalogs, taking that reputation database and moving it into the deployment and development life cycle and making sure that that's part of that entire they have to deploy to runtime chain is what you will see. Cisco do overtime. >>That's fantastic phenomenal perspective video. Thanks for coming on the cube. Great to have you and look forward to having you again. >>Absolutely. Thank you >>in a moment. We'll talk hybrid cloud applications operations and potential gaps that need to be addressed with costume, Das and VJ Venugopal. You're watching the cube the global leader in high tech coverage. Mhm >>You were cloud. It isn't just a cloud. It's everything flowing through it. It's alive. Yeah, connecting users, applications, data and devices and whether it's cloud, native hybrid or multi cloud, it's more distributed than ever. One company takes you inside, giving you the visibility and the insight you need to take action. >>One company >>has the vision to understand it, all the experience, to securely connect at all on any platform in any environment. So you can work wherever work takes you in a cloud first world between your cloud and being cloud smart, there's a bridge. Cisco the bridge to possible. >>Okay. We're here with costume does, who is the Senior Vice President, General Manager of Cloud and compute at Cisco. And VJ Venugopal, who is the Senior Director for Product Management for cloud compute at Cisco. KTV. J. Good to see you guys welcome. >>Great to see you. Dave to be here. >>Katie, let's talk about cloud you And I last time we're face to face was in Barcelona where we love talking about cloud and I always say to people look, Cisco is not a hyper Scaler, but the big public cloud players, they're like giving you a gift. They spent almost actually over $100 billion last year on Capex. The big four. So you can build on that infrastructure. Cisco is all about hybrid cloud. So help us understand the strategy. There may be how you can leverage that build out and importantly what a customer is telling you they want out of hybrid cloud. >>Yeah, no that's that's that's a perfect question to start with. Dave. So yes. So the hybrid hyper scholars have invested heavily building out their assets. There's a great lot of innovation coming from that space. Um There's also a great innovation set of innovation coming from open source and and that's another source of uh a gift. In fact the I. T. Community. But when I look at my customers they're saying well how do I in the context of my business implement a strategy that takes into consideration everything that I have to manage um in terms of my contemporary work clothes, in terms of my legacy, in terms of everything my developer community wants to do on DEVOPS and really harnessed that innovation that's built in the public cloud, that built an open source that built internally to me, and that naturally leads them down the path of a hybrid cloud strategy. And Siskel's mission is to provide for that imperative, the simplest more power, more powerful platform to deliver hybrid cloud and that platform. Uh It's inter site we've been investing in. Inner side, it's a it's a SAS um service um inner side delivers to them that bridge between their estates of today that were closer today, the need for them to be guardians of enterprise grade resiliency with the agility uh that's needed for the future. The embracing of cloud. Native of new paradigms of deVOPS models, the embracing of innovation coming from public cloud and an open source and bridging those two is what inner side has been doing. That's kind of that's kind of the crux of our strategy. Of course we have the entire portfolio behind it to support any, any version of that, whether that is on prem in the cloud, hybrid, cloud, multi cloud and so forth. >>But but if I understand it correctly from what I heard earlier today, the inter site is really a linchpin of that strategy, is it not? >>It really is and may take a second to totally familiarize those who don't know inner side with what it is. We started building this platform quite a few years back and we we built a ground up to be an immensely scalable SAs, super simple hybrid cloud platform and it's a platform that provides a slew of service is inherently and then on top of that there are suites of services, the sweets of services that are tied to infrastructure, automation. Cisco, as well as Cisco partners. The streets of services that have nothing to do with Cisco um products from a hardware perspective. And it's got to do with more cloud orchestration and cloud native and inner side and its suite of services um continue to kind of increase in pace and velocity of delivery video. Just over the last two quarters we've announced a whole number of things will go a little bit deeper into some of those but they span everything from infrastructure automation to kubernetes and delivering community than service to workload optimization and having visibility into your cloud estate. How much it's costing into your on premise state into your work clothes and how they're performing. It's got integrations with other tooling with both Cisco Abdi uh as well as non Cisco um, assets and then and then it's got a whole slew of capabilities around orchestration because at the end of the day, the job of it is to deliver something that works and works at scale that you can monitor and make sure is resilient and that includes that. That includes a workflow and ability to say, you know, do this and do this and do this. Or it includes other ways of automation, like infrastructure as code and so forth. So it includes self service that so that expand that. But inside the world's simplest hybrid cloud platform, rapidly evolving rapidly delivering new services. And uh we'll talk about some more of those day. >>Great, thank you, Katie VJ. Let's bring you into the discussion. You guys recently made an announcement with the ASCIi corp. I was stoked because even though it seemed like a long time ago, pre covid, I mean in my predictions post, I said, ha, she was a name to watch our data partners. Et are you look at the survey data and they really have become mainstream? You know, particularly we think very important in the whole multi cloud discussion. And as well, they're attractive to customers. They have open source offerings. You can very easily experiment. Smaller organizations can take advantage. But if you want to upgrade to enterprise features like clustering or whatever, you can plug right in. Not a big complicated migration. So a very, very compelling story there. Why is this important? Why is this partnership important to Cisco's customers? Mhm. >>Absolutely. When the spot on every single thing that you said, let me just start by paraphrasing what ambition statement is in the cloud and computer group. Right ambition statement is to enable a cloud operating model for hybrid cloud. And what we mean by that is the ability to have extreme amounts of automation orchestration and observe ability across your hybrid cloud idea operations now. Uh So developers and applications team get a great amount of agility in public clouds and we're on a mission to bring that kind of agility and automation to the private cloud and to the data centers and inter site is a quickie platform and lynchpin to enable that kind of operations. Uh, Cloud like operations in the in the private clouds and the key uh As you rightly said, harsher car is the, you know, they were the inventors of the concept of infrastructure at school and in terra form, they have the world's number one infrastructure as code platform. So it became a natural partnership for Cisco to enter into a technology partnership with harsher card to integrate inter site with hardship cops, terra form to bring the benefits of infrastructure as code to the to hybrid cloud operations. And we've entered into a very tight integration and uh partnership where we allow developers devops teams and infrastructure or administrators to allow the use of infrastructure as code in a SAS delivered manner for both public and private club. So it's a very unique partnership and a unique integration that allows the benefits of cloud managed i E C. To be delivered to hybrid cloud operations. And we've been very happy and proud to be partnering with Russian government shutdown. >>Yeah, Terra form gets very high marks from customers. The a lot of value there. The inner side integration adds to that value. Let's stay on cloud native for a minute. We all talk about cloud native cady was sort of mentioning before you got the the core apps, uh you want to protect those, make sure their enterprise create but they gotta be cool as well for developers. You're connecting to other apps in the cloud or wherever. How are you guys thinking about this? Cloud native trend? What other movies are you making in this regard? >>I mean cloud native is there is one of the paramount I. D. Trends of today and we're seeing massive amounts of adoption of cloud native architecture in all modern applications. Now, Cloud Native has become synonymous with kubernetes these days and communities has emerged as a de facto cloud native platform for modern cloud native app development. Now, what Cisco has done is we have created a brand new SAs delivered kubernetes service that is integrated with inter site, we call it the inter site community service for A. Ks. And this just geared a little over one month ago. Now, what interstate kubernetes service does is it delivers a cloud managed and cloud delivered kubernetes service that can be deployed on any supported target infrastructure. It could be a Cisco infrastructure, it could be a third party infrastructure or it could even be public club. But think of it as kubernetes anywhere delivered as says, managed from inside. It's a very powerful capability that we've just released into inter site to enable the power of communities and clog native to be used to be used anywhere. But today we made a very important aspect because we are today announced the brand new Cisco service mess manager, the Cisco service mesh manager, which is available as an extension to the KS are doing decide basically we see service measures as being the future of networking right in the past we had layer to networking and layer three networking and now with service measures, application networking and layer seven networking is the next frontier of, of networking. But you need to think about networking for the application age very differently how it is managed, how it is deployed. It needs to be ready, developer friendly and developer centric. And so what we've done is we've built out an application networking strategy and built out the service match manager as a very simple way to deliver application networking through the consumers, like like developers and application teams. This is built on an acquisition that Cisco made recently of Banzai Cloud and we've taken the assets of Banzai Cloud and deliver the Cisco service mesh manager as an extension to KS. That brings the promise of future networking and modern networking to application and development gives >>God thank you. BJ. And so Katie, let's let's let's wrap this up. I mean, there was a lot in this announcement today, a lot of themes around openness, heterogeneity and a lot of functionality and value. Give us your final thoughts. >>Absolutely. So, couple of things to close on, first of all, um Inner side is the simplest, most powerful hybrid cloud platform out there. It enables that that cloud operating model that VJ talked about, but enables that across cloud. So it's sad, it's relatively easy to get into it and give it a spin so that I'd highly encouraged anybody who's not familiar with it to try it out and anybody who is familiar with it to look at it again, because they're probably services in there that you didn't notice or didn't know last time you looked at it because we're moving so fast. So that's the first thing. The second thing I close with is um, we've been talking about this bridge that's kind of bridging, bridging uh your your on prem your open source, your cloud estates. And it's so important to to make that mental leap because uh in past generation, we used to talk about integrating technologies together and then with public cloud, we started talking about move to public cloud, but it's really how do we integrate, how do we integrate all of that innovation that's coming from the hyper scale, is everything they're doing to innovate superfast, All of that innovation is coming from open source, all of that innovation that's coming from from companies around the world, including Cisco, How do we integrate that to deliver an outcome? Because at the end of the day, if you're a cloud of Steam, if you're an idea of Steam, your job is to deliver an outcome and our mission is to make it super simple for you to do that. That's the mission we're on and we're hoping that everybody that's excited as we are about how simple we made that. >>Great, thank you a lot in this announcement today, appreciate you guys coming back on and help us unpack you know, some of the details. Thank thanks so much. Great having you. >>Thank you >>Dave in a moment. We're gonna come back and talk about disruptive technologies and futures in the age of hybrid cloud with Vegas Rattana and James leach. You're watching the cube, the global leader in high tech coverage. >>What if your server box >>wasn't a box at >>all? What if it could do anything run anything? >>Be any box you >>need with massive scale precision and intelligence managed and optimized from the cloud integrated with all your clouds, private, public or hybrid. So you can build whatever you need today and tomorrow. The potential of this box is unlimited. Unstoppable unseen ever before. Unbox the future with Cisco UCS X series powered by inter site >>Cisco. >>The bridge to possible. Yeah >>we're here with Vegas Rattana who's the director of product management for Pcs at Cisco. And James Leach is the director of business development for U. C. S. At the Cisco as well. We're gonna talk about computing in the age of hybrid cloud. Welcome gentlemen. Great to see you. >>Thank you. >>Thank you because let's start with you and talk about a little bit about computing architectures. We know that they're evolving. They're supporting new data intensive and other workloads especially as high performance workload requirements. What's this guy's point of view on all this? I mean specifically interested in your thoughts on fabrics. I mean it's kind of your wheelhouse, you've got accelerators. What are the workloads that are driving these evolving technologies and how how is it impacting customers? What are you seeing? >>Sure. First of all, very excited to be here today. You're absolutely right. The pace of innovation and foundational platform ingredients have just been phenomenal in recent years. The fabric that's writers that drives the processing power, the Golden city all have been evolving just an amazing place and the peace will only pick up further. But ultimately it is all about applications and the way applications leverage those innovations. And we do see applications evolving quite rapidly. The new classes of applications are evolving to absorb those innovations and deliver much better business values. Very, very exciting time step. We're talking about the impact on the customers. Well, these innovations have helped them very positively. We do see significant challenges in the data center with the point product based approach of delivering these platforms, innovations to the applications. What has happened is uh, these innovations today are being packaged as point point products to meet the needs of a specific application and as you know, the different applications have no different needs. Some applications need more to abuse, others need more memory, yet others need, you know, more course, something different kinds of fabrics. As a result, if you walk into a data center today, it is very common to see many different point products in the data center. This creates a manageability challenge. Imagine the aspect of managing, you know, several different form factors want you to you purpose built servers. The variety of, you know, a blade form factor, you know, this reminds me of the situation we had before smartphones arrived. You remember the days when you when we used to have a GPS device for navigation system, a cool music device for listening to the music. A phone device for making a call camera for taking the photos right? And we were all excited about it. It's when a smart phones the right that we realized all those cool innovations could be delivered in a much simpler, much convenient and easy to consume through one device. And you know, I could uh, that could completely transform our experience. So we see the customers were benefiting from these innovations to have a way to consume those things in a much more simplistic way than they are able to go to that. >>And I like to look, it's always been about the applications. But to your point, the applications are now moving in a much faster pace. The the customer experience is expectation is way escalated. And when you combine all these, I love your analogy there because because when you combine all these capabilities, it allows us to develop new Applications, new capabilities, new customer experiences. So that's that I always say the next 10 years, they ain't gonna be like the last James Public Cloud obviously is heavily influencing compute design and and and customer operating models. You know, it's funny when the public cloud first hit the market, everyone we were swooning about low cost standard off the shelf servers in storage devices, but it quickly became obvious that customers needed more. So I wonder if you could comment on this. How are the trends that we've seen from the hyper scale, Is how are they filtering into on prem infrastructure and maybe, you know, maybe there's some differences there as well that you could address. >>Absolutely. So I'd say, first of all, quite frankly, you know, public cloud has completely changed the expectations of how our customers want to consume, compute, right? So customers, especially in a public cloud environment, they've gotten used to or, you know, come to accept that they should consume from the application out, right? They want a very application focused view, a services focused view of the world. They don't want to think about infrastructure, right? They want to think about their application, they wanna move outward, Right? So this means that the infrastructure basically has to meet the application where it lives. So what that means for us is that, you know, we're taking a different approach. We're we've decided that we're not going to chase this single pane of glass view of the world, which, frankly, our customers don't want, they don't want a single pane of glass. What they want is a single operating model. They want an operating model that's similar to what they can get at the public with the public cloud, but they wanted across all of their cloud options they wanted across private cloud across hybrid cloud options as well. So what that means is they don't want to just consume infrastructure services. They want all of their cloud services from this operating model. So that means that they may want to consume infrastructure services for automation Orchestration, but they also need kubernetes services. They also need virtualization services, They may need terror form workload optimization. All of these services have to be available, um, from within the operating model, a consistent operating model. Right? So it doesn't matter whether you're talking about private cloud, hybrid cloud anywhere where the application lives. It doesn't matter what matters is that we have a consistent model that we think about it from the application out. And frankly, I'd say this has been the stumbling block for private cloud. Private cloud is hard, right. This is why it hasn't been really solved yet. This is why we had to take a brand new approach. And frankly, it's why we're super excited about X series and inter site as that operating model that fits the hybrid cloud better than anything else we've seen >>is acute. First, first time technology vendor has ever said it's not about a single pane of glass because I've been hearing for decades, we're gonna deliver a single pane of glass is going to be seamless and it never happens. It's like a single version of the truth. It's aspirational and, and it's just not reality. So can we stay in the X series for a minute James? Uh, maybe in this context, but in the launch that we saw today was like a fire hose of announcements. So how does the X series fit into the strategy with inter site and hybrid cloud and this operating model that you're talking about? >>Right. So I think it goes hand in hand, right. Um the two pieces go together very well. So we have uh, you know, this idea of a single operating model that is definitely something that our customers demand, right? It's what we have to have, but at the same time we need to solve the problems of the cost was talking about before we need a single infrastructure to go along with that single operating model. So no longer do we need to have silos within the infrastructure that give us different operating models are different sets of benefits when you want infrastructure that can kind of do all of those configurations, all those applications. And then, you know, the operating model is very important because that's where we abstract the complexity that could come with just throwing all that technology at the infrastructure so that, you know, this is, you know, the way that we think about is the data center is not centered right? It's no longer centered applications live everywhere. Infrastructure lives everywhere. And you know, we need to have that consistent operating model but we need to do things within the infrastructure as well to take full advantage. Right? So we want all the sas benefits um, of a Ci CD model of, you know, the inter site can bring, we want all that that proactive recommendation engine with the power of A I behind it. We want the connected support experience went all of that. They want to do it across the single infrastructure and we think that that's how they tie together, that's why one or the other doesn't really solve the problem. But both together, that's why we're here. That's why we're super excited. >>So Vegas, I make you laugh a little bit when I was an analyst at I D C, I was deep in infrastructure and then when I left I was doing, I was working with application development heads and like you said, uh infrastructure, it was just a, you know, roadblock but but so the target speakers with Cisco announced UCS a decade ago, I totally missed it. I didn't understand it. I thought it was Cisco getting into the traditional server business and it wasn't until I dug in then I realized that your vision was really to transform infrastructure, deployment and management and change them all. I was like, okay, I got that wrong uh but but so let's talk about the the ecosystem and the joint development efforts that are going on there, X series, how does it fit into this, this converged infrastructure business that you've, you've built and grown with partners, you got storage partners like Netapp and Pure, you've got i SV partners in the ecosystem. We see cohesive, he has been a while since we we hung out with all these companies at the Cisco live hopefully next year, but tell us what's happening in that regard. >>Absolutely, I'm looking forward to seeing you in the Cisco live next year. You know, they have absolutely you brought up a very good point. You see this is about the ecosystem that it brings together, it's about making our customers bring up the entire infrastructure from the core foundational hardware all the way to the application level so that they can, you know, go off and running pretty quick. The converse infrastructure has been one of the corners 2.5 hour of the strategy, as you pointed out in the last decade. And and and I'm I'm very glad to share that converse infrastructure continues to be a very popular architecture for several enterprise applications. Seven today, in fact, it is the preferred architecture for mission critical applications where performance resiliency latency are the critical requirements there almost a de facto standards for large scale deployments of virtualized and business critical data bases and so forth with X series with our partnerships with our Stories partners. Those architectures will absolutely continue and will get better. But in addition as a hybrid cloud world, so we are now bringing in the benefits of canvas in infrastructure uh to the world of hybrid cloud will be supporting the hybrid cloud applications now with the CIA infrastructure that we have built together with our strong partnership with the Stories partners to deliver the same benefits to the new ways applications as well. >>Yeah, that's what customers want. They want that cloud operating model. Right, go ahead please. >>I was going to say, you know, the CIA model will continue to thrive. It will transition uh it will expand the use cases now for the new use cases that were beginning to, you know, say they've absolutely >>great thank you for that. And James uh have said earlier today, we heard this huge announcement, um a lot of lot of parts to it and we heard Katie talk about this initiative is it's really computing built for the next decade. I mean I like that because it shows some vision and you've got a road map that you've thought through the coming changes in workloads and infrastructure management and and some of the technology that you can take advantage of beyond just uh, you know, one or two product cycles. So, but I want to understand what you've done here specifically that you feel differentiates you from other competitive architectures in the industry. >>Sure. You know that's a great question. Number one. Number two, um I'm frankly a little bit concerned at times for for customers in general for our customers customers in general because if you look at what's in the market, right, these rinse and repeat systems that were effectively just rehashes of the same old design, right? That we've seen since before 2000 and nine when we brought you C. S to market these are what we're seeing over and over and over again. That's that's not really going to work anymore frankly. And I think that people are getting lulled into a false sense of security by seeing those things continually put in the market. We rethought this from the ground up because frankly future proofing starts now, right? If you're not doing it right today, future proofing isn't even on your radar because you're not even you're not even today proved. So we re thought the entire chassis, the entire architecture from the ground up. Okay. If you look at other vendors, if you look at other solutions in the market, what you'll see is things like management inside the chassis. That's a great example, daisy chaining them together >>like who >>needs that? Who wants that? Like that kind of complexity is first of all, it's ridiculous. Um, second of all, um, if you want to manage across clouds, you have to do it from the cloud, right. It's just common sense. You have to move management where it can have the scale and the scope that it needs to impact your entire domain, your world, which is much larger now than it was before. We're talking about true hybrid cloud here. Right. So we had to solve certain problems that existed in the traditional architecture. You know, I can't tell you how many times I heard you talk about the mid plane is a great example. You know, the mid plane and a chastity is a limiting factor. It limits us on how much we can connect or how much bandwidth we have available to the chassis. It limits us on air flow and other things. So how do you solve that problem? Simple. Just get rid of it. Like we just we took it out, right. It's not no longer a problem. We designed an architecture that doesn't need it. It doesn't rely on it. No forklift upgrades. So, as we start moving down the path of needing liquid cooling or maybe we need to take advantage of some new, high performance, low latency fabrics. We can do that with almost. No problem at all. Right, So, we don't have any forklift upgrades. Park your forklift on the side. You won't need it anymore because you can upgrade gradually. You can move along as technologies come into existence that maybe don't even exist. They they may not even be on our radar today to take advantage of. But I like to think of these technologies, they're really important to our customers. These are, you know, we can call them disruptive technologies. The reality is that we don't want to disrupt our customers with these technologies. We want to give them these technologies so they can go out and be disruptive themselves. Right? And this is the way that we've designed this from the ground up to be easy to consume and to take advantage of what we know about today and what's coming in the future that we may not even know about. So we think this is a way to give our customers that ultimate capability flexibility and and future proofing. >>I like I like that phrase True hybrid cloud. It's one that we've used for years and but to me this is all about that horizontal infrastructure that can support that vision of what true hybrid cloud is. You can support the mission critical applications. You can you can develop on the system and you can support a variety of workload. You're not locked into one narrow stovepipe and that does have legs, Vegas and James. Thanks so much for coming on the program. Great to see you. >>Yeah. Thank you. Thank you. >>When we return shortly thomas Shiva who leads Cisco's data center group will be here and thomas has some thoughts about the transformation of networking I. T. Teams. You don't wanna miss what he has to say. You're watching the cube. The global leader in high tech company. Okay, >>mm. Mhm, mm. Okay. Mhm. Yeah. Mhm. Yeah. >>Mhm. Yes. Yeah. Okay. We're here with thomas Shiva who is the Vice president of Product Management, A K A VP of all things data center, networking STN cloud. You name it in that category. Welcome thomas. Good to see you again. >>Hey Sam. Yes. Thanks for having me on. >>Yeah, it's our pleasure. Okay, let's get right into observe ability. When you think about observe ability, visibility, infrastructure monitoring problem resolution across the network. How does cloud change things? In other words, what are the challenges that networking teams are currently facing as they're moving to the cloud and trying to implement hybrid cloud? >>Yeah. Yeah, visibility as always is very, very important. And it's quite frankly, it's not just it's not just the networking team is actually the application team to write. And as you pointed out, the underlying impetus to what's going on here is the data center is where the data is. And I think we set us a couple years back and really what happens the applications are going to be deployed uh in different locations, right. Whether it's in a public cloud, whether it's on prayer, uh, and they are built differently right there, built as microservices, they might actually be distributed as well at the same application. And so what that really means is you need as an operator as well as actually a user better visibility. Where are my pieces and you need to be able to correlate between where the app is and what the underlying network is that is in place in these different locations. So you have actually a good knowledge while the app is running so fantastic or sometimes not. So I think that's that's really the problem statement. What what we're trying to go afterwards, observe ability. >>Okay, and let's double click on that. So a lot of customers tell me that you gotta stare at log files until your eyes bleed and you gotta bring in guys with lab coats who have phds to figure all this stuff out. So, so you just described, it's getting more complex, but at the same time you have to simplify things. So how how are you doing that, >>correct? So what we basically have done is we have this fantastic product that that is called 1000 Ice. And so what this does is basically as the name, which I think is a fantastic fantastic name. You have these sensors everywhere. Um, and you can have a good correlation on uh links between if I run from a site to aside from a site to a cloud, from a cloud to cloud and you basically can measure what is the performance of these links. And so what we're, what we're doing here is we're actually extending the footprint of these thousands agent. Right? Instead of just having uh inversion machine clouds, we are now embedding them with the Cisco network devices. Right? We announced this with the catalyst 9000 and we're extending this now to our 8000 catalyst product line for the for the SD were in products as well as to the data center products the next line. Um and so what you see is is, you know, half a saying, you have 1000 eyes, you get a million insights and you get a billion dollar of improvements uh for how your applications run. And this is really uh, the power of tying together the footprint of where the network is with the visibility, what is going on. So you actually know the application behavior that is attached to this network. >>I see. So okay. So as the cloud evolves and expands it connects your actually enabling 1000 eyes to go further, not just confined within a single data center location, but out to the network across clouds, et cetera, >>correct. Wherever the network is, you're going to have 1000 I sensor and you can't bring this together and you can quite frankly pick if you want to say, hey, I have my application in public cloud provider, a uh, domain one and I have another one domain to, I can't do monitor that link. I can also monitor have a user that has a campus location or branch location. I kind of put an agent there and then I can monitor the connectivity from that branch location all the way to the let's say corporations that data centre, our headquarter or to the cloud. And I can have these probes and just we have visibility and saying, hey, if there's a performance, I know where the issue is and then I obviously can use all the other foods that we have to address those. >>All right, let's talk about the cloud operating model. Everybody tells us it's really the change in the model that drives big numbers in terms of R. O. I. And I want you to maybe address how you're bringing automation and devops to this world of of hybrid and specifically how is Cisco enabling I. T. Organizations to move to a cloud operating model? Is that cloud definition expands? >>Yeah, no that's that's another interesting topic beyond the observe ability. So really, really what we're seeing and this is going on for uh I want to say a couple of years now, it's really this transition from operating infrastructure as a networking team more like a service like what you would expect from a cloud provider. Right? It's really around the network team offering services like a cloud provided us. And that's really what the meaning is of cloud operating model. Right? But this is infrastructure running your own data center where that's linking that infrastructure was whatever runs on the public club is operating and like a cloud service. And so we are on this journey for why? So one of the examples uh then we have removing some of the control software assets, the customers that they can deploy on prayer uh to uh an instance that they can deploy in a cloud provider and just busy, insane. She ate things there and then just run it that way. Right. And so the latest example for this is what we have our identity service engine that is now limited availability available on AWS and will become available in mid this year, both in Italy as unusual as a service. You can just go to market place, you can load it there and now you create, you can start running your policy control in a cloud, managing your access infrastructure in your data center, in your campus wherever you want to do it. And so that's just one example of how we see our customers network operations team taking advantage of a cloud operating model and basically employing their, their tools where they need them and when they need them. >>So what's the scope of, I hope I'm saying it right. Ice, right. I see. I think it's called ice. What's the scope of that like for instance, turn in effect my or even, you know, address simplify my security approach. >>Absolutely. That's now coming to what is the beauty of the product itself? Yes. What you can do is really is that there's a lot of people talking about else. How do I get to zero trust approach to networking? How do I get to a much more dynamic, flexible segmentation in my infrastructure. Again, whether this is only campus X as well as a data center and Ice help today, you can use this as a point to define your policies and then any connect from there. Right. In this particular case we would instant Ice in the cloud as a software load. You now can connect and say, hey, I want to manage and program my network infrastructure and my data center on my campus, going to the respective control over this DNA Center for campus or whether it is the A. C. I. Policy controller. And so yes, what you get as an effect out of this is a very elegant way to automatically manage in one place. What is my policy and then drive the right segmentation in your network infrastructure? >>zero. Trust that, you know, it was pre pandemic. It was kind of a buzzword. Now it's become a mandate. I wonder if we could talk about right. I mean I wonder if you talk about cloud native apps, you got all these developers that are working inside organizations. They're maintaining legacy apps. They're connecting their data to systems in the cloud there, sharing that data. I need these developers, they're rapidly advancing their skill sets. How is Cisco enabling its infrastructure to support this world of cloud? Native making infrastructure more responsive and agile for application developers? >>Yeah. So, you know, we're going to the top of his visibility, we talked about the operating model, how how our network operators actually want to use tools going forward. Now, the next step to this is it's not just the operator. How do they actually, where do they want to put these tools, how they, how they interact with these tools as well as quite frankly as how, let's say, a devops team on application team or Oclock team also wants to take advantage of the program ability of the underlying network. And this is where we're moving into this whole cloud native discussion, right? Which is really two angles, that is the cloud native way, how applications are being built. And then there is the cloud native way, how you interact with infrastructure. Right? And so what we have done is we're a putting in place the on ramps between clouds and then on top of it we're exposing for all these tools, a P I S that can be used in leverage by standard uh cloud tools or uh cloud native tools. Right. And one example or two examples we always have and again, we're on this journey for a while is both answerable uh script capabilities that exist from red hat as well as uh Ashitaka from capabilities that you can orchestrate across infrastructure to drive infrastructure, automation and what what really stands behind it is what either the networking operations team wants to do or even the ap team. They want to be able to describe the application as a code and then drive automatically or programmatically in situation of infrastructure needed for that application. And so what you see us doing is providing all these capability as an interface for all our network tools. Right. Whether it's this ice that I just mentioned, whether this is our D. C. And controllers in the data center, uh whether these are the controllers in the in the campus for all of those, we have cloud native interfaces. So operator or uh devops team can actually interact directly with that infrastructure the way they would do today with everything that lives in the cloud, with everything how they brought the application. >>This is key. You can't even have the conversation of op cloud operating model that includes and comprises on prem without programmable infrastructure. So that's that's very important. Last question, thomas our customers actually using this, they made the announcement today. There are there are there any examples of customers out there doing this? >>We do have a lot of customers out there that are moving down the past and using the D. D. Cisco high performance infrastructure, but also on the compute side as well as on an exercise one of the customers. Uh and this is like an interesting case. It's Rakuten uh record and is a large tackle provider, a mobile five G. Operator uh in Japan and expanding and is in different countries. Uh and so people something oh, cloud, you must be talking about the public cloud provider, the big the big three or four. But if you look at it, there's a lot of the tackle service providers are actually cloud providers as well and expanding very rapidly. And so we're actually very proud to work together with with Rakuten and help them building a high performance uh, data and infrastructure based on hard gig and actually phone a gig uh to drive their deployment to. It's a five G mobile cloud infrastructure, which is which is uh where the whole the whole world where traffic is going. And so it's really exciting to see this development and see the power of automation visibility uh together with the high performance infrastructure becoming reality and delivering actually services, >>you have some great points you're making there. Yes, you have the big four clouds, your enormous, but then you have a lot of actually quite large clouds. Telcos that are either approximate to those clouds or they're in places where those hyper scholars may not have a presence and building out their own infrastructure. So so that's a great case study uh thomas, hey, great having you on. Thanks so much for spending some time with us. >>Yeah, same here. I appreciate it. Thanks a lot. >>I'd like to thank Cisco and our guests today V Joy, Katie VJ, viscous James and thomas for all your insights into this evolving world of hybrid cloud, as we said at the top of the next decade will be defined by an entirely new set of rules. And it's quite possible things will evolve more quickly because the cloud is maturing and has paved the way for a new operating model where everything is delivered as a service, automation has become a mandate because we just can't keep throwing it labor at the problem anymore. And with a I so much more as possible in terms of driving operational efficiencies, simplicity and support of the workloads that are driving the digital transformation that we talk about all the time. This is Dave Volonte and I hope you've enjoyed today's program. Stay Safe, be well and we'll see you next time.

>>Hi lisa martin here with the cubes coverage of demon 2021. I've got to alumni joining me. Please welcome back to the cube Danny. Alan beam's ceo Danny. It's great to see you. >>I am delighted to be here lisa. >>Excellent brian Schwartz is here as well. Google director outbound product management brian welcome back to the program. Uh >>thanks for having me again. Excited to be >>here. Excited to be here. Yes, definitely. We're gonna be talking all about what Demon google are doing today. But let's go ahead and start Danny with you. Seems vision is to be the number one trusted provider of backup and recovery solutions for the, for for modern data protection. Unpack that for me, trust is absolutely critical. But when you're talking about modern data protection to your customers, what does that mean? >>Yeah. So I always, I always tell our customers there's three things in there that are really important. Trust is obviously number one and google knows this. You've been the most trusted search provider uh, forever. And, and so we have 400,000 customers. We need to make sure that our products work. We need to make sure they do data protection, but we need to do it in a modern way. And so it's not just back up and recovery, that's clearly important. It's also all of the automation and orchestration to move workloads across infrastructures, move it from on premises to the google cloud, for example, it also includes things like governance and compliance because we're faced with ransomware, malware and security threats. And so modern data protection is far more than just back up. It's the automation, it's the monitoring, it's a governance and compliance. It's the ability to move workloads. Um, but everything that we look at within our platform, we focus on all of those different characteristics and to make sure that it works for our customers. >>One of the things that we've seen in the last year, Danny big optic in ransom were obviously the one that everyone is the most familiar with right now. The colonial pipeline. Talk to me about some of the things that the team has seen, what your 400,000 customers have seen in the last 12 months of such a dynamic market, a massive shift to work from home and to supporting SAS for clothes and things like that. What have you seen? >>Well, certainly the employees working from home, there's a massive increase in the attack surface for organizations because now, instead of having three offices, they have, you know, hundreds of locations for their end users. And so it's all about protecting their data at the same time as well. There's been this explosion in malware and ransomware attacks. So we really see customers focusing on three different areas. The first is making sure that when they take a copy of their data, that it is actually secure and we can get into, you know, a mutability and keeping things offline. But really taking the data, making sure it's secure. The second thing that we see customers doing is monitoring their environment. So this is both inspection of the compute environment and of the data itself. Because when ransomware hits, for example, you'll see change rates on data explode. So secure your data monitor the environment. And then lastly make sure that you can recover intelligently is let us say because the last thing that you want to do if you're hit by ransomware is to bring the ransomware back online from a backup. So we call this security cover re secure, restore. We really see customers focusing on those three areas >>And that restoration is critical there because as we know these days, it's not if we get hit with ransomware, it's really a matter of when. Let's go ahead now and go into the google partnership, jenny talked to me about it from your perspective, the history of the strength of the partnership, all that good stuff. >>Yeah. So we have a very deep and long and lengthy relationship with google um, on a number of different areas. So for example, we have 400,000 customers. Where do they send their backups? Most customers don't want to continue to invest in storage solutions on their premises. And so they'll send their data from on premises and tear it into google cloud storage. So that's one integration point. The second is when the running workloads within the clouds. So this is now cloud native. If you're running on top of the google cloud platform, we are inside the google America place and we can protect those workloads. A third area is around the google vm ware engine, there's customers that have a hybrid model where they have some capacity on premises and some in google using the VM ware infrastructure and we support that as well. That's a third area and then 1/4 and perhaps the longest running um, google is synonymous with containers and especially kubernetes, they were very instrumental in the foundations of kubernetes and so r K 10 product which does data protection for kubernetes is also in the google America place. So a very long and deep relationship with them and it's to the benefit of our customers. >>Absolutely. And I think I just saw the other day that google celebrated the search engine. It's 15th birthday. I thought what, what did we do 16 years ago when we couldn't just find anything we wanted brian talked to me about it from Google's perspective of being partnership. >>Yeah, so as Danny mentioned, it's really multifaceted, um it really starts with a hybrid scenario, you know, there's still a lot of customers that are on their journey into the cloud and protecting those on premises workloads and in some senses, even using beams capabilities to move data to help migrate into the cloud is I'd say a great color of the relationship. Um but as Danny mentioned increasingly, more and more primary applications are running in the cloud and you know, the ability to protect those and have, you know, the great features and capabilities, uh you know, that being provides, whether it be for GCB er VM where you know, capability and google cloud or things like G k e R kubernetes offering, which has mentioned, you know, we've been deep and wide in kubernetes, we really birthed it many, many years ago um and have a huge successful business in, in the managing and hosting containers, that having the capabilities to add to those. It really adds to our ecosystem. So we're super excited about the partnership, we're happy to have this great foundation to build together with them into the future. >>And Danny Wien launched, just been in february a couple of months ago, being backup for google cloud platform. Talk to us about that technology and what you're announcing at them on this year. >>Yeah, sure. So back in february we released the first version of the VM backup for G C p product in the marketplace and that's really intended to protect of course, i as infrastructure as a service workloads running on top of G C p and it's been very, very successful. It has integration with the core platform and what I mean by that is if you do a backup in G C P, you can do you can copy that back up on premises and vice versa. So it has a light integration at the data level. What we're about to release later on this summer is version two of that product that has a deep integration with the VM platform via what we call the uh team service platform, a PS themselves. And that allows a rich bidirectional uh interaction between the two products that you can do not just day one operations, but also day to operations. So you can update the software, you can harmonize schedules between on premises and in the cloud. It really allows customers to be more successful in a hybrid model where they're moving from on premises to the cloud. >>And that seems to be really critically important. As we talk about hybrid club all the time, customers are in hybrid. They're living in the hybrid cloud for many reasons, whether it's acquisition or you know, just the nature of lines of business leveraging their cloud vendor of choice. So being able to support the hybrid cloud environment for customers and ensure that that data is recoverable is table stakes these days. Does that give them an advantage over your competition Danny? >>It does. Absolutely. So customers want the hybrid cloud experience. What we find over time is they do trend towards the cloud. There's no question. So if you have the hybrid experience, if they're sending their data there, for example, a step one, step two, of course, is just to move the workload into the cloud and then step three, they really start to be able to unleash their data. If you think about what google is known for, they have incredible capabilities around machine learning and artificial intelligence and they've been doing that for a very long time. So you can imagine customers after they start putting their data there, they start putting their workloads here, they want to unlock it into leverage the insights from the data that they're storing and that's really exciting about where we're going. It's, they were early days for most customers. They're still kind of moving and transitioning into the cloud. But if you think of the capabilities that are unlocked with that massive platform in google, it just opens up the ability to address big challenges of today, like climate change and sustainability and you know, all the health care challenges that we're faced with it. It really is an exciting time to be partnered with Google >>Ryan. Let's dig into the infrastructure in the architecture from your perspective, help us unpack that and what customers are coming to you for help with. >>Yeah. So Danny mentioned, you know the prowess that google has with data and analytics and, and a, I I think we're pretty well known for that. Uh, there's a tremendous opportunity for people in the future. Um, the thing that people get just right out of the box is the access to the technology that we built to build google cloud itself. Just the scale and, and technology, it's, you know, it's, it's a, you know, just incredible. You know, it's a fact that we have eight products here at google that have a billion users and when you have, you know, most people know the search and maps and gmail and all these things. When you have that kind of infrastructure, you build a platform like google cloud platform and you know, the network as a perfect example, the network endpoints, they're actually close to your house. There's a reason our technology is so fast because you get onto the google private network, someplace really close to where you actually live. We have thousands and thousands of points of presence spread around the world and from that point forward you're riding on our internal network, you get better quality of service. Uh the other thing I like to mention is, you know, the google cloud storage, that team is built on our object storage. It's uh it's the same technology that underpins Youtube and other things that most people are familiar with and you just think about that for a minute, you can find the most obscure Youtube video and it's gonna load really fast. You know, you're not going to sit there waiting for like two minutes waiting for something to load and that same under underlying technology underpins GCS So when you're going to go and you know, go back to an old restore, you know, to do a restore, it's gonna load fast even if you're on one of the more inexpensive storage classes. So it's a really nice experience for data protection. It has this global network properties you can restore to a different region if there was ever a disaster, there's just the scale of our foundation of infrastructure and also, you know, Danny mentioned if we're super proud about the investments that google has made for sustainability, You know, our cloud runs on 100% renewable energy at the cloud at our scale. That's a lot of, that's a lot of green energy. We're happy to be one of the largest consumers of green energy out there and make continued investments in sustainability. So, you know, we think we have some of the greenest data centers in the world and it's just one more benefit that people have when they come to run on Google Cloud. >>I don't know what any of us would do without google google cloud platform or google cloud storage. I mean you just mentioned all of the enterprise things as well as the at home. I've got to find this really crazy, obscure youtube video but as demanding customers as we are, we want things asAP not the same thing. If you know, an employee can't find a file or calendar has been deleted or whatnot. Let's go in to finish our time here with some joint customer use case examples. Let's talk about backing up on prem workloads to google cloud storage using existing VM licensing Danny. Tell us about that. >>Yeah. So one of the things that we've introduced at beam is this beam, universal licensing and it's completely portable license, you can be running your workloads on premises now and on a physical system and then you can, you know, make that portable to go to a virtual system and then if you want to go to the cloud, you can send that data up to the work load up to the cloud. One of the neat things about this transition for customers from a storage perspective, we don't charge for that. If you're backing up a physical system and sending your your back up on premises, you know, we don't charge for that. If you want to move to the cloud, we don't charge for that. And so as they go through this, there's a predictability and and customers want that predictability so much um that it's a big differentiating factor for us. They don't want to be surprised by a bill. And so we just make it simple and seamless. They have a single licensing model and its future proof as they move forward on the cloud journey. They don't have to change anything. >>Tell me what you mean by future proof as a marketer. I know that term very well, but it doesn't mean different things to different people. So for means customers in the context of the expansion of partnership with google the opportunities, the choices that you're giving customers to your customers, what does future proof actually delivered to them? >>It means that they're not locked into where they are today. If you think about a customer right now that's running a workload on premises maybe because they have to um they need to be close to the data that's being generated or feeding into that application system. Maybe they're locked into that on premises model. Now they have one of two choices when their hardware gets to the end of life. They can either buy more hardware which locks them into where they are today for the next three years in the next four years Or they can say, you know what, I don't want to lock into that. I want to model the license that is portable that maybe 12 months from now, 18 months from now, I can move to the cloud and so it future proof some, it doesn't give them another reason to stay on premises. It allows them the flexibility that licensing is taken off the table because it moves with you that there's zero thought or consideration and that locks you into where you are today. And that's exciting because it unlocks the capabilities of the cloud without being handicapped if you will by what you have on premises. >>Excellent. Let's go to the second uh use case lift and shift in that portability brian. Talk to us about it from your perspective. >>Yeah, so we obviously constantly in discussions with our customers about moving more applications to the cloud and there's really two different kind of approach is the lift and shift and modernization. You know, do you want to change and run on kubernetes when you come to the cloud as you move it in? In some cases people want to do that or they're gonna obviously build a new application in the cloud. But increasingly we see a lot of customers wanting to do lift and shift, they want to move into the cloud relatively quickly. As Danny said, there's like compelling events on like refreshes and in many cases we've had a number of customers come to us and say look we're going to exit our data centers. We did a big announcement Nokia, they're gonna exit 50 data centers in the coming years around the world and just move that into the cloud. In many cases you want to lift and shift that application to do the migration with his little change as possible. And that's one of the reasons we've really invested in a lot of enterprise, more classic enterprise support type technologies. And also we're super excited to have a really wide set of partners and ecosystem like the folks here at Wien. So the customers can really preserve those technologies, preserve that operational experience that they're already familiar with on prem and use that in the cloud. It just makes it easier for them to move to the cloud faster without having to rebuild as much stuff on the way in. >>And that's critical. Let's talk about one more use case and that is native protection of workloads that run on g c p Danny. What are you enabling customers to do there? >>Well? So we actually merged the capabilities of two different things. One is we leverage the native Api is of G C p to take a snapshot and we merge that with our ability to put it in a portable data format. Now. Why is that important? Because you want to use the native capabilities of G CPU want to leverage those native snapshots. The fastest way to recover a file or the fastest way to recover of'em is from the G C p snapshot. However, if you want to take a copy of that and move it into another locale or you want to pull it back on premises for compliance reasons or put it in a long term storage format, you probably want to put it in GCS or in our portable storage format. And so we merge those two capabilities, the snapshot and back up into a single product. And in addition to that, one of the things that we do, again, I talked about predictability. We tell customers what that policy is going to cost them because if for example a customer said, well I like the idea of doing my backups in the cloud, but I want to store it on premises. We'll tell them, well if you're copying that data continually, you know what the network charges look like, What the CPU and compute charges look like, What do the storage costs looks like. So we give them the forecast of what the cost model looks like even before they do a single backup. >>That forecasting has got to be key, as you said with so much unpredicted things that we can't predict going on in this world the last year has taught us that with a massive shift, the acceleration of digital business and digital transformation, it's really critical that customers have an idea of what their costs are going to be so that they can make adjustments and be agile as they need the technology to be. Last question Bryant is for you, give us a view uh, and all the V mon attendees, what can we expect from the partnership in the next 12 >>months? You know, we're excited about the foundation of the partnership across hybrid and in cloud for both VMS and containers. I think this is the real beginning of a long standing relationship. Um, and it's really about a marriage of technology. You think about all the great data protection and orchestration, all the things that Danny mentioned married with the cloud foundation that we have at scale this tremendous network. You know, we just signed a deal with SpaceX in the last couple of days to hook their satellite network up to the google cloud network, you know, chosen again because we just have this foundational capability to push large amounts of data around the world. And that's you know, for Youtube. We signed a deal with Univision, same type of thing, just massive media uh, you know, being pushed around the world. And if you think about it that that same foundation is used for data protection. Data protection. There's a lot of data and moving large sets of data is hard. You know, we have just this incredible prowess and we're excited about the future of how our technology and beans. Technology is going to evolve over time >>theme and google a marriage of technology Guys, thank you so much for joining me, sharing what's new? The opportunities that demand google are joined me delivering to your joint customers. Lots of great step. We appreciate your time. >>Thanks lisa >>For Danielle in and Brian Schwartz. I'm Lisa Martin. You're watching the cubes coverage of Lehman 2021.