VMware

VMware vCenter Orchestrator Plug-In for vCenter Server 5.0 Release Notes

VMware vCenter Orchestrator Plug-In for vCenter Server 5.0 | 13 Sep 2011 | Build 149

VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581

VMware vCenter Orchestrator 4.2 | 24 Aug 2011 | Build 5277

Last document update 02 Nov 2011

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to the VMware vCenter Orchestrator Plug-In for vCenter Server 5.0

This updated version of the vCenter Server plug-in provides 100% coverage of the vSphere 5.0 API and adds new out-of-the-box workflows to further extend the orchestration use cases around vCenter Server 5.0.

Key to this update are more than 50 new workflows extending the coverage of networking and storage, and bringing automation capabilities to new features such as Storage DRS. Some of the new workflows provided in this release include:

  • Connect a virtual machine NIC number to distributed virtual port group
  • Create distributed virtual switch
  • Update port group in standard virtual switch
  • Attach host system to distributed virtual switch
  • Add datastore on NFS
  • Add datastore on iSCSI/FC/local SCSI
  • Add datastore to cluster
  • Create VMDK anti-affinity rule

With this plug-in, organizations can now automate a broader number of use cases such as dynamic provisioning and configuration of vSphere 5.0 resources, while taking advantage of the new vCenter Server 5.0 capabilities. When combined with the SNMP plug-in and other vCO plug-ins, the vCenter Server 5.0 plug-in means that only a fraction of routine processes around the VMware virtual infrastructure still require manual intervention.

The vCenter Orchestrator Plug-In for vCenter Server 5.0 runs on VMware vCenter Orchestrator 4.1 and later. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCenter Server 5.0.x.

Top of Page

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator Plug-In for vCenter Server 5.0 release:

  • New When you install the vCenter Server 5.0 plug-in, the vCenter Server 4.1 plug-in is not removed from your system
    When you install the vCenter Server 5.0 plug-in, the vCenter Server 4.1 plug-in installation is not removed. Having both versions of the plug-in might cause some issues.
    Workaround: Remove the vCenter Server 4.1 plug-in before installing the vCenter Server 5.0 plug-in. To uninstall the plug-in:
    1. Log in as an administrator to the machine on which the Orchestrator server is installed.
    2. Navigate to the vCenter Server 4.1 plug-in .dar file.
      • If you installed Orchestrator with the vCenter Server installer, the default path is:
        install_directory\VMware\Insfrastructure\Orchestrator\app-server\server\vmo\plugins\o11nplugin-vsphere41.dar.
      • If you installed the standalone version of Orchestrator, the default path is:
        install_directory\VMware\Orchestrator\app-server\server\vmo\plugins.
    3. Restart the vCenter Orchestrator configuration service and the vCenter Orchestrator server.
  • Stopping the vCenter Inventory Service causes an error in the plug-in
    If you stop the vCenter Inventory Service on a vCenter Server instance that is registered in the plug-in, the Inventory view of the plug-in in the Orchestrator client displays an error message.
    Note: If you start the vCenter Inventory Service again, you can refresh the Inventory view of the plug-in in the Orchestrator client to use the plug-in with enabled vCenter Inventory Service.

    Workaround: Restart the Orchestrator service to use the plug-in with disabled vCenter Inventory Service.

  • Certificates required for vCenter Server instances in a linked mode group
    If you register a vCenter Server instance which is in a linked mode group, you must import the certificates of all vCenter Sever instances that you added to the configuration in this operation, so that Orchestrator can recognize all vCenter Server instances in the linked mode group.
  • The vCenter Server 5.0 plug-in might run out of memory
    The vCenter Server 5.0 plug-in might run out of memory with an OutOfMemory error message when you configure it to work with vCenter Orchestrator 4.1.

    Workaround: Modify the jetty-service.conf file on the machine on which the Orchestrator server and the vCenter Server 5.0 plug-in are installed.

    1. Log in as an administrator to the machine on which the Orchestrator server and the vCenter Server 5.0 plug-in are installed.
    2. Locate the jetty-service.conf file.
      The default location is: C:\Program Files\VMware\Infrastructure\Orchestrator\configuration\jetty\jetty-service.conf.
    3. Open the file in a text editor.
    4. Add the following line:
      wrapper.java.additional.7=-XX:MaxPermSize=128m
    5. Change wrapper.java.maxmemory=64 to wrapper.java.maxmemory=256.

    Top of Page