XenTegra - The Citrix Session

The Citrix Session: Accelerate Your Hybrid Strategy with Citrix & Nutanix Cloud Clusters on Azure

May 22, 2023 XenTegra / Andy Whiteside / Bill Sutton Season 1 Episode 133
XenTegra - The Citrix Session
The Citrix Session: Accelerate Your Hybrid Strategy with Citrix & Nutanix Cloud Clusters on Azure
Show Notes Transcript

If you haven’t picked up on the trend yet, let me just reinforce that Citrix is working overtime in 2023 to help you go all-in on your hybrid multi-cloud strategy. As we announced earlier this year, we’re significantly investing in features and solutions that provide you with the choice and flexibility to develop your environment how you want it, where you want it, and to integrate with solutions you want.

To that end, we know that many of you are leveraging or considering leveraging Nutanix Cloud Clusters (NC2) hybrid multi-cloud software to simplify IT operations, move to the cloud faster, and lower your on-premises cost of operations. We are excited to announce official support for running Citrix DaaS and Citrix Virtual Apps and Desktops on Nutanix Cloud Clusters on Azure.

The Citrix plugin for NC2 on Azure is available today for early access, and is currently compatible with Citrix Machine Creation Services (MCS). Compatibility with Citrix Provisioning Services (PVS) is expected prior to general availability later this year.

While Nutanix NC2 on Azure was previously a Citrix-Ready validated solution, by providing official Citrix support, we’re ensuring customers can move forward with their hybrid multi-cloud deployment plans, and be confident that they’ll have a great support experience if they run into any issues along the way.

Azure support for NC2 comes as a significant extension to previously announced support for Nutanix Cloud Clusters on AWS – a capability shown to help you burst 2,000 Citrix Desktops to AWS in under two hours as opposed to days or weeks!

Host: Bill Sutton
Co-host: Geremy Meyers
Co-host: Todd Smith

WEBVTT

1
00:00:02.350 --> 00:00:19.910
Bill Sutton: Hello, everyone! And welcome to episode 133 of the Citrix session. I'm your host, Bill Sutton today, Andy White Side is unavailable for this one. So we're gonna we're gonna carry on without him with me As usual, I have Todd Smith and Jeremy Myers from the Cloud software group. Aka Citrix

2
00:00:19.930 --> 00:00:21.620
Bill Sutton: Todd, you will say, Hello.

3
00:00:21.830 --> 00:00:28.130
Todd Smith: hey? Good Good day. Thanks for thanks for having us here today, Bill. We do, Miss Andy.

4
00:00:28.380 --> 00:00:29.450
Todd Smith: but

5
00:00:29.530 --> 00:00:32.980
Todd Smith: you know it's great to have you as a so in host

6
00:00:33.040 --> 00:00:33.870
Todd Smith: for this.

7
00:00:34.010 --> 00:00:37.950
Bill Sutton: Thank you, Todd. Yeah, we do, Miss Andy, for sure, Jeremy, you want to say hello.

8
00:00:38.230 --> 00:00:41.950
Geremy Meyers: Good morning. Good afternoon, actually right. So

9
00:00:42.100 --> 00:00:50.470
Geremy Meyers: how you guys doing, Bill? I got to see you last week in Chicago, Todd one of these days. I guess I could see you here in about a month when I

10
00:00:50.600 --> 00:01:09.640
Bill Sutton: that'll be fun. That'll be fine. Yeah, it was good seeing you, Jeremy. I'm actually as soon as we're finished with this recording the podcast, I'm. Actually headed to Huntersville. I think I will see you tomorrow as well at one of our blueprint dinners or lunches. I will be there. I will be there. In fact, I will be tag teaming the

11
00:01:09.820 --> 00:01:15.510
Geremy Meyers: the presentations. I'll be doing the citrus presentation. So that'll be fun. Okay, definitely.

12
00:01:16.060 --> 00:01:35.230
Bill Sutton: So we settled today on a blog article. It's entitled to accelerate your hybrid strategy with Citrix and Mechanics cloud clusters on azure written by Calvin Sue. This is timely for some of us on Jeremy, as he mentioned, and I were at the Newutanic stop next conference out in Chicago last week, and

13
00:01:35.230 --> 00:01:48.090
Bill Sutton: this was a one of the topics. One of the topics of the conference talking about Nc. 2, as mechanics off often refers to it. So this we'll we'll just hit. Jump right into it.

14
00:01:49.650 --> 00:01:52.470
Bill Sutton: Jeremy, You want to start us off. Kick us off.

15
00:01:53.370 --> 00:02:05.340
Geremy Meyers: Yeah. So first of all, it was really good being in Chicago last week, so I mean I've been working with the Citrix on Newtonic stack for a while.

