Introduction to Virtualization

hello again as you know I'm Eli the computer guy over here Eli the computer guy comm and every man I t.com today's class is introduction to virtualization so today we are going to go over the key concepts you have to understand if you want to implement virtualization within your environment so so many different vendors have many different virtualization products out there and this class is going to give you the overall concepts that you have to understand for you to decide what products you're going to pick and how you're going to deploy them virtualization overall is not a very complicated subject but it has some very specific things that you have to understand especially if you're going to deploy into enterprise environments this class you know we're going to go over the basic terms that you have to understand for virtualization and give you the overall ideas about about how you deploy this in the real world things that you have to think about etc so this class is introduction to virtualization and if you give me a second we will dive right so first let's talk about what virtualization is now you will hear of two terms used synonymously as in to mean the same thing when in fact they don't actually mean the same thing you will hear virtualization and cloud computing used basically interchangeably as the same terms it's very important for you to understand these are not the same terms virtualization is a component within cloud computing cloud computing is something that is much larger than simply virtualization so basically in virtualization what you are doing is you are separating the operating system from the underlying hardware in cloud computing you are separating the application from the underlying hardware so virtualization can be a component within cloud computing but cloud computing is much much much larger than than virtualization itself we have a class on introduction to cloud computing so if you're confused about this please go view that class and it will make more sense I just want you to understand here that virtualization is a component of cloud computing it is not cloud computing itself so when we talk about virtualization what we are talking about is we are talking about separating the operating system from the hardware so back in the old days back back four years ago when you installed an operating system that operating system became inextricably connected to the hardware that it was installed on so if you installed Windows 2008 server onto a piece of hardware it was installed on that physical Hardware on that physical server if you pulled out the hard drive from that physical server put it into a different physical server oh my golly it was a god-awful mess basically with device drivers and other things when you install the operating system it came linked to that hardware and you like I say you couldn't just pull the operating system off that computer and put it on to another piece of hardware it was all bad you could do a migration but it was long and hard and tedious and annoying etc what virtualization does is it gives you a layer on the hardware that you can then install what is called an instance of an operating system so back in the old days you would install the operating system directly onto the hardware now you install something called a hypervisor onto the hardware and then you install the operating system on to that hypervisor that operating system then becomes what's called an instance of an operating system so back in the old days you would have one server here and you would have let's say Windows operating system and those and so Windows was installed onto the server you then install whatever applications you want onto the Windows server that you installed on the hardware the issue when this is if the power supply on this physical server died Windows died the CPU died Windows died if if the Ram went bad Windows died and it was very hard to fix the problem you have to fix this physical server you know sometimes you couldn't find the hardware sometimes you have to get the hardware shipped in for god knows where and it was really really really bad well now what happens with virtualization is you have the physical server like we had before then you put what's called a hypervisor layer installed on this physical server and then you install instances of operating systems onto the hypervisor so now your operating system is tied to the hypervisor it is no longer tied to the physical Hardware now why is this important I mean it's just it's another layer it looks like it does another bit of complication well why this is important is because if you go over to another physical server over here you install the same type of hypervisor on that server you can then move an instance of one of these operating systems over that hypervisor as easily as moving over a file or a picture or a document when you're using a normal desktop computer so now your operating system is connected to the hypervisor all you have to do is you have to have that same hypervisor and stole on a different computer and you can literally move that entire server that entire operating system instance over to that other physical piece of equipment look at me spit like really it can be instantaneous but the most important part to understand is that you can do this now very very very easily because the operating system is now no longer tied to the physical hardware it is now installed on to the hypervisor that is one of the premier reasons why virtualization is very important the next part that makes it very important is because you can now install multiple different instances of operating systems onto one piece of physical server hardware so you have one one sory of one computer you install a hypervisor onto it now you can install different operating systems on it so you can have one physical server you install the hypervisor then let's say you install an instance of Windows 2008 server and then you install an instance of Linux you know abun 2 then you install an instance of Unix all of these different instances of operating systems can be running on the exact same server so instead of buying 10 low-cost low quality servers for all these different operating systems to run on you can purchase one very high power server and have instances of those operating systems run up once you get into the enterprise world this makes a lot of difference remember uh you know if you're new to the computer world you may be thinking it's really cool to have 10 computers or 20 computers well once you start dealing with businesses where they may have a hundred two hundred thousand servers it's really nice to be able to do what is called consolidate those servers onto individual boxes so now instead of having 50 servers spread over 50 physical computers you can have 50 instances of servers installed on one physical box these are the reasons why virtualization is important we're going to talk about a little more you know flush this out but these are the two big things with virtualization you separate the operating system from the physical hardware that is underneath this means you can now move operating systems the same way you can move a file or a picture or a movie document you can now just simply move it from one physical box to another physical box the next big thing is that you can now run multiple instances of operating systems on one physical box so you'd like oh it's what's very popular now if you have a Mac cap here if you'd like with me I'll show you in a second but I have a macbook air every once in a while I need to be able to use Windows programs on that MacBook Air well I cannot install Windows programs onto a mat yes doesn't work you can't install Windows programs onto a Mac so I installed something called VirtualBox which is a hypervisor onto the Mac I then installed Windows XP into that hypervisor and now if I need to use a Windows piece of software I can simply open up a Windows operating system inside the Mac computer and use Windows so that's one of the things that you can do with virtualization now when we're talking about virtualization and we're talking about hypervisors we are generally talking about two different types of hypervisors is called type 1 hypervisor and type 2 hypervisor the type 1 hypervisor is a native or bare-metal hypervisor so with this type of hypervisor you have you have a computer then you install directly on to that computer the hypervisor so there's no underlying operating system you have you have a blank computer you'll install the hypervisor and then you install the instances of the operating system on to that hypervisor and type - or hosted hypervisor you have an operating system underneath so this is probably something that you may be used to by now so when they type 2 hypervisor you have a computer then you either install you know Mac OS X or Linux or Windows 7 you install an operating system onto the computer then onto that operating system you install a hypervisor either virtual box or virtual PC or VMware fusion something like that but that gets installed under the operating system and then the new operating system the instance of whatever operating system only used then gets installed into the hypervisor that's installed on the operating system you understand how that works we'll talk about it a little more in a few minutes so this is the basic overview of what you have to understand with virtualization first thing to remember again virtualization is a component of cloud computing it is not cloud computing cloud computing is something much bigger than virtualization first realization is simply a component within it with virtualization you are separating the operating system from the underlying hardware so this means you can simply drag and drop an entire operating system between different pieces of physical hardware believe me if you've been doing this for 10 years or longer like I have this is a beautiful thing beyond that you can consolidate service so if you have different types of servers running on your network you can now install different instances of servers on the same hardware so like I say you can have one server and then you can have an instance of Windows 2008 you can have an instance of a bun - you get an instance of Unix the blob a buck you can have as many instances as the hardware will be able to cope with then with the hypervisors we are dealing with two types of hypervisors they're literally called type 1 and type 2 type 1 is a native or bare metal the hypervisor gets installed directly on to the hardware there's no middle layer there's no operating system you have you have a hardware then you install the hypervisor and then you install the instances of operating systems onto that hypervisor with type 2 hosted hypervisors this is where you have the computer then you install an operating system whatever operating system will install then you install hypervisor on to that operating system it looks much like a normal application then you install the instance of the operating system that you want to use into the hypervisor that's installed on the operating system which is installed on hardware and then you go about your day there's a final version um you know when you're dealing with virtualization now is you do have the hosted solutions we have you know Amazon Web Services you know one in one GoDaddy of all these different companies have virtualization platforms you can use and that's all they're they're they're proprietary stuff so when you're dealing with virtualization and you're dealing with hypervisors within your environment so within your building within your house within your business you're gonna be dealing with type 1 or type 2 hypervisors you know if you go out and you decide to do something virtual on Amazon Web Services or such that's kind of their own little beast and it works you know however it works I have no idea how it works it just just automatically works somehow the main thing that you have to understand is the type 1 and type 2 hypervisors so let's talk about type 1 hypervisor so when we're talking about type 1 hypervisor x' we're talking about bare-metal hypervisor x' again what bare-metal hypervisor x' mean is that you have the hardware you install the hypervisor directly onto the hardware and then you install instances of operating systems on to the hypervisor so when you're looking at the the hardware that you're going to be using type wieder type 1 hypervisor zhan you're looking at real servers so for me this is one of the servers that I use for type 1 hypervisor virtualization this is a real bad nasty little 1uz on buggabugga boo server so this server is something that will sit in a server rack this is not the type of computer that is going to be sitting on to your desk if you've ever heard one of these things turned on is deafening it sounds like a little jet engine underneath your desk so when you're dealing with type 1 hypervisor x' you're not going to can really be dealing with the types of computers that you would buy it Best Buy or you know at a Walmart marker so when you're dealing with a type 1 hypervisor you're going to be dealing with real enterprise servers the reason for this we're going to we're going to talk about in a minute so with these type 1 hypervisor x' again what you're going to have is you are going to have your physical server here so this is going to be that one user that I just show you you then on to that physical server you are going to install the hypervisor so this type 1 bare-metal hypervisor think of it is a very basic operating system so just like you would install Mac OS X you would install Windows 7 you would install Linux you would install the hypervisor on to the harbor so it's a pretty simple install process basically you put in the CD you hit next next and then it gives you some information at the end we're not going to go into this in depth and actually show you how to set this up we will do that at a different class right now I just want you to give you the concepts then once you've installed the hypervisor you can then install instances of operating systems on to the hypervisor that is on that physical hardware so I say you can have Windows 2000 a Linux UNIX etc etc etc basically as long as the hardware can support it you can continue to put instances of operating systems on there you could have 50 instances there a hundred instances god help you however much you uh you want to put on there now here's one of the big things when you start using hypervisors it's going to throw you for a loop kind of like the first time you use Linux if you remember the first time you usually use Linux you know you install it and then you get a little blinking cursor and then you don't know what the hell to do next that is going to be what is going to happen with you the first time you install a type-1 bare-metal hypervisor because you're going to install that hypervisor on to your your hardware and then when it reboots it's going to like give you its IP address and that's about it basically you're looking at the equivalent of little Linux graphics screen that's going to give you very very very very very little information it's going to give you its like its IP address what kind of processor is on it the RAM that's all it's going to have and you're gonna scratch your head you're gonna be like what the hell what do I do with this because you're just looking at a screen and you're basically just getting blinking cursor well the reason for that is with a type 1 hypervisor you need something called a management console so the management console is what actually manages the hypervisor so you don't do very much of anything on the physical computer directly with that hypervisor what happens is you sit at a computer like this on the computer you will have management software installed and then using that management software you will then manage this hypervisor we'll get into this more when we actually do a practical class on the hypervisors but basically what you need to understand is you are going to have a computer that will have the management software installed using that management software you will connect to this hypervisor that's why they give you the IP address of the of the computer and then from there you are able to install and manage these instances so basically I would go to the physical computer so this computer I would I would install the hypervisor on I would then throw this into the rack I would connect it to the network I would make sure that this server gets the IP address so the hypervisor will say whatever the IP address is right so once this is in the rack once it has an IP address I will then go to my normal desktop computer that has the management software installed and then I will be able to configure the hypervisor from here so I'll be able to install operating systems from here I'll be able to do all the funky configurations this is very important to understand like I say when this server boots up the screen you're going to get again it's going to tell you the computer has a xeon processor how much ram it has and a few other almost pointless things there's very very very little duke you can do at the computer with the hypervisor installed you most of the time basically all you can do is like change a password and chain key IP address that's about it so that is how you're going to be interacting with the hypervisor on the server so through the management console why this this happens in this way is because since the management is controlled by the management console you can now how this management console make things automatically happen with servers with this type of hypervisor installed so let's say you have a rack of physical servers those 1u servers I showed you say I'm not going to write it now let's say you have 20 in that wreck right you then have the hypervisor installed on all 20 of those computers well now with the management console you can move instances of operating systems between these physical servers again basically like copying and pasting so if you have Windows 2008 server running on this hypervisor on this server you can simply move it to this server through the management console and it will just work basically you just click I want to move this instance from here to there and it'll just automatically happen you can now move the instances of the operating system that easily with the management software you can also get a lot of cool other features so so when you're using servers if you've been in an enterprise environment you know that servers need different amounts of resources throughout the day so if you have an Active Directory server an Active Directory server is what allows you to authenticate or log onto a Windows network now you need to hit that server a lot or your employees will need a hammer that server a lot let's say you know in the morning or after lunch is over etc there's going to be certain times of the day and that server is going to need a lot of resources at other times the day is not going to need so many resources well what this management software can do is it can automatically move instances of operating systems between physical servers based on their current resource needs so let's say right now we have these three instances of operating systems running on this hypervisor none of them is being used very much so none of them need very many resources they're all just trucking along doing fine well all of a sudden a lot of people start logging into the Windows 2008 server it starts needing a lot of resources it starts needing more resources than this physical server can handle well the management soft we will then automatically move this Windows 2008 instance to whatever server physical server has enough resources for to run properly so it can just migrate literally that easily that automatically why this is important in the enterprise world is electricity bills get very hot this one little server down here can probably cost one or two hundred dollars a year in electricity it pulls all audible electricity so obviously if you have hundreds or thousands of servers that can be a very big power bill well if you can automatically consolidate servers or send them out to different pieces of hardware based on the requirements you can have your Hardware be turned off most of the time and only be turned on when it's actually used that's one of the cool things with a management software and the new physical server hardware that's out there is this management software can actually turn these servers on and off as needed not simply moving the instance but actually turn them on so this server can be off the management console or the management software can decide it needs to use it it can turn it on it can move the instance and that that's how easy it goes also with the management software it can do things for fault tolerance so let's say you have this server the instance of the server running on this hypervisor well with the management software if the physical Hardware fails that's running all of this the management software can automatically migrate these instances literally so quickly that you don't even realize that the physical Hardware failed so imagine that especially in the enterprise world if they serve at that hardware for a server crashes it's no big deal all the instances of the operating systems were automatically moved they're all up and running your users never saw any downtime they never even saw a blip and so now you can you can you can fix this Hardware whenever you get around to it that's one of the things that makes these type 1 hypervisor so cool and again all these powerful features are probably not something be using in your house you need to use in your house but in the enterprise world they're they're really really really good now when you're you're doing this a one thing to think about with when you're deciding the the hardware and such that you're going to use is that the some of these type 1 hypervisor --zz allow you to do something called over allocation so what over allocation means is if this physical server here only has let's say 16 gigs of ram right and you want to put multiple instances of operating systems onto that hypervisor so you want to put windows and linux and unix right now what you can do is you can actually give these different instances of the operating systems more total ram then the computer has you can say this Windows 2008 server can have up to 12 gigs of ram this linux server can have up to 10 gigs of ram and this UNIX server can have up to eight gigs of ram if you add all this up it comes to 30 gigs of ram well there's only 16 gigs of ram on here what over-allocation allows to happen is each one of the instances of these servers thinks they have this much ram but the server the hypervisor only gives them the ram that they actually need so again remember throughout the day your server is going to need more or less resources so at the high point your Windows 2008 Active Directory server might need all 12 gigs of ram you know one person of the day might need all that ram the rest of the day it only needs two gigs well what can happen is when that Windows 2008 server needs at 12 gigs of ram the hypervisor can give it all that ram while your other servers don't need it they're just sitting there you know once a file server runs a web server there they're fine with you know 2 gigs of ram each well once the time has passed where this Windows 2008 server needs all that RAM the hypervisor can take it back but the Windows Server doesn't see it the Windows server still thinks it has 12 gigs of ram but the hypervisor can take it back and give it to let's say the Linux server or the UNIX server if it needs it so in the morning the Windows server needs 12 gigs of ram so it uses all 12 gigs of ram and the the Linux web server doesn't need it well then an hour later the Windows server doesn't need as much ram the linux server let's say it's getting hammered as a website it needs all the ram it can get so then the hypervisor now gives that linux server the ram it needs that is something called over allocation and if you're looking to purchase a hypervisor or use a type 1 hypervisor it is something that you should look for some of the old hypervisors or some hypervisors you may run into they only allow you to split up the ram um statically so you can give you know if you give the Windows 2008 server 12 gigs of ram then you've only got 4 left to split between those two so you can give that one to that one 2 or this one 3 this one one basically however much ram you give to these instances of servers those all have to equal the total amount of RAM that is on the physical server so that's static allocation with uh with over allocation or dynamic allocation the total doesn't have to equal the exact amount here because with the over allocation the hypervisor can move the RAM as neaby now when you're dealing with these these these hypervisors when I'm talking about it there are a lot of different hypervisors out there there's a lot of different vendors that sell virtualizations type on hypervisors or citrix there's a vmware there used to be virtual iron that got purchased by Oracle I'm not sure what they're doing anymore there's Microsoft etc now when you go out there what you're going to find is that the hypervisor generally generally to say that I always say generally the hypervisor is free yes surprisingly enough either from VMware or Citrix whatever company most of these hypervisors I think almost all these hypervisors are based on something called as n X E and so it's called the Zen so this was created years ago on the linux platform it works so well basically everybody took it it was open source it was free it works so well again like I said people decided we'll just go with that versus creating our own so when you're dealing with a hypervisor you can get the hypervisor for free well again whether you use VMware whether you use Citrix whoever using you can normally get the hypervisor for free where they get you is that the management software what does all this you know flipping operating system instances around and all that fault tolerance and stuff that is what they could argue for so if you go out there again to Citrix or VMware for a type 1 hypervisor you will be able you should be able to install a free hypervisor and free basic management software that you can use both personally and commercially so last time I love VMware the server hypervisor in Citrix you could use for free in a commercial environment you know if you if you work for Microsoft you could install for free well what they do is they only give you limited features with the management so you can install operating systems instances on the hypervisor you can do some basic management tasks that is it if you want to get the really cool super features where you can move instances of operating systems around you know in the blink of an eye that will cost you money and it will cost you a lot of money so so last time I looked like with VMware the basic level of their management software that was really worth a damn they had some stuff that was cheaper but then the stuff that started actually having all the really cool features started at about $3,000 so last time I looked it was $3,000 for the management software and it went up from there you know ten twenty and a hundred thousand dollars you know depending on what you want to do this is just something that you should keep in mind if you're going to be trying to use a type 1 hypervisor again what is really cool with it is almost all the companies again it's up to you to look at the license but last time I looked at the licenses it was for commercial use so you could install the hypervisor and you can install a basic management console absolutely free the thing is if you wanted that really cool functionality that's where you had to pay for this super expensive management software that that's where it okay like I said gets expensive so again type 1 hypervisor x' our bare metal you installed hypervisor directly on to the hardware you then install instances of operating systems on to the hypervisor but as I say you don't do that directly on the hypervisor or on the physical computer you use a piece of management software installed on a different computer to interact with a hypervisor and do all the management you know install the operating systems configure whatever settings etc we talked about the overall location so what over-allocation means is if your hypervisor allows it you can provide RAM more RAM then the the server physically has so with this we have one compute as 12 gigs of ram one that has ten one it has eight that comes to 30 gigs of ram the physical server only has 16 gigs of ram basically what you're betting on or what you're planning is that at any one time you will only ever be using 16 gigs of ram so sometimes your Windows 2008 server can have 12 gigs of ram and sometimes your UNIX server needs 8 gigs of ram the main thing is that at any one time you only have nope not all the instances together aren't going to be using more than 16 gigs ram and finally like I say when you're going to be using these hypervisors and management software again free even for the commercial world even if you work at Microsoft you can install it and run some Microsoft website off of it completely legit legally at least last time I look the issue is if you want the really cool features you're gonna have to pay a stupid foolish about a month that's how it goes so we talked about the type 1 hypervisor so these are bare metal hypervisors so now we need to talk about type 2 hypervisors or what are called hosted hypervisors posted hypervisors are again our hypervisors that are installed onto the operating system itself so whether you have Mac OS X Linux Windows 7 etc basically you have the physical computer you install the operating system onto the physical computer you then install the hypervisor onto the operating system and then you install the instance of the operating system onto that hypervisor so before you just had you had the the server and then you had the hypervisor basically now you have the server then you have an operating system then you have a hypervisor then you have the instance what makes this nice what makes it easy and why you all probably would want to do this versus the type 1 hypervisor is you don't need this management software in order to configure and play with the instance of the operating system that is on your computer basically the instance of the operating system on a type 2 hypervisor literally opens up in a window just like any application and then you can just use it you can right-click you can left-click you can write documents etc you don't need management software in in order to be able to play with it so for most people this is the type of virtualization that they're going to be using even in the corporate world a lot of people use type 2 hosted hypervisors I say just just because it's easy you know if you're not worried about consolidating a hundred servers into one box you know you just want like 2 or 3 or 4 or 5 servers running on one box it may be a lot easier to use a type 2 hosted hypervisor because you can just you just turn on the screen for the box you a little mouse you can do whatever you need to do and then you can walk away from you don't need this management software now the nice part again with with type 2 hosted virtualization is many of the products are free so from Microsoft there's Virtual PC from from Oracle used to be some Microsoft the Sun Microsystems there is a VirtualBox there are other options out there these type 2 hypervisors are generally free to use sometimes if you want to use the more advanced features you have to pay a little bit of money but you know that that's how it always goes a couple of the warnings that I will give you if you decide to start using a type 2 hypervisor is be careful of the resource allocation that you give your instances of operating system so if you give a server that you're installing onto your computer let's say 4 gigs of RAM for the instance it will automatically take all 4 gigs of those of RAM even if that server is not using it right then and there so we talked about with hyper with type 1 hypervisor x' where you can do the overall location that's not really how it works with these type 2 hypervisors for the most part if you give an instance a certain amount of RAM or a certain hard drive space the the virtualization hypervisor will automatically take that from the host computer for the ovide instance why this can be a problem is because you can literally take so many resources for your virtual virtualization virtualize instances that you can end up crashing the host computer so the host computer let's say it needs 2 gigs of ram simply to run you know if you're using Windows or something well if you have 5 gigs of ram and then you give 3 gigs to some server and then you give another gig to another server well if those 2 servers are turned on at the same time 4 gigs of ram will now be taken for those instances your hosting computer now only has 1 gig of ram left to do ever what it needs to do and then it just crashes it all goes bad so just be careful about this whatever resources you give to the instances of the operating system when you turn them on the computer will automatically take those resources the other warning that it will give you is be careful of networking if you are going to be using the host computer for other things so let's say you you create a web server in an instance and you create an FTP server and it you create an Active Directory server in an instance and all those need to use the network well if you open up Outlook or if you're browsing the web on the host computer operating system sometimes that network traffic can all get a little little Wiggly and it doesn't work properly so I've seen this in the past where we've created instances of operating systems and turn them on on the host computer and then email just stops working web browser works fine file transfer works fine but Outlook just stops receiving email this can be one of the issues that comes about when you're using these type 2 hypervisors so if you have the instances turned on and you're using the host computer doing stuff things may make it a little weird the other warning that I will give you is with all this a type 2 virtualization software virtual pc VirtualBox etc they almost always have operating system add-ons this is this is software that you can automatically install into the operating system that's installed on a hypervisor this will make the operating system instance run much much much better I don't know why it's really weird that it's not automatically installed but if you don't install these add-ons you can have some problems for some reason uh but yeah but that's basically what type 2 hypervisors are and these are probably what you're going to be using we do have a class on type 2 hypervisors a introduction or you know VirtualBox to a VirtualBox class you can go do it to a search fork we have one which will show you how all this works but basically with the type 2 hypervisors again you have the hardware then you have a normal operating system windows 7 OS x linux unix whatever you're using then you have the hypervisor then you have the instances of the operating system and that allows you to run multiple instances of Optive and operating systems on one computer you can do this for you know testing out projects if you're creating new software you can test it out on different operating systems if you're a web developer this means on one computer you could have a Mac OSX computer and seven and a Linux and you can look the website you're designing you guys if you're going out to test for these Microsoft tests you can buy a really really really powerful desktop computer but let's say 30 gigs of RAM and then you can actually create an entire virtual network on that one computer so you can create a 2008 Active Directory server in 2008 iis server and for client computers and a Linux computer and then you can all try to network them do all the weird projects that Microsoft wants you to be able to do you can do all of that so those are some of the reasons that you would use a type 2 hosted hypervisor in the real world now at this point you may be thinking well oh then this virtualization technology is really cool this is great but the problem is is I've got 50 servers up and running and they're already up and running and all the virtualization sounds great I don't want to have to migrate each one of those servers to a new virtual server they'll just take forever well one of the nice parts now is there are a lot of ways to convert old operating systems that are installed on the hardware to the virtualized environment so depending on what a virtualization product you're using they have conversion tools basically all you do like normally you copy the conversion tool onto a CD you boot the CD on the server you want to turn into a virtual computer it boots up it will then package the entire operating system and everything into a virtualized instance and then you can simply put that onto a server that has a hypervisor so you know whether you copy it onto a hard disk drive or you do it over the network etc basically what the software does is it images the computer into a virtual hard drive format whatever hard drive format your uh your your hypervisor uses this is something to be careful about the different companies do have different virtual hard drive formats so make sure whatever virtual hard drives you have compatible etc so basically like if you decide to go with VMware if you virtualized solution you can install the hypervisor onto one piece of hardware you then take this CD over to a server that you wanted virtualize you boot the server off the CD it turns it turns that server into a virtual hard drive you can then move that virtual hard drive over to the hypervisor and now that's all you have to do for the migration process there's no copying and pasting there's no migrate and active directory and all that crap basically you have a they have a normal server or the operating system is installed on the hardware you run this conversion software it basically is able to package up to ball up that operating system into a pull hard drive and then you can move that virtual hard drive over to your hypervisor another nice thing nowadays is many of the backup solutions actually back up into virtual hard drives so so with Windows and with something called a Cronus different types of backup software they when they do their backup routine the format that they back up into is a virtual hard drive so if you have a computer and you have this backup software and salt you can simply backup to a virtual hard drive and then move that virtual hard drive over to the hypervisor that you want to use it really really really is that simple if you want to play around let's say you want to use Linux or UNIX and you want to do very specific tasks one of the nice things they have with uh with the virtualization now is something called appliances so you can go to VM ware or Citrix and they will have a list of appliances these appliances these virtual appliances are basically um servers that have already been configured for you so if you want to know bun to web server and you don't want to have to go through the whole install routine you can download in bun two web server appliance and it's it's it's already been set up so it's a little virtual hard drive you can download with all the configurations basically all you do is you put that onto the hypervisor the hypervisor turns it on and then away you go you don't you don't have to go through with the installation process and the configuration process etc with these appliances there's a lot of cool things not only can you have servers but you can have networking equipment so you can have virtual routers you can have virtual switches etc this gets really complicated and gets way beyond the introductory class but if you're worried about security in your real world you know routers and firewalls networking equipment provide a layer of security for servers when network communication happens well you can have the equivalent basically virtual routers virtual firewalls on your hypervisor then you can add your virtual instance is of the operating systems do their networking through those virtual pieces of networking equipment and this just provides a layer of security so basically without having to buy you know very expensive Cisco equipment you can download these virtual appliances and come up with a really insane complicated networking scheme you can at this point I wouldn't do it if I were you but but you can't this is something to think about so the big thing is if you're thinking about migrating from how we've been doing it or the operating system is installed on the hardware to virtualization you don't have to go through the nasty old migration process you know you don't basically all you do is you use the conversion software it will convert the old server into a virtual instance you then move a virtual instance to the hypervisor and then away you go again one of really nice things with modern backup software is they will back up to a virtual hard drive format so if the physical server fails you can simply move that virtual hard drive over to a hypervisor and the server is back up and running that quick then the final thing like I say is these these appliances you should look at you should play with because people go out they configure servers to do very very very very very specific things and then instead of you having to install the operating system and do all the configurations you can just download that appliance basically turn it on and away you go really I mean even though it doesn't take too long to set up in a bunch a server you know it takes 30 minutes to an hour let's say you know if you if you download and set up on these appliances you can literally be up and running in five minutes that's pretty quick so final thoughts for this introduction to virtualization class virtualization is a great new tool it is very very very very very useful and if you've been in the IT field for a while it is just it's just a godsend it really is great basically just remember all virtualization does is it separates the operating system from the underlying and hardware so you can move it around just like a picture just like a movie file etc virtualization is not cloud computing virtualization is a component of cloud computing cloud computing is something much larger fertilisation separates the operating system from the hardware cloud computing that separates the application from the hardware if you don't understand what that means no just just keep doing these classes and you'll understand later basically it is a very big distinction it doesn't sound like a very big distinction by the end of the day it is a big it's a huge distinction one of the things I will give you the warning about remember we're professionals here this is not simply about setting up servers etc licensing you know I always talk about licensing um because in the real world if you're going to be management level um licensing can be evil so be careful when you're going out to purchase hypervisors when you're going out to purchase virtualization software their licensing can be a nightmare um so depending on what hypervisor or management software you're going to be using let's say if you're using a type 1 hypervisor x' um it could the cost can get get bad really quick so sometimes with licensing this is this is something I ran into the real real world so sometimes with licensing let's say for the hypervisor and the management software sometimes each license covers one physical box so you have one server and you need one license not seems crazy stuff well yeah that is pretty simple well then sometimes you know since we're dealing with servers here rich is dealing with real servers real servers many times can support multiple processors so you could have a two socket motherboard or four socket motherboard or eight socket motherboard so you can actually have up to eight processors on the motherboard well many times the virtualization software is licensed per socket so if you have two processors on one physical server then you need to purchase two licenses ooh okay that can get a little painful but you know hey maybe that works you know if you've got two processors I mean that's a pretty powerful server well here's where I can get dumb ridiculously quick sometimes you have to pay licenses per core so this is a xeon quad-core processor if i used some of the enterprise hypervisors out there i would have to pay a license per core even though it's one chip so one processor in the server has for course you have to pay for four licenses I wish I was a joke so this is something you have to be exceedingly ridiculously careful about in the virtualization environment license it you think Microsoft licensing is bad virtualization licensing makes Microsoft licensing look like a joke um so make sure you know what you're buying again you know if you have two processors in one physical server you may have eight cores or 16 cores and so now $1,000 for a license maybe $16,000 that's a lot of money so be very exceedingly careful buy the license read the licenses again the nice part when most of this virtualization software is when you're playing around or even if you're doing simple things in the commercial world it's absolutely 100% free you can use it like I say Microsoft can use it once you start getting into these more powerful things at the virtualization software it can do like I say you can go from free to $16,000 in the blink of an eye if you don't know what you're doing it can be really really really bad so as we talked about type 1 hypervisor or bare metal hypervisors this is where you have the hardware you install the hypervisor then you install instances of the operating system onto the hypervisor now remember with this in order to manage that hypervisor if you need a management computer so it's just a normal computer like when I do it instead of normal Windows 7 desktop I install the client software onto that Windows 7 desktop and then that client software communicates with the hypervisor and I'm able to do all the communication stuff again like I say the first time I booted up a real bare-metal hypervisor I mean all you get you I think I did VM serve VMware server you literally you get it you get a yellow box it tells you the IP address those you have a Xeon processor and how much RAM you have and then you scratch your head and do what the hell do I do next well what you do next is you go over to your your-your-your client computer and configure everything the nice part with this is that again you can move instances of operating systems between different pieces of physical hardware fairly easily if you're willing to pay the ridiculous amounts of money I say with VMware it starts about $3,000 you can do all this fancy auto magical stuff so you can have the management software where it turns on servers as you need them need them turned on you can have it so it automatically moves instances of operating systems if a piece of physical Hardware fails so even in a small office environment you could have three physical servers that are connected for virtualization if one fails all those instances of the operating systems automatically migrate to the other servers so there's no downtime so this I mean it's expensive but but it can be very useful the main thing to remember though is you're going to pay a lot of money for that as we talked about the hypervisor and the basic management software is almost always free again it's all based off the Xen Xen that was created ten years or so ago Xen Xen is robust stable you can't do much better than it so nobody really has tried almost everything is based on it then we talk about the type 2 hypervisors type 2 again we have a class on a VirtualBox for virtualization all this is is you have a normal computer Mac Windows 7 Linux whatever you install the virtualization software onto that operating systems to install Virtual PC VirtualBox VMware fusion parallels etc you then install the instance of the operating system on to that virtualization software so this is very useful again in the Mac world I have a MacBook Air when I need to use a piece of Windows software I can literally open up windows within a window on the Mac use windows all I want and then shut it down when I don't need it anymore the things that you have to be careful about if you're going to be doing type 2 hosted virtualization is again remember with allocation if you if you give too many resources to your virtualized computers your host computer may not have enough resources to keep running and you may end up actually crashing your host computer remember if you give resources to the virtual computers in a type 2 environment of the computer automatically gives those resources away and then your host the computer can't access them anymore the other thing to be careful about is with networking if you have virtual servers and they're using networking and you're on your hosted computer and your hosting computer is doing networking you can have issues the biggest one I saw in the real world was when we had web servers running in the virtualized environment on my computer if I open up Outlook sometimes you just want to get email as soon as you shut off all the virtualization software you got email just fine you know I'm not going to tell you why it happens it just happens finally we talked about converting normal servers to virtual servers so if you have servers you know they've been running five years ten years 20 years you don't want to do a migration normal migration you can convert those servers to virtual servers and house them into a hypervisor so this is really big right now remember you know when I started playing around with with computers and started in the professional world is back with Windows 95 and Windows NT some people still have NT servers running sometimes those NT servers are still doing mission-critical work the problem is is none of the hardware that those empty servers are running on is sold anymore and if that NT server crashes for any reason the climb is screwed I mean it really really is gone awful bad so what you can do is you can convert that NT server into a virtual server and you can put it on the hypervisor now it's still old and still archaic and they still do need to upgrade but they're no longer risking the death of their entire business you know what I'm saying there's a difference between obsolete and something crashing and dying and burning and taking everyone with it so this is something with virtualization that you should think about for your clients so you go in they have old NT servers or 2000 servers um basically you can virtualize those put them on 2 hypervisors and now they're stable they're obsolete but they're stable and hey you made a few bucks out of it so this was a class introduction to virtualization virtualization and you know it's it's not horribly complicated to do we do have a class you know VirtualBox for virtualization I am going to do a class with one of the type 1 hypervisor to show you how is the work again this is relatively simple technology at this point in time it is completely 100% stable I have seen virtualization for 10 years now it's been stable basically for like 10 years now so this isn't like this isn't cutting edge this isn't bleeding edge this isn't any of that basically just have to figure out how you want to configure every you know you have to sit down you have to figure what you want to do figure out what you want to do then you have to figure out product you want to buy then you have to configure the product and then you install everything and then you go home it's really that simple you know a lot of people get worried about virtualization they think it's all what everything blows up we're not there anymore things are much more stable now robust etc this is old technology this is this is paper clip technology basically it works as long as you can figure it properly it works it's not that complicated etc etc so as you know I'm not a computer guy over here for galata computer guy calm and everyman IT calm again this class was introduction to virtualization I enjoy teaching it and look forward to see you at the next one

Channel: Eli the Computer Guy

Views: 887,133

Rating: 4.9333138 out of 5

Keywords: Introduction, to, Virtualization

Id: zLJbP6vBk2M

Length: 58min 57sec (3537 seconds)

Published: Fri Feb 03 2012