Compatibility with VIM version 2
Status: Alpha
Brought to you by:
alexdavidson
Menu
▾
▴
Logged In: YES
user_id=93952
Originator: NO
Are you guys working on this task? News out of VMworld this week is that VMWare's getting serious about Powershell and they're gonna have their own cmdlets and such. See halr9000.com
Logged In: YES
user_id=1830845
Originator: YES
This is definitely on the list, and some of the groundwork is there. Unfortunately, we don't have any VI3 licences to work against...
So it's on hold until such time as the company needs to upgrade to VI3, because I don't trust my grasp of the documentation enough to code it blind :P
Logged In: YES
user_id=1830845
Originator: YES
Addendum:
This project is being developed as we need bits of it. Managed.VIM is a programming API for use by VirtualCloud rather than a PowerShell tool, although we do use it as such. Right now it's justifying its development by letting us prototype some of the simpler parts of VirtualCloud with PowerShell, but I expect we'd use VMware's API if it works with VIM 1.4.
The thought occurs that we already have the ability to wrap up a PowerShell script and pass it to VirtualCloud as a Job. It'd certainly be nice to allow all the Job and Resource objects in VirtualCloud to be specified as PowerShell scriptblocks and offload all that interop onto VMware's PowerShell API, but I suspect it'd involve a hefty rewrite (again). Worth thinking about, definitely.
Logged In: YES
user_id=1830845
Originator: YES
VirtualCloud itself is getting hacked right back to basics, with no builtin resource handling. So it's even more likely that we'll end up leaving the interop to Powershell when/if we migrate to ESX.
At present, it can be assumed that Managed.VIM will not have VIM v2 support, but this decision MAY change in future.