<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>stumpr Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>stumpr Tracker</description>
    <pubDate>Sun, 12 Nov 2023 00:46:33 GMT</pubDate>
    <dc:date>2023-11-12T00:46:33Z</dc:date>
    <item>
      <title>Re: Perl SDK 6.5 and Vsphere</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Perl-SDK-6-5-and-Vsphere/m-p/959700#M930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, the tags are exposed via the rest api, so you could probably use w/e version you wanted. Just need to construct the rest request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the SDKs are backwards compatible.&amp;nbsp; So if you use 6.5, you can target a 6.0 vCenter no issues.&amp;nbsp; Just don't try to access any new 6.5 features against 6.0.&amp;nbsp; You can use a version check if you need to do so across multiple versions of vCenter.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Feb 2017 14:52:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Perl-SDK-6-5-and-Vsphere/m-p/959700#M930</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2017-02-28T14:52:59Z</dc:date>
    </item>
    <item>
      <title>Re: Simple Perl code to get VM parent host</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Simple-Perl-code-to-get-VM-parent-host/m-p/1387519#M1488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have a MOREF from the runtime.host property, you need another get_view call on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;my $host = Vim::get_view(mo_ref =&amp;gt; $HostRef);&lt;/P&gt;
&lt;P&gt;print $host-&amp;gt;{name} . "\n";&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Feb 2017 22:31:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Simple-Perl-code-to-get-VM-parent-host/m-p/1387519#M1488</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2017-02-15T22:31:07Z</dc:date>
    </item>
    <item>
      <title>Re: Retrieve vCenter instance name</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/Retrieve-vCenter-instance-name/m-p/1405874#M7183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You'll need to login.&amp;nbsp; If you are logging in, you also need permissions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12px;"&gt;This method might require any of the following privileges depending on where the property fits in the inventory tree.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;System.View on the root folder, if this is used to read settings in the "client" subtree.&lt;/LI&gt;
