Here is a look at some of these features found in the vSphere 4.0 SDK stubs:
Features known:
| API STRING | FEATURE |
|---|---|
| vim.version.drs | Distributed Resource Scheduler |
| vim.version.dvs | Distributed Virtual Switch |
| vim.version.ft | Fault Tolerance |
| vim.version.ipv6 | IPv6 |
Features eventually known:
| API STRING | FEATURE |
|---|---|
| vim.version.iorm | I/O Resource Management what is now known as Storage I/O Control or SIOC |
Features unknown:
| API STRING | FEATURE |
|---|---|
| vim.version.fed | Unknown - (Federation?) |
| vim.version.lc | Unknown - (Related properties in API referenced Linked Clones) |
| vim.version.logan | Unknown - (Related properties in API referenced MediaAnalysisManager |
| vim.version.policy | Unknown - (Rrelated properties in API referenced PolicyManager |
| vim.version.svm | Unknown - (Rrelated properties in API referenced svmVmxDiskCopy) |
| vim.version.uber | Unknown |
Now, looking at vSphere 4.1 SDK stubs, I noticed a slew of new "potential" features that VMware is or maybe working on:
vim.version.cvp - ?unknown? (Client Virtualization Platform? below are properties and methods associated with this feature)
- SetDisplayTopologyModes
- VirtualMachinePowerPolicyPowerMode
- VirtualMachinePowerPolicyCpuMode
- requestedReplicationCanBeDeferred
- userAllowedToDeferReplication
- policyCacheLifetime
- DiscoverFcoeHbas
- FcoeConfigFcoeSpecification
- removeFcoeHba
- userAllowedToDeferReplication
- InternalPropertyProviderManager
- hostBasedReplicationSupported
- ClusterVmComponentProtectionSettings
- ClusterVmComponentProtectionSettingsFtVmReaction
Here is an example of executing discoverFcoeHbas method via the MOB which is part of the Host's StorageSystem:
I am no fortune teller, but I suspect we may see some of these features much sooner than later ;)

vim.version.uber - Pretty sure this feature will open up hole in space time to allow for LAN-like VMotion across continents.
ReplyDeleteHost Based Replication is part of SRM.next (5?), they talked about this at VMworld, it will reduce the dependency on strict SAN -> SAN replication for SRM, among other things.
ReplyDelete