VMware vCenter Orchestrator HTTP-REST Plug-In 1.0 Release Notes

What's in the Release Notes

• Introduction to the VMware vCenter Orchestrator HTTP-REST Plug-In
• Known Issues

Introduction to the VMware vCenter Orchestrator HTTP-REST Plug-In

The VMware vCenter Orchestrator HTTP-REST plug-in allows organizations to integrate their cloud provisioning and operations use cases with systems that offer Web services. Provisioning a virtual machine or requesting a cloud-hosted IT service, often is part of a larger IT process that includes various management systems, such as service desk, change management, IP address management, CMDB, or configuration management. With the HTTP-REST plug-in, organizations can integrate vSphere and vCloud Director into automated processes that use third-party-system REST APIs.

In addition to HTTP methods such as GET, POST, PUT, and DELETE, the plug-in offers dynamic querying of target URIs directly from the Orchestrator client. This enables workflow developers to create workflows in just a few clicks and hide the complexity of the underlying API.

The HTTP-REST plug-in supports multiple authentication methods to enable secure integration with virtually any application that exposes a REST API.

The VMware vCenter Orchestrator HTTP-REST Plug-In 1.0 release runs on VMware vCenter Orchestrator 4.1 and the subsequent update releases. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator HTTP-REST Plug-In 1.0.x.

Top of Page

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator HTTP-REST Plug-In 1.0 release:

• Limited number of operation input parameters
  

  You cannot specify more than 15 input parameters when you run the Invoke a REST operation workflow.

  Workaround: Generate a new workflow from a REST operation for operations with more than 15 input parameters.

• Adding a schema to a host might be slow
  

  If you add an XSD schema to a host, the operation might take a considerable amount of time depending on the schema size, the number of imports, and the connection to the server hosting the schema.

• Generating a workflow from an operation with attached schema might be slow
  

  The first time you generate a workflow from an operation that has an XSD schema attached to it, the operation might take a considerable amount of time.

• Using a schema might cause problems with arrays
  

  When you generate a workflow from a POST or PUT operation that contains an array of elements as input, if an XSD schema is used to generate the presentation, the workflow shows only one element instead of an array.

• Updating or cloning a REST host might be slow
  

  When you update or clone a host, the operation might take a considerable amount of time, depending on the size of the data that is loaded for the presentation.

Top of Page