Red Hat Bugzilla – Bug 1004725
[origin_ui_58] The suggestion did not show clearly need to delete node from which district
Last modified: 2015-05-14 21:23:47 EDT
Description of problem:
when one district available active gears are greater than 'GEAR_DOWN_THRESHOLD', the suggestion will show 'Excess capacity in gear profile small', but it did not say to need to remove node from which one district.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create one small district and add two nodes to it
2. set 'GEAR_DOWN_THRESHOLD=2000, small: 170'
3. login on admin-console-->suggestions
Excess capacity in gear profile small
Remove 1 node to reclaim excess capacity.
You currently have 179 active gears available, which exceeds the configured GEAR_DOWN_THRESHOLD of 170. The maximum number of active gears for nodes in this gear profile is 90, so removing 1 node will bring the available active gears below the threshold.
At this time, specifying which node to remove is difficult to automate robustly. Generally, it is a good idea to remove nodes that are not districted, nodes that are deactivated in their districts, and nodes that have the fewest gears to move.
should point out: need to remove node from which one distirct.
You're right, that would be ideal. I didn't implement this yet, because the complexity didn't seem to be warranted for such an uncommon case. I'll keep this bug around to remind me, but it's just not a high priority.
Realistically this is not enough of a priority to fix before 3.0, at which point the admin console will receive a radical makeover anyway.