https://staging.projecthomelab.org/index.php?action=history&feed=atom&title=AutoLabAutoLab - Revision history2026-04-26T02:28:29ZRevision history for this page on the wikiMediaWiki 1.44.2https://staging.projecthomelab.org/index.php?title=AutoLab&diff=24&oldid=prevTravis: 1 revision imported2020-07-31T17:00:55Z<p>1 revision imported</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<tr class="diff-title" lang="en">
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 17:00, 31 July 2020</td>
</tr><tr><td colspan="2" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div>
</td></tr></table>Travishttps://staging.projecthomelab.org/index.php?title=AutoLab&diff=23&oldid=prevopenhomelab>AlexGalbraith: Added categories2016-05-17T19:45:03Z<p>Added categories</p>
<p><b>New page</b></p><div>[[Category:Automation]][[Category:Management]]<br />
[[File:AutoLab color leftside Cropped.jpg|400px]]<br><br />
== AutoLab Overview ==<br />
[http://www.labguides.com/autolab AutoLab] is a package of build automation for your nested vSphere lab. <br><br />
Its main aim is to make your lab disposable, so you have no fear of breaking a carefully crafted home lab by trying something silly or misconfiguring a feature.<br><br />
AutoLab is deployed on top of your existing VMware virtualization platform, Workstation, Fusion, Player or ESXi. The AutoLab is just a collection of VMs<br><br />
On the development system the basic AutoLab can be rebuilt in under two hours with minimal manual intervention.<br><br />
Your first AutoLab build will take longer, finding all the parts & putting them in the right place can be confusing.<br />
==AutoLab Requirements ==<br />
You will need a reasonably beefy physical machine to deplopy AutoLab. AutoLab is developed on a Quad Core i7 with 32GB of RAM, a 240GB SSD and a 2TB hard disk. An SSD is important if you don't want to wait all day for VMs to boot and at least 16GB of RAM is required, more is always better. <br><br />
While AutoLab is running on your physical machine, don;t plan on doing anything else with that machine. AutoLab should chew up all your RAM so the lab runs as fast as possible. I always use a second laptop to read emails & documentation while I'm AutoLabing.<br><br />
Autolab can run on a PC, a MAC, or on [[Cloud_Homelabs#Ravello|Ravello]] or [[Cloud_Homelabs#Bare Metal Cloud|Bare Metal Cloud]], these options allow you to rent hardware rather than having to buy your own lab machine.<br><br />
You will also need the installers for the versions of vSphere you want to test as well as a Windows Server Trial ISO. There are a few more pieces of licensed software you will need, everything is outlined in the deployment guide which is on the AutoLab site.<br />
Autolab has it's own support forum on this [http://reddit.com/r/AutoLab/ sub-Reddit] <br><br />
== Inside AutoLab ==<br />
The AutoLab VMs live inside their own, private network. Isolated from your normal lab network.<br />
Once your AutoLab is built it will contain a few VMs:<br />
* FreeNAS shard storage and build server<br />
* FreeSCO router<br />
* Windows Domain Controller with SQL Express<br />
* Windows vCenter<br />
* Up to three ESXi servers<br />
If you use all of the automation then the ESXi servers will form an HA & DRS cluster with both NFS and iSCSI datastores provided by the FreeNAS VM. There is even a TTYLinux VM that can run inside the cluster. If you provide some Windows ISOs then some nested VMs can be created too. <br><br />
== More than vSphere ==<br />
In addition to the basic vSphere cluster the following additional products are supported with AutoLab:<br />
* [[VMware View]]<br />
* [[Veeam#Veeam Backup & Replication|Veeam Backup & Replication]]<br />
* [[Veeam#Veeam One|Veeam One]]</div>openhomelab>AlexGalbraith