WEBVTT 1 00:00.000 --> 00:03.360 Up to this point, we've been covering software as a service, which are 2 00:03.360 --> 00:08.640 different services that we can access that's generally over a browser and think 3 00:08.640 --> 00:13.500 of along the lines of like Gmail or even social media to an extent. 4 00:13.500 --> 00:19.080 Then we went into platform as a service where we were expanding the usage of 5 00:19.080 --> 00:24.560 actual application modifications and management on our end as far as the 6 00:24.560 --> 00:26.500 clients responsibility is concerned. 7 00:26.500 --> 00:30.630 But all the servers and infrastructure that is behind the scenes is still WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:26.500 --> 00:30.630 But all the servers and infrastructure that is behind the scenes is still 8 00:30.630 --> 00:34.360 managed by the actual provider broken down into those two areas of 9 00:34.360 --> 00:38.000 responsibilities that we emphasized from the beginning. 10 00:38.000 --> 00:42.820 The clients responsibility and the providers responsibility well here we're 11 00:42.820 --> 00:46.000 moving more into the infrastructure as a service. 12 00:46.000 --> 00:49.910 Now this is getting very close to just saying you know what we're going to keep 13 00:49.910 --> 00:51.000 everything in house. 14 00:51.000 --> 00:55.400 But there is an advantage to infrastructure as a service and with those 15 00:55.400 --> 00:59.710 advantages also come security concerns which will be covering throughout the 16 00:59.710 --> 01:00.000 skill. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 01:00.000 --> 01:05.000 Because as we move into infrastructure as a service we're going to see that the 18 01:05.000 --> 01:10.740 responsibilities for the client meaning us vastly expands and the actual burden 19 01:10.740 --> 01:16.000 on the provider is far less than it's been before up to this point. 20 01:16.000 --> 01:19.670 Before the most we've had to worry about as far as you know technical abilities 21 01:19.670 --> 01:23.130 and make sure everything's maintained is the actual people in data and 22 01:23.130 --> 01:24.000 applications. 23 01:24.000 --> 01:28.200 Now we're expanding on into taking care of the actual runtime middleware 24 01:28.200 --> 01:32.610 operating system and virtual network with the provider being responsible for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:28.200 --> 01:32.610 operating system and virtual network with the provider being responsible for 25 01:32.610 --> 01:37.130 the actual hypervisor server storage and physical network of the overall 26 01:37.130 --> 01:38.000 infrastructure. 27 01:38.000 --> 01:41.810 Now you may be thinking that's a lot and where does that line get drawn at 28 01:41.810 --> 01:46.590 where we actually maintain physical equipment versus actual infrastructure 29 01:46.590 --> 01:49.000 equipment that's maintained by the provider. 30 01:49.000 --> 01:52.600 Well I'm glad you asked let's take a small look what we're taking a look at 31 01:52.600 --> 01:56.440 here is a normal server room environment think of these as different servers 32 01:56.440 --> 01:59.000 and all the networking components that are in here. 33 01:59.000 --> 02:03.300 Didn't want to go too far in the detail just kind of give a brief sketch of an WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:59.000 --> 02:03.300 Didn't want to go too far in the detail just kind of give a brief sketch of an 34 02:03.300 --> 02:04.000 overview. 35 02:04.000 --> 02:08.440 And if we maintained everything didn't utilize any client kind of cloud 36 02:08.440 --> 02:13.260 infrastructure this would be the setup that we would be required to have 37 02:13.260 --> 02:15.000 somewhere within our organization. 38 02:15.000 --> 02:19.340 It could be this one it could be multiple of these and being able to maintain 39 02:19.340 --> 02:23.680 something like this definitely increases the cost not only for the actual 40 02:23.680 --> 02:29.020 physical equipment but also for the actual maintenance of the equipment and 41 02:29.020 --> 02:32.350 making sure that the network connections between here and the other sites is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 02:29.020 --> 02:32.350 making sure that the network connections between here and the other sites is 42 02:32.350 --> 02:34.000 maintained as well. 43 02:34.000 --> 02:38.630 So when we go to infrastructure as a service this particular server room as we 44 02:38.630 --> 02:43.280 have on the screen right now basically turns into a cloud component for us but 45 02:43.280 --> 02:48.630 we have a lot of control over what goes on in the server room as far as being 46 02:48.630 --> 02:55.000 able to utilize the storage the memory the processing for our organization. 47 02:55.000 --> 02:59.290 See in infrastructure as a service there are multiple of these types of setups 48 02:59.290 --> 03:03.660 all throughout the cloud infrastructure which is why basically this is called WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 02:59.290 --> 03:03.660 all throughout the cloud infrastructure which is why basically this is called 49 03:03.660 --> 03:07.670 infrastructure as a service when we break down the components of it we're 50 03:07.670 --> 03:12.000 looking at actually the physical components that were in our diagram being the 51 03:12.000 --> 03:15.810 responsibility of the provider and the configuration of those components being 52 03:15.810 --> 03:17.000 our responsibility. 53 03:17.000 --> 03:21.670 Now there's a kind of a split off here and understanding that we kind of follow 54 03:21.670 --> 03:26.130 along with for how a virtual infrastructure is built up and I want to have a 55 03:26.130 --> 03:31.050 link below here to into some of the greater virtual infrastructure courses that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 55 03:26.130 --> 03:31.050 link below here to into some of the greater virtual infrastructure courses that 56 03:31.050 --> 03:36.000 we have here on CBT nuggets but know that when we have a server room like this 57 03:36.000 --> 03:40.330 and we have access for it under that infrastructure as a service there were 58 03:40.330 --> 03:43.880 actually utilizing the hardware that are at these different sites be it hosted 59 03:43.880 --> 03:46.000 by let's say Microsoft Azure 60 03:46.000 --> 03:50.800 AWS there are many different ones out there and when we take a look at what we 61 03:50.800 --> 03:55.850 're actually allowed to touch we're basically saying we're waiting on you the 62 03:55.850 --> 04:01.220 provider to install the physical hardware have that hardware back up ever done WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 03:55.850 --> 04:01.220 provider to install the physical hardware have that hardware back up ever done 63 04:01.220 --> 04:05.660 to see throughout your cloud network so we can load balance we can make sure 64 04:05.660 --> 04:09.720 that there's consistent access to it and then we'll take care of everything 65 04:09.720 --> 04:13.580 else as far as the configuration because once that type one or type two virtual 66 04:13.580 --> 04:15.000 ization is installed on hardware we have 67 04:15.000 --> 04:19.690 everything else and that includes maintaining things like the virtual network 68 04:19.690 --> 04:25.030 where we can expand and make different reliance we can go through and create 69 04:25.030 --> 04:30.000 different operating systems in that virtual environment such as server or work WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 04:30.000 --> 04:35.120 stations we can have dummy clients at the actual locations of our clients and 71 04:35.120 --> 04:39.170 have them just virtually connected to those operating systems that's in that 72 04:39.170 --> 04:41.000 cloud infrastructure. 73 04:41.000 --> 04:45.630 So far is to even house through the point of this entire domain Cisco 74 04:45.630 --> 04:51.170 environment inside of that infrastructure as a service environment and kind of 75 04:51.170 --> 04:54.320 do some of the other things that we did in the previous skill where we're 76 04:54.320 --> 04:59.400 looking at platform as a service more in depth inside of infrastructure as a 77 04:59.400 --> 05:00.000 service let's go ahead and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 78 05:00.000 --> 05:03.550 back into our sandbox environment and just take a look at some of the different 79 05:03.550 --> 05:06.550 services offered and how they would be different from platform to 80 05:06.550 --> 05:08.000 infrastructure as a service.