VMware

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

VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.1 | 9 September 2014 | Build 2073620

VMware vCenter Orchestrator 5.5.2 | 9 September 2014 | Build 1951762

vCloud Automation Center 6.1 | 9 September 2014 | Build 2077124

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 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 vCloud Automation Center IaaS model entities.
  • Integrate your existing business logic and models with an arbitrary vCloud Automation Center server.
  • Add a vCloud Automation Center 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 vCenter Operations.
  • Enable workflow designers to include create, read, update, and delete operations for an arbitrary vCloud Automation Center model entity in any entity set.
  • Connect dynamically to a vCloud Automation Center system and provision a virtual machine from a vCloud Automation Center blueprint.

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

For information about vCenter Orchestrator, vCenter Orchestrator plug-ins, or vCloud Automation Center see the following documentation:

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

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.1 works with vCloud Automation Center 6.1.
  • The Add a vCAC host wokflow supports Per User Session connection to the default tenant if the vCenter Orchestrator server is registered in the vCloud Automation Center component registry.
  • When the vCenter Orchestrator server is registered in the vCloud Automation Center component registry, a Default vCloud Automation Center host is automatically added with Per User Session connection to the default tenant.
  • New Add a vCAC host using component registry workflow for adding a vCloud Automation Center host with Per User Session connection to the default tenant if the vCenter Orchestrator server is registered in the vCloud Automation Center component registry.
  • Improved descriptions of some workflows and workflow parameters.
  • New Create a Management Endpoint and Delete a Management Endpoint workflows replacing the Create a Management Endpoint (Deprecated) and Delete a Management Endpoint (Deprecated) workflows.

Resolved Issues

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

  • Per User Session connection is not supported for vCloud Automation Center hosts
    When you configure vCloud Automation Center hosts, you must select Shared Session type of connection and provide credentials for authentication.

  • CACCAFEAuthenticationGroupService.getGroupsByCriteriaAndDomainAndParentGroupAndGroupType method does not take groupType into account
    The vCACCAFEAuthenticationGroupService.getGroupsByCriteriaAndDomainAndParentGroupAndGroupType(tenant, criteria, domain, parentGroup, groupType) method does not take groupType into account.

  • Error Messages for interactions with deleted objects
    If you attempt to execute workflows on deleted objects, for example if you attempt to update an identity store that has been deleted in vCloud Automation Center, the error messages you receive might not explain that the object no longer exists.

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:

  • 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.

    Workaround: For more information on how to resolve this issue, see http://kb.vmware.com/kb/2088838.

  • 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 vCenter Orcestrator 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 Orcestrator 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 vCloud Automation Center Documentation or access the vCloud Automation Center API documentation on https://vcloud_automation_center_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 cofigured 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