WEBVTT 1 00:00.000 --> 00:03.840 So we introduced everything and as far as infrastructure as they serve is in 2 00:03.840 --> 00:07.000 the basic concepts of what is all involved. 3 00:07.000 --> 00:11.000 In this particular video, I kind of want to dive more into the actual 4 00:11.000 --> 00:13.000 responsibilities that we mentioned previously 5 00:13.000 --> 00:16.650 and make sure that we have a firm understanding the split between our 6 00:16.650 --> 00:21.590 responsibility as a customer and the provider's responsibilities is maintaining 7 00:21.590 --> 00:23.000 the actual infrastructure. 8 00:23.000 --> 00:28.660 So as we take a look at our actual handy-dandy responsibility chart, we can see 9 00:28.660 --> 00:34.540 a lot of the cloud infrastructure as a service is split up more in our favor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:28.660 --> 00:34.540 a lot of the cloud infrastructure as a service is split up more in our favor 10 00:34.540 --> 00:35.000 this time. 11 00:35.000 --> 00:40.120 But this gives us an actual advantage over software as a service and platform 12 00:40.120 --> 00:41.000 as a service. 13 00:41.000 --> 00:46.000 As organizational admins, we can monitor usage to identify resource utilization 14 00:46.000 --> 00:46.000 . 15 00:46.000 --> 00:50.360 And this may be for things like cost to the actual organization itself, but 16 00:50.360 --> 00:55.010 less to do with cost in this particular skill, we're more focused on actual 17 00:55.010 --> 00:56.000 resources. 18 00:56.000 --> 01:00.090 If we look at the provider's responsibility, they cover the hypervisor, server, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 18 00:56.000 --> 01:00.090 If we look at the provider's responsibility, they cover the hypervisor, server, 19 01:00.090 --> 01:02.000 storage, and physical network. 20 01:02.000 --> 01:07.000 And this covers the CPUs, the RAM, the storage, etc. 21 01:07.000 --> 01:13.420 Whether it be physical network being expanded or even decreased in some cases 22 01:13.420 --> 01:17.000 based on a site shutting down or whatnot. 23 01:17.000 --> 01:22.720 We can actually go through and monitor everything in more detail than we can if 24 01:22.720 --> 01:26.000 we were in a platform or software as a service. 25 01:26.000 --> 01:31.290 Because in our responsibility, let's just use virtual network and operating WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 01:26.000 --> 01:31.290 Because in our responsibility, let's just use virtual network and operating 26 01:31.290 --> 01:35.560 system as an example. We can identify if we need additional nodes to be able to 27 01:35.560 --> 01:39.430 support the load balancing for some of the servers we have in that virtual 28 01:39.430 --> 01:43.000 network or operating system portion of our responsibility. 29 01:43.000 --> 01:47.330 And specifically with the actual virtual network, we can identify if we need 30 01:47.330 --> 01:51.460 more ingress and egress points for that load balancing connection for the 31 01:51.460 --> 01:54.000 actual clients utilizing our services. 32 01:54.000 --> 01:58.470 As a solid example, we may have a server that's in charge of processing 33 01:58.470 --> 02:03.000 financial information and doing all the purchasing for services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:58.470 --> 02:03.000 financial information and doing all the purchasing for services. 34 02:03.000 --> 02:07.970 And if that server for whatever reason is being tapped out because it doesn't 35 02:07.970 --> 02:13.190 have enough storage to store all the records or there's not enough RAM on it to 36 02:13.190 --> 02:17.000 be able to make it as quickly as possible within reason. 37 02:17.000 --> 02:21.730 We can make that request to the actual fighter to say add more physical 38 02:21.730 --> 02:27.000 components to make sure that we are getting the biggest bang for our buck. 39 02:27.000 --> 02:32.750 Now this also goes into understanding that because of this, the responsibility WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 02:27.000 --> 02:32.750 Now this also goes into understanding that because of this, the responsibility 40 02:32.750 --> 02:38.290 on us to be able to maintain different aspects of our responsibility portion 41 02:38.290 --> 02:39.000 increases. 42 02:39.000 --> 02:43.860 Because just as an example inside of operating system in platform or software 43 02:43.860 --> 02:48.620 as a service, the license scenes for actual operating systems is held to the 44 02:48.620 --> 02:50.000 actual provider. 45 02:50.000 --> 02:54.430 Now yes, that cost is set to us as the actual client and for us utilizing those 46 02:54.430 --> 02:56.000 different components. 47 02:56.000 --> 02:59.920 But when we get into infrastructure as a service and we're putting more servers 48 02:59.920 --> 03:05.530 out there, we're adding more clients, that directly falls on us and is a budget WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 02:59.920 --> 03:05.530 out there, we're adding more clients, that directly falls on us and is a budget 49 03:05.530 --> 03:08.000 ary measure that we have to keep a firm eye on. 50 03:08.000 --> 03:12.150 We'll see more of this inside of a couple of videos later on in the skill as we 51 03:12.150 --> 03:17.000 start diving into the different components and comparing from the last skill. 52 03:17.000 --> 03:21.220 Hopefully this looks a little bit familiar to you because this was in the last 53 03:21.220 --> 03:26.860 skill where we did our catalyst center connection and modeling out the platform 54 03:26.860 --> 03:28.000 as a service. 55 03:28.000 --> 03:32.680 I bring this up because in the platform as a service, these servers that you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 55 03:28.000 --> 03:32.680 I bring this up because in the platform as a service, these servers that you 56 03:32.680 --> 03:37.610 see here that we connected to were maintained by the actual infrastructure and 57 03:37.610 --> 03:40.000 the provider's responsibility. 58 03:40.000 --> 03:45.680 Now that we've taken on more responsibility in our role, these servers are 59 03:45.680 --> 03:50.860 going to be maintained by us, even though the physical hardware is still hosted 60 03:50.860 --> 03:52.000 by the provider. 61 03:52.000 --> 03:56.040 Now this means that as we're working throughout our network and providing those 62 03:56.040 --> 04:01.340 services in the Cisco environment, we have to monitor these and make sure that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 03:56.040 --> 04:01.340 services in the Cisco environment, we have to monitor these and make sure that 63 04:01.340 --> 04:06.050 their resources are within spec or if we need to request more or reutilize them 64 04:06.050 --> 04:11.960 somewhere else or how that agreement is with the actual infrastructure provider 65 04:11.960 --> 04:12.000 . 66 04:12.000 --> 04:17.410 So we maintain the licensee on these actual servers from an operating system 67 04:17.410 --> 04:23.080 standpoint instead of just an actual application or how many users and how much 68 04:23.080 --> 04:28.000 data that we're going to be stored within our actual environment. 69 04:28.000 --> 04:32.550 If in this infrastructure right here, we said we wanted to add let's say WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 04:28.000 --> 04:32.550 If in this infrastructure right here, we said we wanted to add let's say 70 04:32.550 --> 04:37.270 another modeling lab server to be able to represent the different network 71 04:37.270 --> 04:41.000 devices and throw up a different site somewhere else. 72 04:41.000 --> 04:45.540 We would actually have to go through and purchase that license and stand up 73 04:45.540 --> 04:50.360 that actual server from the operating system level within the actual virtual 74 04:50.360 --> 04:54.000 ization modeling, whether it be type one or type two. 75 04:54.000 --> 04:57.870 Now it's probably going to be type one because if we look in the actual 76 04:57.870 --> 05:01.000 providers responsibilities, we can see hypervisor. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 04:57.870 --> 05:01.000 providers responsibilities, we can see hypervisor. 77 05:01.000 --> 05:05.220 And again, if you follow that link above where we go into the intro to virtual 78 05:05.220 --> 05:09.830 ization here on CBT nuggets, that'll bring you more of a clearer picture of how 79 05:09.830 --> 05:14.000 that's actually modeled out and provided to actual clients for use.