Sometimes it’s the little things that can make life easier. This post is actually a fork from the one which I originally wrote previously on a DPM issue. Shortly after that post, it was pointed out that I was reading DPM Priority Recommendations incorrectly. Indeed that was the case.
Where did I go wrong? Look at the priority descriptions between DRS and DPM, where both slide bars are configured with the same aggressiveness:
“Apply priority 1, priority 2, priority 3, and priority 4 recommendations”
“Apply priority 4 or higher recommendations”
My brief interpretation was that a higher recommendation meant a higher number (ie. priority 4 is a higher recommendation than priority 3). It’s actually the opposite that is true. A higher recommendation is a lower number.
I believe there is too much left open to interpretation on the DPM screen as to what is higher and what is lower. The DRS configuration makes sense because it’s clear as to what is going to be applied; no definition of high or low to be (mis-)interpreted. The fix? Make the DPM configuration screen mirror DRS configuration screen. Development consistency goes a long way. As a frequent user of the tools, I expect it. I view UI inconsistency as sloppy.
If you are a VMware DPM product manager, please see my previous post VMware DPM Issue.