1. Delighted
2. Phase-09 Pivotal Phase
3. Verification
4. Conclusion

Delighted

It is a pleasure to have the opportunity to once again convene with you. This document serves as Part 3 of the Blog Series regarding NSX Integration with Aria Automation, entitled “Part-03”.

Part 1 primarily concentrated on establishing the fundamental knowledge of deployment types and initial configuration.

Part 2 delved into a comprehensive explanation of the prerequisites essential for devising the initial configuration roadmap.

In the event that you missed Part 1 & Part 2, we kindly direct you to the following links.

NSX integration with Aria Automation-Part-01

NSX Integration with Aria Automation-Part-02

NSX Integration with Aria Automation-Part-03

Initial Configuration Roadmap

Capture 1: –

Phase-09 Pivotal Phase

Prior to executing the requisite configuration in the production stage, it is imperative to traverse two preliminary phases.

Test: -Prior to initiating a deployment from a VMware Aria Automation template, it is advisable to verify the syntactic validity and conformity to the specified constraints with tags by selecting “TEST” for the YAML code.

Deploy: -To carry out the deployment from a VMware Aria Automation template within the VMware Aria Automation template designer, select “DEPLOY”.

Before we test our YAML code let we understand our scenario as below: –

Capture 1: –

Note: -We aim to implement the 2-Tier APP composed of Tier 1, which is the Overlay-APP, and Tier 2, which is the Web-APP. In Capture 1 canvas, the left side serves as the Design pane, while the right side is designated as the configuration pane. The numbers marked in red represent Tier-1, while those in blue represent Tier-2.

Scenario: –

Note: -(Sr. No of scenario are not matched with the design/configuration pane )

1. We are trying to deploy 2 VMs(Overlay VM & Web VM)(vCenter task).
2. Overlay VM connected to Overlay Segment for Network(NSX Task).
   • Note: – Due to isolation Policy-None, Overlay VM should get the IP from the NSX IPAM.
3. The overlay Segment is connected to the NSX-Overlay-Profile(Aria Automation Assembler task).
4. Overlay VM should be a part of Overlay-VM-Group(NSX Security Group task).
5. Overlay-VM should be tagged under Overlay-VM-Tag.
6. Web VM connected to Web Segment for Network(NSX Task).
   • Note: – Due to isolation Policy-None, Web VM should get the IP from the NSX IPAM.
7. Web Segment is connected to the NSX-Overlay-Profile(Aria Automation Assembler task).
8. Web VM should be a part of Web-VM-Group(NSX Security Group task).
9. Web-VM should be tagged under Web-VM-Tag.

Testing Stage: –

When working with YAML code, it is crucial to verify its syntax for validity and ensure that it adheres to specified constraints. This can be achieved by using tags and selecting “TEST” for the YAML code.

Capture 1: –

Step 1:- Click on TEST

Step 2: – 2-Tier Template is syntactically approved and validated.

Step 3:- Click on Provisioning Diagram.

Note: – This will show the complete testing results workflow.

You have an alternative method to observe the testing results workflow. You can access it from the infrastructure tab by following these steps: Assembler -> Infrastructure -> Activity -> Request. By doing so, you will see the same path that is depicted in the provisioning diagram.

Step 4: – Click on ‘Security group allocation’ and we will be able to see the components of both VMs.”

Step 5: – Click on Network Allocation.

Note: – We can see the segments are attached with the correct network profiles.

Step 6: – Click on Machine Allocation

Note: – We can see each machine is allocated with the defined -image, flavor and instance priority.

All test results have conformed to our expectations, thereby indicating readiness for the deployment of the 2-Tier-template in the production stage.

Deployment Stage: –

To commence the deployment of a VMware Aria Automation template within the VMware Aria Automation template designer, locate the “DEPLOY” option and click on it. This action triggers the start of the deployment process for the selected automation template.

Capture 1: –

Step 1: -Click on DEPLOY

Step 2: – click on “Create a new deployment”

Note: – We have opted for this option because we are in the process of setting up a new deployment. If the template has already been deployed and we intend to make modifications, we should select the “update an existing deployment” option.

Step 3: – Give the rememberable name under the Deployment Name.

Step 4: – This is our first template which is why we selected the template version as a current draft.

Step 5: – Describe the template.

Step 6: – Click on deploy.

Note: – In my lab it will take less than 5 minutes to deploy the current configuration.

Step 7: – We can see the progress of the deployment.

Step 8: – Click on history to see the live deployment steps.

Step 9: – Click on Provisioning Diagram

Note: – This will show the complete testing results workflow.

Step 10: – We can see our deployment is created successfully.

As is said before, we have an alternative method to observe the testing results workflow. You can access it from the infrastructure tab by following these steps: Assembler -> Infrastructure -> Activity -> Request. By doing so, you will see the same path that is depicted in the provisioning diagram.

Verification

let’s verify the configuration in the steps: –

1. Verify our configuration from the vCenter Level(vCenter task).
2. Verify segments assigned to the correct VM(NSX Task).
3. Verify Security groups allocated to correct VM (NSX Task).

1. Verify our configuration from the vCenter Level.

VM Name : – Overlay_node-03-mcm2132-270391117840

IP Address: – 172.16.1.101

VM storage Policies: – vSAN Default Storage Policy

Network Adaptor: – Overlay-Segment

VM Name: – Web_node-03-mcm2134-270391125556

IP Address: – 172.17.1.101

VM storage Policies: – vSAN Default Storage Policy

Network Adaptor: – Web-Segment

Based on the vCenter verification, it has been confirmed that both the Overlay-VM and Web-VM have been successfully deployed with the necessary configuration. We can now proceed to the next verification.

2. Verify VM assigned to correct segment.

Overlay-VM Successfully verified.

Web-VM Successfully verified.

3. Verify Security groups allocated to correct VM

Step 1: – click on Inventory

Step 2: – Click on Groups

As we can see the below details: –

Security Group Name: – Overlay-VM-Group

Segment Port: – Overlay_node_03-xxxxxxxxxxx

IP Address: – 172.16.1.101

VIF: – Overlay-node-03-xxxxxxx connected network adaptor 1

Step 1: – click on Inventory

Step 2: – Click on Groups

As we can see the below details: –

Security Group Name: – Web-VM-Group

Segment Port: – web_node_03-xxxxxxxxxxx

IP Address: – 172.17.1.101

VIF: – Web-node-03-xxxxxxx connected network adaptor 1

Conclusion

Below is the YAML code used in this lab demo. Click here . In the concluding part of this blog series, we have expounded on the fundamental principles of Aria automation, specifically emphasizing the elucidation of diverse deployment types and initial configuration roadmaps in Part 1.

Part 2 provides a comprehensive exploration of the intricate elements of initial configuration, encompassing the integration of Cloud accounts, cloud zones, project creation, network and storage profiles, image and flavor mapping, and configuration pane.

Part 3 presents an in-depth analysis of the comprehensive testing and deployment stages, affording a detailed and interactive outlook on the process.