Build numbers and versions of VMware vRealize Automation

This table lists the vRealize Automation build numbers and versions:

Version	Release Date	Build Number	Installer Build Number
vRealize Automation 8.0.1 HF1	2020-01-24	15464201	N/A
vRealize Automation 8.0.1	2019-12-19	15294185	15336196
vRealize Automation 8.0	2019-10-17	14842736	14878991
vRealize Automation 7.6 HF2	2019-11-14	14907768.14305635	N/A
vRealize Automation 7.6	2019-04-11	13027280	N/A
vRealize Automation 7.5 HF9	N/A	15148823.14395050.14176748	N/A
vRealize Automation 7.5 HF8	N/A	14194237.14176716.14176748	N/A
vRealize Automation 7.5 HF7	N/A	13806180.13036621	N/A
vRealize Automation 7.5 HF6	N/A	12322714.13452153	N/A
vRealize Automation 7.5 HF5	N/A	12322714.12933355	N/A
vRealize Automation 7.5	2018-09-20	10053539	N/A
vRealize Automation 7.4 HF13	N/A	14454487.12266397	N/A
vRealize Automation 7.4 HF12	N/A	13731978.12266397	N/A
vRealize Automation 7.4 HF11	N/A	8182598.12266397	N/A
vRealize Automation 7.4	2018-04-12	8229492	N/A
vRealize Automation 7.3.1	2018-03-15	8004225	N/A
vRealize Automation 7.3	2017-05-16	5610496	N/A
vRealize Automation 7.2	2016-11-22	4660246	N/A
vRealize Automation 7.1	2016-08-23	4270058	N/A
vRealize Automation 7.0.1 - HotFix 1	2016-06-22	3864356	vRA 7.0.1-HotFix-1
vRealize Automation 7.0.1	2016-03-15	3622989	N/A
vRealize Automation 7.0	2015-12-17	3311738	N/A
vRealize Automation 6.2.5	2016-11-17	4619074	N/A
vRealize Automation 6.2.4	2016-03-15	3624994	N/A
vRealize Automation 6.2.3	2015-10-06	3093004	N/A
vRealize Automation 6.2.2.0	2015-06-09	2754336	N/A
vRealize Automation 6.2.1.0	2015-03-12	2553372	N/A
vRealize Automation 6.2.0.0	2014-12-09	2330392	N/A
vRealize Automation 6.1.1.0	2014-10-30	2216936	N/A
vRealize Automation 6.1.0.0	2014-09-09	2077124	N/A
vRealize Automation 6.0.1.2	2014-07-10	768531	1942139
vRealize Automation 6.0.1.1	2014-05-01	1768531	1748175
vRealize Automation 6.0.1	2014-02-13	1569764	N/A
vRealize Automation 6.0.0	2013-12-10	1445145	N/A
vRealize Automation 5.2.2	2014-06-12	5.2.5 Build 104	5.2.2
vRealize Automation 5.2 - HotFix-5	2014-01-13	5.2.3.470	vCAC-5-2-HotFix5
vRealize Automation 5.2 - HotFix-4	2013-11-26	5.2.3.450	vCAC-5-2-HotFix4
vRealize Automation 5.2 - HotFix-3	2013-09-05	5.2.3.422	vCAC-5-2-HotFix3
vRealize Automation 5.2 - HotFix-2	2013-07-26	5.2.3.409	vCAC-5-2-HotFix2
vRealize Automation 5.2 - HotFix-1	2013-06-14	5.2.3.383	vCAC-5-2-HotFix1
vRealize Automation 5.2 (GA)	2013-05-15	5.2.3.349	5.2 (GA)
vRealize Automation 5.1 - HotFix-2	2013-08-08	5.1.1.69	vCAC-5-1-HotFix2
vRealize Automation 5.1 - HotFix-1	2013-06-28	5.1.1.66	vCAC-5-1-HotFix1
vRealize Automation 5.1 (GA)	2012-11-28	5.1.1.56	5.1 (GA)

Custom Naming for VM in vRA 8.x using Action Based Extensibility

In this blogpost you will learn how to create custom names  using action script  options in vRA 8.X to create custom names for VMs.

 

vRealize Automation 8, you mostly noticed that when you create  the Virtual Machine it gets a standard machine name something  likes Cloud_vSphere_Machine_1-mcm799-143460688242 but it will not help to meet customer standard VM naming. Our most customers has their own standard name convention. After this blog you will be able to create Custom Naming for VM to meet customer standard name convention.

 

Create a Action Based Extensibility

Open Cloud Assembly and navigate Extensibility > Actions > NEW ACTION. Enter a Name, Description and select the Project to contain the action

Click on Load Template 

Select Rename VM and Click Load.

Left side in script pane, add [customProperties] in line 12 for the new_name inputs. 

Right side properties tab, remove the all input variables and select On prem as FaaS Provider.

 

Save the action 

Now time to create new Blueprint and create Custom Properties as per your convenience . In my case  I have created  “newname”. 

Save and close the blueprint.

Let ‘s create New Subscription.

Go back to Extensibility. Click Subscriptions. Click New Subscription.

Enter a Name and select Compute Allocation as Event Topic

In my case  I will filter based on the blueprintId to ensure that only my blueprint triggers the execution. Finally, I will assign my ABX Action and ensure it’s a blocking task so that the blueprint deployment will not continue until the action has executed.

Note- Before going to test , make sure that your Project should not be configured with a Custom Naming template. 

 

 Request  for blueprint and Enter a custom VM name.

Go back to the Extensibility tab. Under Activity click Action Runs. Here you can see your actions being run after being triggered by an event broker subscription

Now time to check in vcenter if we have correct vm Name . In my case I have given “ICDS-test01 “

I hope you enjoy reading this blog as much as I enjoyed writing it. Feel free to share this on social media if it is worth sharing.