Users Guide

Known Issues and Forewarning

• In order to use the deployTemplate method in the ASMAppliance object, the target template in ASM should have all the required

fields set to a static value or to auto-generate the value upon deployment request. In ASM UI, the deployment is not allowed

unless the required fields are all set. However, the vRO API plugin does not check to see if all the fields are set. Therefore this

can cause a deployment to start and fail later when the required fields are found to be not set.

• The current version of the plugin can add resources only by duplicating existing component(s) already defined in the Service.

Component types other than SERVER and STORAGE are not supported for duplication at this point. For the STORAGE

component scale up, the source component must be created from the ASM Service deployment or update event. Otherwise,

the ASM throws exception for duplicating a reference storage volume in a single Service.

• Duplicating storage has not been fully tested for NetApp storage type.

• Non-interactive sample workflows that are packaged with the plugin must be updated with valid attributes before they can be

used.

• As with the ASM UI, adding storage to a Service with a hyper-v cluster is disabled.

• Tearing down a Service with shared resources must be requested with precaution. ASM does not checkchecks whether the

resources requested for teardown are shared or not. If shared component is requested for teardown, it will result in an

exception. Selective teardown API method should be used in order to remove a Service without returning the resources to the

pool.

• For best practice, disable the standard users of vRO from the workflows in the Configuration Workflows folder. Ideally, a group

of privileged users and ASM administrators should have access to these workflows (especially the ones that can deploy, update,

or remove Service). Right-click on the target workflow(s) and click on the Edit access rights button. See VMware vRO

documentation for more detail how to control the access rights to workflows. These workflows are used to persist or remove

ASMAppliance objects as vRO resources.

• The vRO fails to load ASMAppliance object from the resource item if the connection fails.