VMware

VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.2 Release Notes

VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.2 | 9 December 2014 | Build 2287231

VMware vRealize Orchestrator 6.0.0 (formerly vCenter Orchestrator) | 9 December 2014 | Build 2289455

VMware vRealize Automation 6.2 (formerly vCloud Automation Center) | 9 December 2014 | Build 2299574

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to VMware vCenter Orchestrator Plug-In for vCloud Automation Center

The VMware vCenter Orchestrator vCloud Automation Center plug-in provides access and control over any vCloud Automation Center or vRealize Automation system.

The vCenter Orchestrator vCloud Automation Center plug-in provides the following capabilities:

  • Interact with and manage catalog services, catalog items, advanced services custom resources, service blueprints and resource actions, tenants, approvals and entitlements, work items, and blueprints.
  • Allow organizations to automate operations on the vRealize Automation IaaS model entities.
  • Integrate your existing business logic and models with an arbitrary vRealize Automation server.
  • Add a vRealize Automation as a policy-based, declarative multi-hypervisor, provisioning functionality to an existing top level service catalog portal.
  • Use the vCloud Automation Center plug-in policies to place a workload when a scale out update is needed based on performance triggered by vRealize Operations.
  • Enable workflow designers to include create, read, update, and delete operations for an arbitrary vRealize Automation model entity in any entity set.
  • Connect dynamically to a vRealize Automation system and provision a virtual machine from a vRealize Automation blueprint.

The VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.2 release runs on VMware vRealize Orchestrator 6.0.0. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCloud Automation Center 6.2.

For information about vRealize Orchestrator, vRealize Orchestrator plug-ins, or vRealize Automation see the following documentation:

What's New in vCenter Orchestrator Plug-In for vCloud Automation Center 6.2

This release of the vCenter Orchestrator Plug-In for vCloud Automation Center introduces the following new functionalities:

  • vCenter Orchestrator Plug-In for vCloud Automation Center 6.2 works with vRealize Automation 6.2 and vRealize Orchestrator 6.0.0.
  • The ResquestsHelper.setFormValues method and the ResquestsHelper.setLiteralMapValues method are no longer restricted to primitive types for entry values. For example, DecimalLiteral, IntegerLiteral, and StringLiteral are now directly accepted as values for entries.
  • New Create an Approval Policy and Add an approval level workflows for creating vRealize Automation approval policies.
  • New workflows for content management allow you to validate and share Advanced Service Designer content between tenants or between vRealize Automation hosts.

Resolved Issues

The following issues are resolved in vCenter Orchestrator Plug-In for vCloud Automation Center release 6.2.

  • vCloud Automation Center Cafe plug-in disappears after restarting the vCenter Orchestrator service
    If you installed the plugin into a clustered vCenter Orchestrator environment, the inventory might be unstable. In cluster mode, the server is not always ready to accept new connections while the plug-in is starting and loading its configuration. This can cause the inventory to appear empty.
    If you install a clean vCenter Orchestrator Plug-In for vCloud Automation Center version 6.2, the issue is resolved. If you are upgrading from an earlier version of the plugin, see KB article 2094023 for information to resolve the issue before you upgrade.

  • Cannot pass JavaScript JSON objects to the methods post(url, object) and put(url, object)
    You cannot pass JavaScript JSON objects to the methods post(url, object) and put(url, object) unless you first transform the object into its string representation by using JSON.stringify(object).

  • Wait for a workflow execution end may finish prematurely
    The extensibility helper workflow, Wait for a workflow execution end, may finish before the workflow token it is monitoring finishes.

  • Duplication of workflow directories when performing an upgrade
    During upgrade from vCenter Orchestrator Plug-In for vCloud Automation Center version 6.0.1 to 6.1, the Administration subdirectory of the vCAC workflow directory contained a Services folder and a Service folder, each with a different set of workflows. When you upgrade to 6.2, all workflows are installed into the Services folder, and you can manually delete the empty Service folder.

  • Unable to find vSphere and vCloud Director virtual machines by unique identifier using the vCenter Orchestrator Plug-In for vCloud Automation Center 6.1 or directly in vSphere API
    The Workflow Runner helper workflow might fail to locate the VC:VirtualMachine inventory object. As a result, custom workflows invoked by the Workflow Runner workflow might fail with the error: TypeError: Cannot read property "datastore" from null. The VMUniqueID virtual machine entity property is changed from BiosUUID to InstanceUUID.

  • getOperations() do not return VcoID attributes
    Workflows might fail with an error message similar to the following:
    ch.dunes.model.type.ConvertorException: Unable to convert object, 'com.vmware.vcac.catalog.rest.stubs.CatalogResource@f3807a47' plugin exception reason : convertToResult() --> Finder 'vCACCAFE:CatalogResource' : unexpected error 'ch.dunes.model.sdk.SDKFinderException: convertToResult() --> Finder 'vCACCAFE:CatalogResource' id 'getVcoId()' is null for the Finder object.

    Resolution: Most findable objects retrieved by any REST service client are returned with a VcoId attribute. The two remaining exceptions are vCACCAFEAuthenticationIdentityStoreClientService().get*() and vCACCAFECatalogConsumerResourceService().getAvailableOperations(resourceId, pageable), but you can use the alternate methods described in the workaround.

    Workaround: Use vCACCAFEEntitiesFinder.find/getIdentityStores(..)) in place of vCACCAFEAuthenticationIdentityStoreClientService().get*(), and use vCACCAFEEntitiesFinder.find/getCatalogResourceActions(..) or vCACCAFECatalogConsumerResourceService().getResource(..).getOperations()) in place of vCACCAFECatalogConsumerResourceService().getAvailableOperations(resourceId, pageable).

