Nutanix Weekly: High performance Nutanix Unified Storage powers VDI

Deploying a VDI environment for a globally distributed workforce, BYOD, hot desk environments and call centers is complex and is hard to manage. However, the storage that supports VDI to run VMs and unstructured user profile data need not be.

Exponential growth of unstructured data is putting a tremendous strain on the legacy three-tier architecture of VDI environments. Whether it is a single user VDI or a multi-user remote desktop service, deteriorating VDI performance, complexity in managing storage, protecting user data against cyberthreats and ransomware are key challenges. This is especially true with a growing remote workforce and user data.

Blog post: https://www.nutanix.com/blog/unified-data-services-platform-simplifies-vdi

Host: Phil Sellers
Co-Host: Harvey Green
Co-Host: Jirah Cox
Co-Host: Ben Rogers

Transcript

WEBVTT

1
00:00:02.850 --> 00:00:13.869
Philip Sellers: Hello and welcome to another Nutanix Weekly Podcast from XenTegra this is your host Phil Sellers. This is episode number 82,

2
00:00:13.910 --> 00:00:20.789
Philip Sellers: happy to have you joining us again today, and I'm happy to have a a nice panel of

3
00:00:21.200 --> 00:00:27.529
Philip Sellers: folks to contribute today. First up our illustrious leader of XenTegra-GOV.

4
00:00:27.570 --> 00:00:30.549
Philip Sellers: Mr. Harvey Green.  Harvey, how are you doing today?

5
00:00:30.640 --> 00:00:46.549
Philip Sellers: I am doing pretty well.

6
00:00:46.770 --> 00:00:52.689
Philip Sellers: Harvey's out working with all of our public sector. Customers.

7
00:00:52.910 --> 00:00:57.469
Philip Sellers: What's what's going on in that world that we should know about Harden.

8
00:00:58.890 --> 00:01:06.490
Harvey Green III:  Gosh, that's that's a lot

9
00:01:06.940 --> 00:01:14.429
Harvey Green III: that's that's a big box. I told you I comp comp compartmentalize. Well, that that is the humongous box.

10
00:01:14.950 --> 00:01:21.480
Harvey Green III: I don't. The I guess the biggest thing to to drill all the way down is just staying secure.

11
00:01:21.790 --> 00:01:27.199
Harvey Green III: Yeah, that's that's probably the one that we have the con. The conversations around most.

12
00:01:27.350 --> 00:01:46.779
Philip Sellers: You know, one of the pathways to that that we've been talking with several customers about is automation things like Newtonics calm. But other platforms as well, you know, taking the human factor out of it that that's one way of of making things more secure and repeatable.

13
00:01:46.910 --> 00:01:48.030
Philip Sellers: Yes.

14
00:01:49.590 --> 00:01:50.480
Harvey Green III: yes.

15
00:01:50.810 --> 00:01:58.769
Harvey Green III: agreed it's it's the whole put 2 keys in and turn them opposite ways at the same time.

16
00:01:58.790 --> 00:02:15.219
Harvey Green III: And then stuff happens. That's it. Multi multi factor controls right? So join the day with Gyra Cox jyra the resident expert office of the CTO at Newton's. How are you doing today.

17
00:02:16.020 --> 00:02:23.439
Jirah Cox: man doing? Okay? Been a while since we recorded? Cause I think we're all pretty pretty are busy lately.

18
00:02:23.490 --> 00:02:31.109
Jirah Cox: Lots of good customer meetings, lots of good partner meetings, lots of good problems to go there and solve.

19
00:02:31.420 --> 00:02:46.490
Philip Sellers: I was. Gonna say, are we playing? We're in the world, is Jira Cox today? That that seems to be the the game we're playing every time we we catch up here lately. I know you're spending a lot of time on the road meeting with customers

20
00:02:46.560 --> 00:02:49.339
Philip Sellers: having those conversations face to face these days.

21
00:02:49.880 --> 00:03:14.480
Jirah Cox: It's it's something I definitely enjoy doing. Yeah, for sure. Seeing folks kind of every week with. You know. Honestly, some recurrence of questions. Everybody's got some special meaning to the environment. But a lot of folks probably are like, you know, hey, who, you know? Okay, are people leaning in all in on. And you can actually run my business. And the answer is totally yes, and prove it to you. 25,000 ways.

22
00:03:14.620 --> 00:03:20.100
Philip Sellers: Yeah, II know those conversations are happening in spades. They're they're making up.

23
00:03:20.160 --> 00:03:30.570
Philip Sellers: probably half of the conversations we're having right now. At least that I'm having. So yeah, I mean it. It's fun to talk about what's possible with the platform

24
00:03:31.510 --> 00:03:34.740
Jirah Cox: cause. Usually, I mean. this might

25
00:03:35.330 --> 00:03:44.069
Jirah Cox: somewhat t of our our talk today. It's so much fun to talk about like, hey, look! Yes, of course you can transform from X to Y, from from A to B, of course, and you know

26
00:03:44.130 --> 00:03:49.980
Jirah Cox: nothing is super easy. Lots of things are doable. It's all about. Let's find the path of most efficiency for you.

27
00:03:50.050 --> 00:04:06.330
Jirah Cox: But honestly, really, we all win more when we also get something before that we need when we get something along the way that you didn't have before. Right? Like, let's also increase your automation coverage or your self service or you know, move to a lower cost per gigabyte delivery or

28
00:04:06.470 --> 00:04:21.990
Jirah Cox: you know. Let's go stock that storefront with more high value offerings back to the business or better cost governance or rapid deployment, or something that that was on the nice to have lists. Right? So we're not just not just answering the mail, taking care of business, but also like actually helping drive drive transformation.

29
00:04:22.430 --> 00:04:36.560
Philip Sellers: Yeah. And a big part of that is is moving the the needle forward right? Trying to get better business results. And that brings us to Ben Rogers, our man on the street.

30
00:04:36.870 --> 00:04:43.799
Philip Sellers: he is a new tanks extraordinaire. Happy to have him on the podcast Ben, how are you doing today?

31
00:04:44.040 --> 00:05:03.609
Ben Rogers: I'm doing well, everybody thank you for having me back on. I'm looking forward to the day's content. And man, I can say it's a busy, good time to be at Newton's. I think 2024 in 2,025 are gonna be pretty bullish years for us. So glad to be here business as well, and always a pleasure to be amongst this crowd.

