Intel and Google Cloud's Partnership
Transcript
>> Hey, how's it going as Keith Townsend principal at the CTO Advisor, I've been looking forward to this conversation. I have a sponsor of the channel Intel who sponsors The CTO Advisor Data Center, and then a good friend from the industry, Wade Holmes, who's the manager of infrastructure modernization at Google. He has a bunch of different titles. I just call him the VMware cloud guy at Google 'cause he's primarily responsible for the VMware cloud solution at Google. We have not had him on the program.
So we're making up for this. Thank you Intel for sponsoring this, and speaking of Intel, we have Justin Van Buren, who is an account executive for the relationship with Google cloud at Intel. Justin, welcome to the show. >> Hi, Keith, great to be here. >> And Wade welcome to the show. >> Hi Keith, awesome to be here with you. >> All right, so we're coming off of a big report in which we can compared all of the VMware cloud solutions, etc, and one of the, let's just get right to the mid of this.
x86 is x86, right? I mean, when I'm thinking about the advantage of VMware abstracting, all of this and Justin, this is for you primarily, when I think about abstracting the data center, the whole point of VMware, vSpheres that I can extract the data center away from me that all of these bits, what's some of the primary advantages of having Intel on-prem and Intel in my public cloud, specifically around the VMware cloud solutions? >> Oh, great question, Keith. Well, essentially first things first, you want everything to work and you want things to work seamlessly, whether it's on-premise or in Google cloud, VMware engine.
So first things first. There's a capability of vMmotion where if you vMmotion from on-premise to GCVE, if you can seamlessly vMmotion across multiple generations of Xeon have on premise and into the latest Intel-based technologies, that's within Google cloud VMware engine. So that's one big advantage. Second is Intel works with tens of thousands of software vendors through the years, and there's a lot of hardware instructions that speed up a lot of the applications, things like VDI or things like, some of your security based applications in that VMware environment.
I'm also, there's been a lot of capabilities that are now in the Google cloud VMware engine. FoR instance, now you can Forex that density VM going from say your five-year-old VMware server, Intel-based VMware server to GCVE, and so all the software optimizations that already happened on Intel and that VMware environment on premise, they can, they will, you can take advantage of that within the Google cloud VMware engine. So you get that consistent predictable application performance and you don't have to worry about that.
It'll just work. >> So you're bringing up a really important point within the infrastructure realm in general, especially when I think about hybrid solutions and Wait, I'd like you to weigh in on this, which is the observability track. I understand the ability to vMotion is current generation, hardWare and being within the same Intel family, Intel to Intel, I know I can be motion from Intel to Intel, Intel to some other x86 is a little bit less. You can't do it big frankly, okay, I get that advantage.
But this observability thing that you mentioned, Wade, as I look at my internal infrastructure and I need to size VDI that runs on-prim versus VDI, that's running public cloud. How does Google VMware engine help me solve that basic observability problem? >> As we look at an environment that needs to move into Google Cloud VMware engine, there's a number of tools that can assist with understanding the posture on premises and then as Justin mentioned, there's a ability to seamlessly move these workloads into Google Cloud VMware engine, based on the abstraction, based from a VMware technology perspective that is now available in Google Cloud VMware engine as a service, and then also the underlying x86 bits, So basically if it runs on premises it's able to run into cloud easily.
So we have tooling that allows for you to understand we have one premises and then be able to move that in seamlessly, and those same tools that utilize on premises can be utilizing Google Cloud VMware engine for day two operations. Or if you, as you go down your modernization journey, you can utilize some of the Google Cloud native services that applause for additional observability, additional day two operation capability, whether it's a cloud operations or whether it's utilizing other some of our data analytics capabilities that are built into Google Cloud platform.
>> So one of the things that obviously comes up to my mind is kind of measuring some of the things that Justin talked about, the relationship of Intel with VDI vendors, whether it's VMware, or even Citrix. There are some optimizations inside of the Intel processor, and Intel chip set that enables better VDI experiences. How do I, I guess the question is, one, is Google VMware engine as a service exposing that Intel base capability out to these other VDI instances like is this, are you guys abstracting the way all of the value that Intel brings other than the point to be able to VMotion on-prem to my off-prem or public cloud instances?
>> Nope, absolutely not. So the service utilizes the same VMware bits that a customer would utilize on premises. So anything that exposed by vSphere for compute or NSX for network virtualization or Vsent for storage virtualization, and those capabilities that take advantage of the x86 extensions are also bubbled up within the Google Cloud VMware engine service. So that's why we can say to our customers that are utilizing the service, if it's running on premises, there's a good chance that it's going to run at the same posture or even better in Google Cloud VMware engine, because we have the latest and greatest hardware within the service.
>> So Justin talk to me about, you're an account executive, so I'm going to hit you with the money question. Like what's the type of customer that looks as a service type offering, whether it's VMware, baremare, etc, entailed type solutions consumed as a service. >> Oh, Keith, the exciting thing that we've seen from Google is that they launched this service in June of this year. I believe now having in 10 regions, so all around the world, and we're seeing a lot of great use cases, but what I would say right now is we're seeing, a lot of customers using it for what you mentioned for VDI.
A lot of customers are using it for a disaster recovery and a lot of customers are using it also to just extend their VMware footprint, and then there's quite a few also that, Hey, they want to get out of the business of managing their own data center, but still like the VMware tooling environments so forth, and we're seeing all those sorts of use cases, and I would kind of turn the more, a hanging fruit, I think over time, you're going to see also a lot more transactional database and a lot more extensive use cases.
The service just launched, I think way to, maybe you could speak to this, but we're seeing as one of Google's fastest rising services, just because it's quite a seamless migration, for Google's customers to use VMware on premise and then vMotion out to a Google Cloud VMware engine. So we're really thrilled with all the use cases and the usability from an adoption, from Google cloud Customers. >> Well, you threw Wade at this. So I'm going to ask Wade a question that did not prepare him for, but I really, you've literally written books on this, on these topics so you can handle it cost.
When I published that we basically spent about $219,000 a year on the CTO advisor hybrid infrastructure, that kind of peak your curiosity. But when I do the math, when I look at the GVE service and I extrapolate that out for a year, that's not a small amount of money. I mean, what am I committing to when I sign up for a GVE service, I might have gone out to write a check for $220,000 a year. How am I consuming this thing? >> So that's the beauty of the service is that you can consume it either on demand and hourly basis.
So if you want to spin up a dedicated private cloud environment within Google Cloud VMware engine, whether it's three nodes or up to 64 nodes, within a private cloud, you can spin that up for an hour and pay for an hour, or you can spend spin it back down, or you can consume it via one or three-year commit contracts. If you know that you have a steady state workload that you're going to migrate into the environment. So this gives flexibility in both how you consume with data center extension, but also use cases such as bursting capacity, DR, Where you may have an event where you want to spin up and spin down resources.
So this gives a lot of flexibility and allows you to optimize your TCO further as you consume the service. >> And while we didn't really measure it as a component of the report that we did, we found that GVE, for whatever reason, you guys spin up faster than the other services, at least in our accounts and the regions that we were in other cloud providers, but you spun up faster and you add it notes faster, meant you will have to dig into that in the later video, but that gives credence to the ideal of I'm using it for DR, I'm using it for bursting, because I do pay for that time.
Once I hit provision in this provisioning and all the cloud providers, I noticed I paid for that time that it takes to actually provision the service. Where are you seeing the most success will fund customer accounts? >> So we're seeing a number of different use cases given the times we're in today, expanding remote workforce with VDI as mentioned on GCVE is a prevalent use case. DR is mentioned, and whether it's utilizing VMware tools or a site recovery manager or other partner tools, to be able to utilize it as either a set utilizer, Google data center as a secondary DR site or utilize in DR across regions, as mentioned, we are available globally in 10 regions today across the world, and then there are just the customers that want to utilize it in a step wise approach in their app modernization journey, they have a number of different applications, legacy applications, costs applications, aren't ready to be containerized.
Aren't ready to be refactored when they're still business critical, and they want to be able to take advantage of the agility of cloud, and that's where GCVE is a perfect fit and be able to now have the best of both rules, the agility of cloud, but utilizing the same operational posture, the same technology posture, same toolings going to have to retrain their people and then able to now also access, allow the Google Cloud native services, whether there is data analytics with big query or AIML or containerize in a step wise approach as this is warranted by the organization.
>> Well, Wade, Justin, I really appreciate you both joining the show and you know what? while smashed I still ask pretty awkward and tough questions and both handed them great. com. You can follow me on Twitter, challenged me. Did I give these guys hard enough time? Do you have questions that you would ask, that you would like for me to relate to them? DMs are open talk to you next CTO dose.