16
00:02:05.540 --> 00:02:13.830
Geremy Meyers: You know. I think we have a lot of parallels as the 2 companies. So you know, I think we kind of both lean into, You know hybrid computing

17
00:02:13.900 --> 00:02:30.820
Geremy Meyers: is where a lot of customers are going to end up landing right? So you know, I think Todd will tell you, Bill, You probably seen this first hand there a lot of customers who were on premise, on premises, so to speak, and when investigating, you know, leveraging the cloud, look to just lift and shift, move everything to the cloud.

18
00:02:31.190 --> 00:02:39.510
Geremy Meyers: and then I guess what they found out is maybe when some levels of cost too much on some levels, just the application architecture, didn't make sense. But for whatever reason they chose, they decided

19
00:02:39.540 --> 00:02:52.240
Geremy Meyers: that they're gonna have to have a mix between on Premise cloud. And in some cases multiple clouds. Ultimately, you know, things are gonna have to live wherever they live. The business is going to drive a lot of that. And so.

20
00:02:52.260 --> 00:02:54.430
Geremy Meyers: you know, ultimately, that was kind of the whole.

21
00:02:54.760 --> 00:03:02.070
Geremy Meyers: you know. That was a lot of the messaging around Newton's next last week. That's been the messaging around. You know the citrix business unit, for

22
00:03:02.200 --> 00:03:08.030
Geremy Meyers: you know several months now. So it was kind of interesting to see the combination. So I think what this blog post does is really talk about where

23
00:03:08.080 --> 00:03:15.400
Geremy Meyers: you know Citrix is headed so Cabin Shu is, you know, one of the principal. He's a director of you know, product marketing for the citrix, be you

24
00:03:15.630 --> 00:03:20.780
Geremy Meyers: where we're headed, and how that sort of connects with where Newton's head and and ultimately

25
00:03:21.090 --> 00:03:26.970
Geremy Meyers: you know what they're doing here, and extending out their cloud clusters to to add her, which is pretty slick. Actually.

26
00:03:27.970 --> 00:03:36.670
Todd Smith: Yeah, in in Jeremy to your point about you know, the customers being either apprehensive or or limited, is to to their move to the cloud.

27
00:03:38.390 --> 00:03:42.320
Todd Smith: you know. Sometimes there was also financial reasons

28
00:03:42.340 --> 00:03:44.750
Todd Smith: why they couldn't move to the cloud. So, for instance.

29
00:03:44.780 --> 00:03:52.250
Todd Smith: you know, a lot of customers have invested on big amounts of dollars in building out data centers that were amortized over

30
00:03:52.580 --> 00:03:55.960
Todd Smith: 1015, 20 years that they're

31
00:03:56.160 --> 00:04:07.600
Todd Smith: that they really can't move out of the cloud easily from a financial perspective. And the other big reason why people are hesitating to move to the file is because sometimes it's a data, sovereignty or data governance issue

32
00:04:07.630 --> 00:04:13.630
Todd Smith: where they can't put data or services in a cloud based on

33
00:04:13.700 --> 00:04:24.170
Todd Smith: regulatory requirements or compliance requirements. Or you know, the control plane needs to reside within certain areas of the world and is prohibited from being

34
00:04:24.400 --> 00:04:35.790
Todd Smith: publicly accessible. Right? So there there's other reasons besides the technologies that are. It's sometimes limit folks ability to go to the cloud, go directly to the cloud.

35
00:04:36.260 --> 00:04:53.550
Bill Sutton: Yeah. So why don't we? Those are all great points. Why don't we step back a second and talk about what is Nc. 2 on azure? What are newutanics? Cloud clusters? What does that really mean? G. Either you guys have insight into that. I have some general ideas, but I don't know if you guys have more insight into that. That I do.

36
00:04:54.140 --> 00:05:05.380
Geremy Meyers: I I do. In fact, it was so. It kind of from 2 different perspective. So the first one being, you know. Listen, I don't work for new tanks. I don't have a new tennis cluster sitting in the back.

37
00:05:05.410 --> 00:05:19.670
Geremy Meyers: You know that I can go pop in and and look into You know I I watch as much you, too, about things as I do anything else. So you know. So going into next, I knew a lot of this stuff at like an academic level outside of, you know, got a lot of customers who have been deploying on

38
00:05:19.680 --> 00:05:31.310
Geremy Meyers: Acropolis in general for years. but walking into the new tanks like the the vendor booth, and just walking in as a beginner all over again and going, hey, guys, will you show me what this looks like and having them take me through

