(bright upbeat music) >> Hello and welcome to the Palo Alto Studios, theCube. I'm John Furrier, we here for a special Cube Conversation and special report, big news from VMware to discuss the launch of the availability of vSphere 7. I'm here with Krish Prasad SVP and General Manager of the vSphere Business and Cloud Platform Business Unit. And Paul Turner, VP of vSphere Product Management. Guys, thanks for coming in and talking about the big news. >> Thank you for having us. >> You guys announced some interesting things back in March around containers, Kubernetes and vSphere. Krish, tell us about the hard news what's being announced? >> Today we are announcing the general availability of vSphere 7. John, it's by far the biggest release that we have done in the last 10 years. We premiered it as project Pacific few months ago. With this release, we are putting Kubernetes native support into the vSphere platform. What that allows us to do is give customers the ability to run both modern applications based on Kubernetes and containers, as well as traditional VM based applications on the same platform. And it also allows the IT departments to provide their developers, cloud operating model using the VMware cloud foundation that is powered by this release. This is a key part of our (murmurs) portfolio solutions and products that we announced this year. And it is targeted fully at the developers of modern applications. >> And the specific news is vSphere.. >> Seven is generally available. >> Generally a vSphere 7? >> Yes. >> So let's on the trend line here, the relevance is what? What's the big trend line, that this is riding obviously we saw the announcements at VMware last year, and throughout the year, there's a lot of buzz. Pat Gelsinger says, "There's a big wave here with Kubernetes." What does this announcement mean for you guys with the marketplace trend? >> Yes what Kubernetes is really about is people trying to have an agile operation, they're trying to modernize the IT applications. And the best way to do that, is build off your current platform, expand it and make it a an innovative, an Agile Platform for you to run Kubernetes applications and VM applications together. And not just that customers are also looking at being able to manage a hybrid cloud environment, both on-prem and public cloud together. So they want to be able to evolve and modernize their application stack, but modernize their infrastructure stack, which means hybrid cloud operations with innovative applications Kubernetes or container based applications and VMs. >> What's exciting about this trend, Krish, we were talking about this at VMworld last year, we had many conversations around cloud native, but you're seeing cloud native becoming the operating model for modern business. I mean, this is really the move to the cloud. If you look at the successful enterprises, leaving the suppliers, the on premises piece, if not moved to the cloud native marketplace technologies, the on-premise isn't effective. So it's not so much on-premises going away, we know it's not, but it's turning into cloud native. This is the move to the cloud generally, this is a big wave. >> Yeah, absolutely. I mean, John, if you think about it on-premise, we have, significant market share, we are by far the leader in the market. And so what we are trying to do with this, is to allow customers to use the current platform they are using, but bring their modern application development on top of the same platform. Today, customers tend to set up stacks, which are different, so you have a Kubernetes stack, you have stack for the traditional applications, you have operators and administrators who are specialized in Kubernetes on one side, and you have the traditional VM operators on the other side. With this move, what we are saying is that you can be on the same common platform, you can have the same administrators who are used to administering the environment that you already had, and at the same time, offer the developers what they like, which is Kubernetes dial-tone, that they can come and deploy their applications on the same platform that you use for traditional applications. >> Yeah, Paul, Pat said Kubernetes can be the dial-tone of the internet. Most millennials might even know what dial-tone is. But what he meant is that's the key fabric, that's going to orchestrate. And we've heard over the years skill gap, skill gap, not a lot of skills out there. But when you look at the reality of skills gap, it's really about skills gaps and shortages, not enough people, most CIOs and chief information security officers, that we talk to, say, I don't want to fork my development teams, I don't want to have three separate teams, I don't have to, I want to have automation, I want an operating model that's not going to be fragmented. This kind of speaks to this whole idea of, interoperability and multi cloud. This seems to be the next big way behind hybrid. >> I think it is the next big wave, the thing that customers are looking for is a cloud operating model. They like the ability for developers to be able to invoke new services on demand in a very agile way. And we want to bring that cloud operating model to on-prem, to Google Cloud, to Amazon cloud to Microsoft Cloud to any of our VCPP partners. You get the same cloud operating experience. And it's all driven by a Kubernetes based dial-tone that's effective and available within this platform. So by bringing a single infrastructure platform that can run in this hybrid manner, and give you the cloud operating agility the developers are looking for, that's what's key in version seven. >> Does Pat Gelsinger mean when he says dial-tone of the internet Kubernetes. Does he mean always on? or what does he mean specifically? Just that it's always available? what's the meaning behind that phrase? >> The first thing he means is that developers can come to the infrastructure, which is, The VMware Cloud Foundation, and be able to work with a set of API's that are Kubernetes API's. So developers understand that, they are looking for that. They understand that dial-tone, right? And you come to our VMware cloud foundation that runs across all these clouds, you get the same API set that you can use to deploy that application. >> Okay, so let's get into the value here of vSphere 7, how does VMware and vSphere 7 specifically help customers? Isn't just bolting on Kubernetes to vSphere, some will say is that's simple or (murmurs) you're running product management no, it's not that easy. Some people say, "He is bolting Kubernetes on vSphere." >> it's not that easy. So one of the things, if anybody has actually tried deploying Kubernetes, first, it's highly complicated. And so definitely one of the things that we're bringing is you call it a bolt on, but it's certainly not like that we are making it incredibly simple. You talked about IT operational shortages, customers want to be able to deploy Kubernetes environments in a very simple way. The easiest way that you can do that is take your existing environment that route 90% of IT, and just turn on the Kubernetes dial-tone, and it is as simple as that. Now, it's much more than that, in version seven, as well, we're bringing in a couple things that are very important. You also have to be able to manage at scale, just like you would in the cloud, you want to be able to have infrastructure, almost self manage and upgrade and lifecycle manage itself. And so we're bringing in a new way of managing infrastructure so that you can manage just large scale environments, both on-premise and public cloud environments at scale. And then associated with that as well is you must make it secure. So there's a lot of enhancements we're building into the platform around what we call intrinsic security, which is how can we actually build in a truly a trusted platform for your developers and IT. >> I was just going to touch on your point about this, the shortage of IT staff, and how we are addressing that here. The way we are addressing that, is that the IT administrators that are used to administering vSphere can continue to administer this enhanced platform with Kubernetes, the same way they administered the older releases, so they don't have to learn anything new. They are just working the same way. We are not changing any tools, process, technologies. >> So same as it was before? >> Same as before. >> More capability. >> More capability. And developers can come in and they see new capabilities around Kubernetes. So it's a best of both worlds. >> And what was the pain point that you guys are solving? Obviously, the ease of use is critical, obviously, operationally, I get that. As you look at the cloud native developer cycles, infrastructure as code means, as app developers, on the other side, taking advantage of it. What's the real pain point that you guys are solving with vSphere 7. >> So I think it's multiple factors. So first is we've talked about agility a few times, there is DevOps is a real trend inside an IT organizations. They need to be able to build and deliver applications much quicker, they need to be able to respond to the business. And to do that, what they are doing is they need infrastructure that is on demand. So what we're really doing in the core Kubernetes kind of enablement, is allowing that on demand fulfillment of infrastructure, so you get that agility that you need. But it's not just tied to modern applications. It's also all of your existing business applications and your monitoring applications on one platform, which means that you've got a very simple and low cost way of managing large scale IT infrastructure. So that's a huge piece as well. And then I do want to emphasize a couple of other things. We're also bringing in new capabilities for AI and ML applications for SAP HANA databases, where we can actually scale to some of the largest business applications out there. And you have all of the capabilities like the GPU awareness and FPGA awareness that we built into the platform, so that you can truly run this as the fastest accelerated platform for your most extreme applications. So you've got the ability to run those applications, as well as your Kubernetes and Container based application. >> That's the accelerated application innovation piece of the announcement right? >> That's right, yeah. It's quite powerful that we've actually brought in, basically new hardware awareness into the product and expose that to your developers, whether that's through containers or through VMs. >> Krish, I want to get your thoughts on the ecosystem and then the community but I want to just dig into one feature you mentioned. I get the lifestyle improvement, life lifecycle improvement, I get the application acceleration innovation, but the intrinsic security is interesting. Could you take a minute, explain what that is? >> Yeah, so there's a few different aspects. One is looking at how can we actually provide a trusted environment. And that means that you need to have a way that the key management that even your administrator is not able to get keys to the kingdom, as we would call it. You want to have a controlled environment that, some of the worst security challenges inside in some of the companies has been your internal IT staff. So you've got to have a way that you can run a trusted environment independent. We've got vSphere Trust Authority that we released in version seven, that actually gives you a secure environment for actually managing your keys to the kingdom effectively your certificates. So you've got this, continuous runtime. Now, not only that, we've actually gone and taken our carbon black features, and we're actually building in full support for carbon black into the platform. So that you've got native security of even your application ecosystem. >> Yeah, that's been coming up a lot conversations, the carbon black and the security piece. Krish obviously vSphere everywhere having that operating model makes a lot of sense, but you have a lot of touch points, you got cloud, hyper scalars got the edge, you got partners. >> We have that dominant market share on private cloud. We are on Amazon, as you will know, Azure, Google, IBM Cloud, Oracle Cloud. So all the major clouds, there is a vSphere stack running. So it allows customers if you think about it, it allows customers to have the same operating model, irrespective of where their workload is residing. They can set policies, components, security, they set it once, it applies to all their environments across this hybrid cloud, and it's all supported by our VMware Cloud Foundation, which is powered by vSphere 7. >> Yeah, I think having that, the cloud as API based having connection points and having that reliable easy to use is critical operating model. Alright guys, so let's summarize the announcement. What do you guys their takeaway from this vSphere 7, what is the bottom line? What's it really mean? (Paul laughs) >> I think what we're, if we look at it for developers, we are democratizing Kubernetes. We already are in 90% of IT environments out there are running vSphere. We are bringing to every one of those vSphere environments and all of the virtual infrastructure administrators, they can now manage Kubernetes environments, you can you can manage it by simply upgrading your environment. That's a really nice position rather than having independent kind of environments you need to manage. So I think that is one of the key things that's in here. The other thing though, I don't think any other platform out there, other than vSphere that can run in your data center in Google's, in Amazon's, in Microsoft's, in thousands of VCPP partners. You have one hybrid platform that you can run with. And that's got operational benefits, that's got efficiency benefits, that's got agility benefits. >> Great. >> Yeah, I would just add to that and say that, look, we want to meet customers, where they are in their journey. And we want to enable them to make business decisions without technology getting in the way. And I think the announcement that we made today, with vSphere 7, is going to help them accelerate their digital transformation journey, without making trade offs on people, process and technology. And there is more to come. Look, we are laser focused on making our platform the best in the industry, for running all kinds of applications and the best platform for a hybrid and multi cloud. And so you will see more capabilities coming in the future. Stay tuned. >> Well, one final question on this news announcement, which is awesome, vSphere, core product for you guys, if I'm the customer, tell me why it's going to be important five years from now? >> Because of what I just said, it is the only platform that is going to be running across all the public clouds, which will allow you to have an operational model that is consistent across the cloud. So think about it. If you go to Amazon native, and then you have a workload in Azure, you're going to have different tools, different processes, different people trained to work with those clouds. But when you come to VMware and you use our Cloud Foundation, you have one operating model across all these environments, and that's going to be game changing. >> Great stuff, great stuff. Thanks for unpacking that for us. Congratulations on the announcement. >> Thank you. >> vSphere 7, news special report here, inside theCube cCnversation, I'm John Furrier. Thanks for watching. (upbeat music) >> Hey welcome back everybody, Jeff Frick here with theCube. We are having a very special Cube Conversation and kind of the the ongoing unveil, if you will of the new VMware vSphere 7.0 we're going to get a little bit more of a technical deep dive here today we're excited to have longtime Cube alumni, Kit Colbert here, is the VP and CTO of Cloud Platform at VMware. Kit, great to see you. And, and new to theCube, Jared Rosoff. He's a Senior Director of Product Management VMware, and I'm guessing had a whole lot to do with this build. So Jared, first off, congratulations for birthing this new release. And great to have you on board. >> Feels pretty good, great to be here. >> All right, so let's just jump into it. From kind of a technical aspect, what is so different about vSphere 7? >> Yeah, great. So vSphere 7, bakes Kubernetes right into the virtualization platform. And so this means that as a developer, I can now use Kubernetes to actually provision and control workloads inside of my vSphere environment. And it means as an IT admin, I'm actually able to deliver Kubernetes and containers to my developers really easily right on top of the platform I already run. >> So I think we had kind of a sneaking suspicion that might be coming with the acquisition of the FTO team. So really exciting news. And I think Kit you tease it out quite a bit at VMware last year about really enabling customers to deploy workloads across environments, regardless of whether that's on-prem, public cloud, this public cloud, that public cloud. So this really is the realization of that vision. >> It is, yeah. So, we talked at VMworld about project Pacific, this technology preview, and as Jared mentioned, what that was, is how do we take Kubernetes and really build it into vSphere. As you know, we had Hybrid Cloud Vision for quite a while now. How do we proliferate vSphere to as many different locations as possible. Now part of the broader VMware Cloud Foundation portfolio. And as we've gotten more and more of these instances in the cloud on-premises, at the edge, with service providers, there's a secondary question, how do we actually evolve that platform? So it can support not just the existing workloads, but also modern workloads as well. >> All right. So I think you brought some pictures for us a little demo. So why (murmurs) and let's see what it looks like. You guys can keep the demo? >> Narrator: So we're going to start off looking at a developer actually working with the new VMware Cloud Foundation for and vSphere 7. So what you're seeing here is a developer is actually using Kubernetes to deploy Kubernetes. The selfie in watermelon, (all laughing) So the developer uses this Kubernetes declarative syntax where they can describe a whole Kubernetes cluster. And the whole developer experience now is driven by Kubernetes. They can use the coop control tool and all of the ecosystem of Kubernetes API's and tool chains to provision workloads right into vSphere. And so, that's not just provisioning workloads, though. This is also key to the developer being able to explore the things they've already deployed, so go look at, hey, what's the IP address that got allocated to that? Or what's the CPU load on this workload I just deployed. On top of Kubernetes, we've integrated a Container Registry into vSphere. So here we see a developer pushing and pulling container images. And one of the amazing things about this is, from an infrastructure is code standpoint. Now, the developers infrastructure as well as their software is all unified in source control. I can check in, not just my code, but also the description of the Kubernetes environment and storage and networking and all the things that are required to run that app. So now we're looking at sort of a side by side view, where on the right hand side is the developer continuing to deploy some pieces of their application and on the left hand side, we see vCenter. And what's key here is that as the developer deploys new things through Kubernetes, those are showing up right inside of the vCenter console. And so the developer and IT are seeing exactly the same things, the same names, and so this means what a developer calls their IT department and says, "Hey, I got a problem with my database," we don't spend the next hour trying to figure out which VM they're talking about. They got the same name, they see the same information. So what we're going to do is that, we're going to push the the developer screen aside and start digging into the vSphere experience. And what you'll see here is that vCenter is the vCenter you've already known and love, but what's different is that now it's much more application focused. So here we see a new screen inside of vCenter vSphere namespaces. And so these vSphere namespaces represent whole logical applications, like the whole distributed system now as a single object inside of vCenter. And when I click into one of these apps, this is a managed object inside of vSphere. I can click on permissions, and I can decide which developers have the permission to deploy or read the configuration of one of these namespaces. I can hook this into my active directory infrastructure, so I can use the same, corporate credentials to access the system, I tap into all my existing storage. So, this platform works with all of the existing vSphere storage providers. I can use storage policy based management to provide storage for Kubernetes. And it's hooked in with things like DRS, right? So I can define quotas and limits for CPU and memory, and all that's going to be enforced by DRS inside the cluster. And again, as an admin, I'm just using vSphere, but to the developer, they're getting a whole Kubernetes experience out of this platform. Now, vSphere also now sucks in all this information from the Kubernetes environment. So besides, seeing the VMs and things that developers have deployed, I can see all of the desired state specifications, all the different Kubernetes objects that the developers have created, the compute network and storage objects, they're all integrated right inside the vCenter console. And so once again, from a diagnostics and troubleshooting perspective, this data is invaluable, often saves hours, just to try to figure out what we're even talking about more trying to resolve an issue. So, as you can see, this is all baked right into vCenter. The vCenter experience isn't transformed a lot, we get a lot of VI admins who look at this and say, "Where's the Kubernetes?" And they're surprised. They're like, they've been managing Kubernetes all this time, it just looks, it looks like the vSphere experience they've already got. But all those Kubernetes objects, the pods and containers, Kubernetes clusters, load balancer stores, they're all represented right there natively in the vCenter UI. And so we're able to take all of that and make it work for your existing VI admins. >> Well, it's pretty wild. It really builds off the vision that again, I think you kind of outlined Kit teased out at VMworld, which was, the IT still sees vSphere, which is what they want to see, what they're used to seeing, but (murmurs) see Kubernetes and really bringing those together in a unified environment. So that, depending on what your job is and what you're working on, that's what you're going to see in this kind of unified environment. >> Yeah, as the demo showed, (clears throat) it is still vSphere at the center, but now there's two different experiences that you can have interacting with vSphere, Kubernetes base one, which is of course great for developers and DevOps type folks, as well as the traditional vSphere interface API's, which is great for VI admins and IT operations. >> And then it really is interesting too, you tease that a lot. That was a good little preview, people knew they're watching. But you talked about really cloud journey and kind of this bifurcation of kind of classical school apps that are that are running in their classic VMs, and then kind of the modern, kind of cloud native applications built on Kubernetes. And you outlined a really interesting thing that people often talk about the two ends of the spectrum, and getting from one to the other, but not really about kind of the messy middle, if you will, and this is really enabling people to pick where along that spectrum, they can move their workloads or move their apps. >> Yeah, I think we think a lot about it like that, we talk to customers, and all of them have very clear visions on where they want to go, their future state architecture. And that involves embracing cloud and involves modernizing applications. And you know, as you mentioned, it's challenging for them. Because I think what a lot of customers see is this kind of these two extremes either you're here where you are, kind of the old current world, and you got the bright Nirvana future on the far end there. And they believe that the only way to get there is to kind of make a leap from one side to the other, they have to kind of change everything out from underneath you. And that's obviously very expensive, very time consuming, and very error prone as well. There's a lot of things that can go wrong there. And so I think what we're doing differently at VMware is really to your point as you call it, the messy middle, I would say it's more like, how do we offer stepping stones along that journey? Rather than making this one giant leap we had to invest all this time and resources? How can we enable people to make smaller incremental steps, each of which have a lot of business value, but don't have a huge amount of cost? >> And it's really enabling kind of this next gen application, where there's a lot of things that are different about it. But one of the fundamental things is where now the application defines the resources that it needs to operate, versus the resources defining kind of the capabilities what the application can do. And that's where everybody is moving as quickly as makes sense. As you said, not all applications need to make that move, but most of them should, and most of them are, and most of them are at least making that journey. Do you see that? >> Yeah, definitely. I mean, I think that, certainly this is one of the big evolutions we're making in vSphere from, looking historically at how we managed infrastructure, one of the things we enable in vSphere 7, is how we manage applications. So a lot of the things you would do in infrastructure management of setting up security rules or encryption settings, or, your resource allocation, you would do this in terms of your physical and virtual infrastructure, you talk about it in terms of, this VM is going to be encrypted, or this VM is going to have this firewall rule. And what we do in vSphere 7 is elevate all of that to application centric management. So you actually look at an application and say, I want this application to be constrained to this much CPU. Or I want this application to have these security rules on it. And so that shifts the focus of management really up to the application level. >> And like, I can even zoom back a little bit there and say, if you look back, one thing we did was something like vSAN before that people had to put policies on a LAN an actual storage LAN, and a storage array. And then by virtue of a workload being placed on that array, inherited certain policies. And so, vSAN will turn that around allows you to put the policy on the VM. But what Jared is talking about now is that for a modern workload, a modern workloads is not a single VM, it's a collection of different things. You got some containers in there, some VMs, probably distributed, maybe even some on-prem, some on the cloud. And so how do you start managing that more holistically? And this notion of really having an application as a first class entity that you can now manage inside of vSphere is really powerful and very simplified one. >> And why this is important is because it's this application centric point of view, which enables the digital transformation that people are talking about all the time. That's a nice big word, but when the rubber hits the road is how do you execute and deliver applications. And more importantly, how do you continue to evolve them and change them, based on on either customer demands or competitive demands, or just changes in the marketplace. >> Yeah when you look at something like a modern app that maybe has 100 VMs that are part of it, and you take something like compliance. So today, if I want to check if this app is compliant, I got to go look at every individual VM and make sure it's locked down hardened and secured the right way. But now instead, what I can do is I can just look at that one application object inside of vCenter, set the right security settings on that and I can be assured that all the different objects inside of it are going to inherit that stuff. So it really simplifies that. It also makes it so that that admin can handle much larger applications. If you think about vCenter today, you might log in and see 1000 VMs in your inventory. When you log in with vSphere 7, what you see is few dozen applications. So a single admin can manage much larger pool of infrastructure, many more applications than they could before. Because we automate so much of that operation. >> And it's not just the scale part, which is obviously really important, but it's also the rate of change. And this notion of how do we enable developers to get what they want to get done, done, i.e. building applications, while at the same time enabling the IT operations teams to put the right sort of guardrails in place around compliance and security performance concerns, these sorts of elements. And so being by being able to have the IT operations team really manage that logical application at that more abstract level, and then have the developer be able to push in new containers or new VMs or whatever they need inside of that abstraction. It actually allows those two teams to work actually together and work together better. They're not stepping over each other. But in fact, now they can both get what they need to get done, done, and do so as quickly as possible but while also being safe, and in compliance, and so forth. >> So there's a lot more to this, this is a very significant release, right? Again, a lot of foreshadowing, if you go out and read the tea leaves, it's a pretty significant kind of re-architecture of many, many parts of vSphere. So beyond the Kubernetes, kind of what are some of the other things that are coming out in this very significant release? >> Yeah, that's a great question, because we tend to talk a lot about Kubernetes, what was Project Pacific, but it's now just part of vSphere. And certainly, that is a very large aspect of it. But to your point, vSphere 7 is a massive release with all sorts of other features. And so there is a demo here, let's pull up some slides. And we're ready to take a look at what's there. So, outside of Kubernetes, there's kind of three main categories that we think about when we look at vSphere 7. So the first first one is simplified Lifecycle Management. And then really focused on security as a second one, and then applications as well, but both including, the cloud native apps that could fit in the Kubernetes bucket as well as others. And so we go on the first one, the first column there, there's a ton of stuff that we're doing, around simplifying life cycles. So let's go to the next slide here where we can dive in a little bit more to the specifics. So we have this new technology vSphere Lifecycle Management, vLCM. And the idea here is how do we dramatically simplify upgrades, lifecycle management of the ESX clusters and ESX hosts? How do we make them more declarative, with a single image, you can now specify for an entire cluster. We find that a lot of our vSphere admins, especially at larger scales, have a really tough time doing this. There's a lot of ins and outs today, it's somewhat tricky to do. And so we want to make it really, really simple and really easy to automate as well. >> So if you're doing Kubernetes on Kubernetes, I suppose you're going to have automation on automation, because upgrading to the sevens is probably not an inconsequential task. >> And yeah, and going forward and allowing you as we start moving to deliver a lot of this great VCR functionality at a more rapid clip. How do we enable our customers to take advantage of all those great things we're putting out there as well. >> Next big thing you talk about is security. >> Yep >> We just got back from RSA. Thank goodness, we got that show in before all the badness started. But everyone always talks about security is got to be baked in from the bottom to the top. Talk about kind of the the changes in the security. >> So I've done a lot of things around security, things around identity federation, things around simplifying certificate management, dramatic simplifications they're across the board. What I want to focus on here, on the next slide is actually what we call vSphere Trust Authority. And so with that one, what we're looking at here is how do we reduce the potential attack surfaces, and really ensure there's a trusted computing base? When we talk to customers, what we find is that they're nervous about a lot of different threats, including even internal ones, right? How do they know all the folks that work for them can be fully trusted. And obviously, if you're hiring someone, you somewhat trust them. How do you implement the concept of least privilege. >> Jeff: Or zero trust (murmurs) >> Exactly. So they idea with trust authority that we can specify a small number of physical ESX hosts that you can really lock down ensure a fully secure, those can be managed by a special vCenter Server, which is in turn very locked down, only a few people have access to it. And then those hosts and that vCenter can then manage other hosts that are untrusted and can use attestation to actually prove that, okay, this untrusted host haven't been modified, we know they're okay, so they're okay to actually run workloads or they're okay to put data on and that sort of thing. So it's this kind of like building block approach to ensure that businesses can have a very small trust base off of which they can build to include their entire vSphere environment. >> And then the third kind of leg of the stool is, just better leveraging, kind of a more complex asset ecosystem, if you will, with things like FPGAs and GPUs, and kind of all of the various components that power these different applications which now the application can draw the appropriate resources as needed. So you've done a lot of work there as well. >> Yeah, there's a ton of innovation happening in the hardware space, as you mentioned, all sorts of accelerators coming out. We all know about GPUs, and obviously what they can do for machine learning and AI type use cases, not to mention 3D rendering. But FPGAs, and all sorts of other things coming down the pike as well there. And so what we found is that as customers try to roll these out, they have a lot of the same problems that we saw in the very early days of virtualization, i.e. silos of specialized hardware that different teams were using. And what you find is, all the things we found before you find very low utilization rates, inability to automate that, inability to manage that well, putting security and compliance and so forth. And so this is really the reality that we see in most customers and it's funny because, and sometimes you think, "Wow, shouldn't we be past this?" As an industry should we have solved this already, we did this with virtualization. But as it turns out, the virtualization we did was for compute and then storage network. But now we really need to virtualize all these accelerators. And so that's where this bit fusion technology that we're including now with vSphere, really comes to the forefront. So if you see in the current slide, we're showing here, the challenges that just these separate pools of infrastructure, how do you manage all that? And so if the we go to the next slide, what we see is that, with that fusion, you can do the same thing that we saw with compute virtualization, you can now pool all these different silos infrastructure together. So they become one big pool of GPUs of infrastructure that anyone in an organization can use. We can, have multiple people sharing a GPU, we can do it very dynamically. And the great part of it is that it's really easy for these folks to use. They don't even need to think about it, in fact, integrates seamlessly with their existing workflows. >> So it's free, it's pretty cheap, because the classifications of the assets now are much, much larger, much varied and much more workload specific right. That's really the opportunity slash challenge there. >> They are a lot more diverse And so like, a couple other things just, I don't have a slide on it, but just things we're doing to our base capabilities, things around DRS and vMotion. Really massive evolutions there as well to support a lot of these bigger workloads, right. So you look at some of the massive SAP HANA or Oracle databases, and how do we ensure that vMotion can scale to handle those, without impacting their performance or anything else there? Making DRS smarter about how it does load balancing, and so forth. So a lot of the stuff not just kind of brand new, cool new accelerator stuff, but it's also how do we ensure the core as people have already been running for many years, we continue to keep up with the innovation and scale there as well. >> All right. So Jared I give you the last word. You've been working on this for a while. There's a whole bunch of admins that have to sit and punch keys. What do you tell them? What should they be excited about? What are you excited for them in this new release? >> I think what I'm excited about is how IT can really be an enabler of the transformation of modern apps. I think today, you look at all of these organizations, and what ends up happening is, the app team ends up sort of building their own infrastructure on top of IT infrastructure. And so, now, I think we can shift that story around. I think that there's an interesting conversation that a lot of IT departments and app dev teams are going to be having over the next couple of years about how do we really offload some of these infrastructure tasks from the dev team? Make you more productive, give you better performance, availability, disaster recovery and these kinds of capabilities. >> Awesome. Well, Jared, congratulation and Kit both of you for getting the release out. I'm sure it was a heavy lift. And it's always good to get it out in the world and let people play with it. And thanks for for sharing a little bit more of a technical deep dive into this ton more resources for people that didn't want to go down into the weeds. So thanks for stopping by. >> Thank you. >> Thank you. >> Alright, he's Jared, he's Kit, I'm Jeff. You're watching theCube. We're in the Palo Alto Studios. Thanks for watching, we'll see you next time. (upbeat music) >> Hi, and welcome to a special Cube Conversation. I'm Stu Miniman, and we're digging into VMware vSphere 7 announcement. We've had conversations with some of the executives some of the technical people, but we know that there's no better way to really understand the technology than to talk to some of the practitioners that are using it. So really happy to have joined me on the program. I have Philip Buckley-Mellor, who is an infrastructure designer with British Telecom joining me digitally from across the pond. Phil, thanks so much for joining us. >> Nice too. >> Alright, so Phil, let's start of course, British Telecom, I think most people know, you know what BT is and it's, really sprawling company. Tell us a little bit about, your group, your role and what's your mandate. >> Okay, so, my group is called service platforms. It's the bit of BT that services all of our multi millions of our customers. So we have broadband, we have TV, we have mobile, we have DNS and email systems. And it's all about our customers. It's not a B2B part of BT, you're with me? We specifically focus on those kind of multi million customers that we've got in those various services. And in particular, my group we do infrastructure. we really do from data center all the way up to really about boot time or so we'll just pass boot time, and the application developers look after that stage and above. >> Okay, great, we definitely going to want to dig in and talk about that, that boundary between the infrastructure teams and the application teams. But let's talk a little bit first, we're talking about VMware. So, how long has your organization been doing VMware and tell us, what you see with the announcement that VMware is making for vSphere 7? >> Sure, well, I mean, we've had really great relationship with VMware for about 12, 13 years, something like that. And it's a absolutely key part of our infrastructure. It's written throughout BT, really, in every part of our operations, design, development, and the whole ethos of the company is based around a lot of VMware products. And so one of the challenges that we've got right now is application architectures are changing quite significantly at the moment, And as you know, in particular with serverless, and with containers and a whole bunch of other things like that. We're very comfortable with our ability to manage VMs and have been for a while. We currently use extensively we use vSphere NSXT, VROPs, login site, network insight and a whole bunch of other VMware constellation applications. And our operations teams know how to use that they know how to optimize, they know how to pass the plan, and (murmurs). So that's great. And that's been like that for half a decade at least, we've been really, really confident with our ability to deal with VMware environments. And along came containers and like, say, multi cloud as well. And what we were struggling with was the inability to have a single pane of glass, really on all of that, and to use the same people and the same processes to manage a different kind of technology. So we, we've been working pretty closely with VMware on a number of different containerization products. For several years now, I've worked really closely with the vSphere integrated containers, guys in particular, and now with the Pacific guys, with really the ideal that when we bring in version seven and the containerization aspects of version seven, we'll be in a position to have that single pane of glass to allow our operations team to really barely differentiate between what's a VM and what's a container. That's really the Holy Grail. So we'll be able to allow our developers to develop, our operations team to deploy and to operate, and our designers to see the same infrastructure, whether that's on-premises, cloud or off-premises, and be able to manage the whole piece in that respect. >> Okay, so Phil, really interesting things you walk through here, you've been using containers in a virtualized environment for a number of years, want to understand and the organizational piece just a little bit, because it sounds great, I manage all the environment, but, containers are a little bit different than VMs. if I think back, from an application standpoint, it was, let's stick it in a VM, I don't need to change it. And once I spin up a VM, often that's going to sit there for, months, if not years, as opposed to, I think about a containerization environment. It's, I really want to pool of resources, I'm going to create and destroy things all the time. So, bring us inside that organizational piece. How much will there needs to be interaction and more interaction or change in policies between your infrastructure team and your app dev team? >> Well, yes, me absolutely right, that's the nature and the timescales that we're talking about between VMs and containers is wildly different. As you say, we probably almost certainly have Vms in place now that were in place in 2018 certainly I imagine, and haven't really been touched. Whereas as you say, VMs and a lot of people talk about spinning them all up all the time. There are parts of architecture that require that, in particular, the very client facing bursty stuff, does require spinning up and spinning down pretty quickly. But some of our some of our other containers do sit around for weeks, if not months, really does depend on the development cycle aspects of that, but the heartbeat that we've really had was just visualizing it. And there are a number of different products out there that allow you to see the behavior of your containers and understand the resource requirements that they are having at any given moment. Allies troubleshoot and seven. But they need any problems, the new things that we we will have to get used to. And also it seems that there's an awful lot of competing products, quite a Venn diagram of in terms of functionality and user abilities to do that. So again coming back to being able to manage through vSphere. And to be able to have a list of VMs on alongside is a list of containers and to be able to use policies to define how they behave in terms of their networking, to be able to essentially put our deployments on rails by using in particular tag based policies, means that we can take the onus of security, we can take the onus of performance management and capacity management away from the developers who don't really have a lot of time, and they can just get on with their job, which is to develop new functionality, and help our customers. So that means then we have to be really responsible about defining those policies, and making sure that they're adhered to. But again, we know how to do that with the VMs through vSphere. So the fact that we can actually apply that straight away, just with slightly different compute unit, is really what we're talking about here is ideal, and then to be able to extend that into multiple clouds as well, because we do use multiple clouds where (murmurs) and as your customers, and we're between them is an opportunity that we can't do anything other than be excited about (murmurs) >> Yeah, Phil, I really like how you described really the changing roles that are happening there in your organization need to understand, right? There's things that developers care about the they want to move fast, they want to be able to build new things and there's things that they shouldn't have to worry about. And, you know, we talked about some of the new world and it's like, oh, can the platform underneath this take care of it? Well, there's some things platforms take care of, there's some things that the software or your team is going to need to understand. So maybe if you could dig in a little bit, some of those, what are the drivers from your application portfolio? What is the business asking of your organization that's driving this change? And being one of those tail winds pushing you towards, Kubernetes and the vSphere 7 technologies? >> Well, it all comes down to the customers, right? Our customers want new functionality. They want new integrations, they want new content, they want better stability and better performance and our ability to extend or contracting capacity as needed as well. So there will be ultimate challenges that we want to give our customers the best possible experience of our products and services. So we have to have address that really from a development perspective, it's our developers have the responsibility to, design and deploy those. So, in infrastructure, we have to act as a firm, foundation, really underneath all of that. That allows them to know that what they spend their time and develop and want to push out to our customers is something that can be trusted is performant. We understand where the capacity requirements are coming from in the short term, and in the long term for that, and he's secure as well, obviously, is a big aspect to it. And so really, we're just providing our developers with the best possible chance of giving our customers what will hopefully make them delighted. >> Great, Phil, you've mentioned a couple of times that you're using public clouds as well as, your VMware firm. Want to make sure I if you can explain a little bit a couple of things. Number one is, when it comes to your team, especially your infrastructure team, how much are they in involved with setting up some of the basic pieces or managing things like performance in the public cloud. And secondly, when you look at your applications, or some of your clouds, some of your applications hybrid going between the data center and the public cloud. And I haven't talked to too many customers that are doing applications that just live in any cloud and move things around. But you know, maybe if you could clarify those pieces as to, what cloud really means to your organization and your applications? >> Sure, well, I mean, tools. Cloud allows us to accelerate development, which is nice because it means we don't have to do on-premises capacity lifts for new pieces of functionality are so we can initially build in the cloud and test in the cloud. But very often, applications really make better sense, especially in the TV environment where people watch TV all the time. I mean, yes, there are peak hours and lighter hours of TV watching. Same goes for broadband really. But we generally were well more than an eight hour application profile. So what that allows us to do then is to have applications that are, well, it makes sense. We run them inside our organization where we have to run them in our organization for, data protection reasons or whatever, then we can do that as well. But where we say, for instance, we have a boxing match on. And we're going to be seeing an enormous spike in the amount of customers that want to sign up into our auto journey to allow them to view that and to gain access to that, well, why would you spend a lot of money on servers just for that level of additional capacity? So we do absolutely have hybrid applications, not sorry, hybrid blocks, we have blocks of sub applications, dozens of them really to support our platform. And what you would see is that if you were to look at our full application structure for one of the platforms, I mentioned, that some of the some of those application blocks have to run inside some can run outside and what we want to be able to do is to allow our operations team to define that, again, by policies to where they run, and to, have a system that allows us to transparently see where they're running, how they're running, and the implications of those decisions so that we can tune those maybe in the future as well. And that way, we best serve our customers. We got to get our customers yeah, what they need. >> All right, great, Phil, final question I have for you, you've been through a few iterations of looking at VMs containers, public cloud, what what advice would you give your peers with the announcement of vSphere 7 and how they can look at things today in 2020 versus what they might have looked at, say a year or two ago? >> Well, I'll be honest, I was a little bit surprised by vSphere 7. We knew that VMware will working on trying to make containers on the same level, both from a management deployment perspective as VMs. I mean, they're called VMware after all right? And we knew that they were looking at that. But I was surprised by just quite how quickly they've managed to almost completely reinvent the application, really. It's, you know, if you look at the whole Tansy stuff and the Mission Control stuff, I think a lot of people were blown away by just quite how happy VMware were to reinvent themselves from an application perspective, and to really leap forward. And this is, between version six and seven. I've been following these since version three, at least. And it's an absolutely revolutionary change in terms of the overall architecture. The aims to, to what they want to achieve with the application. And luckily, the nice thing is, is that if you're used to version six is not that big a deal, it's really not that big a deal to move forward at all, it's not such a big change to process and training and things like that. But my word, there's an awful lot of work underneath that, underneath the covers. And I'm really excited. And I think all the people in my position should really use take it as an opportunity to revisit what they can achieve with, in particular with vSphere, and with in combination with NSXT, it's quite hard to put into place unless you've seen the slides about it and unless you've seen the product, just how revolutionary the version seven is compared to previous versions, which have kind of evolved through a couple of years. So yeah, I think I'm really excited about it. And I know a lot of my peers or the companies that I speak with quite often are very excited about seven as well. So yeah, I'm really excited about though the whole base >> Well, Phil, thank you so much. Absolutely no doubt this is a huge move for VMware, the entire company and their ecosystem rallying around, help move to the next phase of where application developers and infrastructure need to go. Phil Buckley joining us from British Telecom. I'm Stu Miniman. Thank you so much for watching theCube. (upbeat music)