32
00:05:03.620 --> 00:05:20.870
Philip Sellers: Yeah, we we enjoy having you both and we. We thank you for investing back into, you know the lives of all of our listeners. But you know, firstly, into Harvey and myself, I mean, we we enjoy these conversations a lot when we get to have them with you guys.

33
00:05:21.090 --> 00:05:37.809
Philip Sellers: Yeah, as Jira said, we we've got a great conversation today. Talking about unified storage one of the many capabilities Jira did a great job of team up. All of the great business outcomes you can get with the new tanks platform

34
00:05:37.910 --> 00:05:43.690
Philip Sellers: but today's blog post is high performance. New tenix, unified storage powers. Vdi.

35
00:05:43.890 --> 00:05:53.640
Philip Sellers: And so this is one that's near and dear to our heart here. It's integral, because this is this is how we've paid the bills for a very long time. So

36
00:05:54.080 --> 00:05:59.559
Philip Sellers: let me get this shared out here for the people watching on Youtube. And

37
00:05:59.700 --> 00:06:26.590
Philip Sellers: we'll get started and dig right in so high performance. New tanks, unified storage. Jirah brought us the blog post today. It was posted by Shawn Donahue, a senior solutions marketing manager, and Santosh is Servole another senior brought up marketing manager for unified storage. So wanna shout out to Shawn and Santosh, and thanks for posting this.

38
00:06:26.610 --> 00:06:30.979
Philip Sellers: Jayra! Why, why this specific topic for today?

39
00:06:32.900 --> 00:06:35.900
Jirah Cox: The I love the way it highlights

40
00:06:36.500 --> 00:06:47.969
Jirah Cox: the really, the platform, right? Like when I talk, when I talk to customers about the cloud platform right? And for some folks that's new positioning right? Understanding that tanx is a cloud platform.

41
00:06:47.970 --> 00:07:05.270
Jirah Cox: I'm like, well, if you think about it. Right? Cloud, do like 4 things. So not to be super super reductive. Here, right? Run my vms on my run, my containers for my data and hopefully offers some sort of a boutique, you know, higher value service like a database as a service or automation pipelines.

42
00:07:05.270 --> 00:07:19.969
Jirah Cox: Fancy your functionality like that. And so this really combines kind of 2 of those things right? Like, run my Vms store my data, make that all easier on me as the Admin as the platform owner. Then it would be if I did those things separately.

43
00:07:21.180 --> 00:07:31.839
Philip Sellers: Yeah, absolutely. II mean this. This is. you know, as I tell people what we do. At XenTegra, I mean with Euc still kind of forming the core of

44
00:07:32.000 --> 00:07:40.910
Philip Sellers: what we do. This is what makes new tanics a really powerful platform for us is that you don't have to go multiple places. You don't need multiple

45
00:07:42.640 --> 00:07:49.540
Philip Sellers: different solutions. You you can manage it off in the same place and get all of the used cases that you need cause.

46
00:07:49.730 --> 00:08:06.910
Philip Sellers: you know, for us with the Vdi use case, and we'll dig into the blog post more. II don't want to give it all away. We need some of these additional platform services to make things go. So Harvey. As you think about this, II think back

47
00:08:07.000 --> 00:08:09.510
Philip Sellers: to our first discussions. When

48
00:08:09.570 --> 00:08:33.570
Philip Sellers: I was a baby solutions architect here at XenTegra I was just starting. Harvey was mentoring me, getting me started, and he he started to explain this whole platform thing. And do you remember kind of how you you positioned it to me. Maybe I probably need some prompting, but II probably would have told you

49
00:08:33.780 --> 00:08:36.559
Harvey Green III: that this is

50
00:08:36.990 --> 00:08:50.470
Harvey Green III: something more along the lines of a citrix or vmware overall, and that you can use it anywhere. It gives you the ability

51
00:08:50.530 --> 00:09:01.219
Harvey Green III: to be able to use it on Prem in the cloud, back and forth in and out just any which way you need to flip this thing, you can do it.

52
00:09:01.620 --> 00:09:07.679
Harvey Green III: That's I'm I'm trying to think of the timeframe that this was happening. That's probably what I would have told you.

53
00:09:07.850 --> 00:09:16.749
Philip Sellers: Yeah, if if I remember right. I think the word that sticks out to me was how powerful it was. That

54
00:09:16.830 --> 00:09:28.319
Philip Sellers: you know specifically for what we were trying to accomplish in Vdi, that that it could meet all of the challenges that we needed, and more, there was so much more that it could do.

55
00:09:28.540 --> 00:09:36.020
Philip Sellers: You know little personal story. I think within the first 2 weeks I was here at Zintagra. I spent a day.

56
00:09:36.680 --> 00:09:42.519
Philip Sellers: It the Durham headquarters of Newtownics, and started to learn about the platform.

57
00:09:42.530 --> 00:10:05.199
Philip Sellers: and that's the day that that I kinda unlocked for me that yeah, this isn't hyper converged. This is a platform, and there's so much more more value to be had when we think about it that way. If simplification is a big part of that right? I mean, Ben is, as you think, about simplification. And the Newtonics platform. I mean, what?

58
00:10:05.530 --> 00:10:12.310
Philip Sellers: What would you tell someone approaching this for the first time, who maybe just knows you as a hyper converse platform?

59
00:10:13.090 --> 00:10:33.909
Ben Rogers: So one, I would say. II think one of the things I'm starting to see come out of the company is beyond the Hypervisor, you know a lot of talks about our Hypervisor, the Aos platform. But I think now people are starting to see that it's beyond the Hypervisor, and we have many more services that we can deliver specifically, you know, Nus, our unified storage.

60
00:10:33.960 --> 00:11:03.699
Ben Rogers: I look at this particular content here and this. This comes close to what I was dealing with at Cnsa man, user profiles. How do I get those user profiles distributed across the wide area network? You know, how do I make the Vdi experience not feel like a Vdi experience. Harvey worked with me a lot at Cns, saying one of the things we would coin is, I want it in your face. I want you to hit that icon, and the next thing that you should see is the application in your face.

61
00:11:03.700 --> 00:11:25.949
Ben Rogers: and the only way to achieve that was men managing the Citrix profiles and making the Citrix profiles available, so that they were easily ready and able to be configured for the users. And so, you know, I mean, part of that is, how do you deal with that in the unstructured data? It's funny not to detract away from the content. But as we were talking I was slacking with our nus

62
00:11:25.950 --> 00:11:37.269
Ben Rogers: experts in the background. And, man, there's some staggering statistics when it comes to just unstructured data. So I'll throw one of them out there.

