VRA ABX Action to set Deployment Lease

 Running vRealize Automation (VRA), I wanted to create a new catalog item in Service Broker that would basically self-destruct after a certain time. My intent is to allow our Windows engineers to quickly spin up a new machine in AWS with a lease applied to it. 

I could find a catalog template setting that allowed me to configure this, so I found that I could do this via a REST call to the VRA. So I decided to work on creating an extensibility action using Powershell. 

Note, once a lease is set, I don't think it's possible to remove the lease. 

Pre-requisites:

• Extensibility Actions on Prem integration server configured.
• VRA refresh token defined. This will be used in step 0.
• BlueprintID of a catalog template that will apply the lease to. We'll need this for step 2. The blueprint id can be captured easily from the URL when viewing it in the design menu. Copy everything after the %2F, for example (the bolded portion): 
  
  https://www.mgmt.cloud.vmware.com/automation-ui/#/blueprint-ui;ash=%2Fblueprint%2Fedit%2F123456-7890123456-123456789

Step 0: setup Action Constant

1. Inside VRA - Extensibility menu, select Actions on the sidebar. 
2. Select Action Constants and add a + New Action Constant
3. Enter the name of "refreshToken" and paste the refresh token string into the value field and select toggle to enable the Encrypt the action contact value. 
   
   
4. Click SAVE.

Step 1: create the action 

1. Extensibility menu, Actions on sidebar and click + New Action
2. Define the new action Name "SetDeploymentLease" and select the VRA Project that this will run against then click Next.
3. On the top, change the dropdown from PYTHON to POWERSHELL. 
4. Copy the pastebin code below and paste it into the body of the action.
5. Under Default Inputs, add two more input fields (for a total of 3). These fields will be used during the run-time of the action. 
   
   
   
   
1. Default - LeasePeriod - Positive integer for the number of days to define the lease.
2. Default - deploymentId - can be anything, this will be sent to the action from the subscription event defined in step 2. I copied the deployment id off an existing 'test' deployment directly from the URL. (like prerequisites, it's everything after the %2F). 
3. Action Constant - refreshToken - this will pull the value from Step 0.
6. SAVE the action

Step 2: create a subscription - The subscription will trigger after the blueprint is run.

1. Extensibility menu, Subscriptions option on sidebar and click + NEW SUBSCRIPTION
2. Give subscription name. 
3. For Event Topic select "Deployment Resource Completed"
4. Enable the Condition and enter a (case matters) single value of: 
   event.data.blueprintId == "value from pre-requisites"
5. Action/Workflow: select the new action you created in Step 1.
6. Projects: Select the project you specified in step 1, item 2.
7. SAVE
   
   
   
   
   
   

Testing: 

1. Option: If valid values are entered in step 1 part 5, the test button on the Action will run. 
   
   
   
   
   
2. Option: Deploy a new machine using the catalog item defined in the prerequisites. Within a minute after the deployment completes the build, the lease should be applied via the subscription. 
   
   
   

---

Using VRO to query tags for a VRA-Cloud Assembly dropdown

We've just started building servers in our vSphere with NSX-T environment using VRA to deploy the servers. The security group placement is controlled via NSX policies that are determined by the machine's tagging. I wanted to provide a dynamic dropdown in VRA so that I did not have to recode the cloud template and subsequent service broker custom form each time a new tag value was added to vSphere. I noticed in VRA that the NSX tags were being discovered there. 

This routine runs from VRO to read the tags in VRA (/iaas/api/tags) with a specific KEY, and returns the VALUE in a sorted array.

Prerequisites:

1. VRO server integrated with VRA-Cloud Assembly. 
2. VRA Plug-in to VRO (reference: here) - need to download and install on your VRO server.
3. Cloud template that needs a dropdown of tag values. 

Warning:  Without a filter, we have over 7,000 tags coming from NSX. When I tried to query all our tags, I crashed my VRO server and needed to reboot it to kill the query. 

   

Configuration:

1. Set default VRA host 
1. VRO - select Configurations - vRA plug-in
2. Variables tab - click on defaultHost
3. Click on the value field and select the VRA host you want to query.
4. Save
2. Create new Action
1. VRO - select Library - Actions menu item 
2. New Action
3. type in a name and module name 
1. typing in a 'new' name for the module will create a new module. 
4. Click on the Script tab and make sure Javascript is selected for Runtime.
5. On the right, click Add New Input button and create a new input
1. name: tagFilter
2. type: string
6. Change the Return type to string and check the checkbox for Array.
7. Paste the code below.
8. Save.

Last step, TEST! Click the RUN option up top before closing the Action screen and enter a tagFilter value that matches a tag showing in your VRA - Configure - Tags. 

Replication:

1. Log into your VRA instance
2. Scroll down to Integrations and open the VRO integration
3. Click the Start Data Collection button and wait...

Use:

1. Log into your VRA instance
2. Open a cloud template
3. Browse to the Inputs menu. 
4. Locate or create a new input. Mine:
1. Name: ApplicationTag
2. Display name: Application
3. Type: string
4. Default Value: leave blank.
5. Scroll to the bottom of the screen and expand More Options
1. Pairs: External Source
2. Action: click Select and search for the name you input into 2.3 in VRO above. 
3. Unselect BIND and type in the tag KEY value to filter on. 
4. SAVE to save select.
5. SAVE to close Input properties
6. Test cloud template - The dropdown should load for a few seconds then complete.