39
00:05:31.710 --> 00:05:44.560
Geremy Meyers: was kind of cool, actually. But you know ultimately, the idea is, you know, today, when you think about it when you're running workloads on purposes, you're probably hosting them on the sphere. Maybe you're running if you're new tennis customers probably Acropolis.

40
00:05:44.570 --> 00:05:51.100
Geremy Meyers: If you're a citrix customer that's been doing this for years, it might be even zoom or citrix hypervisor. But ultimately you got a tool sack

41
00:05:51.110 --> 00:06:03.410
Geremy Meyers: that you're running on prem, which, by the way, is very different than what you're running in azure, right? So you're login to azure You're learning the tooling around how to manage. You know, as your resource manager. You're figuring out how to run arm.

42
00:06:03.500 --> 00:06:24.570
Geremy Meyers: And, by the way, if you go to aws, you're doing the same thing. You've got to learn the the to Us. Stack, which is completely different manager, which is completely different than your on Prom. So what mechanics is doing with new tanks, Cloud customer clusters is trying to sort of normalize that experience. You're running Acropolis across all 3 clouds is what it is. So from one view.

43
00:06:24.750 --> 00:06:30.910
Geremy Meyers: Prism right. I have visibility into all of my 3 different clouds. I can manage workloads

44
00:06:30.960 --> 00:06:41.660
Geremy Meyers: from one vantage point. I hate to say one panic glass, but I can orchestrate from prism to all 3 different types of locations which is fantastic. So

45
00:06:41.660 --> 00:06:57.630
Geremy Meyers: what that means is, if i'm trying to build an application, and I do it on premises, it makes it really easy to move that to azure. It makes it really easy to move to a and us, because i'm not having to retool the app or the workload, because it's still running on the crop list, which is pretty cool. Now. How that works in practice is different

46
00:06:57.780 --> 00:07:00.870
Geremy Meyers: on our on aws. So I think a of us is bare metal.

47
00:07:01.000 --> 00:07:16.170
Geremy Meyers: so i'm running Acropolis on bare metal at aws, you know instances. If i'm doing this in azure, it works a little bit differently, so it's more of an integrated solution on top of azure, but ultimately, as an it professional. I don't need to care right, because at the end of the day. I'm just looking at prism.

48
00:07:16.280 --> 00:07:20.900
Geremy Meyers: An Acropolis manages the workloads the how it works. So it's pretty cool.

49
00:07:20.980 --> 00:07:42.630
Bill Sutton: Yeah, that's interesting, because what you said something I wasn't aware of Jeremy, so I probably would have said it wrong. I'm glad you went first. so I think my understanding of Nc. 2 on azure was that it was a mirror, if you will, not a mirror, but a very similar deployment to Nc. 2 on aws. In other words, it was running on bare metal. But that's apparently not the case. However.

50
00:07:42.630 --> 00:07:52.910
Bill Sutton: from the standpoint of an administrator or an engineer and a customer, it looks the same. In other words, they. One of the big advantages, as I understand it, is the ability to to essentially

51
00:07:52.910 --> 00:08:11.840
Bill Sutton: move workloads in real time from one location to the other kind of in the in the vein of of of, you know, like zen Motion or V motion, we could do between the same cluster on premises. This is a very similar, a similar process, and does not require the

52
00:08:11.840 --> 00:08:19.510
Bill Sutton: reconfiguration of the workload or refactoring of the workload in terms of having to pull drivers out and inject new drivers and that sort of thing, because it's the same platform.

53
00:08:19.630 --> 00:08:26.340
Geremy Meyers: So let me let me just clarify one thing, because I did go into the booth and ask this right? I wanted to know. Could I?

54
00:08:26.590 --> 00:08:43.409
Geremy Meyers: By the way, what do they call it when you you call the most and or in motion. What is it called an Acropolis where we are? So we're gonna call it a motion right now, because I don't know what to call it. We'll fix this. We'll fix this on next Week's podcast, but ultimately I think it's migrate vms or something, you know something generic.

55
00:08:43.409 --> 00:08:53.090
Geremy Meyers: So I did ask the question. Can I sort of do that live motion across, you know, on premises to Cloud? And the answer was, there was a little bit of downtime, so it's not

56
00:08:53.370 --> 00:09:12.370
Geremy Meyers: kind of like the motion where the user you know. No one knows. There's a little bit of downtime that takes, you know. It mirrors it over the other side probably does a a mirror of the mirror, you know, to get the deltas until there's an off and on. I think some of that just has to do with the just the response time. Yeah, it's got to be super low to be able to pull something off like that

57
00:09:12.370 --> 00:09:15.660
Geremy Meyers: easy to do in the data center between data centers, it becomes a little harder.