63
00:11:37.850 --> 00:11:43.309
Ben Rogers: 50 of the unstructured data is created at the edge of the network.

64
00:11:43.630 --> 00:12:03.010
Ben Rogers: That's kind of staggering when you think about the distribution of your workforce and how Vdi is being implemented and how those users are consuming Vdi and what they're using that environment for 50% of unstructured data on the edge. That's pretty. That's pretty incredible. When you think about that from a workforce day to day.

65
00:12:03.820 --> 00:12:19.239
Philip Sellers: Yeah. And there's a link in the blog post here to a report from Statistica and and it's a staggering number. The amount of data created, captured, copied, or consumed globally, is forecast

66
00:12:19.280 --> 00:12:24.880
Philip Sellers: to be 64.2 zettabytes. And that was 4 years ago.

67
00:12:24.910 --> 00:12:33.689
Philip Sellers: That was 2020. So, you know, their forecast was saying, we're supposed to be up to about 180 zettabytes

68
00:12:33.840 --> 00:12:38.269
Philip Sellers: per year. That's a staggering amount of data.

69
00:12:38.650 --> 00:12:41.849
Philip Sellers: Jira, as as you think about that

70
00:12:42.000 --> 00:12:55.839
Philip Sellers: explosion of growth. I mean, you know, how how do we? 3 tier? II don't think, can combat that. I mean scale and the ability to move that data around is is really tough, like.

71
00:12:56.150 --> 00:13:02.649
Philip Sellers: what would you say for for people trying to handle that kind of growth in their unstructured?

72
00:13:03.160 --> 00:13:07.790
Jirah Cox: I think I think part of it is scale. Part of it is

73
00:13:07.960 --> 00:13:18.130
Jirah Cox: all, almost the sort of natural momentum of data ownership. Right? Here's a here's a very terrible stupid analogy. In the last week or 2

74
00:13:18.350 --> 00:13:20.379
Jirah Cox: while power under my house

75
00:13:20.470 --> 00:13:27.509
Jirah Cox: that left my personal gaming PC. Sideways and wouldn't unable to boot right, and I worked out with it for like

76
00:13:27.730 --> 00:13:40.220
Jirah Cox: an hour, 2 h, some time I will. I want to divulge publicly longer than I want to care to admit we couldn't fix it right. I couldn't hold my tongue right to get windows booting correctly on my old windows. 10 installation.

77
00:13:40.300 --> 00:13:47.030
Jirah Cox: and I just said, probably you know, heck with it right. I've got a that one out. Put the new one in install Windows 11.

78
00:13:47.130 --> 00:14:00.190
Jirah Cox: And have I worked well? One yet. No, haven't migrated, migrated my date off of it. No, it it's the cost value to me as the data owner there to confirm. I can throw away the old stuff

79
00:14:00.470 --> 00:14:15.690
Jirah Cox: is is higher than just holding onto it. Right? I'll just. I'll just keep on holding onto it and never finish migrating it. Never finish knowing what's on there. But if I ever need something there, II know I can go back to it right? So it's easier. Just say yes, and get and hold on to it forever.

80
00:14:16.250 --> 00:14:31.139
Jirah Cox: And we see that with our with our customers, too. Right? Which is, you know, of course, teeing up the segway here, right of how? How far our platform makes it easy to understand. Who owns what, how old is is it being used? Is it being accessed right? Because that's the only way to your point fell around.

81
00:14:31.250 --> 00:14:37.370
Jirah Cox: How do we have a hope of of bringing order to the chaos? Right of data sprawl.

82
00:14:38.020 --> 00:14:40.040
Philip Sellers: That's a hundred percent. It

83
00:14:40.080 --> 00:15:04.630
Philip Sellers: you know. I mean, I I've got 2 thoughts, one, you know, as you're talking. I I'm thinking, digital pack rats. I've met them. I've been. I've been one of them from time to time. You know II was rebuilding a Naz over the weekend and didn't think about backing up before I pulled some drives and wipe them. And

84
00:15:05.040 --> 00:15:06.099
Philip Sellers: you know

85
00:15:06.380 --> 00:15:14.680
Philip Sellers: I haven't touched that data in years, and I'm not really gonna miss it. So I cried for a minute and then I moved on. You know, it's

86
00:15:14.990 --> 00:15:27.060
Philip Sellers: I fall into that same category like we keep data online for far longer than it may be useful, or, you know, according to compliance, maybe

87
00:15:27.280 --> 00:15:40.519
Philip Sellers: legally longer longer than anyone would want it to stick around. Yeah. Yeah, that that's that's an interesting perspective. So so yeah, I mean, we, we're talking about

88
00:15:40.720 --> 00:15:47.220
Philip Sellers: specifically, Vdi here, but unstructured data problems a as a whole, you know.

89
00:15:48.000 --> 00:15:53.550
Philip Sellers: they come from the fact that we've got silo different platforms we've got.

90
00:15:53.870 --> 00:16:15.300
Philip Sellers: you know, an inability to see what's going on in those. And because they're in different file structures and different ways of being stored. Not really a way to get at that. So Jarrah, why don't you lead us through. I think it's the fourth paragraph. We're starting to talk about some data services that are important for us as we try to handle

91
00:16:15.520 --> 00:16:18.329
Philip Sellers:  unstructured data.

92
00:16:19.120 --> 00:16:29.869
Jirah Cox: Yeah, of course. And of course, to get us to go center, too. Right? Like, we're talking about unified storage in the context of Vdi, just because that's the easiest, often one of the most easiest workloads to

93
00:16:29.880 --> 00:16:34.500
Jirah Cox: roll onto a new platform and get a lot of value out of it. Right?

94
00:16:34.570 --> 00:16:54.679
Jirah Cox: you know. Bring those profiles over across, bring those, maybe departmental shares over. But then get those those services like you're talking about feel like instantly available right? Analytics right to like you. And I just talked about like analytics is the is the spotlight to shine on pack rat style problems. Right? If something could tell me.

95
00:16:54.680 --> 00:17:06.349
Jirah Cox: Hey? Here's your old gaming. PC, SSD, here's the 3 files you're gonna care about and if nothing else you touch lately would matter to you. Go copy those off, and you're done, man. That would be a huge, hugely valuable service to me.

96
00:17:07.160 --> 00:17:12.500
Jirah Cox: Ransomware, of course, is one of our truly unique differentiators. Right? Is like.

