Tag - vRealize Suite

While exploring vRealize Automation and SaltStack Config, I had the bright idea to expand the integrations across the vRealize Suite by automatically installing the vROPs Telegraf agent during a vRA Deployment. This would provide immediate guest OS monitoring and (optional) application monitoring to every machine deployed from vRA. What you’ll need: vRealize Automation 8.8 vRealize SaltStack Config 8.8 Integrated with vRealize Automation through either vRealize Suite Lifecycle Manager or as a standalone SaltStack instance.

I was trying to install the vRealize Operations Telegraf agent on my VMs by following the documentation. I wrote the steps out in a Salt state file: unzip: pkg.installed install-telegraf: cmd.script: - source: https://cloudproxy.domain.tld/downloads/salt/download.sh - name: /tmp/download.sh -o install -v vrops.domain.tld -u admin -p p@ssw0rd - mode: '0777' Salt takes the source and puts it in the location under name, executing it with the included arguments. However, everytime it ran I would get this:

During some recent lab work, I deployed a fresh vRealize SaltStack Config 8.8 appliance in my lab and had it integrated with vRA and vIDM. On first login I found that my vIDM/vRA administrator (config admin) was unable to see the minions in SaltStack Config UI. After some trial and error and working with some others internally, I found the issue was related to the default permissions provided by the vRA IAM integration.

Quick post today! While deploying a vRealize Log Insight (vRLI) cluster with a VIP using vRealize Suite Lifecycle Manager 8.1, you receive this error: Error Code: LCMVRLICONFIG40091 Error occured while configuring vRLI Integrated Load balancer. {"errorMessage":"Specified IP address is not available. It is already held by another host in the network","errorCode":"LOAD_BALANCER_ERROR","errorDetails":{"errorCode":"com.vmware.loginsight.api.errors.loadbalancer.ip_address_unavailable"}} This is clearly due to an issue with the VIP that has been configured. Check both forward and reverse DNS records of course.

Following along the theme of one of my previous posts on vRealize Suite Lifecycle Manager (vRSLCM) and its REST API, here’s another on replacing the password for a vCenter Server in a vRSLCM “Datacenter”. Similar to my previous post, we’ll be doing this in the Swagger UI as the ability to replace the password is not available in the standard vRSLCM UI (v8.1). The APIs used in this post are private and, as such, not supported by VMware.

I don’t like doing things manually. My previous post showing how to replace vRealize Suite Lifecycle Manager certificates using the GUI is straight forward, but it’s far too manual. I’m going to show you how to replace the certificate using the vRSLCM 8.1 API(which you can wrap in a script). You can use any tool to interface with the API. I stick to Postman, curl, or if the application provides it, a Swagger UI.

Overview Back in my operational days, my team and I needed ‘pretty’ reports on all VMs in the environment. In almost every case, we needed to include metrics on Guest OS volumes. Back in vRealize Operations 5.x, 6.x and 7.x, I could never find a way report on all instances of a guest volume on many VMs. It always looked like this: Example of a not-so-pretty filesystem report out of vRealize Operations (8.

This post covers the process of replacing a self-signed SSL certificate running on a vRealize Suite Lifecycle Manager (vRSLCM) 8.1 appliance. I’ll be using the UI to show you how to do it. Pre-requisites Make sure you have a defined a certificate template as per https://kb.vmware.com/s/article/2112009 Confirm your user account has the correct privileges to request certificates using Microsoft CA Web Server enrollment. At the least, find someone that can submit and approve it for you.

I’ve been spending some time in my vRealize Automation (vRA) 8.1 lab, specifically the Custom Resource capabilities backed by the embedded vRealize Orchestrator instance. I was following the AD User Custom Resource example from the Docs and kept receiving the following error in vRA: Failed to get request status: 500 Internal Server Error from POST http://tango-vro-gateway.prelude.svc.cluster.local:8080/vro/blueprint/blueprint-provider-request?operation=status 500 Internal Server Error when requesting the Custom Resource I was getting this message in vRA whenever I would try to deploy the Blueprint that contained the newly created Custom Resource.

I had a customer recently ask me what vRealize Automation (vRA) 8.1 was able to manage in the public cloud when using blueprints. While I had a very good idea as I’ve got it running in my homelab, I didn’t have any online reference list that I could direct them to. There just isn’t a simple list of it all for a customer to peruse before they have deployed it.