I was doing some testing with adding an external vRealize Orchestrator 8.4 endpoint to vRealize Automation Code Stream 8.4, and it turns out there’s a redirect that happens with the vRO 8.4 appliance that makes the endpoint validation fail. When you enter the URL and click ACCEPT CERTIFICATE the UI will throw an error:

Server error on getting certificates. Http failure response for https://<vRA FQDN>/codestream/api/endpoint-certificate?url=https://<vRO FQDN>: 400 Bad Request

Integrating vROps with vRA 8 using Workspace One Auth Source

Product Version - vRealize Automation 8.x

Why integrate vROps with vRA 8?

vRealize Automation can work with vRealize Operations Manager to perform advanced workload placement, provide deployment health and virtual machine metrics, and display pricing.

So what is the problem?

When configuring the integration, you will input the vROps URL and it will also ask you to input a username and password of the service account you wish to use. This is no problem if the accouint is a locally created account in vROps itself but most enterprises will want to use AD created service accounts which are then imported into vROps via WorkSpace One (vIDM)

Why use Content Libraries with vRA 8

Product Version - vRealize Automation 8.x

What are vSphere Content Libraries?

A content library stores and manages content in the form of library items. A single library item can consist of one file or multiple files. For example, the OVF template is a set of files (.ovf, .vmdk, and .mf). When you upload an OVF template to the library, you upload the entire set of files, but the result is a single library item of the OVF Template type.

Autumn seems to be a time for the winds of change to blow through our industry, and this year that’s true for me.

TL;DR - I’m leaving VMware PSO to join the Cloud Management Business Unit as a Technical Marketing Manager for Cloud Automation!

It’s been a little over two years since I joined VMware as a Senior Conusltant in the EMEA NSX Practice, and in that time I’ve enjoyed some great opportunities, worked with some great people and technologies. And I’ve learned a lot since taking on my first NSX-T design just days after joining. But, as I mentioned when I joined a couple of years ago , I’ve always said NSX comes alive when it’s automated by vRA. In fact, almost every engagement I’ve done over the past two years has had a strong vein of automation running through it.

I have been working with VMware Cloud Foundation recently and while for the most part things went well there were occasions where challenges were encountered which made the delivery to the customer all the more trickier than expected.

This article is a list of observations and things to most definitely check or watch out for when delivering a VCF project.

We were working with VCF version 3.7.2 (yes I am aware 3.8 has arrived but that was too late for the delivery in this project)

I recently upgraded an instance of vRA from 7.2 to 7.5 and rather than do it the manual way I used VMware’s vRealize LifeCycle Manager (version 2.0 update 3).

Everything was going great and according to plan, the vRLCM pre-requisites checker made short work of all of the checks you need to do before you start an upgrade of vRA. You can see below vRLCM does a great job of keeping you informed of the current progress and in a really elegant way.

When vRealize Lifecycle Manager 1.2 was released recently, I was keen to get it installed in my lab, since I maintain several vRealize Automation deployments for development and testing, as well as performing upgrades. With vRLCM I can reduce the administrative overhead of managing the environments, as well as easily migrate content between environments (I’ll be blogging on some of these cool new features soon).

However, I hit a snag when I began to import my existing environment - I couldn’t get the vCenter data collection to run.

Just a quick post today, as I was working with a customer recently and we were trying to retrieve the Custom Properties assigned to a vRealize Automation 7.3 deployed Virtual Machine, similar to the one in the image below. It’s not as intuitive as you’d like it to be because of the split between IaaS APIs and Cafe APIs. Below you can see I’ve deployed a simple CentOS blueprint with a custom property at the Blueprint level (called “BlueprintLevel” with a value of “CustomProperty”) and a custom property at the VM level (called “CustomProperty” and a value of “Test123”).

vRealize Automation and NSX integration has introduced the ability to deploy multi-tiered applications with network services included. The current integration also enables a method to deploy micro-segmentation out of the box, based on dynamic Security Group membership and the Service Composer. This method does have some limitations, and can be inflexible for the on-going management of deployed applications. It requires in-depth knowledge and understanding of NSX and the Distributed Firewall, as well as access to the Networking and Security manager that is hosted by vCenter Server.

In this episode, Sunny gave us a deep dive into the WLP and WLB features of vROps.

We were also joined by a special guest,  Jad El-Zein who gave us a great insight into how vRA utilises vROps for initial placement of freshly provisioned VMs

We would highly appreciate it if you could spend 30 seconds to fill up this quick and simple survey to provide us your feedback. You can also request topics of your choice through this survey.