WEBVTT

1
00:00.000 --> 00:09.240
So now that we understand the pros and cons of both private and public clouds,

2
00:09.240 --> 00:14.360
now let's take a look at the other three models defined by NIST,

3
00:14.360 --> 00:20.200
which are the community cloud, the hybrid cloud, and multi-cloud.

4
00:20.200 --> 00:22.320
Let's go ahead and get started.

5
00:22.320 --> 00:28.600
So let's start by taking a look here at community cloud.

6
00:28.600 --> 00:32.600
This is honestly probably not our most popular model.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

6
00:28.600 --> 00:32.600
This is honestly probably not our most popular model.

7
00:32.600 --> 00:39.600
This is a cloud that's being used by more than one organization.

8
00:39.600 --> 00:45.600
So a shared cloud, if you will, but not public.

9
00:45.600 --> 00:51.600
This again can be managed either by one or more organizations, again,

10
00:51.600 --> 00:54.600
maybe a third party or both.

11
00:54.600 --> 01:00.600
And again, this could be located on-prem, off-prem, or both.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:54.600 --> 01:00.600
And again, this could be located on-prem, off-prem, or both.

12
01:00.600 --> 01:06.600
Now again, I haven't seen this model implemented very often.

13
01:06.600 --> 01:10.600
The only example that I could actually think of off the top of my head

14
01:10.600 --> 01:15.600
that would sort of fit this model, and I'm not even 100% sure that it does.

15
01:15.600 --> 01:19.600
But I have a friend of mine who works for a private school.

16
01:19.600 --> 01:23.600
They work with a company called Blackbod.

17
01:23.600 --> 01:30.600
Blackbod provides database and let's say school and student management software
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
01:23.600 --> 01:30.600
Blackbod provides database and let's say school and student management software

18
01:30.600 --> 01:34.600
for small private schools and colleges.

19
01:34.600 --> 01:36.600
That's sort of their niche market.

20
01:36.600 --> 01:44.280
So if you were a medical center, you probably would have no use whatsoever for

21
01:44.280 --> 01:45.600
Blackbod.

22
01:45.600 --> 01:50.600
It's specifically designed for small educational facilities.

23
01:50.600 --> 01:54.600
And maybe large facilities at this point, I haven't looked at their product

24
01:54.600 --> 01:56.600
offerings for a while to be fair.

25
01:56.600 --> 02:01.560
But all of it's cloud-based and it's really sort of meant for the education
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:56.600 --> 02:01.560
But all of it's cloud-based and it's really sort of meant for the education

26
02:01.560 --> 02:02.600
community.

27
02:02.600 --> 02:06.600
So there's definitely more than one company and organization using it.

28
02:06.600 --> 02:12.600
Again, where I'm not 100% sure that it fits this model is, I guess, technically

29
02:12.600 --> 02:15.600
anybody could sign up for it.

30
02:15.600 --> 02:20.600
I don't think that they necessarily restrict it to only educational facilities.

31
02:20.600 --> 02:26.390
So I'm not necessarily sure that that completely fits this model, but again, it

32
02:26.390 --> 02:28.600
's the closest thing I could think of.

33
02:28.600 --> 02:32.600
Like I said, not exactly the most popular model.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
02:28.600 --> 02:32.600
Like I said, not exactly the most popular model.

34
02:32.600 --> 02:37.530
In fact, honestly, in a lot of Cisco's documentation, they've stopped even

35
02:37.530 --> 02:38.600
mentioning this one.

36
02:38.600 --> 02:43.600
But you should at least be aware of it and know that it's a model that exists.

37
02:43.600 --> 02:50.600
Now, opposite of that, probably the most popular model is the hybrid cloud.

38
02:50.600 --> 02:56.600
Hybrid cloud is simply any combination of the above models.

39
02:56.600 --> 03:03.600
Of course, the most common being to combine public and private clouds.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
02:56.600 --> 03:03.600
Of course, the most common being to combine public and private clouds.

40
03:03.600 --> 03:05.600
I do this every day.

41
03:05.600 --> 03:13.970
Just as another example, I use Dropbox and Microsoft OneDrive all of the time

42
03:13.970 --> 03:16.600
as a cloud file service.

43
03:16.600 --> 03:21.600
However, that doesn't work so well for doing things like video editing.

44
03:21.600 --> 03:28.600
So if I'm doing video editing, I actually use my NAS inside my own house.

45
03:28.600 --> 03:37.110
I have a Synology NAS and that NAS comes with a feature very similar to Dropbox
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
03:28.600 --> 03:37.110
I have a Synology NAS and that NAS comes with a feature very similar to Dropbox

46
03:37.110 --> 03:43.420
and OneDrive in that you install this software called Synology Drive on your

47
03:43.420 --> 03:44.600
computers.

48
03:44.600 --> 03:49.600
And it adds folder synchronization to your Synology NAS.

49
03:49.600 --> 03:54.640
So again, it's working just like Dropbox and OneDrive, except the data never

50
03:54.640 --> 03:55.600
leaves my house.

51
03:55.600 --> 03:57.600
It's stored here on the NAS.

52
03:57.600 --> 04:00.600
So that's more like a private cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
03:57.600 --> 04:00.600
So that's more like a private cloud.

53
04:00.600 --> 04:06.510
So once again, just by using those three products, that is a combination of

54
04:06.510 --> 04:11.600
public and private cloud, making it effectively a hybrid model.

55
04:11.600 --> 04:16.490
Another popular use of this model, aside from again, just using features like I

56
04:16.490 --> 04:22.720
just mentioned, is we can also use this for cloud bursting and or high

57
04:22.720 --> 04:24.600
availability.

58
04:24.600 --> 04:31.180
So again, you can use this to back up your devices as a secondary, or if your
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
04:24.600 --> 04:31.180
So again, you can use this to back up your devices as a secondary, or if your

59
04:31.180 --> 04:38.230
private cloud gets too busy, you can burst out onto the public cloud, use some

60
04:38.230 --> 04:43.810
resources from a cloud provider to supplement the service you're already

61
04:43.810 --> 04:44.600
offering.

62
04:44.600 --> 04:50.870
And of course, the reason this is so nice is you get to take advantage of the

63
04:50.870 --> 04:54.600
pros or the advantages from each model.

64
04:54.600 --> 05:01.430
So to summarize, I would say that hybrid cloud is probably used by the majority
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
04:54.600 --> 05:01.430
So to summarize, I would say that hybrid cloud is probably used by the majority

65
05:01.430 --> 05:03.600
of companies out there.

66
05:03.600 --> 05:09.780
They probably have some things that they keep on prem or in house in a private

67
05:09.780 --> 05:15.610
cloud, and they probably take advantage of the public cloud and public cloud

68
05:15.610 --> 05:16.600
services.

69
05:16.600 --> 05:20.600
Now the final model is multi cloud.

70
05:20.600 --> 05:26.600
This, of course, is gaining in popularity, and this can also still be hybrid.

71
05:26.600 --> 05:33.110
You can have the hybrid cloud with multi cloud, because all multi cloud really
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
05:26.600 --> 05:33.110
You can have the hybrid cloud with multi cloud, because all multi cloud really

72
05:33.110 --> 05:39.600
is, is the use of two or more public cloud providers.

73
05:39.600 --> 05:43.600
So maybe you don't just work with Amazon.

74
05:43.600 --> 05:49.250
Maybe you also work with Google, or maybe you use Microsoft and Google, or

75
05:49.250 --> 05:51.600
maybe you use IBM and Microsoft.

76
05:51.600 --> 05:55.760
There's a lot of different cloud providers out there. When we start talking

77
05:55.760 --> 06:01.320
about our cloud service models, you're probably going to find out that you're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
05:55.760 --> 06:01.320
about our cloud service models, you're probably going to find out that you're

78
06:01.320 --> 06:03.600
probably doing this already.

79
06:03.600 --> 06:10.280
I sort of already mentioned it. For example, I use Microsoft OneDrive and

80
06:10.280 --> 06:11.600
Dropbox.

81
06:11.600 --> 06:16.600
Well, that's two public cloud providers.

82
06:16.600 --> 06:22.780
Now with multi cloud, they're not necessarily just referring to using end user

83
06:22.780 --> 06:26.600
applications, such as OneDrive and Dropbox.

84
06:26.600 --> 06:32.660
They're generally referring more to you having servers running in the cloud at
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
06:26.600 --> 06:32.660
They're generally referring more to you having servers running in the cloud at

85
06:32.660 --> 06:34.600
multiple providers.

86
06:34.600 --> 06:40.270
But nonetheless, multi cloud is simply using two or more public cloud providers

87
06:40.270 --> 06:40.600
.

88
06:40.600 --> 06:44.600
This also provides for no vendor lock in.

89
06:44.600 --> 06:48.980
The advantage to this, of course, is maybe one of your cloud providers changes

90
06:48.980 --> 06:53.910
the policy you don't like, or changes their billing to a model that doesn't fit

91
06:53.910 --> 06:54.600
yours.

92
06:54.600 --> 06:58.600
You can move to another cloud provider and move all your resources.

93
06:58.600 --> 07:03.240
You have things already running on another cloud provider, then you can run off
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
06:58.600 --> 07:03.240
You have things already running on another cloud provider, then you can run off

94
07:03.240 --> 07:07.020
of those things while you move the other stuff to another provider. So, it

95
07:07.020 --> 07:10.600
gives us a lot of flexibility and no vendor lock in.

96
07:10.600 --> 07:15.890
Of course, it also gives redundancy in case any of those providers were to go

97
07:15.890 --> 07:16.600
down.

98
07:16.600 --> 07:23.600
It's incredibly rare. However, I do recall several years back now.

99
07:23.600 --> 07:30.890
Amazon AWS went offline for if memory serves, I believe it was six to eight
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
07:23.600 --> 07:30.890
Amazon AWS went offline for if memory serves, I believe it was six to eight

100
07:30.890 --> 07:31.600
hours.

101
07:31.600 --> 07:37.600
And that took down thousands of businesses, not only here in the United States,

102
07:37.600 --> 07:39.600
but around the world.

103
07:39.600 --> 07:45.600
Again, is it incredibly rare for a cloud provider to go offline? Absolutely.

104
07:45.600 --> 07:47.600
Let's make sure we're clear on that.

105
07:47.600 --> 07:53.790
However, if it were to happen, multi cloud can help us by staying up with our

106
07:53.790 --> 07:56.600
resources on a different cloud vendor.

107
07:56.600 --> 08:02.920
And I did sort of already mention this, that it can also include on-prem data
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
07:56.600 --> 08:02.920
And I did sort of already mention this, that it can also include on-prem data

108
08:02.920 --> 08:06.600
centers or co location data centers.

109
08:06.600 --> 08:10.600
This is sort of what I meant by it can still be a hybrid.

110
08:10.600 --> 08:18.130
So maybe I use a on-site data center and resources at Amazon and resources at

111
08:18.130 --> 08:19.600
Microsoft.

112
08:19.600 --> 08:25.600
And again, it can be more. Maybe I also use Google and I also use IBM.

113
08:25.600 --> 08:31.650
So there's a lot of providers out there and we can use any and all of the ones
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
08:25.600 --> 08:31.650
So there's a lot of providers out there and we can use any and all of the ones

114
08:31.650 --> 08:32.600
we need.

115
08:32.600 --> 08:36.260
But if you're really, really connecting to multiple data centers, then we're

116
08:36.260 --> 08:42.600
going to generally refer to that as multi cloud or hybrid multi cloud.

117
08:42.600 --> 08:46.600
So clearly, there were quite a few different models we had to discuss here.

118
08:46.600 --> 08:52.350
So just as a review, remember, we talked about the private cloud, which is a

119
08:52.350 --> 08:55.600
cloud being used by a single customer.

120
08:55.600 --> 09:00.330
We talked about public cloud, which is, of course, a cloud being used by the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
08:55.600 --> 09:00.330
We talked about public cloud, which is, of course, a cloud being used by the

121
09:00.330 --> 09:01.600
general public.

122
09:01.600 --> 09:06.600
These would be the major providers that most people have probably heard of.

123
09:06.600 --> 09:12.200
Then we had a community cloud, which again, probably not that popular, but it's

124
09:12.200 --> 09:16.600
a cloud that's being used by multiple different companies.

125
09:16.600 --> 09:21.780
Then we talked about the hybrid cloud, which is again, probably one of the most

126
09:21.780 --> 09:27.040
popular models where you're using any combination of those, which again, this

127
09:27.040 --> 09:33.350
could be either private, public community, or even our last choice, multi cloud
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
09:27.040 --> 09:33.350
could be either private, public community, or even our last choice, multi cloud

128
09:33.350 --> 09:33.600
.

129
09:33.600 --> 09:39.540
So multi cloud again is using multiple public cloud providers, and that could

130
09:39.540 --> 09:44.600
also be hybrid because that can also be included with private cloud.

131
09:44.600 --> 09:49.600
So we can use private with multi cloud, making it a hybrid multi cloud.

132
09:49.600 --> 09:54.600
So that concludes everything that we need to discuss in this skill.

133
09:54.600 --> 09:57.600
That leaves us with just the challenge.

134
09:57.600 --> 10:01.600
So I'll see you in the solution video after the challenge.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
09:57.600 --> 10:01.600
So I'll see you in the solution video after the challenge.

135
10:01.600 --> 10:11.600
[BLANK_AUDIO]