<?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 Re: New TR Released: TR-4698-DEPLOY NetApp ONTAP Deploy on Intel NUC in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/New-TR-Released-TR-4698-DEPLOY-NetApp-ONTAP-Deploy-on-Intel-NUC/m-p/156506#M35331</link>
    <description>&lt;P&gt;Could you share a link to the wordpress article? I'm curious why it says "300gb+" disk space - that's not a requirement for either Deploy or Select.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FYI - This post (TR) is about running &lt;STRONG&gt;Deploy&lt;/STRONG&gt; on a NUC - not an actual ONTAP Select cluster. Requirements for Deploy are much lower (2 CPUs, 4GB Memory, 40Gb storage) - I run mine on a CentOS / KVM NUC setup (no OpenVswitch).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;virt-install --name=deploy --vcpus=2 --ram=4096 --os-type=linux --os-variant=generic --controller=scsi,model=virtio-scsi --disk path=/home/deploy/ONTAPdeploy.raw,device=disk,bus=scsi,format=raw --network "type=bridge,source=br1,model=virtio" --console=pty --import --wait 0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A Select cluster has much more restrictive requirements and Deploy will verify much of it (ie. host, CPUs, avail. memory, storage space) - but never know what you might squeeze it into&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":beaming_face_with_smiling_eyes:"&gt;😁&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 May 2020 16:50:17 GMT</pubDate>
    <dc:creator>JohnChampion</dc:creator>
    <dc:date>2020-05-26T16:50:17Z</dc:date>
    <item>
      <title>New TR Released: TR-4698-DEPLOY NetApp ONTAP Deploy on Intel NUC</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/New-TR-Released-TR-4698-DEPLOY-NetApp-ONTAP-Deploy-on-Intel-NUC/m-p/141097#M31208</link>
      <description>&lt;P&gt;This document shows how to install Select Deploy on an Intel NUC to create a small form-factor Select Deploy appliance.&lt;BR /&gt;&lt;BR /&gt;ONTAP Select Deploy is an essential tool used to create and monitor ONTAP Select clusters. Additionally, it provides a mediator service that enables high availability for two-node Select clusters. Deploy is provided as a virtual machine (VM) that runs on either the VMware ESXi or KVM hypervisors. In certain small-form-factor deployments, the hosts used forSelect do not have enough resources to run both a Select node and a Deploy VM.In those instances, an Intel NUC can be used to run Deploy as a low-cost, small-form-factor standalone appliance.&lt;BR /&gt;&lt;BR /&gt;For more info, please click &lt;A href="https://www.netapp.com/us/media/tr-4698-deploy.pdf" target="_self"&gt;here&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 24 Jun 2018 23:35:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/New-TR-Released-TR-4698-DEPLOY-NetApp-ONTAP-Deploy-on-Intel-NUC/m-p/141097#M31208</guid>
      <dc:creator>hariprak</dc:creator>
      <dc:date>2018-06-24T23:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: New TR Released: TR-4698-DEPLOY NetApp ONTAP Deploy on Intel NUC</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/New-TR-Released-TR-4698-DEPLOY-NetApp-ONTAP-Deploy-on-Intel-NUC/m-p/156504#M35330</link>
      <description>&lt;P&gt;Hi...As per a wordpress publishing, the VM requires 4 vCPUs, 16gb of RAM, and 300gb+ of disk space, which is just within reach of a small platform like the intel NUC.&lt;/P&gt;
&lt;P&gt;The datastore really should be a local SSD or NVME based datastore for performance reasons, so I will be deploying it to the internal NVME drive on my NUC. The VM will need about 302GB for a thick provisioned deployment.&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2020 16:03:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/New-TR-Released-TR-4698-DEPLOY-NetApp-ONTAP-Deploy-on-Intel-NUC/m-p/156504#M35330</guid>
      <dc:creator>MarcoHarn</dc:creator>
      <dc:date>2020-05-26T16:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: New TR Released: TR-4698-DEPLOY NetApp ONTAP Deploy on Intel NUC</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/New-TR-Released-TR-4698-DEPLOY-NetApp-ONTAP-Deploy-on-Intel-NUC/m-p/156506#M35331</link>
      <description>&lt;P&gt;Could you share a link to the wordpress article? I'm curious why it says "300gb+" disk space - that's not a requirement for either Deploy or Select.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FYI - This post (TR) is about running &lt;STRONG&gt;Deploy&lt;/STRONG&gt; on a NUC - not an actual ONTAP Select cluster. Requirements for Deploy are much lower (2 CPUs, 4GB Memory, 40Gb storage) - I run mine on a CentOS / KVM NUC setup (no OpenVswitch).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;virt-install --name=deploy --vcpus=2 --ram=4096 --os-type=linux --os-variant=generic --controller=scsi,model=virtio-scsi --disk path=/home/deploy/ONTAPdeploy.raw,device=disk,bus=scsi,format=raw --network "type=bridge,source=br1,model=virtio" --console=pty --import --wait 0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A Select cluster has much more restrictive requirements and Deploy will verify much of it (ie. host, CPUs, avail. memory, storage space) - but never know what you might squeeze it into&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":beaming_face_with_smiling_eyes:"&gt;😁&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2020 16:50:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/New-TR-Released-TR-4698-DEPLOY-NetApp-ONTAP-Deploy-on-Intel-NUC/m-p/156506#M35331</guid>
      <dc:creator>JohnChampion</dc:creator>
      <dc:date>2020-05-26T16:50:17Z</dc:date>
    </item>
  </channel>
</rss>

