To get the full benefits and support of the new vmware.com/blog/introduction-vsan-express-storage-architecture" target="_blank" rel="noopener" style="box-sizing: border-box; background: 0px center; transition: all 0.2s ease-in-out 0s; color: rgb(0, 0, 0); text-decoration-line: none; border-bottom: 1px solid rgb(0, 51, 102); font-weight: 700; padding-bottom: 1px; border-top-color: rgb(0, 51, 102); border-right-color: rgb(0, 51, 102); border-left-color: rgb(0, 51, 102);">vSAN 8 Express Storage Architecture (ESA), you will need modern hardware from the official vSAN ESA Ready Node HCL. However, from an education and learning point of view, you may want to explore some of the VSAN ESA workflows and easiest way to do that, well you probably know the answer .... it is using Nested ESXi of course! With my recently published vSphere and vSAN 8 Lab Deployment Script, you can use that as the base and the Nested ESXi 8.0 IA Virtual Appliance to setup vSAN 8 ESA using virtual hardware Enabling vSAN 8 Express Storage Architecture (ESA) using Nested ESXi
Once you reach the end of the wizard, you will be presented with a summary and enablement of vSAN ESA will begin.
Again, this is purely for educational and learning purposes, especially in familiarizing yourself with the vSAN ESA enablement workflow. Outside of the initial workflow, I am not sure there will be any real benefits of using vSAN ESA in a Nested ESXi environment, especially compared to the vSAN Original Storage Architecture (OSA) which can be enabled with just 8GB of memory per host versus the 16GB required by vSAN ESA.More from my site
Comments
says
This is actually due to parsing of the hardware after the HCL DB has been downloaded. While the error is a bit miss-leading, it was an issue I had ran into with one of my env and after filing a bug, it looks like this will be resolved in the upcoming 8.0 Update 1 release.
微信支付宝扫一扫，打赏作者吧～
官码2024000195号
萌ICP备20248119号
You don’t need to mess w/checksum. Convert from OVA->OVF and delete the .mf file. Make your change and convert back to OVA or just use OVF+VMDK as-is
Alaa - I've not forgotten about this thread and still trying to get an answer. The official response I've gotten thus far is that VSAN ESA requires minimum of 512GB for proper supported configuration and anything less than that is YMMV and not supported. It sounds like you were able to confirm that simply updating ESXi VM memory from 16GB->18GB allowed you to configure VSAN ESA w/o messing with heap memory?