Category : VRealize Automation

Written by Christopher Lewis on April 15, 2020 .

Introduction

In this series of posts, we will be taking a look at how to configure a Multi-Organization Tenancy (aka Multi-Tenancy) in vRealize Automation (vRA) 8.1.

In this post, we will be looking at how to meet the SSL Certitifcate requirements for configuring vRA 8.1 Multi-Organisation Tenancy. I will cover how many SSL certificates are required, then I will cover which SSL Certificates are required, then I will cover how those can be created easily using vRealize Suite Lifecycle Manager 8.1 and, finally, I will cover how to create certificates manually and import them into vRSLCM 8.1.

vRealize Automation vRA Multi-Tenancy

Written by Christopher Lewis on April 14, 2020 .

Introduction

In this series of posts, we will be taking a look at how to configure a Multi-Organization Tenancy (aka Multi-Tenancy) in vRealize Automation (vRA) 8.x.

In this post, we will be looking at the additional DNS requirements for configuring vRA 8.x Multi-Organisation Tenancy. We will cover which DNS Records are required and then cover how those can be created easily using PowerShell.

For more information on the rest of the posts in this series, click here .

vRealize Automation vRA Multi-Tenancy

Written by Christopher Lewis on April 8, 2020 .

I tend to rebuild my vRealize Automation (vRA) labs ALOT. I am currently lucky and have two environments, my vRA 8 homelab and my vRA Cloud org. I wanted a way to provide a consistent configuration to both environments. I had two options open in front of me:

  1. Use native REST API
  2. Use the Terraform Provider for vRA 8/Cloud

As vRA 8 / Cloud is an API first platform, I could have definitely used the native API to complete the configuration I am looking to do. However, as I have been waiting for an opportunity to get some hands on time with Terraform I decided this was a good reasons to look at the VMware Terraform Provider for vRealize Automation 8 !!

vRealize Automation 8 vRealize Automation Cloud Terraform

Written by Christopher Lewis on December 12, 2019 .

Purpose

One of the recurring themes I hear when talking to people in the community but also when talking to customers there is a perception that vRealize Automation 8.0 does not have an Anything as a Service (XaaS) capability. This is not true and hopefully the following article will paint a clearer picture of what vRealize Automation 8.0 can actually do in this space.

Background

What is vRealize Automation 8.0?

VMware released its new Multi-Cloud Automation platform, vRealize Automation (vRA) 8.0, just before VMworld 2019 Europe in November 2019.

vRealize Automation 8 vRealize Automation Cloud

Written by Christopher Lewis on December 4, 2019 .

Introduction

In this post we’ll be looking at how we can deploy vRealize Automation 8.0 using the new Easy Installer that ships with the product. I’ll be concentrating on the UI version of the installation as that is what most people who are new to the product will use.

The process below mirrors that of the vRealize Automation 8 Installation Guide on the VMware Documentation site. Before using this guide, be sure to check there for the latest information on the installation process.

HOWTO vRealize Automation 8

Written by Christopher Lewis on April 7, 2019 .

This is the sixth post in a series of posts covering the replacement of vRealize Automation SSL Certificates. In this post, we will tackle the replacement of the vRealize Automation Appliance VAMI Site Certificate.

This post is based on the VMware procedure and this is documented here .

Prerequisites

The following are expected prerequisites for this walkthrough:

  • A fully deployed and working vRealize Automation solution.
  • A set of certificate files:
  • The RSA Private Key used to encrypt the vRA Appliance certificate.
  • The Root CA Certificate file.
  • The vRA Appliance Certificate file.
  • The new Server.PEM file.
  • The Root CA Certificate and any Subordinate/Intermediate CA Certificates are installed within the appropriate Certificate store on the local machine (normally the Trusted Root Certification Authorities and the Intermediate Certification Authority respectively).

The Problem

The issue we see is that when you browse to https://vra.fqdn:5480, the site is untrusted.

Certificates

Written by Christopher Lewis on December 12, 2017 .

This is the fourth in a series of posts covering the replacement of vRealize Automation SSL Certificates. In this post, we will tackle steps required to update the embedded vRealize Orchestrator certificate following the replacement of the vRealize Automation Appliance certificate.

This post is based on the VMware procedure and this is documented within the VMware Documentation Site here .

According to the VMware, the reason for completing this additional step is that if you replace or update vRealize Automation certificates without completing this procedure, the vRealize Orchestrator Control Center may become inaccessible, and errors may appear in the vco-server and vco-configurator log files.

Certificates VMware vRealize Automation vRealize Orchestrator

Written by Christopher Lewis on December 11, 2017 .

This is the third in a series of posts covering the replacement of vRealize Automation SSL Certificates. In this post, we will tackle replacing the vRealize Automation IaaS Manager Service Certificate.

This post is based on the VMware procedure and this is documented here .

Prerequisites

The following are expected prerequisites for this walkthrough:

  • A fully deployed and working vRealize Automation solution.
  • A set of certificate files:
    • The RSA Private Key used to encrypt the vRA IaaS Manager certificate.
    • The Root CA Certificate file.
    • The vRA IaaS Manager Certificate file.
  • The Root CA Certificate and any Subordinate/Intermediate CA Certificates are installed within the appropriate Certificate store on the local machine (normally the Trusted Root Certification Authorities and the Intermediate Certification Authority respectively).

Identifying the “Issue”

If you log into any vRA IaaS DEM or Agent server and navigate to https://vra7-man.fqdn/VMPS you will see the screen below:

Certificates VMware vRealize Automation vRealize Orchestrator

Written by Christopher Lewis on December 11, 2017 .

This is the second post in a series of posts covering the replacement of vRealize Automation SSL Certificates. In this post, we will tackle replacing the vRealize Automation IaaS Web Server Certificate.

This post is based on the VMware procedure and this is documented here .

Prerequisites

The following are expected prerequisites for this walkthrough:

  • A fully deployed and working vRealize Automation solution.
  • A set of certificate files:
    • The RSA Private Key used to encrypt the vRA IaaS Web certificate.
    • The Root CA Certificate file.
    • The vRA IaaS Web Certificate file.
  • The Root CA Certificate and any Subordinate/Intermediate CA Certificates are installed within the appropriate Certificate store on the local machine (normally the Trusted Root Certification Authorities and the Intermediate Certification Authority respectively).

Replacing the Infrastructure as a Service Web Certificate

Navigate to the vRealize Automation Appliances Virtual Appliance Management Infrastructure (VAMI) interface, https://vra.fqdn:5480.

Certificates VMware vRealize Automation vRealize Orchestrator

Written by Christopher Lewis on December 11, 2017 .

In this series of posts we will walk through the process of upgrading all of the vRealize Automation Certificates. We’ll be moving from self-signed certificates that were deployed during the installation, to certificates that have been provided by an Enterprise Certificate Authority (CA). It is worth noting that the same process can be used to replace expiring SSL certificates as well.

Amongst other reasons, the purpose of doing this is to update the certificates so that communications between components is secured via a CA and for the following sites within the vRealize Automation deployment to be secured and trusted:

Certificates VMware vRealize Automation vRealize Orchestrator