>> Announcer: From San Francisco, it's theCUBE. Covering VMware Radio 2019. Brought to you by VMware. >> Hi, welcome to theCUBE's exclusive coverage of VMware Radio 2019. Lisa Martin with John Furrier, in San Francisco. This is an internal R&D innovation off site that VMware does, lots of innovation going on here from engineers from all over the globe. We're pleased to welcome Joe Baguley, the CTO from EMEA, from VMware. Joe, welcome to theCUBE. >> Hi. >> So we've been having some great conversations this morning about this tremendous amount of innovation, I mean the potential is massive. Not just from Radio, but from all the other innovation programs that VMware has, really speaks very strongly to the culture of innovation that VMware has had. But of course all this innovation has to be able to be harnessed to deliver what customers need. Talk to us about that, you're in the field, field CTO. What is that connection with the innovation that happens within VMware? How do customers help influence that and vice versa? >> Yeah, I think we're very unique in the structure that we've put around that to drive that innovation over the years. So my job as field CTO is, I call it sort of 50, 50. So 50% is Chief Technology Officer, which is this kind of stuff for Radio and 50% is Chief Talking Officer, which is out with our customers and presenting at conferences, et cetera. But the general remit is connecting R&D in the field. And so for eight years now I've been connecting R&D in the field at VMware, I actually did at my previous company as well. And what we've done is, we've built a series of programs over the years to do that, and one of the biggest ones is the CTO Ambassadors. And so that was, you know, you get to a point, you get to a growth size, I've been here eight years, and suddenly you need someone else to help you because I can't be everywhere. And the original role was, back in the day I was hired to scale Steve Herrod, because Steve Herrod couldn't be in Europe all the time, I was like mini Steve Herrod that could be there when needed. But then eventually I can't be in every European country and our major regions as we get bigger and bigger, and we've grown dramatically. So the CTO Ambassadors is to support that. And that's really, we've got 140 of our top customer facing techies from around the globe in this program called the Ambassadors. And they have to be customer facing, and they have to be individual contributors, so like a pre-sales manager or something doesn't count. They're a massively active community, there's a whole bunch of them here at Radio as well. And their job is really that conduit, that source of information, and also a sounding board, a much shorter range sounding board for R&D. So if R&D want to get a feel of what's going on, they don't have to ask everyone they can bounce off the Ambassadors, which is part of what we do, and that makes it easier. >> So like a filter too, they're also also filtering input from the field, packaging it up for R&D. >> Totally. Yeah, and when you're at an organization of our scale, filtering is really important. Because obviously, you can't have every customer directly talking to every engineer, it's never going to work. (laughs) >> I mean another radio project stay right there, a machine learning based champion CTO to go through all the feedback. >> Yeah, so I started my career, with my previous company doing that, I was the filter. So I'd get a hundred questions a day from various people in the field, and 99 of those I'd bounce right back because I knew the answer. But there was the one that I was like, uh. Then I'd turn around to R&D and ask them. But the great thing was that R&D knew that if I was asking then it was a real question, it wasn't the 99. So the CTO Ambassadors, and what we do in Octo Global field is really a method of scaling that. >> I want to ask you about that because that's a great example of here reputation comes in. Because your reputation is on the line if you go back and pull the fire alarm, if you will, send too many lame requests back, you're going to be lame. So you've got to kind of check, balance there. So that begs the question, how do you do the filtering for the champions that work for you? Is there a high bar? Is there a certain line? Like being a kid, you've got to be this tall to ride the roller coaster. Is there criteria? Is there certification? Take us through the filtering there. >> The Ambassador program is a rotating nomination system. So essentially there's a two year tenure. So what happens is, if you're in the field and you want to be an ambassador, which is a really prestigious thing, then you nominate yourself or get nominated and then people vote on you and you put forward your case, et cetera. Essentially it's a democratic process based on your peers and other people in the company. And then after you're allowed a maximum of two years. Sorry, two tenures so you get four years, if that makes sense, I'm not confusing you. >> John: So term limits? >> Yeah there's term limits, right, we have term limits. And after two terms you have to go out for a year to give someone else a chance because otherwise it will just glub- >> It'll turn into the US government. (laughs) >> But no, it's important to maintain freshness, maintain diversity and all those kind of things. And so it comes back to that filter piece we were talking about before. The reputation is massive, of the CTO Ambassadors. I mean when we started this six years ago as a program, most of R&D were like, who are these Ambassador guys? What value are they going to add? Now, if you're in R&D, one of the best things you can say, if you want to get something done, is what the CTO Ambassador said. I mean, literally it is, you can go and we have- >> John: The routine approach to that. Talk about how you guys add in a new category. So, for instance kubernetes, we saw this years ago when KubeCon was started, theCUBE was there present at the creation of that trend we kind of got it right away. Now Gelsinger and the team sees this as a massive traction layer. So that would be an example, where we need an Ambassador. So do you like just create one or how does that work? >> They create themselves, that's the best thing. So we have an annual conference which is in February, held in Paolo Alto where we all get together along with all the chief technologists, which is the level below me. And the principles, which the most senior field people. So literally the best of the best get together. It's about 200 plus get together for a week. And we are an hour and a half on on one with Pat for example, so Pat's there with all of us in a room. But one of the sessions we do is the shark tank, and there's two of them. One of them is, come up with your really cool, crazy, wacky ideas, and the other one is the acquisition shark tank. So there we get the MNA team, include our E-staff sit in, and the Ambassadors, as teams, will come in and present. We think we should acquire, uh because that's making a big difference. The great thing is, not nine times out of 10 but probably seven times out of 10, the E-staff are going, yeah we know about that, when actually we can't really tell you what's going on but yeah we know about them. But there's the two or three times out of 10 that people are like, oh yeah, so tell me more about them. And it might be a company that's just coming up, it might be 2013 and there's this company called Docker that no one's heard of, but the Ambassadors are shouting about Docker, and saying it's a big, you know. So there's that- >> So white space is too emerging you can see it's a telemetry, literally feedback from the field to direct management on business strategy. >> And our customers are pushing our field in directions faster than maybe R&D get pushed if you know what I mean. >> You guys deserve a lot of credit because Pat Gelsinger was just on this morning with Lisa and me, and we were talking about that. He just came back from the Sales President's club cruise, and one of the comments he said was the sales executive said, hey, who does strategy? Because everything's fitting together beautifully. Which kind of highlights how radiance this all progresses, not like magic, there's a process here, and this kind of points to your job is to fit that pieces in, is that correct? >> Yeah. People always say, as a CTO do you all sit down once a week and talk about strategy? And that's not what you do. There's a hive mind, there's a continual interaction, there's conference calls, there's phone calls, there's meetings, there's get togethers of various different types, groups, and levels. And what happens is there's themes that emerge over that. And so my role specifically, as the EMEA CTO is to represent Europe, Middle East, and Africa's voice in those conversations. And maybe the nuances that we might have around particular product requirements or whatever, to remind people that maybe sit in a bubble in Silicon Valley. >> John: I'm sure you raised your hand on privacy and GDPR? (laughs) >> Just a couple of times, yeah. Yeah, now and again. >> The canary in the coal mine is a really big point that helps companies, if they're not listening to the signals coming in. >> Well you do, and you see a lot. There's a lot of the tech companies that I see, it's often defined as the three bubbles, or your Massimo Re Ferrè, who's now at Amazon. When he was here, did this fantastic blog post talking about the first bubble is Silicon Valley, and the second bubble is North America, and the third bubble is everywhere else. And so you kind of watch these things emerge. And my job is to jump over that pop into the Silicon Valley bubble before something happens and say, no you should be thinking about X, you should think about Y. At an event like Radio I've got a force multiplier because I've got 40 plus Ambassadors with me all popping up at all these little booths you see behind you, and the shows, and the talks. >> And the goal here is not to be a bubble, but to be completely one hive mind. >> And the diversity at VMware just blows my mind, it really does. I think a lot of people comment on it quite often, and in fact I've been asked to be a non-exec director of other companies, to help them advise on their culture. Which is not in tech, in culture, which is quite interesting. And so the diversity that we have here is really infusing people to innovate in a way that they've not done before. It's that diverse set of opinions really helps. >> Well it does. And this, from what we've heard, Radio is a very, there's a lot of internal competition, it's like a badge of honor to be able to respond to the call for papers, let alone get selected. Touch on the synergies, the symbiosis that I feel like I'm hearing between the things that are presented here, the CTO Ambassadors and the customers. Like maybe a favorite example of a product or service that came from, maybe a CTO Ambassador, to Radio, to market. >> Yeah, I'm just trying to think of any one specific one. There are always bits and pieces, and things here and there. I think I should have thought of that before I came on really. I think what you're looking at here is, it's much more about an informed conversation and so it's those ideas around the fact. And also, quite often someone will have a cool idea, and they'll go to the Ambassadors, can you find me five customers that want to try this? Bang, we've got it. So if you're out there on a customer, and someone comes to you as an ambassador and says, I've got a really cool thing I'd like you to try. It might be before, we have a thing called Fling, so it might even be before it's made a fling. You probably heard from Morney how that process goes. Then engage fast, because you're probably getting that conduit direct into the core of R&D. So a lot of the features that people see and functions and products et cetera, that people see. A lot of the work you see, we're doing with the next version if you realized our management platform, a lot of that has been driven by work that's been done by Ambassadors in the field, and what we're doing there. All the stuff you'll see, I've got my jacket over there with NANO EDGE written on it. A lot of the EDGE stuff that you see, a lot of the stuff around ESXi on Arm, a lot of the stuff around that is driven specifically around a particular product range. So a really good example is, a few years ago, probably around four, myself and Ray sat down and had a meeting in VMware Barcelona, with a retail customer, and the retail customer was talking about could we get them an STDC, but small enough to fit in every store. They didn't say that at the time, but that's how we kind of got to it. So that started off a whole process in our minds, and then I went back and we, the easiest actual way for me to do it was to then get a bunch of the Ambassadors to present that as one of their innovation ideas, which became NANO EDGE. I originally called it VX Nook, because we were going to do it on intel Nooks. (laughs) Unfortunately the naming committee wouldn't allow VX Nook, so it became NANO EDGE. And that drove a whole change within the company, I think within R&D. So if you think up until that point, four years ago, most of what we were doing was, how do we run things bigger and faster? It was all like Monster VM, remember that? All those kinds of things, right? How do we get these SAP HANA 12 terabyte VMs running? And really NANO EDGE was not necessarily a product, per se but it was more of a movement driven by a particular individual, Simon Richardson, who had got promoted to Principle as a result, through the Ambassador program. That was driven through our R&D to get them to think small as well as big, you know. So next time you're building that thing, how small can you run your SX, how small can we get an SX? >> John: Small, at scale. Which is EDGE, right? >> And, you know, so get small, at scale, which was EDGE. And so suddenly everyone starts talking about EDGE, and I'm like, hang on I've been talking about this for a while now, but we just didn't really call it that. And then along comes technology like Kubernetes, which is how do you manage thousands of small things. And it's kind of, these things come together. But yes, totally, you can almost say our EDGE strategy, and a lot of the early EDGE work was done and driven out of stuff that was done from CTO Ambassadors. It's just one of the examples. >> What are some of the Kubernetes service mesh? Because one of the things we heard from Pat, and we've heard this before, but most recently at Dell Technologies World, in the last couple of weeks, was don't look down, look up. Which basically means we're automating the infrastructure. I get that, I've covered ad nauseam. But looking up the stack means you're talking about kubernetes app developers, you've got cloud native, you've got services meshes, microservices, new kinds of challenges around instrumentation. How are you guys inside Radio looking at that trend? Because there's some commercial impact, You've got Heptio, you've got Craig and the team, some of the original guys. >> Yeah, yeah. >> As well as you have a future state coming out, with state, pun intended, data, stateless. (laughs) These are new dynamics. >> Yeah, yeah. >> What's the R&D take on this? >> So there's two ways that I really talk to people about this. The first one is, I've got a concept that I talk about called application chromatography. Which sounds mental, but you remember from high school probably, chromatography was where you had that really special paper and you put the dot of liquid on and it spread it to all it's constituent parts. That's actually what's happening with our applications right now. So, we've gone through a history of re-platform. You know, mainframe, blah blah blah blah blah. So then when we got to x86, everything's on x86, along comes cloud, and as you know John, for the last 10 years it's been everything's going to cloud because we think that's the next platform. It's not, but then everything's not going to SAS, it's not all going to paths, it's not all going to Functions, it's not all going to containers. What you're seeing is those applications are coming off that one big server, and they're spreading themselves out to the right places. So I talk to customers now and they say, okay, well actually I need a management plan, and a strategy and an architecture for infrastructure as a service, containers as a service, functions as a service platform as a service and SAS, and I need a structure for that on premises and off premises. So that's truly driving R&D thinking is not how do we help our customers get from one of those to the other? They're going to all of them. >> It sounds like a green screen for media. >> It is, and then the other side of that is I've just had a conversation with some of the best, you know, what these events are like? Some of the best conversations in the water cooler, in the- >> In the hallway, yup exactly. >> I've just had a fascinating conversation with one of our guys has been talking about, oh it's really cool if we got kubernetes cause I could use it right down at the edge. I could use it to manage thousands as a tiny EDGE things. And as I'm talking to him and sort of saying, you know what he's doing, I suddenly went, hang on a second, how does a developer talk to that? He's like, well I've not really thought about that. I said, well that's your problem. We need to stop thinking about things from how can that framework help me? But how can I extend that framework? And so a lot of that- >> Moving beyond just standing up kubernetes, for what purpose? Or is that what you know, the why, what? >> So if the developers there, it shouldn't be all. I'm going to use this new framework to solve my problem or the EDGE if an R&D person would, but people like myself are there to drive them to think of the bigger picture. So ultimately at some point a developer in the future is going to want to sit there and through an API, push out software SQL server, a bit of Mongo over here, some stuff on AWS, go and use the service on our Azure at the same time pushing stuff into their own data center and maybe push a container to every store if they're a retailer and they want to do that through one place. That's what we're building. And you know, driving that, all these bits and pieces you see behind you pulling those all together into this sort of consistent operations model. As I'm sure you've heard many of- >> And it's dynamics not static, so it's not like provisioning the old way. You got to track what's being turned on and off because how do you log off? What goes turns on? What services get turned on? Turned off, turned on. >> If you don't get a theme of really, I suppose not only Radio, but our industry of the last few years, people have always said if that cliche change is constant, right? Oh, change is constant. Yet still architects build systems that are static, right? You guys that just, I'm designing an architect in this new system for the next three years. I'm like, that's stupid. What you need to do is design a system that you know is going to change before you've even finished starting it. More or less started going half way through it. So actually, as I see, I was in a fantastic session yesterday with the Architects around ESXi and VCenter, which might be boring to most, but where we architecting that for scale at a huge way. >> Well, I think that's the key thing I mean this is, first of all, we'd love this conversation because, if you can make it programmable with API and have data available, that's the architecture because it's programmable, it's not static. So you let it morph into however the application, because I think I mentioned green screen, you know chroma keys as we have those concepts here, but that's what you're saying. The apps are going to have this notion of, I need an app right now and then it goes away. Services are going to be provisioning and turning on and off. >> There is a transience, there's a transience to infrastructure, there's a transience to applications, there's a transience to components that traditional mechanisms aren't built to do. So if you look at actually, what are we building here? And what's that sort of hive mind message? It's how do we provide that platform going forward that supports transience? that allows customers to come, I mean people used to use the term agile, but it's been over years and it's not right. It's the fact that literally it's a situation of constant change. And what your deploying onto, it's constantly changing and what you're deploying is constantly changing. So we're trying to work out how do we put that piece in the middle, that is also changing but allows you some kind of constancy in what you're doing, right? So we can plug new things in the bottom, a new cloud here, a new piece of software there, a new piece of hardware there or whatever. And at the same time, there's new ways of doing architecture coming on top. That's the challenge of this, the software defined data centers, almost like an operating system for clouds or the future operating system for all apps on all clouds and all of- >> It's a systems thinking for sure, absolutely. >> Let's put your Chief Talking Officer hat on for a second as we look- >> I thought I've been doing that for the last fifteen minutes. (laughs) >> At VMWorld 2019, which is just around the corner. Any cool ANEA customers that are going to be on stage that we should be excited to hear about it? >> Actually, I was having a meeting yesterday morning about that, so I can't really say, but there's some exciting stuff we're lining up right now. We're obviously now is the time we start thinking about the keynotes, now at the time you start thinking about who's on stage. Myself and a few others are responsible for what those demos are, you know the cool demos you see on stage every year. So we literally had the meeting yesterday morning at Radio to discuss what's going to be the wow at VMWorld this year. So I'm not going to give anything away to you. I'll just say make sure you're there to watch it because it's going to be good. And we're also making sure there's a big difference between what we're doing in Moscone now and what we're going to be doing it in Barcelona when we- >> And when expand theCUBE outside of the United States certainly, we'd love to have you guys plug in and localize some of these unique challenges. Like you said, I agree bubble now the west of the world has different challenges content different. >> Definitely, I think to that end, multicloud is probably more of a thing in Europe than it was necessarily in, in North America for a longer time because those privacy laws you talked about before, people have always been looking at the fact that maybe they had to use a local cloud for some things. You know, a German cloud run by German people in a German data center and they could use another cloud like Amazon for other things. And you know, we have UK cloud who provide a specific government based cloud, et cetera. Whereas in America there was, you could use an American cloud and that was fine. So I think actually in Europe we've already been at the forefront of that multicloud thinking for a while. So it's worth watching. >> It is worth watching, I wish we had more time to, so you're just going to have to come back. >> Definitely, anytime tell me when. >> We look forward to seeing you at VMWorld. We thank you for sharing some insights with John and me on theCUBE today. >> Cool, thank you. >> For John Ferrier, I'm Lisa Martin. You're watching theCUBE's exclusive coverage of VMware Radio 2019, thanks for watching. (upbeat music)

>> Live from Las Vegas, it's theCUBE. Covering Dell Technologies World 2019. Brought to you by Dell Technologies and its ecosystem partners. >> Welcome back everyone to theCUBE's live coverage of Dell World Technologies here in Las Vegas. I'm your host, Rebecca Knight along with my cohost, Stu Miniman. We have two guests for this segment. We have Honore LaBourdette. She is the VP, Global Market Development, Telco Business Group. Welcome, VMware, thank you, sorry. >> Thank you, yes. >> Welcome. And we have Kevin Shatzkamer, Senior VP, Networking and Solutions, Dell EMC. Thank you both so much for coming on the show. >> Our pleasure. >> Thank you. >> So Kevin I want to start with you. There was a big announcement this morning, signing with Orange of France. Tell our viewers a little bit more about this. >> Yeah, sure. So, I think as overall Dell Technologies continues to focus on helping our service providers through what is a very complex transition, both in their business, in their operations, in their technology investments, in the operational skill set gaps, in the business models, the architecture's use cases kind of comes across the board of how their businesses are evolving. What we continue to do is focus on a core set of telecommunication service providers that we can partner with very deeply to help in that transformation and use the knowledge gained through that collaboration as a means to expand the Dell Technologies capabilities globally. So, I think that the belief is that when we help solve problems, it not only benefits the service provider we're working with, it benefits the industry as a whole with the lessons learned, so that we can then contribute back. >> And so far, there's been some enthusiasm about this? >> There certainly has. I think it's been a big day for us. Obviously, the first two days at Dell Technologies World, we're extremely focused on new product introductions across the Dell portfolio, and today, with the opportunity to expand the messaging and announce some of the great things we're doing with partners, we're doing with out customers, and we're doing within the ecosystem, I think we continue to drive a very positive message. >> Honore, the networking component is something that we know service providers have a need and is ever-changing. We've watched that expand greatly in the VMware portfolio over the years. I've done plenty of interviews with telcos talking about things like NFV, network functions virtualization, but the big thing everybody's been talking about, the last couple of years it feels like, is 5G. So, maybe we could start there, but talk a little bit about what you're hearing from service providers and how VMware and VMware plus Dell are helping to meet some of those requirements. >> Sure, well, needless to say, 5G is the topic of every conversation we have with our telecommunication customers, and I think that there's a number of areas around 5G that are most prevalent in those conversations. One is really how does the service provider get a return on investment for the huge amounts of monies that they're investing in this infrastructure, right? So, 5G is a new infrastructure, a new technology, that's going to require a refresh of the entire infrastructure. And so, while they're making all of those investments, and they are doing so very aggressively to have a first-mover advantage, in terms of the first to deliver on a 5G technology, they want to work with vendors who can, in fact, accelerate their time to a return on the investment for that infrastructure. So, many of our conversations are really focused around how can we help these service providers actually accomplish that, right? Not just build out, or take advantage of a software-defined infrastructure and all of the technologies that both Dell and WMware offer to them under the umbrella of the Dell Technology Companies, but also, how can we help them accelerate services that they want to to put on top of the 5G technology? I think one of the key differentiators of 5G over its predecessors is that the industry has recognized that it's going to require partnerships in order for the service providers to really get their return on investment. And that's where the partnership with VMware and with Dell and the work that Kevin and I are doing together to focus on service providing is really anchored, right? It's bringing together those partnerships, so that these telecommunication customers can take advantage of our technology and do it very quickly. >> So, there's a real acknowledgement of the need for partnerships? >> Yes. >> So then, how do you show customers that the VMware-Dell partnership is the right direction? >> Well, needless to say, it's anchored in our technology. Kevin and I have been working together for a number of years now, and our partnership really started out focusing on just making sure that the components of the stack worked as promised, right? That we could deliver a high degree of confidence to our customers that when they software-defined the infrastructure on Dell Technology hardware, and then layered on top of that, their virtual network functions, that it would perform our outperform their legacy, bare-metal, vertical-stack equipment. Over time, however, our partnership has progressed to where we're actually collaborating to bring new technology to market together. And one example of that is the City of Las Vegas. We recently announced a Smart City IoT use case, and that technology, that solution, was co-developed with NTT, Dell EMC, and VMware using VMware software, Dell hardware, as well as Dell Storage, Dell Data Analytics and Intelligence, and NTT's infrastructure and points of presence. >> Yeah, I think there's both a technical reality and an operational reality to the technologies that we speak of, right? The technical reality is that the transformation that the telcos are going through around NFV and the direction toward network edge, edge computing, cloud environments, is really just software-defined data center similar to what we've done on the IT side for a long time. So, the technologies that the telecommunications industry is adopting are the technologies that both Dell EMC and VMware have been working on for a very long time. The operational reality is that just taking what you've done in IT and applying it into a telco network is not sufficient. Understanding of the workloads, how those workloads layer on top of infrastructure, understanding that those workloads are in a transformation of their own, and that virtual network functions were not designed to natively consume and compute. They were designed for network appliances, and that there are still requirements that they drive down to the infrastructure was, I think, where Honore and I have been investing for the last several years, right? How do we complement the broad capabilities of both Dell EMC and VMware in IT virtualization software-defined data center, and bring in telco service provider networking expertise and domain knowledge that we can use to be able to really ramp up and accelerate the partnerships we have in the service provider industry? >> That's great stuff. We actually got to do an interview on the smarter cities earlier this week, and a fascinating discussion to see how there's, Kevin, I like what you laid out there. When I look at this space, scale gets talked about a lot, but you talk to telcos, they have a little bit of a different scale, and the management for these kind of environments is also quite a bit different than if you were talking to the enterprise. Are those some of the key items? Where would you say your focus? >> I also think that even further. That the challenges of scale that have been solved in the public cloud are a different set of challenges than the telco industry is really trying to wrestle with, right? In the public cloud, we're taking about a very small number of facilities, and we can build a homogenous architecture within there. We define a standard server. We replicate that server across a rack, replicate that rack across rows, replicate those rows across a data center. The reality is, as we get further and further towards the edge of the telco network, it looks more heterogeneous, right? I need GPUs for particular instances. I have cloud-native applications. I have virtualized applications that sit inside of VMs. I have native Linux environments. I need to handle dense networking topologies. I have east-west traffic, north-south traffic that I need to take into account. And I think that what we've figured out and what we've learned in automating and orchestrating the public cloud is how to handle hundreds of thousands of things at single-digit number of locations. And what we're talking about here is hundreds of thousands of locations with single-digit number of things. >> And that's another key area of the collaboration between the two groups, in terms of how we deliver value to our telco customers. So, rather than us working in silos and delivering yet another disparate technology for managing the edge, cloud, or all these different locations, we're working together so we can bring a cohesive technology to market for them. >> That's right, I think the infrastructure demands and openness and a willingness to be a productive member of a complex and consistently changing ecosystem, and I think that, obviously, Dell EMC does that in our way. VMware does it in their way, but there's clear recognition that the better capabilities are when we work together to really drive the platform and bring the true capabilities of the broader Dell technologies together. >> So, telcoms is a hugely competitive industry, and as you've talked about, there's a lot of challenges, and it's a real transformative moment for this sector. Can you lay out some of sort of what you're thinking about for after 5G, which as you've said, is a hugely expensive investment for these companies? But sort of post-5G, what are we looking at? What's on their minds of your customers? >> So, I don't know that there's going to be distinct, post-5G event, right? I think that 5G, in and of itself, is going to take some time to roll out and proliferate, to the extent that its predecessors is now deployed across all locations all over the world. I do think that 5G, in addition to the infrastructure technology, or the refresh of that technology, a lot of what is going to happen around 5G is, in fact, the applications and use cases that's going to take advantage of 5G. If we about what 5G is capable of enabling, it doesn't just address consumer applications. 5G also will address enterprise applications. And that opens up a whole world of innovation, and again, applications, partnerships, and vendors coming together, who can really help the service providers put those pieces together and deliver on those applications. There's already talk about 6G, although it's very limited. So, it's easy for me to say what's coming next after 5G will be 6G, but I think that there's still a lot of activity and a lot of innovation that will happen around 5G for some time to come. >> Yeah, we know that standards and the consortiums always have to be working. I was looking at terabit ethernet on the networking side. So, I wanted to help kind of bring this conversation together. If you have maybe a customer example, love if you could share who it is, but if not, give us a little bit of anonymity around what it is to help highlight this partnership. >> Sure, I think Honore shared the City of Las Vegas as a great example of where we're enabling the Smart Cities use case. We can speak to MetTel, in terms of the capabilities of Dell Technologies to be able to transform their NFV offerings and really help them bring NFV to market at scale. We can speak to at least one tier-one service provider in AMIA that is delivering a full-stack offering, in which we extended the capabilities of our Ericsson partnership that both Dell EMC, as well as VMware have, to build a complete stack offering of Ericsson, VMware, as well as Dell EMC. >> Yeah, and to Ericsson, there's some of the edge computing in there. I've talked to them quite a bit about what they're doing on their edge offering. >> Yeah, so I think we have a number of examples that we also can't share as publicly. But we continue to collaborate. I think we're driving fantastic innovation. The industry is responding extremely favorably across the board, and I think that the strategy that we have jointly to not just develop technology, but really change the way we engage with telecommunications organizations and service providers to work with them well before they're ready to deploy technology, and also, help them scale their own operations and understand this transformation is really key to the success here. Because just having the best technology at this inflection point in the industry is not enough. We really have to partner to help them understand how to operationalize and monetize that infrastructure. >> And we do have a number of innovation projects, with regards to the edge and far edge with some of the top-tier service providers, in particular, in the Americas, where we're working together for edge solutions. I've got to hear what this far-edge is in a future conversation, because I thought I was getting my arms around it, but -- >> I know, it was edge, and now it's edge and far-edge. >> That's for Dell Technologies World 2020. >> That's right. >> Honore, Kevin, thank you both so much for coming on theCUBE. >> My pleasure. >> Thank you. >> Thank you. >> It's a great time. >> You are watching theCUBE's live coverage of Dell Technologies World. There's more to come after this. (upbeat music)

