Introduction Virtualization Management Part 2
Video Activity
This lesson discusses storage options: NFS: Windows shared drive. NAS: Network attached storage Local storage on the physical hosts ISCSI Participants learn how virtual machines run on the host. On a network there can be many virtual machines (VMs); all of which can be connected to a virtual networking or physical switch. Each virtual machine has i...
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Video Description
This lesson discusses storage options:
-
NFS: Windows shared drive.
-
NAS: Network attached storage
-
Local storage on the physical hosts
-
ISCSI
Participants learn how virtual machines run on the host. On a network there can be many virtual machines (VMs); all of which can be connected to a virtual networking or physical switch. Each virtual machine has its own operating system (OS). You can create data centers to separate your hosts depending on an organizations needs
Video Transcription
00:04
so I can have NFS,
00:06
which is your typical Windows share Dr
00:09
Or or Linux UNIX share. Dr.
00:12
I can also have a network attached
00:15
storage device, such as now as
00:18
and another option is I scuzzy.
00:23
And this is an option where you can
00:26
use
00:27
traditional scuzzy commands, but they go over the network instead of through a cable to the actual hardness.
00:33
Uh, the last option is local storage
00:40
on the physical host themselves.
00:46
So if you think about the the
00:48
what we're looking at here, we've got a couple of computers that could be very inexpensive. Computer is a desktop workstation worked fine for any SX I host if especially as you're learning and building out an environment.
01:02
Once you get into a more production situation, of course you'll need to buy a more high performance server, one that has perhaps raid disk arrays, multiple processors and a large memory capacity.
01:15
I think about the way that
01:19
virtual machines actually run on the host itself.
01:23
I'll draw my host again
01:30
and again. The host is running e s X I,
01:34
and in the case for the labs that will be seeing later.
01:38
It is version five,
01:42
not five
01:42
update to
01:46
So my printing is a little sloppy. Sorry about that.
01:49
Mmm.
01:51
And on the host, once you have the SX are installed
01:56
that that creates the hyper visor.
01:59
So this the hyper visor
02:05
is the virtual ization layer
02:07
between the operating system
02:09
and
02:12
the physical hardware of the host itself.
02:15
So when the operating system wants to send a command to, for instance, access storage or
02:23
send traffic out of the network interface,
02:24
hyper visor translates the command from the windows or Linux. Whatever the whatever the OS is through the hyper visor, it uses that abstraction later to tell the physical hardware what to d'oh
02:38
and then within the within the OS on the host, we have our different V EMs
02:46
BM is short, of course, for virtual machine.
02:53
And as I showed before, I can have my
02:57
my network connection,
02:59
I might have several network cards. I'll just call them 123 and four.
03:06
And these could all be connected
03:08
to a virtual networking switch
03:12
or a physical switch, and we'll see some different options for how that works.
03:15
And then, of course, we saw the connections to our different possibilities for storage
03:22
as I, as I showed before we have.
03:25
And as
03:27
NFS and I scuzzy
03:34
one other option. That's very high performance, but a little bit more expensive, Not something the typical home or are learning it Person would be using would be Fibre Channel,
03:46
so we'll draw that as another option here.
03:59
Fibre channel, of course, uses optical fibers. So you get the highest performance
04:03
and the highest throughput overall compared to I scuzzy, which goes to the regular network connection just like NFS. And now, as does
04:14
we don't go too deep into the configuration details for anything about fibre channel. We will talk about a little bit, but we will do a lab where we attach a network attached storage device,
04:26
uh, as a nice, cosy partition. And we'll also attached manifest partition to show how some of those stores possibilities are available to you.
04:38
Another thing to consider with the host is the physical on virtual architecture and how that
04:45
differs. What I've drawn here is a little bit of the representation of the physical architecture. I I know that I've got,
04:51
uh,
04:51
a server of some sort here
04:55
with the SX I installed,
04:57
which provides that hyper visor functionality to give me an abstraction layer between the OS and the V M.
05:03
Keep in mind that each of the virtual machines
05:09
has its own operating system.
05:12
I drew this as one layer here, but each one of these really has its own. I could have,
05:16
for instance,
05:18
Windows
05:20
seven.
05:21
I could have Lennox.
05:26
I could have Server
05:30
2012.
05:32
Each of these guest operating system to resides on this on this B M
05:38
and basically replicates what this less layers doing through the hyper visor
05:43
telling the
05:44
the actual physical hardware what we wanted to d'oh
05:48
So
05:49
all of my network interface cards here,
05:54
I'll just put Nick back on the diagram
05:57
control access to most of the features and functionality that that you would be using within your environment.
06:02
But of course,
06:04
the host has other components built in
06:08
as we saw a moment ago. We have
06:12
local disc,
06:18
and I also have
06:21
in addition to a network cards.
06:24
I have my memory.
06:28
Just draw that as a box,
06:30
kind of looks like a bunch of little memory chips,
06:36
and you even have some provisions for using certain features of the hosts video card.
06:44
That's more of an advanced option, which we'll be covering it in another class.
06:48
So because I'm able to create a host like this
06:51
and abstract, it's hardware and share, the resource is it becomes at
06:57
much easier task to define your data center
07:00
with software
07:03
so effectively,
07:05
I can have
07:10
post one
07:13
host, too
07:15
three and four,
07:18
all contained
07:21
if in a data center.
07:24
This is very similar to a physical data center in that you can organize the host.
07:29
And when you're using the center, you can create
07:31
data centers to separate your hosts according to whatever organization schedule you wish.
07:38
For instance, I could have a data center for Washington D. C systems. I could manage a data center for Chicago, another one for New York and so on.
07:47
Or maybe your your organization has different offices. You could have
07:53
your headquarters has born data center and one of your
07:57
remote offices as another data center.
08:00
And managing all of those from the one instance of the center
08:03
is a wonderful way to to deal with a large environment with a lot of different users, lot of different requirements
08:11
and be able to deal with this all from one centralized location
Up Next
Similar Content