97
00:17:12.619 --> 00:17:27.159
Jirah Cox: not just the value of the platform. And like, yes, it can host your data shares, of course, but it can also host your data shares and tell you when they're being attacked and block the attackers and roll back to a healthy state and actually go on the offense against

98
00:17:27.160 --> 00:17:43.539
Jirah Cox: I guess bad guys that want to get at your data right? Which those are terrifying headlines right? We see them all the time. There's there's some literally in the news right now, as we record this that we want our customers to not be a part of right. So more layers of defense is better than fewer, for sure

99
00:17:43.840 --> 00:17:47.980
Jirah Cox: life cycle management, wisely called out here in the article about.

100
00:17:48.240 --> 00:18:02.219
Jirah Cox: and that goes back to how I how I opened about simplicity, right? Like patching all of this stuff, and owning as the platform owner should be, should get easier on the overtime. Not hardware overtime, right? Or, as you use more parts of the mechanics platform

101
00:18:02.280 --> 00:18:09.480
Jirah Cox: that should get more streamlined. Not not be a linear consumption of your time as an admin right?

102
00:18:10.020 --> 00:18:27.059
Jirah Cox: And then, of course, data protection, right? Because because the whole point is this is data that is important to the business right? Therefore I have to be able to have burgeoning over it. Know who can get to it. I have a strong kind of our backstop controls, but also be able to say, yes, I can solve a problem right? Yes, I can go back to

103
00:18:27.060 --> 00:18:40.269
Jirah Cox: 48 h ago, 48 months ago, maybe depending on the data set. So having all those kind of interoperabilities, is key. Right like is A is a absolutely must deliver to our customers style of outcome

104
00:18:41.130 --> 00:18:43.849
Philip Sellers: absolutely. And, you know.

105
00:18:44.200 --> 00:18:54.280
Philip Sellers: specific to the Vdi the ability to scale. You know our, our, some of our largest deployments are supporting 50,000 seats. So

106
00:18:54.350 --> 00:19:02.839
Philip Sellers: one of the other things to highlight. Here is the fact that we do have that ability to scale here.

107
00:19:03.830 --> 00:19:18.940
Philip Sellers: It's, you know, scaling hard. You'll throw it to you. Let let's talk through the scaling a little bit. I mean, you know, we've we've got the ability to scale at the core of Newtonics. But we've also got the ability to scale at at in us. Tell us a little more.

108
00:19:19.730 --> 00:19:35.769
Harvey Green III: Yeah. I mean. Ultimately, you've got the ability to to. Just II just fashion, is adding, Lego blocks. My my son wants a bigger Lego tower. He goes and gets more Legos, and just stacks them up and gets higher and higher

109
00:19:35.800 --> 00:19:48.080
Harvey Green III: until it falls over, or he comes to try to chase me with it. Maybe that last part's not a good analogy, but

110
00:19:48.620 --> 00:19:59.910
Harvey Green III: but you you've got the ability again, you know, as we kind of talked about, and I can. You know I was talking about how you can just make this thing bend over backwards for you.

111
00:20:00.440 --> 00:20:06.800
Harvey Green III: you're just adding, and it's already set up. The Platform's already set up to take that

112
00:20:06.860 --> 00:20:26.329
Harvey Green III: you can add different size nodes, you can, you know, go storage heavy. You can do whatever it is that you need to do to give yourself the capacity and the performance that you need and and the platform still is, is already built in. Please give me more to do.

113
00:20:27.620 --> 00:20:35.889
Philip Sellers: And and then the same breath, you've got that life cycle management built in, you know, it's important to patch. It's important to upgrade.

114
00:20:36.160 --> 00:20:41.619
Philip Sellers: But all of this was thought out to be highly available, scalable, highly performant

115
00:20:41.980 --> 00:20:53.010
Philip Sellers: with the life cycle. As part of that. It wasn't an afterthought. It wasn't a bolt on. It's not another product. And so back to that message of simple.

116
00:20:53.140 --> 00:21:00.039
Philip Sellers: it's it's all integrated. And so it's a simple operation to to be able to do those life cycle.

117
00:21:00.460 --> 00:21:07.279
Philip Sellers: There's more built-in, I mean, Ben, I'll throw it to you. I mean data protections right there, built in as well.

118
00:21:07.380 --> 00:21:21.039
Ben Rogers: So what I what I think's really, you know, awesome about all of this is, if you've ever seen our customer journey, you know, customers can start out with a small cluster, and then, as they grow, they add those the cluster grows.

119
00:21:21.040 --> 00:21:45.710
Ben Rogers: This is the same type of environment, and it even goes into those original clusters that you have. So one thing you talked about simplicity, I want to talk about flexibility. You can have one cluster that can deliver all these services, for you can do the Hv. For the Hypervisor. It could do the files if you can do the container, and it's all managed under one management platform. So simple interface gives you all the services that you need and the flexibility

120
00:21:45.710 --> 00:22:15.100
Ben Rogers: to go as you need, and more that's important to our customers is our customers as their business needs grows, the technology behind that can grow as well. So that's that's kind of what I think about what I think about from a technology and a delivery platform is, it's just as you're saying, Philip. It's built into the fabric of the platform. But that's because, you know, man, that's the way it's been designed, and that's to to make it where it's consumable. At a customer level. You know, we realize that

121
00:22:15.250 --> 00:22:39.660
Ben Rogers: customers are gonna need to turn on these features in phases and we don't wanna always have to ask them to buy more when they need to do it now when they need to grow, and they need to expand, of course, add notes in the cloud. You know, you're just adding more capacity. And so that's really how, in my opinion. It's been thought out and been designed. And may I see customers taking great

122
00:22:39.660 --> 00:22:55.740
Ben Rogers: advantage of it? And we're having to educate customers on that. They don't. I don't think a lot of customers realize when they they buy new tanks for a specific reason, and then over time they realize that. Oh, I've bought an engine that's capable of doing more than what my original purpose was.

123
00:22:55.750 --> 00:23:08.580
Philip Sellers: It? It's a great point, you know, as Jarrah said earlier, Vdi is a great first use case, and it's often the gateway into more. Once they understand the platform once they understand and see the power.

124
00:23:08.900 --> 00:23:13.640
Philip Sellers: Yeah, I think that's a great way of teeing us out for the benefits.

125
00:23:13.930 --> 00:23:28.729
Philip Sellers: There's a graphic right in the middle of the blog post here. Of course, the blog post is linked in the notes for the the podcast here. But you know, simple, scalable and enterprise class. That's what the graphic kind of points out

