posts/vra-how-to-add-vnic-to-vm-as-day2-action/ #5
Replies: 2 comments 4 replies
-
Hi, Thanks for sharing the details. I am trying to test the same in my Lab environment but the workflow getting failed missing ; before statement (Dynamic Script Module name : virtualNetworkManagement#10) Am I missing something here? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi, Thanks for your reply. I imported this package com.clouddepth.add_new_nic_to_vm-1.0.14.package and copied the action code(virtualNetworkManagement.ts) and created new action in my lab. Provided inputs values and ran the workflow. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
posts/vra-how-to-add-vnic-to-vm-as-day2-action/
Today, we’re going to implement a day 2 action for vRA deployment. Custom day 2 actions are a great feature of vRA. They allow us to add almost anything. We will use this feature to add and connect a new vNIC to the deployed VM. We will support both Standard and Distributed switches and all available types of vNICs. Additionally, we’ll use native JavaScript, but we’ll employ more advanced techniques to make our code more professional. To do this, we’ll create a networking class that covers all the network parts. The idea is to create a workflow that will be triggered by the deployment and will call the action element, which will take care of creating and configuring a new network card.
https://www.clouddepth.com/posts/vra-how-to-add-vnic-to-vm-as-day2-action/
Beta Was this translation helpful? Give feedback.
All reactions