WEBVTT

1
00:00.000 --> 00:09.460
So, in this day and age, I'm sure that everybody has some idea at least of what

2
00:09.460 --> 00:10.160
cloud computing

3
00:10.160 --> 00:13.240
is and what cloud computing entails.

4
00:13.240 --> 00:18.450
Well, it's important as we're jumping into this course to understand right up

5
00:18.450 --> 00:19.080
front how

6
00:19.080 --> 00:24.760
Cisco defines things and what other standards bodies they reference when

7
00:24.760 --> 00:25.760
defining cloud

8
00:25.760 --> 00:26.760
computing.

9
00:26.760 --> 00:32.040
So, our goal in this video is just to get an overview of those things.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:26.760 --> 00:32.040
So, our goal in this video is just to get an overview of those things.

10
00:32.040 --> 00:36.600
What is cloud computing and what are some of the characteristics of it that are

11
00:36.600 --> 00:37.160
defined

12
00:37.160 --> 00:40.800
by both Cisco and some of our standards bodies.

13
00:40.800 --> 00:44.640
So, let's jump in and take a look.

14
00:44.640 --> 00:49.200
So, overall, what is cloud computing?

15
00:49.200 --> 00:54.900
Well, cloud computing is something that can provide businesses with access to

16
00:54.900 --> 00:55.720
computing

17
00:55.720 --> 01:02.440
resources such as networking, applications, even whole servers, all available
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:55.720 --> 01:02.440
resources such as networking, applications, even whole servers, all available

18
01:02.440 --> 01:03.160
over the

19
01:03.160 --> 01:04.520
Internet.

20
01:04.520 --> 01:11.570
And what makes this so popular is this is a pay as you go model, which means

21
01:11.570 --> 01:13.160
that businesses

22
01:13.160 --> 01:16.680
only have to pay for the resources they use.

23
01:16.680 --> 01:22.670
This can be incredibly popular, particularly if you have very elastic workloads

24
01:22.670 --> 01:22.760
.

25
01:22.760 --> 01:27.750
As an example, maybe you normally run your own on site servers, but if they get

26
01:27.750 --> 01:28.200
super

27
01:28.200 --> 01:33.400
busy, you can actually offload some of that work and spin up some servers on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:28.200 --> 01:33.400
busy, you can actually offload some of that work and spin up some servers on

28
01:33.400 --> 01:34.120
the cloud

29
01:34.120 --> 01:38.120
on the fly using this pay as you go model.

30
01:38.120 --> 01:43.560
So, this is a very, very popular aspect of cloud computing.

31
01:43.560 --> 01:50.320
Now, the National Institute of Standards and Technologies, this is an American

32
01:50.320 --> 01:51.480
Institute.

33
01:51.480 --> 01:55.770
So, those of you who may not be in the United States, you may have your own

34
01:55.770 --> 01:57.160
standards bodies.

35
01:57.160 --> 02:08.920
However, NIST defines cloud computing in a special publication, 800-145.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:57.160 --> 02:08.920
However, NIST defines cloud computing in a special publication, 800-145.

36
02:08.920 --> 02:16.360
The way they define it is as a model for enabling ubiquitous.

37
02:16.360 --> 02:20.660
And if you're not familiar with that particular word, it means found everywhere

38
02:20.660 --> 02:20.960
.

39
02:20.960 --> 02:27.290
So, widely available, convenient, because again, it's over the Internet, which

40
02:27.290 --> 02:28.080
of course,

41
02:28.080 --> 02:30.960
most companies are going to have access to.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
02:28.080 --> 02:30.960
most companies are going to have access to.

42
02:30.960 --> 02:37.230
And we already sort of mentioned this on demand aspect with the pay as you go

43
02:37.230 --> 02:37.680
model.

44
02:37.680 --> 02:45.560
But it's ubiquitous, convenient, and on demand network access to a shared pool,

45
02:45.560 --> 02:45.680
which of

46
02:45.680 --> 02:52.880
course also helps to reduce costs of configurable computing resources.

