Transcripts
1. Intro to Class: Hi, how are you?
Welcome to Skillshare? My name is Emilio, and we are watching
three classes here on the topic of VMware, the first-class and all the lessons focused on
VMware ESX psi, given you an introduction
about what ES6 is, what its purposes,
how to download it, how to set it up, and
how to configure it. This class now focuses on foundations that we
covered in the last class. Now, building onto that
and actually going and setting up your
own virtual machines, building some virtual servers, and then configuring them
so you can actually start to use them out on your network. Whether that be in
your own home lab, your own learning environment, or whether that is in a real production environment
in a company. So this next number
of lessons in this class focuses
on building VMs, setting up VMs, configuring, troubleshooting best practices
around VMs in VMware. So I recommend that you follow along with your computer where possible if you've got
yourself a computer that is now running ESX
psi, that is great. If you don't, I recommend go
and watch the previous part, one of the class
to actually go and set up ESX site on
a computer first, because now the next number
of lessons we'll build upon that as we start now building
our own virtual machines.
2. Your Project Tasks: Following on from
the first class, you learned how to
install VMware ESX, psi. Now you're learning a little bit more about the technology. You are actually
going in configuring your building yourself some VMs and you're playing around with some of
the underlying tech, the storage and everything
that comes around. First, ESX, psi, environment
and infrastructure setup. Now, what I recommend is, as we go through each
of these classes, go and try it yourself. It's great that you
can go back and rewatch each of the
lessons in this class. But you doing it yourself
is what we want you to do. So when you finish
one of the lessons, go grab yourself a computer with ES6 psi and try and
do it yourself. And also let us know
how things are going. You've got a project section there in the Skillshare class. So go in and comment, let us know the progress. Those know if you're
getting stuck, let us know if things
are going well or if they're not going
well and collaborate with other students
that are also taking place in this
Skillshare classes, of course is the second class in that three paths cutting that
three-part class series, we're, now we're
configuring and getting to know more about our
VMware ESX side. So as I said, go and
try this yourself, because that is the best
way that we learned.
3. Storage Types: We are logged in here to
our ESX in environment. And we're really
just going to give you a bit of an overview, essentially of what
storage is within the VMware environment and essentially the different
options that you have available for storage. Now, if you've already built
yourself, your ESX hosts, which I'm assuming that you have if you haven't
go and look at those videos first
and get yourself your ESX Hosts and built. But by default, A6
I host of course, is a physical server, a physical desktop
or whatever sort of hardware you've chosen
to build your VM on your hypervisor on within
here, this is my host. This is, this is the
configuration of my host. This particular one is an Intel knock is just
used for the demo. It's running 6.7. But if you're running
seven or later versions, the process is really the same. And of course you've got CPU, memory and storage that is
allocated to that ESX host. Every single host will
have these resources. Every single computer
has some form of resources built-in,
including storage. Now by default, when you
create your own ESX host, when you're actually going
and installing the software, you will generally you'll
install the ESX size software directly onto some form of storage on that
desktop or server, whether that be an SSD
or SATA hard drive, even modern service. Sometimes you can
even install it onto an essayist on an SD card. There's also options to
install the hypervisor since the ES6 I
directly onto storage. If you have e.g. no storage available at all
within your host. So let's just look at that. So by default. So we're going to talk about
that aspect right now. We're going to focus
on, Let's look at the very first
instance of you having storage on your host directly. Now, by default, if
you're installing ESX psi onto the stories
that he's built in. Once you're up and running
and you've logged in, if you go into the storage
area within ESX psi, you will see your data store. Okay, you'll see
that right here. I've got a data store called primary data store that has got, so by default, you'll see I've got two
data source in here. One I've added in, which we're gonna go
through in a second. But one is the data
store that would be automatically preconfigured
when you build your ESX. This Datastore right here, you'll see it has
a capacity of 231, which let's say it's a
250 gig SSD harddrive. And that has been converted
into what's called a VM NFS type of storage. That is the format
that VMware users. So this is an actual
physical hard drive on my Intel knock
on my ESX host, which is now being converted automatically into a data store. I can go and build VMs. You'll see there's a whole
bunch of VMs right here. I can go and build a VM. And that VM of course, needs to sit somewhere in is
to physically sit somewhere. That location is a data store that needs to sit
on a datastore. So again, in this
very first instance, we've got a VFS datastore, which has been
created by default, which is the storage
that is used and located on the ESX host itself. Now, that is all well and
good for a small environment. So if you're doing this in a lab environment or
even a small business, you could potentially use the
storage that is built-in to your server or your
computer that you're using to configure
your ESX host. But most of the time you want your storage
to be separate. You want your host
to just give you the processing power around
the CPU and the memory. But you don't want
all of your VMs stored necessarily on your host. This will become a
bigger topic that we'll talk about where we're focusing on the vCenter environment. Because especially
if you're building vCenter and you're adding multiple ES6 I host
into vCenter itself. You don't want storage of a VM being on one host and
another VM being on another host because one host can not see the storage
of another host. There is ways to
do that with Visa, which we're not going
to cover in this video. But generally you would have some external storage
of some sort. Generally, something
like an NFS IS Gazi or Fibre
Channel conductivity could be on a SAN storage
attached network, or on a nasa network
attached storage, which is a physical
storage network device. And then that is discoverable
essentially by your hosts. So then you can have
a VMs sitting on a storage piece
outside of your host. And both host can actually see the storage and you can
easily move the VM between. Because the end
location where it's actually stored is not
on the host itself. So that is the beauty
of VMware as a whole, is that you can actually
take advantage of storage that is not physically
located on your host. Now here we are, as I said in our Datastore
section right here, this is in our ESX host. If you're doing this
within vCenter, you've just got the little
area up the top here, which is all of your storage. And you can actually
go and configure your storage right in here. But the process is
really the same. So we're just going to focus
here on ES6 for this demo. You see that by default
I've got my data store, as I said here, which
is my local storage. Then I've also got a
separate primary data, so which I have added, which is NFS right here. And that is a very
large amount of capacity available against
these primary data store. Now this is not local, this is not physically
attached to my host, is actually on the network. This is a Naz for the purpose of this
demo, It's a phonology, Nas and I've connected that's
phonology now is using the NFS protocol
into my ESX host. Now what you do right here is there's two things
that you need to do. Firstly, you go through
the process of doing a new data store and selecting a particular
option right here. And you also need
to do some sort of configuration on the nares
or on the sand itself. Now, if you are interested, we're not going to talk
about in this video specifically how to do that. We're going to talk about
the different options. But there is a follow-up
video to this one, which specifically
we'll go through how I configured a phonology now has over the NFS protocol how I got it set up
on the phonology. Notice how I made it
discoverable and essentially sharing its resources
with the ESX host. And then the steps that I went
through to actually go and configure it and connect
it to this specifically. So regardless of what
storage you are using, the process will
be very similar. So if we just go back
into new data store, you'll see there's a few
different options here. You've got create new
VM EFS Datastore, add an extent and
existing VFS or expand an existing VFS or
mount NFS data store. Now, the other video that will let you know that you
can look at after this, which is the specific
phenology one that is using NFS
as its protocol. So depending on the actual
storage media that you've got, this type of storage, you've either got what's called block-based or database storage. Essentially, a nasa been using the protocol
generally of NFS, which will be some sort
of an SMB share, e.g. that you create On a
nurse that you can then share over the
network as an NFS, over the NFS protocol, and then you can
figure it that way. The other option is what's
called block-based storage, which is generally what
you'll see on a sand. And that can be done overnight
or over a fiber channel, fiber channel beam technology where you can take advantage of fiber Channel switches
and you do zoning. And essentially, it's a
network-based storage network that goes over fiber
channel connectivity, while generally IS Gazi, we'll go over Ethernet. There are different cabling
and different protocols that can be done
like you can sort of mimic one or the
other and share them. But generally what
you'll find is, IS Gazi can be done
over Ethernet. So you're gonna be limited
to Ethernet speeds, say overextended cat six or some other sort of network
ethernet cable. And you're gonna get speeds of maybe a gigabit or a ten
gigabit network, e.g. connected over
that fiber channel uses completely
different technology. It's not going to go over Ethan, it's going over fiber channel. And then you can get speeds of maybe eight or 16 or 32 gigabits per second depending
on that technology. But for that purpose, you need to have, make
sure that your servers, that your storage running and have fiber channel
connectivity cards. You're going to have
things like SFP modules. Potentially with fiber
channel connectivity. And that's how you
will run it that way. While most out of the
box servers will not have fiber channel unless you've actually gone and
bought it with that. So you can do ice Ghazi over
an Ethernet connection. So that's really a bit of a
difference between the two. Which one I would recommend? Well, it's really up
to you and really up to your environment. Fiber channel does have a lot, a lot of redundancy options, but it's going to be generally higher cost because you have to purchase a whole bunch of
fiber Channel switches and have somebody that's
experienced in fiber channel
connectivity and doing zoning and things of this nature on a fiber channel network. But let's look at
the first option. So he is create new
VFS Datastore Next. And now I need to
select the device and wish to create a
VM if a storage, now by default, nothing
showing up in here. The following devices
are unclaimed and can be used to create a
new VM if S Datastore. Now the reason nothing is
on here is because there is no storage medium over ice guys, your fiber channel sharing
its connections or its lungs, like in a sane world
if what a land e.g. your storage pools, you'll all these other
sort of technology. There's other videos that I will do around storage specifically, but you need your sand
to be able to say, Hey, I've got all these
lands configured. Lands are being
blocks of disks, e.g. and I'm gonna be sharing
them out on my network. And then this will go and
scan your network and go. Here it is, and it will find it. And generally there's a
connection between the two. So you're saying, we'll
say all of my ESX Hosts, these, these are
my IP addresses, these are the credentials and
you can share it that way. That's why that is empty. But what will happen is you'll, you'll actually
see that storage, the IS Gazi or Fibre Channel
storage listed in here that the block of the storage that you've presented to it. And then you can select
it and then add it into your datastore
environment and create its own storage location
for you building VM's. Okay, so that's IS
Gazi and fiber channel IS Gazi fiber channel discs
being presented from a sand. Generally, you're creating
storage pools are creating lens essentially
pulls of disks in raid configurations
configured as lines presented out to your network in
block storage, right? And then your VM. And then your VMware environment
can see it an added. And that is the first one. The second one here being NFS. Nfs, as I said before, is generally going
to be something like an SMB share share, share. That is also e.g. you can navigate to that the same way that you
can navigate to a shared folder on
a Windows Server. You can actually do that, sharing that directly into
our ES6 environments. So there's very similarly, you can say mount NFS. And of course this
is considering that your NFS, your Naz e.g. has actually been configured correctly and that
it's presenting its storage again out to the network or directly
out to the host. You then input the details
of the NFS Server, the share, and then click on
Next and then we'll add it. Now, that is a
summary of those two. As I said, I do have a
follow-up video to this that will specifically
go how I did that on a phenology NES creating
the NFS share and then presenting it out to the
network to then add it onto here as a data store. Now the great thing is that
because it's shared storage, it can be shared across
multiple ESX Hosts. Exactly the process that
I just did right there. I've just gotten new
data store and I navigated to either
via NFS or NFS. You could do something similar
across all of your hosts. There are ways to automate that, so it does it
across all of them. But essentially every ESX
host inside your environment. If you're configuring
your ESX Hosts into clusters within vCenter. Every VM, every, every ESX host or every
cluster can see that storage. And you can navigate
to that storage. And literally it's just all of these hosts all
around the place, all pointing to
one location, e.g. which is one data store in
a physical storage device. Some way of course you can
get very fancy and have multiple data stores across multiple storage units,
across multiple locations. That's thinking much
more bigger picture, but that's really the basic
things that you can do. And the great thing is
that you can actually expand your storage
very similar to when you actually are
building a VM and you're setting a disk to
be thin or thick provisioned on the storage
side when you're creating your NFS shares or if
you're creating a LAN, you can also set those as thin or thick depending
on the vendor, depending on the brand of
the sand or the nerves. So you can also expand
that thin or thick. And what you can do is say e.g. you create a LAN
on the sand, e.g. that he's a two terabyte lung. You've presented
that to ESX psi, psi, you've gone into here, you've said create new VM NFS, you've clicked Next,
you've added it in, that's now 2 tb. You've now run out of space. Well, what you can do
is on the same side, you can expand that
perhaps to 3 tb. You go back to your host, URI, scan your storage, you go back through
a little process here of increasing
capacity loops. We can say increased capacity of course as blank,
blank for now. But you can also go
into here, refresh it, rescan your storage,
and then you can actually add that additional
storage into here. And then it will be
presented as a storage, as a data store within here. Now, think about this
as a virtual storage. This is essentially
virtual storage which is connected to a, I guess I pull of disks in a physical sign on as that then is physically some hard drives
within a center itself. It's very important
that you do understand the storage area because
it's going to be integral for you to
build your environment, to build a properly
and to be able to expand your
environment as well. Perhaps you didn't know that when you're creating a new VM, you could do a little
drop-down area right here and select thin or thick. What is the difference? Why would I use
one over another? Let's just go over
what each of the two thick. Let's
start with that. This is a standard disk setup. Let's say in a
physical computer, you're going in and
you are installing an 80 Gig hard drive into a computer, a
physical computer. You've got that
operating system, recognizes the full 80 gig and
can use the full AD again, it's all readily
available up front. That's essentially
what thick is. Thin is you actually
allocating an 80 gig disk, but you're not
physically giving it the entire 80 gig upfront. E.g. you've allocated an
80 gig rasa right here for an 80 Gig hard disk
as my primary, my primary disk for this server, I'm allocating it as
thin provisioned. So then I can go and build
Windows Server onto it. E.g. Windows does not
need 80 gig to run. It only needs a little
smaller amounts, maybe 20 or 30 gig,
let's say maximum. So the good thing about
thin is that you're not allocating the
full 80 gig upfront. So you can actually, if you
have a pool VMs and you're allocating all of
these disks all over the place being
thin provision, the operating system
and the software that's running on
that Virtual Machine will only allocate or use
the storage that it needs. And the rest of that
storage is free to be used and it's not
actually being taken up on your physical storage. E.g. you've got some, some physical hard
drives on your ESX host, or even if you've
got them set up on a NFS or IS Gazi on a
SAN or on an as someone, you've allocated that and
it's been used on your VM. Well, it will only use the
capacity that it needs. So let's use the example, Let's say windows
and some software that you've installed
only needs 20 gig, but you've allocated an
80 gig thin provision. That means potentially
60 gig of that disk, even though Windows sees
it and sees a full 80 gig, it's not physically using the
entire elite only using 20. So 60 gig is Kim can
be used elsewhere. It's not physically been
taken up by that VM itself. So what's great about
this is that you can leverage the stories that you have and not
use it all upfront. This give you another example. I've now got two VMs. One I want to allocate
an 80 Gig hard drive. The other one I want to
allocate an ADE harddrive. Traditionally, what
would you have to do? You'd have to go and grab
a 80 Gig hard drive, put it inside a physical server, to another server you building allocated a gig hard drives, so you've got 160
gig and they are dedicated for those two
with thin provisioning, I could give 18180, but he doesn't use 160 gig of the storage on my
physical storage device, whether that'd be on my host, whether that be on
my nose or my son. So I can actually
use the storage between those two VMs thick. You're actually
allocating that storage. And that storage
will be dedicated and set aside for that VM. You'll see that right here. I've got lazy zero and
I've got eagerly zeroed. The end goal for both of these thick provisioned
versions is really the same. But just to give you a bit
of a summary and eager zeros are going to give you
better performance and security to take up a
lot of time to create. Lazy is well, on a
little bit more lazy. That's the y that
I think about it. It's short time to create, doesn't provide as much speed. So eager being better
performance and better security, but takes a lot longer to set up because you're
essentially doing a whole bunch of stuff
in the background to set it up properly. Now, while Lazy, we're going
to be a bit more lazy and we'll set it up as we go in the back-end I'm
talking about here. So it's good for
short creation times, but it's going to be not as fast and a
little bit less secure. So that's when you're, when
you're creating a thick or a, when you're creating
a lazy or an eager. Consider those to. My general recommendation is
to go thin whenever you can, unless you've got a
whole bunch of storage. If you've got a whole bunch
of storage available, then always go thick. But you're wasting storage. If I've gone an allocated
and 80 gig storage to a VM, and forever for
the next ten years it's only going to
use 30 or 40 gig, let's say 40 gig maximum. I've wasted 40 gig of that. I could have just
said it as a thin. So allocating it 80. But if you're only uses 40, then I've got 40
to use elsewhere. You may be thinking, well what
happens when I physically use the storage like
because what you can do, he's a little bit of a gotcha. This is something that a
lot of people overlook. Sometimes it's hard to
maintain over time. If I've got a limited
amount of storage on my son and I'm allocating
all my VMs with thin. Great, This is awesome.
I'm allocating all this stuff with thin. Over time. Those VMs will start to
grow and they may start to use more storage and more storage on your
thin provision disks. Remember that now
we're starting to use the physical storage
on a physical device. If I've allocated
everything is thin and have proper monitoring or
I'm not monitoring the growth of those
VMs, what can happen? I can allocate, Let's say,
I give you an example. I've got a 1 tb worth of
storage on my host available. And I've got a whole bunch of VMs and I'm going to allocate them 250 g h and say I've got 5,200.50 gig hard drives allocated to five hosts. So 25250 is 500 gig, 25250 is another 500 gig, and then another 250 is 1.25 tb. I've only got 1 tb
with a storage. So if I'm not
allocating or I'm not monitoring my VMs correctly. Those two fifties times five
eventually will fill up. And then I don't have more than 1 tb of storage
physically available. So then I'm going to have a problem because I'm
going to round a storage. So thin is good. As long as you are
monitoring it correctly. Thick is good if
you've got a lot of money and you're
able to allocate it. But then you've got a bit
of wastage of the disks. If you're not using
all of that capacity.
4. Configuring your VM's: We are here logged into
our vSphere environment, which is going to go to
the host view right here. So again, remember
we've got host here. We've got here an area where
we can actually see the VMs. You'll see here
that the VMs are, have all been put by default into discovered
virtual machines. But what you can do is
to make it look a little bit neater and function
a little bit better. You can right-click right here. We can say New Folder, new VM and template folder. And in here we can actually
say production VMs. And say, Okay, now I've
got a folder in here. So what you can
actually now do is you can actually
let say these two, this one, move it in here. This one we can move it in here. Now this folder has
got these two VMs in them and then these
folders or something else. So we could potentially
right-click right here and say demos. Okay? And then add these into here. Okay? So now it's just,
we've essentially just manage it a little bit better to make it look a
little bit better. But in the host view
that all remains as is, there's still a cluster
created that we've made tests and then
the VM ESX size, sorry, that we've added into the actual host with all the
VMs inside there as well. Then of course you've
got your storage view and your network view. From within here, you
can see all your VMs. We can click on
the little VMs tab at the top, selecting the host. Selecting VMs, see all the VMs that we have built, all
of them right here. So you can right-click
on this VM. And you've got a
number of different options that you
can do right here. So you can do the power on, power off, suspend,
etc. Can you shut down? You can do some guest OS stuff. So this is around
installing VMware Tools. You can customize the guest OS. So in this case being Windows
Server and actually add some customization
directly into there. You can open up the console
right from there, migrate. So moving it from one host to another while it's powered off, you can clone the VM, which is actually a
really nice feature. We can literally
just clone it and create a template
right from here. You can do fault
tolerance stuff. So this is an event where
you wanna be able to fail one VM to another in the
event of a host failure, e.g. and a whole range
of other things. Okay, so you can
create templates, you can export and
over EF template, you can upgrade
the compatibility. There's a whole range of stuff, so there are a number of videos. I do cover some of these, so do stay tuned and find
some of those later on. A bit that gives you a bit
more information around the actual settings that you can add and change within here. You can also rename the
actual description of the VM. So I can just literally
say Rename right here and give it a new name. Now because this has got Windows Server
installed, of course, a Windows Server itself
has to have a name, a Windows Server Name. This is different. This is just a VM name, so you can name this
whatever you want. But then when you
log into Windows, the name within
Windows will actually remain exactly the same. You can also remove
from the inventory. So what that means is
it's going to just remove it from this
screen right here, but it won't physically
delete the files. The files will still be there. And you can actually
see those files by easily going into the
data store itself. Okay, So you got
datastores right here. Here's our Datastore,
primary data store. So we saw here, you can
right-click and do Browse files, potentially see the contents
of that data store. And this particular server is Windows Server 2019, right here. And here are the physical
files of that VM. So in the event that you
want to go and move things, you can actually go and
navigate straight through and essentially look through
the data store itself. Actually browse through
the data store itself. We're not going to be doing
that of course, just yet. But let's just go back. So removing, as I said, removes it but doesn't actually delete it from the data store. Delete from disks, actually does delete it from
the Datastore and VC and lets you do
a bit more sharing around storage between hosts. The other thing that you
can do is you can actually go into Edit
Settings right here. And you've got some furthest settings in here that
you can actually go and customize
right from here. So when you've built
these VM originally, you've obviously then
gone and allocated specific amounts of CPU, memory, hard disk space, and a whole range
of other things. So while the VM is powered off, you can actually
go into here and increase the CPUs
cores per socket. We've got two sockets. We've got one core
across two sockets. So I can say two
across one soccer. So I can sort of change
that as I need to. I can go up to here and say
for one across four sockets. So you can really
go and customize it to how many CPUs you want. You've got other areas
he around CPU, hot plug, which there is
another video talking about this essentially lets you add CPU while it is
currently turned on, while the VM is actually turned
on, reservations limits. So essentially setting limits to how much resources of the CPU can use while it's powered on. Essentially, it's helps
with sharing the load of CPUs between VMs. Additionally to that, you've got memory and you've
got hard disk space. So all of this you can upgrade, you can go right
into heat and add more RAM right into here. Say okay, boot up the actual VM and
then you've got more additional RAM in there. You can also do things
such as harddrive. So you can add additional
hard-drive space. Now when you do add
additional hard disk space within here, you will have to login to
your VM into Windows server. In this case, do a refresh of the computer
management of the disk itself to be able to find that additional stories
that has been added. And then you expand the disk
and you have to do that within the VM once
you've allocated it. So if this is 80 gig
and I give it 100, and I'll say, okay, Windows doesn't know
about that just yet. So you have to go and
refresh the disk within Windows to find that
additional 20 gig, which is now going
to be available. We'll leave that as the default. And he's a range of
other stuff, right? You guys, you can try
going network adapter. You got CD, DVD drive. I will just currently
mapped to my datastore ISO USB Controller, video card, etc. So you can easily go into
here and delete things. You can easily just select it. And then on the right
you see there's this little cross to if
you don't want that, you can actually remove it
and that removes it from the actual guest OS from
the Windows side itself. If you don't want
a USB controller, you can just go and
delete it from there. Now here's the great thing is
you can actually go and add additional resources right
from here if you so choose to, you can actually select add
new disk at new device, sorry, right from here. And then you'll see
that there's a range of different options
that you can actually add to your VM itself. It's a fantastic thing. So you can add new devices
to virtual machines. You can add new disks, you can add additional CD, DVD drives, additional
USB drives, PCI devices, serial ports, all this sort of stuff to
essentially mimic what a physical server would have. And you can just virtualized, essentially it's a virtual
version of those options. Okay? You can also do VM options. There's some additional stuff in here that you can look through. We're not going to
cover everything he in too much detail, but you've got VM Tools. You can settings,
settings around VM Tools, power management, food options. You've got some
additional advanced settings in here as well. Don't play around with
too much stuff in here. Unless you really want
to go in, tinker around. It could it could make things better, it could
make things worse. So just, I would say focus on the virtual hardware for now. Later on when you were
a bit more advanced, you can go in and actually
play around with VM options. Now, the other thing you can
do is you can easily just click on this Windows Server. Then you're brought into this
essentially like it opens up and you can see a lot more information
right from here. So of course we're
here in the center. You can see the
actual resources and live activity around that
VM when it is powered on, you got an additional error
on the top here to be able to power stuff on
console, et cetera. You've got all of
your monitoring, so all of your stats
on how that VM is performing, tasks, events. You can do configuration stuff. These are things that are not available in that
other screen that will Justin permissions who can actually get access to these VM. Okay, so of course,
once your host is bound to Active
Directory e.g. you can go and create
specific security groups. You can add users,
you can create your own VMware
groups so that when people login to vCenter, e.g. that will only see the
relevant VMs in this case, they could only see
this or they could see other things if they're
given adequate permissions, information about
the data store. So it's sitting on
this data store and a few other things
right from there.
5. Setting up a NFS Datastore: Okay, so what we've
now done is we've connected into our na, na's. So right here is
my phonology now is just for the
purpose of this demo. This is a DS9 20 plus
phonology nares. And then I've also got
my VMware ESX host. First thing we're gonna do
is we're now going to login to our ES6 I host. You can do this via
vCenter or ESX side. We're gonna do it
directly via an A6 I host and login with
my root credentials. And there's a bit of an
overview about my environment. So what we're going to
need to do is we need to now navigate essentially to the storage area on your
ESX host or in vCenter. And create a new data store
that is actually relevant to a folder that's sitting on your phenology NES within
your storage area. Before we actually go and
create a new data store, it's important to
give your phenology NAS the relevant rights
to your ESX host. So in my case, my IP address is one-seventh 2161 dot 100 of my ESX
host specifically. And on my phonology Nas, I need to essentially grant a specific folder
that's going to be acting as my data store
to that ESX host. We're gonna be doing
this over NFS. So the first thing that I
would do is now click on the main menu section right here and select Control Panel. Control panel will open up. We then select shared folder. And we now need to
allocate one of these shared folders with adequate permissions
so that it can be read and mountain
essentially as a data store within VMware,
we're selecting data. This is my shared folder. And what I'm gonna do is
within false station, if I open up file station, if you see that within
my data folder that corresponds to this
data shared folder, I've got a folder
in here called ES6. Esx psi is the folder that
we're going to be mapping to. And then the next step is
now that we select data, we know what's inside of it. We now need to give this particular folder
adequate rights, adequate permission into VMware. Now what we need to do
is we need to firstly enable the NFS service
on phonology nerves. By default, this
service is turned off. We then need to grant
the NFS service access to my data shared folder and then give it the
relevant rights that it needs to have under
the services area. We want to select NFS. So you'll see that
there's a whole bunch of other protocols in here, including FTP, SMB for Windows, AFP for app, all those
sorts of things. But what we need is
the NFS service, which is the service that
VMware ESX psi is familiar with and what's gonna be used
to connect into our nares. So we're going to take
on that and select Save. That service is now turned on. We can navigate back
into shared folder. And the folder that we
are considering here, or the one that we
want to use is data. So let's go ahead
and select Edit and data is selected there. And we're going to now select NFS permission on
the very far right. By default, this is now empty. So the mount path is volume
one, forward slash data. So when we're mounting it, you have to keep that in mind. What we wanna do
is we now want to create a new permission. Now, you essentially establish
a connection between your phonology and your ESX
host or hosts directly. So what we're gonna do right in here is we're going to add the IP address of the
destination host. In my case, that's going to
be, as I mentioned before, one dot 10172161 dot 100. So we're going to throw that in. We wanted to have read
write permissions. Otherwise you won't
be able to read it and write to it,
which is very important. Squash no mapping. When I leave that as is, security is six,
we don't want to go and add extra security. In my case, we'll leave
the rest as default. We're not going to
touch anything there. And select, Okay? Now that permission is now set. Now what you would essentially do is if you have
more than one host, you'd go in and you'd add
all of your hosts into here. That way, that particular
share data has access to all of the IPs that are listed within your NTFS
permissions section. If we're happy with that, great. The next step that
I just like to do, just to make sure it's all okay. Is under permissions is ensuring that admin has proper
read write access because you may be asked
for credentials and the credentials that
we're gonna be using our admin which have got read, write access to
that data folder. Okay, so that is
now ready to go. Now what we'll do is we'll show you what's within
my data folder. So within false station where you can just
navigate what's going on. I've got data and I've
got some folders in here, applications, Documents,
Pictures, et cetera, stuff that I like
to have for myself. But then I've got
a folder called ESX should be probably
called ASX Cyber. Esx is the fold up. Let's actually rename it. Hey, probably good to
give it an actual name. Esx used to be the
old name by the way, back in the day, and
then it changed to ES6. And then within here, I've got a whole bunch of
stuff in here already. I've got a number of VMs and I've already previously created, and I just want to remount
these into my ESX host. Then I can then
connect to these. Yours could be completely empty. I would recommend not only
just mapping it to a share, but perhaps have a folder
in there that is relevant for all of the storage
of all of your VMs. Let's now go back
into my ESX host. Now it's ready to go. So what I'm gonna
do right here is I'm going to select
new data store. And there's a few
different options here. You've got create new
VFS, add existing, expand existing VM if S Now
the VFS is what you're gonna be using if you are
mounting a sand generally, and there's things like
lungs that have been created and those lines
are presented to your, to your host, e.g. if it's a fiber channel IS Gazi, you're going to be
doing things like zoning, things like that. This demo is not covering VM AFS and ice Qazi
and fiber channel. That's a different video or the videos that I've got
that talk about that. This one is focusing
specifically on NFS. We are going to
mount an NFS data, so which is the protocol
that we've turned on on the phonology
now is select. Next. Let's just give it
a meaningful name, calling it primary data store. The NFS Server is the IP address or the
fully qualified name, but I recommend the IP
address of the NFS Server, which is of course
the phonology Naz. So adding the IP address, which I know is
that right there, yours will be different. Make sure that you put in
the correct IP address. Nfs share is now the path
that you want to be saying. This is the path to where
my data store points. Okay, now remember
if we go back to S analogy knows we've
got a few things. Under data, edit,
NFS permissions. He's the path and
the bottom forward slash Volume one,
forward slash data. And then within
data I've got ESX. So that is the full
path that I'm going to be connecting to back to my ESX psi volume
one for such data. Now remember this
is case-sensitive. A lot of people have issues. Like why isn't it working? It's case-sensitive. Forward slash ES6. We leave the NFS
version as NFS three. Next, Here's a summary of
what's going to happen. We click finish. If everything has
worked correctly, that should have mountain. Okay, you'll see that
it says the capacity, which is the capacity of my
sin of minus what's free. The type is NFS and it's done, it's ready to go,
which is excellent. If yours failed for
whatever reason, you're gonna have to go back, review some of the stuff
that I talked about. Review that the NFS
has been turned on, the service has
been turned on at the permissions are
correct that you've added the ESX Hosts to be able to be given the relevant rights, to be able
to connect to it. But that is really
the steps to get it now mounted as a data store.
6. Building a VM: To see here that
we are logged in. We've got our host, we've got our virtual machines,
storage, and network. So we've just already commissioned a brand
new piece of hardware, brand new server
running ESX psi, which is VMware's hypervisor. It's up and running. So this guy will
not show you how to install that necessarily. We're assuming that you've
already built that. And now you want to go and
build your very first VM. The first thing that you want
to do is you want to login to your ESX host. In this case, we're
on our ESX Hosts. Or you could be connected
to a vCenter environment. And you are connected
via your web client. Why your web browser, you're connecting to
your IP address of your, of your host or your vCenter. And your neck presented with
a similar screen to this. Alright? First thing you wanna
do is you want to have an ISO of your operating system. Alright, so we're
gonna be installing Windows Server 2016. You need to have the eyesight of 2016 to be able to go and install this
particular operating system and build this VM. So there's a couple of
things you could do. You could either create
VMs straight from here and then mount that I
saw directly onto the VM. Or you can copy that I saw
it into your data store. Your Datastore will be a
physical disk somewhere. It could be the disc on your
server or it could be a disk on a separately attached piece
of storage such as sand, or you'll have your
data stored here. What we need to do is
we need to copy that. I saw that Windows Server 2016, I start into the Datastore. There is a way to manually mount that I saw
directly onto the VM. But it can be a little
bit slow because it's reading that I sent
directly from your hard drive, from your local hard drive. And I just like to copy it to the datastore
that way I've got a permanent copy of that ISO sitting on
the VMware Datastore. You'll see on the storage
I've got my data store. I want to right-click on it and say Browse, create a folder. Alright, so in here, I've just created a folder called ISO. So you'll see down
the bottom here create directory ISOS e.g. and here is my ISO that
I've already copied. But all you have
to do is click on Upload and then navigate to where your ISO is on
your physical computer. Whether if it's a Windows or on a Mac, whatever it may be. And you can copy that
also directly onto here. Alright, so that
might take a bit of time depending on how big your ISO is and how quick
use your networks VDS. Once it's in there,
you're good to go and you can click on Close. And then we can build the VM. The first thing we're gonna
do is I'm going to say create or register a VM. And it's going to go
through a simple guide. Create a new VM, deploy
a VM from an OVA, OVA file or registered an
existing virtual machines. So we're going to be creating
a brand new virtual machine to now ask you for the name
of your virtual machines. So we're just going
to call this, we're going to call
this V center. Alright, compatibility. This is the version of compatibility that you
want for this particular VM. So if you're running
in an environment that have other VMs running early aversion,
say 55046 e.g. and you go and deploy
a 65 installation e.g. you won't be able
to use this VM on earlier versions of
ES6 psi under 65. It's up to you what you
want to pick in the demo. We're just going to go for 65. You're going to select what
operating system it is. We're going to say it's
Windows 2016, 64-bit. Alright, Next, you'll see this is the data store that we
were talking about. So this is a
datastore that we've already pre-configured
and defined within our ES6 style or your vCenter environment
and sign next. You cannot customize
your settings, so you can go ahead
and do this later. But it's also a good thing
to perhaps do it now. So you want to
allocate how many CPUs you want to give it, right? You can expand this
and you can say, I want these many
cores per socket. I can enable a few
other features. How much RAM do I want to
give it a full gig of RAM? Or I'd give it more. What size? Hard-drive Duo one. Alright, so we're going
to just leave it as 40, nostalgic controllable, going to leave that as the default. And a few other things
around your network adapter. You've seen here on Drive, video card, et
cetera, et cetera. So that's the simple things
that you want to do. I'm the CD, DVD, your operating system boots up. He's going to try to search for that ISO and it will be
mounted from your CD, DVD. So now we're going to
select the ISO from the datastore that we just
copied that I saw too. Alright, and there it is. So my datastore, I want Tim ISOS folder and then
there is my Windows 2016. Alright. So from here you're going to say next and what this is gonna do if connected power
or is powered on. Then as soon as you boot up this new template,
this new VM, it's going to automatically
go and mounts and boot from this
ISO, which is 2016. Windows Server. Give you a summary of what we've
just done or configured, and we say Finish. You'll see that now
I've got a new vCenter. I saw a new lease
it to VM ready, it's going to boot
from this ISO. So all I do is I
literally, I can open it. And then click on power on that he's not going
to stop to power on. I can quickly now click on the Console tab and
it should open up, let's say as a new tab should be able to
essentially console him. It's the same as
if I'm in front of the physical computer
or somewhere. And then you go home
now presented with your Windows login screen. So I just go through
the simple step C, simple steps of just installing a brand new Windows Server 2016. Alright, just going to
stop the setup installed. And then once it's
done, you will have Windows server configured. So we'll put the
key in later on. We're gonna be doing
2016 data center. You accept the terms custom and he is the disk
that we just selected. So 40 gig is the disk
size that we saw that, that the Datastore had. And we allocated a
disc of 40 gig sine x. And that will now stop
the install process. So it's copying the
files and then it will go through
the installation. Once the installation
is complete, we then need to install a
few other small things, but we'll check back after this. So that is now finished
and it's presented with the basic Windows login screen here I'm going to
configure a password. So putting their posture
that you want to use. Here we are. We're now logged
in to control alt, delete, and login
to our windows. Do some basic
configuration from him. Now once witnesses popped up, what we wanna do is we want to go and configure or
install VMware Tools. So VMware Tools is a piece of software that is going to
be running on Windows, but essentially will
help you communicate better with the VMware
infrastructure, right, with your ESX host
or with vCenter, allow better functionality
with your mouse, with your shortcuts, allows you to remotely controlled power on, power off those sorts of things
from your VMware console. So it's always important
to install VMware Tools. So let's go ahead and do
VMware Tools installed. So you select your bayonet, you just build the center. You see that's the
current screen which we're seeing right now. And we want to click on Actions. You can click on
actions that we can right-click on your
vCenter itself. Same thing. And you got to go guest
OS, install VMware Tools. Alright, so back on our server, sometimes you'll get
a prompt and it'll automatically pop
up on your screen. Otherwise, you
might have to just physically go into
Windows Explorer e.g. and you'll see that now your
D drive these VMware Tools. So I can double-click on this, and this will start the
installation of VMware tools. The other thing you want to
make sure is that you keep the M12 is updated
every so often. Go and check the version
of vn tools that's available and push out a newer version of
VMware Tools to your VM fleets as
often as you can. All right, we're
going to leave it all as standard default. Install. Installation
will finish, you click on Finish, and it will ask you
to restart that VM. So just be mindful
that every time you install VMware
Tools or update via my tools is going to ask
you to reboot your VM.
7. It’s Your Turn: You should now have some
VMs built, if not one, a pool of VMs and
hopefully from class while you were able to now
configure a sx sy cost to, you are now able to
build a whole bunch of VMs and get them built
the best way possible. And then you have a bit
more of an understanding around some of the
technologies around VMware and around
how to configure the best practices in
building virtual machines. But now it's your turn. So get yourself your computer. If you haven't already
installed ASX, I go and do that first
guinea A65 working well, get some ISOS of your Windows servers of other service that you
want to go and build, and then go and build
your virtual machines, go and actually deploy some VMs. Go back and watch some of the earlier lessons
if you do want to follow it step-by-step, but now it is your turn. So why don't you let
us know how you went, let us know if you
were successful in building your own VMs. Now of course, we've
been talking here around VMware ESX site and
building VMs path three. Now it goes a lot
more advanced and we start talking about the center. A lot of corporate
environments will not just be running ESX host by themselves. It can be running
poles of ESX host, multiple ESX host managed
within the vCenter environment. So part three of
these three classes is going to be focusing
on the center. So what's one? And watch to
build yourself your VMs. And now let's go into
the third class. We're not going to be
going into vCenter itself, but that's it for this
class and these lessons, hopefully you found them
helpful if you didn't want it to let us
know let me know in the comments section
and reach out should you need any questions.
Thank you so much. We'll see in the next
part three class.
Emilio Aguero, ...all things tech
