When running certain REST Tasks in Code Stream, the pipeline execution fails on this task with:
Unexpected character ('\\' (code 92)): was expecting double-quote to start field name \n at [Source: (io.netty.buffer.ByteBufInputStream); line: X, colume: X]"
Continue reading vRealize Automation 8.5 – Code Stream – Unexpected character (‘\\’ (code 92))
This walk through will detail the technical configurations for using vRA Code Stream to deploy vSphere with Tanzu supervisor namespaces and guest clusters.
For a recent customer proof-of-concept, we wanted to show the full automation capabilities and combine this with the consumption of vSphere with Tanzu.
The end goal was to use Cloud Assembly and Code Stream to cover several automation tasks, and then offer them as self-service capability via a catalog item for an end-user to consume.
To achieve our requirements, we’ll be configuring the following:
In my Lab environment I have the following deployed:
For the various bits of code, I have placed them in my GitHub repository here.
This configuration is detailed in this blog post, I’ll just cover the high-level configuration below.
Continue reading Walk through – Using vRA to deploy vSphere with Tanzu Namespaces & Guest Clusters
Myself and Katherine Skilling (LinkedIn, Twitter) recorded a session for TAM Lab and VMUG Events.
In the below session, we cover how to use vRealize Automation Cloud (or vRA 8.x for on-prem) to operate your Multi-Cloud environment.
So what does this actually mean?
We cover how to use vRealize Automation to deploy and consume your public cloud provider of choice. This is a demo heavy recording and we cover the following;
Regards
In this blog post I am going to dissect backing up vRealize Automation 8.x using Veeam Backup and Replication.
- Understanding the backup methods - Performing an online backup - Performing an offline backup
Understanding the Backup Methods
Reading the VMware documentation around this subject can be somewhat confusing at times. And if you pay attention, there are subtle changes between the documents as well. Lets break this down.
Performing an Online Backup
Let’s start with the easier of the two options. Again, this will be supported for vRealize Automation 8.0.1 and higher. Continue reading How to backup vRealize Automation 8.x using Veeam
Ok, so I’m just going to call it out straight away, when using wildcard SSL certificates with vRealize Automation 8.0, read the release notes.
I did not, and caused myself quite a few headaches with the deployment, which you can read about further in this post.
Cannot set wildcard certs for certain domain names, specifically those not using a Public Suffix. vRealize Automation 8.0 supports setting a wildcard certificate only for DNS names that match the content of the Public Suffix List ([https://publicsuffix.org/]) For example, a valid wildcard certificate: you can use a wildcard certificate with DNS name like "*.myorg.com". This is supported because "com" is part of the Public Suffix List. An invalid wildcard certificate example: you cannot use a wildcard certificate with DNS name like "*.myorg.local".This is not supported because "local" is not part of Public Suffix List. Workaround: Only use domain names in the Public Suffix List.
The issues caused by using an unsupported wildcard SSL
When deploying vRA 8.0 via vRSLCM, either as part of the easy installer or as part of an existing vRSLCM setup, you will asked to provide an SSL certificate.
This does not validate your certificate is supported for use with the vRA 8.0 deployment. vRSLCM will do some checking on the SSL selected, but is only to ensure the SSL certificate is not about to expire, you will see a Green tick and “healthy” status as below.
Once you hit deploy, you will find your vRA appliance finally stood up, however the initialization tasks will stall.
Error Code: LCMVRAVACONFIG590003 Cluster Initialization failed on VRA. vRA Initialize Cluster failed on vRA VA - ***Hostname***. Please login to the vRA and check /var/log/deploy.log file for more information on failure.