*Disclaimer: I am an EMC employee, this post was not sponsored or in any way required by my employer, it is my experience getting to know this particular product.**
In my last ViPR SRM post, I introduced you to some of the features if you were not already aware of them. In this post, I will look at installing ViPR SRM 6.5.2. I downloaded ViPR SRM from support.emc.com; while I am an EMC employee, I logged into the support site with my personal email account to download the files. Once logged in, search for ViPR SRM and click on the downloads menu, as I mentioned I will be going with the vApp option versus a binary installation.
Once downloaded, extract the content of the zip file – you’ll have 2 OVF’s. One is the 4 VM vApp I mentioned in my last post, the other, a 1VM vApp useful for lab and evaluation purposes. Given I have limited resources in my home lab, I will be deploying the 1 VM vApp.
Important note here, you will need to deploy the OVF to vCenter, not a stand-alone ESXi host as some of the OVF properties will not be exposed properly, causing the deployment to fail.
Follow the OVF deployment wizard, when prompted select the All-In-One configuration:
By default, the VM deploys with 4 vCPU – adjust according to your lab, I have set mine to 2, 16GB RAM and removed the reservation (performance here would not be ideal obviously, but this is for lab purposes only). Once the OVF has been deployed, you should be able to log into http://:58080/APG. Login as admin/change me to access ViPR SRM.
By default, you are in the “User” interface, if you click on “Administration” in the upper right corner, you will go to the administration screen. Go ahead and click on Administration >> Centralized Management (on the left nav menu) >> License Management (also on the left nav menu). As you can see you have a 30 day trial license to test out ViPR SRM.
Close the license window/tab. Notice where the “Administration” menu was, you now see a “User Interface” menu, this will (like the administration link did) take you to the User interface (where you initially landed when you logged in.
In the next post, I will look at connecting ViPR SRM to vCenter and, in my case, XtremIO.
With the decision made to use vSphere SSO for vCloud Automation Center / vRealize Automation, it’s time to deploy the vRealize Appliance. The appliance comes as, well an appliance as the name suggests and is a straight forward OVF deployment. One thing to keep in mind, at least as of 6.0 it was very difficult to change the network settings that were supplied through the OVF properties during the deployment. If you fat finger something here just punt and redeploy – something I’m likely to hold on to for a while.
Also, we don’t really want to skimp on vCloud Automation Center / vRealize Automation resources, to that end I have increased the amount of memory in both of my ESXi hosts to 8GB instead of 4 to ensure the appliance can access the resource it needs.
Since we are going to start using the Web Client to build virtual machines and deploy OVFs, now would be the time to create an entry in your host file so you can access the web client via FQDN, otherwise you will not be able to deploy OVFs for example, like we are about to do! You should also add a host file entry for your vCloud Automation Center / vRealize Automation appliance. In addition, I also had to do this from the domain controller behind the NAT, doing it from my home computer running workstation kept having errors.
You can now log in and start to configure the vCloud Automation Center / vRealize Automation appliance – which as you may have guessed will be my next blog post!
Posted in Tech Tagged with: appliance, automation, automation center, Cloud, ESXI, Home, home lab, lab, ovf, ovf deployment, ovf properties, Shared, Technology, Training, vcac appliance, vcenter, vcloud, vcloud automation center, vCloud Automation Center (vCAC), vcsa, Vendors, Virtualization, VMware, vra appliance, vRA Home Lab, vrealize automation, vRealize Automation (vRA), vSphere, web client
All right – ESXi hosts built, datastores created (on at least 1 ESXi hosts) so lets import the vCenter Virtual Appliance. The VCSA should be a bit lighter weight for our home lab that vCenter on Windows + SQL. Before getting started, make sure you have download the VCSA from VMware and placed it in a location accessible to the vSphere Client.
If you are not interested in deploying via PowerCLI, go ahead and click finish, the OVF will be imported. The rest of the setup for the VCSA is something I have written about in the past, Installing the vCenter Server Appliance 5.5 which is also one of the more popular pages people find my site on from Google. Have a read over those steps and we will pickup the rest of the setup in part 11. For those interested, stay tuned for how to import the OVF via PowerCLI next.
Posted in Tech Tagged with: ESXI, HOL, Home, home lab, import ovf, lab, Lab Series, nested esxi, ovf, Shared, Technology, Training, vcenter, vcenter server appliance, vcsa, Vendors, Virtualization, VMware, vSphere, vsphere client