&lt;LI&gt;System.Read on the root folder, if this is used to read all settings or any settings beside those in the "client" subtree.&lt;/LI&gt;
&lt;LI&gt;System.Read on the host, if this is used to read the advanced options for a host configuration.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Feb 2016 11:00:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/Retrieve-vCenter-instance-name/m-p/1405874#M7183</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2016-02-16T11:00:47Z</dc:date>
    </item>
    <item>
      <title>Re: Retrieve vCenter instance name</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/Retrieve-vCenter-instance-name/m-p/1405872#M7181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You'll want the OptionManager object on the ServiceInstance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ServiceInstance -&amp;gt; setting ['&lt;SPAN style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12px;"&gt;VirtualCenter.InstanceName&lt;/SPAN&gt;']&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Feb 2016 15:30:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/Retrieve-vCenter-instance-name/m-p/1405872#M7181</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2016-02-15T15:30:51Z</dc:date>
    </item>
    <item>
      <title>Re: C# application using vSphere SDK 5.5 fails to retrieve VM's data from VMware ESXi 4</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/C-application-using-vSphere-SDK-5-5-fails-to-retrieve-VM-s-data/m-p/1392851#M7166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's probably the property: &lt;STRONG&gt;config.service.service[\"vmware-vpxa\"].running&lt;/STRONG&gt;.&amp;nbsp; You'll need to request &lt;STRONG&gt;config.service&lt;/STRONG&gt; and iterate them yourself to find the key &lt;STRONG&gt;vmware-vpxa&lt;/STRONG&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2015 18:34:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/C-application-using-vSphere-SDK-5-5-fails-to-retrieve-VM-s-data/m-p/1392851#M7166</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-26T18:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: C# application using vSphere SDK 5.5 fails to retrieve VM's data from VMware ESXi 4</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/C-application-using-vSphere-SDK-5-5-fails-to-retrieve-VM-s-data/m-p/1392849#M7164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It all depends on what properties you're requesting.&amp;nbsp; What properties are you requesting for the non-VM objects?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2015 17:58:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/C-application-using-vSphere-SDK-5-5-fails-to-retrieve-VM-s-data/m-p/1392849#M7164</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-26T17:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: C# application using vSphere SDK 5.5 fails to retrieve VM's data from VMware ESXi 4</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/C-application-using-vSphere-SDK-5-5-fails-to-retrieve-VM-s-data/m-p/1392847#M7162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Without digging too deep, you'll get errors if you ask for properties from the property collector that aren't defined in an older version of the SDK.&amp;nbsp; You'll have to write code logic to ask for 4.x properties only, if you ask for properties that weren't added until a later API version, it will error out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2015 13:49:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/C-application-using-vSphere-SDK-5-5-fails-to-retrieve-VM-s-data/m-p/1392847#M7162</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-26T13:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: Modify vApp Options from an existing vm</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Modify-vApp-Options-from-an-existing-vm/m-p/2655604#M2689</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The example you linked is calling into vCloud Director -- I think (I generally work in *nix so PowerCLI isn't on my usual toolset).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe you'll want to go to &lt;STRONG&gt;UpdateVAppConfig() &lt;/STRONG&gt;in vSphere.&amp;nbsp; If you look at the &lt;STRONG&gt;VAppConfigSpec&lt;/STRONG&gt; object, you'll probably want to modify &lt;STRONG&gt;property&lt;/STRONG&gt; or &lt;STRONG&gt;ovfSection&lt;/STRONG&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2015 13:47:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Modify-vApp-Options-from-an-existing-vm/m-p/2655604#M2689</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-26T13:47:18Z</dc:date>
    </item>
    <item>
      <title>Re: VimException Timeout, Session no longer exist</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/VimException-Timeout-Session-no-longer-exist/m-p/1318171#M6904</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Generally you'd want to use SessionIsActive() on SessionManager, or I *think* CurrentTime() on the ServiceInstance object may do it as well.&amp;nbsp; Some of the property collector calls don't actually trigger a session anti-idle, but SessionIsActive() usually will (I think).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is also a socket timeout, to prevent sockets from getting flooded out.&amp;nbsp; But any traffic to that socket will keep those from idling out (usually only a problem if you're process is sleeping for long periods of time).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Oct 2015 17:55:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/VimException-Timeout-Session-no-longer-exist/m-p/1318171#M6904</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-23T17:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to fetch Data Objects properties such as vDS port state in a similar way to the propertyCollector for the Managed Objects</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/Is-there-a-way-to-fetch-Data-Objects-properties-such-as-vDS-port/m-p/468796#M2198</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I generally haven't seen much of a gain in parallel queries.&amp;nbsp; Usually it's just a DB lookup on the backend and the data transfer (at least for what you're working on) shouldn't be that large.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Criteria isn't deprecated, it's the scope parameter.&amp;nbsp; And that's likely to be around for a long time.&amp;nbsp; Most of the deprecated properties are still available from 2.5 for example.&amp;nbsp; I think the official statement is deprecated is guaranteed for at least 2 releases?&amp;nbsp; But I'm not sure if that's still true (working on old statement).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Oct 2015 14:03:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/Is-there-a-way-to-fetch-Data-Objects-properties-such-as-vDS-port/m-p/468796#M2198</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-21T14:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to fetch Data Objects properties such as vDS port state in a similar way to the propertyCollector for the Managed Objects</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/Is-there-a-way-to-fetch-Data-Objects-properties-such-as-vDS-port/m-p/468794#M2196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You won't be able to do so for the data objects, but FetchDVPorts does support criteria.&amp;nbsp; Assuming you have something besides *all* that you care about, that should be more efficient?&amp;nbsp; Are you seeing extremely slow queries for that data?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Oct 2015 13:37:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/Is-there-a-way-to-fetch-Data-Objects-properties-such-as-vDS-port/m-p/468794#M2196</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-21T13:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: How do i programtically create a tag category via VIJAVA or vSphere SDK?</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/How-do-i-programtically-create-a-tag-category-via-VIJAVA-or/m-p/1321625#M6929</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I didn't spend enough time on it, just did a few SSL packet captures.&amp;nbsp; It's basically the SOAP API, just they seem to embed some XPATH operations for the tag management inside the content.&amp;nbsp; I honestly recommend just not using vSphere Tags, unless you're really bumping into functionality instead of metadata tagging.&amp;nbsp; You can get the same result with custom values for the most part when looking to just do tag lookups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's been something we've raised as an issue several times to the PMs, but it hasn't gotten any traction outside of the vSphere 6.0 REST API (so only PowerCLI support pre-6.0).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Oct 2015 13:31:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/How-do-i-programtically-create-a-tag-category-via-VIJAVA-or/m-p/1321625#M6929</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-21T13:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI vs Perl SDK</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/PowerCLI-vs-Perl-SDK/m-p/2274615#M2363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah, probably have to hop through the host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_macro_code jive_text_macro _jivemacro_uid_14448634854372099" jivemacro_uid="_14448634854372099" modifiedtitle="true"&gt;
