To Build a lab:
I have been thinking a lot about how there seems to be a few gaps in the VMware community when it comes to learning to set up a VMware vSphere lab environment. So I thought I would take the time to try and put together a full on post dedicated to resources on building a VMware Lab. When I first thought about this I wasn’t sure if I wanted to do a full A-Z build. Covering every single feature or deployment, but often times I would rather not re-invent the wheel. There are MANY post covering how to do this in general but I wanted to make a point of identifying the types of labs that you can set up and how to exactly go about it as well. The key word is “lab” so you don’t want to spend a ton of money (unless you have it) on your lab. To start off there are a multitude of setups you can do and many ways you can do it. I also want to stress that if you are getting ready for your test then YOU need to have one of these labs.
vSphere Lab video 2 Cents and quick overview! (this is my fist video post)
Nested VMware vSphere Lab
- Hosted on a Desktop Virtualization Product Like VMware Workstation 7 or 8
- Allows for easy HCL compliance
- Does require a robust desktop
- Can get slow depending on what you’re doing (design)
- Networking is all virtualized (plus)
- Storage can be virtualized or something like iSCSI can be used
- Mobility (can move VM’s around between desktops and laptops)
Physical VMware vSphere Lab
- Runs ESXi as bare metal
- Is more expensive
- “Real World” set up so is truly a lab
- Must meet HCL
- Will need Physical Networking (Managed networking highly recommended)
- Takes longer to build out or rebuild
- Can run nested labs on top of ESXi (pretty much using ESXi in the way you would use VMware Workstation)
- Storage can be virtualized or something like iSCSI can be used
- Can move hosted VM’s but the physical systems are not portable/mobile (depends I guess)
In a nutshell I will be covering the nested set-up since that seems to be the less expensive rig. I also love the fact that I can move it around to my laptop and desktop which is quite handy. Also fairly easy to backup as well.
***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~
RDM (Raw Device Mapping) has changed a little between VI and vSphere. They have continued to improve over time as well. Now there are a lot of resources out there for RDMs in general but I just wanted to do my own research and learn about the particulars. I also wanted to note some of the blogs I used and the difference between vSphere 4 and vSphere 5. I don’t think things have changed a whole lot for RDM’s other then the size of pRDM (Physical or Pass-thru) have been increased almost to 64TB.
Now RDM is more of a topic of “use case” than anything. Other things like “Performance” can be debated on all kinds of levels and usually there are always workarounds to avoiding using RDM’s. Now the real limitation to RDMs in my opinion is pretty much not being able to back it up with the vStorage API. That is my only real personal gripe. The size of an RDM can sometimes be more accommodating for large Databases and large file servers in some cases. Again this is “use case”. For the most part when I see RDMs implemented in our environment it was done based off of bad logic… meaning some people don’t understand the risk associated with what they are doing or wasn’t necessarily the best “use case” they intended it for. Mostly when I see that a pRDM is used a vRDM would’ve worked better.
A misconception: “RDM’s are more secure because you cannot snapshot”
I am not sure where I can start this discussion. This was what a colleague of mine told me around the first time I started learning vSphere 4 and I kind of believed him at first but he too was relatively new and I know being in a virtual environment there is a way around anything..almost.
This was a hot topic because we were virtualizing AD servers and they were arguing with the AD team about how they should implement AD on vSphere. The security team didn’t want anything to do with it and they didn’t want to go along with it at all. So the engineer(s) decided to throw out the RDM as a way to keep people from being able to snapshot AD so they could keep AD from blowing up (Misconception as well) and securing the data because you couldn’t just copy it off. What they were thinking was that if they cannot actually see the VMDK file then no one can steal or retrieve the data. What a misconception that is… there are many ways to convert any RDM into a VMDK file as long as it’s not over a particular size that is – 2TB – 512mb.
You can use a variety of tools from VMKFSTools, Cold Migrations, sVmotion (vRDM) and cloning. Of course there are limitations like snapshots and such which can prevent this from happening. What you need to note is that if you are using a RDM for a particular case make sure you DON’T accidently convert it to a VMDK file.
The following reference is from a KB located here:
With file relocation:
- Any non-RDM virtual disks are physically moved to the destination.
- The virtual machine configuration files are physically moved to the destination.
- Raw LUNs themselves cannot be moved, as they are raw disks presented from the SAN. However the pointer files (RDMs) can be relocated if required.
- When performing a cold migration of a virtual machine with RDMs attached to it, the contents of the raw LUN mapped by the RDM are copied into a new .vmdk file at the destination, effectively converting or cloning a raw LUN into a virtual disk. This also applies when the virtual machine is not moving between ESX hosts. In this process, your original raw LUN is left intact. However, the virtual machine no longer reads or writes to it. Instead, the newly-created virtual disk is used.
- If you wish to cold migrate a virtual machine without cloning or converting its RDMs, remove them from the configuration of the virtual machine before migrating. You can delete the RDM from the disk when removing it (the raw LUN contents are not changed). Re-add them to the configuration when completed.
Again other references can be noted in the KB. Also if you wanted to convert your RDM from Physical to virtual mode just follow this KB here. Also Scott Lowe did a great job writing about this similar subject in regards to svMotion here.
In short, I just wanted to know a particular reference and the misconception of RDM’s being secure because you can easily convert an RDM to a VMDK and VMDK to RDM.
I would like to thank VMware and all the VMware Bloggers if you know of any other good resources let me know and I’ll update it.
Resources vSphere 4.1:
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_esxi_server_config.pdf (Lots of references to RDM)
http://www.virtuallifestyle.nl/2010/01/recommended-detailed-material-on-rdms/ (Lots of Good stuff)
http://www.virtualizationteam.com/virtualization-vmware/vmware-vi3-virtualization-vmware/dont-use-vmware-raw-device-mapping-rdm-for-performance-but.html (RDM performance Blog)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005241 (Great resource for learning RDMs and Conversions)
http://www.vmware.com/files/pdf/performance_char_vmfs_rdm.pdf (RDM Performance Article)
http://blog.scottlowe.org/2010/08/18/storage-vmotion-with-rdms/ (Scott Lowe’s Blog on sVmotion RDM)
Resources vSphere 5:
http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-virtual-machine-admin-guide.pdf (pg. 39)
http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf (pg. 140)
***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.org and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~