126
00:23:28.910 --> 00:23:39.290
Philip Sellers: and then we dig into those key benefits, you know. Then you you hit simplicity on the head. That is absolutely one of the huge huge key benefits.

127
00:23:39.540 --> 00:23:43.850
We we talked about performance, Harvey, you you brought this one up?

128
00:23:44.260 --> 00:23:51.960
Philip Sellers:  one of the things we didn't talk about was the data locality piece of it. You know that

129
00:23:52.160 --> 00:24:08.220
Philip Sellers: for us on a Vdi standpoint is really key to great performance. For someone that's not understanding data locality. Harvey. How would you explain that?

130
00:24:08.360 --> 00:24:16.829
Harvey Green III: I knew you were gonna do that. There's an inside joke. And I love this, and now I had to take you up. Man. Oh, you gotta tell us

131
00:24:18.540 --> 00:24:34.309
Harvey Green III: II have. I have this little story. I'll try to keep it short, but I do it a couple of different ways. Phil knows that I like to eat, so II kind of gravitate towards food analogies, but I'll give you this one. I'll use you been since I haven't done this with you before.

132
00:24:34.690 --> 00:24:42.779
Harvey Green III: As you as you thinking about sitting at home in your living room. you get hungry, whereas the fastest place for you to get something to eat.

133
00:24:43.950 --> 00:24:48.820
Harvey Green III: Our refrigerator. Yeah. Your kitchen is that your favorite place to eat.

134
00:24:49.620 --> 00:24:58.209
Harvey Green III: Yeah, only any given day, maybe. Exactly. So. How far away is your favorite place to eat?

135
00:25:00.570 --> 00:25:01.960
Ben Rogers: About 30 min

136
00:25:02.190 --> 00:25:09.490
Harvey Green III: about 30 min. Alright, we're gonna do our best to make that 30 min trip as fast as it is to your refrigerator. You ready.

137
00:25:10.710 --> 00:25:13.020
Harvey Green III: I'm all ears movement. Aye.

138
00:25:13.090 --> 00:25:19.870
Harvey Green III:  Let's see if we get you a race car upfront when I do it.

139
00:25:21.240 --> 00:25:22.130
Ben Rogers: No.

140
00:25:22.400 --> 00:25:25.770
Harvey Green III: how about if I

141
00:25:26.420 --> 00:25:33.360
Harvey Green III: I don't know? Put an driver in the driver's seat, and all you gotta do is get in and let him take it.

142
00:25:34.070 --> 00:25:36.149
Ben Rogers: Dude! You gotta bring the cook to me

143
00:25:36.420 --> 00:25:42.960
Harvey Green III: police escort, and we clear the streets still, not gonna do.

144
00:25:42.980 --> 00:25:50.350
Harvey Green III: So you know, as as we go through that, and I know it's a shortened version. But

145
00:25:50.440 --> 00:25:58.269
Harvey Green III: you think about all the things that you can do to try to speed the transport of data. And 3 tier architecture.

146
00:25:58.380 --> 00:26:00.960
Harvey Green III: you can clear the streets

147
00:26:01.210 --> 00:26:04.589
Harvey Green III: by using data prioritization.

148
00:26:04.620 --> 00:26:10.730
Harvey Green III: you can have your police escort. Again, more data prioritization and actually

149
00:26:10.780 --> 00:26:15.500
Harvey Green III: using quality of service stuff. You can

150
00:26:15.620 --> 00:26:28.109
Harvey Green III: get your race car outfront, you know. 10 gig, 40 gig, 100 gig connections. Right? You do all of these things, spend all the money on all of these things, no matter how much you spend, it won't be faster

151
00:26:28.240 --> 00:26:34.920
Harvey Green III: and having it right there on the same bus. So that.

152
00:26:34.970 --> 00:26:42.620
Jirah Cox: that's that's a condensed version. But you can kind of see what I'm getting at there.

153
00:26:42.760 --> 00:26:55.839
Philip Sellers: Never faster than food to your kitchen. But that's what's interesting about that. Harvey is like, I have a lot of customers go. How can you all do all these things? How can you to be a platform?

154
00:26:55.840 --> 00:27:20.240
Ben Rogers: And you have to remind them of where we started from. We started with data management. That's what that's what makes it easy for us to have a files, a database engine, a backup engine, I mean, because we're managing the data at the core. And so you know, that's really what differentiates us in our platform from the competitive market. And and we have to talk to customers about. That

155
00:27:20.240 --> 00:27:45.099
Ben Rogers: is that if the core is about managing the zeros and ones, and then from that we can bubble up all these marvelous services like Nus. And that's what makes it possible is because at the end we're managing all that data in the background for you. And so you're absolutely right, Harvey. So to add on to the data locality because we are managing the zeros and ones. And what we originated doing and still do very well.

156
00:27:45.470 --> 00:28:11.280
Ben Rogers: we can make sure that data is where you needed. We can make sure that cook is in your kitchen cooking that steak so that it comes off the grill onto your plate at the temperature. It was on the grill. So a great analogy, but also want to remind the crowd that listens to this. That's really the nut of what new tanks is that ability to manage those data and produce these services that go on top of that? Yeah.

157
00:28:11.510 --> 00:28:27.500
Philip Sellers: Yeah. And and just to wrap it up. I'm sure most of the folks listening understand the data locality. But from a new tanks perspective, if a virtual machine's running on a note. It's gonna bring all of the data locally so that it's just as fast as possible. It's gonna put that food in the kitchen

158
00:28:27.530 --> 00:28:37.159
Philip Sellers: and that that's really the the idea behind performance. And why Vdi has always been such a great workload on the Newtonics platform.

159
00:28:37.520 --> 00:28:42.629
Philip Sellers: But efficiencies there, too, you know, when we talk about unstructured

160
00:28:43.090 --> 00:28:57.789
Philip Sellers: our unified storage, unstructured data on new tanics, getting up and going scaling up and scaling out as we talked about with Ben just a few minutes ago is really easy and that adds to efficiency.

161
00:28:58.120 --> 00:29:08.639
Philip Sellers: There's a quoted statistic here in the blog post. That file storage is 82% faster. And object storage is 75% faster.

162
00:29:08.920 --> 00:29:12.609
Philip Sellers: And that's the deployment time compared to traditional storage.

163
00:29:13.040 --> 00:29:14.810
Why is that, Jyra.

164
00:29:16.660 --> 00:29:22.930
Jirah Cox: I like to tell customers that I meet with right, that we try to do our very best to never