Known Issues

Some issues have been discovered and the following information is intended to help you understand some behaviors you might encounter in this release:

  • Retrieving approval information by using a script results in missing property '@type' error
    The missing property type error is returned when you use the following script to retrieve approval information:
    var service = vcacHost.createApprovalClient().getApprovalApprovalInfoService();
    var approvalInfo = service.getApprovalInfo( approvalId );


    Workaround: Use the following script to retrieve approval information:
    var approvalClient = vcacHost.createApprovalClient();
    var vars = [ approvalId ]; var approvalInfo = approvalClient.getWithVariables("/info/approvals/{0}", vars);
    var approvalPolicy = new vCACCAFEApprovalDescriptiveReference() ;
    approvalPolicy.setId(approvalInfo.getProperty("policy").getProperty("id"));
    approvalPolicy.setName(approvalInfo.getProperty("policy").getProperty("name"));
    approvalPolicy.setDescription(approvalInfo.getProperty("policy").getProperty("description"));

  • On the Items tab of the vCloud Automation Center console, the name and description of some vCAC Infrastructure Administration resources do not display correctly
    If you publish a catalog item by using the Advanced Service Designer based on an infrastructure administration workflow that has an output parameter of vCAC:Entity type, when consumers request the catalog item successfully, the name and description of the provisioned items do not display correctly.

  • In the Inventory view of the vCenter Orchestrator client, the totalQuata property of some business groups does not display correctly
    When viewing the details of a business group in the Inventory view of the vCenter Orchestrator client, the value of the totalQuata property might display as 3.4028235E38 instead of 0.0.

  • The requests workflows for waiting do not work correctly when a vCloud Automation Center host is added with Per User Session connection and the vRealize Orchestrator server is restarted during running of the workflows
    The Wait for work item, Wait for resource action request, and Wait for catalog item request workflows result in "Unable to retrieve authentication for this task" instead of "Approved" or "Rejected" if a vCloud Automation Center host is added with Per User Session connection and the vCenter Orchestrator server is restarted during running of these workflows.

  • vCloud Automation Center Plug-in API documentation is still in development
    vCAC and VCACCAFE modules of the vCenter Orchestrator API Explorer do not provide complete API documentation.

    Workaround: You can download the latest versions of the API documentation from vRealize Automation Documentation or access the vRealize Automation API documentation on https://vRealize_automation_appliance_host/component-registry/services/docs.

  • Searching for business groups returns results for all hosts
    When you run workflows for updating or deleting business groups, or adding, updating, or deleting custom properties for a business group from the Workflows view, there is no option to restrict the search function to a particular vCloud Automation Center host.

    Workaround: Run these workflows from the Inventory view.

    1. Click the Inventory view in the Orchestrator client.
    2. Right-click the business group you want to update.
    3. Select the workflow to run.

  • The workflows provided in the plug-in do not perform the same validation as vCloud Automation Center UI
    The vCloud Automation Center user interface performs validation checks, but not all of this logic is accounted for in the workflows provided with the plug-in. For example, vCloud Automation Center prevents you from creating a tenant with a non-unique URL, but the plug-in workflow does not validate this. Make sure that your custom workflows take care of any validation required by vCloud Automation Center.

  • The vCACCAFEAuthenticationGroupService.updateCustomGroup method removes all members of the updated group

    Workaround: Before using the vCACCAFEAuthenticationGroupService.updateCustomGroup method, retrieve the group members and reassign them to the group after the update, for example:

    // Create a vCACCAFEAuthenticationGroupService instance to perform operations, where host is the vcac host configured by the vcaccafe plug-in.

    var groupService = host.createAuthenticationClient().getAuthenticationGroupService();

    // Retrieve current members, where groupToBeUpdated is the target custom group

    var membersUsers = groupService.getUsersInGroup(tenant, groupToBeUpdated, criteria, pageable);

    var membersGroups = groupService.getGroupsByCriteriaAndDomainAndParentGroup(tenant, criteria, domain, groupToBeUpdated);

    // Update the group, retrieve the updated group, and reassign the members:

    groupService.updateCustomGroup(tenant, groupToBeUpdated);

    var updatedGroup= groupService.getGroup(tenant, groupToBeUpdated.getPrincipalId().asString());

    groupService.assignGroupsAndUsersToCustomGroup(tenant, updatedGroup, membersGroups, membersUsers);

Top of Page