47
02:52.880 --> 02:57.480
And again, this can be anything from networks to servers to storage

48
02:57.480 --> 03:00.200
applications, services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:57.480 --> 03:00.200
applications, services.

49
03:00.200 --> 03:05.280
All of these that can be rapidly provisioned and released.

50
03:05.280 --> 03:09.360
Again, that's going back to the pay as you go model.

51
03:09.360 --> 03:15.200
The advantage, of course, is that this takes very minimal management effort.

52
03:15.200 --> 03:18.800
A lot of this is going to be fully automated.

53
03:18.800 --> 03:24.200
We don't have to get a service provider involved in order to use the cloud

54
03:24.200 --> 03:25.360
resources.

55
03:25.360 --> 03:30.840
If you're interested in reading this publication, I have it linked here in the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
03:25.360 --> 03:30.840
If you're interested in reading this publication, I have it linked here in the

56
03:30.840 --> 03:31.160
skill.

57
03:31.160 --> 03:36.780
And it's also available here at this URL, if you'd like to go there yourself

58
03:36.780 --> 03:37.640
and download

59
03:37.640 --> 03:41.480
the file directly from NIST.

60
03:41.480 --> 03:48.480
One of the big advantages to this model, of course, is it gives access to a lot

61
03:48.480 --> 03:49.520
of IT

62
03:49.520 --> 03:56.040
resources, again, things like infrastructure, platforms, and services.

63
03:56.040 --> 04:02.200
And the real key here is it's all without taking up capital.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
03:56.040 --> 04:02.200
And the real key here is it's all without taking up capital.

64
04:02.200 --> 04:07.600
For a lot of small companies in particular, this is a big issue.

65
04:07.600 --> 04:13.030
Small companies can now take advantage of resources the same way a large

66
04:13.030 --> 04:14.080
corporation

67
04:14.080 --> 04:20.110
would without having to put out that upfront capital that they may not have

68
04:20.110 --> 04:20.760
because they're

69
04:20.760 --> 04:22.720
a small company.

70
04:22.720 --> 04:28.660
So to make all of this work and function, cloud computing has been built on a

71
04:28.660 --> 04:29.520
few founding

72
04:29.520 --> 04:31.120
principles.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
04:29.520 --> 04:31.120
principles.

73
04:31.120 --> 04:34.960
The first one is automation.

74
04:34.960 --> 04:40.680
One is that whole zero touch idea for just a small example.

75
04:40.680 --> 04:47.570
You could go out to Amazon today, access the AWS cloud, fire up a server with

76
04:47.570 --> 04:48.360
Linux on

77
04:48.360 --> 04:54.390
it, have the whole thing up and running, give or take within about five minutes

78
04:54.390 --> 04:55.200
, and never

79
04:55.200 --> 04:57.240
talk to Amazon at all.

80
04:57.240 --> 04:59.200
It's fully automated.

81
04:59.200 --> 05:05.240
We can go through this self service portal and deploy all the needed resources,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
04:59.200 --> 05:05.240
We can go through this self service portal and deploy all the needed resources,

82
05:05.240 --> 05:06.320
for example,

83
05:06.320 --> 05:08.160
maybe that Linux server.

84
05:08.160 --> 05:10.280
So automation is key to this.

85
05:10.280 --> 05:15.560
We don't want to have to contact service providers to handle this for us.

86
05:15.560 --> 05:19.120
Another big principle is resilience.

87
05:19.120 --> 05:23.020
We don't want to put corporate resources in an environment that would be prone

88
05:23.020 --> 05:23.560
to a lot

89
05:23.560 --> 05:25.040
of failure.

90
05:25.040 --> 05:31.480
So any decent size cloud provider is going to use distributed resources across
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
05:25.040 --> 05:31.480
So any decent size cloud provider is going to use distributed resources across

91
05:31.480 --> 05:32.240
massive

92
05:32.240 --> 05:34.280
redundant systems.

93
05:34.280 --> 05:39.740
That's going to include your storage, your networking and data centers

