Home > vSphere API > Common Mistakes Using VMware VI and vSphere SDK

Common Mistakes Using VMware VI and vSphere SDK

January 31st, 2010 Leave a comment Go to comments

I posted two blogs on the top 10 best practices of using the vSphere SDK (part 1, part 2) two days ago. Here is a list of several common mistakes developers make during their development. It’s based on the stats from our SDK support team.

  1. Defining wrong interval information in PerfQuerySpec
  2. Using same unit number for each device attached to a controller
  3. Mistakes in defining the TraversalSpec
  4. Using case sensitive DNS names or IP address
  5. Wrong customization spec setting for cloning a VM
  6. Mistakes in environment setup

Hope you can avoid them. If you have any mistakes to share with other developers, please feel free to add them in the comments.

Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.

  1. February 1st, 2010 at 01:21 | #1

    I have seen at least 4 out of those 6 in practice already 😉
    Another one that makes me pull my hair regularly, is the case-sensitivity of some enumeration values.
    For example “Community” as a value for the pvLanType gives an error. It should be “community”.

  2. February 1st, 2010 at 21:46 | #2

    That is true. One more reason we should use toolkit over hand code these sensitive strings. Still there are some types meant to be enumeration, but end up as string. So pay more attention to them.
    -Steve

  1. No trackbacks yet.