Terraforming my vSphere lab – part 1

As promised on my post here, it’s time to show how dive into vSphere scenarios generating the “infrastructure as code”. In fact, the modern cloud infrastructures are more and more delivering the final customer using many automation tools like Terraform. In this way, it is possible to consume cloud resources regardless of the underline cloud IaaS, and at the same time, keeping track of changes. In this post, I’ll show how I set up and coded vCenter and nested ESXi hosts.

In order to successfully deliver the environment, elements are important to prepare and upload all needed templates like:

  • ESXi nested VM
  • vCenter
  • Windows and Linux template.

Windows and Linux template are the easiest part of the deployment: create a new VM, install the OS and VMware tools. The ESXi template generation is a little bit complicated, but luckily, William Lam has shared his ESXi template image here: https://www.virtuallyghetto.com/2017/05/updated-nested-esxi-6-0u3-6-5d-virtual-appliances.html.

ESXi Environment Setup

I don’t wanna spend too much time about Terraform download and installation… just check the official website here or simply on MAC open a console and type:

Before continuing, it’s necessary to check some underline virtual environment he underlines virtual infrastructure:

  • All vSwitch used as physical switches for nested ESXi must be configured in promiscuous mode and “forged transmit” enabled

On my infrastructure I’ve got the following scenario:

  • Firewall/Router with DHCP based on pfSense
  • Domain: linoproject.lab and DC
  • Management LAN IPs from 20-23 are already assigned… so we can use IPs from 30 to 39 (3 are enough)
  • PC with Terraform, powerCLI and VCSA Image can reach vSwitch physical infrastructure by the firewall/Router (adding another NIC connected to local LAN)

The following example deploys ESXi hosts with two NIC cards: one is connected to the laboratory network and the other is available for NAS/SAN.

Note: the following automation doesn’t include DNS configuration and post installation configuration process. It’s possible to realize a fully configurable process simply using PowerSHELL/CLI to complete the configurations connecting with the hosts and vCenter after the complete nested VM deploy.

Now it’s possible to deploy the previously downloaded ESXi virtual appliance via vCenter and convert it in Template… but wait!

According to Troy Lindsay’s blog, before reconverting the VM in the ESXi template,  it’s necessary to download and execute (after Connect-VIServer) this PowerCLI script to enable debug properties in the VM or vAPP Template. This script contains a fix documented here that overcomes a Terraform issue during the “apply” process.

Now it’s time to write the terraform file using the editor you like. Create a directory and write the main.tf file as following

This is the common part that describes where to deploy the VMs which must be referenced as a template:

Then describe every VM using the following statements:

For the second and the third ESXi just repeat the statements above, changing resources name, properties, etc…

Finally, it’s time to deploy :

After a couple of minutes (depending on the physical and nearby virtual environment) you should have your nested hosts up and running.

The source for this post is: https://www.troylindsay.io/2018/04/10/using-terraform-to-deploy-nested-esxi-hosts/

Thanks to Troy Lindsay for sharing his experience.

VCSA is still WIP, but in the meantime, you can check the alternative deployment based on PowerCLI from Lam’s blog: https://www.virtuallyghetto.com/2016/11/vghetto-automated-vsphere-lab-deployment-for-vsphere-6-0u2-vsphere-6-5.html, and this Github deployment script repo: https://www.virtuallyghetto.com/2016/11/vghetto-automated-vsphere-lab-deployment-for-vsphere-6-0u2-vsphere-6-5.html

For further information about Terraform with vSphere Provider just check the official documentation here: https://www.terraform.io/docs/providers/vsphere/index.html

   Send article as PDF