94
05:39.740 --> 05:41.040
themselves.

95
05:41.040 --> 05:45.860
So what we mean by this is that the storage, the networks and the data centers

96
05:45.860 --> 05:46.640
themselves

97
05:46.640 --> 05:48.800
are all redundant.

98
05:48.800 --> 05:54.320
All of your big providers, Amazon, Microsoft, Google and many others have data

99
05:54.320 --> 05:55.080
centers all

100
05:55.080 --> 05:56.760
around the world.

101
05:56.760 --> 05:59.800
And you can control the distribution of your resources.

102
05:59.800 --> 06:02.320
However, it works for you.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:59.800 --> 06:02.320
However, it works for you.

103
06:02.320 --> 06:08.640
And of course, another of our major principles is going to be cost savings by

104
06:08.640 --> 06:10.000
using the cloud

105
06:10.000 --> 06:15.590
companies not only don't have to put up any upfront investment, but also the

106
06:15.590 --> 06:17.080
ongoing costs

107
06:17.080 --> 06:22.150
are generally cheaper when you pull resources and you're not having to run your

108
06:22.150 --> 06:22.760
own data

109
06:22.760 --> 06:28.330
center with your own building, your own racks, your own hardware, your own

110
06:28.330 --> 06:29.400
servers, network

111
06:29.400 --> 06:32.160
equipment, your own backup equipment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
06:29.400 --> 06:32.160
equipment, your own backup equipment.

112
06:32.160 --> 06:37.320
You don't have to have your own HVAC, your own power structure.

113
06:37.320 --> 06:40.360
All of these things cost a lot of money.

114
06:40.360 --> 06:45.200
But when you go with a cloud provider, they're providing all of those resources

115
06:45.200 --> 06:45.320
.

116
06:45.320 --> 06:50.630
And since everybody's sharing it, they can offer it at a much cheaper cost in

117
06:50.630 --> 06:52.400
most cases.

118
06:52.400 --> 06:57.120
Now of course, another big principle is going to be security.

119
06:57.120 --> 06:59.640
There's no other way of saying this.

120
06:59.640 --> 07:04.420
When we put our information in the cloud, clearly we are putting sensitive
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
06:59.640 --> 07:04.420
When we put our information in the cloud, clearly we are putting sensitive

121
07:04.420 --> 07:06.400
corporate information

122
07:06.400 --> 07:09.520
onto another person's environment.

123
07:09.520 --> 07:12.000
There's no other way to say that.

124
07:12.000 --> 07:16.560
They're using somebody else's resources for our sensitive data.

125
07:16.560 --> 07:24.720
So that means they have to provide a very robust security model and they all do

126
07:24.720 --> 07:24.800
.

127
07:24.800 --> 07:28.480
We're going to have things like encryption of the data on storage.

128
07:28.480 --> 07:34.200
So at rest also in motion using VPNs and things like this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
07:28.480 --> 07:34.200
So at rest also in motion using VPNs and things like this.

129
07:34.200 --> 07:38.730
We're also going to have advanced security at the edge using advanced firewalls

130
07:38.730 --> 07:39.960
and such.

131
07:39.960 --> 07:44.190
So there's going to be a lot of security because without that, of course, most

132
07:44.190 --> 07:45.040
corporations

133
07:45.040 --> 07:49.950
wouldn't consider cloud even for a moment because security is going to be a big

134
07:49.950 --> 07:50.560
concern

135
07:50.560 --> 07:51.760
here.

136
07:51.760 --> 07:55.600
And our last founding principle is flexibility.

137
07:55.600 --> 07:58.120
This of course is also a big one.

138
07:58.120 --> 08:02.580
We sort of already alluded to this back at the beginning of this video where I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

138
07:58.120 --> 08:02.580
We sort of already alluded to this back at the beginning of this video where I

139
08:02.580 --> 08:03.080
said you

140
08:03.080 --> 08:06.240
could easily use this to scale out.

