From my experience so far with VCF9, many customers are thinking about VCF9 as the next step in the series. They already have vSphere in an earlier version (Hopefully 8 already, as 7 is out of support). Many are continuing to use VCF9 as if it was just a normal vSphere system. This is not the case. VCF9 is a complete private cloud solution. It comes with many products built in and is intended to offer customers an On-Premise alternative to public cloud.
For this reason, I decided to write a series to show how you can go from a traditional vSphere mindset and adopt this amazing solution from VMware.
This set of posts is to simulate a customer who has an existing environment that consists a site with 2 hosts. The primary site is vSphere 8, the vSAN witness node is placed on the primary site. DNS and NTP servers are also presented from the first site.
In the scenario, customer decided to update to version 9 of ESX and vCenter to test the upgrade path to VCF 9 instead of deploying the site from fresh with the VCF Installer (SDDC Manager). Part of the reason for this is that the customer does not want to spend extra money on 4 hosts for a management domain.
Currently the solution is not a VCF solution because at the time of installation the customer updated his solution
If you are interested in the setup of the single node vSAN, you can find the setup of that here.