apol wrote:
This is something I'm wondering as well. With vvs, there are vv sets and host sets, so from a storage perspective, we still have an idea what's going on and which esx is doing what kinda stuff. Whick ESX belong to the same cluster.
With vVols, should I create one container per cluster (SQL, Linux, Windows, Appliances)? Or just one big container, hand it all over to all the esx (maybe several dozens), and let vCenter do the coordination?
Oh you are so touching my pain point with vVols!
The short answer is that you should create one storage container for each CPG you would historically would do.
For the first part, they answer from the people "selling" vVol is that you don't need to know any of that now because the Vmware admin is in control of that now... if you are both, then good. If you're not, then the first issue will send you on a new and exciting adventure