Latest / Nutanix Weekly / Nutanix Weekly: Elevate Your IT Infrastructure with Long-Term Support Release: Nutanix AOS 6.10

Transcript

Nutanix Weekly: Elevate Your IT Infrastructure with Long-Term Support Release: Nutanix AOS 6.10 · Nutanix Weekly

WEBVTT 1 00:00:02.980 --> 00:00:13.460 Philip Sellers: Hey, and welcome to another episode of Nutanix Weekly one of the many podcasts that we like to call content with context here at Zentagra. 2 00:00:13.510 --> 00:00:37.231 Philip Sellers: I'm your host, Phil Sellers. I'm the practice manager for modern data center. We call it modern data center, because we know that not all of the things that run your business run in a colo or in that room down the hallway anymore. It's probably hybrid in some way. Some aws, some sas little bit of everything contributing to how you run your infrastructure. So 3 00:00:38.340 --> 00:00:51.429 Philip Sellers: I'm joined today again with 2 great guests 2 great co-hosts. From Nutanix. We've got Jira Cox, who is a principal technologist. Jaira, how you doing. 4 00:00:51.630 --> 00:00:53.790 Jirah Cox: Good man. Good doing well. 5 00:00:53.810 --> 00:00:56.769 Jirah Cox: appreciate the the invite back again. 6 00:00:57.217 --> 00:01:06.159 Philip Sellers: As always, it's standing invite right? We've also got Ben Rogers, a enterprise sales engineer. Ben, how you doing. 7 00:01:06.450 --> 00:01:09.739 Ben Rogers: Good glad to be here. It is, as Jairus said. 8 00:01:09.760 --> 00:01:13.010 Ben Rogers: glad to be invited back, so always a pleasure to hang out with you, too. 9 00:01:13.780 --> 00:01:27.630 Ben Rogers: and and just to let you just let the listeners know I learned just as much from this hanging out with you 2 as probably they do. Listen to all 3 of us. So I always appreciate the time and the invitation to sit in on the podcast. 10 00:01:28.200 --> 00:01:42.350 Philip Sellers: Well, it it's funny. I think there's a lot of learning going on, Ben, and it's good to point that out like I'm I'm sitting in Durham just across the railroad tracks from Nutanix, headquarter here on the East Coast. I've been here 11 00:01:42.460 --> 00:01:51.399 Philip Sellers: a lot over the last few months, just doing different activities with customers with, you know, training internal 12 00:01:52.042 --> 00:02:04.389 Philip Sellers: spending a a fair amount of time here and a lot of that is learning. So I don't care if it's bringing a customer here for an executive briefing which we did last week, or 13 00:02:04.966 --> 00:02:16.939 Philip Sellers: if it's it's hardcore training, you know, 8 HA day always leave with something new, because there's just that much going on inside of Nutanix inside of the product. And 14 00:02:17.050 --> 00:02:31.390 Philip Sellers: I'll be honest. Today is is a great, and we couldn't have asked for a better intro for for what we're gonna talk about today, which is the brand new release, a long term support, release of Nutanix Aos. Version 6.10. 15 00:02:31.940 --> 00:02:35.859 Philip Sellers: This came out. What last week is that? Right? Jaira? 16 00:02:35.860 --> 00:02:40.449 Jirah Cox: Sounds correct. Yep. Well, last week, as we as we were talking about it, you and I now. 17 00:02:41.029 --> 00:02:51.260 Philip Sellers: That's true. This probably isn't gonna release for a few weeks. So came out on October the 8th so early October. And 18 00:02:52.040 --> 00:03:09.334 Philip Sellers: yeah, we were talking a little bit about this. But you know, long term service releases short term service releases. It's a release cadence for nutmx. But basically lts, and 6.10 is a long term. Service release is gonna be supportable for a longer period of time. 19 00:03:09.740 --> 00:03:15.890 Philip Sellers: but what goes into one of these lts's Jaira. What what are we getting with? 6 dot 10. 20 00:03:16.240 --> 00:03:39.399 Jirah Cox: Sure, with 6 to 10 you're getting. It's kind of a you can think of it almost as like a roll up. Release a little bit like, you know. We've seen those for years, and like the windows server patching cadence right where you have patches that that catch up, you know, as giant releases things that are shipped beforehand as well. Now that's trickling out to lots of stuff like us. Patching one of my desktops here at the house the other day, and it was like. 21 00:03:39.410 --> 00:03:50.915 Jirah Cox: Do you want some early stuff first, st or do you want to catch it? You know, as it kind of goes mainstream. So I would think of these more like a mainstream release like they're they're intended for all customers to roll out all new clusters with 22 00:03:51.200 --> 00:03:54.259 Jirah Cox: to patch existing clusters up to right 23 00:03:54.270 --> 00:04:11.450 Jirah Cox: and and therefore really everyone for all purposes, for all workloads ready to go. And then, of course, we do, of course, put out some intermediate releases, right? That are what we call Sts that are for like, if you need a new feature faster, then, of course, those are there for you as well, and those sts eventually get merged into a future. Lts like this. 24 00:04:12.150 --> 00:04:15.399 Philip Sellers: So so the short version of that is new toys. 25 00:04:15.400 --> 00:04:15.990 Jirah Cox: Yeah. 26 00:04:18.250 --> 00:04:30.069 Jirah Cox: totally true. Yeah, very much true. So new for new for everybody. Right? So a couple of some some kids have been playing with these toys and testing them for us earlier on. And now toys for everyone. 27 00:04:30.360 --> 00:04:35.715 Philip Sellers: No, that that's funny, like you know. My son grew up as the Youtube generation. So 28 00:04:36.290 --> 00:04:56.950 Philip Sellers: much to my surprise, he enjoyed watching other kids unwrap and play with new toys. That was one of the video crazes for his generation. So this is kind of our version of I can't remember the Kid's name now. But kind of those Youtube videos of playing with new toys we we get to talk about here today. 29 00:04:56.950 --> 00:05:05.339 Jirah Cox: Trying to think about how those kids out earn all 3 of us combined doing that as like a 6 year old on Youtube, you know, playing with toys. 30 00:05:05.530 --> 00:05:06.290 Philip Sellers: Absolutely. 31 00:05:06.290 --> 00:05:08.629 Ben Rogers: Doubt. No doubt 32 00:05:09.460 --> 00:05:16.330 Ben Rogers: I would like to take a moment here to kind of, you know. Talk about my learning. Curve a little bit since I've been here at Nutanix. 33 00:05:16.520 --> 00:05:35.219 Ben Rogers: you know I'm going to age myself here to get enhancements out of an environment. You used to have to throw a lot of hardware at it. And there was really no software change that could be made. It was basically to throw hardware at it today. Specifically with this 1st area we're going to talk about now, kind of segwaying into the storage capabilities. 34 00:05:35.260 --> 00:05:51.819 Ben Rogers: This is where you see Nutanix. And I'm kind of fascinated by this, and being 54 years old to get fascinated by something that I've done for 30 years is quite of achievement. But I'm starting to see where our software engineers can play with the operate. Our our Aos 35 00:05:51.870 --> 00:06:08.070 Ben Rogers: and man bring goodness and performance out of just, you know, man changing some some gears within the software itself. And since I've been here over the 2 and a half year period, I've seen them make several enhancements to the software part of the 36 00:06:08.070 --> 00:06:23.699 Ben Rogers: equation that has really bought some enhancements, you know, discharging some of those things. Jare can speak a whole lot more of what we brought to the table, but it just amazes me when you look at some of the features and capabilities that we bring in these Lts releases 37 00:06:23.700 --> 00:06:43.060 Ben Rogers: that are software driven that bring performance to the platform where it used to be. You had to wait to refresh hardware to get some of those performance enhancements, and so I'm very fascinated by that, and what our company is able to do from a software level to get as much power and performance as they can out of the hardware stack. 38 00:06:43.970 --> 00:06:56.039 Philip Sellers: Well, I think you hit on one of the age, old sort of conflicts inside of it. Is, is it the software, or is it the hardware. And and as infrastructure guys, we've, we've probably always thrown 39 00:06:56.240 --> 00:07:04.620 Philip Sellers: more hardware at the problem to try and solve it. But really there's a lot of magic that can happen inside the software. And 40 00:07:05.080 --> 00:07:17.870 Philip Sellers: I I think that's 1 of the shifts that we see in where we're at today. And as an industry is that the software is the defining difference. And that's the story of hyper converge. That's the story. 41 00:07:18.040 --> 00:07:19.020 Philip Sellers: Cloud 42 00:07:20.440 --> 00:07:29.720 Philip Sellers: breaking down silos, making things scale and using industry standard Lego building blocks to to do that. And 43 00:07:29.810 --> 00:07:32.619 Philip Sellers: I think it's a great point. You know. It's 44 00:07:32.650 --> 00:07:35.600 Philip Sellers: it is something that we're seeing tremendous 45 00:07:37.190 --> 00:07:39.829 Philip Sellers: progress. I guess, as 46 00:07:39.940 --> 00:07:44.690 Philip Sellers: time comes on with with the capabilities around performance. So 47 00:07:45.254 --> 00:07:51.275 Philip Sellers: you know, as as we dig into this, it's it's not only higher performance, but there's some 48 00:07:51.840 --> 00:07:55.557 Philip Sellers: density changes that come along with this, too. Right? 49 00:07:56.030 --> 00:07:58.099 Philip Sellers: we're we're able to get 50 00:07:58.480 --> 00:08:00.059 Philip Sellers: some new limits 51 00:08:00.487 --> 00:08:08.180 Philip Sellers: in place, I mean, is there anything, maybe, beyond what's here in the blog post, Jaira, that that you could share in terms of those 52 00:08:08.280 --> 00:08:11.419 Philip Sellers: density, capabilities and things like that. 53 00:08:13.750 --> 00:08:19.139 Jirah Cox: yeah. So so, which is a neat point to to highlight there, right? How 6.10 really 54 00:08:19.210 --> 00:08:20.290 Jirah Cox: catches up 55 00:08:20.340 --> 00:08:33.549 Jirah Cox: what? What has already been brought by Aos 6.6 6.7 and 6.8. So yeah, of course, if you're anywhere in there in the middle, then yeah, there probably is new stuff here for you around larger nodes. 56 00:08:33.690 --> 00:08:52.409 Jirah Cox: I know one of the key things that we're highlighting, of course, is even larger larger nodes that can support things like nightly snapshot rates. Right? So if you only need once a night snapshots and less than like, say, continuous data protection, then yeah, the nodes can get get truly truly large these days, the blog. But this blog post doesn't call out specifics on that one. 57 00:08:52.717 --> 00:09:07.170 Jirah Cox: But that, of course, is an area. You can imagine that we're always looking to make continual improvement on right to give our customers better rpos larger density, larger density translates into better financials, right? Better economics around, you know, denser hardware refreshes, fewer notes to manage 58 00:09:07.170 --> 00:09:19.230 Jirah Cox: and helps keep pace from a storage platform level. Really, I would say of what CPU vendors are looking to do as well right like they're they're much more investing into. How many cores can we fit into this node? 59 00:09:19.230 --> 00:09:45.050 Jirah Cox: Not. Let's get you more nodes to hit a certain kind of core account right? So as our core counts per node, really push limits of what some of us even enjoy as like an ha boundary. You know. How many baskets do I want for my for my eggs? Here, then, you know, like 1, 28 cores is kind of like, oh, wow! That's a really interesting design. Non limit. Right? So then, we want storage to not also be the the constraining part below that either. 60 00:09:45.550 --> 00:09:46.580 Philip Sellers: Absolutely. 61 00:09:46.790 --> 00:09:56.590 Philip Sellers: And I think you know that that takes us into the idea of you know what is truly enterprise. Ready? Right? We're 62 00:09:57.280 --> 00:10:10.099 Philip Sellers: we're talking about eggs in a basket. We're talking about you know, risk at the end of the day. And so you know, one of those risk factors is, you know, does the software running on this platform. 63 00:10:10.210 --> 00:10:20.969 Philip Sellers: you know. Is it supported? Is the Isv I'm working with going to support it. So Lts is really important when it comes to that ecosystem of things that run on Nutanix. 64 00:10:21.040 --> 00:10:24.940 Philip Sellers: A lot of vendors don't certify for Sts releases. And so. 65 00:10:25.446 --> 00:10:37.860 Philip Sellers: as we talk about that and enterprise readiness, you know. That's a huge factor for 6.10. This will be something that we can expect. Many Isv softwares to be certified against. 66 00:10:37.910 --> 00:10:40.500 Philip Sellers: And so this is another 67 00:10:40.660 --> 00:10:50.819 Philip Sellers: huge step forward where we're getting tons of new capabilities, speed, density, all of these things, but also that enterprise, level support, and that that kind of takes us to 68 00:10:50.920 --> 00:10:55.020 Philip Sellers: point number 2. Enterprise readiness with Ahv 69 00:10:57.580 --> 00:11:00.925 Philip Sellers: You know, age fees been around 10 years now, and. 70 00:11:01.260 --> 00:11:02.169 Jirah Cox: We're there for the birthday party. 71 00:11:02.170 --> 00:11:06.979 Philip Sellers: Birthday. Yeah. So we saw that at Dot next earlier this year. 72 00:11:07.790 --> 00:11:10.239 Philip Sellers: it's come a long way, and 73 00:11:10.500 --> 00:11:18.230 Philip Sellers: there's tons of of goodness in here. Let's kind of cover off some of the things from an enterprise. Readiness, standpoint. 74 00:11:18.900 --> 00:11:48.609 Jirah Cox: Yeah. So the post calls out, you know a new one. It's again, it's new. It's new now to really all customers, whether you were on, or at least they already have this feature or not. So on demand. Cross, cluster migration. That's a mouthful. But a great thing right? The ability to move running vms, of course, from one cluster to another, which in our standard nutanix designs are sort of always shared nothing right. Those those clusters might not share anything other than maybe the network that your your guest Vm. Is attached to. 75 00:11:48.620 --> 00:11:52.150 Jirah Cox: so that ability to move a running vm from one cluster to another, whether that's across. 76 00:11:52.180 --> 00:12:00.580 Jirah Cox: and a wreck across the aisle or across town, all now possible for all customers, whether you are on a release that had it before or not. 77 00:12:01.738 --> 00:12:11.620 Jirah Cox: Storage optimizations, of course, helping to place vms more intelligently onto even clusters where they want to run. 78 00:12:11.630 --> 00:12:13.800 Jirah Cox: and then and then vm placement as well. 79 00:12:14.380 --> 00:12:20.329 Jirah Cox: and then security. And then I mean you. You really touched on it, Phil, but that ecosystem right, that 80 00:12:20.830 --> 00:12:37.059 Jirah Cox: nothing exists in a vacuum right? So so much of what our customers experience when they want to move on to Nutanix and move on to Ahv involves looking at that vendor matrix of like, what else do I use to help manage and monitor my environment? Help make my job easier as an administrator, as a platform owner. 81 00:12:37.170 --> 00:12:48.150 Jirah Cox: and and it's really a delight, and thanks to our alliances team for all the work they put into this. When I sit with customers and look through the matrix of like what supports Nutanix? And what can they keep that they already own 82 00:12:48.390 --> 00:12:55.290 Jirah Cox: as they migrate over? And that list gets longer and longer by the day. It's really quite really delightful to see, and it's wonderful for our customers. 83 00:12:55.860 --> 00:13:00.370 Philip Sellers: And Ben, you come from that customer background. This is a huge deal. 84 00:13:01.484 --> 00:13:02.310 Philip Sellers: Because 85 00:13:02.820 --> 00:13:08.049 Philip Sellers: what you don't want as a customer is to call into support and be like, sorry I can't help you. 86 00:13:08.120 --> 00:13:12.822 Philip Sellers: because X, this, this is a huge deal. 87 00:13:13.710 --> 00:13:14.600 Philip Sellers: what? 88 00:13:15.310 --> 00:13:21.075 Philip Sellers: I I guess. What's your perspective, as you kind of look at this enterprise. Support 89 00:13:22.070 --> 00:13:24.599 Philip Sellers: and how it's changed over time. 90 00:13:25.030 --> 00:13:54.560 Ben Rogers: So, you know, there's a there's a paradigm shift kind of going on in the industry to this micro service mentality. And I think that's really where we're. We're shining right now, as far as like it is a platform where Hv. Is just a service within that platform. So you know, you were talking about our ecosystem, you know. Right now we have the ability to look at customers and go. You know the platform is the foundation for the micro services that you want to run. 91 00:13:54.560 --> 00:14:18.819 Ben Rogers: So if you want to run Ahv, and you want to run containers. With that we can do that if you want to run? Hv, and you want to run our nus, our unified storage services on that. I mean, this is what we're bringing to the table. And I think that's what's making it. Enterprise ready is, we're not just a hypervisor. We're not just a storage component anymore. We're really bubbling up goodness that allows you to manage files, manage unstructured data. 92 00:14:18.820 --> 00:14:34.770 Ben Rogers: manage ransomware and looking at the content of your unstructured data, kubernetes, container management deployment application. You know, I mean database management and deployment now. So there's a there's a lot of things when you say enterprise readiness. 93 00:14:34.770 --> 00:14:53.390 Ben Rogers: and what I go back to is that you know nutanix at the heart is a cloud platform that's based on micro services that live in that platform. Hv. Is one of those services amongst the other ones that we just talked about, and that to me is what defines the enterprise. Readiness. 94 00:14:54.230 --> 00:14:58.469 Philip Sellers: Yeah, I I think that's a a valid point. It is a platform. 95 00:14:58.770 --> 00:15:16.490 Philip Sellers: you know. I'm a huge performance proponent of calling it a platform. You know, it's it's not just hyper converse. This is so much more because the services that run on top of it are really valuable to your business. One of those hugely valuable 96 00:15:17.178 --> 00:15:21.641 Philip Sellers: services is really around disaster, recovery, and resiliency. 97 00:15:22.240 --> 00:15:25.840 Philip Sellers: we're raising the bar again with 6 dot 10 98 00:15:26.270 --> 00:15:45.199 Philip Sellers: new replication resiliency features near sync for volume groups and consistency groups, multi-site metro, multi-site. Dr. Which is really interesting. And and that's 1 i would want to talk a little bit about. And then also multi cloud snapshot technology which I think is really interesting. 99 00:15:45.675 --> 00:15:51.219 Philip Sellers: When you start talking about and thinking about cost, effective ways to handle Dr. 100 00:15:52.520 --> 00:15:54.259 Philip Sellers: Yeah, spot on Megan. 101 00:15:55.110 --> 00:16:20.720 Jirah Cox: Yeah. So I mean, it's great to see near sync. Come now to volume groups and and consistency groups. That's our way of saying our 1 min replication threshold. So we can now get that data offsite within 1 min which gives a ton of protection to the business. And really I usually describe this as sort of like for the most complicated apps. Our customers ask us to host right? So like into the, you know, either multi vm groups or multiple Vdisc groups right where I need, like the right order, fidelity of like 102 00:16:20.730 --> 00:16:30.540 Jirah Cox: this. These snaps occur in the right way, preserving that data right as it was flowing down to disk, or even flushed down to disk. If I needed app consistency as well. 103 00:16:30.550 --> 00:16:34.810 Jirah Cox: helping those those most complicated applications right? Get off site and get protected. 104 00:16:35.600 --> 00:16:46.790 Jirah Cox: And then the the metro multi-site is such a neat way to phrase this ability now to have a workload that runs with sort of 2 sites, keeping it in full lockstep right full synchronous replication. 105 00:16:46.810 --> 00:17:05.559 Jirah Cox: and then also still have a 3rd site that catches an asynchronous replica as well. So I can now have, you know, 0 data loss recovery among 2 sites, and still have a whole 3rd site participating in that. That's asynchronous as well, for even like a sort of a near, near, far recovery and availability model for my my critical data. 106 00:17:06.660 --> 00:17:30.260 Philip Sellers: Yeah. And and you know, Ben, as as we talk about multi cloud snapshot technology, this, to me, is really interesting, because for the 1st time you're leveraging, not Nutanix necessarily as the destination for that replication. You're actually directing it to S. 3. I mean that that seems like it's gonna be a a significant cost savings and you know, for certain use cases, but not all. 107 00:17:31.143 --> 00:17:32.410 Philip Sellers: Maybe worth. 108 00:17:33.279 --> 00:17:38.909 Philip Sellers: you know, stepping back from really aggressive sort of Rpos or rtos. 109 00:17:38.910 --> 00:17:56.009 Ben Rogers: Well when when he, when he was describing this man healthcare, came to my mind with active active in a tertiary backup, I mean, that's that's screaming healthcare infrastructure right there. So absolutely right again, I just think this goes to our commitment to to our customers to have 110 00:17:56.040 --> 00:18:23.049 Ben Rogers: world class replication and Dr. Services again. You know I don't want to minimize the Hypervisor with this conversation, but when customers go into cloud they're not looking at the Hypervisor, the hypervisor is just part of the service that's delivered. They're looking at more of things like, how do I replicate my data? How do I protect my data. How do I give my data governance so that it stays in the realms? And these are all the things that we're delivering. Now. 111 00:18:23.350 --> 00:18:23.990 Ben Rogers: yeah. 112 00:18:23.990 --> 00:18:27.820 Jirah Cox: And I agree with you, Phil, that like that, you know, I think it speaks to how many customers 113 00:18:28.010 --> 00:18:28.920 Jirah Cox: want 114 00:18:29.110 --> 00:18:44.570 Jirah Cox: nowadays to have their 1st 4 I'd be like, how do I use cloud for Dr. For my workloads? It's such a juicy target in their minds of. I get to close this entire whole other data center that has always kind of been like sort of a boat anchor for procurement of like, I get to buy 2 and only use one of them. 115 00:18:44.570 --> 00:19:06.960 Jirah Cox: Well, now, I get to spend less on that second copy right, because I can rent it in the cloud. Keep the the running cluster. Very tiny. Right? The pilot light nutanix cluster and then let that offload data into other cloud native storage. Right? So it's sort of the more direct and most effective way to use cloud as a Dr. Target cost. Effective technology, effective accomplishes the mission as well. So I think it's really exciting. 116 00:19:07.830 --> 00:19:13.349 Philip Sellers: Yeah. And honestly, I mean doing some architecture training that I mentioned earlier. 117 00:19:13.560 --> 00:19:32.079 Philip Sellers: You know, it's great to say, multi site. You know, Metro. Dr. Here, there's still a lot of planning that goes in on that. But it's really cool technology. You know. I I worked in a a place where we did, Metro clustering. And you know, stretch vlans between our 2 data centers. And 118 00:19:32.250 --> 00:19:38.220 Philip Sellers: you know it. It is the Nirvana state of disaster avoidance. Right? This. 119 00:19:38.220 --> 00:19:41.259 Jirah Cox: I'm sure it's super easy to get there, and very easy to maintain. 120 00:19:41.680 --> 00:19:42.535 Ben Rogers: No. 121 00:19:43.390 --> 00:19:48.824 Philip Sellers: Hey? I will say the software helps a lot when it comes to that. Easy to maintain thing right. 122 00:19:49.110 --> 00:19:56.290 Jirah Cox: It's not a part of a solution that we all work together to provide. Right. It's not a 1 click. Turn it on, you know instantly now, your metro, all the things. 123 00:19:57.070 --> 00:19:58.719 Ben Rogers: We do we do 124 00:19:58.750 --> 00:20:10.149 Ben Rogers: in Phil. I totally agree with you. It's not the easiest thing in the world, but we do make this process easier for our customers, where they have less gears, they have to turn 125 00:20:10.150 --> 00:20:36.879 Ben Rogers: before it was networking, you know, storage, compute blah blah blah with with this solution that we're bringing. There's always going to be networking, you know. That's the 1st thing customers have to deal with when they go in the cloud is, how do I get my networking to catch up with what I'm doing on? Prem, but the back end of how you set the volume groups up to be replicated and ensuring and monitoring of that replication reporting, we do make those things easier because we bring that into the platform. 126 00:20:37.060 --> 00:20:45.240 Philip Sellers: And it's a great point, guys like I that wasn't a knock on software at all. You guys make it easier for sure. But that networking piece. 127 00:20:45.670 --> 00:20:57.050 Philip Sellers: The plumbing is still pretty hard, and and especially as an infrastructure. Guy, I you know I even sleep in a holiday inn express last night like, I got no claim to networking whatsoever. So 128 00:20:57.999 --> 00:21:06.969 Philip Sellers: it's it's 1 of those things where, yeah, we we definitely have to have our partners help. And there's a lot of planning that goes into making this magical. 129 00:21:08.200 --> 00:21:20.790 Philip Sellers: yeah. But as we talk about networking, that's a great segue into Number 4 here network security offering enhanced security connectivity and cyber resilience. Jaira, I'll throw it over to you. 130 00:21:20.790 --> 00:21:44.459 Jirah Cox: If you hadn't made the segue. I was going to. Yeah, for sure. It was an amazing team. And I was also just making the point of like, you know, as it's a solution that we all drive towards consultatively right, that it's not just not just, you know, one product, right? But the partner. And it matters the integration matters, the operational practices matter. And to both of your point, yeah, we definitely can help make the networking part a little simpler as well by offering our own Sdn stack as well 131 00:21:44.460 --> 00:21:56.029 Jirah Cox: to be that network stretched layer when your workloads require that right? There's also obviously lots of ways. You can do it from private data center to private data center. Do it in the fabric, do it in your top rack, do it lots of different ways. 132 00:21:56.330 --> 00:22:04.429 Jirah Cox: You can do it purely in software, and you almost need to when one of those clusters is going to be in the cloud right where there is no top rack that you can go touch. 133 00:22:04.560 --> 00:22:25.720 Jirah Cox: So now, with some of the maturity brought to flow network the flow networking stack right on both the security and the networking side of things. Some really great stuff to call out is, of course, there's a new dashboard again. It did come out in 6.6. But now everyone gets that by just doing their regular standard. I would almost say boring Tnx updates, you just get new functionality, get new features 134 00:22:25.720 --> 00:22:38.480 Jirah Cox: on the cluster. You're already running really good stuff that you know the calls out here, protecting your data, safeguarding your network. And of course, helping you as the Admin host, to kind of own and wrangle all of this ensure more operational security more easily. 135 00:22:39.500 --> 00:22:44.789 Jirah Cox: But then, also, yeah, flow networking security goes next. Gen now 136 00:22:44.840 --> 00:22:56.780 Jirah Cox: brings the controller for all that into prism central along with basically the entire stack, whole platform, right? More and more management done through prism central. So fewer places to go to do things as part of your day job. 137 00:22:56.830 --> 00:23:19.980 Jirah Cox: but also really now cool is that flow networking can also now help you do more security, oriented operational activities, right? Like traffic, monitoring traffic, mirroring policy management, scaling to clouds, stretching your networks out there when you need to, and really just helping you stay in a posture to stay on the alert against threats in real time, in your environment. 138 00:23:22.030 --> 00:23:24.140 Philip Sellers: You know it's interesting here, and 139 00:23:24.780 --> 00:23:39.885 Philip Sellers: I'm not one to brag but I have to brag on my managed services team. So we. We implemented both flow network security and flow virtual networking in our data centers. And 140 00:23:41.000 --> 00:23:44.345 Philip Sellers: I guess it's been maybe a month and a half ago. 141 00:23:44.760 --> 00:23:55.650 Philip Sellers: Our colo provider, had an outage at the facility where we we host in Atlanta. So during that outage we had customers affected, obviously, that we're hosting for? 142 00:23:55.720 --> 00:24:22.289 Philip Sellers: Well, because of what we've done in the networking stack with flow we were able to fail over and get our customers back online in 7 min. So shout out to my manage services team, also to the development team at Nutanix around that it's a perfect example. And and that's 1 of the things that we always say is a differentiator for us here at integra. We're running the same things. You're running as a customer, and so we can talk about our experiences. 143 00:24:22.420 --> 00:24:30.370 Philip Sellers: If that's not proof, I don't know what it is. But shout out to my managed services team, because, you know, those calls come at 144 00:24:30.450 --> 00:24:35.179 Philip Sellers: really bad times in the middle of the night, when you're not, you know. 145 00:24:35.560 --> 00:24:37.639 Philip Sellers: probably the most awake and. 146 00:24:37.640 --> 00:24:38.120 Jirah Cox: Yeah. 147 00:24:38.120 --> 00:24:51.499 Philip Sellers: You're getting out of bed to respond to these things. And these guys did an amazing job and had the customer back online in 7 min. Just an amazing kind of illustration of how good this technology is today. 148 00:24:51.500 --> 00:24:53.120 Jirah Cox: No, that really is fantastic. Kudos. 149 00:24:53.120 --> 00:24:54.029 Ben Rogers: You're not even. 150 00:24:54.030 --> 00:24:54.880 Jirah Cox: Everyone involved. 151 00:24:54.880 --> 00:24:59.080 Ben Rogers: The money that you saved them for only being down for 7 min. 152 00:24:59.260 --> 00:25:21.794 Philip Sellers: No, not at all. I I mean, there's implications, financially, operationally. You know, everywhere in the stack there, there's implications here, but you know there was an investment of time to configure this, to set it up, make it interoperable with our physical, networking infrastructure. But you know it also saved us. 153 00:25:22.330 --> 00:25:29.778 Philip Sellers: you know, to a great degree, during a Dr. Situation, a real world, Dr. Situation. So it's proven technology. 154 00:25:30.300 --> 00:25:40.519 Philip Sellers: we probably didn't set out to prove it on Saturday morning, a a month and a half ago. But you know I'm glad that it it worked out well for us. And it's a success story today. 155 00:25:40.870 --> 00:25:41.540 Philip Sellers: Yeah. 156 00:25:41.760 --> 00:25:50.308 Ben Rogers: I think one of the biggest sections with this is is, you know, our existing customers that have come from prison element into 157 00:25:51.008 --> 00:26:07.320 Ben Rogers: prism central, and have, you know, I don't want to say, gone through some growing pains, but have gone through some growing pains. This really is starting to show the commitment of Nutanix to our, you know, prism Central, and getting more services in there. And you know, trying to get to that. I don't want to say, one pane of glass, but 158 00:26:07.320 --> 00:26:25.920 Ben Rogers: a centralized environment where you can look at all the micro services in one, in 1 1 application. And so, you know. I'm glad to see that we're we're committed this to Prism Central and getting more services into there, and I'm glad to see all these Sts. Lts are bringing us a little closer to that. 159 00:26:26.420 --> 00:26:27.740 Philip Sellers: Yeah, 100%. 160 00:26:27.810 --> 00:26:39.900 Philip Sellers: Well, and and you gave us another great segue, Ben, I, I have to say, last up here is streamline management and automation, just one of the other services delivered. And 161 00:26:40.620 --> 00:26:44.101 Philip Sellers: yeah, we've we've got a number of new things here. 162 00:26:44.500 --> 00:27:00.360 Philip Sellers: you know. But again, building on what's been released in the incremental things, you know. Fine grain. Our back is a big one that came with 6.8 but let's talk a little bit about, you know. Streamlined management and automation. Jaira, I'll throw it to you. 163 00:27:00.700 --> 00:27:12.034 Jirah Cox: Sure. That that's definitely part of it. Right? more detailed, more configurable. Our back controls, of course, helps the entire organization. Right operations, team security teams, networking teams. 164 00:27:12.580 --> 00:27:28.949 Jirah Cox: as as we, you know, help. Our customers have a path to streamline and sort of democratize all operations. We know that not everyone's there yet. Right? So when I need to have just a certain team that can only do certain operations, that kind of a management model and and policy engine helps with all of that. 165 00:27:29.560 --> 00:27:38.639 Jirah Cox: But also even things like like data centric policies where I can tag a Vm or apply a category to it in the PC parlance. But with that category have that. 166 00:27:38.710 --> 00:28:00.649 Jirah Cox: Do things like affect my Vm replication status for offsite affect? Who can see it affect my data reduction on it. Do I want to apply compression to it? Do I want to have it be rf, 2 or Rf, 3. From a data, resilience, perspective, all these things that I can now do via policies that in before I had to do sort of as the admin and making and making careful and 167 00:28:00.720 --> 00:28:14.789 Jirah Cox: purposeful placement decisions right? But now I can really change virtually anything about the environment from one state to another, just by changing my changing my policies that apply to that object. So that allows for a lot of simpler planning. 168 00:28:14.910 --> 00:28:29.930 Jirah Cox: faster, faster execution, and sort of simplifies the stack right before. Where, if I would have needed multiple, say, like data stores for things like data reduction versus richer coding versus Rf, 2 versus Rf, 3. Now, I can have just one and have policies that apply to the workloads where they need to 169 00:28:30.530 --> 00:28:50.299 Jirah Cox: for access control. We, of course, are still rolling out v. 4 Apis across the board. This calls out how the ones in this release are released candidate. So they're able to be inspected. And you can start planning on moving operations. Automations. There we go to using those V 4 Api endpoints. That'll be great. And then a long time 170 00:28:50.300 --> 00:29:02.559 Jirah Cox: asset. It's so great to to have fully solved. Now is that ability for Ngt installs or guest tools? You can now install them really, any which way you want to write ansible terraform. 171 00:29:02.760 --> 00:29:16.989 Jirah Cox: Sccm. Powershell, any which way you wanted to. You can now spray out the Ngt. Installation itself as opposed to needing us to do it for you. So you had to script us versus. Now we can give you the payload. You install it on your own vms 172 00:29:17.330 --> 00:29:25.450 Jirah Cox: that allows more customers to use that more places more easily right. So making the guest tools kind of a lighter touch more broadly applicable. Installation 173 00:29:25.700 --> 00:29:29.320 Jirah Cox: is is fantastic. Right lets our customers solve problems the way that they want to. 174 00:29:30.870 --> 00:29:53.169 Jirah Cox: And then we also did bring out this new extra small prism central. It's it's travel size for your convenience, right? So when you need one at the edge. It's tinier and smaller. So that when you want this sort of prism, central based management construct, which is kind of, you know, really the direction we're headed across the board. I can now put one of those really anywhere, and it can be a right sized workload for the environment that it wants to run in. 175 00:29:54.140 --> 00:30:01.780 Philip Sellers: You know that that's an interesting one to talk about, too, because, as we pack more goodness into prism central, you know, it 176 00:30:01.790 --> 00:30:06.689 Philip Sellers: really hasn't significantly grown in a while. We've 177 00:30:06.860 --> 00:30:13.019 Philip Sellers: yeah. It's another thing to point out, like the high end, large or extra large. 178 00:30:13.690 --> 00:30:16.439 Philip Sellers: is still kind of consistently 179 00:30:16.590 --> 00:30:18.239 Philip Sellers: the same. So 180 00:30:18.749 --> 00:30:26.260 Philip Sellers: kudos to the team, developing in that same footprint, but adding and incrementally pushing things forward. 181 00:30:26.893 --> 00:30:27.780 Philip Sellers: You know 182 00:30:27.990 --> 00:30:29.920 Philip Sellers: we we must be 183 00:30:30.470 --> 00:30:41.209 Philip Sellers: busting at the seams, I guess, would be the right way to say it in our current sizing for prism central. So but there's so much goodness that is is being built in 184 00:30:41.724 --> 00:30:53.779 Philip Sellers: you know, Ben, as as you talk to customers and stuff in the field. Let's talk about that robo use case that Jira mentioned, like the extra small prism central, the robo, you know. That's that's 185 00:30:53.790 --> 00:30:55.650 Philip Sellers: somewhat of a newer 186 00:30:57.880 --> 00:31:07.169 Philip Sellers: I guess. Subscription style for Nutanix. Are you seeing a lot of interest in it, because I know I am with with customers. I talk to. 187 00:31:07.890 --> 00:31:33.810 Ben Rogers: On the robo side, not so much on the prism central, I think, where a lot of people are gravitating towards Robo is just the multi micro services that we can run there as far as like, it doesn't have to be just vms or containers or unified storage. You know, it can literally be all 3 or 4 of those services running at the edge. And then AI is becoming a big thing. You know. We're talking to customers that are in kind of a retail market in. 188 00:31:33.810 --> 00:31:39.880 Ben Rogers: They're looking for having Gpus on the edge to do some AI for 189 00:31:40.362 --> 00:31:56.309 Ben Rogers: buyer buyer trends, you know. If they see things in the store being able to interact with the buyer. So we see a lot of interest on our robo just being multi serviced and being able to do it in one cluster instead of multiple clusters per service. 190 00:31:57.520 --> 00:32:04.150 Philip Sellers: Yeah. And and that echoes some of what I'm hearing with customers, too. They want to do more analysis at the edge 191 00:32:04.170 --> 00:32:27.540 Philip Sellers: rather than transmitting everything back to a data center or to the cloud provider. And Robo is a compelling offering for a lot of customers with branch locations and retail locations. And so it's really a a good way of repackaging all the great things we've talked about into a very cost effective 192 00:32:28.324 --> 00:32:37.889 Philip Sellers: package for the edge. So if if you're listening and you're not sure what we're talking about, you can find information online for Nci Edge. 193 00:32:37.960 --> 00:32:44.600 Philip Sellers: It's kind of a robo based per vm. Packaging for all this in Nutanix. Goodness, we're talking about and 194 00:32:44.720 --> 00:32:53.289 Philip Sellers: certainly reach out to your Nutanix or Zintegra rep, and and we'll help you get connected with information. If that sounds like something that could help you in your business. 195 00:32:53.290 --> 00:32:58.369 Ben Rogers: Now, listeners, I'm gonna ask this question from a customer standpoint, because I've 196 00:32:58.440 --> 00:33:01.649 Ben Rogers: just going through a deal with this and learning about it myself. 197 00:33:01.940 --> 00:33:06.969 Ben Rogers: If I understand the robo licensing you pretty much buy it per vm. 198 00:33:07.060 --> 00:33:22.249 Ben Rogers: So you buy it, I think, like, in 25 vm. Packages. But it doesn't have to be per site, so you could buy like a pool of vms and then spread those across. How many ever sites that you would have so like, example, if I've got 3 sites 199 00:33:22.250 --> 00:33:40.960 Ben Rogers: and they've got 25 vms before those between those 3 sites, I can buy a 25 impact licensing and use it across those 3 sites. It don't have to be a license per site, if I understand the way we've done that correctly, Jaira and Philip, please keep me honest there as I'm I'm regurgitating that back. 200 00:33:42.890 --> 00:33:45.250 Jirah Cox: There are some parts that I 201 00:33:45.880 --> 00:33:55.180 Jirah Cox: don't devote a lot of brain cells to memorizing and look up when I need to. You've got more detail at your fingertips there than than I do at mine. So I'm going to defer to you, Ben. 202 00:33:55.180 --> 00:33:55.890 Ben Rogers: Yeah. 203 00:33:55.890 --> 00:34:03.430 Philip Sellers: Yeah, I I think that there's a lot of flexibility based on what we've worked and and again, with. 204 00:34:05.720 --> 00:34:10.713 Philip Sellers: the competitor with a V name. Do we want to call it Voldemort? Maybe. 205 00:34:11.494 --> 00:34:23.719 Philip Sellers: that was a terrible terrible joke. They've eliminated their per vm licensing. So you know it's it's 1 of those things where it's definitely a compelling offering that that we 206 00:34:23.820 --> 00:34:26.149 Philip Sellers: we're talking about more and more. So. 207 00:34:26.170 --> 00:34:27.199 Ben Rogers: Yeah, for sure. 208 00:34:29.269 --> 00:34:33.724 Philip Sellers: roll ups. I think it's time to roll up this. 209 00:34:34.249 --> 00:34:54.330 Philip Sellers: podcast based on roll ups and 6.10. So I am not hitting on much with my jokes at this point. I'm just getting blank stares back. So I think that's a sign that we probably just need to cut this one off today. Guys, 6 dot 10 is a huge milestone, though, and we're gonna have this version out for a while. 210 00:34:55.079 --> 00:34:58.519 Philip Sellers: so there, there's a lot of great things to 211 00:34:59.339 --> 00:35:00.779 Philip Sellers: to make use of. 212 00:35:00.939 --> 00:35:13.459 Philip Sellers: Is there anything that sticks out for either of you that's been in the last sts releases that 6 dot 10 delivers for the mainstream customer that they should absolutely check out. 213 00:35:15.780 --> 00:35:24.005 Jirah Cox: Almost hard to avoid it. Live migration improvements, I mean, migration is part of what we do all day, every day. For sure. And then 214 00:35:24.490 --> 00:35:33.000 Jirah Cox: better, easier, faster, more accessible sort of software to find networking as well. Just so can be such a problem. Solver kind of like your your excellent example. There, Phil. 215 00:35:33.430 --> 00:35:35.380 Jirah Cox: when you need it, you really really need it. 216 00:35:35.380 --> 00:35:36.529 Philip Sellers: Yeah, absolutely. 217 00:35:36.980 --> 00:35:59.580 Ben Rogers: I think some of the granularity with our our back is important for security organizations and being able to get people in the system. So now I'm seeing more junior engineers having access to Nutanix where before, because the limit of the Rbac. We couldn't do that. So just now, being able to bring more junior people in because you have more of a stricter. Our back policy that's huge 218 00:35:59.580 --> 00:36:14.740 Ben Rogers: for security organizations is huge for us, because it brings more people into our ecosystem to learn how to use it. And these junior engineers now become senior engineers one day, and so very grateful to see that coming to it, and I've had some customers thank me for bringing that in. 219 00:36:15.060 --> 00:36:15.670 Philip Sellers: Yeah. 220 00:36:16.090 --> 00:36:39.719 Philip Sellers: Well, guys, I I definitely appreciate your time talking about Aos 6.1 0. I don't think I actually said the name of the blog post. So blog post is, elevate your it. Infrastructure with long term support. Release. Nutanix aos 6.1 0. This was written by Alan waters. I think he's on the Nutanix tech marketing team. So shout out to Alan and the entire tech marketing team. 221 00:36:39.720 --> 00:36:46.769 Philip Sellers: We appreciate what you do because it lets us do what we do. So shout out to to you and the team. 222 00:36:47.322 --> 00:36:54.139 Philip Sellers: On behalf of Jaira and Ben. I want to say thanks for spending a little time with us this afternoon, guys. Thank you for your time 223 00:36:54.210 --> 00:36:55.290 Philip Sellers: and 224 00:36:55.430 --> 00:36:58.639 Philip Sellers: for everyone listening. We'll catch you on the next episode. 225 00:36:58.820 --> 00:37:00.149 Philip Sellers: Hope you have 226 00:37:00.480 --> 00:37:01.980 Philip Sellers: a great evening. 227 00:37:03.000 --> 00:37:03.770 Ben Rogers: Have a good one.