>> Narrator: Live from Chicago, Illinois, it's theCUBE, covering VeeamOn 2018. Brought to you my Veeam. >> Welcome back to Chicago everybody. You're watching theCUBE, the leader in live tech coverage, and we are covering VeeamOn 2018, #VeaamOn. My name is Dave Vellante, and I'm here with my cohost Stuart Miniman, Duncan Epping is here, Chief Technologist, Storage and Availability at VMWare and the world's number one blogger in virtualization, Yellow Bricks, yellow-bricks.com. Duncan, thanks very much coming to theCUBE. Good to see you. >> No problem, my pleasure, it's been a while. I actually hoped to be on the show probably six, seven, eight years ago, I don't know how long it is, but I've watched many episodes. So it's great to be part of it. >> Well great, Duncan one of the biggest problems is you're so busy, every year at VM World you were totally booked up, so no thanks so much we're so glad we could do this. >> So Stu and I remember the peer insight we did many many years ago back when we had Boonyon on recently, and he was talking about when VMWare sort of created virtualization, it pushed the bottle neck around. It created a lot of stress on the storage systems. And WMWare for years dealt with that through API integration and the like and very well sort of covered. But I wonder if you could take us through your perspectives of the journey of storage at VMWare and generally, or specifically, and virtualization generally. >> Yeah, it's a good question. I think everyone that has been part of the community has faced all of the different challenges from a storage perspective. I mean, Stu, you now what kind of problem EMC had when VMWare first started doing virtualization. And I think the key reasons for these were fairly straightforward. When we started virtualization and we started leveraging shared storage systems, those shared storage systems were never designed with virtualization in the back of their minds. They were designed for physical workloads, maybe one or two machines connected to it, you know in larger volume it may be 10 or 15, but not 10 or 15 physical hosts with hundred of virtual machines. So we started noticing is that from a performance perspective systems were lagging, we were doing all sorts of things to the storage systems that they weren't expecting, virtual machine snapshots. They were seeing IO patterns that they had never seen before. Instead of sequential IO we had a lot of random IOs so we had to start doing different things from a storage perspective so as you said, we started with APIs, we had the vSPhere APIs for IO filtering, we have the Divi APIs, the array integration, so that we can offload some of the functionality, but of course on top of that what we started doing within VMWare is we started exploring what we could do smarter from a storage point from our stance. So not just looking at how we can help the ecosystem, but also what we can do from our perspective, so there were two main efforts over the past couple of years. The first one is virtual volumes. It has taken a while before the adoption ramped up. I think part of that is mainly because a lot of our customer base was still on vSphere 5.5. Now that we're starting to see broader adoption of vSphere 6.0 and actually 6.5 and 6.7, we're starting to see the adoption of stuff like virtual volumes go up as well. That is also due to the fact that our partners like Pure Storage, Nimble, HP with 3PAR has been pushing or have been pushing VVols tremendously. So they've done a great job, and we're starting to see a lot of customers adopting VVols, and that way we're getting around some of the limitations that we have from a traditional storage perspective. >> Explain that, what are customers telling you about the benefits that they're getting out of VVols and VVol and VVol adoption? >> Well, there's two main things. It kind of depends on what kind of problems you're facing, but a lot of customers come to us with management issues and scalability issues. From a scalability perspective we have larger customers that literally have thousands of volumes. If you look at an E6 cluster today you're limited in terms of the numbers of volumes you can connect to a cluster. So that's one thing. As soon as they start moving to VVols now they're not managing those individual volumes anymore but they're managing the storage system as a whole, and they start creating policies, and that's where the management aspect comes into play. So it becomes a lot easier to manage, because instead of having thousands of volumes to select from, they don't normally have to look at a spreadsheet, for instance, to figure out where to place a virtual machine, now they simply make a policy and the policy engine will figure out where to place that virtual machine. >> Dave: It sounds like cloud. >> It actually is, you know, the cloud version of, cloudified version of storage I would say. But it brings a lot of benefits. And the funny thing is that we've been talking about policies and policy engines for a long time, even in the cloud, but try to come up with one cloud that actually has a decent policy engine. Hardly anyone has that today. From a storage perspective I think storage policy based management framework that VMWare has is quite unique. Well now we're starting to see that popping up in other areas, and that's the strange thing about it. >> Always back to the software mainframe Stu. >> Yeah, and Duncan one of the things we've really seen, a transition for, it took us about a decade to try and fix storage in a virtualized environment, and today most things are built either understanding virtualization, or at least that's part of the puzzle, and then of course VVols led us into was the ability for vSANs. Help us kind of transition that threshold as to how that's just kind of a given underneath for vSAN and other solutions like it. >> Yeah, if you look at vSAN it has been around for a while. The beta was in 2013, as you guys know. We have a large adoption, at least we saw a large increase over the last couple of years, I would say the last two years. You guys have spoken with Yangbing before, so you know about the business side of vSAN, I'm not going to cover that, but if you look at it from a technology perspective we stared developing this 2008, 2009, that's when we started thinking about what we could do different from a storage perspective. There were already some companies doing something in the hyperverge space and we figured we could do something significantly different than they were doing. They had a storage solution that sat on top of the hypervisor, we own the hypervisor so we can create something that sits within the hypervisor, and that's when we started looking at including these different technologies, so we started looking in how can we introduce things like deduplication and compression? What can we do with for ROBO solutions? Can we do something like stretch clustering in an easy way? There are a lot of stretch cluster solutions out there, but if you look at a stretch clustering solution today it typically takes weeks to implement that. If you look at something like vSAN, it was our aim to actually to be able to deploy something like that from a storage perspective within hours instead of weeks, right? And we've been able to achieve that, and it has been a huge undertaking, but I think it's fair to say that it has been rather successful. >> All right, Duncan, help connect the dots to where we are here at VeeamOn. It's funny, I think Veeam started out heavily in virtualization, still heavily involved in virtualization, they've got a v in the beginning of their name. When I hear the keynote this morning, a lot of hyper, reminded me of before we had, before hyperconverge fully took over, VMWare tried to call it a hypervisor converge system around VMWare, so talk to us a little bit about data protection, the Veeam relationship and how that fits into things like vSAN and vSphere? >> Yeah I think, I talk to a lot of customers as a Chief Technologist, it's part of my role to talk to customers and have discussions about what's on top of their mind. Data protection is always one of those things that comes up. I would say it's always in the top three. Whenever you talk to a CIO, a CTO, protection of the data, availability of data, resiliency, reliability, it's fairly important. Veeam of course, for us, is a great partner. Primarily because of the simplicity of the features and the products that they offer. Whenever I talk to a customer and they explain how difficult it is to manage their backup and recovery solutions I always point them to a partner like Veeam simply because it's going to make their life a lot easier if you ask me. And I can see that Veeam is slowly transitioning. As you mentioned, the v is in front of the name. The v is in front of our name as well, but we know that it's not, the whole world isn't just VMWare and the whole world isn't just virtual. There's a lot of other different solutions out there, and actually Veeam's looking at other revenue streams as well. I would argue, though, if you're looking at something like the edge space which I think that more or less exploring at looking at things like IoT, there's going to be some form of virtualization within that, whether that's VMWare based or another solution of course is going to be the question. That is something that we'll need to figure out in the upcoming years, but I think there's a big opportunity out there. If you ask me, the keynote was really interesting. I kind of missed the end of details. I'm hoping that the closing keynote is going to give some more details on what they will be doing in the IoT space, how they see their solution evolving from that point of view because it's a market that's still being developed, but that's definitely going to be interesting. >> So Duncan it's interesting to hear you say that when you talk to customers data protection is in the top three, even amongst CIOs. It used to not be that way. Data protection was always a bolt on, it was an afterthought, it was kind of one size fits all. What's changed? >> Well I think the importance of the data has changed. If you look over the last 10 years whenever you talk to any company out there that has lost any significant amount of data they understand what the value was of the data that they were hosting. I think the big difference over the past 10 years is in the past we had applications like email, maybe some file services and that's it. But now everything revolves around applications, and that's also the shift that I'm seeing in the industry. Also from an IT perspective, right? In the past, over the past decade I think everyone has been focused on the infrastructure layer. If you look at something like VBlock, very much infrastructure focused. If you look at something like hyperconverged solutions, very much infrastructure focused. But now whenever we talk to customers, customers are more and more interested in what we can do for the application layer. What kind of benefits do we have for Exchange, for Oracle, for SAP, you name it? I think that's also a big change that's happening in the industry right now. One of the things from a technical perspective, and there may be others, but when VMWare really became prominent it was wonderful but we were reducing the number of physical resources, and the one workload that took a lot of physical resources was backup, and then sort of Veeam swept in and took advantage of that sea change. What's the technical constraint now when you think about things like multi cloud and SaaS and IoT, data's much more distributed, it's out of the control necessarily of a single platform. So from a technicals perspective, what's the big challenge and sort of the gate to architectures today? >> Well as you said, the distribution of data is the big challenge as it stands right now from a technical perspective. I think the biggest challenge that most of the players in this space, and not just Veeam, some other players as well, will have is trying to figure out how to control and manage their data. Other platforms are facing similar challenges. And no one really has solved this problem yet. We're starting to see some players in this space that have solutions that sit out in Azure, that sit out in Google Cloud, but it's a very challenging solution, and I think if you ask me, and this is something that I've said internally as well, the company that is capable of managing and owning the data is the company that's probably going to be most successful in the cloud war that's now happening. I think that's the most critical aspect. Workloads can move around, but data is very difficult to move around and own as well. >> Duncan one of the discontinuities we see in the marketplace that you mentioned earlier, wondering if you can talk to, in the enterprise in the data center, how do we get them to get to that next version? Comfortable with it, it's stable, it works. I look at the cloud, I'm running Microsoft Azure or AWS I'm running the version that they want. How do we help close that gap? Because from a security standpoint, from a features standpoint, we need to move there, but you know it seems to be just one of the greatest disconnects we see between kind of my data center and somebody else's cloud. >> That is a great question. I think we had a lot of challenges in the past. I think it's fair to say with vSphere 5.0 it was a great release, 5.5 among great releases. But the challenges that we have from an upgrade perspective was typically V centered and all of the components connected to it. It's not just the vSphere platform but if you look at the vSphere platform, the challenges that we had were all of the components integrating with it, whether that's something like vROps, VRA's, or VREalize Automation, but it could also be something like Evermar or maybe Veeam. So there were so many different components we had to take into account. So what we started doing within VMWare was simplifying the architecture from a vSPhere perspective. If you look at vSAN for instance, it used to be a solution where we had multiple functions spread out across different virtual machines. I'm now trying to bring that back into a single virtual machine again. Actually dumbing it down, making it easier to upgrade. So that is something that is actively happening within VMWare, and it is something that we started with 6.0, and that's also the reason why we see the adoption from 6.0 to 6.5 and 6.5 to 6.7, is at a must faster pace than 5, in the 5 code stream, so 5 to 5.1, for instance, took a lot longer for a lot of customers or 5.1 to 6.0, took extremely long for a lot of customers. It's the key reason is complexity from our infrastructure stand. While we're changing that, we're evolving that in the upcoming years. >> Duncan it's the last question here, but as the technologist, things that you're looking at that are exciting to you, that you know, get your juices flowing? >> Yeah, that's an interesting one because it's something that I've been thinking about recently. I've been doing vSphere for the last, well wasn't even called vSphere back then, but I've been doing this for the last 12 years, virtualization. Thirteen years maybe something like that. At least as a consultant and then as a technologist and technical marketing, but recently I'm starting to look more and more at the edge space. For computing, IoT, I think that's a really interesting space, especially because there isn't really significant market. Well, there is a significant market out there, but there isn't really one player out there that really stands out. No one has really figured out what customers would like to do with it and how our customers are going to use it. So the edge computing space and IoT's a really interesting thing and especially because of the distributed aspect is one of the things that I've been always been passionate about, vSphere clusters, which is a distributed mechanism. So distributed computing is definitely something that has my interest. >> All right if you care about virtualization, VMWare, follow the yellow brick road, yellow-bricks.com. Duncan, thanks very much for coming on theCUBE. >> Thanks for having me guys. >> You're welcome. All right, keep it right there buddy. We'll be back with our next guest. You're watching theCUBE live from Chicago, VeeamOn 2018. We'll be right back. (techno music)

