>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019 brought to you by VM Wear and its ecosystem partners. >> Welcome back here on the Cube, we continue our coverage. We're live in San Francisco. Mosconi, North Day to wrapping up Day two of our three days of coverage here, Veum. World 2019 day Volante. John Wall's glad to have you with us here on the Cube. And we're now joined by Kevin Schatz. Camera. Who's the Vice president of service provider Strategy and solutions. A deli. Um, See, Kevin. Good to see this afternoon. Thank you. You as well. And, uh, yeah, Tarazi, Who is the S v p and chief technical officer at Dell Technologies in the heart. Good to see you. Thanks for taking the time to be with us. A couple of telco guys and we've had a lot of telco on and talking about it in terms of progress that you made. This was an area that you got into with a major commitment, some probably three years ago. Kind of bitch market for me then for where you were there on on day one to where you are now today and the progress you've made and maybe the service is that you're about to provide. Yeah, >> sure. So I think if we look over the last three years, our opportunity that we defined early on telecommunications space was the virtual ization, and software to find everything was leaving the data center. And we would see the software to find architecture extend all the way from radio through the core network through the cloud over a period of time. And it started with technologies like network function virtualization. So if we flash back three years ago, where our entire strategy was built on the premise that relationships with the network equipment providers like Nokia and Ericsson, where our primary path to market our primary opportunity, I think what we've realized is we've emerged in this space to a greater detail is that our expertise, our expertise and experience in building I T Networks and Building Cloud has led to the first wave of conversations in the telecommunications industry directly not through the network equipment providers, but that carriers want to engage directly with Delhi emcee for the lessons learned and how did to play. I tr detectors. And now, as we extend towards the edge that they want to engage directly with Del Technologies in terms of how we build cloud architectures. We've had a number of big announcements. Over the last several years. We've announced partnerships and engagements with NTT. We've announced partnerships and engagements with China Unicom. Just in the last three months, we've announced partnerships with our rounds around network EJ out of France and then most recently with 18 C on the automation of EJ infrastructure related to their airship project. I think from a benchmark perspective, it's just been a continued growth opportunity for us and recognition that the more we engaged in, the more we contribute as a productive member of what is a very complex and changing and transforming industry, the more success in relationships that will build, and the more it will translate into opportunity to sell to >> when you think about you have the the modernization of N F. E. For example, as a former technologist inside a large telco, Um, what were some of the challenges? Is it? It's taken a long time. Obviously, when you talk to some of the telcos, they say, Well, you know it affects our infrastructure, but we still get this application mass. I mean, maybe you could add some color and describe for our audience why it's been so challenging. >> Yeah, I think that's an excellent question. Um, going back to my days at Telco on data centers, even S d n and the software defined tools were just beginning to show up. So the biggest challenges where you were basically having toe work with predefined operating system. But he defined hardware. The hardware was not exposed for for GAM ability, the ability to take advantage of it. And then you had to interrogate multiple players of technology in a way where it took significant time, too, not only for software development, but for product development and user experience. Since then, many of those walls have come down, and some of them have come down very hard. When you look at what we're doing, Adele here and we lead for the open networking. Not only do you have the choice of operating system were also pushing hard. Don't new open operating systems for networking like Sonic with Microsoft and bade calm. And then we're taking industry leading steps to expose the silicon chips themselves for four GAM ability. These are all the components that are critical. When you talk about five G, for example, do you really have to have those capabilities? I also would say that the software evolution have made it to infrastructure. The Dev ops and the modern applications we talk about here is also available for infrastructure, which means you really can develop a capability in weeks instead of years and months. Five people can do in amazing parkas. All of this was not possible before, >> so we talked to Shekhar about this in the earlier segment challenges in the telco business. I mean, the one hand you got these quasi monopolies in some cases real monopolies that just chug along and do pretty well. But the same time you got the cost for a bit dramatically coming down, you've got the data growth doing this. You got over the top providers taking advantage of the those those networks, and so new infrastructure allows them to be more more agile. But there's a workforce component to that, and there's a skill set, and that's how they got to transform. I wonder if you could maybe talk about that a little bit. Kevin. >> Yeah, I think that's exactly right. I think when we work within this industry, it's not just a technology conversation. It's the ability to consume an operationalized technology. And I think that comes down to a number of different things, comes down to the processes that exist when it comes down to the skill sets that exists to be able to build these new processes around. And I think if we flash back several years ago, the model of how we build networks was that the team that operated it needed to understand networking. Right now, if you look at the team that needs to operate it, they need to understand networking. They need to understand, compute. They need to understand virtualization. They need to understand AP eyes. They need to be able to script and program. They need to understand some level of data science that they can close a loop in the operational models eventually with a I and machine learning technologies. So I think that the teams that are getting built look very different than the single soul capabilities that they've had in the past, right? These air smaller teams they're more agile teams that can develop and have their own more unique processes in each part of the network. Right? And even if we think about the organizational structures, we've always built vertical organizations. Right? When I had an appliance, that was an e p. C. I had an operations team that was focused on an e p. C. And I even broke that into an S gateway P Gateway and Emma, me et cetera. If we look at the world now, that s Gateway P Gateway. Mm E consists of a server consists of the networking that connects at server consists of a virtual ization layer. It consists of a stack of a software application, and all of those need to be automated, orchestrated program toe work as any PC does. So I think that the skill sets have just really expanded in terms of what's expected, >> and this is really important because the process is used to be pretty well known and hardened, so the infrastructure could be hard, and now it's of every every months, the more the market changes right. What kind of what kind of challenges is that bring to the telco provider? But also to the infrastructure provider. >> Yeah, I actually I have a really good way to describe what I think is happening. We heard it from a lot of our customers and not just tell cause but enterprises. I would say the last 5 to 10 years everybody's been dealing with Hybrid Cloud. The Move to Cloud Waas. The Big Challenge. While this remains a key challenge, a new challenge showed up, which is how to succeed in this new modern software development model. You know, are you able to do to move at that speed, which means you have full stack engineers? Can you develop the app beginning to end? It's not a nightie model anymore. Also, you no longer have an operations team. You really have to have saris who, able with software and also the customer service, changed to a softwood Devyn. So we're starting to hear from a lot of our customers. That's the next journey they really need help with. If you think of infrastructure, those challenges are even bigger, and this is where it's important to lean on technology partners who can help you with that, >> and you hit on five G a little bit ago. You have in your initial statement and we've kind of touched on the impact that it can have in terms of you understanding there. They're going to a transformative time, right? I mean, telcos are with new capabilities, and new opportunities in this whole edge is gonna be crazy. So you've got to you've got I would say some learning to do, but you have. You've got to get up to speed on what their new fundamentals are going to be, right? Yeah, I think that's >> true. I think where you know, we we've understood >> their fundamentals because it's the same transition that the IittIe world's gone through. And to a large degree, that cloud world has gone through. I think that the challenge we've we've been working to break through collectively as an industry is the paralysis at the rate of adoption of new technologies because they're so much change so quickly because we talk about virtualization. And then we're talking about kubernetes. We're talking about cloud native we're talking about Ah, bare Metal Service's. We continue to talk about Micro Micro Service's architectures. We see this progression of technology that's happening so fast in various segments of the industry. I think that the telecommunications industry has been somewhat paralyzed in terms of where do they jump in and which do they adopt and how fast they migrate between them. And which of them can be capable of being hardened to be telco grade and fit into their requirements. That they have for being able to offer regulated service >> is paralyzed because it's just too fast. It's too fast for a big amazed, a big decision to make for big. But but things are evolving too quickly. That's that's It's evolving >> too quickly. And they also sometimes have a concern that they get stuck on a dead end path, right, Because things change so quickly it's Do I jump here? Then here, then here, then here, Then here. Where do I follow a logical path and what we tend to find when we work with the telecommunications industry is that, yes, del technologies can define a strategy. Certainly VM wear and L E. M. C can define our individual strategies. Are operators can define their strategies. But there's just not one strategy for this industry. Reality is, is that when you get when you get together with an ecosystem of partners, and you work at a particular telecommunications company. That is a strategy, and you start from scratch when you go to the next right because they're their ability to consume technology. It's just so different the end game, maybe the same across the board. But the path to get there will look different, >> so every customer's different Get that. But clearly some patterns must be emerging. So my question is, where do you start your sitting down with What are you seeing in terms of common starting points and advice you'd give Thio? >> I think that to Maine has everybody starting with First of all, the physical infrastructure. Compute storage Networking is moving to X 86 model of some sort, which means many, many parts of their infrastructure today that is not based on X 86 needs to transition. So what? Seeing big art piece significant discussions of how you take compute and this new programmable networking and put it everywhere like in thousands of locations. So infrastructure wise, that is a known specific thing to be solved at early stages and given you know, that capability he's we've delivered toward enterprises. We have a lot of tools and capabilities to give them, and the 2nd 1 is that a lot of people are approaching this as a network issue. In reality, it's a cloud decision, not a network. You hurt Shaker, talk about it so the tools capabilities you need to build a cloud is completely different. This cloud may not be genetic cloud it needs to be. It needs to support the defense specific platforms under for they want Cloud, and they needed to support the specific capabilities. So that's the two. A year ago, nobody even could articulate. That was the challenge they were facing. But I would say that's what we are today. >> I would add to that that as we kind of think about the infrastructure and then that cloud decision that there's abstractions that exist between those right at the infrastructure layer, there is the need tohave, an automation system that has the ability to support multiple different cloud platforms that sit on top of it. And that's work that we're doing in the deli in seaside and then secondary to that at the cloud layer. It's the ability to support a multi virtualization environment. Virtual machines do exist and will continue to exist. Kubernetes and cloud native containerized applications do exist and will continue to exist. And the challenge becomes. How do I orchestrate an environment that allows those two exist simultaneously and be layered on top of a common building block of infrastructure? And I think that's really the power that the broader Del Technologies has is that we have all of these entities and capabilities in house. >> How long does this take? A telco toe transform is this decade. Is it? Is it Maur can Obviously certain parts can happen faster. But when when you sit down with with customers and they put together their plans, I mean, what what what's their time horizon? >> So I would argue that we define the first NFI standards and 2012. And if we look globally and even within the vast majority of the Indus story and carriers were somewhere in the 10 to 15% range, yeah, >> yeah, that too compelling. Uh, hey, is that enough? Maybe be a forcing function for making some of those decisions. Are the economics on moving toe X 86 are very compelling. It's 10 times the speed to deploy, and it's a massive order of magnitude and costs. Therefore, it's not something that you could wait on as you continue to build capacity. So that's is forcing the infrastructure decision. The second forcing function is that what five G's starting to look like is not network and wireless, independent from enterprise solutions, you really have to collapse. The single infrastructure you know to offer service is and why it lists embedded on That's another forcing function in terms of enterprises is starting to ask for those capabilities. >> You know, you mentioned X 86 couple times and when you think about the Telco Cloud generically what we're talking about here in the in the commercial cloud not to tell ghost no commercial but the mainstream cloud you're getting a lot of offload, you know, hardware offload alternative processing arm uh, GP use F p g a Z even, you know, custom, a six coming back. You've seen the same thing in the Telco club >> for sure, I think I think if if you look at what we've done over the last several years, we've seen this dramatic shift in almost a pendulum swing away from a six and proprietary hardware towards everything on X 86 I think what we've learned over the last several years at X 86 is a platform that has its value. But it's just not for every work with So we've seen things like network slicing and control, user plane separation and technologies that her first moving user playing very high Io applications back onto smart nicks and F PJs and eventually onto merchant silicon with programmable silicate in the network switches. But I think that even if you look at what's happening in in Public Cloud with things like GPU virtualization, they're still largely virtualized in the time domain, which means that they're used by a particular application for a period of time and then the next application scheduled it in the next application schedule. Is it that doesn't work for network workloads? So I think that what we're finding is we go to this Toko Cloud model, especially with offload in the virtual ization of Acceleration Technologies, is that it's an entire set of problems that just aren't solved in public cloud yet. >> Yeah, I would say, based on experience, the vast majority of network workloads have to be x 86 I definitely think arm cores and GPO offloads will play all at some point in the future. But they that's not the heavy duty that you need to offload those functions because most of these network applications were it. And for custom, a sick. That's very high performance that you know, it has high throughput. Security, built in ability to build service is directly into the silicon. So that kind of transition over time you'll feed. You see a lot of distributed applications, it and container formats all the way at the edge. But that transition to that kind of distributed model from what we are today is probably not possible. And I would argue you'll always have their mics off high performance, high throughput. I mean, think about it. If you're trying to activate 20,000 I ot devices instantly, you really need a high core density, you know, x 86 chip with significant memory. You really worry about the data plane and how much data you can put. So it's better >> we didn't even hit I ot dead. Wait, wait Another day, Another conversation. Hey, thanks for the time. We certainly appreciate it. Been a good show I for you all to write for, sir? Good. Good energy. Good vibes and good business. Thanks for the time We appreciate it. >> Thank you, guys. Thank >> you very much for your time. >> Watching the Cube live coverage Here it Veum World 2019 in San Francisco. Thank you.