WEBVTT

00:00:01.040 --> 00:00:03.850
When we look at the various cloud deployments,

00:00:04.010 --> 00:00:08.440
we've seen, for example, and discussed a little bit about a private cloud,

00:00:08.440 --> 00:00:15.520
which quite simply is a cloud or a set of IT infrastructure which is

00:00:15.520 --> 00:00:19.250
provisioned for the exclusive use of one organization,

00:00:19.740 --> 00:00:21.440
and many companies have done this.

00:00:21.450 --> 00:00:24.510
Yes, they're using cloud‑based services,

00:00:24.690 --> 00:00:29.060
but they are the only tenant, it's not a multi‑tenant environment.

00:00:29.840 --> 00:00:32.970
This could either be in their own facility,

00:00:32.970 --> 00:00:37.360
their own server room, or off‑premise as we've discussed as well.

00:00:38.740 --> 00:00:39.890
In many cases,

00:00:39.890 --> 00:00:44.260
the private cloud could be owned by the organization

00:00:44.260 --> 00:00:47.940
itself or it could actually be owned, managed,

00:00:47.940 --> 00:00:53.570
and operated by a third‑party where the third‑party actually does all of

00:00:53.570 --> 00:00:58.060
the support work to ensure that this operates correctly.

00:00:58.440 --> 00:01:02.500
The organization that is the cloud consumer then

00:01:02.850 --> 00:01:06.660
doesn't have to worry about their IT, they've outsourced all of that.

00:01:08.140 --> 00:01:11.510
When we look at an outsourced private cloud scenario,

00:01:11.510 --> 00:01:12.450
for example,

00:01:12.590 --> 00:01:16.670
we can see on the right‑hand column here the customers

00:01:16.670 --> 00:01:20.330
facility where they have their own users,

00:01:20.330 --> 00:01:23.150
and within their trusted computing base,

00:01:23.150 --> 00:01:28.000
their security perimeter, and they manage things within there,

00:01:28.000 --> 00:01:31.450
the things like the endpoints and user access levels.

00:01:32.140 --> 00:01:37.670
But within the facility of the cloud provider is a separated area which

00:01:37.680 --> 00:01:42.690
is very often physically isolated from the other parts of the cloud

00:01:42.690 --> 00:01:48.700
service provider's service offerings and it becomes a separate domain

00:01:48.700 --> 00:01:52.010
within that cloud providers facility,

00:01:52.250 --> 00:01:56.100
and it is there for the exclusive use of that consumer

00:01:56.100 --> 00:02:01.600
organization with its own perimeters, its own access controls,

00:02:01.600 --> 00:02:02.360
and so on.

00:02:04.440 --> 00:02:06.800
We also, of course, have the most common,

00:02:06.800 --> 00:02:07.980
the public cloud,

00:02:07.980 --> 00:02:12.660
something that almost everybody uses today, where we have a cloud

00:02:12.660 --> 00:02:17.620
infrastructure which is provisioned for open use by the general public,

00:02:17.630 --> 00:02:20.250
email services and so on.

00:02:20.940 --> 00:02:24.710
This exists on a premises of the cloud provider,

00:02:24.710 --> 00:02:26.390
and in fact, in most cases,

00:02:26.840 --> 00:02:31.270
the cloud consumer has no idea where their data is actually being kept.

00:02:31.280 --> 00:02:35.650
They don't know whether email physically is located or all of those

00:02:35.650 --> 00:02:38.000
pictures that were backed up off of their phone,

00:02:38.000 --> 00:02:38.810
for example.

00:02:40.340 --> 00:02:44.660
We also, of course, have where several organizations work together.

00:02:45.300 --> 00:02:49.430
This is a community cloud, and this has been done by universities,

00:02:49.430 --> 00:02:53.430
it's been done by hospitals, it's been done by government.

00:02:53.560 --> 00:03:00.930
The idea is that you have a cloud infrastructure which is provisioned,

00:03:00.930 --> 00:03:05.710
but only for a select group of organizations,

00:03:05.930 --> 00:03:10.190
maybe a specific community of consumers that very often

00:03:10.200 --> 00:03:12.690
have the same types of requirements.

00:03:13.280 --> 00:03:16.790
Two or three universities or two or three hospitals,

00:03:16.790 --> 00:03:18.700
for example, go together,

00:03:18.700 --> 00:03:21.710
and instead of each having their own separate data center,

