WEBVTT

00:00:01.020 --> 00:00:04.480
In the cloud, everything begins with virtualization.

00:00:04.580 --> 00:00:08.790
The underlying capabilities of virtualization means

00:00:08.790 --> 00:00:11.880
that the resource pools of storage, compute,

00:00:11.890 --> 00:00:17.070
and networking are going to be made available to multiple tenants who

00:00:17.080 --> 00:00:22.940
have really no idea who may actually be consuming services from the same

00:00:22.940 --> 00:00:25.860
systems that represent additional customers.

00:00:26.840 --> 00:00:30.820
When we think about virtualization mechanisms in the cloud,

00:00:30.830 --> 00:00:35.250
the hypervisor is the underlying capability that allows

00:00:35.250 --> 00:00:37.770
for that virtualization to take place.

00:00:39.540 --> 00:00:43.290
There have traditionally been two types of hypervisors.

00:00:43.300 --> 00:00:47.600
The first hypervisor on the scene was called a Type 2 hypervisor.

00:00:47.610 --> 00:00:52.540
The Type 2 hypervisor is also known as a hosted hypervisor and the fact

00:00:52.540 --> 00:00:56.400
that it's a traditional operating system that may actually have an

00:00:56.410 --> 00:01:00.670
application that is emulating another operating system.

00:01:00.680 --> 00:01:03.030
This one has been around for many decades.

00:01:03.040 --> 00:01:07.980
The Type 1 hypervisor is the cloud hypervisor, the modern day

00:01:07.980 --> 00:01:11.420
hypervisor, that fuels consumption of cloud services.

00:01:11.430 --> 00:01:14.360
If you were to look more carefully at the Type 1 hypervisor,

00:01:14.370 --> 00:01:19.550
another way of calling it out is bare metal, or embedded, or native.

00:01:19.560 --> 00:01:20.870
Why is it called bare metal?

00:01:20.880 --> 00:01:25.340
Because it actually gets installed directly on the hardware.

00:01:25.350 --> 00:01:29.840
In some cases, it actually can be installed within firmware.

00:01:29.990 --> 00:01:35.550
It is a small form factor control of the underlying resources,

00:01:35.550 --> 00:01:39.350
the compute, the network, and the storage, without the overhead

00:01:39.360 --> 00:01:43.160
of a traditional operating system doing many other things. Its

00:01:43.170 --> 00:01:46.350
only focus is to serve up resources.

00:01:46.940 --> 00:01:50.900
If we were to make a comparison of the traditional operating system, you could

00:01:50.900 --> 00:01:56.260
see quite simply that the center of the traditional OS would be its kernel.

00:01:56.410 --> 00:02:02.770
With a Type 1 hypervisor, it is actually the hypervisor that's at the center

00:02:02.770 --> 00:02:08.270
of attention that can serve up additional services and can have an operating

00:02:08.270 --> 00:02:10.360
system exists on top of it.

00:02:10.940 --> 00:02:14.640
The first service that we'll consider that is served up by the

00:02:14.640 --> 00:02:18.540
hypervisor will be networking. Join me over in the next clip,

00:02:18.550 --> 00:02:20.260
and let's take a closer look.