*Some of you may have seen a couple of twitter posts of mine regarding AutoLab lately, that’s because I am in love with this awesome automation tool that simplifies setting up a home lab.Whether it is for study, training, testing, or whatever you use your vSphere lab for, AutoLab is going to be something you will want, especially if you are rebuilding your lab over and over again.
AutoLab was created by the extremely talented Alastair Cooke (@DemitasseNZ) with the help of many, including Nick Marshall (@nickmarshall9), Grant Orchard (@grantorchard), Ariel Antigua (@aantigua), Damian Karlson (@sixfootdad), James Bowling (@vSential) and the vBrownBag crew.
First of all, head over to LabGuides website where you can download AutoLab 1.5 (vSphere 5.5 or 1.1a – vSphere 5.1). There are a few versions of each version. You can get AutoLab for ESXi if you have a server that is hosting the type 1 hypervisor, or there is the Workstation 8 version that you can nest on your desktop/laptop running VMware Workstation/Fusion. (I can confirm that the 1.1a works well on Workstation 10)
You can find the system requirements here.
Once the ZIP is downloaded, you can extract it to a location that has 100Gb spare space or more. Keep in mind that the VMDks are thin provisioned and are going to grow. The overall download size is only ~300mb but this does not include the VMvisor and the VIMsetup ISOs that you will need to download from your my.vmware.com account. If you do not have a license, VMware offers a free 60 Eval. License for your convenience. While you are grabbing the required vSphere ISOs from VMware, you can also grab the powerCLI installation file.
The last lot of ISOs you will need are the Windows Server 2003, Windows XP and Windows Server 2008.
Once you have downloaded or created your ISOs for the installation, you start added your VMs to VMware Workstation. (I’ll just take you though the steps for Windows).
Navigate to the location you extracted the zip file to and open up each folder and double click on the .vmx file available – this will register the virtual machine to Workstation.
At this point, **DO NOT** power on VMs, there is a little configuring with workstation to do first – not much, but it needs to be done.
First you need to set the total amount of host memory the VMs can use. To do this, you need to select Edit > Preferences > Memory. A recommendation on the amount of RAM to use is presented, but you can choose your preferred amount.
The next step is to open up Virtual Network Editor (Under the Edit Menu) – All you need to do is create a new VMNetwork using the VMnet3 and give it an address of 192.168.199.0