What’s New in vSphere 4.1 API?

VMware announced GA of vSphere 4.1 product this Tuesday. Here is the official what’s new in vSphere 4.1. Many bloggers already covered different aspects of the product itself: VMware vSphere 4.1: Advancing the Platform for Cloud ComputingUseful vSphere 4.1 knowledgebase articlesvSphere 4.1 releasedRelease: VMware vSphere 4.1, etc. I don’t repeat these here, but focus on the new APIs in 4.1 release.

In general, the APIs are the programatic “view” of features. Understanding the features helps a lot on understanding the APIs. So I strongly encourage you to read new features of the product itself. Note that not all the new features especially the performance and scalability features are explicitly reflected in API signatures.

Bothered by SLOW Web UI to manage vSphere? Want to manage ALL your VMware vCenters, AWS, Azure, Openstack, container behind a SINGLE pane of glass? Want to search, analyze, report, visualize VMs, hosts, networks, datastores, events as easily as Google the Web? Find out more about vSearch 3.0: the search engine for all your private and public clouds.

vSphere API 4.1 introduces 7 new managed object types:

vSphere 4.1 adds 23 new methods to 10 existing managed object types:

Managed Object Method
ClusterComputeResource CancelRecommendation
Datastore UpdateVirtualMachineFiles
DistributedVirtualSwitch EnableNetworkResourceManagement
UpdateNetworkResourcePool
DistributedVirtualSwitchManager QueryDvsCheckCompatibility
QueryDvsFeatureCapability
HostSystem EnterLockdownMode
ExitLockdownMode
RetrieveHardwareUptime
HttpNfcLease HttpNfcLeaseGetManifest
PropertyCollector CancelRetrievePropertiesEx
ContinueRetrievePropertiesEx
CreatePropertyCollector
DestroyPropertyCollector
RetrievePropertiesEx
WaitForUpdatesEx
ResourcePool QueryResourceConfigOption
RefreshRuntime
VirtualApp SuspendVApp
UpdateLinkedChildren
VirtualMachine AcquireTicket
QueryFaultToleranceCompatibility
reloadVirtualMachineFromPath

vSphere API 4.1 also adds 8 properties to 6 existing managed object types:

There is one method signature change in the PowerOnMultiVM defined in Datacenter managed object with an additional parameter called option. If you use Web Service directly, your code may break.

Associated with the changes of the managed object types are the additions/changes of the data objects, enumerated type, and fault types. You don’t need to know these changes before you get to them from the managed object types introduced above.

The support of vSphere 4.1 is already done in vSphere(VI) Java API 2.1 beta. I will merge the code and push it to sourceforge code repository very soon. Please stay tuned for the announcement.

This entry was posted in vSphere API and tagged , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

One Trackback

  • […] The 2.1 beta works with VMware Infrastructure 3.0, 3.5, vSphere 4, and 4.1. It automatically detects the versions of 4 and 4.1, so you don’t need to change the way you work with the API. Besides the support of 4.1, it also includes several bug fixes since 2.0 update 1 released last December. For more info on what’s new in vSphere API 4.1, check out this blog. […]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

  • NEED HELP?


    My company has created products like vSearch ("Super vCenter"), vijavaNG APIs, EAM APIs, ICE tool. We also help clients with virtualization and cloud computing on customized development, training. Should you, or someone you know, need these products and services, please feel free to contact me: steve __AT__ doublecloud.org.

    Me: Steve Jin, VMware vExpert who authored the VMware VI and vSphere SDK by Prentice Hall, and created the de factor open source vSphere Java API while working at VMware engineering. Companies like Cisco, EMC, NetApp, HP, Dell, VMware, are among the users of the API and other tools I developed for their products, internal IT orchestration, and test automation.