WEBVTT 1 00:00.000 --> 00:07.980 So let's begin our discussion of cloud service models by taking just a moment 2 00:07.980 --> 00:08.760 to talk about, 3 00:08.760 --> 00:11.560 well, what that actually means. 4 00:11.560 --> 00:15.970 But after that, we're going to jump into our first example of our service 5 00:15.970 --> 00:16.840 models, which 6 00:16.840 --> 00:22.440 is the infrastructure as a service or IaaS. 7 00:22.440 --> 00:25.320 That's going to be the main focus of this video. 8 00:25.320 --> 00:27.400 We're going to focus in on what that means. 9 00:27.400 --> 00:34.520 And of course, we'll also provide some examples of IaaS services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:27.400 --> 00:34.520 And of course, we'll also provide some examples of IaaS services. 10 00:34.520 --> 00:39.490 So our main goal here is going to be to discuss these different service models 11 00:39.490 --> 00:40.400 that we have 12 00:40.400 --> 00:43.520 available to us in the cloud. 13 00:43.520 --> 00:49.020 Now of course, one of them is IaaS, which is our infrastructure as a service, 14 00:49.020 --> 00:49.280 clearly 15 00:49.280 --> 00:54.600 the topic of this video, but we have a few others coming up. 16 00:54.600 --> 00:59.540 So I think the main question to get out of the way here is really what is the 17 00:59.540 --> 01:00.080 service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 00:59.540 --> 01:00.080 service 18 01:00.080 --> 01:01.440 model. 19 01:01.440 --> 01:07.760 And quite simply, the service model is a way to indicate what services are 20 01:07.760 --> 01:08.840 being offered 21 01:08.840 --> 01:10.720 to the customer. 22 01:10.720 --> 01:17.140 Or another way to say that is it's like the demarcation point or the end of 23 01:17.140 --> 01:18.800 responsibility 24 01:18.800 --> 01:22.200 between the provider and the customer. 25 01:22.200 --> 01:28.320 So which aspects are the responsibility of which entity? 26 01:28.320 --> 01:33.600 Now let's make sure we're clear here on the difference between responsibility WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 01:28.320 --> 01:33.600 Now let's make sure we're clear here on the difference between responsibility 27 01:33.600 --> 01:35.360 and control. 28 01:35.360 --> 01:41.160 What we mean by this is let's just take Amazon AWS as an example. 29 01:41.160 --> 01:46.260 Let's say you roll out a VPC, you set up a server, you put in an internet 30 01:46.260 --> 01:47.440 gateway, and 31 01:47.440 --> 01:52.550 you give that server a public IP address or an elastic IP address, and that 32 01:52.550 --> 01:53.240 server is 33 01:53.240 --> 01:56.000 now reachable from the outside. 34 01:56.000 --> 02:00.560 All of those things I just said were yours to configure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:56.000 --> 02:00.560 All of those things I just said were yours to configure. 35 02:00.560 --> 02:02.360 You chose how to do that. 36 02:02.360 --> 02:06.080 You chose what to name those things, what kind of server to deploy. 37 02:06.080 --> 02:08.120 You chose all of those things. 38 02:08.120 --> 02:11.240 So you were in control of those things. 39 02:11.240 --> 02:12.880 You made that decision. 40 02:12.880 --> 02:17.820 However, at the end of the day, if something doesn't work in that environment, 41 02:17.820 --> 02:18.320 it's not 42 02:18.320 --> 02:20.200 your responsibility. 43 02:20.200 --> 02:23.680 You would have to contact AWS support. 44 02:23.680 --> 02:27.410 They're the ones actually responsible for making sure that all of that 45 02:27.410 --> 02:28.400 infrastructure 46 02:28.400 --> 02:30.360 is actually functioning. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 02:28.400 --> 02:30.360 is actually functioning. 47 02:30.360 --> 02:34.090 So yes, you're still of course going to have control because an environment we 48 02:34.090 --> 02:34.400 have 49 02:34.400 --> 02:37.720 don't control over would not be very useful. 50 02:37.720 --> 02:40.360 But we don't have the responsibility for it. 51 02:40.360 --> 02:42.840 That's the main difference with these service models. 52 02:42.840 --> 02:48.080 We want to talk about where that responsibility lies between the provider, what 53 02:48.080 --> 02:49.720 they're offering, 54 02:49.720 --> 02:56.760 and what the customer has that we can consume or partake in. 55 02:56.760 --> 03:03.630 So let's take a closer look at what that means for infrastructure as a service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 55 02:56.760 --> 03:03.630 So let's take a closer look at what that means for infrastructure as a service 56 03:03.630 --> 03:04.720 or IaaS. 57 03:04.720 --> 03:09.800 If we take a look at our diagram over here on the right, what we basically have 58 03:09.800 --> 03:10.000 is a 59 03:10.000 --> 03:17.000 demarcation point right here between operating system and virtualization. 60 03:17.000 --> 03:22.500 And what that means is all of these services here at the bottom are going to be 61 03:22.500 --> 03:23.240 handled 62 03:23.240 --> 03:25.240 by the service provider. 63 03:25.240 --> 03:30.910 The service provider is going to be responsible for providing the reliable WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 03:25.240 --> 03:30.910 The service provider is going to be responsible for providing the reliable 64 03:30.910 --> 03:32.000 networking, the 65 03:32.000 --> 03:36.280 reliable and restorable storage system. 66 03:36.280 --> 03:40.300 Of course, the actual servers themselves that everything is going to be running 67 03:40.300 --> 03:41.200 on and the 68 03:41.200 --> 03:46.680 virtualization platform that lets us run all of our virtual machines. 69 03:46.680 --> 03:50.680 These are all of the different services that are going to be the responsibility 70 03:50.680 --> 03:50.960 of the 71 03:50.960 --> 03:53.560 service provider themselves. 72 03:53.560 --> 03:57.760 Up at the top are all of the things that we as customers are going to have 73 03:57.760 --> 03:59.400 control over. 74 03:59.400 --> 04:04.340 So we're going to get to choose the operating system that we're going to run on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 74 03:59.400 --> 04:04.340 So we're going to get to choose the operating system that we're going to run on 75 04:04.340 --> 04:05.440 our servers, 76 04:05.440 --> 04:08.600 at least within the offerings of the cloud provider. 77 04:08.600 --> 04:13.050 But there is going to be a large variety of Linux based builds and Windows 78 04:13.050 --> 04:13.880 versions and 79 04:13.880 --> 04:16.640 such that we can choose to run. 80 04:16.640 --> 04:20.120 We then of course choose what software. 81 04:20.120 --> 04:24.970 So the middleware, the runtime environments that are needed to support that 82 04:24.970 --> 04:25.800 software, 83 04:25.800 --> 04:31.050 of course what data itself is going to be on these servers and the final WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 04:25.800 --> 04:31.050 of course what data itself is going to be on these servers and the final 84 04:31.050 --> 04:32.120 applications 85 04:32.120 --> 04:35.920 that are going to be running on these various devices. 86 04:35.920 --> 04:38.880 But the main thing here is that we have control of everything from the 87 04:38.880 --> 04:40.680 operating system up. 88 04:40.680 --> 04:45.080 So all of the software, everything we need to make these servers function the 89 04:45.080 --> 04:45.560 way we 90 04:45.560 --> 04:47.080 want them to. 91 04:47.080 --> 04:52.440 So that means that as the customer, we can provision the processing power. 92 04:52.440 --> 04:58.000 So in other words, choosing the servers themselves, we can choose the storage. 93 04:58.000 --> 05:01.700 There are generally different types of storage offered, usually offering WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 04:58.000 --> 05:01.700 There are generally different types of storage offered, usually offering 94 05:01.700 --> 05:02.640 different levels 95 05:02.640 --> 05:06.120 of protection at different price points and so on. 96 05:06.120 --> 05:11.050 We of course can provision our networking, how we want our networking to be run 97 05:11.050 --> 05:11.640 and what 98 05:11.640 --> 05:14.520 different security features we wish to use. 99 05:14.520 --> 05:20.290 For example, do we want to implement a software firewall or do we not want to 100 05:20.290 --> 05:21.320 and so on? 101 05:21.320 --> 05:24.040 These are all things that we can choose. 102 05:24.040 --> 05:28.950 It's also important to note that as the customer, we can choose any software 103 05:28.950 --> 05:29.800 that we want to 104 05:29.800 --> 05:30.800 run. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 104 05:29.800 --> 05:30.800 run. 105 05:30.800 --> 05:36.420 Again, we're responsible for everything from the operating system up to the end 106 05:36.420 --> 05:37.640 application, 107 05:37.640 --> 05:42.760 which means we're the ones making the choice as far as what to run on this 108 05:42.760 --> 05:43.640 server. 109 05:43.640 --> 05:48.560 Now again, we may have a limited subset choice of operating system. 110 05:48.560 --> 05:54.070 We can't necessarily go to Amazon and choose to deploy any virtual machine we 111 05:54.070 --> 05:54.720 want. 112 05:54.720 --> 05:56.080 They have choices. 113 05:56.080 --> 06:00.400 You can customize those choices, but we generally have to build on the baseline WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 113 05:56.080 --> 06:00.400 You can customize those choices, but we generally have to build on the baseline 114 06:00.400 --> 06:01.000 of what they 115 06:01.000 --> 06:02.240 offer. 116 06:02.240 --> 06:06.000 But the flip side of that is it's a rather complete list. 117 06:06.000 --> 06:11.840 Now again, what we do not have access to is the actual infrastructure. 118 06:11.840 --> 06:14.200 So that's all of this down here. 119 06:14.200 --> 06:20.760 And of course, we do have control over what we choose to deploy and really how 120 06:20.760 --> 06:21.480 that is 121 06:21.480 --> 06:23.800 going to ultimately be configured. 122 06:23.800 --> 06:27.160 But it's of course going to be configured through automation. 123 06:27.160 --> 06:32.340 So what we don't have is direct access and or responsibility for everything WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 123 06:27.160 --> 06:32.340 So what we don't have is direct access and or responsibility for everything 124 06:32.340 --> 06:33.160 below this 125 06:33.160 --> 06:35.160 demarcation point. 126 06:35.160 --> 06:40.080 So let's take a closer look at some of the IaaS characteristics. 127 06:40.080 --> 06:45.570 Some of those characteristics are first, this operates much like a utility 128 06:45.570 --> 06:46.520 company. 129 06:46.520 --> 06:51.720 You're paying for a service and you get a monthly bill, much like you would 130 06:51.720 --> 06:52.360 your phone 131 06:52.360 --> 06:54.520 bill or your electric bill. 132 06:54.520 --> 06:56.440 It works very much the same way. 133 06:56.440 --> 06:59.760 You're going to get billed for the services you choose to use. 134 06:59.760 --> 07:04.040 And of course, as we've mentioned in previous skills, this is a pay as you go WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 134 06:59.760 --> 07:04.040 And of course, as we've mentioned in previous skills, this is a pay as you go 135 07:04.040 --> 07:04.720 model. 136 07:04.720 --> 07:08.460 So of course, that could definitely vary from month to month, but you're going 137 07:08.460 --> 07:09.360 to get billed 138 07:09.360 --> 07:11.640 based on what you've used. 139 07:11.640 --> 07:15.000 And we did already sort of mention that all of this is automated. 140 07:15.000 --> 07:18.970 So again, when you go to these cloud providers and you tell it to deploy a 141 07:18.970 --> 07:20.120 virtual machine, 142 07:20.120 --> 07:22.600 you're not actually going to be doing that. 143 07:22.600 --> 07:27.340 You're simply going to choose a couple buttons, hit go, and the back end 144 07:27.340 --> 07:28.760 through automation 145 07:28.760 --> 07:31.960 is going to build all of that for you. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 145 07:28.760 --> 07:31.960 is going to build all of that for you. 146 07:31.960 --> 07:35.910 One of the other big characteristics and one of the big selling points of cloud 147 07:35.910 --> 07:36.120 is the 148 07:36.120 --> 07:38.160 dynamic scaling. 149 07:38.160 --> 07:43.840 This is virtually unlimited or infinite scaling. 150 07:43.840 --> 07:49.000 Now of course, there's actually no such thing as unlimited resources. 151 07:49.000 --> 07:52.840 At some point, this scaling is technically finite. 152 07:52.840 --> 07:58.650 However, for all intents and purposes, for the purposes of most companies, 153 07:58.650 --> 07:59.240 obviously 154 07:59.240 --> 08:05.680 you're big providers such as Amazon, Microsoft, Google, IBM and so on. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 154 07:59.240 --> 08:05.680 you're big providers such as Amazon, Microsoft, Google, IBM and so on. 155 08:05.680 --> 08:11.480 They all have far more resources than any one single company would use. 156 08:11.480 --> 08:17.490 Therefore, from the company where the customer's perspective, it's virtually 157 08:17.490 --> 08:17.840 infinite. 158 08:17.840 --> 08:23.680 And of course, with this option, we can always choose to scale up or we could 159 08:23.680 --> 08:24.720 also choose 160 08:24.720 --> 08:26.560 to scale out. 161 08:26.560 --> 08:30.030 And simply what that means, if we're going to scale up, it means we're going to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 161 08:26.560 --> 08:30.030 And simply what that means, if we're going to scale up, it means we're going to 162 08:30.030 --> 08:31.080 run bigger 163 08:31.080 --> 08:34.320 servers, maybe more CPU, more RAM. 164 08:34.320 --> 08:40.100 Obviously, all of these providers have multiple tiers of servers you can choose 165 08:40.100 --> 08:40.640 from, or you 166 08:40.640 --> 08:44.200 could scale out by running more servers. 167 08:44.200 --> 08:49.280 So either one of these options are available with IaaS. 168 08:49.280 --> 08:53.640 We also support things such as desktop virtualization. 169 08:53.640 --> 08:55.840 We support policy-based services. 170 08:55.840 --> 09:00.530 We'll be talking about policy-based services in more detail a little bit later WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 170 08:55.840 --> 09:00.530 We'll be talking about policy-based services in more detail a little bit later 171 09:00.530 --> 09:02.360 in the course. 172 09:02.360 --> 09:05.640 And of course, all of this is going to be available through internet 173 09:05.640 --> 09:06.600 connectivity so 174 09:06.600 --> 09:10.400 that these services can be reached through the internet. 175 09:10.400 --> 09:14.930 We can either have customers access these resources directly if we choose to, 176 09:14.930 --> 09:15.240 or we 177 09:15.240 --> 09:21.080 could just make it available to internal employees through our WAN services. 178 09:21.080 --> 09:24.350 So we have different ways that we can manage this, of course, but internet 179 09:24.350 --> 09:25.080 connectivity 180 09:25.080 --> 09:27.960 is always, of course, going to be a big part of that. 181 09:27.960 --> 09:32.920 Finally, let's wrap up with some examples of IaaS. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 181 09:27.960 --> 09:32.920 Finally, let's wrap up with some examples of IaaS. 182 09:32.920 --> 09:39.030 One of the biggest ones, of course, is going to be Amazon's AWS or Amazon Web 183 09:39.030 --> 09:39.960 Services, 184 09:39.960 --> 09:44.760 which of course offers all of the services we've been discussing so far. 185 09:44.760 --> 09:46.880 As does Microsoft Azure. 186 09:46.880 --> 09:52.120 This is, of course, very similar in options to Amazon Web Services. 187 09:52.120 --> 09:54.280 There's also IBM Cloud. 188 09:54.280 --> 09:59.160 They offer many services as well, as does the Google Compute Engine or Google 189 09:59.160 --> 10:01.640 Cloud Services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 189 09:59.160 --> 10:01.640 Cloud Services. 190 10:01.640 --> 10:06.240 Oracle also has an offering, the Oracle Cloud Infrastructure. 191 10:06.240 --> 10:10.240 And honestly, there's many more. 192 10:10.240 --> 10:17.220 So the main takeaway here should be that IaaS is probably the cloud service 193 10:17.220 --> 10:18.240 model that 194 10:18.240 --> 10:23.840 most of us in IT think of when we talk about the cloud. 195 10:23.840 --> 10:29.370 We're running our servers in the cloud with the storage, of course, any form of 196 10:29.370 --> 10:30.040 security, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 196 10:29.370 --> 10:30.040 security, 197 10:30.040 --> 10:32.080 such as software firewalls. 198 10:32.080 --> 10:37.320 All of this stuff is running in the service provider's infrastructure. 199 10:37.320 --> 10:42.340 There are times, however, where we don't necessarily want all this control 200 10:42.340 --> 10:43.120 simply because 201 10:43.120 --> 10:46.990 it means we have to build and maintain all of the things that we've discussed 202 10:46.990 --> 10:47.440 in this 203 10:47.440 --> 10:48.800 video. 204 10:48.800 --> 10:54.190 Sometimes we may want the provider to actually be responsible for more of this 205 10:54.190 --> 10:54.960 offering. 206 10:54.960 --> 10:59.280 And that is where things like platform as a service come into play. 207 10:59.280 --> 11:01.400 And that's what we're going to be discussing next. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 207 10:59.280 --> 11:01.400 And that's what we're going to be discussing next.