58
00:09:15.710 --> 00:09:26.670
Geremy Meyers: So as far as I know, there is some kind of downtime, although it's not a lot into your point. You're not having a refactor. Your workload, which is a really big deal

59
00:09:26.900 --> 00:09:27.540
Todd Smith: right?

60
00:09:29.290 --> 00:09:39.900
Bill Sutton: So that gives us good baseline of what Nc. 2 is, so as far as the blog article itself indicates, why use Nc. 2 with Citrix.

61
00:09:39.940 --> 00:09:46.900
Bill Sutton: So the first item here i'll let all of you guys, i'll just toss it out there and easily expand on premises. Citrix work close to the cloud.

62
00:09:47.510 --> 00:09:56.400
Todd Smith: Yeah, and I can. I can chime in on that one, because a lot of times people what we're seeing a lot of customers do is they're using the cloud as a way to burst out

63
00:09:56.570 --> 00:10:08.240
Todd Smith: additional capacity or to do some type of testing. That's their first kind of for a into the cloud. Right? I need to do some testing. I don't want to go out and build out an environment

64
00:10:08.500 --> 00:10:10.060
Todd Smith: with physical hardware.

65
00:10:10.070 --> 00:10:16.220
Todd Smith: hey? The cloud provides some real great resources. Cloud also provides some great resources for disaster Recovery

66
00:10:16.240 --> 00:10:22.350
Todd Smith: Cases like this. So with Nc. 2 and Citrix really it it it

67
00:10:22.540 --> 00:10:26.730
Todd Smith: starts with that. It's got to be easy to enable those.

68
00:10:26.780 --> 00:10:34.370
Todd Smith: Take those on premise workloads and migrate them over to the clouds very easy, especially the citrix workloads.

69
00:10:34.960 --> 00:10:48.180
Todd Smith: And and that was kind of the starting point. Right? So how do we make sure that that works and make sure that works. See mostly. Well, the first thing you want to do is you want to make sure that the tools are set up, and the administrative processes

70
00:10:48.500 --> 00:10:54.390
Todd Smith: are as simple as possible, so that you don't have to give up something to make this work

71
00:10:57.310 --> 00:11:14.840
Bill Sutton: right, so the the next item will, before I do that, Jeremy. Any comments on that on that. So let me look at this. There's a there's a something. I I chatted with an architect while I was there that might fall into this bucket the best. So you know, we talk about

72
00:11:15.330 --> 00:11:23.600
Geremy Meyers: being able to expand on premises workloads. We're talking citrix here, but you know, just generally speaking, take on premises, workloads and expand those out to the cloud.

73
00:11:25.350 --> 00:11:32.520
Geremy Meyers: One of the botanics architects told me this, and I thought was pretty fascinating is just given the supply chain challenges that we've got right. Now.

74
00:11:32.820 --> 00:11:38.360
Geremy Meyers: you know the idea is well. In some cases, you know I need to roll out new clusters, but I don't have

75
00:11:38.450 --> 00:11:40.380
Geremy Meyers: the hardware yet. So

76
00:11:40.390 --> 00:11:48.110
Geremy Meyers: he that goes he he uses phrase called Cloud start, which is what if you could start in the cloud and then move it back right? So I need to roll out the users like right now.

77
00:11:48.390 --> 00:11:52.980
Geremy Meyers: You know I need to scale out or expand, but I don't have the hardware. What if I started in the cloud

78
00:11:53.130 --> 00:12:00.610
Geremy Meyers: with this new use case, and as I get the hardware in, and I add that to my on-premises cluster, I can migrate those users back which is kind of a different

79
00:12:00.680 --> 00:12:14.820
Geremy Meyers: a different thought right, because again it's the same platform you're moving these folks around. However, you need to. Why not start in the cloud and just move it when you need it

80
00:12:14.820 --> 00:12:32.660
Bill Sutton: scale with additional nodes. The ability to this gives you the ability to really quickly scale up with additional nodes just by adding a note. And this is kind of going back to the early days of Newtonics that that's kind of, you know. When they first came out as an offering, one of the one of the value props there was

81
00:12:32.660 --> 00:12:40.920
Bill Sutton: the ability to you. You state up a 3 Cl: 3. Node cluster is so you can get a just. We'll throw a number out there, so you can get 300 users per node.

82
00:12:40.970 --> 00:12:51.730
Bill Sutton: You wanted to add 3 or more users. You just had another node. You want to add 600 users. You had 2 nodes, I mean in theory. So it's scaled in a linear way. But what's interesting about this is

83
00:12:51.770 --> 00:13:09.830
Bill Sutton: it talks about that same concept, but being but being able to do it in the cloud, and where you can expand it seamlessly up to 16 nodes. But then scale it down. Which kind of weighs into your argument there, Jeremy, about the ability to go both up and back, if you will, and that's really a an interesting

