The recommendations for the vRealize Appliance have changed with 6.2, the published reference architecture now does not recommend using an external Postgres database (either vPostgres appliance, a 3rd party Postgres deployment or using a third vRealize Appliance as a stand-alone database installation). Instead the recommended layout is shown in the diagram below. One instance of postgres on the primary node becomes an active instance, replicating to the second node which is passive.
Having just welcomed VMTurbo on board as a blog sponsor, I thought I’d do a quick posting on how to deploy their free Virtual Health Monitor appliance.
Sign up for a free license here and download the appropriate version
Deploy the VMTurbo Appliance Deploying the appliance is simply a case of importing the OVA downloaded. There’s nothing really to configure and it took 61 seconds in my lab environment, so it’s pretty quick!
I tested vSphere 6 quite intensively when it was in beta, but I didn’t ever upgrade my lab - basically because I need a stable environment to work on and I wasn’t sure that I could maintain that with the beta.
Now 6 has been GA a while and I have a little bit of time, I have begun the lab upgrade process. You can see a bit more about my lab hardware over on my lab page.
For several months now we have seen glimpses of vROps by way of limited blog posts and the HOL demo’s so it was great to see it finally released.
So what is it like out of the box?
vROps 6.0 Release notes
The first clear change is the move away from 2 VMs in a vAPP and consolidation down to 1 VM which is then easily scalable to more as you require.
This is the fourth article in a series about how to build-out a simple vCAC 6 installation to a distributed model.
By the end of this post we will have deployed a second vCAC Appliance, clustered it with the first appliance and registered the load balanced URL with the Identity Appliance. This will mean logging on to https://vcloud.definit.local/shell-ui-app will be successful.
vCAC deployment with clustered and load balanced vCAC Appliances An overview of the steps required are below:
This is the second part of the 3rd article in a series about how to build-out a simple vCAC 6 installation to a distributed model.
By the end of this part, we will not have modified the vCAC deployment in any way, we’ll just have 3 configured load balanced URLs
vCAC Simple Install with vPostgres deployed and load balancers prepared An overview of the steps required are below:
Issue and install certificates Deploy an external vPostgres appliance and migrate the vCAC database Configure load balancing Deploy a second vCAC appliance and configure clustering Install and configure additional IaaS server Deploy vCenter Orchestrator Appliance cluster I’ve previously configured 3 DNS records for the load balanced services (see part 3.
According to VMware, Infrastructure Navigator is
…a component of the VMware vCenter Operations Management Suite. It automatically discovers application services, visualizes relationships and maps dependencies of applications on virtualized compute, storage and network resources.
Effectively it takes a look at the network connections that are running between your VMs (and physical servers) and works out which applications and services are running on each, and the dependencies – both upstream and downstream – for each VM.
With the release of vCenter Log Insight Public Beta (http://communities.vmware.com/community/vmtn/vcenter/vcenter-log-insight) I thought I’d strike while the iron is hot and run through the installation and configuration.
Deploying the OVF This is such a bread and butter task that it doesn’t require more than a few words – it’s definitely worth looking at the Sizing PDF before you deploy (VMware-vCenter-Log-Insight-1.0-Beta-Virtual-Appliance-Sizing.pdf) as it’s not small even for a test installation. If you’re using less than the recommended 8GB RAM there are additional steps to change the heap size for performance.
So VMware’s Support Assistant is pretty awesome and it’s free! I thought I’d do a quick run through of the installation and set up for anyone who was interested, it’s fairly straightforward and if you raise a lot of calls or have multiple calls on the go it’s a time saver!
VMware’s official page for the Support Assistant is here - https://www.vmware.com/products/datacenter-virtualization/vcenter-support-assistant/overview.html
The OVF deploy is so simple I’ve just taken screenshots: