1. Introduction
2. Journey
3. High-level View of Workflow
4. Deployment Time
5. Conclusion

Introduction

In this blog, I will conduct a thorough analysis of the capabilities offered by VMware Aria Automation Orchestrator workflows. These workflows are integral to the automation of various processes within the VMware by Broadcom ecosystem.

This discussion will focus on the mechanisms by which VMware Aria Automation manages the deployment and deletion of virtual machines, particularly in relation to DNS entries. When a new machine is deployed, the system automatically generates a corresponding DNS entry, ensuring efficient network connectivity and management. Conversely, upon the deletion of a virtual machine, the associated DNS entry is systematically removed, thereby maintaining an accurate and up-to-date DNS record.

By examining these automated functionalities, this analysis aims to highlight how VMware Aria Automation significantly enhances operational efficiency while reducing the need for manual interventions. This enables IT professionals to allocate their resources and efforts toward more strategic and high-level initiatives.

I am currently utilizing VMware Aria Automation, specifically version 8.18.1.36791, Build 24282366. For the template, I have selected ubuntu-22.04.5-desktop-amd64, which offers a reliable and comprehensive platform for my initiatives. The compute environment is supported by VMware vSphere version 8.0.3.00400, facilitating optimal resource management and scalability. Additionally, I am employing the Overlay network NSX-4.2.1.0.0.24304122, configured with the IP address , to ensure efficient and secure communication throughout the infrastructure.

Journey

This blog series consists of two detailed parts, aimed at guiding you through the process of managing DNS entries using VMware Aria Automation Orchestrator workflows in conjunction with machine deployments and deletions.

Part 1: In the first part of this series, we will thoroughly investigate the steps involved in creating VMware Aria Automation Orchestrator workflows that automatically add a DNS entry whenever a new machine is deployed. We will cover the necessary configurations, best practices, and troubleshooting tips to ensure a smooth integration between the orchestration workflows and the DNS management process.
https://puneetsharma.blog/2025/01/31/vmware-aria-automation-capabilities-orchestrator-workflows-part-1/

Part 2: In the second part, we will shift our focus to the opposite scenario, where we will develop VMware Aria Automation Orchestrator workflows designed to delete a DNS entry when a machine is removed from the environment. This segment will include a comprehensive explanation of the workflow creation process, along with essential insights on managing DNS records effectively during machine deletions.

Together, these parts will provide you with a robust understanding of how to enhance your automation efforts while maintaining accurate DNS records in your infrastructure.

High-level View of Workflow

Capture 1: –

As shown in capture 1 is high level View of Workflow. lets get summary each Step: –

1. Connect Your PowerShell Endpoint in an Orchestrator: – You connect VMware Aria Automation Orchestrator to the PowerShell host so that workflows can run PowerShell commands.
2. Creating A VM-Node & Network template: – We will create a VMware Aria Automation template that creates a VM Node and sets a static IP address.
3. Creating an Orchestrator Workflow: -This workflow receives custom properties from VMware Aria Automation Orchestrator and uses them to add a DNS entry to the DNS server.
4. Embedded-VRO data collection: – We will wait for data collection to make sure that VMware Aria Automation Assembler is aware of the new workflow.
5. Creating an Extensibility Subscription: – We will create a subscription to run a workflow after the virtual machine is provisioned.
6. Deploy a VM Node: – We will deploy the VMware Aria Automation template to test the subscription and workflow.
7. Verify the DNS Entry: – In the DNS Manager view we will view the new DNS entry.

Deployment Time

1. Connect Your PowerShell Endpoint in an Orchestrator

Capture 1: –

Under VMware Aria Automation Orchestrator

1. Navigate to library.
2. Click on Workflows.
3. Write down “PowerShell” in the Filter text box.
4. find the “Add a PowerShell host” library.
5. Click on Run.

Capture 1.1: –

7. Navigate to PowerShell Host.

8. Give the Appropriate Name

9. Give the FQDN /IP of the Domain Controller host

10. Give the port number.

Note: – This is the Windows Remote Management (WinRM) HTTP transport port number.

Capture 1.2: –

11. Navigate to User Credentials.

12. Select the “Shared Session” under the Session mode.

13. Give the Enterprise domain controller administrator credentials under the Username.

14. Give the password of the Enterprise domain controller administrator

15. Click on run the workflow.

Capture 1.3: –

Capture 1.4: –

19. Navigate to Inventory under Administration.

20. Expand the PowerShell.

21. Click on Domain Controller.

Note: – here we can verify again the PowerShell plugin successfully added. We can use the Python or other compatible plugin instead of PowerShell Plugin.

2. Creating a VM-Node & Network template

Capture 2.0: –

Go to VMware Aria Automation Assembler

1. Click on Design.

2. Click on Templates.

3. Drop Down the NEW FROM.

4. Click on Blank Canvas.

Note : – If you already have the YAML configuration file, click Upload.

Capture 2.1: –

5. Gives the name of the template.

6. Give the Description of the template.

7. Select the Project

8. Select the “Share only with this project”

Note: – This template i only want to sync with assigned project.

9. Click on CREATE.

Capture 2.2: –

10. Write the Configuration under the code in the Coding Area.

11. Click on test.

Note: – Test the syntax before deploying is the best practices.

Capture2.3: –

12. Give the name of the Host.

13. Give the Ip address of the Host.

14. Click on Test.

Capture2.4: –

15. Successfully tested the YAML configuration.

3. Creating an Orchestrator Workflow

This workflow utilizes custom properties obtained from VMware Aria Automation Orchestrator to facilitate the addition of a DNS entry to the DNS server. The process is designed to ensure accuracy and efficiency in integrating new entries into the existing DNS infrastructure.

Capture 1: –

Open the VMware Aria Automation Orchestrator.

1. Navigate to Workflows.
2. Click on NEW WORKFLOW.
3. Give the name of the New Workflow.
4. Click on Create.

Capture 2: –

5. Give the tag in the Enter a new tag text box.

6. Select the workflow where you want to store the current Workflow.

7. Click on Save.

Capture 3: –

8. Click on Variables.

9. Click on NEW.

Note: – We have created the 06 local variables.

Capture 4 : –

10. Select and Click on the host.

11. Click on Value.

Capture 5: –

12. Expand the PowerShell and Check the Domain Controller.

13. Click on Select.

Capture 6: –

14. Click on Save.

Capture 7: –

Now we will configure the Input/Outputs as per our workflow.

15. Click on Inputs/Outputs.

16. Click on New.

Note: – As per our workflow required we have configured the 01 Input & 01 Output.

Capture 8: –

17. Click on Schema.

Note: – The Schema has three schema Elements. Verifying InputProperties, Creating CommandShell and Execute a PowerShell Script. Let’s examine each schema element in brief.

Verifying InputProperties

Capture 8.1: –

In the heart of the Verifying InputProperties schema element lies a piece of code that skillfully maps the value of yamlHostname1 to the variable hostName, while also linking yamlIpAddress to the variable ipAddress. Both of these variables are defined as strings, serving a vital role in the configuration.

Capture 8.2: –

The inputs and outputs for the Verifying InputProperties schema element are defined as follows.

This code taps into the custom property yamlIpAddress, a critical element crafted in your cloud template YAML(DNS Template). It’s designed to extract the precise IP address that is assigned to a virtual machine. With this setup, you can seamlessly retrieve the actual IP address from the input property associated with that virtual machine, ensuring clarity and precision in your configurations.

Creating CommandShell

The Creating CommandShell schema element intricately crafts a dynamic PowerShell command, seamlessly incorporating both the hostname and the IP address into its structure. This powerful tool allows users to easily manipulate and execute commands tailored to their network environment.

Capture 8.3: –

In the workflow, the cmdletName and zoneName variables are explicitly defined as Add-DnsServerResourceRecordA and XYZ.local, respectively. To explore these variables in detail, simply navigate to the Variables tab within the workflow interface, where you can easily view and manage them.

Capture 8.4: –

The text is combined into pshellCommand and used to run a PowerShell script in the final vRealize Orchestrator schema element. For example: –

Sr. No	Description	Execution cmd
1	Add DNS Server	Add-DnsServerResourceRecordA
2	host Name	– Name Dev-VM198
3	Zone Name	-ZoneName xyz.local
4	Creating Pointer	-CreatePTR 172.20.10.198

Capture 9: –

Now we will validate the workflow.

18. Click on Validate.

Note: – Validation of scripts and workflow are successful.

4. Embedded-VRO Data Collection

The term “Embedded vRO in vRA 8” describes the version of VMware vRealize Orchestrator (vRO) that is integrated within a vRealize Automation (vRA) 8 deployment. This integration enables users to execute workflows directly from the vRA interface, thereby eliminating the need for a separate installation of the vRO server. It offers built-in automation capabilities that enhance the functionality of the vRA platform.

Capture 1: –

Go to Assembler Tab.

1. Click on Infrastructure.
2. Navigate to Integrations under Connections.
3. Click on Open.

Capture 2: –

4. Click on Start data collection.

It is necessary to wait for data collection to confirm that VMware Aria Automation Assembler acknowledges the introduction of the new workflow. A status message that indicates that data collection is complete appears.

5. Creating an Extensibility Subscription

Now we will create a subscription to run a workflow after the virtual machine is provisioned.

Capture 1: –

Go to Assembler.

1. Click on Extensibility.
2. Click on Subscriptions.
3. Click on +New.

Capture 2: –

4. Give the name of the Subscription.

5. Give the description of the Subscription.

6. click on + ADD under the Event Topic.

Capture 3: –

7. find the “Compute post provision” in the filter.

8. Click on radio button.

9. Click on Select.

Note: – event topic has added successfully.

Capture 4: –

10. Turn ON the toggle of the Filter Events in topic.

11. Write down event.data.componentId == ‘Overlay-Node’ in the Condition text box.

Note: – Filter used in this Topics are Case-Sensitive. As we can see the Resource name of the yaml code called in the condition filter of the event data.

Capture 5: –

12.Click on + ADD under the Action/Workflow

13. Select the Workflow under the Runnable type.

14. Search the Workflow name in the Filter. As we use VOE Add DNS.

15. Select the Radio button of the Workflow.

16. Click on Select.

Note VOE Add DNS is successfully added.

Capture 6: –

17. Verify that the Blocking toggle is turned off (no blocking).

18. The Project scope toggle is turned on to activate Any project.

19. Click on Save.

6. Deploy a VM Node From Template

Now we will deploying the VMware Aria Automation template to test your subscription and workflow.

Capture 1: –

Go to Assembler Tab.

1. Click on Design
2. Click on Templates.
3. Select the template.
4. Click on Deploy.

Capture 2: –

5. Create a new deployment.

6. Give the name of the deployment under the deployment Name.

7. Template version should be Current version.

8. Give the description.

9. Click on Next.

Capture 3: –

10. Give the name of the Host.

11. Give the Ip of the host

12. Click on Deploy.

Capture 4: –

13. Creation in Progress.

Capture 5: –

14. DNS template test successfully Deployed.

Capture 5: –

Go to Aria Automation Orchestrator.

15. Click on Workflow Runs under the Activity.

16. Search the Workflow run in the recent workflow.

17. As we can see status is completed.

18. Click on logs.

19. As you can see the Hostname “DEV-198” and IP Address 172.20.10.198 is successfully executed.

7. Finally -Verifying the DNS Entry

Capture 1: –

Go to vSphere Client.

1. We can VM is successfully created in the name of Overlay-node-mcm405-XXXXXXX.
2. VM status is Powered On.
3. DNS Name is DEV-198.
4. IP Address is 172.20.10.198.

Capture 2: –

5. We can see the A Record of DEV-198 is Successfully created automatically.

6. We can see the PTR Record of DEV-198 is Successfully created automatically.

Conclusion

VMware Aria Automation Orchestrator is a powerful development and process automation platform, featuring a rich library of workflows and an advanced workflow engine. Using the intuitive workflow editor, we have demonstrated how DNS auto-updates occur seamlessly during the creation of a new virtual machine (VM), ensuring uninterrupted network connectivity. In the following section, I will clarify the process of DNS auto-updates that takes place during the deletion of a VM template, emphasizing its crucial role in maintaining network integrity.

Please find all the templates and scripts used in this blog here.