We're pleased to announce that the Approval Policies feature is now available in Tech Preview for the Nutanix Cloud Manager™ (NCM) Self-Service.
NCM Self-Service (formerly Calm) provides an easy and seamless way to consume simple Infrastructure as a Service VMs and multi-tier applications via the marketplace[JG1] . This is possible via easy to use blueprints to automate complex application deployment processes. As NCM Self-Service continues to grow its footprint across enterprise deployments, customers have remarked on the need for even better governance and controls on resources provisioned and managed. Governance is key to building a cloud-like experience for IT organizations, and the ability to easily define and monitor policies are important for enterprise customers.
Host: Harvey Green
Co-host: Jirah Cox
We're pleased to announce that the Approval Policies feature is now available in Tech Preview for the Nutanix Cloud Manager™ (NCM) Self-Service.
NCM Self-Service (formerly Calm) provides an easy and seamless way to consume simple Infrastructure as a Service VMs and multi-tier applications via the marketplace[JG1] . This is possible via easy to use blueprints to automate complex application deployment processes. As NCM Self-Service continues to grow its footprint across enterprise deployments, customers have remarked on the need for even better governance and controls on resources provisioned and managed. Governance is key to building a cloud-like experience for IT organizations, and the ability to easily define and monitor policies are important for enterprise customers.
Host: Harvey Green
Co-host: Jirah Cox
WEBVTT
1
00:00:03.480 --> 00:00:16.260
Harvey Green: hi everybody thanks for joining us and welcome to episode 56 of the metallics weekly podcast I have with me a couple of my co host Mr john Cox, how are you today, sir.
2
00:00:16.410 --> 00:00:19.110
Jirah Cox: Man, the big five, six, I said we couldn't get here, we got there.
3
00:00:20.670 --> 00:00:21.300
Harvey Green: Right.
4
00:00:22.860 --> 00:00:24.480
Harvey Green: Mr Rogers how are you, sir.
5
00:00:24.930 --> 00:00:26.970
Ben Rogers: i'm doing great Harvey i'm glad to be here today.
6
00:00:27.540 --> 00:00:31.860
Harvey Green: Wonderful I was just telling the guys right before I got on here.
7
00:00:33.450 --> 00:00:44.580
Harvey Green: That, for whatever reason, my mind left me and I couldn't remember the key combination to zoom in a browser I was right before this I was working on.
8
00:00:45.300 --> 00:01:02.520
Harvey Green: A report that I have to do and that don't like doing reports and all of that working in excel and go looking up 10 things for one line when I have to do, multiple line items so that was fine and it apparently rocked my brain just a little bit.
9
00:01:03.900 --> 00:01:05.940
Jirah Cox: hey it sounds like you need a pivot table there.
10
00:01:07.110 --> 00:01:09.510
Harvey Green: yeah, it is a pivot table, but i'm having to.
11
00:01:09.510 --> 00:01:11.250
Harvey Green: fill in all of the information.
12
00:01:13.980 --> 00:01:22.080
Jirah Cox: And if you're listening this podcast it's control plus control minus under keyboard there, so if you learn nothing else today we've been evaluating as a tech podcast.
13
00:01:24.540 --> 00:01:25.530
Harvey Green: So yeah yeah.
14
00:01:26.550 --> 00:01:30.330
Harvey Green: that's that's my daily doses feeling silly I guess.
15
00:01:30.840 --> 00:01:33.660
Jirah Cox: Oh good you're you're up you're up you're like a manager now it's right so just.
16
00:01:35.040 --> 00:01:36.060
Jirah Cox: move on up the food chain.
17
00:01:39.030 --> 00:01:43.980
Harvey Green: i'm gonna let that one go I don't even want to consider the implications behind.
18
00:01:47.430 --> 00:01:57.810
Harvey Green: today's topic is approval policies in ncs which we'll get to in a minute ncs of service that's now available as a tech preview.
19
00:01:58.980 --> 00:02:04.200
Harvey Green: Will will stick it out, so you both who wants to be first to the fire within cms.
20
00:02:05.040 --> 00:02:15.450
Jirah Cox: and see him as the new tannic cloud manager it's kind of the artist formerly known as prison pro within prison central step for doing more automation orchestration activities.
21
00:02:16.500 --> 00:02:20.850
Jirah Cox: Within prison central right I get across your multi cluster manager there with npc.
22
00:02:23.130 --> 00:02:23.400
Jirah Cox: yeah.
23
00:02:23.580 --> 00:02:36.210
Jirah Cox: And this blog post comes to us from the the Community blog next calm proving once again to be all killer no filler This is where the the real techie stuff gets published and it's awesome.
24
00:02:37.650 --> 00:02:43.590
Jirah Cox: This is pretty cool we've talked before right about automation and these are self service.
25
00:02:44.220 --> 00:02:45.390
Jirah Cox: We love good automation right.
26
00:02:46.740 --> 00:02:47.940
Harvey Green: Never talked about that.
27
00:02:49.320 --> 00:02:50.190
Jirah Cox: Bad automation.
28
00:02:50.700 --> 00:02:52.230
Jirah Cox: automating the right things.
29
00:02:53.250 --> 00:02:56.340
Harvey Green: With Andy see I haven't booked him.
30
00:02:56.880 --> 00:02:58.710
Jirah Cox: With us with us in spirit today.
31
00:02:58.920 --> 00:02:59.220
Right.
32
00:03:00.750 --> 00:03:04.500
Jirah Cox: But, of course, and all kinds of fun things you can do within the tactics.
33
00:03:05.730 --> 00:03:16.560
Jirah Cox: Self service automation you know you can do quote, as you know, this user or this team can consume or deploy X amount of V cpus or y amount of memory or disk storage.
34
00:03:17.790 --> 00:03:21.120
Jirah Cox: But even if you have those kind of guard rails setup in place.
35
00:03:22.230 --> 00:03:27.570
Jirah Cox: You still might not want some people to have full autonomy to do certain actions let's say.
36
00:03:28.380 --> 00:03:36.000
Jirah Cox: Whether it's a vm deployment, I can picture our use case for an in guest installation right, if you want licensed software, you know, maybe.
37
00:03:36.360 --> 00:03:48.360
Jirah Cox: salon sequel or adobe pro so thing I think it is inside of your your virtual machine, maybe you need to go get approval right for a license consumption before you go do that deployment, so we wouldn't want to give.
38
00:03:48.960 --> 00:03:55.380
Jirah Cox: Everybody full rights to do that automation you know soup to NUTS right and end autonomously.
39
00:03:56.070 --> 00:03:57.000
Jirah Cox: So this is a.
40
00:03:57.240 --> 00:03:59.040
Jirah Cox: new feature here that is actually gonna let.
41
00:04:00.330 --> 00:04:11.580
Jirah Cox: Customers use us new tannic automation but then for certain trigger certain actions certain thresholds that you can set require approval before that that automation will complete.
42
00:04:12.270 --> 00:04:14.610
Ben Rogers: So Tyler, can I ask a question about this and i'm.
43
00:04:15.750 --> 00:04:21.810
Ben Rogers: always put on my customer hat, so I used to manage an IT team, and my it team had various skill sets.
44
00:04:22.230 --> 00:04:28.770
Ben Rogers: With this system, allow me to say hey i've got a junior engineer that's building out some vdi for me.
45
00:04:29.130 --> 00:04:41.370
Ben Rogers: And if he reaches a certain threshold where it looks like he's going to take X amount of capacity from the system, I didn't want that to be approved by somebody above him is that, where this product to kind of fit into play.
46
00:04:41.730 --> 00:04:43.350
Jirah Cox: yeah seems like a great great use case.
47
00:04:44.640 --> 00:04:48.750
Jirah Cox: The blog post walks through a couple of examples like that right we're like in this example, they give.
48
00:04:49.200 --> 00:04:58.380
Jirah Cox: Is if you're deploying it and it contains prod PR OD so you're playing a prod application and it's going to get more than, say, in this case 10 gigs of memory.
49
00:04:58.770 --> 00:05:06.000
Jirah Cox: require an approval right like get a sign off on that kind of action so again that's a that's both an environmental or I should have vm naming.
50
00:05:07.260 --> 00:05:11.820
Jirah Cox: check combined with to your point Ben hey consumption above a certain threshold check.
51
00:05:12.630 --> 00:05:23.700
Ben Rogers: see that is awesome because that was one of my kind of fears as a manager is I didn't want to pigeonhole my employees and go I don't want you to do this because of risk to the system.
52
00:05:24.120 --> 00:05:33.180
Ben Rogers: But at the same time, I did get called a couple of times for engineers got a little bit too ahead of themselves and it caused problems with the system from a capacity standpoint.
53
00:05:33.510 --> 00:05:41.160
Ben Rogers: or a performance standpoint, instead of kind of have this safeguard at an administrative level that's huge right he managed to my opinion.
54
00:05:41.730 --> 00:05:53.040
Ben Rogers: And can really give us a good sits up, I can allow my engineers to get into the environment, but I can also percent some protective guardrails that don't allow them to overtake the bar.
55
00:05:53.700 --> 00:06:04.590
Jirah Cox: Totally yeah so so and then to that use case, could you imagine, did you need to approve everything or were there more senior folks on your team, who also could have served as an improver.
56
00:06:05.340 --> 00:06:15.120
Ben Rogers: Well Harvey knows the answer to that I had one or two gentlemen and females that that would you know those requests would get bumped to them and then they would have the skill set to look at that.
57
00:06:15.330 --> 00:06:23.790
Ben Rogers: 30,000 foot view to go this is going to work, this is not going to work and then ultimately if there was a question, they would come to me, but I didn't I wouldn't want to burden.
58
00:06:24.120 --> 00:06:33.060
Ben Rogers: You know somebody at my capacity at that time you know, a director level dealing with things like this i'd rather that be, you know my infrastructure manager or somebody like that.
59
00:06:33.390 --> 00:06:40.950
Ben Rogers: it's just if the hits the fan that's when it's coming to me and half the time i'm doing something administrative going what.
60
00:06:41.400 --> 00:06:53.580
Ben Rogers: And so, when I read this article today that was one of the first things that came to my mind was, this is a way for me to limit what junior engineers could do, and to get senior engineers that they got to a dangerous.
61
00:06:54.180 --> 00:07:02.760
Jirah Cox: Totally totally right, and so what I think is cool here is is, you could have really any kind of held up group you wanted to create any kind of ad group you wanted to create.
62
00:07:03.120 --> 00:07:07.680
Jirah Cox: As a previous for that action right so doesn't that doesn't just need to be you as the funnel you know people manager.
63
00:07:08.040 --> 00:07:18.840
Jirah Cox: It could be anybody more senior as a lot to prove this action right and they could come to those people first, if they're all out, you know, on pto then they can come bug you a sort of a approval of last resort, if you will.
64
00:07:19.740 --> 00:07:33.780
Ben Rogers: Now, right now, our conversations been solely with you know hardware resources, but also see where this thing can help us out in an application level, can you describe some of that, for me, or I might be getting a little ahead of ourselves, I apologize.
65
00:07:34.560 --> 00:07:35.220
Jirah Cox: No, no, no.
66
00:07:35.550 --> 00:07:41.100
Jirah Cox: So we can we can walk through it there's there's gonna be basically three sections to configuring this kind of approvals.
67
00:07:41.610 --> 00:07:50.100
Jirah Cox: Within within the mdm self service, so the first one is going to be picking your you know entity type right like an application right which does.
68
00:07:50.580 --> 00:07:55.620
Jirah Cox: can include a virtual machine right that can you know, whatever your blueprint can contain one vm multiple vm.
69
00:07:56.490 --> 00:07:59.730
Jirah Cox: can call out to containerized environments do container launches as well.
70
00:08:00.360 --> 00:08:05.970
Jirah Cox: And then, what kind of action right so you're actually defining window I want this requirement for an approval to trigger and it's like.
71
00:08:06.210 --> 00:08:14.430
Jirah Cox: This type of thing doing this type of action, like the screenshots here so like launching right, so I want to launch this blueprint, which is basically considered a deployment.
72
00:08:16.410 --> 00:08:30.480
Jirah Cox: And then you know once once the system filtering on what things my watching for to then go get go and get an approval for when Do I need to go bug somebody right, what are the thresholds, like in this case, for example, of memory above 10 gigs so so yeah that can be.
73
00:08:31.650 --> 00:08:42.510
Jirah Cox: A launch action I can imagine that being like a day to action like software deployment or a vm scale out or a grow a vm in size type operation so.
74
00:08:43.530 --> 00:08:56.970
Jirah Cox: I don't have the exhaustive list of what this could trigger, but I can imagine it's pretty broad it's tied into self service at a very, very deep level, so we can catch just about any action and then route that to whoever needs to be the right kind of approval for that action.
75
00:08:57.780 --> 00:09:04.170
Ben Rogers: Now let me ask you this, and Harvey I I don't want to dominate the conversation here, but this help with rogue it.
76
00:09:05.280 --> 00:09:06.030
Jirah Cox: hmm.
77
00:09:08.670 --> 00:09:10.920
Jirah Cox: Go ahead and lead the witness there been how could that help with rogue.
78
00:09:10.920 --> 00:09:11.220
It.
79
00:09:13.440 --> 00:09:19.020
Ben Rogers: What i'm thinking is you know i've got a database administrator that is tired of asking for.
80
00:09:19.410 --> 00:09:31.740
Ben Rogers: You know database sizes and the gods want to go and create a massive database engine and and so i'm thinking you know, again, how can I continue to the developers in my department to keep them from over running our resources.
81
00:09:32.580 --> 00:09:37.320
Jirah Cox: Oh yeah okay i'm see that for sure yeah I can I can see a lot of good functionality, there are a lot of usefulness.
82
00:09:39.990 --> 00:09:49.440
Harvey Green: Alright i'm going to go all the way back just a little bit because you gentlemen just got extremely excited about what we're doing we forgot to.
83
00:09:50.250 --> 00:10:04.740
Harvey Green: Define one more thing, so we talked about attacks cloud manager, we also have in here in cm self service and it says, formerly called is Does that mean somebody agitated it or what what is, what do they mean formerly call.
84
00:10:04.920 --> 00:10:05.520
wow.
85
00:10:07.680 --> 00:10:08.670
Jirah Cox: What a way to end the Monday.
86
00:10:11.910 --> 00:10:16.680
Jirah Cox: yeah i'll let i'll let i'll let marketing know the game a suggestion there they can call it agitated and right.
87
00:10:18.090 --> 00:10:19.620
Jirah Cox: we'll leave it up to leave it for them to run with that.
88
00:10:20.820 --> 00:10:23.130
Jirah Cox: know for sure we give it coffee.
89
00:10:24.870 --> 00:10:35.400
Jirah Cox: For sure, but uh but yeah so totally are rebranding here from if you've heard of calm before that's we're talking about now in nc am self service right so anywhere that you've heard of say.
90
00:10:35.760 --> 00:10:49.440
Jirah Cox: Calm for automation application blueprints vm deployments day zero day one day two operations, all things that that calm used to play in now and cm self service does still play in yes.
91
00:10:49.530 --> 00:10:53.520
Ben Rogers: Okay, so let me, let me as a new tannic new employee.
92
00:10:54.930 --> 00:11:08.520
Ben Rogers: Let me get it right now so new tonics cloud manager was the artist formerly known as prism crow and new talents cloud manager self service is the artist formerly known as car.
93
00:11:08.880 --> 00:11:11.130
Ben Rogers: yep okay so.
94
00:11:11.460 --> 00:11:14.970
Jirah Cox: We probably have maybe not finished updating all of your new hire training videos.
95
00:11:16.710 --> 00:11:18.780
Jirah Cox: If I have to you have a probably a foot in both camps.
96
00:11:19.350 --> 00:11:27.240
Ben Rogers: so well in some of our DEMO environments, you still see some of the old names too so i've been in our DEMO environment a lot this morning, this afternoon.
97
00:11:27.570 --> 00:11:31.680
Ben Rogers: And said when I got this article I was, like all right, let me step back, I know prison.
98
00:11:32.340 --> 00:11:48.000
Ben Rogers: is now in cm but the inseam self services COM kind of threw me for a little bit because I was, like all right is this being built in the pro and i'm missing something, and when you're drinking from the firehose sometimes things go past year, like wait a minute I should stop look.
99
00:11:49.170 --> 00:11:51.660
Jirah Cox: Totally fair right good good to certainly connect all the dots.
100
00:11:52.170 --> 00:11:58.830
Jirah Cox: I said earlier, you know and i'm still not going to read people the exhaustive list of what all this can do, but I did click into it the blog post links to.
101
00:11:59.190 --> 00:12:03.390
Jirah Cox: Our documentation about, but what kind of thresholds that can be used to said we're going to operations.
102
00:12:03.870 --> 00:12:12.090
Jirah Cox: And it's honestly genuinely pretty impressive I love it like so let's let's take a step back a number that you know calm now and cm self service.
103
00:12:12.480 --> 00:12:19.140
Jirah Cox: is so multilingual right it's a write your application wants deploy to HP environments V sphere environments.
104
00:12:20.100 --> 00:12:27.690
Jirah Cox: aws azure GDP environments, and this can apply to all of that right, so you want to use a certain network, whether it's a villain on V sphere.
105
00:12:27.990 --> 00:12:42.840
Jirah Cox: or an HP network or network in aws or azure tcp for your application deployment same kind of thing or you want to deploy to Dev knock yourself out you want to deploy to prod okay let's get approval from you know the prod network manager kind of person for that for that environment.
106
00:12:44.250 --> 00:12:45.300
Jirah Cox: Taking a snapshot.
107
00:12:46.440 --> 00:12:51.390
Jirah Cox: You know, exceeding a certain threshold of the cpu cores per view cpu.
108
00:12:53.490 --> 00:12:56.790
Jirah Cox: And it goes to disk sizes, this is a really extensive list.
109
00:12:58.110 --> 00:13:01.830
Jirah Cox: Here on on the documentation here about what this all can be used for.
110
00:13:02.550 --> 00:13:08.100
Ben Rogers: Alright, so let's take a step back you said something that that made me want to expand the conversation a little bit.
111
00:13:08.640 --> 00:13:22.200
Ben Rogers: This will not only manage and approval on local private cloud infrastructure, but we can extend the services out to the advisors gc fees aws is that our new tannic clusters are running.
112
00:13:22.860 --> 00:13:35.580
Jirah Cox: yeah right so it's still have it for me to say calm and Sam self service can can let you, you know rifles application blueprints one time and then deploy them to any of those cloud environments right or really we say your cloud environment which can be multi cloud.
113
00:13:36.180 --> 00:13:42.990
Ben Rogers: I tell you, if I would have known about this for years ago Harvey this would have been in our environment just just for the.
114
00:13:43.530 --> 00:13:51.030
Ben Rogers: sake of being of knowing that i've got all these call centers and I don't want to get surprised by a heavy bill.
115
00:13:51.360 --> 00:13:54.900
Ben Rogers: Building this into would say hey if you're going to build something in azure.
116
00:13:55.110 --> 00:14:07.260
Ben Rogers: You know, you can build something on Prem I don't care that's already bought and paid for, but when you start to get away from on Prem and now you're looking at azure or aws where it's going to cost some significant money to have the loads right.
117
00:14:07.950 --> 00:14:11.310
Ben Rogers: There needs to be an approval process this fits perfectly into that model.
118
00:14:12.000 --> 00:14:24.150
Jirah Cox: Well, I think about how quickly, it can be enabled and stood up right because we've had our friends from service now on this podcast right and they clearly this is their bread and butter they live there all day, every day, complex business routing logic policies.
119
00:14:25.230 --> 00:14:26.280
Jirah Cox: And I would say this is almost.
120
00:14:27.360 --> 00:14:31.710
Jirah Cox: it's not even competitive right like if you need that level of automation you need that level of automation and approvals.
121
00:14:32.220 --> 00:14:39.390
Jirah Cox: If you just need I need someone like to your point bad I need to prevent a junior admin from doing something perhaps unwise in an environment.
122
00:14:40.140 --> 00:14:51.600
Jirah Cox: This is the stands up in minutes right like one click to enable calm now and cm self service a second click to say turn on approval policies and start building them right all hosted right there in prison central.
123
00:14:52.440 --> 00:15:06.060
Jirah Cox: With no other cloud services to call it to and deploy integrations that kind of stuff you can of course use a lot of things to to do your approval policies, but this is now baked into the very base product that you can just turn on in minutes.
124
00:15:06.780 --> 00:15:13.080
Ben Rogers: Now i'm looking at these screenshots this doesn't look like right rocket science it's just looks a lot like low code no code.
125
00:15:13.920 --> 00:15:22.080
Jirah Cox: yeah that's very fair yeah you can even use, you can even use it to call i'm looking back at the documentation here on the portal this blog post links to.
126
00:15:22.590 --> 00:15:33.450
Jirah Cox: And it even can be used for for run books right So if you want to you know use calm to trigger a certain kind of run book within PC, then you know hey go get approval for that.
127
00:15:36.630 --> 00:15:44.820
Jirah Cox: Oh here's a fun one if your application is estimated to cost more than a certain amount go get approval right number, the cost estimation built into.
128
00:15:45.240 --> 00:15:56.880
Jirah Cox: The deployment engine which, of course, can go out and Republic cloud pricing, but also, you can provide you an estimate for on Prem application pricing, so you can even have even have some cost base threshold here wow that's awesome.
129
00:15:57.210 --> 00:15:58.860
Ben Rogers: Now talk to me about.
130
00:16:00.390 --> 00:16:17.130
Ben Rogers: If i'm a junior engineer, and I want to put some test environment and aws and i've been through the approval process and it's approved does that automatically get built that come back to the engineer and say you are now eligible to go ahead and build this environment.
131
00:16:18.030 --> 00:16:18.630
So.
132
00:16:20.280 --> 00:16:23.670
Jirah Cox: The whenever whenever the approvals.
133
00:16:24.990 --> 00:16:31.980
Jirah Cox: come in which you can set to either say I just I need one person in this group to approve or i'm going to send out a bunch of approvals need all of them to come back approved.
134
00:16:32.550 --> 00:16:42.990
Jirah Cox: Whenever that matches your desired approval threshold, then it just go ahead, go ahead and continue with the deployment so to you as the request or there's no second action needed right you've already sent it off.
135
00:16:43.680 --> 00:16:48.000
Jirah Cox: Because back approved or rejected and either way, no more actions needed for you.
136
00:16:49.620 --> 00:16:57.870
Jirah Cox: And then yeah if you were one of those people and they approve or list you get an email login give it your yes or no, and it will go go off then with that request.
137
00:17:00.840 --> 00:17:03.600
Ben Rogers: I hate to see amazed by this, but this is so cool.
138
00:17:04.830 --> 00:17:07.140
Ben Rogers: The stuff you discovering these podcasts is awesome.
139
00:17:08.880 --> 00:17:10.440
Jirah Cox: Very good i'm pretty excited about it too right that.
140
00:17:10.440 --> 00:17:21.180
Jirah Cox: ability, just to go to all our customers running this and say here's this new feature we just built in for it, you know click go to your SEM run your updates come back and find new functionality here it's pretty awesome.
141
00:17:22.410 --> 00:17:32.460
Ben Rogers: Like another administrators, like me, in the past, they would be clamoring for this, because you know again it's always that fear of what could happen that I don't know is going to happen.
142
00:17:32.970 --> 00:17:44.550
Ben Rogers: And this again puts that safeguard on it, where I know that I can clip it at a certain level and have it to be an approval process instead of a Oh, I did this, and now we're having performance issues.
143
00:17:47.010 --> 00:17:55.980
Jirah Cox: Well into your point band around like safety thresholds, you know what we call it what it is right, what can wake me up at two in the morning right and make me give me a give me a rough night.
144
00:17:57.000 --> 00:18:06.000
Jirah Cox: This is complimentary to all the other monitoring of natively with npc right, so I can say you know if i'm if i'm a developer, I might be part of the Dev project right, I can put.
145
00:18:06.450 --> 00:18:20.010
Jirah Cox: Put thresholds are in that project to save this project can't consume more than X cpu why memories, the storage might only be build a deployed a certain veal and there's a whole other ways that I can safeguard those environments.
146
00:18:21.360 --> 00:18:35.040
Jirah Cox: To ensure my stability of the environment as well from from perhaps an overly ambitious developer, or you know consumer so yeah we want, we want the healthy self service we want rational safeguards and then.
147
00:18:35.760 --> 00:18:41.130
Jirah Cox: And then the ability to even go beyond safeguards into approvals when needed, so they all kind of work together pretty collaboratively.
148
00:18:45.300 --> 00:18:58.740
Harvey Green: sounds good, that was a man you guys are really diving in on this topic so that's great um I was kind of reading through you know some of these other pieces and it said this.
149
00:18:59.340 --> 00:19:07.560
Harvey Green: toward the bottom this feature is currently available as tech preview in column three dot five and i'll I will wait a minute, is it call is mcs.
150
00:19:10.380 --> 00:19:11.640
Jirah Cox: Oh, thank you, thank you.
151
00:19:12.540 --> 00:19:14.370
Jirah Cox: MAC fact checking acknowledged appreciate it.
152
00:19:15.180 --> 00:19:17.730
Harvey Green: Well i'm just reading through.
153
00:19:19.980 --> 00:19:22.860
Jirah Cox: Your your checks in the mail as a as a proofreader.
154
00:19:22.890 --> 00:19:23.250
appreciate it.
155
00:19:26.340 --> 00:19:32.850
Jirah Cox: Sure, but a good call it as well, but of course it is the tech preview feature so, of course, please use it try it give your account team feedback on it.
156
00:19:34.920 --> 00:19:41.430
Jirah Cox: For sure so it'll be in tech preview usually is the step, you know prior to a broader rollout.
157
00:19:43.080 --> 00:19:50.790
Ben Rogers: So let me ask this question again being a new mechanics employee, had we had something like this before, is this kind of the first iteration of this type of service.
158
00:19:51.960 --> 00:19:55.050
Jirah Cox: Usually before this usually it would.
159
00:19:56.220 --> 00:20:08.640
Jirah Cox: Be you would pull up your you know calm now and see i'm self service to some other cloud based portal that will handle all of the approvals right and then just call into calm after it got all those approvals.
160
00:20:10.290 --> 00:20:12.180
Jirah Cox: So you could do it, but it wasn't us hosting it.
161
00:20:12.540 --> 00:20:16.710
Ben Rogers: Okay, so we're bringing this 100% as functionality in our products that no.
162
00:20:17.010 --> 00:20:18.060
Ben Rogers: Totally okay.
163
00:20:22.050 --> 00:20:28.710
Harvey Green: And so Ben he mentioned, I didn't mention this to you, five years ago it didn't look like this, five years ago.
164
00:20:34.890 --> 00:20:40.170
Ben Rogers: i'm thinking about a time that our systems got tore down because of an anti virus update.
165
00:20:40.890 --> 00:20:41.250
Harvey Green: Oh yeah.
166
00:20:41.280 --> 00:20:44.010
Ben Rogers: And this would have been something that would have prevented that.
167
00:20:44.640 --> 00:20:51.780
Ben Rogers: And so you know i'm sitting in a meeting i've got two data centers that are you know load balance active active and all sudden I get out of a meeting and my.
168
00:20:52.170 --> 00:21:03.330
Ben Rogers: engineer goes we're down and i'm laughing i'm like no way we're now where do I start to you know roll back why it happened, this would have prevented that from happening.
169
00:21:03.900 --> 00:21:11.130
Ben Rogers: You know, there would have been some type of approval process that you know one if you want to do, Dr that's one thing, but once you move into production.
170
00:21:11.610 --> 00:21:15.810
Ben Rogers: Heavy approvals got to be done, especially when you're playing with a core technology like eating.
171
00:21:16.530 --> 00:21:22.950
Ben Rogers: So that's that's really the situation that comes to the top of my mind that I go if I would have had this sake, are.
172
00:21:23.280 --> 00:21:32.280
Ben Rogers: I would have not walked out of the meeting and gone you're kidding me there's no way that could happen, and then the reality of it happened, you know so again, I think I think this is wonderful.
173
00:21:33.810 --> 00:21:43.410
Jirah Cox: that's a it's always the way right with the you know any kind of event post mortem autopsy investigations right things that have never happened before happen all the time.
174
00:21:45.390 --> 00:21:46.770
Jirah Cox: always a failure of imagination.
175
00:21:50.130 --> 00:21:53.850
Harvey Green: Yes, and fortunately, and unfortunately.
176
00:21:56.400 --> 00:22:08.160
Ben Rogers: Well it's just hard when you got explain to the organization and they're like you know you built this robust environment they shouldn't go down how did it go down, and you go the human element I haven't gets that yet.
177
00:22:08.580 --> 00:22:16.830
Ben Rogers: Yes, this really kind of you know man I love engineers, I mean I love my engineers i'm an engineer at heart, and just again.
178
00:22:17.190 --> 00:22:26.250
Ben Rogers: safeguards are always a priority for companies, because they don't understand you know what it takes to get the IT systems to run efficiently, they just want to.
179
00:22:26.580 --> 00:22:41.340
Ben Rogers: hit the application and be in the in the database looking at patient records and and for something like this again it just gives a level of comfort that you won't be interrupted in a meeting going we're down and acted back and situation, what how did that happen.
180
00:22:42.510 --> 00:22:45.600
Jirah Cox: Well, that I mean like like we've talked about four months now Harvey right like.
181
00:22:46.440 --> 00:22:57.180
Jirah Cox: In some sense, like the pie in the sky yeah sure automate everything like Well, this is that's a tangible benefit there they've been sharing is is if the more you automate The more I can wrap these approvals around.
182
00:22:57.660 --> 00:23:03.630
Jirah Cox: Compared to getting approvals for a human process doable harder to enforce.
183
00:23:04.440 --> 00:23:09.060
Jirah Cox: Right right so more governance available with that kind of process.
184
00:23:09.570 --> 00:23:17.730
Ben Rogers: No, let me ask this let's say that one of these approvals came in in the system that had the capacity to do that.
185
00:23:18.660 --> 00:23:33.360
Ben Rogers: Would it make recommendations is back to us, or when it stopped the process, I mean give me an idea of how that would work that the engineers made some realistic demands and we don't have the resources to meet that.
186
00:23:36.570 --> 00:23:36.870
Harvey Green: yeah.
187
00:23:36.930 --> 00:23:39.150
Harvey Green: So i'll go ahead or.
188
00:23:39.270 --> 00:23:50.010
Harvey Green: Anyway, I was gonna say so you've got the ability to handle it by a threshold and so with with your threshold being.
189
00:23:50.520 --> 00:24:01.980
Harvey Green: The condition it's taking a look at I mean that that is your built in way hopefully to stop that if you've got your your conditions set up correctly.
190
00:24:02.460 --> 00:24:14.700
Harvey Green: um and if not, I mean to your point the human element is still there if we don't if we don't protect ourselves against things like that, then they can still happen to us.
191
00:24:15.810 --> 00:24:19.890
Jirah Cox: yeah I can think of an answer that involves like a few different components.
192
00:24:20.970 --> 00:24:32.850
Jirah Cox: The first day like if you're just broadly rolling out like, and these are self service automation right like self service deployments you know you're you're moving it into a model where you know you run the store keep the keep the shelves stocked.
193
00:24:33.960 --> 00:24:35.490
Jirah Cox: And you just can come in and get what they need.
194
00:24:37.980 --> 00:24:50.880
Jirah Cox: Part of that would involve some sort of a level of responsibility of understanding, like a pace of deployment right like we average 100 times a week or 200 times a week or you know hundred hundred terabytes a week or whatever your growth rate is.
195
00:24:52.530 --> 00:25:01.110
Jirah Cox: If something dramatically exceeded that right like you know you went from 100 terabytes a week to a petabyte a week or someone wanted 10 petabytes in a week.
196
00:25:02.460 --> 00:25:12.300
Jirah Cox: You you'd want that deployment to fail right you wouldn't want that to contend you'd want to get that you'd want that to fail and alert and you know, have a conversation about that one.
197
00:25:13.680 --> 00:25:16.080
Harvey Green: Which brings in another dimension right with automation.
198
00:25:16.620 --> 00:25:24.030
Jirah Cox: watch the logs right you want to know what succeeding know what's failing right and be able to because of the failures will tell you as much as the success messages do.
199
00:25:26.250 --> 00:25:39.390
Jirah Cox: let's say it wasn't a real outlier in your just it was organic growth on a healthy trajectory, then the cluster itself would already be alerting you whenever you drop below a certain kind of threshold right by default it's up for a one year.
200
00:25:39.750 --> 00:25:41.100
Jirah Cox: kind of runway if your.
201
00:25:41.220 --> 00:25:48.300
Jirah Cox: If your growth in cpu memory or storage is trending towards and out of out of resource condition and the next 12 months.
202
00:25:48.660 --> 00:25:58.560
Jirah Cox: That generates its own alerts within prism to say hey you know plan for growing this this dimension, this environment in this dimension by X amount to sustain a healthy growth runway.
203
00:25:59.490 --> 00:26:05.280
Jirah Cox: So lots of different answers there that all add up to how we handle that how we can handle it a normal, healthy environment.
204
00:26:06.750 --> 00:26:14.970
Jirah Cox: And how it could be a good challenge for the you know if somebody really came to you need to 10 petabytes like there's more conversations to be had there.
205
00:26:18.810 --> 00:26:19.650
Harvey Green: Absolutely.
206
00:26:20.910 --> 00:26:26.190
Harvey Green: um alright any parting thoughts for us, Mr Rogers.
207
00:26:27.870 --> 00:26:40.290
Ben Rogers: I think this is awesome you know I could say that being a new tonics employee, but I can also say that, being a former it director anytime that I can build safe cards into a system, it just makes it for a good night's rest.
208
00:26:41.340 --> 00:26:42.480
Harvey Green: yeah absolutely.
209
00:26:43.380 --> 00:26:43.890
Jirah Cox: we're all about.
210
00:26:47.220 --> 00:26:48.360
Harvey Green: Jared top there.
211
00:26:49.860 --> 00:26:54.090
Jirah Cox: Man, you know proof point right, you know nights and weekends back that's that's what really matters.
212
00:26:54.960 --> 00:27:05.250
Harvey Green: yeah I agree i'm being able to just I mean it still as me, but the tenants, for your sanity people.
213
00:27:07.530 --> 00:27:11.250
Harvey Green: This is just this is just another one and a long line.
214
00:27:12.000 --> 00:27:13.650
Harvey Green: of being able to.
215
00:27:14.130 --> 00:27:18.600
Harvey Green: Take back your some of your sanity if you've already lost pieces of it.
216
00:27:19.800 --> 00:27:21.450
Jirah Cox: i'll get us shirts made were on team sanity.
217
00:27:21.810 --> 00:27:25.800
Harvey Green: Yes, rocky insanity I often say another.
218
00:27:25.830 --> 00:27:28.710
Ben Rogers: place this would really help and that's what compliance.
219
00:27:29.220 --> 00:27:37.260
Ben Rogers: and risk assessment, you know if you've got a tool like this, you can guarantee you can stay in compliance and it also look at your risk assessment team and going.
220
00:27:37.590 --> 00:27:43.830
Ben Rogers: Again i'm building protection features into the environment that won't, let us over run the environment if we don't have the capacity to do it.
221
00:27:44.280 --> 00:27:44.580
yeah.
222
00:27:45.960 --> 00:27:56.430
Ben Rogers: You know that died, that the the it leaders that are out there and a half the answer to a risk assessment department or a compliance department, this could be a really good tool for not only.
223
00:27:56.730 --> 00:28:03.210
Ben Rogers: You know, protecting the environment, but also documenting what's being done, and if there was an approval process.
224
00:28:03.630 --> 00:28:10.950
Ben Rogers: That went into this decision and went into this action so again i'm putting back on it directors hat on you know when the compliance people would come to.
225
00:28:11.910 --> 00:28:15.840
Ben Rogers: My office and be like, why did you let this happen, or how did this happen and.
226
00:28:16.080 --> 00:28:29.520
Ben Rogers: You know if I had a way to go back and go here here was the approval chain here was the thought process here's what went into to get to where we're at today again just another see why and better way of doing business in my opinion.
227
00:28:31.140 --> 00:28:31.530
Harvey Green: yeah.
228
00:28:32.730 --> 00:28:34.020
Harvey Green: You can argue that.
229
00:28:36.120 --> 00:28:43.680
Harvey Green: That makes perfect sense so so dire Is this something that I have to buy in order to see it or cannot test this out.
230
00:28:45.240 --> 00:28:51.360
Jirah Cox: You guys should take take a test drive for this right on a test drive so test driving change.com.
231
00:28:54.630 --> 00:28:59.190
Jirah Cox: or call your friendly mechanics teams and tiger team for a powerhouse DEMO.
232
00:28:59.820 --> 00:29:03.360
Harvey Green: yeah absolutely that is definitely another option so.
233
00:29:06.660 --> 00:29:13.830
Harvey Green: guys, I appreciate it for sure definitely a good conversation, today you just you just took off and I couldn't stop you.
234
00:29:18.300 --> 00:29:21.240
Harvey Green: So appreciate you guys jumping on.
235
00:29:22.350 --> 00:29:25.200
Harvey Green: We will see everybody on the next one.
236
00:29:26.070 --> 00:29:26.940
Jirah Cox: Go talk to you then.
237
00:29:27.660 --> 00:29:28.380
Ben Rogers: bye have a good one.
238
00:29:39.240 --> 00:29:39.840
Harvey Green: Sorry.
239
00:29:43.020 --> 00:29:43.890
Harvey Green: bloopers.
240
00:29:44.010 --> 00:29:46.140
Ben Rogers: hey I found you guys hold on.
241
00:29:47.340 --> 00:29:48.690
Harvey Green: hold on just a second there.