- Create 3 or more nested hosts with at least 6GB RAM (add more for your VMs).
- Setup a separate VMK that you will tag for VSAN traffic. I set these on a separate NIC and subnet, in a vSS with no uplink, using VMXNET3 interfaces (10GB) to separate from the 1GB where i'm running management and VM traffic. Don't forget to set promiscuous mode on the switch so everyone can ping each other.
- Add an SSD disk, and a capacity disk (in the case of hybrid). I found that my nested host picked up the type automatically, but I'm pretty sure you can "tag" the device as SSD or HD from the interface as needed, in case you want to test all flash.
- Create a cluster, move 3 or more hosts in
- Enable VSAN, which will take you through the wizard that enables VSAN.
That's really it. You will see a new vsanDatastore datastore that is shared among all hosts. You can rename this datastore. There's a performance service and a health service you can check. If you did everything well, you will pass all tests except the HCL, for obvious reasons.
Very important - when putting a host in maintenance mode, always do it from the webclient. There are new options that VSAN exposes in a drop down!