GUI Based VSAN Bootstrap VCSA Deployment

When deploying my 3 node NUC VSAN lab I got to try out the new bootstrap vcsa gui installer blogged about here…

https://blogs.vmware.com/virtualblocks/2017/04/25/bootstrap-vcsa-with-vsan-easy-install/#respond

Once you download and unpack the VCSA you’ll find a file called installer within the following path %filepath%\vcsa-ui-installer\win32\installer.exe (there’s a MAC & LINUX option too)

You need to have installed ESXi on your target host first, also if your networking is trunked to the ESXi host, make sure you tag the VM port group where the VCSA will reside before deploying.

By default this installer will enable the MGMT VMK for VSAN, this was fine with me as once the VCSA was deployed I retrospectively changed all the VSAN related host settings.

You will also need the VCSA to be resolvable by the DNS server you specify during the setup, I already had a Domain Controller deployed within workstation on my laptop which was routable from my lab network so I used that.

The Gui is relatively straight forward, ensure you select the option to install on a new virtual san cluster.

1

IP the VCSA

2

Select the disks on the host for the approproiate teir, if you want to enable Dedup do it now as the disk group will need to be evaucated to enable dedup and compression at a later date!

3

Do the traditional next next finish and it’ll start deploying. The VCSA deployment is now two step, once this stage is complete you need to log into the VCSA Mgmt page to complete the remainder of the setup.

4

Here is the proof of the pudding; my incredibly annoyingly named disks are now claimed by VSAN

5

The host is also now a member of a VSAN cluster.

6

A single host vsanDatastore

7

You can now complete the configuration through the vCenter

Horizon 6.1 NVIDIA GRID vGPU

VMware Horizon 6.1 now supports NVIDIA GRID vGPU for their virtual desktop users, but before jumping on the rich graphic bandwagon there are some considerations to be made, for instance NVIDIA GRID VGPU doesnt support vMotion or HA because of the direct-path access to the hardware.

in addition to that there is no support for vGPU in a Linux guest as NVidia drivers are not availble

https://gridforums.nvidia.com/default/topic/285/nvidia-grid-drivers/grid-driver-for-ubuntu-and-centos-/

A handy comparison of vSGA, NVDIA GRID vGPU and vDGA is shown below

GRID

Before using the hardware-based (GPU) virtual Shared Graphics Acceleration (vSGA) feature in vSphere, you must install and configure the NVIDIA GPU VIB (vSphere Installation Bundle) on ESXi.

More information can be found here

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033434

I’m sure there will be some use cases for GRID, but I’d imagine the lack of vMotion & HA support will be a deal breaker for most.