84
00:13:09.830 --> 00:13:13.010
Bill Sutton: advantage of this. Any thoughts on that

85
00:13:14.560 --> 00:13:24.690
Geremy Meyers: I mean, you know your on-prem clusters or i'm not going to say there is some cost, because I think in a lot of cases there is on prem subscriptions that make that look a little different now. But

86
00:13:24.720 --> 00:13:30.600
Geremy Meyers: listen when you're running in the cloud, and when you've got it turned on you're paying the you're paying the ticker

87
00:13:30.660 --> 00:13:37.750
Geremy Meyers: Anything you can do to turn workloads off, suspend whatever you can do to turn that you know that that faucet off

88
00:13:38.080 --> 00:13:44.970
Geremy Meyers: is is awesome. So the fact that you can do that from both a new tanks perspective. You know as well as Citrix, using auto scale. Let's be select.

89
00:13:46.780 --> 00:14:05.530
Bill Sutton: Yeah. And then moving to the next one. I'm not rough trying to rush through this, but save on cloud. Infrastructure costs this kind of plays into what you just said to Jeremy. You're very forward looking here. It's like I stared at this. I didn't mean to do that, but I but this is interesting because this is not something that I think you can natively do easily

90
00:14:05.530 --> 00:14:25.230
Bill Sutton: in certain clouds that to be able to do hibernating, resume. I know that that there's at least one cloud that does suspend, resume very, very easily, but this keeps you the ability to put along, but the clusters on hold when capacity is not required, and then so this, and then resume them when necessary. So todd any thoughts on that.

91
00:14:25.520 --> 00:14:33.860
Todd Smith: Yeah. And and I think this is kind of where everyone's trying to get to is the ability to control not only the cost, but also the performance.

92
00:14:33.960 --> 00:14:34.960
Todd Smith: and

93
00:14:35.240 --> 00:14:38.810
Todd Smith: you know there's a big difference between hibernate and suspense

94
00:14:38.820 --> 00:14:46.870
Todd Smith: right in in. Both of those are different than turning off right. So if I need to spin up something from a

95
00:14:47.070 --> 00:14:48.660
Todd Smith: from a dead stop.

96
00:14:48.850 --> 00:14:53.970
Todd Smith: It's going to take me considerably more time and resources to do that versus.

97
00:14:54.200 --> 00:14:54.940
Todd Smith: you know.

98
00:14:55.060 --> 00:15:01.060
Todd Smith: Take something out of hibernation, taking out of a suspend boat right? So there's there's cost associated with that.

99
00:15:01.190 --> 00:15:09.190
Todd Smith: There's also the time and effort, right If we if we're talking in a specific industry like health care. As an example.

100
00:15:09.340 --> 00:15:12.020
Todd Smith: you know precious seconds matter.

101
00:15:12.280 --> 00:15:16.810
Todd Smith: and they don't want to have to wait right. There is entire

102
00:15:17.350 --> 00:15:22.310
Todd Smith: segment of the software industry that deals with, you know, optimizing performance.

103
00:15:22.970 --> 00:15:25.600
Todd Smith: And this is just another

104
00:15:26.670 --> 00:15:30.620
Todd Smith: instance where you know that that technology is coming into play.

105
00:15:33.140 --> 00:15:37.520
Bill Sutton: Yeah, it's interesting that it re this section of the article reflects

106
00:15:37.630 --> 00:15:48.550
Bill Sutton: kind of a something that it's that I'm: i'm very familiar with, and that is things being left on by my kids, mostly lights, not television. But and this

107
00:15:48.720 --> 00:15:53.310
Bill Sutton: concept of of being able to scale back

108
00:15:53.540 --> 00:16:10.360
Bill Sutton: or hibernate workloads and save costs. But then give you kind of the same level of agility, or at least a close level of agility, in terms of being able to spend the backup. You know much more quickly than like you, said Todd, from a. From a dead state, or a the allocated state and azure

109
00:16:10.380 --> 00:16:22.830
Bill Sutton: so certainly an advantage. I, you know when I first read this just scanning it. I was thinking, okay, so you can suspend and resume, or hibernate and resume vms. But this is talking about putting whole clusters on. Hold? That's a yeah, the whole different ball game. There.

110
00:16:24.480 --> 00:16:28.950
Todd Smith: Now you're talking about cost savings at at scale.

111
00:16:28.970 --> 00:16:37.810
Todd Smith: at scale of the data center in it in in situations where it's going to make a huge difference on your costs. If you can shut down

112
00:16:38.060 --> 00:16:40.680
Todd Smith: an entire cluster versus individual Vms.

