Nutanix Weekly
Join XenTegra on a journey through the transformative world of Nutanix’s hyper-converged infrastructure. Each episode of our podcast dives into how Nutanix’s innovative technology seamlessly integrates into your hybrid and multi-cloud strategy, simplifying management and operations with its one-click solutions. Whether you're operating on-premises or in the cloud, discover how Nutanix enables always-on availability, intelligent automation, and the operational simplicity that drives business forward. Tune in for expert insights, real-world success stories, and interactive discussions. Engage with us as we explore how to harness the full potential of your IT environment in this rapidly evolving digital landscape.
Nutanix Weekly
Nutanix Weekly: Elastic SAN and Nutanix Move for Azure VMware Solution With NC2
Nutanix is excited to announce the upcoming tech-preview of Elastic SAN support for Nutanix Cloud Clusters (NC2) on Azure solution and the ability to easily move workloads from Azure VMware Solution (AVS) to NC2 on Azure with the Nutanix Move migration tool.
Blog Post: https://www.nutanix.com/blog/elastic-san-and-nutanix-move-for-azure-vmware-solution-with-nc2
Host: Phil Sellers, XenTegra
Co-Host: Jirah Cox, Nutanix
Co-Host: Chris Calhoun, XenTegra
1
00:00:02.790 --> 00:00:20.340
Philip Sellers: Hello, and welcome to another episode of Nutanix Weekly, the XenTegra podcast that focuses on the best content on the internet, all about Nutanix. I'm your host, Phil Sellers. I'm also the practice director for Modern Data Center here at XenTegra.
2
00:00:20.340 --> 00:00:29.019
Philip Sellers: And, you know, I couldn't do this alone, so I, of course, have my merry band of men joining me again today.
3
00:00:29.020 --> 00:00:42.070
Philip Sellers: We've got Jirah Cox from Nutanix. Jirah's a primary architect and long-time guest on this podcast. Jirah, how are things going in your neck of the woods?
4
00:00:42.070 --> 00:00:49.849
Jirah Cox: Good, I'm happy to be a member of the merry band. The tights are a little restricting, I gotta say, but, you know, I'll adapt.
5
00:00:49.850 --> 00:01:00.800
Philip Sellers: Yeah, for sure. That was not the best decision you made, was making us wear tights. I will say that we questioned it a little bit. Jirah?
6
00:01:02.970 --> 00:01:12.300
Jirah Cox: It's, you know, uniforms help, drive group coherence, right, and form a sense of camaraderie. This is… history's proven this over and over.
7
00:01:12.710 --> 00:01:23.890
Philip Sellers: Yeah, well, you know, the next Mary Band brother, Chris Calhoun, he does love that hat, the little green hat with the feather in the top. He's a big fan of that, so,
8
00:01:23.890 --> 00:01:30.340
Chris Calhoun | XenTegra: Chris, how are things going in your world? Between that and the pointy shoes, I am digging the outfit.
9
00:01:30.400 --> 00:01:42.440
Philip Sellers: Well, if you ever get kicked off of this, I guess there's room for you at the North Pole as an elf. We're coming up on that season, too, so, you know, there's always more that could be had, right?
10
00:01:42.440 --> 00:01:47.009
Chris Calhoun | XenTegra: That, and some stretchy elastic waist, for our waistband.
11
00:01:48.390 --> 00:01:49.260
Jirah Cox: This is the season.
12
00:01:49.260 --> 00:01:49.870
Chris Calhoun | XenTegra: Hmm.
13
00:01:50.360 --> 00:02:02.959
Philip Sellers: Well, this Merry Band of Brothers, as always, I appreciate you being here, and it's always fun to talk tech, and you know, last week was a big week for Microsofts, and…
14
00:02:02.960 --> 00:02:13.100
Philip Sellers: They held their Ignite event in San Francisco. We had a few people out there, and we also brought along some customers. That's one of the things we really love to do, is
15
00:02:13.130 --> 00:02:27.700
Philip Sellers: to provide an opportunity for the community to come out to these big tech events, learn about the technology that they're investing in, and where things are going in the future. And so, I know we had team members, including our CEO, Andy Whiteside.
16
00:02:27.700 --> 00:02:35.020
Philip Sellers: out at, Ignite, and entertaining some customers. So, it was a really good week.
17
00:02:35.020 --> 00:02:49.870
Philip Sellers: And, if you'd like to maybe participate in one of those industry conferences, we've got information about that out on the XenTegra website. For instance, hint, hint, nudge, nudge.next!
18
00:02:49.940 --> 00:03:07.199
Philip Sellers: We'll be in Chicago, I believe, next year, and we're looking forward to bringing customers along. So, you know, if you're interested in getting into some Nutanix goodness in Chicago, then reach out. Let's talk about how we can get you there and help,
19
00:03:07.200 --> 00:03:10.820
Philip Sellers: Help cover the expenses of .NEXT, next year.
20
00:03:11.490 --> 00:03:16.710
Philip Sellers: So, I mentioned Microsoft because…
21
00:03:16.860 --> 00:03:33.200
Philip Sellers: Nutanix had a pretty decent present out there at Ignite, and they had some announcements, and so today we want to talk about, what was announced during Microsoft Ignite last week, a couple big announcements around Azure.
22
00:03:33.200 --> 00:03:49.390
Philip Sellers: And so, we're gonna dig in on that. So, today's blog post that we're gonna be talking about is Elastic SAN and Nutanix Move for VMware… Azure VMware Solution with NC2. So, a couple things to help, switchers.
23
00:03:49.390 --> 00:03:59.649
Philip Sellers: that are looking at moving from Azure VMware Solution to Nutanix Cloud clusters. So, I guess, what's the big news? Jirah, let's start there.
24
00:04:00.270 --> 00:04:12.940
Jirah Cox: I guess you could say the big news is, like, giving customers what they've asked for. You and I both have a ton of customers in Azure, right? Very popular cloud among our customer demographic.
25
00:04:12.940 --> 00:04:22.760
Jirah Cox: Of choice, right? A lot of VMs there, and a lot of VMs that customers want to, get a solution for, right? For, like, what's their long-term home gonna look like? And…
26
00:04:22.910 --> 00:04:29.160
Jirah Cox: So, these announcements, have been, certainly something I've heard from customers a lot.
27
00:04:29.630 --> 00:04:43.269
Jirah Cox: thrilled to see this now, getting talked about and coming out shortly. But yeah, like that, in order, that first one there, Elastic SAN integration, right? That, gives customers even more flexibility with how they want to get deployed.
28
00:04:43.380 --> 00:04:47.759
Jirah Cox: onto, Nutanix in Azure, right? Nutanix in the cloud.
29
00:04:48.000 --> 00:05:06.820
Jirah Cox: Where we normally run on, you know, bare metal hardware that's in your tenant, right? But as it's… as it's bare metal hardware in the Azure fleet, it's got a defined, you know, size, right? Like, no one's gonna run out there and add more drives into it just because you ask them to, because, you know, these are very lights-out data centers that, you know, people don't go touch.
30
00:05:06.820 --> 00:05:19.420
Jirah Cox: therefore, the traditional solution's been, when you want more storage, you get more nodes, right? Kind of the old, reality of HCI from 10, 12 years ago, right, was, like, inflexibility of hardware, therefore when you want
31
00:05:19.420 --> 00:05:27.030
Jirah Cox: more of anything, you gotta buy more of everything, right? Now, of course, we all know that's not the case for HCI on-prem, right, where you have a lot of flexibility to tailor what you want.
32
00:05:27.160 --> 00:05:45.649
Jirah Cox: But it all involved touching the nodes. When I can't go touch the nodes in the data center, then there's constraints. So this is such a wonderful solution to that, of getting more flexibility around, I want X amount of storage, but I want Y compute, I want Z memory, and I can now kind of customize some of those parameters by adding more storage to the nodes.
33
00:05:45.650 --> 00:05:48.120
Jirah Cox: via Azure Elastic SAN.
34
00:05:49.320 --> 00:05:52.220
Philip Sellers: Yeah, you know, this is one of the,
35
00:05:52.230 --> 00:06:09.829
Philip Sellers: great things that we got a little earlier in the competing cloud in AWS. It's a very welcome sort of addition, heh, no pun intended, to what we have inside of Azure. Chris, you know, this addresses one of the primary
36
00:06:10.000 --> 00:06:14.400
Philip Sellers: constraints that we've kind of had in Azure, and what is that?
37
00:06:15.800 --> 00:06:17.549
Chris Calhoun | XenTegra: Definitely no types.
38
00:06:17.680 --> 00:06:35.459
Chris Calhoun | XenTegra: that's been something to me that, as we've worked with several customers that are looking for that flexibility, they are already existing Microsoft customers because, of course, they're either M365, O365, whatever the name is, but they have
39
00:06:35.790 --> 00:06:52.869
Chris Calhoun | XenTegra: Azure capabilities, or even have some workloads there. So, getting the right configuration and not having to fit Nutanix in a very small, isolated, shaped box of gear is really something that I think that now
40
00:06:52.980 --> 00:07:04.310
Chris Calhoun | XenTegra: as Azure looks to adopt more of this solution for, quote, the movers, this is a good solution for them. You know, obviously, they've been new to…
41
00:07:04.310 --> 00:07:14.619
Chris Calhoun | XenTegra: I'm sorry, they've been VMware customers in the past, but they've also been Microsoft customers for a long time. So let's… let's take that Microsoft
42
00:07:15.030 --> 00:07:28.129
Chris Calhoun | XenTegra: And extend that to, okay, now let's bridge the gap away from VMware and integrate that within, the Nutanix stack, and give you some flexible options that they haven't previously had.
43
00:07:28.430 --> 00:07:40.540
Philip Sellers: Yeah. Yeah, no, this is very welcome news. Again, you know, we have a few more node types. In reality, you know, as I've gone through helping fit customers on AWS nodes.
44
00:07:40.620 --> 00:07:53.210
Philip Sellers: The conversation generally comes back down to a couple of node types. There may be 7, or 10, or 12, or whatever the current number is available, but really, most workloads fit in on a couple of different node types.
45
00:07:53.610 --> 00:08:12.020
Philip Sellers: it's… it's very similar on the Azure side, you know, we have 3 different node types, and they're available in different regions. So, now, this addresses a huge thing when you need more storage in a cluster, you don't necessarily have to add nodes. So that's a welcome thing.
46
00:08:12.020 --> 00:08:18.589
Philip Sellers: And it kind of makes me think, you know, it's really useful for disaster recovery use cases.
47
00:08:18.590 --> 00:08:34.490
Philip Sellers: you know, having a 3-node cluster, but then being able to grow out the storage, that makes disaster recovery a much more viable option to cloud. And that's one of the places I think we're seeing in conversations a lot of interest for customers.
48
00:08:34.570 --> 00:08:49.689
Philip Sellers: Let's talk a little bit about how it works, Jirah. What's happening under the covers? You know, when we talk about this on an AWS perspective, we're attaching elastic block storage, or EBS, to the Nitro card.
49
00:08:49.850 --> 00:08:52.989
Philip Sellers: What are we doing with Elastic SAN here in Azure?
50
00:08:54.000 --> 00:09:00.609
Jirah Cox: So with Elastic SAN, right, what's cool about this is this is actually using, Azure storage that is connected
51
00:09:00.620 --> 00:09:11.859
Jirah Cox: Of course, to join up in the CVM, so I have local NVMe storage in the node, and then I also have a separate tier of storage that exists over in Elasticsend that the CVM
52
00:09:11.860 --> 00:09:21.919
Jirah Cox: knows how to reach out and route over to, of course, over the Azure network, right? And there's some of the… we'll talk about some of the networking, perhaps, a little bit down, around the provisioning there.
53
00:09:22.050 --> 00:09:40.799
Jirah Cox: But this gives a customer an opportunity, like, I think the DR use case is fantastic, right? A great way to test this out is, for disaster recovery, I obviously need all the storage for all my stuff, right? I gotta have all my… all the bits there when I have a disaster. But I can definitely take time to add a note or two.
54
00:09:40.830 --> 00:10:00.389
Jirah Cox: to be able to fit all the runtime for my VMs, right? CPU memory, and I don't need that all of the time, right? I can shave down my solution costs that way by getting some of that on-demand later on. So this has, the article calls out about a 4X enabler for what we can now address. So if a node had 18 terabytes of storage.
55
00:10:01.060 --> 00:10:15.119
Jirah Cox: in… inside of it internally, in the local NVMe, that now means the node can address about close to 75 terabytes of storage overall, right? So, like, almost a 5x effect, or adding 4X storage in the external tier there.
56
00:10:15.120 --> 00:10:25.059
Jirah Cox: For nodes that were closer to 30 terabytes, that's in the mid-140s now for what it can address. So a huge, huge enabler here, right? That's effectively, like, getting the storage of 5 more nodes.
57
00:10:25.080 --> 00:10:29.839
Jirah Cox: Without paying for 5 more nodes, right, on the first node that I already was paying for.
58
00:10:30.090 --> 00:10:38.689
Jirah Cox: So it does act as a Tier 2 remote storage there, which just means the CDN can tell the difference between the NVMe that's in the node and the storage that's not in the node.
59
00:10:38.690 --> 00:10:51.950
Jirah Cox: spoiler, we've been doing that in ATANX for, like, 16 years now, right? Is profiling workloads, understanding what is the truly hot stuff, put that locally, or it used to be… it used to be on, like, the… the… the, what, SATA SSD?
60
00:10:51.950 --> 00:11:05.999
Jirah Cox: Right? And the colder stuff could fit on the spinning HD next to it, right? And nowadays, we can use that exact same logic around, hey, this goes on my local NVMe, and this goes on my NVMe elsewhere in the cloud, right? Which, spoiler, is still really fast.
61
00:11:07.400 --> 00:11:20.309
Jirah Cox: So, helps out for customers that maybe larger storage requirements, right? Like, databases come to mind, disaster recovery replication comes to mind, because this is all still flashbacked, right, from the Azure provider there.
62
00:11:20.820 --> 00:11:27.009
Chris Calhoun | XenTegra: Yeah, from my experience, too, working with a specific customer that we're looking at,
63
00:11:27.410 --> 00:11:32.980
Chris Calhoun | XenTegra: a few different options in Azure. They've… settled on
64
00:11:33.140 --> 00:11:36.870
Chris Calhoun | XenTegra: two different choices. One is kind of light on storage.
65
00:11:37.100 --> 00:11:45.539
Chris Calhoun | XenTegra: So basically, it's a matter of, do we go with more nodes that are light on storage to hit that storage target?
66
00:11:45.720 --> 00:11:51.289
Chris Calhoun | XenTegra: Or, in this case now, we've got options. Let's pick the right model for the…
67
00:11:51.580 --> 00:12:08.569
Chris Calhoun | XenTegra: compute and the RAM, knowing that we can extend that storage a little bit further than what it had been configured in the past. So, that definitely adds flexibility to the customer's base options, and then extending that as you grow.
68
00:12:08.700 --> 00:12:10.579
Philip Sellers: Or as your workload grows.
69
00:12:11.240 --> 00:12:11.790
Jirah Cox: Yeah.
70
00:12:12.080 --> 00:12:19.859
Jirah Cox: Yeah, no, excellent point, right? And what's cool about the way that the article calls out some of the new… I love the phrase, mandatory architectural components.
71
00:12:20.060 --> 00:12:29.889
Jirah Cox: Because it does get people in the right mindset of, there's some new stuff here that you might need to take advantage of this, which is totally fine, that's an easy migration. But you'll want to run this on a cluster.
72
00:12:29.890 --> 00:12:42.430
Jirah Cox: right, that is in an environment that uses the Azure Virtual WAN, VWAN, with a dedicated V-Hub, right? So that's what lets you connect over to Elastic SAN, because it'll drop a private endpoint into your tenant there.
73
00:12:42.430 --> 00:12:58.750
Jirah Cox: So that means that you now get, way faster and non-egress-related access to that service, right? It acts like it's within your tenant there via that private endpoint. Of course, as you can expect, right, this is all super easy, because the Nutanix Deployment Wizard
74
00:12:58.750 --> 00:13:06.400
Jirah Cox: That you'll run in your portal to get this cluster deployed, provisions all this for you, or uses what you've already got if you already have it stood up there.
75
00:13:07.090 --> 00:13:14.860
Philip Sellers: Well, and that's no shocker either, because simplicity and wizard-based creation, that's one of the hallmarks of the Nutanix system on-prem.
76
00:13:14.970 --> 00:13:18.740
Philip Sellers: It does an amazing job of that in NC2 as well.
77
00:13:18.870 --> 00:13:36.360
Philip Sellers: You know, the blog post that we're looking at here also has a demo, so you can kind of see step-by-step Elastic SAN Attach in NC2 through the GUIs, and so that's a really cool, thing that you can follow up on after the podcast today.
78
00:13:37.030 --> 00:13:43.320
Philip Sellers: But, getting started with Elastic SAN, where is this gonna be available, Jirah?
79
00:13:43.840 --> 00:13:53.939
Jirah Cox: So, the article calls out, which is helpful, that it sets expectations here right in it. So, it says, all NC2 Azure regions except for Qatar Central. So, that's…
80
00:13:54.090 --> 00:13:57.410
Jirah Cox: That's a lot of regions. That's… that's coming to a region near you.
81
00:13:57.730 --> 00:14:06.009
Philip Sellers: Yeah, absolutely. We were working… Chris and I were working on this, and actually, Andy Green and I were working on it for a different customer.
82
00:14:06.090 --> 00:14:24.349
Philip Sellers: You know, we've got a lot of new regions coming online, and new node types, and there's been a lot of development inside of Azure, so that's been really great. As for timeline for this, this is going to be in a public preview, tech preview, starting in January.
83
00:14:24.350 --> 00:14:29.130
Philip Sellers: So, there's some information here in the blog post about how
84
00:14:29.130 --> 00:14:33.639
Philip Sellers: You could get involved with this, if you're interested.
85
00:14:33.800 --> 00:14:52.650
Philip Sellers: And so, you know, that's a huge step forward for us, but it is available both to the AN36, AN36P, and the AN64 nodes, so all the different node types, which is amazing. So, all node types, all regions, except Qatar. So…
86
00:14:53.670 --> 00:14:55.430
Philip Sellers: Thank you.
87
00:14:55.880 --> 00:15:06.819
Philip Sellers: Yeah, the next part of this blog post moves on to Nutanix Move support for Azure VMware Solutions. So, Azure VMware Solutions, an in-situ-like
88
00:15:07.020 --> 00:15:18.680
Philip Sellers: environment for the VMware stack, that runs inside of Azure. But as things are changing around Broadcom, you know, folks that had adopted ABS may want an alternate path.
89
00:15:18.860 --> 00:15:21.369
Philip Sellers: Those that have moved to NC2
90
00:15:21.680 --> 00:15:26.470
Philip Sellers: What's this news about? What, what are we getting here with Nutanix Move?
91
00:15:27.410 --> 00:15:31.430
Jirah Cox: So with this release for Move, or this announcement for an upcoming release for Move.
92
00:15:31.440 --> 00:15:39.720
Jirah Cox: This makes it easy for customers to do that technical migration, right, to move a VM from their AVS solution.
93
00:15:39.720 --> 00:15:55.600
Jirah Cox: possibly backed by, say, like, something like NSX, to move that VM over to NC2, right? So staying perhaps in the same Azure tenant, moving from one bare-metal node type with a hypervisor to another bare-metal node type with a different hypervisor, so that it's very much a stay in the cloud.
94
00:15:55.600 --> 00:16:00.810
Jirah Cox: just easily migrate, from, you know, provider A to provider B.
95
00:16:00.810 --> 00:16:17.780
Jirah Cox: kind of prospect here. We've had, of course, general Azure virtualization migration onto NC2, whether that's NC2 or even Nutanix on-prem, forever, right? But this is very much a targeted release offering, so now Gold Star support for AVS specifically.
96
00:16:17.780 --> 00:16:27.699
Jirah Cox: as a, you know, you're in Azure, stay in Azure, just change out the components of your infrastructure here as the proposition, which is a huge help for customers.
97
00:16:30.090 --> 00:16:40.399
Chris Calhoun | XenTegra: Yeah, I definitely think that makes sense, because to me, like we were talking about just a little bit ago, they've made the decision to utilize Azure
98
00:16:40.610 --> 00:16:46.790
Chris Calhoun | XenTegra: As either… Disaster recovery, or for primary workloads.
99
00:16:46.930 --> 00:16:49.770
Chris Calhoun | XenTegra: But… stood…
100
00:16:49.770 --> 00:17:12.149
Chris Calhoun | XenTegra: strong in their decision previously to stay with VMware, and now maybe regretting that decision even more, or looking for a way out. And I think that that's where, Nutanix Move will definitely help, relocate from within Azure, like you said, from one hypervisor over to Nutanix, so that definitely makes sense.
101
00:17:12.150 --> 00:17:29.779
Jirah Cox: Yeah, I mean, we don't let anybody have regrets. We're fundamentally anti-regrets here. I do love the way the article calls out one of the built-in enhancements, or built-in values of Move is that ability to test stuff, right? So if it's… if you're the guy, you're the gal who has to make the change window successful Friday night, 10 o'clock.
102
00:17:29.890 --> 00:17:39.400
Jirah Cox: you could set up this replication from AVS to NC2 in Azure to Azure, and then give it a test, like, Thursday morning, 9am, over a cup of coffee.
103
00:17:39.400 --> 00:17:46.669
Jirah Cox: not touch production at all, no breaking changes at all, but you can get the assurance of, when I hit this button, when it's go time, Friday night.
104
00:17:46.670 --> 00:18:01.300
Jirah Cox: I'm gonna know that my VM can power up, can pull an IP address, can get connectivity 100%, and, you know, we're just, you know, fundamentally, we're against surprises, right? We want success. And you can test it out, you know, non-impactfully, and know that when you need it to work, it's gonna work great.
105
00:18:02.100 --> 00:18:10.550
Philip Sellers: Well, and you hit the thing I was actually going to point out. There's a lot of networking involved in this, right? So…
106
00:18:10.590 --> 00:18:23.070
Philip Sellers: you're mapping to the same VNets, using the same express routes, you know, it's gonna help you test those things across, you know, the same infrastructure that you've already built for AVS.
107
00:18:23.070 --> 00:18:31.220
Philip Sellers: And so that's also a compelling feature for companies that have adopted ABS but are looking for an escape route.
108
00:18:31.220 --> 00:18:34.089
Philip Sellers: From the Broadcom licensing costs.
109
00:18:34.140 --> 00:18:47.530
Philip Sellers: So, that's an amazing thing. Testing, you know, huge, huge advocate of de-risking the situation. Like, who… anybody that's been a practitioner doing these changes at 2 in the morning.
110
00:18:47.770 --> 00:18:56.369
Philip Sellers: One of the things I try to say is we're not always our sharpest at 2 in the morning, you know? I don't care how many cups of coffee you had.
111
00:18:57.640 --> 00:19:07.260
Philip Sellers: So, you know, you want to be able to test these things in business hours and work through it ahead of time and not be caught. I love that, no surprises.
112
00:19:07.260 --> 00:19:15.539
Jirah Cox: Yeah, so the article calls out that, you know, this is going to ship in an upcoming version of Nutinix Move, so watch the support portal for the release notes that will
113
00:19:15.540 --> 00:19:31.299
Jirah Cox: Give you all the details and speeds and fees on that, but… but even right now, if you're having trouble sleeping at night, you can read the required network reports documentation right now around what will be needed to make this work, so… so you can even start planning for that migration right now.
114
00:19:31.530 --> 00:19:34.519
Philip Sellers: Who needs melatonin? We've got network documentation.
115
00:19:37.590 --> 00:19:56.079
Philip Sellers: Well, and that's not the only news. NC2 Azure has also achieved SOC 2 Type 2 compliance, and as a company who's going through SOC 2 Type 2, this is not trivial. I love that it gets only a paragraph in the blog post, but
116
00:19:56.310 --> 00:20:03.840
Philip Sellers: this is a huge deal. It involves a lot of checks and balances, controls and compensating controls.
117
00:20:03.970 --> 00:20:14.129
Philip Sellers: Yeah, this… this is great news. Is there anything else, beyond a high-level headline that you would point out, Jirah, around SOC 2 Type 2 compliance?
118
00:20:14.620 --> 00:20:32.669
Jirah Cox: I think it's great. I mean, MuseumX has always made security, extremely important to us, the way we develop, the way we run software, make it easier for our customers with the most secure of secure environments to be able to adopt our platform, and run us as a solution. So, yeah, we take security extremely seriously.
119
00:20:32.670 --> 00:20:48.219
Jirah Cox: But yeah, but on that note, if you've got super insomnia, right, we also have security documentation you can read, to help out as well. If the network report documentation doesn't, doesn't cut it for you. There's links all over this paragraph to where you can go read the pedigrees and attestations around these security controls.
120
00:20:48.300 --> 00:20:59.009
Philip Sellers: Yeah, there's more ISO designations and numbers than I think we have in the actual alphabet, so, you definitely could get yourself some, some heavy reading.
121
00:20:59.650 --> 00:21:05.180
Chris Calhoun | XenTegra: And is that a Mar- one of the new Marvel, characters, or…
122
00:21:06.070 --> 00:21:06.670
Chris Calhoun | XenTegra: her ensemble.
123
00:21:06.670 --> 00:21:08.250
Jirah Cox: Stuber, stupor insomnia.
124
00:21:08.550 --> 00:21:09.030
Chris Calhoun | XenTegra: Yes.
125
00:21:10.780 --> 00:21:30.050
Philip Sellers: Yeah, I mean, listen, we joke about this, but it's incredibly important. You know, the AI threat in the security space is a huge one, and so, you know, these controls and the ability to ensure and audit and show these, these are a huge deal.
126
00:21:30.050 --> 00:21:46.210
Philip Sellers: And, you know, I know that there are a lot of teams and a lot of people, shout out to everyone on the engineering and operations teams who have made this happen, because it's not an easy thing. And, I know they put a lot of hours and a lot of work into this.
127
00:21:46.570 --> 00:21:53.960
Philip Sellers: So, definitely kudos to the team for making it happen. There are a lot of…
128
00:21:54.030 --> 00:22:05.970
Philip Sellers: companies that can't exist without SOC 2 Type 2. And, you know, it's becoming increasingly evident that insurers want to see evidence of
129
00:22:06.010 --> 00:22:25.119
Philip Sellers: this type of compliance, a lot of different regulations being adopted within companies to try and mitigate the risk of ransomware and losses. So, yeah, this is important for all of us to think of, even if it does help us sleep at night.
130
00:22:25.120 --> 00:22:32.390
Philip Sellers: Actually, that might be the whole point, is to help us all sleep at night. So, yeah, nail on the head, right?
131
00:22:33.850 --> 00:22:34.669
Jirah Cox: There you go.
132
00:22:35.310 --> 00:22:52.339
Philip Sellers: Well, you know, it's, it's good news. Like I said, Microsoft Ignite last week, was a great event. I heard nothing but great reports of all sorts of news from the field. We've got our Nutanix Roundup here, and
133
00:22:52.340 --> 00:22:58.140
Philip Sellers: It's been, fun just sharing time, with Jaira and Chris today to kind of talk about it.
134
00:22:58.590 --> 00:23:04.819
Philip Sellers: I'd be remiss to say a huge thank you to Jaira for spending time with us.
135
00:23:04.930 --> 00:23:13.520
Philip Sellers: And investing so much time over the last several years predates me on this podcast. He was a founding member of Nutanix Weekly.
136
00:23:13.540 --> 00:23:25.759
Philip Sellers: And Gyro's gonna be moving on from Nutanix to his next adventure, and I just want to say thank you on behalf of everyone at XenTegra for your support, and for spending time with us.
137
00:23:25.850 --> 00:23:33.890
Philip Sellers: helping everyone that listens learn as well. I know that's a huge part of it for you, so, I just really want to say thank you.
138
00:23:34.420 --> 00:23:53.689
Jirah Cox: Well, I'll turn right back around and say, Phil, Chris, thanks to you guys, thanks for doing it with me. It's been a pleasure and a delight and a genuine hoot all throughout. Hope we've made, you know, it's only with our powers combined that we can make summarizing technical blog posts actually entertaining, and enjoyable.
139
00:23:54.530 --> 00:23:55.060
Philip Sellers: Well…
140
00:23:55.060 --> 00:23:55.740
Chris Calhoun | XenTegra: Nearly.
141
00:23:56.560 --> 00:23:59.449
Philip Sellers: I appreciate you so much. Good luck.
142
00:23:59.520 --> 00:24:17.660
Philip Sellers: We're gonna continue working together, and that's the best part. So, don't be a stranger, but thank you again. And thank you, everyone, for listening. We appreciate it. Until we catch you on the next episode, I want to say, we're coming up to holidays. I hope you have
143
00:24:17.660 --> 00:24:30.380
Philip Sellers: Happy Holidays, and if there's ever anything we can do, please do reach out. Info at centagra.com, that'll get you connected to someone, and we'd love to help you anywhere you're at.
144
00:24:30.530 --> 00:24:34.550
Philip Sellers: On behalf of Jirah, Chris, and myself, Have a great day.