In previous posts we discussed considerations for building a Home Lab and for deciding on network ranges to use. Once we know the networks we will be using, its time to start thinking about services that will be required. For me the first service is always Domain Name Server (DNS). This is a foundational building block for many systems which expect forward and reverse lookups to be working before you deploy (like vCenter Server).
Its somewhat common to see folks use a name in the reserved top-level domain of .local suffix, like corp.local. I’m not a fan of this practice, as RFC 6762 spells out special considerations for this domain, and that it should be used for link-local names only.
I’ve also seen folks use domains with a common top-level domain, like bwuchlab.com. As of this writing that domain is available for sale, so there wouldn’t be any conflict or such if I started using it internally without registering the domain. I feel like this is a bad practice as someone else could buy that domain, I’d have no control over it, but may have some documentation or screenshots that include that name. I prefer to use a name that I own. For example my internal DNS domain is lab.enterpriseadmins.org. I already own the domain enterpriseadmins.org and have control over who would get to use the subdomain LAB. If I wanted to create an external DNS host name of something.lab.enterpriseadmins.org, I could do that no problem and could even get an SSL certificate issued for that name if needed. I wouldn’t be able to do this with a domain that I don’t own.
If you don’t need/want to own a domain name, another good option is to use a reserved name. For example, RFC 2606 reserves the names example.com, example.net, and example.org for documentation purposes. You could use them in your internal network without prior coordination with the Internet Assigned Numbers Authority (IANA). This works well as you can take screenshots and such for documentation where example names in screenshots work, for example:
Once we have selected the DNS names that we are going to use, we also need to figure out a way to get our clients to point at our DNS server for resolution. I don’t like pointing clients directly at my lab infrastructure for name resolution. Just like I mentioned in a previous post about Home Lab Networking, I don’t want a lab problem to prevent the TV from working. There are a couple of options in this space, I’ve included a few options below with links to more information.
When building a lab network, it is helpful to put in a little time upfront and consider your learning objectives versus the complexity you can add into the system. If we are looking to gain a bit of experience with products like vSphere or vRealize Operations, its possible we could deploy a handful of components into our existing home network, assign them static IP addresses and be done – no complexity added at all. However, if we plan to dive deep into NSX-T, build overlay networks and configure routing, and we want to BGP peer with our physical network, we are going to be adding a bit of complexity. I like to start somewhere in the middle, where there is some flexibility to get complicated if needed, but simple enough that I don’t spend all my time managing networking. I also like to logically separate the ‘home’ network from the ‘lab’ network. The last thing I want to do is make some DHCP or name resolution changes in my lab and the family can no longer watch TV.
I’ve seen a lot of folks build logically separated networks for their labs. I’ve seen others do stuff that I’d consider crazy. Sure, you could make your internal network 126.96.36.199/24 so that its very few characters to type, but don’t try using Cloudflare’s DNS service. Instead of re-using internet routable blocks of traffic, RFC 1918 dedicates three different ranges of IP Addresses for private/internal use that you can pick from. They are:
10.0.0.0/8 [10.0.0.0 through 10.255.255.255]
172.16.0.0/12 [172.16.0.0 through 172.31.255.255]
192.168.0.0/16 [192.168.0.0 through 192.168.255.255]
If you connect to a VPN for a large enterprise, it is very common for them to assign an IP from the 10.0.0.0/8 or 172.16.0.0/12 blocks. When this happens, the VPN provided route statements may prevent you from accessing those same IP ranges if they are in use in your home network. Because of this, I’ve historically leaned towards the 192.168.0.0/16 range for home lab purposes. This still gives you the ability to segment/subnet into smaller networks. For example, I have a VLAN 10 that maps to 192.168.10.0/24 and is only used for temporary lab VMs. I have another VLAN 32 that maps to 192.168.32.0/24 and is used for a handful of separate lab gear to represent a disaster recovery site. All in I have about a dozen networks with 24-bit masks for various purposes, some routed and others not. Some of these have very valid reasons, like logically separating storage traffic from guest traffic. In other cases there is a bit of unnecessary separation for the production management workload VMs for things like vROps and Log Insight and virtual desktops. At the scale of my lab this separation is not really required, I maintain the extra complexity for the sake of having extra complexity like you’d find in a real production environment.
Once we have selected the IP address range(s) we will be using its time to start considering name resolution. I have some thoughts on that as well, so be on the look out for a future post where we will dive into that.
I’ve recently had several discussions with a friend about building a home lab. We covered various aspects including defining requirements, creating networks, and figuring out DNS domain names to use. In the next few blog posts, we will document lessons learned.
To get started we had to articulate our goal — to learn VMware SDDC products, gain hands on experience, and prepare for certification exams. The second consideration was how the lab was going to be used. For example, did we want an environment that could be quickly recreated for a specific purpose or did we need an environment on the other end of the spectrum with a long life / persistence? This longer life environment would likely require that we perform upgrades, troubleshoot when things broke, and have sample data for systems like vRealize Operations or Log Insight. For the first use case of an ephemeral, non-persistent environment, a solution like the VMware Hands On Labs would be perfect. It would have no cost, be easy to instantiate, and then could be torn down and recreated with just a few clicks. For a more persistent environment, we would likely need to acquire our own hardware, which would add costs and force us to understand system requirements of all of the solutions we would like to deploy in advance and go through a capacity planning exercise. Through our discussions a decision was reached that a more persistent environment would be necessary.
The next step was to document hardware requirements. I would recommend starting by creating a list of all of the workloads that you would like to run in the lab. Interesting data points you’d want to capture for each workload would be the number of virtual CPU required, the amount of RAM needed and total disk capacity. In my home lab experience the 1st place you’ll run low is on RAM, so I would take the total you think you are going to need, double that number, and start there. With rough hardware requirements in hand, the next step would be to find a solution that meets budget constraints. There are a lot of options in this space, from large, loud, & power-hungry refurbished server grade hardware on one end down to small, quiet, & power saving micro devices like the Intel NUC. There are plenty of sites to review some of the hardware other folks are using, and its worth checking out the collection of HomeLab BOMs at https://github.com/lamw/homelab.
With hardware ordered and on the way the next step will be to talk about networking. Please look for the next post where we will discuss getting started with home lab networking.
I’ve recently made several improvements to my home office / desk setup. Several people have asked for details on the parts/pieces I used to complete this, so I wanted to take a moment and document them here.
I started with an Autonomous SmartDesk 2 – Home Office motorized sit/stand desk. There is a premium version of this desk that appears to have more range (can go lower/higher) than the home version, but for my needs the home office version seemed to have very similar specs and was slightly less expensive.
I already had a very good desk chair (the Autonomous ErgoChair 2), but also added a Topo Comfort Mat for when I’m standing. This was a touch more than I planned to spend, but came highly recommended and initial impressions are very good.
I’m using two different monitor arms, one from my previous setup and a new ErGear Adjustable Gas Spring mount which was very inexpensive (only $25) and supported the weight required by my monitor (the specs for the monitor arm show it supports up to 26.5 pounds).
Lighting was the toughest problem to solve. I wanted to have a primary light source that was centered in front of me, to reduce shade cast from one side of my face for video calls, but also desired more light than most round / camera lights provide. I also preferred an indirect light source that would bounce of the ceiling first, but not be blocked by my monitor when in a standing position. My first thought was a very tall floor lamp, but I didn’t really want a base that I would be kicking right in front of my feet, and couldn’t find anything tall enough anyway. I found some desk mounted lamps that looked like they might work, but I couldn’t find any with the right height to be able to reach over my monitor. What I settled on was a fairly custom solution. I purchased a Twinkle Star Floor lamp with Remote Control, but disassembled / rewired part of it and mounted it to an unused monitor arm I had laying around using some bolts and rubber wire clamps. The end result is a desk mounted lamp that’s the perfect height (and adjustable), but also has a remote control that can adjust light temperature and brightness.
On a recent TAM Lab session (TAM Lab 082) I covered several methods for managing vSphere templates. At the end of the presentation we had a brief bonus method that showed using PowerCLI to clone a template to a different vCenter. This could be used once you update your primary copy of a template in vCenter1 and you wanted to make that template available in a different environment. The script used in the demo is available below.
This script uses splatting to improve readability. You can read more about_Splatting here. There are a couple basic components. First we connect to both vCenters, in this case using the same credentials. We then create a new VM from template on the source side, then move that VM to the destination side, and finally rename the destination VM and convert it to a template. We did this as multiple steps as Move-VM has additional parameters to assist with changing the destination network adapter to specify the correct portgroups and such.