141
08:06.240 --> 08:10.930
If your servers get too busy, you can scale out to the cloud and use resources

142
08:10.930 --> 08:11.400
in the

143
08:11.400 --> 08:12.640
cloud.

144
08:12.640 --> 08:15.240
You can also scale up.

145
08:15.240 --> 08:19.320
Maybe the servers that you're using currently aren't big enough, fast enough,

146
08:19.320 --> 08:20.000
have enough

147
08:20.000 --> 08:21.000
RAM.

148
08:21.000 --> 08:25.000
Well, you can upgrade your servers in the cloud.

149
08:25.000 --> 08:29.440
You're dealing with virtually unlimited resources.

150
08:29.440 --> 08:32.760
Certainly more than any one company would use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

150
08:29.440 --> 08:32.760
Certainly more than any one company would use.

151
08:32.760 --> 08:37.600
And of course, down the road, if you don't need as many resources, you can of

152
08:37.600 --> 08:38.120
course

153
08:38.120 --> 08:40.440
scale this down as well.

154
08:40.440 --> 08:42.880
You can start using less resources.

155
08:42.880 --> 08:46.520
This is the beauty of the pay as you go model.

156
08:46.520 --> 08:50.560
You pay for the resources you need and when you don't need them anymore, you

157
08:50.560 --> 08:51.160
just stop

158
08:51.160 --> 08:54.960
using them and therefore you stop paying them.

159
08:54.960 --> 08:58.080
Think about a physical data center for a moment.

160
08:58.080 --> 09:02.590
What happens while your company is growing and growing and growing and your
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

160
08:58.080 --> 09:02.590
What happens while your company is growing and growing and growing and your

161
09:02.590 --> 09:03.360
data centers

162
09:03.360 --> 09:07.700
get bigger and you need more servers and you need more physical infrastructure,

163
09:07.700 --> 09:07.800
but

164
09:07.800 --> 09:11.520
then maybe your company is not doing quite so well down the road.

165
09:11.520 --> 09:16.240
Now you need to scale back or maybe it's just things get more efficient.

166
09:16.240 --> 09:18.400
Maybe the business isn't even downscaling.

167
09:18.400 --> 09:23.160
I remember back when virtualization first started back in the early days of

168
09:23.160 --> 09:23.920
things like

169
09:23.920 --> 09:26.440
VMware ESXi.

170
09:26.440 --> 09:32.610
You would take 20 to 30 physical servers and take those down to one big
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

170
09:26.440 --> 09:32.610
You would take 20 to 30 physical servers and take those down to one big

171
09:32.610 --> 09:34.320
powerful server.

172
09:34.320 --> 09:39.360
Well, that took up a heck of a lot less space in the data center.

173
09:39.360 --> 09:44.490
Well when you do that at scale, you could end up with only using a third of the

174
09:44.490 --> 09:44.920
data

175
09:44.920 --> 09:48.480
center you've paid for, but you're still paying for the building.

176
09:48.480 --> 09:51.840
You're still paying for the air conditioning to cool it.

177
09:51.840 --> 09:56.010
Maybe not as much power, but the point is you're still paying for resources

178
09:56.010 --> 09:56.520
that are

179
09:56.520 --> 09:59.480
now widely underutilized.

180
09:59.480 --> 10:04.100
Plus all those old servers that you paid for, well they're still sitting there
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

180
09:59.480 --> 10:04.100
Plus all those old servers that you paid for, well they're still sitting there

181
10:04.100 --> 10:04.480
and of course

182
10:04.480 --> 10:08.960
we all know that things like servers don't have a lot of resale value.

183
10:08.960 --> 10:13.720
But the point here is as you need to scale down for whatever reason, you can do

184
10:13.720 --> 10:14.280
it very

185
10:14.280 --> 10:18.840
easily on the cloud and we don't have to worry about recovering costs.

186
10:18.840 --> 10:25.570
Now just to go back and revisit NIST one more time, they also outline five

187
10:25.570 --> 10:28.480
essential characteristics.

