Following up on my last post on Limiting disk i/o in vSphere we will now see how to automate this. First off we need some way to identify what limit a specific disk should have. You can do this in multiple ways, you could use an external source, you can use Tags or as we've done, Storage Policies. All our VMs and VMDKs …

As a Service provider we need to have some way of limiting individual VMs from utilizing too much of our shared resources. When it comes to CPU and Memory this is rarely an issue as we try to not over-committing these resources, at least not the Memory. For CPU we closely monitor counters like CPU Ready and Latency to …

In a previous post I've talked about issues in the StoragePolicy and Tag cmdlets in PowerCLI. I found a workaround by ignoring certificate warnings and setting my date format to en-US. Today I tried to replicate some Storage Policies from one vCenter to another and I found that I got new errors... I can export the …

We are using Storage Policies on all VMs in our environment and rely on those to give the VM's the correct storage. Storage Policy based management is a key area for VMware going forward it seems, especially with things like vSAN and VVOL. In addition to matching a VM and it's storage we are using the policies to set …