In order to use vSphere templates in vRealize Automation / vCloud Automation Center and Application Services / Application Director there is a bit of preparation you need to do, especially if you want to use Application Services. There are guest agents for both vRealize Automation and Application Services so lets get started. A quick assumption here, you already have a linux virtual machine installed with VMware Tools. I am going to cheat a bit here and use the e1000 NIC, if you want to use the VMXNET3 adapter see my post on how to install VMware Tools…which needs Perl…which needs network access…which needs Perl! Let’s get started with the specifics on configuring your Linux VM; I have a CentOS virtual machine called vxprt-centos-tmp that is powered on and ready to configure. Log in via the VMRC or SSH to get started:
Note that as of Application Services 6.1, you cannot use CentOS7 – at the very least the guest agent will not install, I have not tested beyond the agent installation so certain functionality may work. The support matrix has more details on supported operating systems.
The installer will download all of the necessary components and place them in the correct location; a nice step forward from vCloud Automation Center and Application Director 6.0. You should receive a message that the Installation Complete Successfully and Ready to capture as a template… however there is still one more step we actually need to do – remove the 70-persistent-net.rules file. This file keeps track of MAC addresses and it will change every time we clone the template. By removing it, it will recreate the file on first boot.
We should now be ready to add the vSphere template as a Blueprint in vRealize Automation Center
Posted in Tech Tagged with: app d, applicaiton director, Application Director (AppD), application services, Application Services (AppS), apps, automation, Cloud, create template, ESXI, Home, home lab, install vcac guest agent, lab, Lab Series, nested esxi, Shared, Technology, template, Training, vCloud Automation Center (vCAC), vcsa, Vendors, virtual machine, Virtualization, VM, VMware, vra, vRA Home Lab, vrealize, vrealize automation, vRealize Automation (vRA), vSphere, web client
I was going to do a post on NFS versus iSCSI, to be honest that is such old hat in my opinion it doesn’t really matter. Whether you use iSCSI or NFS is up to you, your application and business requirements along with any constraints in your infrastructure that may force you to lean one way or another. Since I am an NFS networking ninja, clearly I am going to go the NFS route. Let’s get started on setting up NFS, if you are not already log into your Synology DSM.
Next I need to connect to my NFS share from the ESXi hosts. Typically I’d have NFS on its on VLAN, but sans a switch in my home lab to VLANs it will be riding with all my other network traffic.
The datastore should now be available on both hosts (Click on the host >> related objects >> datastores) as seen below. Repeat for the gold datastore.
Now that the datastores are created, I am going to create an “ISO” folder on the silver datastore to hold my linux ISOs and build virtual machines in vCenter.
Posted in Tech Tagged with: datastore, ESXI, Home, home lab, lab, Lab Series, NAS, nested esxi, network, NFS, nfs datastore, Shared, Storage, Synology, synology nfs datastore vmware, Synology Setup Series, Technology, Training, vcenter, vcsa, Vendors, Virtualization, VMware, vpshere, vSphere, web client
That is a wrap on getting the basics of a home lab up and running in VMware Workstation. Within Workstation we have a working Windows 2012 Domain Controller, two virtual ESXi hosts both capable of running nested 64-bit virtual machines thanks to the RVI support in the processor of the 8-core home lab system build and vCenter running. In vCenter we have our datacenter and cluster created with both virtual ESXi hosts added. The cluster has DRS enabled, a virtual distributed switch setup with both hosts attached and port group and VMkernel interface setup and running and demoed using vMotion to move a virtual machine from one host to another. Not bad for 4 virtual machines barely consuming any memory on the host computer!
All that though, was leading up to this; setting up vRealize Automation and Application Services. In my next series I will go over some of the basics of getting vRealize Automation setup in your home lab so you can start to get a feel for the various roles, requirements and setup. Here is some handy reading in the interim (ignore anything that says vSphere SSO can’t be used)
Thank you for following along with the home lab series setup, I know there may be a few holes but again the goal was to get this setup to have an environment as the foundation to test other tools.
Posted in Tech Tagged with: ESXI, HOL, Home, home lab, lab, Lab Series, Microsoft, nested esxi, PowerCLI, Shared, Technology, Training, vcenter, vcsa, Vendors, Virtualization, VMware, vmware workstation, vRA Home Lab, vSphere, web client, Windows, wrap-up
vCenter is built, now we can start doing some of the cooler things VMware vSphere has to offer; up first – Dynamic Resource Scheduler. DRS can be run in either manual, partially automated or fully automated mode. Partially automated will make initial placements of new virtual machines and virtual machines during power on operations and suggest how to rebalance the cluster. Fully automated, well its fully automated. It will balance cluster resources based on how aggressive you want it to be. For a deeper dive into DRS, check out the Clustering Deep Dive book, basically the bible for all things HA and DRS.
To enable DRS, log into the vSphere web client and perform the following steps:
So enabling DRS – not to hard; understanding all of the settings and how it impacts your environment – well that is typically the harder part. As for our home lab setup, we are ready to setup vMotion – a requirement for DRS to be fully automated!
Posted in Tech Tagged with: automation, cluster, drs, dynamic resource scheduler, ESXI, HOL, Home, home lab, lab, Lab Series, nested esxi, Shared, Technology, Training, vcenter, vcsa, Vendors, Virtualization, VMware, vSphere, vsphere cluster, web client
So you’ve got vCenter up and running and hosts added, it’s time to enable the cool things vCenter can do – namely vMotion, HA and DRS. I’ve gone back and forth on how I wanted to present vMotion and networking in the home lab. On one hand many existing deployments are likely running 1Gbps, though newer ones are likely to start with 10Gbps as prices have dropped. After a quick Twitter chat I decided to move forward as I would if I had 10Gbps networking and not have separate physical interfaces in my host for different traffic types.
When we setup our ESXi templates there was only a single NIC, let’s add a 2nd NIC to the VM’s. For purposes of this labs (and maybe I’m still old like this) I will keep my management network on a standard switch and my VM network and vMotion traffic on a distributed switch.
Once the ESXi virtual machine has been restarted, you should see two interfaces in the vSphere Web Client. Repeat for your 2nd host.
In the vSphere Web Client, click on the network tab in the navigator so we can create the VDS.
Your hosts will be added to the VDS and vMotion will be enabled on the newly created VMkernel adapter. To test, I have created an empty virtual machine on vxprt-esxi02 in the silver datastore, I am going to vMotion and Storage vMotion that virtual machine to vxprt-esxi01. Here you can see the screenshot
You can see the progress of the vMotion in the Running Tasks window. After a few minutes you should now see your virtual machine on vxprt-esxi01
Posted in Tech Tagged with: create vds, distributed switch, ESXI, HOL, Home, home lab, Lab Series, migrate virtual machine, nested esxi, network, port group, Shared, Storage, Technology, Training, vcenter, vcsa, vDS, Vendors, virtual machine, Virtualization, VM, vmk, vmkernel, vmotion, vmotion vm, VMware, vSphere, web client