188
10:28.480 --> 10:32.970
Now these aren't that different from the founding principles, but it's the same
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
10:28.480 --> 10:32.970
Now these aren't that different from the founding principles, but it's the same

189
10:32.970 --> 10:33.320
sort

190
10:33.320 --> 10:36.340
of idea you want to be familiar with these as well.

191
10:36.340 --> 10:40.830
The first one is of course we already sort of mentioned this is on demand

192
10:40.830 --> 10:41.680
service.

193
10:41.680 --> 10:46.300
The customer should be able to unilaterally provision these computing

194
10:46.300 --> 10:47.440
capabilities as

195
10:47.440 --> 10:49.360
they need to.

196
10:49.360 --> 10:56.200
Things like server time, network storage are going to be used only as needed.

197
10:56.200 --> 10:59.240
There's going to be no human interaction.

198
10:59.240 --> 11:02.760
Again all of this needs to be automated.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

198
10:59.240 --> 11:02.760
Again all of this needs to be automated.

199
11:02.760 --> 11:08.920
The second characteristic is this has to be broadly available over the network.

200
11:08.920 --> 11:14.590
So these capabilities need to be available over the network and accessed

201
11:14.590 --> 11:15.720
through standard

202
11:15.720 --> 11:17.420
mechanisms.

203
11:17.420 --> 11:23.620
So what this means is we need a way to connect using thin or thick clients.

204
11:23.620 --> 11:28.130
We need to be able to use things like mobile phones, tablets, laptops, workst

205
11:28.130 --> 11:28.900
ations and

206
11:28.900 --> 11:30.060
so on.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

206
11:28.900 --> 11:30.060
so on.

207
11:30.060 --> 11:34.960
So the information has to be readily available and sometimes that may require a

208
11:34.960 --> 11:36.880
special application.

209
11:36.880 --> 11:41.420
We'll get into that more as we get more detailed into this skill.

210
11:41.420 --> 11:45.160
The third principle is resource pooling.

211
11:45.160 --> 11:49.840
Now again we've sort of already mentioned this but all of those resources of

212
11:49.840 --> 11:50.740
the provider

213
11:50.740 --> 11:55.260
are going to be pooled and serve multiple customers.

214
11:55.260 --> 12:00.380
This again of course is going to save a lot of money for the customer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

214
11:55.260 --> 12:00.380
This again of course is going to save a lot of money for the customer.

215
12:00.380 --> 12:04.650
Now of course this needs to fully support a multi-tenant model because of

216
12:04.650 --> 12:05.500
course we don't

217
12:05.500 --> 12:09.020
want customers resources getting intermingled.

218
12:09.020 --> 12:13.140
This could involve different physical and virtual resources.

219
12:13.140 --> 12:17.590
Again they're going to be dynamically assigned and reassigned based on what the

220
12:17.590 --> 12:19.320
customer needs.

221
12:19.320 --> 12:23.220
So in other words you may be using a server one day when you're done with it,

222
12:23.220 --> 12:23.560
you turn

223
12:23.560 --> 12:29.030
it off and then ten minutes later somebody else is going to use the same server

224
12:29.030 --> 12:29.280
to do

225
12:29.280 --> 12:31.480
what they need to do on the cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

225
12:29.280 --> 12:31.480
what they need to do on the cloud.

226
12:31.480 --> 12:35.520
So all of this is going to be dynamically done through the portal.

227
12:35.520 --> 12:40.020
And as I mentioned before as the customer you can generally specify the

228
12:40.020 --> 12:41.000
geographical

229
12:41.000 --> 12:43.940
location of the resources.

230
12:43.940 --> 12:49.020
Be that CPU, memory, storage, networking, virtual machines.

231
12:49.020 --> 12:53.660
Because generally speaking you probably want to choose a data center or

232
12:53.660 --> 12:54.980
resource location

233
12:54.980 --> 13:01.380
close to you or for redundancy you may want to duplicate your work across data
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

233
12:54.980 --> 13:01.380
close to you or for redundancy you may want to duplicate your work across data