165
00:29:22.940 --> 00:29:25.929
Jirah Cox: send a human to do a robot's job.

166
00:29:26.030 --> 00:29:49.040
Jirah Cox: Ask you the bare minimum viable questions, right? Like, what Ips can we use on your network? And you know, do you do we need to ask you questions about me. Maybe resiliency or capacity or protocols great. Just give us that detail and we'll go deploy it for you right? We try, and it will make you things a. You go do this on your tanics. It's a give us the information. Go, do this for you. Proposition.

167
00:29:49.390 --> 00:29:56.170
Philip Sellers: Yeah, very heavily orchestrate. I love that. Never send a human to do what a robot can do for you.

168
00:29:56.310 --> 00:30:23.819
Philip Sellers: Harvey, you hit this one a little bit earlier. But scale flexibility needs of adding infrastructure, and that's both the physical nodes and the virtual nodes inside of a in us cluster so that ease of of adding things. But also here they're talking a little bit about

169
00:30:23.990 --> 00:30:29.040
Philip Sellers: other models to to license. You wanna hit that one.

170
00:30:30.670 --> 00:30:36.870
Harvey Green III: Yeah. So again, you've got the ability with Newtonics to just

171
00:30:37.250 --> 00:30:45.359
Harvey Green III: spread it out as you need. So again, you can do that physically right with more nodes. You can do that also.

172
00:30:45.370 --> 00:30:54.340
Harvey Green III: kind of logically, with more nodes that are more storage heavy you can use the cloud. You've got the ability to

173
00:30:54.370 --> 00:31:16.189
Harvey Green III: just do do us necessary, as I mean, as as the as your storage demands grow. As you see, you know, the the needs of the business become much bigger, much faster. We're we're at the point where we're talking multiple zettabytes of data at this point. I even have to go back and think about

174
00:31:16.190 --> 00:31:29.859
Harvey Green III: where in the factory Zeta is. So

175
00:31:30.200 --> 00:31:48.249
Harvey Green III: but you know you've you've just got the flexibility, and you've got a platform that that has this built in. And and to Ben's point earlier, you know it. It started as managing the data. We're continuing to talk about that just in a much, much bigger way. But

176
00:31:48.250 --> 00:32:03.060
Harvey Green III: if you are already doing that well and you're compensating for growth, and you're compensating for different models of being able to do it all in the same platform. You just continue to get expected results.

177
00:32:03.140 --> 00:32:23.809
Jirah Cox: Yeah, well, for scaling is like, I coach customers around like you know you can. You can get the best team in the world doing a Vdi design for you in 2,004, and maybe you find some ratio of like. I can put a hundred users per node, and that's great, so that if I have 500 users up by 5 nodes, 6 notes from plus one. And I'm done here.

178
00:32:23.880 --> 00:32:28.570
Jirah Cox: And then over time, you watch that cluster. Right? And of course, windows updates.

179
00:32:28.640 --> 00:32:29.870
Jirah Cox: Chrome.

180
00:32:29.900 --> 00:32:51.439
Jirah Cox: yeah, security agents, right? And just like, yeah, like, who knows? Like the Xbox store, like all these kind of things that will come for your your Vdi fleet if you're not managing that golden image like Super, carefully will drive your density down over time. Right? And so one other trick up our sleeve is the ability to say, we can license this cluster on a per user basis.

181
00:32:51.650 --> 00:32:57.380
Jirah Cox: So that over time, if you need more hardware to keep your sla's high for your user base.

182
00:32:57.990 --> 00:33:18.409
Jirah Cox: You can tie your licensing the same way you would with like Citrix to per user, tie your antennx for that cluster the same way to per user, so that now, scaling out from more nodes to get more horsepower, to run the same on our desktops is just a simple buy. Go by more hardware proposition and not need to revisit your actual platform licensing

183
00:33:18.620 --> 00:33:26.410
Philip Sellers: well. And and that also comes into our next point, which is business continuity. You know, using that same Vdi model

184
00:33:26.580 --> 00:33:39.759
Philip Sellers: you, you gain the benefit of having licensing for your business continuity, for your Dr. Plans. And so that that's another huge part. But that's not the only thing we're talking about from business continuity.

185
00:33:40.110 --> 00:33:51.849
Philip Sellers: We're also talking about, you know, built in storage features. So, Ben, you know, you wanna take this one. I mean in us leverages, that platform you're talking about built on a

186
00:33:51.880 --> 00:33:54.090
Philip Sellers: solid data platform.

187
00:33:54.860 --> 00:34:22.479
Ben Rogers: Yeah. And so what's what's cool here is we have recovery options at the file server level. So you know, obviously, we have recovery options at the cluster level, the Vm level. Now we're just bubbling that up to where, if you gotta have something that looks specifically at your files, I'd also like to bring 2 more items into business continuity. And, Philip, you'll you'll appreciate this. You know. We were talking about the ability to run your business, and that also includes the ability to manage your employees.

188
00:34:22.480 --> 00:34:31.309
Ben Rogers: We have a lot of customers that are managing, you know, just basic Aos HV. Today. And then they go and they turn on files.

189
00:34:31.310 --> 00:34:55.339
Ben Rogers: A lot of them have done this really stress free. They haven't had to re-engineer the It department, because again, it's a single platform. So a lot of the tools. They're used to seeing a lot of the screens they're used to seeing or just replicated over into the files area of prism. So it makes it very easy to bring it on board, and also get your customers, who are customers and employees that are used to working and

190
00:34:55.389 --> 00:35:17.910
Ben Rogers: new tanics, men bringing on files, and and there's value to that. And so, you know, I don't wanna oversee that where again, simplicity and flexibility is really the name and the game, and from a business continuity aspect, we just bring that to the table as well, man bringing services that are concentrated at the file level, so that you have visibility into that as well.

191
00:35:18.290 --> 00:35:45.170
Philip Sellers: Yeah, I mean, these 2 scale and business continuity really link together a lot. You know, the the choice of consumption models, the choice of licensing models the ability to run anywhere with that consistent operational experience. No learning curve. I mean that there, there's so many advantages to that. You you can run an Aws, you can run in your own colo. It's the same. It's managed the same

192
00:35:45.170 --> 00:35:51.040
Philip Sellers: a. A. And the built in Dr. Is.

193
00:35:51.090 --> 00:35:55.030
Philip Sellers: you know that that's a huge game changer, too, because

