Step 2 - Once ESXi is up and running, you will need to minimally configure networking along with an FQDN (ensure proper DNS resolution), NTP and specify which SSD should be used for the vSAN capacity drive. Step 1 - Boot up the ESXi installer from USB and then perform a standard ESXi installation using the same USB device that it was booted up from Note: While my experiment used an Intel NUC, any system that meets the basic requirements above should also work. Ability to deploy and run the VMware Cloud Builder (CB) Appliance in a separate environment (ESXi/Fusion/Workstation).ESXi 7.0 Update 3g installed on the Intel NUC using USB device.2 x SSD that are empty for use for vSAN bootstrap (500GB+ for capacity).Dual onboard networking ("Tall" NUC like Intel NUC 11 Pro, which is what I had used), no USB NICs.VMware Cloud Builder 4.5 OVA (Build 20612863).While you can deploy a basic VCF Management Domain running on a single Intel NUC, if your intention is to get the full benefit and power out of the VCF solution, you will definitely need more resources and ideally additional ESXi hosts, especially if you want to deploy a VCF Workload Domain and the management components will not fit onto a single Intel NUC.ĭisclaimer: This is not officially supported by VMware, use at your own risk.
Sounds crazy, right? I thought so too until I realized it was actually possible! To conclude this week, I thought it would be a fun experiment to see if I could leverage all the tricks that I have shared this week ( here, here and here) and push the boundary even further and attempt to deploy a VCF Management Domain running on just a single Intel NUC? As some of you may have noticed, the theme for several of my blog posts this week has been about deploying VMware Cloud Foundation (VCF) in a homelab environment.
0 kommentar(er)
