VMware

tos2k

tos2k's Profile

  • Name: stf 
  • Email: stefan[o]tomato.no
  • Member Since: May 11, 2007
  • Last Logged In: Nov 17, 2009 4:03 AM
  • Status Level: Expert Expert (901 points)
  • Location: Norway

tos2k's Latest Content


I possibly got a clue on the VMway, within the last few months.

VMware published the VI Client Plugin Guide http://www.vmware.com/support/developer/vc-sdk/vcplugin-exp/vcplugin_technote_exp.pdf butit basically gives access to the VI Clients interface, not to the data ( http://communities.vmware.com/message/974914#974914 ). This is annoying, as reading data from the VC webservice is often very slow. I think that the API did not open for data access, as a plugin can not completely trust in the data shown in the VI client... possibly VMware doesnt want a too tight plugin integration!?

Then, VMware published the Disk SDK http://www.vmware.com/support/developer/vddk/ , but of course it is not so easy to access the vmdk files. Especially considering ESXi servers, i really think that VMware will include this in the VI Client, as they will do with SVMotion...

In Addition, talking VMway, I am wainting now for more then two months (!) on an specific answer according this issue: http://communities.vmware.com/thread/140735?tstart=0

This is absolutely unaccaptable: In these two months, VMware got all requested files: logs, code, descriptions, support forms. And what got I? I wrong answer (not a bug) where the did not really understood my SR, the code and all descriptions that has been sent. After explaining to them that copy a virtual disk file for powered on VM running on a snapshot may not result in the same as a VM not being on a snapshot, the just priorized the priority down to the bottom and kept me waiting. Uh.

Lets see whats coming next.

Tos2k

0 Comments Permalink

Nothing new in Tos2k - Blog

Posted by tos2k Mar 14, 2008 0 Comments


Its been quite the past weeks in the VimSdk world. I converted my app to be VC2.5 compatible only. To do so, basically VimService.dll and VimService.XmlSerializers.dll has to replaced by their VC2.5 compatible equivalents. Finally you add "using VimApi;" to each class (.NET, C#) to get it up and running. Possible issues may come up - resolve it manually then ;-)

The most important change in theVimSdk world may have been the possibility to create plugins for VC. Thanks to Andrew Kutz for this, get more info on

http://www.lostcreations.com/viplugins/viplugins

Tos2k

0 Comments Permalink

The VMway in Tos2k - Blog

Posted by tos2k Jan 23, 2008 1 Comments

Okay, I really like the virtual stuff, VMware. But there are a few things that really could be improved:

  • Better documentation of the VimSdk .NET (predefine constants, add more info about methods, classes)


Although VMTN is great it doesn't necessarily come up in Product
Feature reviews when VMware looks at SDK "next" nor is VMware
required to respond.


  • The structure of VI and its traversal via VimSdk should be redesigned, completely

But what really matters is, it works (finally) and is stable ;-)


Tos2k

1 Comments Permalink

Write your own drafts, invite selected collaborators, or leave it open for all to pitch in.

Communities