In a typical over provisioned system (you can think of any folder-based filesystem as being this way too) you have many VMs, not just one or two. Once you have, say, a dozen it is trivial to over provision safely. You do this by a few means:
Reporting and alerting so that systems growing rapidly are addressed. Maintaining caps that are large enough for flexibility but small enough so that if X VMs spiral out of control it will not be an issue. The X factor here is to be determined based on your risk and risk aversion. If you have, say, a dozen VMs, you might have the cap set so that ten VMs could expand to maximum but not all twelve. If any two VMs don't have an issue, you would be all set. Or maybe you'd set it for six. You don't overprovision to where any VM could use the entire space, it just doesn't make sense.-
2 Votes31 Posts4k Views
-
5 Votes10 Posts1k Views
-
1 Votes7 Posts2k Views
-
0 Votes8 Posts743 Views
-
1 Votes9 Posts2k Views
-
1 Votes6 Posts1k Views
-
1 Votes48 Posts10k Views
-
1 Votes11 Posts2k Views
-
2 Votes2 Posts1k Views
-
2 Votes31 Posts6k Views
-
0 Votes4 Posts1k Views
-
What To Do when RAID Has a Hard Drive Failure
Watching Ignoring Scheduled Pinned Locked Moved raid best practices general it knowledge storage hard drive how to4 Votes15 Posts7k Views -
2 Votes3 Posts1k Views
-
4 Votes23 Posts4k Views
-
1 Votes18 Posts3k Views
-
1 Votes7 Posts10 Views
-
1 Votes58 Posts11k Views
-
0 Votes40 Posts8k Views
-
Windows Server 2016 TP4 on Scale HC3 HC2000 Test
Watching Ignoring Scheduled Pinned Locked Moved scale hc3 windows server 2016 ntg lab windows server9 Votes26 Posts5k Views -
1 Votes11 Posts2k Views