MammaGutt wrote:
Vvol are generally a good idea, but for siloed organisations it may cause the same conflicts as with hyper-converged... Server/virtualisation teams doesn’t always understand storage and with Vvol everything is controlled from vCenter and storage teams will have limited access/visability.
Also I still think there are some storage feature available on 3pars (and other systems) which are still not available with Vvol because the storage systems doesn’t control the volumes.
Well this particular storage admin is now also a VMware admin (taking over from the inside)
I'd been keen to know of any pitfalls of VVols, going to be trailing them in a test bed once I get back to NZ and get the firewalls/routing between the 3PAR and vCenter sorted out.
I do know that 3.2.2 code exposes less 3PAR features for use by vCenter (just basic creation and snapshots I think), but 3.3.1 also gives control of replication. In time it should just get better as HPE and VMware sort the code out.