HP Matrix Operating Environment Software - Manual (Page 94)

2. Given these results, you can
•
Press Cancel to prevent these changes from being saved.
•
Press Save to write these changes to the scenario with which you started the load
balancing.
•
Press Save As... to save these changes under a new scenario name.
•
Press Return to Step 1 to edit the constraints prior to running the Smart Solver again.
Results: Automated load balancing of servers or VM hosts
Expected results
The solutions show workloads that are balanced across the selected existing servers or VM hosts.
Load balancing is based upon CPU, memory, network I/O, and disk I/O capacity, utilization
limits, and headroom, where the goal is to distribute workloads so that each system has comparable
headroom and therefore, similar headroom rating.
Resource capacity
Workloads that specify utilization limits for a metric (for example, memory or disk I/O) can only
be placed on resources that define a capacity for the corresponding metric. In other words, if you
specified that a workload never exceed 100% memory utilization, that workload can only be
placed on a system for which total memory capacity is known.
Utilization limits
Every workload selected must have at least one utilization limit applied before using the Smart
Solver. This can be any type of utilization limit, including the default global utilization limit.
Headroom rating
The headroom rating shows the amount of available resource above the existing resource utilization
that will exist for the resulting solution in the simulation. Among the solutions that require the same
target systems, the solution with the tightest fit is shown.
Possible anomalies in the results
Load balanced results appear unbalanced
The solution may not look balanced because smaller systems generally are assigned a smaller
percentage of usage than larger systems, and very small systems may end up with no workloads
at all.
For example, a large 16 GB system at 87% memory usage has 2 GB of headroom, and a smaller
4 GB system at 87% has only 500 MB of headroom. Aiming for 87% usage on both systems would
not yield a balanced solution. Instead, a balanced solution is to fill the larger system to 87% and
fill the smaller system to only 50%. With this placement, workloads placed on either system will
have the same amount of headroom to grow (2 GB).
No apparent change from original configuration
The solution may be the same as the original scenario, and it looks as though no computation was
performed. Actually, with the current attributes and constraints, the Smart Solver could not find a
better solution than the current configuration of systems. This means that the current configuration
is the current best solution. A message displayed in BLUE text indicates that the results are not an
error (errors are displayed in RED text).
No apparent change on one or more systems
The solution may show no change on one or more destination systems. Thus, it may appear that
the Smart Solver did not include the server in its computations. In actuality, the Smart Solver
determined that as part of the best solution, it was best to leave these target systems with their
original configurations.
94 Procedures