&lt;P&gt;my $vm_name = "test_vm_template";&lt;/P&gt;
&lt;P&gt;my $vm = Vim::find_entity_view(view_type =&amp;gt; 'VirtualMachine', filter =&amp;gt; { 'name' =&amp;gt; $vm_name });&lt;/P&gt;
&lt;P&gt;my $host_ref = $vm-&amp;gt;{'runtime'}{'host'};&lt;/P&gt;
&lt;P&gt;my $host = Vim::get_view(mo_ref =&amp;gt; $host_ref, properties =&amp;gt; ['name', 'parent']);&lt;/P&gt;
&lt;P&gt;my $compute = Vim::get_view(mo_ref =&amp;gt; $host-&amp;gt;{'parent'}, properties =&amp;gt; ['name', 'resourcePool']);&lt;/P&gt;
&lt;P&gt;my $pool = Vim::get_view(mo_ref =&amp;gt; $compute-&amp;gt;{'resourcePool'}, properties =&amp;gt; ['name']);&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;# Now use $pool as parameter to MarkAsVirtualMachine&lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm doing this completely from the SDK doc, so I'm sure there are typos.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Oct 2015 23:11:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/PowerCLI-vs-Perl-SDK/m-p/2274615#M2363</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-14T23:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI vs Perl SDK</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/PowerCLI-vs-Perl-SDK/m-p/2274612#M2360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So even without any ResourcePools in our vSphere Client UI, there are some default resource pool entities.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can get it from your virtual machine object with the property 'resourcePool'.&amp;nbsp; That's most likely what the PowerCLI cmdlet is doing, just using the same resource pool the template is current in (template and virtual machines are the same object, it's just a boolean flag).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, from Perl, assuming you got the resourcePool property from your get_view or find_entity_view calls:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;$pool_moref = $vm-&amp;gt;{'resourcePool'};&lt;/P&gt;
&lt;P&gt;$pool = Vim::get_view(mo_ref =&amp;gt; $pool_moref);&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;# ...&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Oct 2015 18:30:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/PowerCLI-vs-Perl-SDK/m-p/2274612#M2360</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-10-14T18:30:52Z</dc:date>
    </item>
    <item>
      <title>Re: Run Commands in Guest OS</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Run-Commands-in-Guest-OS/m-p/2703984#M2828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would probably recommend looking at some tooling like Ansible as your first pass at this, the assumption being you may want to do more complicated in-guest operations and potentially stage into some configuration management activity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if are looking to leverage the out-of-band connectivity of the vSphere GuestOperations API (VIX), then you really don't have too many choices. &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;lamw&lt;/B&gt;‌ actually wrote an example of using the GuestOperations API.&amp;nbsp;&amp;nbsp; &lt;A href="http://www.virtuallyghetto.com/2011/07/automating-new-integrated-vixguest.html"&gt;http://www.virtuallyghetto.com/2011/07/automating-new-integrated-vixguest.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Sep 2015 22:40:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Run-Commands-in-Guest-OS/m-p/2703984#M2828</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-09-22T22:40:24Z</dc:date>
    </item>
    <item>
      <title>Re: how to get the uuid of the virtual machine that got deleted from the VM Deleted event</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/how-to-get-the-uuid-of-the-virtual-machine-that-got-deleted-from/m-p/2688353#M14397</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, it's deleted.&amp;nbsp; You won't be able to get the UUID unless you saved it prior to the delete.&amp;nbsp; I don't think that UUID information is packed into the data of the delete event, unfortunately.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Sep 2015 18:32:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/how-to-get-the-uuid-of-the-virtual-machine-that-got-deleted-from/m-p/2688353#M14397</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-09-09T18:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: retrieve datacenter name in vsphere SDK 6.0</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/retrieve-datacenter-name-in-vsphere-SDK-6-0/m-p/2682619#M14383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which part throws a null pointer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's nothing that changed (unless there is a bug in the dotNET version of the SDK) that would impact looking at the first level parent.&amp;nbsp; However, you may have nested folders (not sure if getParent is recursive).&amp;nbsp; Still, I'd expect parent to be the first parent, regardless of type based on what you shown below.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Sep 2015 12:49:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/retrieve-datacenter-name-in-vsphere-SDK-6-0/m-p/2682619#M14383</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-09-03T12:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: getting esxi information from vm</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/getting-esxi-information-from-vm/m-p/2672328#M14340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You'll need some identifier from the GuestOS (HW UUID, IP Address).&amp;nbsp; Then you can query for that VM in the vCenter API.&amp;nbsp; Once you have the VM, you can get the current HostSystem of that VM from *runtime.host*.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Sep 2015 11:31:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/getting-esxi-information-from-vm/m-p/2672328#M14340</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-09-02T11:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: The object has already been deleted or has not been completely created</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/The-object-has-already-been-deleted-or-has-not-been-completely/m-p/1328308#M1420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you mean that you have two processes both deleting the same datastore?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally I'd do a Try::Tiny or eval { } block around the call to capture things like that and avoid a runtime error.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Aug 2015 12:49:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/The-object-has-already-been-deleted-or-has-not-been-completely/m-p/1328308#M1420</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-08-18T12:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Management SDK url is just blank page</title>
      <link>https://communities.vmware.com/t5/vSphere-Management-SDK/vSphere-Management-SDK-url-is-just-blank-page/m-p/984523#M4671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As &lt;A _jive_internal="true" href="https://communities.vmware.com/people/rcporto"&gt;Richardson Porto&lt;/A&gt; pointed out,&lt;STRONG&gt; /sdk&lt;/STRONG&gt; is the SOAP endpoint.&amp;nbsp; There is also web-ui oriented interface called the mob at &lt;STRONG&gt;/mob&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Overall the API documentation is generic to any of the SDK kits (Python, Perl, dotNet, Java, etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Python, you'll probably want to use pyvmomi: &lt;A href="https://github.com/vmware/pyvmomi" title="https://github.com/vmware/pyvmomi"&gt;https://github.com/vmware/pyvmomi&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You'll have to know the utility functions for each SDK (they vary) and there are some quirks between how you instantiate the API objects.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jul 2015 15:14:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Management-SDK/vSphere-Management-SDK-url-is-just-blank-page/m-p/984523#M4671</guid>
      <dc:creator>stumpr</dc:creator>
      <dc:date>2015-07-17T15:14:33Z</dc:date>
    </item>
  </channel>
</rss>