234
13:01.380 --> 13:02.120
centers

235
13:02.120 --> 13:04.380
that are geographically diverse.

236
13:04.380 --> 13:09.260
So you have a choice here on how you want to handle your resources.

237
13:09.260 --> 13:11.960
Next is rapid elasticity.

238
13:11.960 --> 13:18.440
The capabilities have to be rapidly, analystically, provisioned and released.

239
13:18.440 --> 13:23.760
It says sometimes automatically that's just right from their documentation.

240
13:23.760 --> 13:28.910
These days I would say always automatically but this is going to be done for

241
13:28.910 --> 13:29.840
outward and

242
13:29.840 --> 13:32.880
inward mobility on demand.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

242
13:29.840 --> 13:32.880
inward mobility on demand.

243
13:32.880 --> 13:38.980
But as I mentioned earlier these capabilities often appear unlimited.

244
13:38.980 --> 13:44.600
Again, it's generally going to be far more than any one company is ever going

245
13:44.600 --> 13:45.180
to need.

246
13:45.180 --> 13:51.220
And of course they can be appropriated in any quantity at any time.

247
13:51.220 --> 13:54.180
This is going to be based on the customer's needs.

248
13:54.180 --> 13:58.580
Finally, this has to be a measured service.

249
13:58.580 --> 14:02.990
The cloud provider needs to be able to automatically control and optimize this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

249
13:58.580 --> 14:02.990
The cloud provider needs to be able to automatically control and optimize this

250
14:02.990 --> 14:04.560
resource use.

251
14:04.560 --> 14:10.060
They need to be able to meter the capability at some level of extraction that

252
14:10.060 --> 14:11.560
is appropriate.

253
14:11.560 --> 14:15.940
So again, whether that's storage, processing, the bandwidth available for the

254
14:15.940 --> 14:16.620
network, how

255
14:16.620 --> 14:19.900
many active user accounts there are.

256
14:19.900 --> 14:24.130
Something has to be used to meter the resources and make sure that they're

257
14:24.130 --> 14:25.180
available.

258
14:25.180 --> 14:31.280
The usage of those resources needs to be monitored, controlled and reported so
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

258
14:25.180 --> 14:31.280
The usage of those resources needs to be monitored, controlled and reported so

259
14:31.280 --> 14:32.860
that there's transparency

260
14:32.860 --> 14:35.820
for both the provider and the customer.

261
14:35.820 --> 14:40.230
Again, this is going to be important for resource utilization, keeping track of

262
14:40.230 --> 14:41.420
the resources

263
14:41.420 --> 14:43.060
that need to be billed.

264
14:43.060 --> 14:48.020
So there's no surprises for the customer when they get their bill.

265
14:48.020 --> 14:52.500
They should have an idea of the resources that they've already been using.

266
14:52.500 --> 14:59.020
As an example, you can go into Amazon AWS, look at your account billing anytime

267
14:59.020 --> 15:00.340
you want.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

267
14:59.020 --> 15:00.340
you want.

268
15:00.340 --> 15:04.670
And based on your resource utilization, it will give you a real-time estimate

269
15:04.670 --> 15:05.140
of what

270
15:05.140 --> 15:08.260
your cost is going to be for that month.

271
15:08.260 --> 15:09.780
Now of course that can change.

272
15:09.780 --> 15:13.140
If you suddenly turn off a bunch of resources, it could go down.

273
15:13.140 --> 15:16.740
If you fire up a bunch of resources, of course, it will go up.

274
15:16.740 --> 15:19.860
But it all needs to be measured and made transparent.

275
15:19.860 --> 15:22.740
So everybody's on the same page.

276
15:22.740 --> 15:27.940
So this has just been an introduction to some definitions and concepts behind

277
15:27.940 --> 15:29.820
cloud computing.

278
15:29.820 --> 15:33.660
Up next, let's take a look at some of the cloud deployment models.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

278
15:29.820 --> 15:33.660
Up next, let's take a look at some of the cloud deployment models.