Nutanix launches the most significant update yet to its Nutanix Cloud Clusters™ (NC2) hybrid cloud software, now enabling organizations to run the Nutanix Cloud Platform™ software on the Microsoft Azure® cloud service. With support for both the AWS and Azure clouds, NC2 is a true hybrid multicloud platform. It provides easy access to Azure services from customer VNets running enterprise applications. There’s a simple migration path for applications without modification, and expanded license portability with a consumption model choice.
Organizations are increasingly investing in the public cloud to solve business and IT challenges for improved operational flexibility, agility and cost-efficiency. According to 1,700 IT decision makers polled for the 2022 Enterprise Cloud Index report, 83% agree that hybrid multicloud is the ideal operating model.
Host: Andy Whiteside
Co-Host: Harvey Green
Co-Host: Philip Sellers
Co-Host: Jirah Cox
Co-Host: Ben Rogers
Nutanix launches the most significant update yet to its Nutanix Cloud Clusters™ (NC2) hybrid cloud software, now enabling organizations to run the Nutanix Cloud Platform™ software on the Microsoft Azure® cloud service. With support for both the AWS and Azure clouds, NC2 is a true hybrid multicloud platform. It provides easy access to Azure services from customer VNets running enterprise applications. There’s a simple migration path for applications without modification, and expanded license portability with a consumption model choice.
Organizations are increasingly investing in the public cloud to solve business and IT challenges for improved operational flexibility, agility and cost-efficiency. According to 1,700 IT decision makers polled for the 2022 Enterprise Cloud Index report, 83% agree that hybrid multicloud is the ideal operating model.
Host: Andy Whiteside
Co-Host: Harvey Green
Co-Host: Philip Sellers
Co-Host: Jirah Cox
Co-Host: Ben Rogers
WEBVTT
1
00:00:02.450 --> 00:00:13.199
Andy Whiteside: Hello, everyone, and welcome to episode sixty. One of new tanks Weekly and your host, Andy White's side have been uh been gone for a few weeks, I think a lot of us have, and now it's Halloween. We have a lot to cover um,
2
00:00:13.210 --> 00:00:32.500
Andy Whiteside: I guess, before we jump too much into the the serious stuff which we probably need to, because we got a short amount of time today. Uh, we were just having the Halloween discussion. Well, first I was having a discussion around how the previous owner of my house used a um what at the time probably seem like a great idea, and I see a ton of this in home automation with my H back unit for upstairs.
3
00:00:32.509 --> 00:00:35.719
Andy Whiteside: But now it's so complicated you can't uh enable.
4
00:00:35.750 --> 00:00:50.859
Andy Whiteside: You can't enable the latest digital transformation of home. H. Back to um to work with it. So I've either got to start over which i'm not going to do, because it's probably ten thousand dollars uh, or I'm just gonna live with the fact that I can't bring my
5
00:00:50.870 --> 00:00:59.130
Andy Whiteside: house in two thousand and twenty-three into my Google nest modern digital transformation from A to back world. Java, You had a phrase for that, would you call it?
6
00:01:01.260 --> 00:01:05.080
Jirah Cox: I called it uh tech it? Yeah, it's a real thing. It's a real threat.
7
00:01:05.710 --> 00:01:11.709
Andy Whiteside: So uh someone over invested too deeply in tech. Now I can't get out of Is that what you're calling
8
00:01:11.960 --> 00:01:21.329
Jirah Cox: It's a well, or it's a you know, past decisions made right that lock you in and limit your options for the future. Right? So always whenever you think about a new technology you gotta think about.
9
00:01:21.410 --> 00:01:26.490
Jirah Cox: But how is it how to interoperate? How to? How do I evolve beyond this on the next phase?
10
00:01:26.850 --> 00:01:41.319
Andy Whiteside: Well, I think that's going to be really closely tied into what we're going to talk about here in a minute. How about that? Uh, then, Rodgers is with Gyro Java Cox. That was the voice of Gyrocox, which hopefully, you know by now. And and Ben Rogers. Those are our two new tanks, Gurus on the call bin. How's it going,
11
00:01:41.330 --> 00:01:52.839
Ben Rogers: Good man? Doing well? Any now question I would have for you is, how long are you gonna have to wait till you get to change that ac units and technology that will work with your Google Nest if you figured out that piece of it.
12
00:01:52.860 --> 00:02:06.709
Andy Whiteside: Well, I don't plan to live here. It's it's my! It's my big house, for when I have four kids, and it's the right thing for what I needed two years ago. Um, I don't plan to be here in one to three years, so i'm gonna let the next guy deal with that.
13
00:02:06.720 --> 00:02:17.099
Jirah Cox: I I think there's some um, you know examples there in our real world. I'm gonna say you're just beefing up per segway. More and more like your mobility affects the choices. You make. It's amazing, Andy,
14
00:02:17.810 --> 00:02:34.540
Andy Whiteside: and and if I had some form of a ubiquitous um hypervisor, I could put in various data centers. I could have gone that I I wouldn't be locked into the other Guy's decision. I could come halfway back, and I Oh, man, if I could virtualize my house, I have so much more more stuff done?
15
00:02:34.840 --> 00:02:37.770
Jirah Cox: Well, I think the Facebook guys are actually working on that
16
00:02:38.090 --> 00:02:44.889
Jirah Cox: right, you know. Roll your roll your house back to a snapshot from before uh before you, you know. Put your foot to the ceiling.
17
00:02:46.410 --> 00:03:05.089
Andy Whiteside: I use this one all the time, too. I travel a lot, and I go now. Finally, in the last couple of years. There's a there's a Usb plug, you know. Usb one dotto, or whatever it is uh plug I could use to charge my paraphernalia at night, maybe multiple. Uh, of course. Now everything I have is Usbc: so
18
00:03:05.100 --> 00:03:22.639
Ben Rogers: like, hey? It finally caught up. But it's already behind the blessing and curse of a standard. Yes, it's actually a standard gyro. What you just said about virtualizing your house. I'm sure my wife would love. That would be. I just built a bunk bed for my son. It is about two times the size of what she wanted,
19
00:03:22.650 --> 00:03:28.749
Ben Rogers: and when she walks in the room I can see the look on her face where she goes. I just wish it was like it was before we started.
20
00:03:28.990 --> 00:03:31.160
Jirah Cox: There you go! There you go, man,
21
00:03:31.550 --> 00:03:47.409
Andy Whiteside: with that virtual. It physical is hard when you make decisions around physical things. But when you can make uh decisions around software Aka virtual all of a sudden, you know, uh bad decisions can be fix more easily.
22
00:03:47.420 --> 00:03:58.009
Ben Rogers: Well, I did make one mistake. I had the design in my head, and I just described it to her in little bits of pieces. I should have done some kind of simple cad drawing.
23
00:03:58.020 --> 00:04:27.489
Ben Rogers: They let her envision what seven feet six inches was gonna look like. And uh, I kind of, you know, I gave her like a design, but I don't think she had the concept of the size. And then, when it started, you know I built it downstairs, and then brought it upstairs. When it started coming together she was like, Oh, Lord! Of course, my son's digging, and he's like, Oh, yeah, a massive place set blah blah blah, and she's just like you've taken up three quarters of the room with the I'm: i'm like a college loft or something. Oh, yeah,
24
00:04:27.500 --> 00:04:37.659
Jirah Cox: to just beat our analogy just all the way to death, like the client approved the uh high, level logical design. But the physical design did not pass muster.
25
00:04:38.400 --> 00:04:40.680
Andy Whiteside: So here's another one, too.
26
00:04:40.690 --> 00:05:09.469
Ben Rogers: Then was she around when you were putting parts of it together, or did she go? My My wife's a good designer, and I don't. I don't know not a knock on her, but she just couldn't envision how this thing would fit in the room and myself, You know I had done the measurements, but it's another thing. When you start to put it together. Now the same in Graces. It is a loft bed, so i'm looking at her like he's really gained the whole room, because now the beds up. But it is A. It is an ominous site in the room.
27
00:05:09.480 --> 00:05:18.070
Andy Whiteside: It's it's It's big. Now, i'm going to keep going with this Ben. Was this totally your design, or did you take a design from somewhere else? That where she could have
28
00:05:18.080 --> 00:05:46.740
Ben Rogers: I got this to breed out of somebody else's mind first? So what I did was because my wife is so picky about design and colors is. I got a an example of what it would look like from a color perspective. Here's what the posts are going to look like. Here's what the rails are going to look like. And she loved that we didn't really have the conversation about the size, and I had to make it bigger than normal, because i'm doing it with a queen size bed.
29
00:05:46.820 --> 00:05:53.429
Ben Rogers: And so you know it's massive man. I i'll take a picture and send it to you. All we're done with the with the podcast.
30
00:05:53.470 --> 00:06:22.180
Ben Rogers: So as i'm thinking through this, i'm thinking great big oracle database that needs to go on premises in private cloud in public cloud all the same time. And if you're not careful you can get it woefully wrong. Oh, yeah, Well, where you're diving into where we're going to. What's interesting is is this is a hot topic for us to talk to customers about right now, because this does open up some doors that you know a lot of customers think about Cloud. What they immediately come to is, I got a refactor, my application
31
00:06:22.190 --> 00:06:49.489
Ben Rogers: and what we're. You know what we're able to offer with this in C to offering is, you, don't have to refactor the application to take advantage of cloud where azure becomes really a good part for us is a lot of people have azure spin as part of their eel licensing or la licensing. I'm. Not up to Microsoft licensing more, but they roll some of this cost in there, and companies are looking at ways to try to take advantage of that without refactoring their applications.
32
00:06:49.500 --> 00:07:00.320
Andy Whiteside: And then you got down to the money conversation right? So you called it spin, I call it commitment, and depending on which side of the equation your own commitments, either really good or really bad, or depends on what moment of the commitment you're in
33
00:07:00.330 --> 00:07:16.229
Andy Whiteside: uh. And so we'll we'll talk through that more. Harvey Green is uh I I I really refer to him as a solutions architect as in Tech. But now he's actually running z tech or go, but he's gonna stay part of this podcast and other podcasts because he's a a great technical mind when it comes to Newtonix Harvey has it going?
34
00:07:16.240 --> 00:07:32.070
Harvey Green: Pretty good, Pretty good. It's a good thing. I was already planning on doing that, because otherwise you would have committed me on here this couple of things you got to keep doing in our world.
35
00:07:32.080 --> 00:07:41.510
Andy Whiteside: And um, it it helps. I love doing this because we're tying technologies down to business outcomes, which is part of my world in your world, no matter what your title says.
36
00:07:41.520 --> 00:07:56.220
Andy Whiteside: We also have a guy in Philip Sellers on today is day one for Philip and Philip is kind of shadowing. He's going to be picking up some of harvey's uh responsibilities when it comes to being uh infrastructure subject matter experts. Specifically, in this case, all things Newton's.
37
00:07:56.230 --> 00:08:07.999
Andy Whiteside: So Philip will be playing a a larger role. I think he's still in in Mobile world, trying to get from the office back to his home. So welcome, Philip, and we'll look forward to being you being part of this conversations going forward
38
00:08:09.700 --> 00:08:20.670
Andy Whiteside: all right. Well, um probably may have not picked up. Our topic today is in the announcement around Nc. Two Um, which is Newton's clusters on azure
39
00:08:20.680 --> 00:08:33.150
Andy Whiteside: and let's jump into the blog. The blog title is Um from October twelfth of this month this year uh Newtonix accelerates hybrid cloud with Microsoft azure.
40
00:08:33.309 --> 00:08:37.120
Andy Whiteside: Gyro. What Why do this Why does this matter?
41
00:08:38.549 --> 00:08:53.190
Jirah Cox: Um! I was thinking as you were talking about it. Um, well, and as a sidebar our listeners, I don't know what timestamp we're at in this episode. But if you'd as if you'd bet me a dollar about like, could, it would Andy tolerate as much preamble as we had there
42
00:08:53.200 --> 00:09:17.319
Jirah Cox: for the for the podcast, that you might be most excited about right this. Go back to the history of this podcast. You were like, Hey, Jerry. Let's do a podcast also. By the way, when Nc. Two on azure right um, you know, and then, like it was like it was almost like a punchline like the the ending. The first five episodes is all like. Oh, by the way, also gyre, when Nc. Two on azure um. So what do we do when we do in ct on aws uh gonna say in the past.
43
00:09:17.330 --> 00:09:20.069
Andy Whiteside: Well, but it had to be like podcast number
44
00:09:20.080 --> 00:09:49.589
Jirah Cox: twenty or something. We've been waiting a while it wasn't on my bingo card, for with this much pent up demand among the hosts of this podcast for us to ramble that long at the beginning. So good self-control really did a good job setting it up because a lot of this things are going to tie into what we talked about here. It was as much, Harvey beating you up as it was me right. So the the why it I kind of formed a thought while you all were talking about about. You know, Ben mentioned refactoring right and moving to the cloud.
45
00:09:50.340 --> 00:09:51.590
Jirah Cox: And the
46
00:09:51.870 --> 00:09:59.559
Jirah Cox: the thing I see a lot among a bunch of my customers is, those can be different timelines and treat them like one timeline. Um
47
00:09:59.720 --> 00:10:16.469
Jirah Cox: can be problematic, right? So of course, we want to refactor our apps. Do we have full power to do that. Not always. I. I know a lot of customers that are ninety percent, you know, caught software right? Purchase software that they deploy and run. Maybe the business units dictate what the the line of business up will be
48
00:10:16.480 --> 00:10:23.679
Jirah Cox: uh it has to run them, but there's not a lot of uh empowerment to actually do that Refactoring yourself right? You're waiting on the vendor to do that.
49
00:10:24.310 --> 00:10:28.070
Jirah Cox: But whether we have that power to to refactor or not.
50
00:10:28.080 --> 00:10:49.110
Jirah Cox: There's a lot of mandates or benefits, or or use cases for getting to public cloud. I want to get on my data center. I want to uh stop spending money on a Dr. Site. I want to uh get more mobility. I get more availability than I have in my local data center. Um, I want to move to Cloud because I've got business alignment right with Microsoft funding, or or other strategic partnerships. Um!
51
00:10:49.120 --> 00:10:59.290
Jirah Cox: That just don't give a hoot whether you can or can not refactor your apps, or what timeline that might be. So the use case of get to cloud sooner.
52
00:10:59.630 --> 00:11:07.010
Jirah Cox: Um with the apps that we have today, but prepare for the apps that we want to run tomorrow really does resonate pretty pretty quickly,
53
00:11:07.950 --> 00:11:27.349
Andy Whiteside: so i'll do a normal endiism which is beat up on the idea that it's not cloud. It's clouds and gyro. When you say, get to the appropriate cloud, you really mean the pro the appropriate cloud of the cloud options as soon as you can, because time is money. Efficiencies is time and money.
54
00:11:27.360 --> 00:11:30.749
Andy Whiteside: Um! It makes sense to get. If you're going there they might get there
55
00:11:31.310 --> 00:11:44.999
Jirah Cox: totally. The the matching, the matching gyro is is. It is one cloud, but it's your cloud right. It's like the Acme Cloud, or whatever company you work for that you need to find a way to have presence in one or more
56
00:11:45.010 --> 00:11:57.060
Jirah Cox: locations, right which can be public clouds can be data centers can be your on-prem. But you need to empower the business that this is the Acme cloud right and it has legs, and all these various different availability zones. So we're we're saying same thing. I agree with you.
57
00:11:57.070 --> 00:12:22.959
Andy Whiteside: I I like that. Because now you're saying the cloud, don't think of that as from all the options. Think about the clouds or the you know the the overcast, or whatever. However, you want to say it, you know first of all for our listeners. If you don't know where cloud comes from, it's the idea. There's a bund. There's services that come from somewhere. You don't really understand what it is. Specifically, therefore, it guys drew it up as a on the whiteboard as a as a cup of this cloud quite often, and said, The stuff comes from there. You don't really know what it is exactly, but it comes from there.
58
00:12:22.970 --> 00:12:37.609
Andy Whiteside: Um! So Br. Did I do like your comment that for the consumer of it. It kind of needs to look like a cloud, even though it's made up of clouds, and at the end of the day it's their cloud story as an it leader like
59
00:12:37.620 --> 00:12:57.370
Jirah Cox: the you're empowering your business right? Your kind of parts and business units to solve problems with cloudy outcomes that we should be on Prem could be fully public cloud. It could be cloud native could be Nc: Two uh can be, you know, other Sas services like from data center hosting and so forth. Um, But at the other day that that all empowers you or one company's cloud
60
00:12:58.060 --> 00:13:16.489
Ben Rogers: this will be a two-part. That so, Bill. Then I want you to talk about the number. One thing, the application move. But tell me you were ahead, and you had a comment. Well, Yeah, I mean one of the things you said that I think is pointed to this whole conversation that gets lost in the in. The luck sometimes with it is about service delivery.
61
00:13:16.500 --> 00:13:21.820
Ben Rogers: So when you talk about you know where the services coming from, the users don't care about that,
62
00:13:21.830 --> 00:13:50.639
Ben Rogers: and most sea levels at times don't care about that. They want it to be able to deliver the services and deliver services on the man. The sla of the companies. That's where this multi-cloud hybrid cloud what I call our Newtonics foundation. That's where really this comes into play and where some of this also comes into play. Is we're in C two really hits a home for some businesses is that they don't have to retrain their employees if they know prison and they need to do tanks. This is just another leaf off of their
63
00:13:50.650 --> 00:13:57.760
Ben Rogers: their infrastructure. Their foundation is that that's kind of how I try to pay it to customers is that if you know, if you, if you
64
00:13:57.770 --> 00:14:13.010
Ben Rogers: consume our products, is to our portfolio, whether on-prem or in cloud, you they can get to a service delivery model, where it's A. It's your infrastructure behind the services that are being delivered to the company.
65
00:14:13.560 --> 00:14:15.970
Andy Whiteside: Yeah, I guess. Could you stop and think about it? You're
66
00:14:16.100 --> 00:14:33.820
Andy Whiteside: You're trying to get people out of the on-premises data center which makes a ton of sense when you look at a lot of different pieces of it. But you the customer. You don't want to just get stuck somewhere else. So if you can come up with a way that allows you to take advantage of the best to breed, maybe at the moment, at any point in time.
67
00:14:33.830 --> 00:14:37.990
Andy Whiteside: Then you're actually winning if you're just moving it from one place to another, and you got a new type of
68
00:14:38.050 --> 00:14:42.180
Andy Whiteside: um getting stuck in the mud? Then you have you really one
69
00:14:42.720 --> 00:14:56.860
Ben Rogers: like I've seen some customers that take their you know they're like for um. I came from health care so they they might have technical reasons why they didn't leave that emr on pre or close to a data center
70
00:14:56.870 --> 00:15:25.810
Ben Rogers: uh inside of the inside of the company's network, but they have. They might have remote sites that they could move those services off the cloud so that the cloud component is now their edge service that's now collapsing back to our on-prem data center for whatever their crown jewel application is. So we see some companies talking to us in that regard where they go. I've got all these sites across the world. I'd rather collapse these sites to edge service that runs in azure aws wherever the closest presence is.
71
00:15:25.820 --> 00:15:49.979
Ben Rogers: But I need to safeguard my application in my database is all pre for performance compliance, whatever the reason would be. That's where these models really get fit in, really well. And again, you don't have to retrain your staff man. They know the prism prison pro uh, all of those elements of our portfolio. They can extend this out to aws azure, and it's. It's the same environment.
72
00:15:50.860 --> 00:16:09.240
Andy Whiteside: So I won't. Go into this um the survey that was done by these seven hundred one thousand seven hundred it decision makers, and these three bullets, the three points they pull out. But, uh, I don't know if this is in the blog or not. Um, are we? What is what technically is in C two on azure?
73
00:16:10.150 --> 00:16:27.549
Harvey Green: Uh, I I will. I will give you the the I guess, the the Harvey definition here. Um it. It is all of the wonderful great things about mechanics that you've been experiencing on Prem and the ability to have that
74
00:16:27.560 --> 00:16:30.380
Harvey Green: for for this use case in azure
75
00:16:30.550 --> 00:16:50.249
Harvey Green: um bare bare miller blades in azure that they're providing their servicing, their hosting that Don't live in your data center. So you no longer worried about that hardware uh, but you still have all of the wonderful nice things and wonderful management of mechanics.
76
00:16:50.260 --> 00:17:07.100
Harvey Green: Uh that you are now using on hardware that is not hosted by you are are covered by you; that you have no responsibility over, uh, but you still have the ability to manage it, as as you have been managing your on pro.
77
00:17:07.109 --> 00:17:11.620
Andy Whiteside: So, Harvey, how is this any different than Zintegr for the past year and a half
78
00:17:11.810 --> 00:17:15.350
Andy Whiteside: hosting native Newtonics on our hardware in our data center,
79
00:17:15.500 --> 00:17:33.330
Harvey Green: let me say our two data centers that is gonna be the key. So it it's not different, because again, that that is a way that the customer isn't providing the support and the touch and the feel of all of that hardware we're providing it for them.
80
00:17:33.340 --> 00:17:39.099
Harvey Green: Um, it. It is just another place that you can do it.
81
00:17:39.870 --> 00:17:58.930
Andy Whiteside: But I set you up a little bit. I I was highlighting the number two. We actually have three. If you take the fact that we have a customer where we've rolled it out within the same colo as theirs. But that's three. What you get out of, you know. Doing this with an aws or azure is the the the public cloud scale of hardware in the smartness of the Newtonic software
82
00:17:59.030 --> 00:18:04.110
Andy Whiteside: to make it work here, there, and everywhere as needed without being unique and different.
83
00:18:05.270 --> 00:18:18.199
Harvey Green: Yeah, I mean It's It's more choice again, just more choice as a customer. Uh: as to where you want to put your data where you want your data to live, and who you want to take care of that hardware.
84
00:18:19.360 --> 00:18:43.330
Andy Whiteside: So let me go back to bin for number one here the first um graph that's there and then, Gyra for the next two, and I go back to Ben because he's been talking about application, refactoring and getting stuff in the cloud without having to totally rewrite it for at least six, if not twelve months with me. Been number one. It says ninety. One percent of the people surveyed uh, moved one or more applications to a new. It environment over the past twelve months.
85
00:18:43.340 --> 00:18:45.040
What does that mean for us?
86
00:18:45.120 --> 00:19:04.760
Ben Rogers: Well, I would. I would question whether That's refactoring, or whether they moved off to a sas-based application, so that their application get refactored from you know traditional on-prem. And now where that companies offering uh sa space. I see a lot of companies trying to get to a refactory mode. But really what I see is the limitation is talent,
87
00:19:04.870 --> 00:19:23.480
Ben Rogers: talent, and you know you and I discuss this privately, Man, there's there's not a lot of consulting firms that are out there that are, you know, looking at this in and helping customers refactor their applications. So companies are having to look at doing it internally, and and talent is, is Is that a premium right now,
88
00:19:23.780 --> 00:19:34.749
Andy Whiteside: and it's expensive like. It will tell that that's part of the big part of the expense. But the time and the expense associated with that to truly move it to like a sass at running on kubernetes on the back end
89
00:19:34.760 --> 00:19:45.759
Ben Rogers: well and and let's. Just also take You're doing this while you're also keeping the bus running. So some some companies are looking, you know. I'm gonna have to pull the set of people out of the daily operation.
90
00:19:45.770 --> 00:20:15.709
Ben Rogers: It put them this on this refactoring thing. And then this. You know all the Gyra, I think, said it best, man. The time it takes to refactor, and the time that it could take to get out to a cloud. Service like in C two is two totally different time factors. And the other thing we do see with this service is that some companies go. We want to refactor, but we need to have some kind of cloud presence, so we're not constantly having to go back on Prem to get the pieces that we need. And so they'll stand up these clusters, and then they'll, you know, re architect or
91
00:20:15.720 --> 00:20:23.020
Ben Rogers: uh, you know, basically. We analyze and reform at how they're doing things once they get the Nc. Two clusters up.
92
00:20:23.050 --> 00:20:29.380
Andy Whiteside: Yeah, I mean, you think about a world where they build that three-legged bar, slow, but one legs a little shorter or longer latency than the other. And
93
00:20:29.440 --> 00:20:46.419
Andy Whiteside: uh you might, as you know what What, How valuable is that? Really, It depends on how much you want to deal with the the shortcoming. Hey, gyra, This uh, says sixty four percent of the people survey expect to be operating in a multi cloud environment within one to three years. Um!
94
00:20:46.430 --> 00:20:50.960
Andy Whiteside: Help us understand what that means. And and do you think that means also there
95
00:20:51.160 --> 00:20:57.060
Andy Whiteside: private or semi-private co-load data center as one of those multi- options
96
00:20:57.880 --> 00:21:15.050
Jirah Cox: uh I think to the last part. Yeah, I think it's extremely likely. Very much so the the multi-class operating environment right within one to three years. I I agree with this uh strongly right I tell. I coach my customers. It really is an eventuality, right? As much as you can try to be um
97
00:21:15.240 --> 00:21:25.359
Jirah Cox: uh deterministic, and set expectations on the front end of like we're going to tightly align to cloud A, or cloud, B or cloud, c. And that's our strategy. Um
98
00:21:25.370 --> 00:21:54.670
Jirah Cox: and kernels just happen in this world, right? And the amount of things like companies. Healthy companies grow by acquisition, right for the for a large part. Acquisitions get messy real fast, right like we don't have to think very long about our customer lists, to think of customers that still have stuff that's on Platform X and Y and Z. That someone had great intentions to move one day. Um, but it just Hasn't happened yet. So so at the very least, acquisitions dni um as an M. And a activity are going to.
99
00:21:54.680 --> 00:22:01.510
Jirah Cox: There's some curve balls. Right? So how do we help simplify multi-cloud? Because it's probably going to happen to you sooner or later. Um
100
00:22:01.830 --> 00:22:21.059
Jirah Cox: to say these workloads. They're coming to us from azure. He's going to be those from ads. These are coming from you know an on-prem environment. Help make this part of our one unified cloud that that runs the business experience. Because to Ben's point, like talent, is such a constraint right like. Are you really going to be able to double or triple your skill, sets um on your team
101
00:22:21.070 --> 00:22:32.649
Jirah Cox: to avoid what's What's the alternative? Right? If you don't double the triple skill sets uh for everyone. Now you're back to having silos and specialists. And now I've slowed down velocity of change that I can manage in the organization.
102
00:22:33.560 --> 00:22:42.769
Andy Whiteside: How often are you guys under your meet with a lot of people? How do you see customers that have multi-public cloud initiatives either intentionally or unintentionally
103
00:22:43.280 --> 00:23:00.890
Jirah Cox: both right? I mean for some people. It it just happens right. Some business unit goes off and try something, and and it kind of sticks. Um, you know the the big umbrella, for all this is data. Has gravity right moving stuff around. It does happen a lot back to the first point. You know. Ninety- of people have moved the application between environments in the last twelve months,
104
00:23:00.900 --> 00:23:06.820
Jirah Cox: so that ability to say, I want this to to move from X to Y, from from from location A to location. B.
105
00:23:06.840 --> 00:23:17.929
Jirah Cox: People feel more empowered to to mandate that more and more. But data has gravity. Data has connectivity, right? Um latency as a thing in the real world. And so um,
106
00:23:18.130 --> 00:23:34.859
Jirah Cox: maybe let's say worst case scenario. Maybe it's a shadow. It thing. We found these vms in these in this environment. Now they're under our governance, but they're in this location. Maybe best case scenario could be a more strategic like. We want to use a best of breed service. This clouds great at Ai Ml: Therefore go put this work cloud workload over there,
107
00:23:34.870 --> 00:23:39.769
Jirah Cox: but still I have to federate it right. It's gonna be one part of my one acne cloud right?
108
00:23:40.040 --> 00:23:48.359
Andy Whiteside: The Java. I will stay with you because I mean you talked to a lot of enterprise customers. That last one eighty-three percent agree that a hybrid multi-cloud is ideal. Um,
109
00:23:49.450 --> 00:23:59.879
Andy Whiteside: i'm gonna ask that question as it relates to a public cloud, plus there to my private or private cloud. First, whether you believe that number is accurate, and then we'll expand that in a minute.
110
00:23:59.890 --> 00:24:14.650
Jirah Cox: The I would agree right that one hundred that. Um that the stat around uh agreeing that hybrid move cloud is ideal is is accurate, and I think that's even gonna grow right, because that's kind of the message is that Um
111
00:24:14.660 --> 00:24:21.530
Jirah Cox: is keeping your options open, right? We've done it since the history of mechanics, of supporting customer Choice of like. Where do you want to run's, workloads,
112
00:24:21.540 --> 00:24:36.519
Jirah Cox: and how do you plan to move them when you need to right? What are your What kind of choices can you make today that Don't lock out choices tomorrow like buying the wrong h back units that. Now I can't use my fancy their thermostats right like put these vms in in a certain cloud today, but when
113
00:24:36.870 --> 00:24:55.469
Jirah Cox: call it any circumstance changes right, whether it's economic, financial um strategic alliances um, even like bordering on like political or Pr. Reasons right like we don't want to use this cloud anymore for perception. X: Right? Um. I was. I was with the buddy a couple of weeks ago, who who supports our Fed customers right?
114
00:24:55.480 --> 00:25:11.910
Jirah Cox: And he mentioned about a certain cloud that, like didn't quote didn't support war fighters right. It was like their stance of like. We don't want to do that anymore. So if you were in that industry and using that cloud, you'd want to move your workloads Well, how would you move a cloud? Native Vm. Workload if you had gone all in?
115
00:25:11.920 --> 00:25:26.999
Jirah Cox: And Nc. Two has the answer for that is to say, Nc. Two is the same Newton that you run on Prem, or in any cloud that we support today. And of course this podcast is happy to say that it's it's in. That includes azure today. Workload mobility when there's a need for it. Isn't valuable.
116
00:25:27.530 --> 00:25:32.409
Andy Whiteside: Yeah, I mean to the point of some type of even live migration without downtime at all
117
00:25:32.430 --> 00:25:34.780
Andy Whiteside: would be a future state potentially
118
00:25:34.790 --> 00:25:53.650
Jirah Cox: potential. Yeah, I mean, latency is still a thing. Walls of physics still apply. Um, and depending on your source and target. Of course I'm going to go to the engineering. It depends. Answer. If you're ever crossing hypervisors right changing from my prize, or, you know, like going from be sphere to a Hv. That's a not, an that's not a no downtime Approach right. You can't change hypervisors with a no downtime live migration.
119
00:25:53.820 --> 00:26:10.409
Andy Whiteside: So I think you were touch on this. But let me change the the the statements last question uh, so one thousand seven hundred it. Decision Makers agree that multi public cloud, public cloud multi-cloud public cloud, a multi cloud is ideal
120
00:26:10.420 --> 00:26:20.959
Andy Whiteside: for example you've got gcp and azure. You've got azure and aws. You've got Gcp as you're in aws, and your Covid nineteen workloads throughout those three. Do you think that number is that high?
121
00:26:22.810 --> 00:26:32.490
Jirah Cox: I? I I have very few customers that are in all three major public clouds. Usually it's. Usually it's on prem in one cloud or on prem with it. Most kind of two clouds looking for integration.
122
00:26:33.500 --> 00:26:43.269
Andy Whiteside: I I bring that up because I've kinda from, you know, Guys doesn't have to implement stuff every day or maintain it or maintain relationships with you. Public cloud vendors. At the same time,
123
00:26:43.280 --> 00:27:02.880
Andy Whiteside: the idea that you could put some workloads in one and one some of the other, and if somebody starts to treat you badly or change their political views or raise the rates, you can just start ramping up the other one, and it's all because you decided not necessarily that you were in different uh resource zones within one public cloud. You were literally in two public clouds,
124
00:27:02.890 --> 00:27:10.369
Andy Whiteside: and one going down didn't kill you, and and one changing their, you know political mindset didn't impact you either. You were ready to,
125
00:27:10.380 --> 00:27:28.629
Jirah Cox: you know. Turn it up on the other side one hundred, I mean. Think of how many customers we have today that we all call on that talk about implementing a multi vendor strategy for the purposes of keeping everybody honest, keeping pricing healthy um keeping, you know the the sword sharp from a a talent and staffing perspective right keeping their options open. Um.
126
00:27:28.640 --> 00:27:50.689
Jirah Cox: You know. Nc. Two brings that ability to implement a multi- vendor strategy with simplicity. Right with sanity to the whole process to public clouds right there's no there's no native azure way to deploy like an av usbm or an aws way to deploy azure. Vm that there's a pretty big moat there right. But that overall Federal Federation. Uh federating. There we go. Layer
127
00:27:50.700 --> 00:27:52.889
Jirah Cox: is what is what brings that sanity?
128
00:27:53.770 --> 00:28:05.769
Andy Whiteside: And and I want to move away from this, but I just can't help but keep asking the questions. Do you think it's eighty-three? Think a multi um multi-public cloud is the way they're gonna go and be able to handle those scenarios and more.
129
00:28:07.000 --> 00:28:08.270
Jirah Cox: Um,
130
00:28:08.310 --> 00:28:15.670
Jirah Cox: I mean, we're all we all work for a company here uh doing this host email in any cloud other than azure.
131
00:28:16.690 --> 00:28:20.320
Andy Whiteside: Uh. Well, we just did a joint venture with the company. Does zimbra. So we
132
00:28:20.330 --> 00:28:42.270
Andy Whiteside: But no, I mean emails that one thing. It's it's gonna be an azure period. Um, I guess what you're saying if if you choose to do Aws for one application, and you've got your email and azure because it's a sass base solution, not an I ass solution you're you're technically multi-cloud we we we all use salesforce on this. Call that doesn't run an azure.
133
00:28:42.540 --> 00:28:43.470
Andy Whiteside: Yeah,
134
00:28:43.780 --> 00:28:54.190
Andy Whiteside: that's what you're saying. You won't have a choice. It's going to happen and it's going to be application driven in many cases. I guess I'm really focusing on it. It's not your fault, but it is your problem for a lot of a lot of decision makers.
135
00:28:54.250 --> 00:29:00.170
Andy Whiteside: Yeah, i'm just looking at it from an I as perspective. Do you think like, if we ask that question differently? Do you think um
136
00:29:00.180 --> 00:29:20.299
Jirah Cox: from an Is perspective? Your average or eighty-three percent of people surveyed would say, Yeah, we're gonna have two public clouds. Or are they really saying i'm gonna have my data center or my partner data center? And i'm gonna have a call That's hybrid. Well, So remember that that is the definition right? That that applies here right like on-prem plus public cloud that operates as one seamless
137
00:29:20.310 --> 00:29:25.720
Jirah Cox: customer. Cloud equals hyper multi-cloud. Right? So so I think that's that's
138
00:29:25.730 --> 00:29:42.810
Jirah Cox: partly one boat anchor, if that's the right analogy right is like You've got huge data on Prem. Probably that may might not be a good citizen for a cloud migration right if you have the you know, this talks to the mainframe. Mainframe lives on prem or losing a colo um. But next Gen. Stuff wants to run into the cloud,
139
00:29:42.820 --> 00:29:46.810
Jirah Cox: make this all fit and make it, my cloud. Well, that's that's your hybrid multi Cloud.
140
00:29:46.960 --> 00:29:47.880
Yeah.
141
00:29:48.520 --> 00:30:00.430
Andy Whiteside: And the whole point in this offering from um, you know mechanics around in C two on azure and aws previously. Also, as well as you know, my data center. Their data center means it.
142
00:30:00.560 --> 00:30:04.079
Andy Whiteside: It's all doable when the time comes because it's software-driven not
143
00:30:04.570 --> 00:30:10.870
Andy Whiteside: not locked into physical hardware forever, then did bring up that commitment thing, and I don't know if we'll get back to that at some point in this, but
144
00:30:10.910 --> 00:30:26.100
Andy Whiteside: the the commitment is might as well be locked into the hardware. If you've made that commitment you probably won't do it again. I don't think but that's how they the public cloud guys are trying to drive your decisions around.
145
00:30:26.150 --> 00:30:32.460
Jirah Cox: Everybody on the call has a mortgage, but here is also used in Airbnb: right length of stay affects the choices you make.
146
00:30:32.560 --> 00:30:33.450
Andy Whiteside: Yeah.
147
00:30:33.980 --> 00:30:38.849
Andy Whiteside: Well, me, I I've got the house i'm in. Now what five years? I had three mortgages,
148
00:30:39.280 --> 00:30:42.370
Andy Whiteside: so that makes it attractive enough. I'll talk to him about it.
149
00:30:42.750 --> 00:30:50.899
Jirah Cox: So yeah, right, you know, when when the right person knocks and offers the right number right, keeping your options open, and having that agility. That mobility is, uh, you know,
150
00:30:51.640 --> 00:31:10.560
Jirah Cox: from a new tennis perspective I just had never unpack. I should leave it in those virtual containers, and then be ready to go.
151
00:31:10.570 --> 00:31:13.170
Jirah Cox: Yeah, there you go. I'll call marketing now.
152
00:31:13.230 --> 00:31:41.880
Ben Rogers: Uh, I hate to bring dollars and cents into this, but you know sometimes it's a matter like we're. We're talking to a company right now that they don't want to do the capital expenditure to have any more on they. They want to move this to an optics model and spread the cost out over time, not have to come out with the capital. They also want to get better density. So you know some of our customers with jar. I'm almost positive. Or this is
153
00:31:41.890 --> 00:32:08.329
Ben Rogers: why would I want to use mechanics and azure. Why would I just go natively in azure? And one of the things that we can do is we can get more density on our hardware, because we're controlling our hardware in a native as your environment. You might be a tenant on a host that other tenants are running on in our Nc. Two clusters. When you know that that hardware is dedicated to your function, and we can also get better density on our hardware because of our software. Driven platform.
154
00:32:08.340 --> 00:32:13.159
Ben Rogers: So a lot of times it might come to. I've got a fork out of a bunch of cash,
155
00:32:13.170 --> 00:32:36.780
Ben Rogers: or I can go to an opex model and still control my destiny and get the density. I need out the hardware in a public cloud environment. And so we see a lot of customers that are starting to look at those possibilities of. You know I have the hardware. I control the environment. It's in that. It's in a as I environment cloud, but I still retain some of the ownership of that that that infrastructure,
156
00:32:36.790 --> 00:32:53.719
Jirah Cox: I mean. I was on a call before this one with a a teammate who showed me some financial models. He'd worked up for his customer with only three hundred vms. So not a enormous environment right on the large side, but Not that we all seem. We all seem bigger. We all seem smaller. Um, but pretty average,
157
00:32:53.730 --> 00:32:58.330
Jirah Cox: with only three hundred Vms and Nc. Two proposal was saving them fifty percent per year
158
00:32:58.340 --> 00:33:23.209
Jirah Cox: every single year, right like you could pay double and have native vms, or you could pay half as much and run those Vms. On new tanks on bare metal in public cloud. So to your point, Ben spot on like there's there's that break even point that you hit, because you know. Of course it's That's the name of the game, right when you're a cloud provider. You're charging for every Vm. From Vm. One thousand and one. There's no freebies, right, whereas you pay for the nodes. You control your density.
159
00:33:23.220 --> 00:33:36.479
Jirah Cox: And by the way, you get more performance, anyway, right? Because cloud is pay for provisioning. Pay again for performance right? Oh, you want that storage tier. Oh, you want what generation of uh of intel host are on that Vm: Right swip your card again. Um.
160
00:33:36.510 --> 00:33:48.840
Jirah Cox: Whereas natively here, right, no one's questioning the performance of Antennas right. We all have customers that have blindingly fast clusters that run their workloads. That same tech comes to bare metal loads into the cloud. And now it runs your cloud bms as well.
161
00:33:50.280 --> 00:34:07.359
Harvey Green: Yeah, I think that hits on Another important point, too. Um, that that's another big advantage is when you're in public. Cloud is using virtual machine instances. There you use the sizes that they've already picked and prescribed for you.
162
00:34:07.430 --> 00:34:18.149
Harvey Green: Uh, and if you decide you want to go up to something different, then you to to Driver's Point, swept your credit card again, and you can do that. That's great.
163
00:34:18.159 --> 00:34:38.019
Harvey Green: Um. But with Nc. Two you're able to just resize your Bm. The same as you would uh on pro and then continue moving on and and not end up paying more to do that or be stuck doing it with pre-planned or pre-prescribed uh virtual machine instant sizes.
164
00:34:40.260 --> 00:35:04.930
Jirah Cox: Yeah, I mean, we can all think of customers right that we've advised in the past. Hey? This over over provision right? Doesn't need this much memory this much. Cpu uh you could. You could shrink that down, and they kind of look at you and go. Yeah, I know that. But if I try to make that smaller. Someone else yells at me uh right. That's a That's a political decision, not a technical decision. Uh well, now, imagine you're paying per gig paying per v cpu every month. Uh, when does that get fun? Right?
165
00:35:05.310 --> 00:35:25.379
Jirah Cox: It It it makes sense to optimize, for well, like I want to run these vms if I can't really sh them that shrink them down right, whether it's political or with a vendor, dictates the vms to be the size, efficiency matters right. You get way. More efficiency uh being in control of those Vms like you are now, but on a platform, your choice, like in a public cloud Provider. Absolutely.
166
00:35:26.000 --> 00:35:46.400
Andy Whiteside: So, So, guys, this is going to be two or three parts to cover this whole that we're gonna have seventy conversations we have uh. So Phillips on with us those sellers again first day as integr. But I want to bring him into the conversation because uh a week ago last Friday. Maybe he might have left sooner than that. But uh, basically a week ago he ran an infrastructure team for a customer here in the Charlotte area.
167
00:35:46.410 --> 00:35:58.450
Andy Whiteside: So this conversation we've been having. Um, does it as a customer? What you were? Um, you know, three days ago. Um! Does this make sense? Is our Oh, this is this logic real or this made up numbers.
168
00:35:58.760 --> 00:36:08.820
Phil: I I don't know about these particular numbers, but I will say the logic sound um. You know one of the things that I haven't heard kind of discussed so far is
169
00:36:08.830 --> 00:36:24.639
Phil: uh best in breed services. You know. Each one of these Cloud providers is also doing their own research into things like Ml. And Ai and other differentiated services. So not all clouds are created equal. You're gonna find some services. You may want to consume
170
00:36:24.650 --> 00:36:29.100
Phil: uh out of one, and and you know a competing service out of another.
171
00:36:29.110 --> 00:36:47.449
Phil: Well, and then you need your data next to it to to make that useful. So how do you get your data there? Well, in C, too, gives you a a really viable way of either replicating your data uh into that cloud of your choice to consume it with the service of your choice.
172
00:36:47.460 --> 00:37:02.520
Phil: Um, you know it. It kind of gets back to what jar is saying. I mean you. You have uh unlocked, you know, a a multitude of choices here for you, your your business to choose whatever they need to to get the job done.
173
00:37:02.530 --> 00:37:21.850
Phil: Uh, and so I think that's that's the value that it ultimately brings to the table. Um, you know we were a merger and acquisition heavy company. So we had a little bit of this a little bit of that. So uh I I will second that comment that was made earlier. Uh, that certainly grows from multi cloud footprint,
174
00:37:21.860 --> 00:37:42.649
Phil: Um, you know, certainly had a lot of different Sas platforms. Um! And at the end of the day as a customer. I don't care, you know who's on the back end for salesforce, unless there's a global you know, outage affecting salesforce, and it's down for me, and and then, you know, I I may actually care who their service provider was. But
175
00:37:42.660 --> 00:38:02.250
Phil: it it's about the outcomes at the end of the day. You know, we we want an email provider because none of us really want to to run email. Um, We want, you know, whatever service or software is being provisioned uh for us, and we just wanted available at the end of the day. Um, you know, when when it comes to Sas
176
00:38:02.470 --> 00:38:13.699
Phil: infrastructure certainly changes that that conversation I think um a a to a greater degree. But um! I love that. Jere called out the whole
177
00:38:13.780 --> 00:38:32.630
Phil: cots software because so much of the world is still uh on traditional client server software, and they don't have a choice um and their vendors aren't rushing out to create a Sas platform to switch them to um, and that's still. I think
178
00:38:32.640 --> 00:38:37.699
Phil: I would love to see that metric. I'd love to know how many customers
179
00:38:37.790 --> 00:38:41.149
Phil: software portfolio is, you know
180
00:38:41.510 --> 00:39:01.010
Jirah Cox: what percentage of cot software I think that has a lot to do with with this sort of solution. And why it's more viable for customers. Yeah, it's It's one of my leading questions, usually for for meeting a new customer is like that percentage, because it helps contextualize like. So what kind of autonomy. Do you really have what options are really open to you? Um.
181
00:39:01.020 --> 00:39:06.649
Jirah Cox: Only correction, Phil. Welcome to the show Is Andy is interested in running email servers right, he said. Zebra, he's waving that flag.
182
00:39:10.500 --> 00:39:23.950
Jirah Cox: So I I got a guy. Yeah, I I think we all got a guy that that makes perfect sense. I've been that guy. I like doing this more.
183
00:39:24.240 --> 00:39:35.659
Andy Whiteside: But I got a guy I got a I got a guy with a team of guys that actually like doing that stuff. So it brings into our options. Hey, guys, we're out of time uh It's Halloween. Ben's got a bunch of little kids. He's got to go decorate.
184
00:39:36.130 --> 00:39:37.919
Harvey Green: Wait what
185
00:39:39.330 --> 00:39:59.540
Ben Rogers: these are my grandkids and my Mike will be face painting. I mean Daniel Congrats on Halloween Mask. That is really scary. Good good try. I didn't want to. I do want to step on something that you know one of the things when you talk about being able to.
186
00:39:59.550 --> 00:40:07.910
Ben Rogers: You know it uh interact with native cloud services. We do have some customers that would like to end up in like a containerization environment
187
00:40:07.920 --> 00:40:31.810
Ben Rogers: that again, they move this stuff into Nc. Two, and then they start to refactor it. For whether that be now, we would love for them to go on our containerization uh technology and keep it all within our clusters. But we do have some customers that are looking at a school. Once I get out to these clouds, How can I interact with the data services? And that is one part of the service that I assume we'll discuss in our next meeting guys.
188
00:40:31.980 --> 00:40:49.879
Harvey Green: I was going to say you might have to make a bookmark of that. And then when we start in the next one, i'm going to ask you for that bookmark, because i'm not going to remember. I might. I'm going to ask you about a bookmark. Let's see what happens. Same thatat channel. That's all right,
189
00:40:49.890 --> 00:40:56.779
Harvey Green: All right. Thanks, guys, for coming on with us, and we will see you that. Oh, my gosh, I I tell you
190
00:41:02.400 --> 00:41:10.160
Andy Whiteside: sorry, guys, this couldn't help but do it. This has been my Halloween costing for the last two weekends. I've been the phone my wife has been digging.
191
00:41:10.460 --> 00:41:12.879
Andy Whiteside: We had to go with something. We go as together.
192
00:41:12.930 --> 00:41:19.629
Andy Whiteside: Um, you know, I could actually wear this tonight, and probably scare the heck of a lot of little kids that apparently cover the frog is turned into
193
00:41:20.050 --> 00:41:21.909
Andy Whiteside: kind of an intimidating figure.
194
00:41:22.110 --> 00:41:36.499
Harvey Green: If you're uh one of our beloved audio, only listeners uh pull over safely. And uh, they got the video recording of this one,
195
00:41:36.540 --> 00:41:46.110
Harvey Green: we should have done that we should have dressed up. Oh, i'm just not that creative. Next year we're going to dress up.
196
00:41:50.590 --> 00:42:10.230
Andy Whiteside: We can move it, we can move it. Somebody remind me. I said, this All right, guys. Well, thank you, and we'll do again. I assume it's going to be two or three of these episodes to get through this topic. It's a big topic, and uh Gyra finally got it done. He's up at night right in the code.
197
00:42:10.750 --> 00:42:12.440
Andy Whiteside: All right, guys. We'll see you next week.
198
00:42:13.090 --> 00:42:14.559
Harvey Green: See it?
199
00:42:15.160 --> 00:42:16.910
Ben Rogers: Oh, that was classic.