So our problem needs to be solved here.
And the problem really stems around the fact that if I'm going to deploy a set
of hardware that I can only deploy a single operating system instance and
therefore single application per set of hardware.
And so this is where we're going to introduce virtualization.
Virtualization is going to break up one of these relationships.
Now, we're not going to be able to escape this application to OS mapping.
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
We need to have a one-to-one relationship between our applications and our
operating systems.
And again, we see why with, for example, the ports, if two different
applications need to use the HTTP or HTTPS port, then we can't really change
this relationship.
There are a lot of hard limits associated with this.
But what we can change is the relationship between our operating system and our
hardware.
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
In fact, we could make it so that we could put multiple operating system
instances all on the same hardware.
And that's exactly what virtualization is designed to do.
So now what we have is we have a set of hardware.
So this is still all of our CPU and our memory, our RAM, our disks, everything
here, all of the normal hardware components of a server.
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
And now we're going to install multiple operating system instances here on this
hardware.
And because we still have to maintain this one-to-one relationship between our
applications and our operating systems, we're going to deploy one at a time
here.
But what we see is even though it's one-to-one with the operating system, now
we can deploy many applications on a single set of hardware.
So we're maintaining the important relationships, but we're kind of breaking
the rules where we're able to break the rules. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the rules where we're able to break the rules.
So how exactly do we go about doing this?
Well, we can't actually just directly deploy multiple operating systems onto
hardware.
That would kind of break the rules a little bit.
So instead what we're going to do is we're going to split off the hardware from
the operating system.
We're going to insert something into the middle here.
So we're going to insert is a set of software known as a hypervisor.
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
This hypervisor is essentially sort of a new operating system, but it's called
a hypervisor because it's managing multiple operating systems.
We don't just want to call this an operating system, but rather it's a set of
software that exists between the operating system and the hardware down here.
So we take a piece of hardware, a bare metal server, if we want to think of it
that way, and we're going to install something onto it.
Well, we install a hypervisor onto it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Well, we install a hypervisor onto it.
And now the hypervisor allows me to install individual operating systems, which
can run individual applications.
These become known as guests that are running on a host.
So we have virtual guests and we have virtual hosts.
This is an important method of distinction because both of these concepts could
be a server.
If we think about it, what is a server now? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
If we think about it, what is a server now?
Is the server the physical set of hardware, the CPU and the memory and
everything?
Or is the server the operating system instance?
And the answer is yes, which is a weird answer, but the answer is really both.
Both of these are servers. We have a virtual server and we have a physical
server, but we don't want to use the same word to describe both of them.
So we're going to call a virtual host and a virtual guest.
Now, I will say this in our industry, even though these are technically the
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
correct terms, we don't usually see this word guest be referenced very often.
And instead, what we see is a reference to a virtual machine or VM.
So usually, we will say, hey, a virtual host in this term is used quite a bit.
This virtual host is hosting maybe 10 or 15 different virtual machines rather
than virtual guests.
Although if you do hear it, now you know what we're talking about.
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
So we have the relationship of hosting guest where the VM is the guest and the
physical server is the host.
And if we think about it, we're going to need some amount of networking between
and among all of these virtual machines.
And we'll talk about this coming up here shortly. So stay tuned.
Now, on the blueprint directly, we are going to see that Cisco is going to ask
us to understand the two different hypervisor types.
So let's talk about those really quickly.
First of all, we have type one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
First of all, we have type one.
And then we also have a type two. Now the type one hypervisor is installed
directly.
On to hardware.
And so this is when we say that the hypervisor is sort of like an operating
system.
Used air quotes here on purpose to say it's not really an operating system, but
it kind of feels like one because we take hardware and we install the hyper
visor directly onto the hardware.
At this point, we are going to install virtual machines onto the hypervisor, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
At this point, we are going to install virtual machines onto the hypervisor,
but everything here with type one is exactly how we've got it drawn out here.
Meanwhile, we also have a type two.
And the type two is primarily intended for maybe personal use labs development
if we're developers.
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
But the idea here is that the hypervisor is installed onto an operating system
as an application.
Meaning that maybe I've got a laptop and I'm running Windows on this laptop and
I install an application here that can run virtual machines.
Now there are several different hypervisors in the industry that fall into both
of these categories.
And keep in mind type ones, these are usually what we're going to see used in
our enterprise space.
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
So in the enterprise network, we're going to see, for example, VMware has a
product called vSphere.
This is kind of what they're known for. They actually make a lot of different
products.
But when we think about VMware having a hypervisor, their hypervisor is called
vSphere.
So that's a pretty common example from a type one hypervisor perspective. We
also have Microsoft in this space and they have a product that feels a little
bit on the nose.
It's called Hyper-V, which is a hypervisor.
But both of those fit into the type one category. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But both of those fit into the type one category.
Meanwhile, again, we do have type two hypervisors and there's a place for this.
And so we might see, for example, Oracle has a good option. It's called Virtual
Box.
So if you want to run a virtual machine on your home PC, which I've done many
times,
is part of, again, think about running labs and trying to learn things.
I mean, Cisco's got some emulator software that runs as a virtual machine.
Well, now I can deploy it onto my home PC here.
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
And so Oracle VirtualBox is one option. We also have VMware, actually does have
a product for this as well.
It's called Workstation.
And so the idea here is I can deploy these onto my existing Windows or Mac
machine,
whatever it is that I use, even Linux.
And if I deploy these, then at that point I can run virtual machines on my home
PC.
At that point, there's going to be some back-end networking to make it work,
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
but usually we are going to be able to directly log into whatever application
is being hosted
by the individual virtual machines that we're spinning up using the type two
hypervisor.