>> Announcer: Live from San Francisco, it's the CUBE covering Pure Accelerate 2017. (upbeat music) Brought to you by Pure Storage. (sparse percussion fading) >> Welcome back to San Francisco. We're at Pier 70, and this is Pure Accelerate. And this is the CUBE, the leader in live tech coverage. I'm Dave Vellante with my co-host David Floyer. First segment of the day. Welcome! >> Thank you. >> Dave: Todd Graham is here. He's the Vice President of IT Infrastructure at ScanSource, Inc. >> Thank you. >> Dave: Axel Streichardt, who's the Director of Business Applications Solutions at Pure Storage. Gentlemen, welcome to the CUBE. >> Thank you. >> Thanks. >> Okay, so let's get right into it. Well, if we start with ScanSource, what does ScanSource do? Set up the interview with just a little background. >> Sure, so we are an international technology distribution company. We have been around since 1994, public since 1994. Today we're in the US, North, we're in Europe, Latin America, and we are quickly growing to 45 to 47 locations around the globe. We focus, very vertically focused, on technology such as telecommunications. Recently we bought a telecommunications services master agency, so we can deal with service and connectivity. Point of sale and barcode is our original business unit. And we do Voice over IP phone systems, videoconferencing, and those types of technologies today. >> You said you started in '94 and you been public since '94. So you started with an IPO? (panelists laughing) >> It was very early. That's correct. (panelists laughing) >> Wow, that's amazing. I'd love, I got to talk to you afterwards. (panelists laughing) >> That's right. That's right. >> That's like Bitcoin or something. Okay, and then maybe we could set up to the segment here. Axel, I saw you speaking here earlier to an audience. >> Axel: Right. >> Maybe describe the discussion that we're going to have here about cloud. >> We, of course, focusing a lot on the different flavors of cloud and the different deployment models that SAP customers are considering today, right? So it could be on premise. Do you want to do it in a hybrid cloud? Do you want it in a public cloud? And we see that, initially, a lot of customers were thinking and considering public cloud as the solution for SAP workloads. And it is interesting that, in recent months, we actually see that from this initial, let's say, movement we see a lot of customers actually reconsidering and coming back, right? And they're seeing that the economics, the flexibility, the agility that they were thinking about when moving certain SAP workloads to the cloud is actually not really the reality. And the reality caught up with them. And they see that the value that they get from Pure Storage actually to run SAP workloads on Pure Storage make way more sense from an economical and also from an agility perspective, right? And we also see that IDC and some other analysts, even SAP themselves, they are actually saying that probably 60%-70% of all SAP workloads will stay on premise. They will not go into a public cloud or cloud deployment. >> Okay, so, Todd. So tell us about, so you're a ERP customer, SAP customer. You decide to move into the cloud. Maybe tell us about that journey. You moved in, and the pendulum swung back. So add some color to. >> Yeah, we were migrating away from our legacy ERP environment and moving to SAP. It was a greenfield opportunity, so we felt like it was the right time to move into the cloud. We looked very heavily at our internal expertise from an applications standpoint as well as an infrastructure standpoint and felt that this would be the right opportunity to move to that infrastructure as a service, application as a service model. And then we could take time to take our center of excellence team around SAP and do knowledge transfer between the cloud organization, the managed organization, and use it as a ramp for us to educate ourselves more around SAP. Some of the other driving factors were simply. Why do we want to go to the cloud? The elasticity, the ease of deployment, the things that we firmly believed at the time were the right decision. And we felt like it could be done quicker by moving to the cloud to do that. >> Okay, so you moved to the cloud, and then it wasn't the experience that you thought it would be. It was >> Todd: Correct. >> Axel mentioned a bunch of factors. The agility wasn't there. The cost wasn't there. Maybe add some color to that as well. >> Yeah, absolutely, we felt like, with the growth of our company through acquisitions, that speed of deployment was going to be key in the future. And we quickly learned that that was not necessarily the case. Everything became request-driven, SLA-driven, versus actually worrying about what was happening within our application itself. And so we just became another customer that was submitting tickets, if you will, in that environment. Stability and performance, we saw some real impacts to the environment that were actually end-user-affecting, which really began to force us to look for some different solutions. >> Okay. So, David, you just participated in a study. We call it the True Private Cloud. >> David: Right. >> So what was happening was it was a lot of cloud washing going on. >> Right. >> And with Private Cloud, we said, "Well, you know, essentially what people want is "to be able to substantially mimic "the public cloud on private." So they can get back that control and address some of the problems. >> That's right. >> So maybe pick it up from there and talk a little bit about. >> Sure, so yes, this, this is reports that we've done on the amount of spend that'll go to hyper-converged types of products and bring it back in-house and offer the same sort of facilities to the end users as you get from a public cloud but in a private cloud itself. So is that how you've done it? Did you take a package, or how did you go, how did you take your work from the public cloud back into the private cloud? >> So part of that was, we did the initial cost analysis of where we were at. And that was one of the main drivers behind, we really can do this in-house ourselves. That's when we began looking at partners that could help us. It was a perfect time that it had set up within our refresh strategy around our traditional storage and compute environment for us to really look at what the cost factors were. Could we improve the performance and the stability of that environment and improve that service to our end users? And so those are the decisions that we made, right? And then we said, "It's time for us to bring that back in." We can have control. And one of the biggest things, and it was really more than control, it was that we understood our environment. And that was the biggest thing that we saw a challenge with, was trying to convey the importance of what was happening within our deployment of SAP to the managed services provider. >> So what led you to the Pure decision? Like David said, you got some kind of converged infrastructure, whatever, the metaphor for mimicking public cloud. What led you to Pure? And we could talk about what the solution was. >> Yeah, one of the things was just the simplicity of Pure. At first, when we heard the story, we weren't sure we really believed it. We were like, "This is, this is entirely too simple." The evergreen model was very intriguing to us at the time, because we had been in that traditional storage and compute environment where, every three years, we had a massive project and do a forklift upgrade with choose any of the providers. And it was, is what we were doing. We were looking to set ourselves up for SAP HANA in the future. We wanted to build an infrastructure that would allow us to get there. And in all of the due diligence that we did, Pure came out on top with that, with a lot of the story around their compression and dedupe capabilities. Performance around IO was just extremely compelling at the time. >> So you got to love this story. >> Absolutely. >> I mean, you hear this a lot from customers? Is this a unique situation maybe? >> Yeah, we see this a lot from customers. Actually by moving SAP workloads, mission-critical workloads, now to Pure Storage. And what really, it's not just about the evergreen and the simplicity, right? What also resonates very well with customers today is our story around the data platform, right? So that's not about storage anymore. It's really about providing a foundation for certain SAP workloads, and you can seamlessly go from, let's say, typical Oracle SAP deployment, and you can start with HANA deployments. Actually, by using our solution, you can actually reducing the cost by up to 75%, right? So these are all compelling reasons, and this all without any configuration changes or any setups that you need specifically for SAP workloads, right? It is so simple that you can run various SAP workloads on the same platform. And to move this, actually, to another angle is, What if in the future you want to do analytics, big data, internet of thing? Again, it's the same platform, it's the same foundation that you can run all these various SAP workloads on. And I think this is a very compelling story. >> And it's interesting for us. It's not just SAP workloads that are running in that environment. >> Oh, really? >> We're, it's, it's a mixed environment, so we're running everything else on top of that FlashStack today. >> Dave: Well, you've done a lot of work. >> Axel: Sure, yes. >> Well, I've got one other question I'd like to ask you about landscapes. See, you're a big international set of companies that you are servicing. So from a landscape point of view, did you want to centralize that onto one landscape or multiple landscapes? And I would have thought that's an area as well where using Flash was a great advantage that you could actually. >> It is centralized today. And then as we grow, we are giving consideration to, Will we have multiple instances across the globe. But today it is centralized and will be so probably for the next 24 months. >> But what you described earlier, Todd, was this horizontal infrastructure layer that could support mixed workloads. But there's got to be some kind of software, something in the middle that supports that as well. Did you have to write something to >> Orchestrate >> To support that >> Was it, yeah, some kind of orchestration or management, stack. >> No, today it was all, everything that we're doing today is within the Pure UI or within Wmware and UCS Manager today. >> Dave: Okay, well that'll get you pretty far. >> Yeah, yeah. Yeah. >> So where do you, what do you take away from this in terms of where this market's going? You talked about analysts generally say that most SAP workload's going to stay on prem. I think we would generally agree with that. >> Yes. Yeah. >> It's going to be a long slog before they're ready for the cloud. At least the core, mission-critical stuff, right? Okay, so that says there's real pressure on IT organizations to mimic substantially that public cloud experience. Are we there today? With a lot more work to be done? I'd like both of your inputs on that. >> Right, and that's the beauty of it. We're actually providing it, at Pure, the various flavors of cloud. So if customers want to actually go from physical to virtual, we are supporting this, because you can actually run your virtual SAP workloads seamlessly on our storage array. At the same time, if you're already then moving to the next level and you want to have a private cloud environment, right? So we have all the components and capabilities actually built into our product that you can do things like self-service, right? You can have chargeback. You can have all the deployment, right? So all of these features that actually make up a private cloud environment, so we have them in our mix already, right? So we more or less have everything ready for customers today. And if they want to actually go to a hybrid cloud, that's why I'm saying. 30%, maybe, to 40% of SAP workloads might go into a cloud, into a public cloud or a hybrid cloud environment. And we're actually also providing this hybrid cloud capability that you can move workloads seamlessly to an Azure, to an AWS, or to Google Cloud. So we just heard this morning we have this capability to move certain workloads seamlessly from on premise, from on premise Pure, onto AWS, for instance. So we have all the ingredients, so throughout this entire journey that the customer wants to go through, that they can actually move along with this one data platform, and that makes it. >> So, Todd, how do you decide now, knowing what you know, what goes where, what to put in the public cloud, what to put on prem, what's eventually going to be hybrid? >> Well, and we have adopted a strategy of Cloud First, which means, Will the workload or will the application fit in that as-a-service model? Does it necessarily mean that we're going to put everything there? We still believe that most mission-critical, anything around the RP, will most likely remain in-house. And one of the main differences that we saw was the availability in uptime that the Pure system gives us around what we could see that the manu-services providers could provide. And downtime is really not tolerated, and it's one of those things that we need. And when it's down, we've got to have things back up, and we need the availability to our end users. And as we expand across the globe, we're becoming more of a 7 by, maybe today we're a 6 by 20. We're not fully 7-by-24 shop yet. But we're getting to that, and so we're looking at the infrastructure that will help us achieve that goal. >> So you're looking at cloud as an operating model more so than a destination. Is that right? >> Todd: That's correct. That's correct. >> And of course, there's the destination aspect of it, which is a function of, what, performance and cost, and. What do you look at? What are the determinants there? >> Yeah, so performance is obviously key for us. Cost is always an important factor, but it's probably number 3 or 4 on the list, right? Availability, uptime, and performance are our key. And if we can get those, we can get the support and the availability that we need, then maybe it makes sense, right? If it's a web application, if it's something that's very straightforward, again, one of the biggest reasons that we go back to bringing it in-house is we truly understood the environment and how things fit together. Whereas in that manu-services environment, it was very difficult to do that. >> And what about security? We haven't talked much about security today. But where does that fit in in your cloud decision? >> David: Especially internationally, the different rules in different countries, for example. >> Yeah, internationally, it's a challenge with all of the data privacy laws and the things that are country-specific, and we're learning a lot of that in Latin America as well (David chuckling) as we begin to move into those markets. But security is absolutely top of mine. We will work with those cloud services providers, but we've talked to a lot of folks along the AWS and the Azure route. And we're comfortable with where the security around the cloud is going. We're talking to a lot of new cloud security brokers to understand what they can bring to the table as well. And it's not just an IT discussion. It's a legal discussion, right >> Right. >> We're having those legal teams come back to us and say, "Well, what does this mean?" Right? Where is the data going to live? And is it going to fit within our retention models and all of the things that we have in place today? >> Alright, good. Okay, we got to leave it there. But Axel, I'll give you the last word. >> The last word? Pure Accelerate. Give me the bumper sticker. >> So we are really excited to have, actually, a confirmation from a customer side to see that the strategy and the direction that we're going here at Pure is exactly on par with what customers are actually demanding and what they want when it comes to SAP or mission-critical workloads. So I'm really glad that we're hearing this now from a customer and get the confirmation from a customer. So I'm just really super duper excited to have Todd here with us to hear from, directly from a customer. >> Excellent. Alright, Cloud First. The CUBE, we hope you're first, we're first on your playlist. Gentlemen, thank you very much for coming on the CUBE. >> Thank you. Thank you. >> I appreciate it. Alright, keep it right there, buddy. We'll be back with our next guest right after this short break. (upbeat percussion music)