Users Guide
NOTE: Mismatching in selection will make the ASM server to refuse the deployment.
13. Provide the service name and description to complete all the elds (Optional).
14. Click Submit.
The vRA triggers the vRO workow to call the ASM server for a new service deployment.
Workow Output
The ASM vRO sample workow may have an output parameter with a custom API object type. If the vRA needs to use the
information in the output parameter, it cannot be parsed easily in the vRA layer. Therefore, the workow should be modied to parse
the parameter into primitive data type objects before running it (For example: Add a script action that takes the custom API object
and outputs string objects). In this way the output data can be easily used by vRA.
Upgrading the vRA XaaS Blueprint
To upgrade the vRA XaaS Blueprint along with the vRO and the ASM vRO plugin, complete the following tasks:
1. Place both vRO and vRA servers under maintenance. No deployments should be made during this period. Take note or snapshot
to save the non-interactive workows’ congurations.
If customized workows or newly created workows are implemented, create a new package to save those elements.
To create a new package,
a. In the left pane, click Packages.
b. In the right pane, click Add package.
c. Type the appropriate name to the package and click Edit.
d. In the Edit mode, click the Workows tab, and then click Insert Workows (either list search or tree).
A pop-up window is displayed.
e. Search or select the custom workows.
f. After the workows are added to the package, save and exit the edit mode.
g. To export the package, click Export package.
2. Uninstall the old plugin and congurations.
3. Upgrade the vRO server. Optionally, vRA server can be upgraded during this period.
4. After the upgrade, install the vRO plugin 2.0.
5. Modify the non-interactive workows as needed in the new plugin installed.
6. Update the XaaS Blueprint in vRA to point to the new workows.
29