113
00:16:41.550 --> 00:16:43.240
Bill Sutton: Exactly. Yeah.

114
00:16:44.090 --> 00:17:03.320
Geremy Meyers: Interesting. I would, I would imagine, and we don't really want to get into pricing. But I would imagine that that suspending them doesn't suspend the cost, but probably reduces the cost for the time it's suspended, I would imagine something. So yeah, you know. So when you think about it, just using just thinking about how azure works right? So it's probably not the allocated

115
00:17:03.490 --> 00:17:16.970
Geremy Meyers: I just suspended. So there is some level of consumption that is reserved. If you need to spin it back up like you. Yeah, somebody else can grab it. And then you're not able to spin it back up in a in a really serious situation that that would be a problem.

116
00:17:16.990 --> 00:17:25.510
Geremy Meyers: Yeah. So I mean, there's definitely some questions there. Does it make sense to do that with a observed instance of some kind. But you know I don't still trying to pick apart what that looks like, so

117
00:17:26.109 --> 00:17:29.160
Bill Sutton: i'm sure there'll be more to come for sure. This is very new.

118
00:17:29.860 --> 00:17:45.380
Bill Sutton: So the next item here experience familiar administrative features, so the integration of C. Bad, or citrix to with mechanics, clusters, provides new tanks, customers with the same management experience. So same prism interface from a mechanics perspective.

119
00:17:45.430 --> 00:17:56.100
Bill Sutton: same citrix as interface can be used. and with respect to mechanics, the same one on prem versus using mechanics clusters in azure.

120
00:17:56.150 --> 00:17:58.060
Bill Sutton: Any thoughts on this Jeremy or Todd

121
00:17:59.620 --> 00:18:08.270
Geremy Meyers: I mean, i'll tell you that out of curiosity I went out to the azure portal, just to see just to see it out there. So there is

122
00:18:08.770 --> 00:18:14.330
Geremy Meyers: it's it's out there on the azure marketplace, which is awesome. So what that means is, if you are a

123
00:18:14.750 --> 00:18:24.510
Geremy Meyers: if you have any sort of commit with with Microsoft on azure, it looks like this will probably ding that plan, so you can use up some of your consumption as you go.

124
00:18:25.570 --> 00:18:30.430
Bill Sutton: Yeah, that and indicates that new tennis customers can use their existing term licenses

125
00:18:30.440 --> 00:18:40.000
Bill Sutton: to get the consumption of the new panic software through the azure marketplace. So that makes makes it pretty simple for them to to move into the cloud leveraging in C 2 based on what this says.

126
00:18:40.280 --> 00:18:45.320
Geremy Meyers: Yeah. As I'm. Looking at this, it talks about how the payment frequency is $0 a month.

127
00:18:45.710 --> 00:18:55.470
Geremy Meyers: and you're probably using your your cluster licensing what you already own, You keep it on the cluster. So that point you're just paying for whatever the azure consumption of this is.

128
00:18:58.280 --> 00:19:00.030
Geremy Meyers: Yeah, yeah.

129
00:19:00.170 --> 00:19:07.640
Geremy Meyers: no, this is. This is very cool. So this is Ga. Now. So I can clearly go out to the portal and grab it

130
00:19:09.300 --> 00:19:20.690
Geremy Meyers: fully supported. So it's not a it's not like a what is what is new tanks call there? I'm gonna use a citrix word, but their tech previews. This isn't like early access, is what they call it. So. Is it still early access, or is this Ga. Now?

131
00:19:20.760 --> 00:19:33.140
Todd Smith: Oh, I saw it. Reference to G. A reference to Ga. Or maybe it's a Ga. Soon. Yeah, there's a couple of references around Pbs and Mcs integration as well. There is. Yeah, we mentioned. We skipped over that. Yeah, yeah.

132
00:19:33.230 --> 00:19:37.040
Bill Sutton: yeah, it says the plugin. It's the plugin for Nc. 2

133
00:19:37.110 --> 00:19:44.450
Bill Sutton: is available for early access, as currently works with Mcs and Pbs is expected later this year.

134
00:19:44.580 --> 00:19:45.170
Todd Smith: Yeah.

135
00:19:46.000 --> 00:20:00.600
Geremy Meyers: Got it. So I guess the real point to this one as well is this is already been validated for the Citrix ready program. So I did have a meeting with one of our internal architects, and he's been working pretty close on this joint solution. So it is validated

136
00:20:00.660 --> 00:20:04.580
Geremy Meyers: like you said it works with Mcs today, and I think later this year.

137
00:20:07.260 --> 00:20:09.740
Geremy Meyers: you just said, but

