Latest / Nutanix Weekly / Nutanix Weekly: Nutanix accelerates hybrid cloud with Microsoft Azure - Part 2

Transcript

Nutanix Weekly: Nutanix accelerates hybrid cloud with Microsoft Azure - Part 2 · Nutanix Weekly

WEBVTT 1 00:00:03.630 --> 00:00:16.099 Harvey Green: All right. Welcome Everybody to episode. Sixty-two of the mechanics weekly Podcast. I've got a bunch of the regular group here with me today, Mr. Ben Rogers. How are you, sir? 2 00:00:16.110 --> 00:00:33.829 Ben Rogers: I'm doing well. I just got back from a good Thanksgiving break. Had golf with my uh in laws, and got to do a Table Rock Mountain climb. So i'm feel pretty good these days. Nice! That sounds nothing like mine, which was just uh sitting down and eating and gaining weight. 3 00:00:33.840 --> 00:00:47.710 Jirah Cox: Uh, Gyra, How about you, Mr. Jarra Cox? Hey, man, Thanks for having us back. I will claim somewhere in the middle of the sitting down in the eating uh punctuated by sleeping in and video games. 4 00:00:47.720 --> 00:00:57.400 Harvey Green: Uh: okay, All right. Um, That's sort of still on my side. I don't know how many calories you burn are playing video games, but I guess 5 00:00:57.410 --> 00:01:13.579 Harvey Green: I don't know what were you playing, and I I I just had some of the middle, and it's a dead middle like It's totally on your end of the spectrum. Nice, Mr. Philip Sellers, How are you today, sir? I'm. Good. I'm. Good. How did you spend Thanksgiving? 6 00:01:13.680 --> 00:01:41.859 Philip Sellers: Well, uh, we were on the road. We were in our nation's capital, so I got a chance to show the kids around uh some of the National Mall and museums when you get out of the car. I was just about to give you credit for actually walking around and doing something. But so what the driving tour? Um, but uh, that was good for them. And uh, we had great conversations about uh 7 00:01:41.870 --> 00:01:48.799 Philip Sellers: history and different people. And uh so uh I I I spent some time with the family. 8 00:01:49.120 --> 00:01:56.739 Harvey Green: Nice, all right. Well, that's that's cool. Um! We'll we'll have to, uh see if we can get you back up there when you can actually get out. 9 00:01:56.810 --> 00:02:06.890 Philip Sellers: That's right. Yeah. The uh art museums and uh all the other great great things that we've got there in Dc: That's right. You need get out, walk around and go eat. 10 00:02:07.360 --> 00:02:19.840 Philip Sellers: We saw plenty of food trucks, so you know that's that's a staple there on the National Mall. So uh, can always get yourself corn dog. Nice that it is also true. 11 00:02:19.900 --> 00:02:35.669 Harvey Green: Alright, Uh, we are going today to attempt to focus ourselves a little better than last time. Um, we're gonna jump into, I guess what we'll call part two hopefully part two of two. But you never know with us 12 00:02:35.680 --> 00:02:43.769 Harvey Green: uh part two of the conversation around the tennis cloud clusters in C two on Microsoft azure 13 00:02:44.040 --> 00:02:50.099 Harvey Green: um. The last time that we jump into this. We've got this this very uh 14 00:02:50.420 --> 00:02:59.279 Harvey Green: detailed and extensive blog post, and we probably got down. We say, Jarra, maybe maybe a quarter of the way, or or maybe a ten 15 00:03:01.100 --> 00:03:29.170 Ben Rogers: closer to a quarter. I'll go a little quicker for that. Alright. Perfect? Yeah, They got these big pictures in the middle that they made it helped us make some progress. I remember Andy got wrapped around the statistics. You know the ninety-one sixty-four eighty-three. He was querying all of us if we thought those statistics were accurate. So today's probably more of the the on the bone of why customers and in companies want to want to move in this direction. 16 00:03:29.460 --> 00:03:54.490 Harvey Green: Yeah, absolutely. So. I think I think I hear you're saying, Harvey, like pictures on a blog post is sort of like the the double spacing of a college essay like That's really where the the pound comes in. That's right. So So uh, if anything, it looks like it, it looks like we made progress right we quarter of the way down, but the rest of it is probably a little more detailed, you know, single space, and all of that. 17 00:03:54.500 --> 00:04:01.729 Harvey Green: Well, uh, so we jump in. Um, I know right before we got on actually. 18 00:04:01.740 --> 00:04:29.470 Ben Rogers: Uh, Miss Mr. Bill Rogers, you have a question that I wouldn't allow you to ask until we got on the podcast. So i'm gonna let you ask it that we're gonna we're gonna jump around So we're gonna go to Bullet Point two, which is this on demand elasticity. So I I came from a citrix world, Harvey, you know at, and I've made the move over to new tax, which is a lot of difference, You know, man Running Citrix, you know you're running an applications, or in deploying applications versus running an infrastructure. So 19 00:04:29.480 --> 00:04:47.390 Ben Rogers: this idea of elasticity in the citrix world. It's understood the elasticity could mean, You know, man, auto, scaling the the the infrastructure is gonna come as you need it. You don't have to hit some magic button. It rose as you grow, and it collapses. You class auto scaling elasticity 20 00:04:47.400 --> 00:05:12.659 Ben Rogers: in this cluster world. A hci rural cloud world. I understand that to be a little different where you actually gotta go and let's say you're fixing the cap out on. You know X nodes in the cluster you have to You hit the magic button. So that was the question I asked. Is kind of explain, you know. Auto scaling and elasticity in this environment. This is not so much to azure. This is more to 21 00:05:12.670 --> 00:05:30.069 Ben Rogers: clustered environments and cloud environments. And I'm. Curious about that coming from an environment where it'll automatically appear. I don't have to worry about that. If another two hundred users go on no big deal where in this case, I don't think that is quite the uh, the the configuration there. 22 00:05:30.080 --> 00:05:40.269 Harvey Green: Well, let's let's talk about that. Because it might be, this might surprise you. 23 00:05:40.280 --> 00:05:58.199 Jirah Cox: No, so it's all about how you define the terms right? So the the exact text is on demand, elasticity, right? So the question becomes, who's demand right? You as the human operator or the clusters right? The the logical entity that you're telling to run your workloads, 24 00:05:58.210 --> 00:06:16.049 Jirah Cox: and the answer really can be, it can be either right. You can say I I need more capacity, right? Something's going to get deployed tomorrow. It needs more space. It's some new hires. It needs more desktops, whatever you can know what the catalyst is. Uh, or of course you can automate it right? So actually there's another blog blog post Um and and I'm, sure we 25 00:06:16.110 --> 00:06:24.470 Jirah Cox: we we also uh podcasted about it. But there's a you can automate that right, because you can run that in like through X play in prism 26 00:06:24.480 --> 00:06:43.790 Jirah Cox: to say, Hey, we're We're hidden seventy. We're hit eighty percent. Push the button called the Api run the script. Um basically hit the button that you would hit in the Cloud portal. Console to say, Give me a fourth note. Give me a six node, and of course you could automate that the other direction, too. Right demand is down. It's night time. Whatever inject that node give it back. Don't pay for it. 27 00:06:44.390 --> 00:06:47.010 Harvey Green: Do the things, score the points when the game 28 00:06:47.480 --> 00:06:53.360 Philip Sellers: well, and and today's the perfect day being cyber Monday to talk about elasticity right? I mean 29 00:06:53.370 --> 00:07:15.860 Harvey Green: all the retailers of the world. They're They're riding the thick of it today, doing this exact uh exercise, trying to keep uh their dot. Com alive to take orders. Right? Yeah. Hopefully Profitable d loss, attack right and and and not uh run into things like what happens when you try to sell Taylor's Loop concert tickets. 30 00:07:15.870 --> 00:07:45.400 Philip Sellers: Yeah, yeah, My family was on the receiving end of two very lucky tickets. Uh, but apparently uh, according to my daughter, you had a better chance of getting into Harvard than getting Taylor Swift tickets. Uh so tell her you did number one. It's hard trying to do Number two. That's right. You go to Harvard Um scholarship. That's right. 31 00:07:45.410 --> 00:07:46.380 Philip Sellers: Yeah, 32 00:07:46.410 --> 00:08:14.760 Ben Rogers: that would work. But you know this is an interesting concept. When you talk to customers, cause customers that are coming from a three to your architecture, and you talk about web design. I don't think a lot of times they really understand this concept of elasticity, and trying to make it so easy to you, have an infrastructure that infrastructure can age. Well, it didn't necessarily have to age. You can keep adding new components to it, and keep that infrastructure alive. 33 00:08:14.770 --> 00:08:44.739 Ben Rogers: I came from Three Tier and Harvey, you know. Many times we had a Bm. We upgrade it would be. Keep the old Vm. We're up and running. Let's hope we have enough space to create a new Vmware, and basically migrate from one to the other. In this environment you don't have to do that. You can literally just add those in that environment stays the same. So as hardware ages out, you reject those nodes as hardware gets better and better. You end you in check those nodes. So it's just real interesting. 34 00:08:44.750 --> 00:09:14.270 Ben Rogers: It's interesting to talk to customers about the difference between your traditional three Tier and your hci, you know, Hyper converged environment like we're talking about here, and we're seeing evident of with it being Cyber Monday. I completely forgot that. But i'm sure my wife will remind me in about thirty minutes. When it comes to. What are we doing for my son's? Christmas 35 00:09:14.280 --> 00:09:26.370 Jirah Cox: just depends on your billing side. Yeah, there's There's ways that the mechanics as a as a technology platform, Right? Actually sort of um 36 00:09:26.450 --> 00:09:40.160 Jirah Cox: really lends itself to a hardware as a service mall right like push button, receive new new hardware node in so many ways, Ben, you you're totally right, like the ability to, of course, scale in scale out right, so get more when I need it. Give it back when I don't um 37 00:09:40.170 --> 00:10:05.150 Jirah Cox: is is easier to do when you're getting those those nodes in like of the cloud right? Because i'm renting them, and I can actually give them back in a way that I can't really give them back if they're in my own data center. Um, but also stuff like self healing stuff like uh you. You hit it as well. Technology refresh right like we. We see it on prem every day with customers right like. Oh, here's your you know outgoing, you know. G. Five notes. Here's your incoming G eight notes. Great. You just expand the cost to reject the old nodes, and it's the simple refresh you've ever done. 38 00:10:05.200 --> 00:10:24.310 Jirah Cox: But that applies even more so in the cloud right where you can. Just you know. Yeah, this month i'm paying for this generation of node. But next month, if if another one comes out, I can just add that new node and roll through my cluster, and on the latest hardware that whatever that cloud provider chooses to stock on the shelves there, I just easily instantly take availability of it, you know, and it's It's so so simple. 39 00:10:24.640 --> 00:10:53.619 Philip Sellers: Well, we're focusing just on the the hyper converged infrastructure layer. But I mean, if you talk about carbon and kubernetes, layer. That modern application is built in a very similar way. So if you're talking micro-service applications and things like that they're built to scale up and scale down. And if if you have this capability at the infrastructure layer, it's just going to drive that ability to to automate and fully into end 40 00:10:53.630 --> 00:11:13.400 Philip Sellers: kind of programmatically, you know, expanded. Contract your infrastructure. So, um! The The stories even more powerful when you start talking about, you know, refactoring those traditional three tier applications into something modern that can make use of that dynamic uh expansion of your infrastructure. 41 00:11:14.160 --> 00:11:27.749 Ben Rogers: It's a trip, fellow, because you just kind of segue into Section three about this about m migrate and modernize. You know we know that customers want the end result to be refactoring, 42 00:11:27.760 --> 00:11:57.739 Ben Rogers: and we we do not necessarily see that as a threat where we do see in C to fitting perfectly in, that is, when they do this modernization they need to be close to cloud, and That's what the clusters and cloud does for you. It allows you to move that workload as it is, and then, once you get your cloud presence, you know out there now. You can be couple of that to figure out how we'll work at native azure. Native aws, and you don't have this, you know, transport cost of getting it in and out there. 43 00:11:57.750 --> 00:12:01.609 Ben Rogers: So we see a lot of customers doing that as well as for 44 00:12:01.620 --> 00:12:28.160 Ben Rogers: let me set up a footprint. Let me you know, Replicate my on-prem footprint out to azure as is, and then let my development team work solely in azure to decouple that for an azure as it environment, and necessarily use the new tanks back in to run that Kubernetes environment just as we do on Prem in C to and and azure, and now our Kubernetes offerings. 45 00:12:28.640 --> 00:12:57.190 Philip Sellers: But you know you you pick on two really great things there, and the first is around um control. So why would someone want to run their own kubernetes when you've got aks sitting out in azure? Well, it's about control. Do you want Microsoft doing the updates when they want to do the updates, or do you want to be able to control that? You know we we we talked to, or driver mentioned that you know the the whole Bm. Where disruptive, or maybe it was men, 46 00:12:57.200 --> 00:13:08.200 Philip Sellers: the whole being where upgrade, disrupting your citrus infrastructure. Well think about that now. Applied to modern applications, you know, if if something gets deprecated in Kubernetes 47 00:13:08.360 --> 00:13:27.590 Philip Sellers: now your application that depends on that is stuck in a particular version. So if Microsoft moves you to the new version of Kubernetes. That's not a great thing for your particular application. So it may break you and calls downtown. Um, yeah, that's That's one of the things that 48 00:13:27.600 --> 00:13:37.219 Philip Sellers: you you get that control back, even though you're getting public cloud. Uh you get the ability to, uh, still 49 00:13:37.230 --> 00:13:50.459 Philip Sellers: be able to to version the things that you're running your workloads and make those decisions about what's right for your business rather than being at your Cloud Providers schedule. 50 00:13:50.480 --> 00:13:57.169 Philip Sellers: Um, you know. And and then the other thing. Um, there's a lot of traditional workloads that Aren't going to go away. 51 00:13:57.560 --> 00:14:02.400 Philip Sellers: I think that's the reality that you're picking out to Ben is. 52 00:14:02.500 --> 00:14:09.970 Philip Sellers: We need to bring things closer to those cloud native services. But there's a lot of client server applications. I know 53 00:14:10.360 --> 00:14:16.850 Philip Sellers: We spent a lot of time working with customers on traditional applications. Um, 54 00:14:17.270 --> 00:14:24.179 Philip Sellers: not all of those vendors are entice to to make it a modern web. Application or sass. So 55 00:14:24.880 --> 00:14:32.799 Philip Sellers: enterprises require this, and we we have to be able to support our our customers and our businesses to keep the lights on. 56 00:14:33.600 --> 00:14:38.470 Jirah Cox: I think it's spot on Phil. Right like It's um. It was, you know. Early on in the cloud 57 00:14:38.530 --> 00:14:57.140 Jirah Cox: cloud services met both consuming cloud economics and consuming as a service right? So, not being able to express a preference around versioning and maintaining the control. More mature. Cloud service is right. Let you get the Cloud economics, but maintain that control that really you often need as an enterprise. Right? There's things you just aren't allowed delegate when they are part of the 58 00:14:57.200 --> 00:15:02.530 Jirah Cox: you know line of business systems right. You have to have that kind of control and and change processes around them. 59 00:15:03.550 --> 00:15:06.869 Jirah Cox: And then to your point. Yeah, I think it's it's um. 60 00:15:07.100 --> 00:15:14.530 Jirah Cox: There's a lot of wisdom there right? So many customers uh have to do both right Run next ten apps run. Old school apps alongside um, 61 00:15:14.540 --> 00:15:33.669 Jirah Cox: and that's one reason money to actually shine is, it can do both. So whether whether you're ten, ninety, eighty-two twenty, twenty-eight, whatever your blend is of of that containerized app and Vm. Based app like they both won't get on mechanics, and I can solve both those problems with one common stack. And as as as my blend changes over time. My experience as an admin does not 62 00:15:35.680 --> 00:15:48.349 Harvey Green: beautiful. So one of the things to been that you had on earlier. Uh, when you were talking about the developers wanting to stay on the same platform. I thought of another way. 63 00:15:48.360 --> 00:15:57.630 Harvey Green: That, uh is mentioned here that you know it. It helps to be able to stay on the same platform and just have the exact same infrastructure move from one place to the other. 64 00:15:57.660 --> 00:16:07.760 Harvey Green: We are the first one on the list. Um, arguably, you know one of the more important ones. Uh, you know it is. 65 00:16:07.770 --> 00:16:25.240 Harvey Green: You know something we end up getting to by way of another conversation Right? Um! But I could say very, very important to be able to do that uh, be be able to not have to go and and purchase more infrastructure and house more infrastructure in a different location. 66 00:16:25.310 --> 00:16:26.170 This 67 00:16:26.340 --> 00:16:46.289 Harvey Green: put it in azure uh it's It's sitting there and ready and waiting for you at any point. So um, you know, if you can't get if you can't get hardware, or you don't have a location, or you just need something to happen right now uh, for you know, because you might have a hurricane coming, or something like that something that 68 00:16:46.300 --> 00:16:54.040 Harvey Green: you know wasn't planned. It just happened. You need to hurry up and get something in place, and this absolutely could be a way for you to to accomplish that. 69 00:16:54.100 --> 00:17:12.060 Ben Rogers: So let me let me ask a question, because I hear this a good bit from customers. Can you guys talk to me about this as your spend idea is, is this committed dollars that a company has, under under a license agreement, a little confused on that. We have a lot of customers that 70 00:17:12.069 --> 00:17:31.530 Ben Rogers: they have a lot of interest in this product. Exactly what you said. This gives them a Dr. Footprint, but part of that Vr footprint is reducing this as your spin, and I mean I need to wrap my head around that, and I hope that our customers are out there going. Hey? How can I use this technology to not only 71 00:17:31.540 --> 00:17:39.269 Ben Rogers: create a Dr. Foot, pip, but potentially help me with some azure, spin, or commit, or or whatever the exact language is there. 72 00:17:39.280 --> 00:17:53.990 Harvey Green: Well, so I've actually seen it be the other way around where they want to increase their azure span, because ultimately that will decrease what they're paying for the other projects that they have going on in azure like with anything else. 73 00:17:54.000 --> 00:18:11.669 Harvey Green: The more you use it, the more you consume it, the better the numbers look and feel. Um. So if you I mean, I think we all know if you commit to uh spending a certain amount, or doing a certain amount in in usage, or in compute with virtual machines right? Your price comes down. 74 00:18:11.680 --> 00:18:30.099 Harvey Green: Uh. But Microsoft also has some other creative things that they do. If you commit to an overall, you know certain amount of spend. Then you can get a a certain amount of discount from that, too. So very much depends on the customer and the agreement that they have. Uh, but I, 75 00:18:30.110 --> 00:18:45.679 Philip Sellers: Phil, you look like you want to chime in there because um, I actually do know of one way to kind of use this. I mean you. You've got data services here within Newton that you can turn on the do compression things like that 76 00:18:45.690 --> 00:19:01.919 Philip Sellers: that Don't exist in some of the native azure products. So if you're using something to store into blob storage, you need it to be there when you need it. You know you don't need to spend two weeks rehydrating from slow storage 77 00:19:01.930 --> 00:19:19.849 Philip Sellers: that's cost-effective. You need it to be available to you when you need to turn on a Dr. Event. So if if your your data center goes dark, You' to be able to start spinning up quickly, and N. C two for Dr. Gives you that capability because it's all on 78 00:19:19.860 --> 00:19:30.579 Philip Sellers: good storage. But your guess is getting these storage efficiencies that Don't exist in in native cloud platforms. You're not seeing didoop and things like that, and blob storage, and 79 00:19:30.870 --> 00:19:42.829 Philip Sellers: you know that's always part of the conversation. Whoever the software provider is that I've talked with in the past, how quickly your your recovery. Time is always a variable 80 00:19:42.930 --> 00:19:54.380 Philip Sellers: that you're trying to understand when your d are into cloud. So if you're going into native azure instances you're going into native blob storage things like that. 81 00:19:54.820 --> 00:20:14.350 Philip Sellers: If you've got to answer, Do I put it on the more expensive fast tiers, or do I put it on the lower cost archival tiers, where it's going to take me longer to spin up when I have a Dr. Of it, and it's kind of this balancing act that customers have to go through with the native cloud services, 82 00:20:14.360 --> 00:20:17.700 Philip Sellers: and in this you kind of avoid that. 83 00:20:20.240 --> 00:20:30.230 Harvey Green: Yeah, agreed Um. The The last one on here Uh, we we kind of hit on a couple of times just around it is in user computing. 84 00:20:30.350 --> 00:20:43.350 Harvey Green: And uh, it was mentioned here in the blog that you can flexibly create citrix uh desktops of the service environment for to suit customer workload needs. I know you can also 85 00:20:43.450 --> 00:20:47.929 Harvey Green: carry forward um. You know, a a couple of 86 00:20:48.180 --> 00:20:50.819 Harvey Green: a couple of positive things from that, too. 87 00:20:50.890 --> 00:20:59.479 Harvey Green: Uh, you've got the ability there to kind of expand on demand as you talk about earlier. Then. Um! You've got 88 00:20:59.850 --> 00:21:17.590 Harvey Green: the different pieces that you can have out of mechanics that that involve, you see, and Citrix around the way that Newton's approaches it. Um, especially around machine creation services. But but I guess you know, instead of diving a lot into that, or at a question instead of 89 00:21:17.600 --> 00:21:26.449 Harvey Green: Do do any of you guys want to hit on any of that before we move to the next piece 90 00:21:26.470 --> 00:21:55.890 Ben Rogers: in our Nc. Two environment, we're going to be able to get more users per node than you are natively, and that and that's a big thing with cost. So I think that's one thing is, if you're using this for end. User compute environment is, how many users can I get on those nodes? And I'm: i'm pretty sure new tanks is going to shine when it comes to that density which is then going to come back to saving money. So that's one reason we see a lot of customers really look at the Citrics partnership, 91 00:21:55.900 --> 00:22:01.580 Ben Rogers: but also the density they can get out of our technology sitting in the Nc. Two as your platform. 92 00:22:01.710 --> 00:22:10.710 Jirah Cox: Yeah, pulling control right? Giving the customer control of their sizing um and allocations. So like i'll call back to our past episode about 93 00:22:10.720 --> 00:22:22.900 Jirah Cox: um some newer, Amd Cpus, and how they actually broke our internal desktop density testing method because their cpu. The the cores were so broad that we actually found a new sweet spot for density from um 94 00:22:22.910 --> 00:22:32.289 Jirah Cox: up from two B cpus up to three Vcp. Per desktop. Right? A really weird setting number, because it's not base two, and we're all nerds, but three V cpus actually let the the node. 95 00:22:32.400 --> 00:22:52.279 Jirah Cox: Okay, we're all nerdy. So, Harvey Cpus, are these things that do all the thinking for a computer. Um. So through Vcp. Is, was a real sweet spot. Right? Don't go from two to four. Well, guess what if your Cloud provider any cloud provider only offers you two or four Vc. View instances right? Well, that's Do you want to pay more? Do you want to pay less? 96 00:22:52.290 --> 00:23:00.149 Jirah Cox: And so keeping you as the user in control of your desktop Vm: allocation sizes. Um! You really ring all the value out of that platform. 97 00:23:00.260 --> 00:23:10.059 Harvey Green: Yeah, that's that's a great uh great conversation there, too, because you, you just, you don't have to be beholden to the sizes that were already determined for you. 98 00:23:10.200 --> 00:23:11.840 Um! Which 99 00:23:12.310 --> 00:23:18.020 Harvey Green: which is huge when it comes to being able to compute in the cloud, giving you that flexibility. 100 00:23:18.310 --> 00:23:30.710 Philip Sellers: Now i'll be while we're on the topic. I mean we. We had this come up with a customer virus out in the field, you know, you see, and ther you know. How How do you have multiple 101 00:23:30.920 --> 00:23:51.979 Philip Sellers: regions and things like that, and and get your golden masters out. I mean There, there's lots of other benefits here. Um! That kind of come in with that close integration between uh mechanics and Citrix, and and things like that that you get to benefit from here in Nc. Two absolutely absolutely one hundred percent. 102 00:23:52.250 --> 00:24:02.939 Harvey Green: Um, That is definitely not the first time we've had that conversation. It's kind of magic. And um, it it's definitely a secret sauce here. Yeah, 103 00:24:03.090 --> 00:24:28.239 Jirah Cox: I mean, in in one sense, feels like you're touching on the the heading of the next section. Right like uh the cool thing about Nc. Two on azure is, it's different, because it's the same right. So the same way that my Gold master Image works, and my cool cloning works, and provisioning all works. I can now take that to the cloud, get cloud economics get control of my own destiny and get the agility. Get achieve that um check box of like we're all in on the cloud, or whatever my mission is um, 104 00:24:28.810 --> 00:24:46.479 Harvey Green: but my experience doesn't have to change. So i'm glad you scrolled because I was starting to feel like I was doing a terrible job of focusing us and moving. We're going to get through this, and we talk about like six lines 105 00:24:47.050 --> 00:25:00.180 Harvey Green: uh That's all right. No problem. So uh, I I love This phrasing here in into two so new tennis cloud clusters. Lc. Two on azure is different, because it's the same. 106 00:25:00.450 --> 00:25:11.400 Harvey Green: Uh, I talk a lot about you know, having the ability to move forward with the things that you know, uh which which in this case would be 107 00:25:11.600 --> 00:25:22.070 Harvey Green: uh prism, right? Our prism pro Mechanics Cloud Manager, I guess, is is what I should be saying, since the naming has changed. Um, but 108 00:25:22.920 --> 00:25:33.420 Harvey Green: names aside right. You have skills that you already know you have things that you already know. You have workflows that you already know. Why not be able to use those things 109 00:25:33.540 --> 00:25:45.669 Harvey Green: in azure the same way you do on Prem. I I think that is a game changer um, and have for a lot of a lot of reasons and a lot of time. But, uh, Gary, you want to hit on that one. 110 00:25:46.690 --> 00:26:08.469 Jirah Cox: Well, then, I can think of even better operational benefits around, like when I go to update my goldmaster images once a month or once a quarter, please. Not once a year. Um! Why wouldn't I want to use a solution that can just auto protect them up to my cloud environment, right like that. That's one less thing I can forget to do or something I can't. I no longer need to be worry about forgetting to do um. That'll just happen automatically. So 111 00:26:09.260 --> 00:26:12.739 Jirah Cox: that gives me room in my brain to think about other things 112 00:26:13.160 --> 00:26:14.030 right 113 00:26:14.410 --> 00:26:23.920 Harvey Green: uh like, How do I get my other workloads to do the same thing, you know again being able to just 114 00:26:24.330 --> 00:26:40.710 Harvey Green: you. You don't have to go and rescue your team. If you have a team. If you got people you're in charge of. You don't have to worry about, you know, spending extra money to train them right. All of those things disappear when they're using the same tool set that they've been using um, 115 00:26:40.720 --> 00:26:47.490 Harvey Green: and ultimately, you know, I I talked a lot about soft cost right at all. 116 00:26:47.610 --> 00:27:02.949 Harvey Green: You can't just measure expenses in terms of how many dollars you're writing a check for. Uh. You also have some soft costs behind it, and and that would be one of them, you know, having to take the time to, you know, retrain your team, 117 00:27:02.960 --> 00:27:09.549 Harvey Green: or even worse, having to pay the price for a team that is untrained on the technology you're using in production. 118 00:27:09.700 --> 00:27:16.120 Jirah Cox: I bet nobody's ever run into that 119 00:27:16.470 --> 00:27:19.120 Jirah Cox: focus on a lot. Or I think about a lot, because 120 00:27:19.160 --> 00:27:45.439 Jirah Cox: for most customers it's tough to paint in very broad brush strokes here. But for most customers Um! The answer is, not everything on proud or in Colo. Not everything in the cloud it's. Usually It's going to be a mix right, because right um, you know, data has gravity, and most mostly most users don't work in the cloud right? They work at home, they work in offices. So latency is a thing, so so almost everybody has has multiple silos of availability right usually on-premisely cloud. Um. 121 00:27:45.450 --> 00:27:59.700 Jirah Cox: And if you're hearing this, if you're a customer listening to this and thinking, you know. Oh, yeah, staffing is easy. Training is easy within your then life's good, right. But if you're like, I need to have a team that does more every single day with less 122 00:27:59.710 --> 00:28:17.639 Jirah Cox: that needs to learn new skills. Well, then, this is the easy button for saying that one skills that applies to all those pockets of availability. Now, right cloud on prime colo, and I didn't just double or triple my training burden, hiring burden, retention, burden for my human resource right? That actually makes this whole thing work 123 00:28:17.650 --> 00:28:27.539 Ben Rogers: right now. Those are Those are also sea level conversations, because, as we're sitting here talking, we're talking at the infrastructure level at the end of the day, 124 00:28:27.550 --> 00:28:41.749 Ben Rogers: c. Levels care about applications how our applications being used by our customers, our end users, X, y, and Z. So I'm. Talking about simplicity and flexibility, whether on prem in cloud 125 00:28:41.760 --> 00:28:56.540 Ben Rogers: Cloud has flight, I I think Andy says it best. Clouds. What flavor do you have private file, public file? Something between this product set can fit into that. I mean it. Can. It can go where you need it to go? I I think one thing is 126 00:28:56.550 --> 00:29:26.130 Ben Rogers: very flexible about new tanks. That kind of differentiates us from some of our competitors. That one license does this. We have single uniform license that will allow you to go in all these places. So to me, when they say Nc. Two is different, but the same. The same to me is the license that you have today, and the functionality had today. Just take that with you to where you want it to go today. We're talking about azure, but it could be aws it could be, you know, uh some of the private 127 00:29:26.140 --> 00:29:39.899 Ben Rogers: vendors that are out there equ next those guys, you know. So I think that's really in essence to me. What that title says is by your license you pick where you want to go. Flexibility, simplicity will follow in that model. 128 00:29:40.360 --> 00:29:47.509 Harvey Green: Yeah, agreed. And that kind of hits to on on what's in the middle of the the pictures Here the accelerate cloud adoption. 129 00:29:47.570 --> 00:30:06.980 Harvey Green: Um there! There's no faster way to do something than to use what you already have. I mean You've got the licensing You've got the skill set uh Microsoft got the hardware. It's already there. Everything you need is already there. You just need to connect the dots. So 130 00:30:06.990 --> 00:30:15.699 Harvey Green: um definitely, definitely uh accelerating your your cloud adoption there. Uh, you know another way that you can do that 131 00:30:15.750 --> 00:30:27.540 Harvey Green: uh completely behind the scenes and not have you know the rest of your end? Users uh worry about it or know about it. They don't care where the infrastructure is hosted. They just care that stuff works. 132 00:30:27.770 --> 00:30:37.799 Harvey Green: So this, you know, work on making it work, and uh having the ability to have it alive and working and available in in more than one setting. So, 133 00:30:38.000 --> 00:30:44.690 Harvey Green: uh, definitely it's it is. It is different, because it's the same by like that. 134 00:30:46.510 --> 00:30:50.810 Harvey Green: Um, let's see. So the the next 135 00:30:50.980 --> 00:30:58.980 Harvey Green: next uh heading here is in C to availability where, what? And when we kind of talked about that a little bit 136 00:30:58.990 --> 00:31:14.850 Harvey Green: uh, but to get into more detail, it's got a listing here of the Microsoft azure regions uh some of them that it is available in the uh azure East Us. West, Us. To uh North Central Us. And support for 137 00:31:14.860 --> 00:31:29.369 Harvey Green: other global azure regions being developed. Um, at this point, you know you've got a few options right. You got an east coast optional west coast option a central option, and they're continuing to build that out in in other regions. 138 00:31:29.400 --> 00:31:33.890 Harvey Green: Um, I guess ultimately the the point there is that 139 00:31:33.900 --> 00:31:53.129 Harvey Green: again. It's already there and available for you. You've got options where you want to put it. You can put it closer to your users, or, uh, you know, if you want it geographically, this first, and you you've got that option as well. If you're on the East, they've got East, if you need to be in the middle. They've got the middle got you all covered. 140 00:31:53.140 --> 00:31:55.320 Harvey Green: However, you need to do that. So 141 00:31:55.510 --> 00:31:56.930 Harvey Green: um 142 00:31:58.070 --> 00:32:03.569 Harvey Green: questions pieces on that guys anything you want to hit on there. I think that one's 143 00:32:03.690 --> 00:32:33.470 Ben Rogers: pretty cut and dry. Yeah, I mean, just just trust it'll grow, I mean, like anything else. If you look at our aws uh footprint, it's a little bit bigger than this, so we'll follow right into that. And then the other thing that you know our nodes right now are not storage heavy with their code. And so those are two things. You know the footprint will continue to grow, and trust there'll be more nose with storage heavy in it, so we can look at more of these replication offloads and workloads and stuff like that. So uh, just may keep your eye on on the growth of it. Know that we're in the business, and we're now 144 00:32:33.520 --> 00:32:35.120 expanding the service 145 00:32:35.440 --> 00:32:36.810 Harvey Green: absolutely 146 00:32:37.110 --> 00:32:50.829 Harvey Green: uh pricing flexibility here. So you got options here for sure. Uh they got some laid out, but at a at a very basic kind of level here. You've got ways that you can do this and 147 00:32:50.930 --> 00:33:05.719 Harvey Green: uh set it up so that you're pulling it out of the azure marketplace uh for your Newtonic software. You've got ways to do it. Continuing to use the licensing you already have which Ben spoke to, or if you want to have 148 00:33:05.730 --> 00:33:22.789 Harvey Green: uh, you know both what you have on, Prem, and have azure. Be a a new data center for you and have them up can uh simultaneously. Then you got the option to just pull licensing in for that um, and and have everything up not just, you know. Have it 149 00:33:22.900 --> 00:33:25.239 Harvey Green: uh set up in one place, so 150 00:33:25.510 --> 00:33:33.310 Jirah Cox: and you can mix and match, which I think is one of the coolest ones. Right. So like, if you're doing e-commerce right in the last six weeks of the year really busy. 151 00:33:33.400 --> 00:33:45.850 Jirah Cox: Maybe you need three or four nodes for ten months out of the year, so go ahead and own your new next licensing for ten months out of the year, or for, for you know, by by three years or five years. Whatever you want. However, you want to buy that license 152 00:33:45.860 --> 00:34:04.999 Jirah Cox: um, and those nodes that you can burst onto right expand on to uh on demand like I talked about, you know. Sure rent those licenses right through the marketplace for six weeks or eight weeks or two months. Whatever you need to right, so you can mix and match within a cluster to have that. Uh, I own these licenses, and I I buy these on demand when I only when I need to burst them Uh! Burst out to them. 153 00:34:05.200 --> 00:34:20.799 Harvey Green: Yeah. And I think to to Phil's point earlier, too. Right? Today is Cyber Monday, And really that this is the beginning for a lot of those retail type customers. This is the beginning for a very hectic next two months for them. 154 00:34:20.840 --> 00:34:22.699 Harvey Green: Uh, but then, after that 155 00:34:22.750 --> 00:34:31.800 Harvey Green: you don't really need all that capacity anymore. So you got the flexibility there to be able to to pull in what you need when you need it, 156 00:34:31.929 --> 00:34:39.870 Harvey Green: and then let it go and not pay for it later. So that's that's hugely important for those kinds of customers with seasonal business. 157 00:34:40.460 --> 00:34:58.340 Philip Sellers: When you're more traditional businesses, I mean, that plays into the Dr. Conversation right? So you just need a landing area um kind of a hot N. C two cluster that you're replicating into. But when you have your event. Well, then, pay for your actual full footprint at that point. Not 158 00:34:58.350 --> 00:35:18.149 Philip Sellers: not, you know. Upfront, uh, you know. Wait until um, Whatever happens to your your data center happens. Uh, I I hate being throw out examples, cause you know it's gonna be some crazy crazy thing uh That's little that ultimately gets you. Not, you know. 159 00:35:18.180 --> 00:35:31.009 Philip Sellers: Rain ring fire from the sky, taking out your data center. You know It's gonna be like a a back Co. You know North American fiber seeking back home. But it's good that you bring it up, because, uh, 160 00:35:31.230 --> 00:35:42.730 Ben Rogers: man, we go into a lot of places, and that's a and that's a subject. That is, not a lot of customers have really signed, sealed, and delivered that, and my hope is, as I learn, more about my customers. I can kind of 161 00:35:42.740 --> 00:36:06.529 Ben Rogers: they, you know, hint to them that we have this capability, and they they look at it a little more seriously, because what I hate is when customers go, you know what is your Dr. Plan? Well, we would just restore from backup, and you go. Well tell me what that looks like, and you really don't, you don't hear anything that gives you a comfort level that they have a run, book or a plan, and so again to our customers. Help us, you know. Help you 162 00:36:06.540 --> 00:36:14.309 Ben Rogers: uh get to where you know you have a solid Dr. Plan and and help on some of that Microsoft spin that you've got this wrapped around this, 163 00:36:14.350 --> 00:36:43.109 Jirah Cox: and depending on where the customer's coming from right this this isn't even an equivalency conversation for Dr. It's actually a couple ofling in some ways right. If you're if you're really doing all the things that you really ought to be doing when you deploy this your new Vms, you deploy can auto get protected. Auto-replicate to your Dr. Environment, your Dr. Environment can auto run a Dr. Test for you every Sunday night and email you every Monday morning to say, Yeah, we're still all good here. Keep on deploying stuff, and and you have the confidence you can recover it when it's when it's needed. 164 00:36:43.170 --> 00:36:53.479 Jirah Cox: So um! It's not even just the the insurance policy of Dr. It's the it's the actually I can prove that this is super super usable. Um, and it's protection that follows us as we grow the business. 165 00:36:53.870 --> 00:37:04.090 Philip Sellers: Well, and let's be honest. I mean everything that we've done over the last fifteen years has just ratched it up. Complexity within our environment. Our our 166 00:37:04.600 --> 00:37:10.189 Philip Sellers: our environments are incredibly hard to troubleshoot hard to understand. Um, 167 00:37:10.340 --> 00:37:22.820 Philip Sellers: but we've we've benefited from great amounts of flexibility, right? This is one of those few opportunities where we can really start to tap into that flexibility to make it a game changer for our business 168 00:37:22.840 --> 00:37:28.889 Philip Sellers: and and get true benefits uh true, true sort of um 169 00:37:29.470 --> 00:37:35.669 Philip Sellers: independence uh, in a way, I mean, because you know, we are talking about azure. But 170 00:37:35.680 --> 00:38:04.169 Philip Sellers: I know I listen to a podcast not that long ago about another cloud provider, and uh, uh, so so you're giving back some level of choice to your customers. Um! You're meeting them where they are, where they feel comfortable, and I think that also goes to Harvey's point about not having to reskill because azure and aws, they do things a little differently. And so, anytime you introduce those things. Um, you have that 171 00:38:04.770 --> 00:38:09.340 Philip Sellers: that learning curve that slows things down absolutely. 172 00:38:09.350 --> 00:38:26.179 Jirah Cox: It's almost like our, I think, with that earlier feel like It's like our rate of change is is increasing in in the industry, and I was actually thinking about like, is there? This is totally off the wall. Is there some future where we can picture like a Cio or Cco being almost measured in gold on 173 00:38:26.220 --> 00:38:50.310 Jirah Cox: um, on agility, right on like decision making that absolutely prevents future lock in right. And like, if x happens, I can react to that. If y happens, I can scale for this, you know, if this kind of contraction happens, I can scale in for that um, and almost rewarding more flexible decision making so simplicity and flexibility equals agility. 174 00:38:50.380 --> 00:39:05.329 Harvey Green: No, look at you so I mean ultimately right. All all of our end users have become increasingly less tolerant of downtime. 175 00:39:05.400 --> 00:39:10.750 Harvey Green: Uh they're being asked to be able to work from anywhere, 176 00:39:10.760 --> 00:39:40.750 Ben Rogers: Right? We have to make sure they can work from anywhere. Well, some industries it's not even like in healthcare man. It was very rare that you could take the systems down, and the moon had to be fine, and I I didn't work, and I would consider trauma in some trauma environments. You're not going to be able to take that network down. You've got to have some kind of way of switching over something secondary or so, and I hear that in finance as well, that they get real picky about things going down so uh downtime is not tolerated 177 00:39:40.760 --> 00:39:43.929 Harvey Green: at this point in certain industries 178 00:39:44.010 --> 00:39:57.419 Harvey Green: I I mean I would argue again to the point where it's for all of them. Um! I I just. I don't. I don't see it, and it's It's not necessarily because the users are demanding to be able to. I I want to work right now. 179 00:39:57.430 --> 00:40:09.349 Harvey Green: They've just gotten used to. Hey, If I want to watch a movie, I just go to Netflix and I start watching the movie, And if that movie doesn't start within five seconds. Right? That's a bad interaction, 180 00:40:09.870 --> 00:40:14.949 Harvey Green: and and they're taking that standard into the workplace. 181 00:40:14.960 --> 00:40:36.719 Harvey Green: And so that's That's kind of what I think we're seeing uh, more and more. And why? To Gyrus point you absolutely will. We'll see those types of positions graded by resiliency and by up time and availability in ways that just haven't been the norm uh for for those types of positions before, 182 00:40:36.730 --> 00:40:46.870 Ben Rogers: and we'll think about what it, what Java saying is when you have to see a cio, they can sit back and go. Okay. I've got X Cloud Provider. Here's what my workloads cost to me today. 183 00:40:46.880 --> 00:41:14.180 Ben Rogers: And where do I need to have it where it will be, and most efficient for the company that's going to really be the person that's in control, you know, when they, when they've got their cost almost calculated and able to predict we know when and where and how. Imagine being able to do testing on things like a storm coming. And now you need to move your load to another part of the country. What's that going to cost? The That's exactly it. And So those are going to the driver's point with agility. 184 00:41:14.190 --> 00:41:36.050 Ben Rogers: Those are things that Cios are gonna want to look at, as far as you know. How am I looking today but as future uh as future risk come up. How's that going to affect my ability? And what could that Potentially it cost me? And Let's not get the cyber security insurance into it. They're going to be asking those questions, too. They're gonna be looking at. What's your agility statements? And so again 185 00:41:36.060 --> 00:42:02.799 Philip Sellers: take the pounding in the ground. But simplicity and flexibility is going to equal that agility. Well, then, you you hit the mail on the head with that one I mean, I I know having gone through a couple of cyber renewals. Um, they're asking increasingly more technical questions. So it used to be your underwriters the folks that you were working with for your policy. They weren't asking it questions. Now they're getting into the nuts, and both, 186 00:42:02.950 --> 00:42:09.070 Philip Sellers: and and trying to understand what their risk profile looks like. So yeah, you you hit the now on the head with that one. 187 00:42:09.550 --> 00:42:17.930 Harvey Green: Yeah, I I have a hate hate relationship with 188 00:42:18.090 --> 00:42:29.369 Harvey Green: um. But yes, no, that's that's a hundred percent correct. And and maybe one day uh I I hope to never have to use it right. You buy it in hopes that you never have to use it. 189 00:42:29.470 --> 00:42:37.919 Ben Rogers: Um. So yes, this is your person that takes care of your technology in the day. I would like to speak with them. 190 00:42:43.760 --> 00:42:46.269 Harvey Green: Um, all right. What else 191 00:42:46.770 --> 00:42:54.310 Harvey Green: so good to get? You get to scroll and move it? I think we got to go to the 192 00:42:54.410 --> 00:43:05.340 Harvey Green: look at that we did. We did so, as as I always try to ask Gyre and stick them on the spot, and he always just nails it There, 193 00:43:05.400 --> 00:43:08.430 Harvey Green: what do we have to do if we want more information, 194 00:43:10.590 --> 00:43:23.250 Jirah Cox: Man, we've just got. We're rolling out the buffet. So if you like to read. You can read stuff uh if you want to watch. We got videos. If you want to see it, we can spin it up for you. Um. 195 00:43:23.260 --> 00:43:49.109 Jirah Cox: So you got. You got plenty of options. The the blog post your links to the white papers. Um, Of course we're also listed on the azure uh web pages as well. Um! Call your friendly tanks, Essie. Uh, and they can give you a a nifty demo or get you a spun up on a trial. Uh, there's also, instead of incentives around uh trials right now, which may or may not expire by the time you hear this recording, uh, so check for the latest on that. 196 00:43:49.120 --> 00:44:18.190 Ben Rogers: But I like how you put the disclaimer out there. It's almost like It's almost like recording. Stand forever uh, but but maybe free trial offers Don't. But and then also links in the blog post here to that uh the free test drive as well. So, yeah, if you, if you want it. Reach one of us on this broadcast. We'll get it to you, man. It should be really easy for us to get this out. This is a a hot topic for the company. We're exciting that we got the product, and anybody that wants to use it. You let us know we'll. 197 00:44:18.200 --> 00:44:22.940 Harvey Green: We'll tear down the walls and get it to you. Absolutely, absolutely. 198 00:44:23.110 --> 00:44:45.529 Harvey Green: Um, All right, Thanks, guys. I definitely appreciate the level of conversation here of the day. I also appreciate that we actually made it. So. I can use that as a bragging point to Andy, who's probably already listening to this uh, that, that we did it. We made it 199 00:44:45.600 --> 00:44:52.259 Harvey Green: so um definitely appreciate you guys, as always. And uh, we will see you next time.