194
00:35:55.090 --> 00:36:15.359
Philip Sellers: you're not having to relearn another console. I know we have a lot of Dr. Conversations where we have to layer on a tool in other environments. And so it's another console life cycle to learn to learn the vernacular and how things work. I mean, the there is a huge learning curve there sometimes.

195
00:36:17.880 --> 00:36:31.550
Philip Sellers: Yeah. The the next thing the next 2 options here integrated security and ransomware protection. And then also data visibility and compliance. Both of these tie back to new tanics data lens,

196
00:36:31.600 --> 00:36:44.309
Philip Sellers: and if you haven't heard of Dave data lens. That's the build in analytics platform that goes along with in us jar, I'm gonna throw it to you. Cause I think the ransomware protection is is really key

197
00:36:46.330 --> 00:36:59.530
Jirah Cox: for sure, right like for for really all kind of all data storage in general. But all the more so, I think, for Vdi, right? Because Vdi is kind of where users live on the network. That's where you have better than even odds of

198
00:37:00.150 --> 00:37:08.759
Jirah Cox: of bad stuff getting into the network and trying to see what it can give access to. So yeah, it is by far, some of the most critical

199
00:37:09.000 --> 00:37:24.680
Jirah Cox: places to have good good security, good ransomware, monitoring good visibility in place, but also, therefore the easiest ones as well. To get all those things, check all those boxes with data lens, right? Which is our our Saas based analytics platform, that.

200
00:37:25.270 --> 00:37:30.780
Jirah Cox: That watches your your data. Your data never leaves your environment never crosses your firewall.

201
00:37:30.940 --> 00:37:53.049
Jirah Cox: but we watch the activity on it with our eye on the sky and then react to those conditions right? To tell it, you know. Hey, look, we see an attack happening. Let's go and block the source. IP block the source user, take a snapshot of the cluster and then automatically roll back to a prior snapshot as well. So the forensic preservation of what was going on, what was done.

202
00:37:53.140 --> 00:37:59.529
Jirah Cox: but also can recover back to a prior healthier point in time. Right? So the business gets back on its feet faster.

203
00:37:59.630 --> 00:38:03.940
Jirah Cox: My favorite thing to talk about on this one is that when we when we

204
00:38:04.040 --> 00:38:14.899
Jirah Cox: preview this feature at next in Chicago last year we talked about a 20 min or so period of exposure from start of attack to really end when we've recovered from it.

205
00:38:15.140 --> 00:38:33.729
Jirah Cox: When we actually ship this feature and had a third party validated, they actually clocked it at like 14 min. So even faster than than what we were promising. So like, no humans get out of bed, which is always my favorite part. Right? Is like, Let's bug. Let's bug humans less for processes that we can automate good automation, right? 2 keys to turn and all that good stuff.

206
00:38:33.850 --> 00:38:50.040
Jirah Cox: so yeah, yeah, I think it's just it's absolutely brand new. If you've been looking into tanics and files for a while, it's a it's a newish feature in the last year, but it is absolutely one of those compelling reasons to think about hosting any any flavor of data on Newtonics.

207
00:38:50.370 --> 00:38:57.879
Philip Sellers: Yeah. And and as you said, your, I am sky. Right? It's got global data visibility. It says here in the the article.

208
00:38:58.310 --> 00:39:02.170
Philip Sellers: looks at permissions, risk visualization. I mean

209
00:39:02.250 --> 00:39:05.689
Philip Sellers: all of that. And it gives you that

210
00:39:05.810 --> 00:39:06.650
Philip Sellers: that

211
00:39:06.830 --> 00:39:19.669
Philip Sellers: view that we've been missing? Where? Where is the stale data? Where is the thing? So it also plays into your tearing and the ability to make more efficient use of your your storage platform.

212
00:39:20.830 --> 00:39:26.710
Ben Rogers: So, Philip, I want, I want to add to the you know, the concept of the data visibility.

213
00:39:26.970 --> 00:39:41.959
Ben Rogers: I talk to a lot of customers that when we talk to them about unstructured data, a lot of them go. I have no idea what's out there, and I would I would love to have a tool that could you know. Espionage my network. Tell me where shares are, what are in those shares

214
00:39:41.960 --> 00:40:04.659
Ben Rogers: coming from, you know, managing it. Departments and data management that's terrifying to hear when we have, you know it, leadership. Tell us that. So this tool alone, from the 4 things we mentioned. The data visibility is what really gets people to. You can go out there and find my data and tell me where it's at. And that's been huge win for us, as far as

215
00:40:04.660 --> 00:40:07.820
you know, talking to customers about the services of data lens.

216
00:40:08.170 --> 00:40:20.009
Philip Sellers: Yeah, we we talked we did a webinar a week or so ago around Microsoft co-pilot and co-pilot, like the universal search that came before it.

217
00:40:20.180 --> 00:40:30.649
Philip Sellers: You know, it uses that access from a user to surface what they have access to to the data that they have access to, and then draw insights from it. And so

218
00:40:30.740 --> 00:40:39.770
Philip Sellers: a lot of times. There's security through obscurity. They don't know that they have access, you know. They may have access to a share where

219
00:40:40.000 --> 00:40:56.269
Philip Sellers: all of the the users in the company have read, write, access, which is not great. That's pretty horrible. But you know, when we turned on universal search and sharepoint years ago it surface that problem in in an organization I was working with. So

220
00:40:56.420 --> 00:41:12.129
Philip Sellers: you know, it's it's one of those things where locking it down and having appropriate permissions can't be understated. Now that we're getting assistive technology, you know, to Jira's point earlier, why send a human to do what a robot can do

221
00:41:12.240 --> 00:41:26.219
Philip Sellers: with AI and generative. You know. AI, particularly. We're starting to move into that territory with those permissions really critical and security through obscurity doesn't really work anymore.

222
00:41:28.790 --> 00:41:50.329
Philip Sellers: Well, back up to the ransomware protection for just a second we did another podcast around about Igl a week or so ago. And you know a lot of times when we have a ransomware incident sometimes the Vdi environment is the one that

223
00:41:50.400 --> 00:42:13.610
Philip Sellers: isn't affected. It's the one place where we've got golden masters that were sealed. And so we can spend those back up with a level of confidence that they're unaffected. So your point around user data in those shares, we wanna make sure it's equally unaffected. So data lens is a great insurance policy around all of that data. Because

224
00:42:13.880 --> 00:42:23.589
Philip Sellers: in in practice we have seen a reliance on Vdi during and in the immediate aftermath of a ransomware attack.

