About a month ago I accidentally deleted a SQL database as part of a migration to a new failover cluster. The database in question was the IaaS database used by my vRealize Automation installation, and no backup was available. Mistakes like that in a lab happen from time to time and are okay, as long as you can be the one to fix them. Continue reading
In part 10 we configured the vRealize Automation default tenant for our lab. We decided against using multiple tenants as the lab is only hosting one organization, and business groups utilizing it will be defined using other means.
In this part, we configure the blueprints which will make up our service catalog. Continue reading
This is due to an error I’ve encountered whilst trying to add a licence for the IaaS components. Once I have resolved this (or pulled out all my hair and called VMware!) I will continue on with the series.
Thanks for checking back.
In part 8 we installed and configured the vRealize Automation Appliance into the lab.
In this part we deploy and configure the IaaS platform. This will involve building a Windows Server VM and installing the requisite components. Once done, we will secure the platform with an SSL certificate from our Certificate Authority. Continue reading
In part 7 we configured SSL certificates for our newly deployed vCenter Server Appliance. In this part, we deploy the vRealize Automation Appliance into the lab.
After deployment we will perform a number of tasks to enable the appliance to work in the lab environment.
In part 6 we installed and configured a vCenter Server Appliance in the lab. This will manage the various components, plus serve as an endpoint for vRealize Automation.
In this post we replace the default SSL certificates from the vCSA with trusted certificates from our in-house certificate authority. Continue reading
In part 5 of this series we created a Windows 2012 R2 Domain Controller to provide our authentication services for the environment.
In this part, we deploy the VMware vCenter Server Appliance (vCSA) 5.5. This will serve as the backbone to our infrastructure, as well as the endpoint for the majority of our VMware vRealize Automation deployments. Later in the series, we will configure other endpoints such as VMware’s vCloud Air or AWS. Continue reading
In part 4 of this series we configured two ESXi hosts to host our lab. In this part we will setup a Windows Server 2012 R2 Core virtual machine and configure it as a domain controller in a separate root domain. We will then configure a forest trust to our production domain so that our users can authenticate. Continue reading
In part 3 of this series on building a lab using VMware vRealize Automation we configured the physical networking to support our lab. In this part we install and configure VMware vSphere 5.5 on our servers.
Before we can install vSphere, we have to analyse our requirements and source hardware to satisfy them. Obviously we would like hardware that comes with as much compute, storage and network capacity as possible, but budgetary constraints must be taken into consideration. Continue reading