<?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>topic Provisioning virtual NVDIMM with Perl SDK in vSphere SDK for Perl Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455769#M439</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone!&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I am trying to provision a virtual NVDIMM device using the Perl SDK. Specifically how the default storage policy for the PMEM datastore backing the device is determined / used.&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I actually have been able to provision the virtual NVDIMM using a storage policy ID I&amp;nbsp; have determined with a REST call against the vSphere RESTful API service. But that requires a vCenter server and I was hoping to run this script against standalone hosts as well.&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I was hoping some folks here might have some examples of provisioning a virtual NVDIMM device using the Perl SDK&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Mar 2019 16:46:59 GMT</pubDate>
    <dc:creator>GoodBrew</dc:creator>
    <dc:date>2019-03-07T16:46:59Z</dc:date>
    <item>
      <title>Provisioning virtual NVDIMM with Perl SDK</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455769#M439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone!&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I am trying to provision a virtual NVDIMM device using the Perl SDK. Specifically how the default storage policy for the PMEM datastore backing the device is determined / used.&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I actually have been able to provision the virtual NVDIMM using a storage policy ID I&amp;nbsp; have determined with a REST call against the vSphere RESTful API service. But that requires a vCenter server and I was hoping to run this script against standalone hosts as well.&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I was hoping some folks here might have some examples of provisioning a virtual NVDIMM device using the Perl SDK&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2019 16:46:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455769#M439</guid>
      <dc:creator>GoodBrew</dc:creator>
      <dc:date>2019-03-07T16:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: Provisioning virtual NVDIMM with Perl SDK</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455770#M440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;B&gt;GoodBrew&lt;/B&gt; I am trying to do the same thing, but using the rbvmomi api.&amp;nbsp; Can you share what you were able to do. We do have vCenter server.&amp;nbsp; I think I am using correct storage profile, but something in how I am calling ReconfigVM_Task is not working right, so I suspect I am creating the storage profile incorrectly!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jul 2019 16:52:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455770#M440</guid>
      <dc:creator>amy_reed</dc:creator>
      <dc:date>2019-07-22T16:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: Provisioning virtual NVDIMM with Perl SDK</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455771#M441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We ended up automating an API call to the vCenter Server's RESTful API server to get the datastore policy ID. We used this endpoint:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; GET &amp;lt;vcenter-server&amp;gt;/vcenter/datastore/&amp;lt;datastore-moid&amp;gt;/default-policy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once we had the policy ID, we constructed a VirtualMachineConfigSpec object like this to pass to reconfigure_vm task:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;# make the nvdimm_backing object&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;# We had to pass an empty string as a fileName value for some reason...&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;nvdimm_backing = VirtualNVDIMMBackingInfo(fileName = "")&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;# make the nvdimm device object&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;nvdimm_dev = VirtualNVDIMM(capacityInMB = &amp;lt;some_size&amp;gt;, backing=nvdimm_backing, controllerKey=&amp;lt;your-nvdimm-controller&amp;gt;)&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;# some other values we needed to fill out&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;op = VirtualDeviceConfigSpecOperation("add")&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;fileOp = VirtualDeviceConfigSpecFileOperation("create")&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;nvdimm_profile = new VirtualMachineDefinedProfileSpec(profileId = &amp;lt;the policy ID you got from the vcenter&amp;gt;)&amp;nbsp; # this is where we insert the policy ID&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;# combine it all together for the VirtualDeviceConfigSpec:&lt;BR /&gt;vnvdimm_spec = VirtualDeviceConfigSpec(profile=[ nvdimm_profile ], device=nvdimm_dev , fileOperation=fileOp, operation=fileOp)&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;# then roll that into the VirtualMachineConfigSpec and reconfigure the VM&lt;/CODE&gt;&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;config_spec = VirtualMachineConfigSpec([deviceChange = &lt;SPAN style="font-family: monospace;"&gt;vnvdimm_spec]&lt;/SPAN&gt;&lt;/CODE&gt;)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jul 2019 17:40:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455771#M441</guid>
      <dc:creator>GoodBrew</dc:creator>
      <dc:date>2019-07-22T17:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: Provisioning virtual NVDIMM with Perl SDK</title>
      <link>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455772#M442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@GoodBrew&lt;/P&gt;&lt;P&gt;Thanks so much!&amp;nbsp; That worked!&amp;nbsp; I had the correct profile ID, it was the filename in the nvdimm backing info that was giving me trouble. Passing the empty string worked wonderfully. Appreciate your help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jul 2019 18:45:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-SDK-for-Perl-Discussions/Provisioning-virtual-NVDIMM-with-Perl-SDK/m-p/455772#M442</guid>
      <dc:creator>amy_reed</dc:creator>
      <dc:date>2019-07-22T18:45:19Z</dc:date>
    </item>
  </channel>
</rss>