225
00:42:24.140 --> 00:42:29.660
Jirah Cox: It's a great point. I hadn't thought about that. I guess. I guess you could. You could make an argument right? That a well

226
00:42:29.720 --> 00:42:33.400
Jirah Cox: architected Vd environment for most customers is sort of the most.

227
00:42:33.950 --> 00:42:42.880
Jirah Cox: It's not fully stateless, but it has compartmented compartmentalize statefulness. And it's actually maybe close to the most declarative part

228
00:42:42.960 --> 00:42:50.659
Jirah Cox: of the infrastructure. Right? So like resinning. It is, is A is a lighter lift than a lot of other parts of the data center.

229
00:42:50.870 --> 00:43:09.170
Philip Sellers: Yeah, especially non persistent. I mean that that really is kind of at the heart of it. Right, you reboot, and you get a pristine image. It. It's kind of beautiful in that way. So I know we've had some wins on on behalf of our customers, you know, using that

230
00:43:13.320 --> 00:43:25.790
Philip Sellers: well, and and you know we can't go without saying a a, a a new tags. Conversation without talking about nps is like peanut butter without jelly. Does that work?

231
00:43:25.810 --> 00:43:32.119
Philip Sellers: jayra, I'll throw it to you for for closing this out on benefits. Superior customer support

232
00:43:32.820 --> 00:43:37.719
Jirah Cox: it. It is job number one, right like

233
00:43:37.830 --> 00:43:48.769
Jirah Cox: Absolutely true customers. Customers enjoy and love running. Xanax customers tell other customers that they enjoy loving and running.

234
00:43:49.130 --> 00:43:53.140
Jirah Cox: and it's a huge part of why I'm here. It's something that I love telling our customers about.

235
00:43:53.200 --> 00:43:56.679
Jirah Cox:  And and

236
00:43:56.700 --> 00:44:14.429
Jirah Cox: I'll say this, as we highlight more and more of these years, 7 years, 8 years 9 years of 90 plus nps customer satisfaction ratings. And of course we're kind of on a big you know. I'm sure we'll make a lot of hey about when we hit 10 years in a row there. As we hit these milestones.

237
00:44:14.510 --> 00:44:26.259
Jirah Cox: What I would remember is, where do we start out right during this 7, 8, 9 year period, as we've maintained this low customer support. And fandom. Really.

238
00:44:26.410 --> 00:44:33.090
Jirah Cox: we have, like tenx or customer base, right? So tons more nodes in the field tons, more clusters in the field

239
00:44:33.120 --> 00:44:36.030
Jirah Cox: tons, much, much larger support staff

240
00:44:36.250 --> 00:45:00.650
Jirah Cox: and I don't know the exact number on like cases per day on average handled, but I guarantee it's higher than it was 7, 8, 9, 10 years ago. And so that I remind customers, speaks to our commitment to maintaining this as we grow like anybody can do it flash in a pan one time as a sampling data point, maintaining over time takes dramatic intentionality and investment

241
00:45:01.700 --> 00:45:11.370
Philip Sellers: so set a different way. It's easy to scale the new tanks. Cluster nodes. It's harder to scale the newtanic support experience. And yet you're doing that. Well as well.

242
00:45:11.580 --> 00:45:14.339
Ben Rogers: What do we do buying those things like, you know?

243
00:45:14.350 --> 00:45:24.270
Ben Rogers: I've gotta add to this. I just did a tour of our support center in Durham and talking to support leadership. And these are some smart people.

244
00:45:24.270 --> 00:45:49.059
Ben Rogers: and the in the way that they go about evaluating our engineers and onboarding our engineers and looking for future engineers. I mean, we've got a partnership with East Carolina University going on. And so I mean, just really you you begin to understand. You see the score, and you know the scores impressive. But when you start to see how they have the engine working, and what goes into keeping that engine running

245
00:45:49.060 --> 00:46:05.799
Ben Rogers: as good as it is, and making it better than what we you know we are now, it's really impressive, you know. So so an employee of the company. It just really fascinated me when I got to see the inside workings of it and the people that are managing, I mean, these are some smart.

246
00:46:05.800 --> 00:46:21.000
Ben Rogers: smart people that are running that part of our company. And so I was highly impressed with that. So II think the score speaks to the people that are running and working in the department, and once you meet and see those people, you understand why it is a 90 plus score.

247
00:46:21.470 --> 00:46:35.070
Philip Sellers: II wholeheartedly agree with that. As a a partner of yours. It is impressive to to go and see and talk with the folks in the support organization. At the beginning of podcast I mentioned, I spent

248
00:46:35.530 --> 00:46:48.070
Philip Sellers: a day at the Durham headquarters doing an Evc with a customer and one of the highlights for me was they brought in one of the support agents, not the manager, although we met him

249
00:46:48.260 --> 00:47:15.009
Philip Sellers: not. Not one of the managers, not one of the Vps, one of the in line folks answering tickets working with customers, and she was absolutely one of the most impressive people I've encountered in many years. I was really really impressed by her, so my feedback to to the folks in the room was, bring her back and bring her associates back. It's really the best way to show off what you're doing.

250
00:47:16.730 --> 00:47:28.430
Philip Sellers: Well, Jets, I really appreciate. Today's conversation. I mean to me in us inside of the portfolio is a huge part of why Vdi runs so well

251
00:47:28.480 --> 00:47:39.770
Philip Sellers: it. It just answers another critical question around profiles and user data. And there's so much more value there for

252
00:47:39.780 --> 00:47:55.489
Philip Sellers: new tanics customers and potential new tan tanks customers. So if if you don't know or if you need to go deeper in on some of these topics. Please reach out. You can always email sales at Integratecom. That'll get you connected with your account. Rep

253
00:47:55.760 --> 00:48:16.330
Philip Sellers: we'd be glad to to work with you and go deeper one on one sessions. Education we have workshops and webinars, events and things like that all the time. But please please do reach out if we could be of help. But on on behalf of the Z Integral team myself and Harvey. Wanna thank Jair and Ben.

254
00:48:16.490 --> 00:48:27.839
Philip Sellers: We appreciate this conversation. Thanks for nominating the conversation. The blog post shout out again to Shawn Donahue and Santosh simple.

255
00:48:28.290 --> 00:48:38.370
Philip Sellers: We appreciate you posting this out for us to talk about today. And we look forward to having another conversation very, very soon.

256
00:48:39.670 --> 00:48:41.379
Harvey Green III: Great day everybody

257
00:48:41.990 --> 00:48:43.129
Jirah Cox: thanks. Very much. Phil.