138
00:20:10.950 --> 00:20:22.740
Geremy Meyers: that's pretty select. You know what? Here's the real question now as much as I love Pvs. You know, Bill, what you know about Newton's in the shadow copy clones that that kind of come with it. You know, Ncs is

139
00:20:23.250 --> 00:20:41.860
Bill Sutton: an awesome solution on the team. It is an awesome solution, and I know there were a lot of you know we've we've done most of the projects we've done with Newtonix had been Mcs. We, I believe we've had trying to remember if they ended up staying with it. I think they did. We had one where they leveraged the Pvs with an on-premises cluster.

140
00:20:41.950 --> 00:20:44.180
Bill Sutton: and but you know as as

141
00:20:44.220 --> 00:20:50.330
Bill Sutton: the way you are, the way the newutanics is designed it. It really lends itself to Mcs as as

142
00:20:50.540 --> 00:21:08.170
Bill Sutton: where that makes sense from performance, perspective, and management perspective. You don't have as as much much infrastructure required as you do with Pbs. And it because of the shadow copy Clones and the and the data locality, you don't really get a performance hit, or at least not much of one, if any with Mcs. So

143
00:21:08.170 --> 00:21:20.770
Bill Sutton: most customers are are either pivoting from Pbs. On premises to Mcs. On the tanks. We have a couple that have have continued to leverage Pbs. Largely because I think they're familiar with it. They're comfortable with it.

144
00:21:20.770 --> 00:21:32.910
Bill Sutton: and one benefit of pbs is, if you want to go back from you know your one image to the image previously. It's really just a reboot. There's not a lot of orchestration that needs to go on in the background. It's really just stupid, simple.

145
00:21:33.040 --> 00:21:38.460
Geremy Meyers: So, being very cognitive of the fact that Todd came from Martin's, and

146
00:21:39.750 --> 00:21:56.110
Geremy Meyers: it's got a a special place in it's hard for it. Yeah, it's an interesting conversation, although I will say this because this has been image portability, has been a big topic for on-premises, customers moving to the cloud. So if you're an existing Pbs customer running on it tanks.

147
00:21:56.730 --> 00:22:02.430
Geremy Meyers: it's pretty easy because your image does not need to again be refactored for Pvs. In the Cloud.

148
00:22:02.520 --> 00:22:17.990
Geremy Meyers: Whenever that goes live. It's just easily to you know. You can move those images over. The rollback is super nice, right? So being able to just roll back almost instantly. It's a huge selling factor. But I gotta imagine you know the other piece of that is just being able to move this Pvs images.

149
00:22:18.210 --> 00:22:24.160
Geremy Meyers: you know, out to a cluster sitting in azure or aws, for that matter, that's pretty powerful as well.

150
00:22:24.230 --> 00:22:30.950
Todd Smith: yeah, very careful. And that's one of the. And that's obviously one of the things that's that's been out. There is understanding that

151
00:22:31.070 --> 00:22:35.200
Todd Smith: Pbs and Mcs are both going to be around for a while.

152
00:22:35.240 --> 00:22:49.910
Todd Smith: and the fact that that image portability service is really that game, it's the link between that and being able to say no. I could take that same image and use it in Pvs, and I can use it on, and a variety of different cloud platforms as well.

153
00:22:50.170 --> 00:22:52.880
Todd Smith: It really eliminates that that block or

154
00:22:53.840 --> 00:23:00.860
Todd Smith: that a lot of people have, whether it be real or kind of in their in their mind is that you know I i'm gonna have to go and rebuild

155
00:23:01.810 --> 00:23:06.070
Todd Smith: my entire environment just to be able to support these new resources.

156
00:23:07.300 --> 00:23:25.430
Bill Sutton: Yeah, and the and the portability again. And I think this is what you're saying. Todd is. You know when you think about today. If you, if you've got an on-premise to see that environment, or you've got a centric stance environment with your on-premises, workloads, and you want to put those in azure or an aws or gcp for that matter Those images have to be

157
00:23:25.430 --> 00:23:43.040
Bill Sutton: offense essentially converted, or prop. What we would probably recommend is that you build a new. If you're taking an image on Prem, a traditional image on prem and putting it even Mcs and Azure. You don't want to build it an asher to to make sure that you're not going to have any issues same for Aws same for Gcp. Whereas in this instance

158
00:23:43.110 --> 00:23:50.260
Bill Sutton: you like you said, you don't you don't really have to do that, because it's the same underlying environment in theory, across all clouds.

159
00:23:51.400 --> 00:23:52.170
Todd Smith: Absolutely

