HP Matrix Operating Environment Software - Manual (Page 108)

what destinations you selected. When a combination of VM hosts are chosen, the placement of
VM guests goes first to existing VM hosts, and then to the template VM hosts.
Further, as part of the input parameters, you can select to load balance the resulting VM hosts.
This load balancing occurs after and only amongst the target VM hosts that are required for the
consolidation solution. In other words, if the consolidation solution results in any VM hosts being
unused (and therefore, not required in the solution), the unused systems will not be involved in
the load balancing. Only the required systems in the solution are involved in the load balancing.
The resulting solution is the configuration requiring the fewest number of systems with the
minimal requirement for
headroom , while taking into consideration resource utilization and
utilization limits.
Resources The placement of VM guests takes into consideration CPU, memory, network I/O,
and disk I/O capacity, and utilization limits. If load balancing (balancing resource utilization
across the resulting systems) was selected, the VM guests were load balanced across the systems
that had 1 or more VM guests.
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 ranking 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
Fewer systems shown. The Smart Solver solution can contain fewer VM host targets than were
originally selected. This occurs when the workloads fit on fewer systems than originally selected.
For example, if systems A, B, and C are selected as target VM hosts, but all the workloads can
fit into VM hosts A and B, then only VM hosts A and B are shown in the solution.
Systems involved in load balancing. When load balancing is performed, the loads are balanced
only across the resulting systems in the solution. For example, if only VM hosts A and B are used
(and VM host C is not), then load balancing is performed only across VM hosts A and B. VM
host C is not included for the load balancing calculation.
Headroom rating shows zero (0) stars. The headroom rating shows zero stars even though it
appears that there is sufficient room on the VM host for the workloads. This happens whenever
one or more of the original servers violates a utilization limit prior to the Smart Solver being run.
Before running the Smart Solver, ensure that your source systems are not already violating a
utilization limit.
To return to a planning checklist:
•
Consolidating server loads onto a virtual machine using automated solution finding [p. 47]
Automated solution finding: Load balance of servers or VM hosts
This section describes the procedure for automating the search for an optimal load-balanced set
of servers.
108 Procedures