00:03:21.840 --> 00:03:25.990
they have one shared data center because all three hospitals

00:03:25.990 --> 00:03:30.830
really have the same regulatory needs, the same types of policies,

00:03:30.830 --> 00:03:31.560
and so on.

00:03:32.040 --> 00:03:37.510
So therefore, a community cloud can operate for one of the universities,

00:03:37.510 --> 00:03:41.310
maybe it's even an onsite private private cloud,

00:03:41.320 --> 00:03:45.570
but for the other two universities or other two hospitals,

00:03:45.580 --> 00:03:49.760
it's an offsite private cloud, but it's,

00:03:49.770 --> 00:03:52.770
it's a community, the three of them work together,

00:03:52.770 --> 00:03:54.070
and of course,

00:03:54.070 --> 00:03:57.630
there are the advantages of the resource pooling

00:03:57.630 --> 00:04:01.460
and economies of scale and so on.

00:04:02.040 --> 00:04:06.650
Now it could well be that I gave you the example that of the three hospitals,

00:04:06.650 --> 00:04:08.220
one of them hosts the data center,

00:04:08.220 --> 00:04:12.840
but we also see other cases where that community was hosted by a

00:04:12.840 --> 00:04:15.660
third‑party cloud service provider as well.

00:04:16.640 --> 00:04:17.430
And of course,

00:04:17.430 --> 00:04:20.940
this could be either on the premises of one of the

00:04:20.950 --> 00:04:25.460
universities or hospitals or off‑premise altogether.

00:04:27.020 --> 00:04:29.960
The idea of an outsourced community cloud.

00:04:30.210 --> 00:04:33.870
We see that we have a number of different organizations that

00:04:33.870 --> 00:04:36.440
are similar on the right‑hand side here,

00:04:36.760 --> 00:04:40.330
community organizations, consuming cloud resources,

00:04:40.620 --> 00:04:44.360
each one has its own security perimeter,

00:04:44.360 --> 00:04:49.530
its own trusted area that it communicates through some type

00:04:49.530 --> 00:04:54.030
of access controls to the community cloud,

00:04:54.030 --> 00:04:55.050
which in this case,

00:04:55.050 --> 00:05:00.870
we're showing hosted as a cloud provider's facility that really operates,

00:05:00.870 --> 00:05:03.220
as we said, almost like a private cloud,

00:05:03.220 --> 00:05:06.420
except for the fact is for say, three companies in this case,

00:05:06.840 --> 00:05:10.390
but within that cloud providers facility.

00:05:12.040 --> 00:05:13.340
We also have the hybrid,

00:05:13.350 --> 00:05:16.850
which quite simply means we're not satisfied with any one of these,

00:05:16.850 --> 00:05:18.120
we use a combination.

00:05:18.640 --> 00:05:22.720
So a hybrid cloud is a composition of two or more distinct cloud

00:05:22.720 --> 00:05:25.900
infrastructures that operate as separate entities,

00:05:26.440 --> 00:05:31.270
but are bound together by standardized or proprietary technology.

00:05:31.840 --> 00:05:35.880
So this could be for the sake of business continuity,

00:05:35.880 --> 00:05:38.050
it could be, of course,

00:05:38.840 --> 00:05:44.540
that we have a couple of different infrastructures that operate and cooperate.

00:05:44.550 --> 00:05:47.880
We could say that even though they're separate entities,

00:05:47.910 --> 00:05:54.070
it's seamless often to the cloud consumer because the data can pass

00:05:54.070 --> 00:05:57.260
back and forth between them without any restrictions.

00:05:57.640 --> 00:06:02.400
So this allows what we called before cloud bursting where I

00:06:02.400 --> 00:06:06.230
can easily move some of my processing off to another

00:06:06.230 --> 00:06:08.660
facility and that's what we would, therefore,

00:06:08.660 --> 00:06:11.260
also therefore call data portability.

00:06:12.940 --> 00:06:15.880
We see here in a hybrid where we could have a

00:06:15.880 --> 00:06:21.310
combination of almost any of these, a combination of an onsite private cloud,

00:06:21.490 --> 00:06:25.790
an outsourced private cloud, an onsite community cloud,

00:06:25.790 --> 00:06:29.390
an outsource community cloud, or the public cloud.

00:06:29.390 --> 00:06:34.360
And so a hybrid is, as we said, two or more of these that work together.