160
00:23:53.480 --> 00:24:12.580
Geremy Meyers: all right, Bill. You got me chasing down the Did I make that stuff up around bare metal or not in azure. So next week we'll validate it. But I am looking at a slide. In fact, this is one of the slides we presented at the partner session. It's the Monica who's joined us on the on the podcast before has called this slide the new tanks.

161
00:24:12.580 --> 00:24:13.770
Geremy Meyers: the Hamburger.

162
00:24:13.980 --> 00:24:30.420
Geremy Meyers: It's. Got you know it's got prism. It's got Citrix. It's got the new tanks in the middle, and then all your different, you know locations, and it does say Ec. 2, which is aws is bare metal, and then it says additional public clouds, because again, these could be private clouds. But you know, Microsoft.

163
00:24:30.930 --> 00:24:36.560
Geremy Meyers: but we'll get an answer on that, because i'm pretty sure Ec. 2 is bare metal, and I think it's native azure.

164
00:24:36.980 --> 00:24:55.320
Bill Sutton: Well, I I I spent very little time because of meetings and other things in the at all last week, so I didn't get a chance to go around and talk to them, so i'd be inclined to say that there's probably some differences there, because I know that Newton's in a and azure took their time getting into the cloud, and I think that was on purpose.

165
00:24:55.320 --> 00:25:03.010
Bill Sutton: So there, I suspect there are some differences, some advantages and differences between that approach their approach there and to other clouds. So

166
00:25:03.180 --> 00:25:15.870
Geremy Meyers: you know what to, so to your point about being busy. I was. I was busy all week as well. I did get a. I did get a short window of time where I did go into the vendor village and I got to go see. Obviously, I went to the Citrix one. You gotta go high. 5 year old guys

167
00:25:15.940 --> 00:25:22.500
Geremy Meyers: and gals. But you know I did go into the Newtonics one, and of course it just touched a lot of different things. And I

168
00:25:22.530 --> 00:25:29.550
Geremy Meyers: I just remember thinking, man, I missed this. I remember walking into the vendors and just having them. Tell me what it is is new.

169
00:25:29.630 --> 00:25:43.750
Geremy Meyers: because you kind of miss that, and most of them have a really good demo which is really cool to see. Yeah, I gotta be if i'm being transparent, I went into the Citrix Booth doing the same thing. There were things that listen. I get so busy. I kind of miss some things. So sometimes

170
00:25:43.900 --> 00:25:51.010
Geremy Meyers: there are certain things that I haven't seen yet as a citrix employee that it was kind of good to get from the product manager. Whoever's presenting.

171
00:25:51.010 --> 00:26:03.920
Bill Sutton: Yeah, I was in there just briefly for breakfast, and I actually got a chance to finally meet Monica in person. So but I didn't get any demos, because it was early in the morning, and

172
00:26:03.920 --> 00:26:11.920
Geremy Meyers: she did give me a t-shirt that unfortunately I left in one of the exhibit all one of the break rooms. So I have to score that some other time. So

173
00:26:12.690 --> 00:26:19.820
Bill Sutton: all right, anyways, I think we've covered this pretty fully. Anybody any of you guys have any other final closing comments.

174
00:26:21.260 --> 00:26:22.550
Todd Smith: No, I think

175
00:26:22.590 --> 00:26:33.350
Todd Smith: you know, I think the one comment that Calvin put in at the very end here is, you know, Contact your citrus and Newton's partner, and ironically with Zen Tiger. You've got once one phone call to make.

176
00:26:33.380 --> 00:26:36.820
Todd Smith: That's right. So obviously you can reach out to

177
00:26:37.160 --> 00:26:49.400
Todd Smith: to Zen. Take her to here about both Citrix and Newton. There's a couple of other vendors out there to really kind of put this all together so really appreciate the the opportunity to talk here today, so

178
00:26:51.310 --> 00:27:09.740
Bill Sutton: well sure. Thank you, Todd: yeah, we we we've got a lot of experience. Got a lot of experience. Consultants, solutions, architects around both of these stacks and can definitely help help customers get understand the the options here and and what the requirements are, and get them into it if if they want to. So yeah, reach out to your

179
00:27:09.760 --> 00:27:14.600
Bill Sutton: your local Zentag or a CEO. If you don't know who that is, or reach out to me, and i'll tell you.

180
00:27:14.770 --> 00:27:16.860
Todd Smith: Jeremy, any final parting thoughts.

181
00:27:17.120 --> 00:27:25.330
Bill Sutton: You know what I think. I've run my mouth enough. So all right. Thanks so much, guys. We'll talk to you next week.

182
00:27:25.380 --> 00:27:27.660
Geremy Meyers: Thanks to

183
00:27:28.170 --> 00:27:28.900
Todd Smith: you guys.