I work at a datacenter in St. Louis and we do quite a bit of vmWare virtualization. We prefer to run almost everything we can virtual because of all the management benefits. We have a very robust vmWare 'cloud' (redundant hosts, storage, network, etc). All in all it's about a $15M cluster of stuff.
One of our customers is deploying a new video storage server. It's not processing vids, just storing them. Most of the vids are 4GB+ in size. They are deploying a machine with 6x2TB drives to store everything. Normally, we suggest installing vmWare first (just the freebie ESXi for most situations), and then deploying your server as a vm on top of that virtualization layer.
The customer didn't want to go virtual though, and replied with this reasoning. I actually see his point, but it doesn't carry as much weight with me as compared to the advantages of working in a virtual environment. I'd personally just throw more disk space at the project if it meant going virtual would eat up more inodes than normal.
One of our customers is deploying a new video storage server. It's not processing vids, just storing them. Most of the vids are 4GB+ in size. They are deploying a machine with 6x2TB drives to store everything. Normally, we suggest installing vmWare first (just the freebie ESXi for most situations), and then deploying your server as a vm on top of that virtualization layer.
The customer didn't want to go virtual though, and replied with this reasoning. I actually see his point, but it doesn't carry as much weight with me as compared to the advantages of working in a virtual environment. I'd personally just throw more disk space at the project if it meant going virtual would eat up more inodes than normal.
