WEBVTT 1 00:00.000 --> 00:03.480 So our problem needs to be solved here. 2 00:03.480 --> 00:07.680 And the problem really stems around the fact that if I'm going to deploy a set 3 00:07.680 --> 00:12.080 of hardware that I can only deploy a single operating system instance and 4 00:12.080 --> 00:16.120 therefore single application per set of hardware. 5 00:16.120 --> 00:20.360 And so this is where we're going to introduce virtualization. 6 00:20.360 --> 00:24.680 Virtualization is going to break up one of these relationships. 7 00:24.680 --> 00:29.240 Now, we're not going to be able to escape this application to OS mapping. 8 00:29.240 --> 00:33.510 We need to have a one-to-one relationship between our applications and our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:29.240 --> 00:33.510 We need to have a one-to-one relationship between our applications and our 9 00:33.510 --> 00:34.520 operating systems. 10 00:34.520 --> 00:39.170 And again, we see why with, for example, the ports, if two different 11 00:39.170 --> 00:45.220 applications need to use the HTTP or HTTPS port, then we can't really change 12 00:45.220 --> 00:46.320 this relationship. 13 00:46.320 --> 00:49.440 There are a lot of hard limits associated with this. 14 00:49.440 --> 00:55.900 But what we can change is the relationship between our operating system and our 15 00:55.900 --> 00:56.960 hardware. 16 00:56.960 --> 01:00.970 In fact, we could make it so that we could put multiple operating system WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:56.960 --> 01:00.970 In fact, we could make it so that we could put multiple operating system 17 01:00.970 --> 01:03.520 instances all on the same hardware. 18 01:03.520 --> 01:07.240 And that's exactly what virtualization is designed to do. 19 01:07.240 --> 01:11.680 So now what we have is we have a set of hardware. 20 01:11.680 --> 01:19.240 So this is still all of our CPU and our memory, our RAM, our disks, everything 21 01:19.240 --> 01:23.760 here, all of the normal hardware components of a server. 22 01:23.760 --> 01:32.100 And now we're going to install multiple operating system instances here on this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 01:23.760 --> 01:32.100 And now we're going to install multiple operating system instances here on this 23 01:32.100 --> 01:33.520 hardware. 24 01:33.520 --> 01:37.380 And because we still have to maintain this one-to-one relationship between our 25 01:37.380 --> 01:42.990 applications and our operating systems, we're going to deploy one at a time 26 01:42.990 --> 01:43.880 here. 27 01:43.880 --> 01:48.710 But what we see is even though it's one-to-one with the operating system, now 28 01:48.710 --> 01:53.520 we can deploy many applications on a single set of hardware. 29 01:53.520 --> 01:57.710 So we're maintaining the important relationships, but we're kind of breaking 30 01:57.710 --> 02:00.480 the rules where we're able to break the rules. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 30 01:57.710 --> 02:00.480 the rules where we're able to break the rules. 31 02:00.480 --> 02:03.000 So how exactly do we go about doing this? 32 02:03.000 --> 02:08.010 Well, we can't actually just directly deploy multiple operating systems onto 33 02:08.010 --> 02:08.880 hardware. 34 02:08.880 --> 02:11.480 That would kind of break the rules a little bit. 35 02:11.480 --> 02:17.440 So instead what we're going to do is we're going to split off the hardware from 36 02:17.440 --> 02:18.720 the operating system. 37 02:18.720 --> 02:21.840 We're going to insert something into the middle here. 38 02:21.840 --> 02:28.520 So we're going to insert is a set of software known as a hypervisor. 39 02:28.520 --> 02:35.950 This hypervisor is essentially sort of a new operating system, but it's called WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 02:28.520 --> 02:35.950 This hypervisor is essentially sort of a new operating system, but it's called 40 02:35.950 --> 02:41.240 a hypervisor because it's managing multiple operating systems. 41 02:41.240 --> 02:45.280 We don't just want to call this an operating system, but rather it's a set of 42 02:45.280 --> 02:51.800 software that exists between the operating system and the hardware down here. 43 02:51.800 --> 02:56.590 So we take a piece of hardware, a bare metal server, if we want to think of it 44 02:56.590 --> 02:59.080 that way, and we're going to install something onto it. 45 02:59.080 --> 03:00.880 Well, we install a hypervisor onto it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 02:59.080 --> 03:00.880 Well, we install a hypervisor onto it. 46 03:00.880 --> 03:06.940 And now the hypervisor allows me to install individual operating systems, which 47 03:06.940 --> 03:09.400 can run individual applications. 48 03:09.400 --> 03:17.080 These become known as guests that are running on a host. 49 03:17.080 --> 03:22.360 So we have virtual guests and we have virtual hosts. 50 03:22.360 --> 03:27.350 This is an important method of distinction because both of these concepts could 51 03:27.350 --> 03:28.200 be a server. 52 03:28.200 --> 03:30.360 If we think about it, what is a server now? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 03:28.200 --> 03:30.360 If we think about it, what is a server now? 53 03:30.360 --> 03:34.230 Is the server the physical set of hardware, the CPU and the memory and 54 03:34.230 --> 03:35.000 everything? 55 03:35.000 --> 03:38.920 Or is the server the operating system instance? 56 03:38.920 --> 03:44.200 And the answer is yes, which is a weird answer, but the answer is really both. 57 03:44.200 --> 03:48.040 Both of these are servers. We have a virtual server and we have a physical 58 03:48.040 --> 03:51.560 server, but we don't want to use the same word to describe both of them. 59 03:51.560 --> 03:55.200 So we're going to call a virtual host and a virtual guest. 60 03:55.200 --> 03:58.830 Now, I will say this in our industry, even though these are technically the 61 03:58.830 --> 04:03.240 correct terms, we don't usually see this word guest be referenced very often. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 03:58.830 --> 04:03.240 correct terms, we don't usually see this word guest be referenced very often. 62 04:03.240 --> 04:13.640 And instead, what we see is a reference to a virtual machine or VM. 63 04:13.640 --> 04:18.440 So usually, we will say, hey, a virtual host in this term is used quite a bit. 64 04:18.440 --> 04:24.930 This virtual host is hosting maybe 10 or 15 different virtual machines rather 65 04:24.930 --> 04:25.960 than virtual guests. 66 04:25.960 --> 04:29.000 Although if you do hear it, now you know what we're talking about. 67 04:29.000 --> 04:32.990 So we have the relationship of hosting guest where the VM is the guest and the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 67 04:29.000 --> 04:32.990 So we have the relationship of hosting guest where the VM is the guest and the 68 04:32.990 --> 04:35.080 physical server is the host. 69 04:35.080 --> 04:41.150 And if we think about it, we're going to need some amount of networking between 70 04:41.150 --> 04:43.720 and among all of these virtual machines. 71 04:43.720 --> 04:47.400 And we'll talk about this coming up here shortly. So stay tuned. 72 04:47.400 --> 04:51.950 Now, on the blueprint directly, we are going to see that Cisco is going to ask 73 04:51.950 --> 04:56.640 us to understand the two different hypervisor types. 74 04:56.640 --> 04:59.440 So let's talk about those really quickly. 75 04:59.440 --> 05:02.440 First of all, we have type one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 75 04:59.440 --> 05:02.440 First of all, we have type one. 76 05:02.440 --> 05:07.310 And then we also have a type two. Now the type one hypervisor is installed 77 05:07.310 --> 05:09.240 directly. 78 05:09.240 --> 05:12.360 On to hardware. 79 05:12.360 --> 05:19.120 And so this is when we say that the hypervisor is sort of like an operating 80 05:19.120 --> 05:19.640 system. 81 05:19.640 --> 05:24.120 Used air quotes here on purpose to say it's not really an operating system, but 82 05:24.120 --> 05:27.430 it kind of feels like one because we take hardware and we install the hyper 83 05:27.430 --> 05:29.880 visor directly onto the hardware. 84 05:29.880 --> 05:35.000 At this point, we are going to install virtual machines onto the hypervisor, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 84 05:29.880 --> 05:35.000 At this point, we are going to install virtual machines onto the hypervisor, 85 05:35.000 --> 05:40.760 but everything here with type one is exactly how we've got it drawn out here. 86 05:40.760 --> 05:44.280 Meanwhile, we also have a type two. 87 05:44.280 --> 05:51.640 And the type two is primarily intended for maybe personal use labs development 88 05:51.640 --> 05:53.400 if we're developers. 89 05:53.400 --> 06:00.720 But the idea here is that the hypervisor is installed onto an operating system WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 05:53.400 --> 06:00.720 But the idea here is that the hypervisor is installed onto an operating system 90 06:00.720 --> 06:04.320 as an application. 91 06:04.320 --> 06:10.000 Meaning that maybe I've got a laptop and I'm running Windows on this laptop and 92 06:10.000 --> 06:17.200 I install an application here that can run virtual machines. 93 06:17.200 --> 06:21.430 Now there are several different hypervisors in the industry that fall into both 94 06:21.430 --> 06:22.600 of these categories. 95 06:22.600 --> 06:26.550 And keep in mind type ones, these are usually what we're going to see used in 96 06:26.550 --> 06:28.040 our enterprise space. 97 06:28.040 --> 06:33.200 So in the enterprise network, we're going to see, for example, VMware has a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 97 06:28.040 --> 06:33.200 So in the enterprise network, we're going to see, for example, VMware has a 98 06:33.200 --> 06:35.000 product called vSphere. 99 06:35.000 --> 06:38.250 This is kind of what they're known for. They actually make a lot of different 100 06:38.250 --> 06:38.840 products. 101 06:38.840 --> 06:44.560 But when we think about VMware having a hypervisor, their hypervisor is called 102 06:44.560 --> 06:45.480 vSphere. 103 06:45.480 --> 06:50.500 So that's a pretty common example from a type one hypervisor perspective. We 104 06:50.500 --> 06:55.080 also have Microsoft in this space and they have a product that feels a little 105 06:55.080 --> 06:55.920 bit on the nose. 106 06:55.920 --> 06:59.760 It's called Hyper-V, which is a hypervisor. 107 06:59.760 --> 07:03.040 But both of those fit into the type one category. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 107 06:59.760 --> 07:03.040 But both of those fit into the type one category. 108 07:03.040 --> 07:07.480 Meanwhile, again, we do have type two hypervisors and there's a place for this. 109 07:07.480 --> 07:13.300 And so we might see, for example, Oracle has a good option. It's called Virtual 110 07:13.300 --> 07:13.640 Box. 111 07:13.640 --> 07:17.340 So if you want to run a virtual machine on your home PC, which I've done many 112 07:17.340 --> 07:17.640 times, 113 07:17.640 --> 07:21.640 is part of, again, think about running labs and trying to learn things. 114 07:21.640 --> 07:25.640 I mean, Cisco's got some emulator software that runs as a virtual machine. 115 07:25.640 --> 07:28.520 Well, now I can deploy it onto my home PC here. 116 07:28.520 --> 07:34.820 And so Oracle VirtualBox is one option. We also have VMware, actually does have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 07:28.520 --> 07:34.820 And so Oracle VirtualBox is one option. We also have VMware, actually does have 117 07:34.820 --> 07:36.360 a product for this as well. 118 07:36.360 --> 07:38.360 It's called Workstation. 119 07:40.440 --> 07:44.830 And so the idea here is I can deploy these onto my existing Windows or Mac 120 07:44.830 --> 07:45.160 machine, 121 07:45.160 --> 07:47.960 whatever it is that I use, even Linux. 122 07:47.960 --> 07:53.160 And if I deploy these, then at that point I can run virtual machines on my home 123 07:53.160 --> 07:53.880 PC. 124 07:53.880 --> 07:56.840 At that point, there's going to be some back-end networking to make it work, 125 07:56.840 --> 08:01.240 but usually we are going to be able to directly log into whatever application WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 125 07:56.840 --> 08:01.240 but usually we are going to be able to directly log into whatever application 126 08:01.240 --> 08:02.360 is being hosted 127 08:02.360 --> 08:06.260 by the individual virtual machines that we're spinning up using the type two 128 08:06.260 --> 08:07.160 hypervisor.