VMware

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

VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1u1 | 5 August 2014 | Build 2008337

VMware vCenter Orchestrator 5.5.1 | 11 March 2014 | Build 1617131

vCloud Automation Center 6.0.1.2 | 10 July 2014 | Build 1768531

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.0.1u1 release runs on VMware vCenter Orchestrator 5.5.1. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.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.0.1u1

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.0.1u1 works with vCloud Automation Center 6.0.1.2.
  • New API methods for invalidating inventory cache.
    • vCACCAFEEntitiesFinder.invalidateAll() invalidates the entire plug-in inventory cache
    • vCACCAFEEntitiesFinder.invalidateEntity(Object entity) invalidates the cache for an object entity
    • vCACCAFEEntitiesFinder.invalidate(String type, String id) looks up an object entity by string type and string ID and invalidates the cache for the entity
  • New API methods for requesting catalog items in business groups.
    • vCACCAFERequestHelper.requestCatalogItemBySubtenant(CatalogItem item, Form form, String subtenant) submits a catalog item request for a business group
    • vCACCAFERequestHelper.requestCatalogItemBySubtenantOnBehalfOf(CatalogItem item, Form form, String subtenant, String onBehalfOf) submits a catalog item request on behalf of a specified user in a business group
  • New workflows for importing virtual machines include the step to publish the machines as catalog items.
    • Import vCAC Virtual Machine replaces deprecated workflow Register vCAC Virtual Machine
    • Import vCenter Virtual Machine replaces deprecated workflow Register vCenter Virtual Machine
  • Discovery workflows process child machines for multi-machine blueprints.
  • Host, group, and machine prefix fields in workflows for managing machine prefixes and fabric groups are marked as mandatory to reduce errors.
  • The Create a connection credential workflow returns both the entity and the inventory representation for the output parameter.

Resolved Issues

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

  • Executing workflow "Add an IaaS host" fails with error "java.lang.NullPointerException"
    This error occurs when using vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1 with vCloud Automation Center 6.0.1.2. This issue is resolved in vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1u1.

  • vCenter Orchestrator Plug-In for vCloud Automation Center invalidates cache settings required for vCenter Orchestrator Plug-In for vCloud Director
    The plug-in for vCloud Automation Center uses a custom cache configuration that overrides the default settings required by the vCloud Director plug-in and causes the vCloud Director plug-in to fail with an exception similar to the following: "Login failed with username 'test' (Dynamic Script Module name : addHost#15)." This issue is resolved.

  • vCenter Orchestrator Plug-In for vCloud Automation Center does not function when vCenter Orchestrator is set to cluster mode
    This issue is resolved.

  • Library Action "getRequestFormInputForCatalogItem" returns 'null' value even though all values are provided
    Requests for IaaS blueprints use the BlueprintViewModel object, which might contain a null value for business group ID that causes an internal exception. This issue is resolved.

  • Workflows for requesting catalog items always request for the first business group entitled to the item
    If multiple business groups are entitled to a catalog item, the item is requested for the first entitled business group. This issue is resolved.

  • Nesting multiple getLink() methods can result in scripting errors
    If you invoke the getLink() method on an object returned by a getLink() method, the child links might not expand and could cause scripting errors such as null pointers. This issue is resolved.

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:

  • Create a Management Endpoint workflow fails when using vCenter Orchestrator 5.5.1
    Running the Create a Management Endpoint workflow fails with a log message similar to the following: "Unable to serialize object of class : ch.dunes.vso.sdk.SDKTypeConvertor_server$1". This issue will be resolved with the next release of vCenter Orchestrator.

  • "Per-user session" authentication is not supported for vCloud Automation Center hosts
    When you configure vCloud Automation Center hosts, you must select "Shared Session" and provide credentials for authentication.

  • vCloud Automation Center 6.0.1 API documentation is still in development

    Workaround: You can download the latest versions of the API documentation from vCloud Automation Center Documentation.

  • 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 you want to run.

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

    Workaround: You can manually refresh the inventory in vCenter Orchestrator when objects are removed in vCloud Automation Center. Right-click the vCloud Automation Center host in the Inventory view and select Reload.

    1. Click the Inventory view in the Orchestrator client.
    2. Right-click the vCloud Automation Center host you want to refesh.
    3. Select Reload.

  • Out-of-the-box plug-in workflows do not provide 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.

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

    Workaround: You can iterate on the result and filter for a group type, for example:

    var childGroupsOfAllTypes = groupService.getGroupsByCriteriaAndDomainAndParentGroupAndGroupType(tenant, criteria, domain, group.getPrincipalId().asString(), vCACCAFEType.fromValue("CUSTOM"));

    var childCustomGroups = new Array();

    for ( var i = 0; i < childGroupsOfAllTypes.length; i++) {

    if (childGroupsOfAllTypes[i].getGroupType() == vCACCAFEType.fromValue("CUSTOM")) {

    groupsOfAllTypes = childGroupsOfAllTypes[i];

    }

    }

  • 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