>> Narrator: Live from Las Vegas, it's theCUBE covering VMworld 2017. Brought to you by VMware and its ecosystem partners. (upbeat tech music) >> Hi, I'm Stu Miniman here with my co-host Justin Warren, And we're at vmworld 2017. You're watching theCUBE worldwide leader in tech coverage. Happy to welcome to the program, first time guest, Juan Gaviria who's with ADP, and he's the senior director of technical systems engineering. Juan, thank you so much for joining us. >> Thank you for having me. It's a pleasure to be here. >> So vmworld, it's my 8th year coming to the show. I've been part of the community for a long time, but one of the things that people love at this show, about 20,000 maybe a little north of that, it's peers talking to peers. People that dig into the technology, find out what works and how to do things better and everything. Tell us a little bit about your role. I think most of us know ADP. We've gotten checks with the logo on it, or lots of areas of other services. But what's you're role inside the org? >> Yeah, sure. So really quick about ADP to your point, the logo is pretty well known. We actually pay one in six people in the United States, so over 25 million employees we pay. We have over 650,000 clients, and our mobile app, which is really the way I recommend you look at your pay stubs, 401K, benefits, etc., has been downloaded over 12 million times. So the ADP brand is doing well. It's a healthy business. My role specifically is that I manage all computer at ADP, so think about servers, server operating systems, and server virtualization; that's my role. >> Yeah, you brought up mobile, so maybe start there. Pat Gelsinger this morning was talking about kind digital transformation. We look at financial services, how do you reach those users? What does that kind of ripple through to all of the things that you manage? How long have you been there, and what changes have you been seeing? >> I've been there 15 years, and I've seen a lot of changes. >> Stu: 15 years ago they probably weren't even virtualized so... >> No, no, in fact, I remember rolling out ESX2.X and using the good ole mooey, so we've come a long way. And mobile has just been explosive. Ya know, from a product perspective the goal now, it's mobile first, right? So even now if you think about your benefits, when you go enroll in your benefits every year, the goal is to make that experience translate to mobile, and that's a little harder than it seems, but that's the goal for ADP. It's everything mobile. >> Bring us in. What's kind of the scope of what you manage? You said ADP globally what you handle, but what's kind of the team size? How many devices or VMs or however you manage, what are you listed in? >> Sure, so my team is responsible for computers, I mentioned, so think of everything from demand management through operations. We have globally about 50 associates that are responsible for that. We have over 3000 ESXI hosts deployed across seven global data centers with well over 40000 VMs. So it's a pretty good size infrastructure. >> And bring us inside VMware. How long have you been using it? What pieces of VMware in the ecosystem have you been using? >> We have been using VMware, again, since the early days of server virtualization. We're a VROPS customer, a VRA customer, in fact, VRA, we're leveraging it for infrastructure as service to our deaf community. We have, for ADP, thousands and thousands of developers, so just the amount of churn in our private cloud is tremendous. Airwatch, we're a big Airwatch customer, as well. >> Expand a little bit on the developer piece. What do they look for? How does that impact what you're doin? >> Yeah, sure. I don't know what they're looking for cause it's always changing to be honest with you. But we have somewhere around 6000 developers, and they're obviously developing ADP's next generation products. So they're just looking for us to get out of their way, right? They want VMs; they want 'em now. They want containers; they want 'em now. And every day I turn around they want bigger VMs, bigger containers, and it's getting harder and harder. So through VRA, we provide those pools of capacity and then they're able to spin up, tear down, rebuild VMs as needed. On a monthly basis what I see through VRA just in the developer community lab is about 3000 or so actions a month. So it's pretty high amount of change in that environment. >> Based on what was announced in the Kali, particularly around the partnership with AWS, do you thing that's going to resonate with the developers? >> Yeah, absolutely. Most of our, not most, but a fair amount of our next generation products are being developed on AWS, right? So everyone wants to be on AWS. In fact, we're bringing in a lot of college hires, and as soon as they come in they say, "I want to work on AWS." So for us it resonates because what ADP does, security is key, and we want to have a hybrid cloud, so we were actually part of the Lighthouse Program. So we were an early customer. Got to see the logo during the KeyNote which was nice. So, yeah we plan on leveraging that relationship to help us. For example, burst in that DevCloud. >> Unpack that for us. One of the things we look at, when I hear hybrid cloud I need you to explain that because every customer I talk to, it means different things to me, especially, you mention things like bursting that's a little scary sometimes. So maybe explain what that actually means in your environment. >> Yeah, so, in the Dev environment specifically, what it means is, as I mentioned, we get requests that come out of left field, right? I need a 300 gig memory VM and 10 terabytes of storage. You're just like, "Where, I don't have this," right? I don't have hundreds of those. So we can put that capacity out on AWS much faster, and as those projects materialize, we can then bring that back in. So that's what I mean by hybrid cloud for us. >> So you're using the VMware on AWS, you've been testing that out, you said? My understanding is you're also using Vsan, is that separate from that? Cause Vsan's part of the VMware Cloud or cloud foundation suite, a piece of it, so what's your interest been in Vsan, and how does that fit into the entire picture? >> So it is different. For us, the AWS relationship is going to be more of a manage service, obviously. We're actually going to become a consumer. So we're going to feel like our own customers. To answer your question on Vsan, yeah, we've made a huge investment in Vsan, so all of our VM storage, which again is 40000 VMs worth, which is well over 4+ petabytes of storage, we're moving that all to Vsan. >> What's happenin to all those arrays? >> They're going to be gone. >> Yeah? >> They're going to be gone. >> That's a really big move. Can you, you got to take us back, ya know. How did you is this a top-down or, ya know, bottoms-up walk us through some of that. >> Yeah what started that? Like how did you come to even begin contemplating replacing all of your storage? >> So it's been both to answer your first question. Both top-down and bottom-up. We've been looking at the technologies for a while, and just kind of keepin close to them. At this point, they're mature enough that we feel they can run our business-critical products. And it's been a journey, right? For the last year, we've spent looking at all the different market leading technologies and figuring out which ones make sense in an environment our size. How do we operationalize this thing? So it's been a journey and this is the beginning for us, so we're actually, as I speak, we're starting to deploy our first Vsan clusters in production and we're deploying it in hundreds of servers at a time so it's exciting and interesting times for the team and I. >> Yeah, one of the interesting things, some people look at Vsan and they're like "Oh well it's kind of small deployments," but we had some of the VMware people on earlier today, and they're like, "We're deploying internally," but it's lots of clusters because if you tell me hundreds of servers, I'm like, "Well that's not a single cluster that's lots of clusters." How do you carve that up? How do you manage that? How do you roll that out? What does that look like? >> That's the trickiest part, right? And, by the way, as we look at different solutions, the cluster size became one of the reasons why we chose Vsan. >> Okay. >> A lot of the other solutions that are out there will limit you to about eight node clusters, and to your point, we have thousands of hosts. That's hundreds of clusters. So Vsan gives us the ability to have slightly larger clusters. Today we're going to look at about 16 node clusters to start. That seems to be where VMware is going as well, so we'll follow their lead. We figure they know what they're doin'. And we'll manage that using Vroms as well. >> Yeah I was curious as to what was actually driving the change to Vsan, and what was it about Vsan that said, "Yes! This is great! "This is the one that we're going to pick." You've mentioned cluster size, were there other things that made you sort of decide that Vsan was the right choice for you? >> So to me, the way I look at Vsan from a Vsphere perspective is that they've made storage a feature. And our Vsphere administrators, they know how to run Vsphere and now they just have another feature. So that was one of the main reasons, just the operational efficiencies from a team perspective. There are a lot of other reasons as well. Security: some of the other competitors out there, for example, didn't have encryption when we were looking at it, which is, everything we do revolves around security, so that was another key reason for Vsan for us. And what drove us at first was really, with the traditional models, we found ourselves to not be very agile. Because our business is growing so fast, we're building about six months of capacity at a time, and if you can think about the cost of that much capacity at a shot it's millions of dollars, it's kind of sitting idle. So with HCI technologies and Vsan, specifically, we think we're going to be much more modular in our approach and closer to just in time. So we expect significant capital benefits from that. >> So if I hear you right, it's the pooled nature of what you're doing and that the building blocks are small enough that you're not getting to what people usually have is like, "Oh yeah, I have all this capacity and I'm three years in "and I'm still not using a lot of what I run into, "ya know, I overbuy so much because of that." >> Exactly, and think about that first purchase. You've got to sit with finance and say, "Hey I've got to go buy an array "and I've got to go buy a couple hundred servers." Now I don't have to buy that much up front so it's a huge benefit for us. >> And it sounds like it's going to be cord deployments as well, cause there are a lot of like the HCI deployments, traditionally, have been for remote office things, or just particular work loads like VDI will be one thing that it runs on, but it sounds like this is going to underpin pretty much everything that you do. >> Pretty much everything, yeah. And in addition to VDI we have a very large VDI deployment that supports all of our customer support reps, and it's going to underpin that in addition to underpinning all of the business products that you use to view your pay statement. >> Alright, so you talked about the finance people, what about the storage people? I have to imagine you had storage admins, you look at it and you say, "Okay are they out of a job? "Are they going to work on new challenges?" Can you walk us through how you approach them? How they've looked at this whole migration? And what happens to them versus the VMware people? The virtualization admins I should say. >> It's a funny question cause I've become a little bit more popular now with the storage scene. They've actually knocked on my door and said, "Hey, anything we can help you with?" But, no, it's a good partnership. My peer and I who run storage, we actually built a team together that's going to help us roll out Vsan so we know that there are skills in the storage team that we can leverage, and our vision of it is that we're no longer going to have Vsphere administrators or storage administrators. We're going to have cloud engineers, and they have to know, compute network storage really cause we view the skills as converging as well. It's not just the software and the hardware. >> How about the management of that though? Are you essentially going to be managing a team together rather than it being separate people managing different people? >> Correct it's one team. >> One team? >> It's really interesting, Juan, I'm just curious, in your kind of evaluation phase, what did you learn that if you had known it at the beginning might have either accelerated or you might have positioned things a little bit differently now that you're ready to kind of this massive roll out? >> I think I would have had maybe stricter entrance criteria. You think about a company our size and all the partners we have. We looked at a lot of different solutions. We spent a lot of time in the lab. Where in the end we knew that, for example, an eight node cluster, or not having encryption, were showstoppers, but yet we spent the time in the lab to do that, so my recommendation or advice to my peers out there is come up with good criteria that you know you have to have, and then from there, do the paper exercise and bring in the ones that you know will actually be able to get to production. >> What was that entire kind of evaluation phase? How long did that take? >> More than six months. >> And can I ask what underlying deployment you're going to use for Vsan? >> From a hardware perspective? >> Yeah. >> Sure, HP servers. DL360s. >> Okay, and what led you to choose that versus, ya know, the Dell people are all lined up to say, ya know, come on we own VMware, ya know, you should do VXrails? >> Vxrail to me is a little bit different than just Vsan, but yeah absolutely Dell was pretty interested in that business as well, and the beauty of Vsan is that it gives us the choice. We've been a long-time, happy HP customer, so for this first phase we'll continue to be with HP, and for some reason, if something changes we know with Vsan we have that flexibility. >> You've been with VMware for quite a while, I'm sure you've been watching Vsan. What are you still asking them for? They've had a very aggressive road map. I think they've got most of the basic check blocks done. I've heard a little bit about the road map, but what's on your to-do list for Vsan or any kind of the associated pieces? >> You mentioned VXrail as an example and the automation that they've brought with rail is significant. It's very valuable. I think they need to bring some of that same automation to Vsan's standalone. So as I think about patching thousands of hosts with Vsan and the drivers and that entire matrix of things. They've got to help us there. I think they've got some work to do in terms of improving the performance management of that because environments this size, managing that manually is too much work. So I think we've got some work to do there. But they've been a great partner. They've been listening to us, so I'm pretty happy about where they're headed. >> Earlier you mentioned deploying VMs and containers, is that like Docker or how do containers fit in? >> So Docker has been sort of a religious debate internally to be honest. Do you deploy it on bare metal? Do you deploy it on VMs? I think right now, we're settled on deploying Docker on VMs, but very large VMs. We're thinking 200 gigs, and the goal will be, we're going to try to do that on Vsan. So we're still in early development there, but that seems to be where we're finally landing on. >> Interesting, and I'm assuming that's Linux on top of the VMs to allow that. >> Yes. >> Alright, well, Juan Gaviria, really appreciate you sharing that really interesting use case. I wish ya best of luck on the rollout, and thank you for being on theCUBE. >> Thank you. Thanks for having me. >> Alright, for Justin, I'm Stu, and we'll be back with lots more coverage here from VMworld 2017, you're watching theCUBE.