Technical Preview Version of VMware vCenter Orchestrator Plug-In for VMware vSphere 5.1.2

Technical Preview Version of VMware vCenter Orchestrator Plug-In for VMware vSphere 5.1.2

Technical Preview Version of VMware vCenter Orchestrator Plug-In for VMware vSphere 5.1.2

This is a patch release of the plug-in.

Version 5.1.2-568

  • Support virtual E1000e NIC
  • New VC extension manipulation methods in scripting API
  • Fixed data synchronization by retrieving certain properties of VcVirtualMachine objects from property collector (as opposed to inventory service)
  • Improved performance by utilizing the session cache when inventory service is used
  • Fixed session cache configuration, preventing object eviction, degrading performance
  • Possibility to disable use of inventory service by setting the value of the java system property "com.vmware.o11n.vim.useInventoryService" to "false" (in vmo.properties).
  • Other fixes:
    • close unused vCenter sessions
    • reload plugin configuration after updating it through workflows
    • recover unusable vCenter instances after they become usable again

Please note, that the attached plug-in is QE verified, but still not a final version.

This release is not an official one and is intended for testing purposes only. It is not recommended for production use.

Attachments
Comments

Thank you!

Could you explain more on these items?

  • New VC extension manipulation methods in scripting API
  • Other fixes:
    • close unused vCenter sessions
    • reload plugin configuration after updating it through workflows
    • recover unusable vCenter instances after they become usable again

Sure.

When a new VC host is added to the plugin configuration, the plugin registers itself with the VC instance as an extension. In some cases it is necessary for this registration to be manipulated manually. We added new scripting API methods and workflows, to allow registration and deregistration of the plugin, as well as listing the currently registered extensions on a given VC instance.

Regarding the fixes:

1. Previously it was possible for an VC session to remain open, even if it was no longer needed. The fix corrects reference counting of open VC sessions.

2. After making changes to the plugin's configuration through workflows (e.g. adding/removing/updating a VC host), in some cases VCO clients were not notified of the changes. The fix ensures that clients are always notified of configuration changes.

3. When an open VC session was detected as unusable (e.g. after a temporary hostname resolution error), it was possible that the session was not recovered, even after the detected error condition disappeared. We have addressed such situations.

Regards,

Victor Semionov

Version history
Revision #:
1 of 1
Last update:
‎11-13-2013 03:56 AM
Updated by: