HP Matrix Operating Environment Software - Manual (Page 115)

6 Using Capacity Advisor with HP Serviceguard
You are likely to use both Capacity Advisor and HP Serviceguard together in your data center.
Serviceguard organizes systems or nodes into Serviceguard clusters, called SG Members in
Capacity Advisor screens such as the scenario editor and profile viewers. In a Serviceguard
environment, applications, services, and other entities are organized as packages that can move
from one cluster node to another.
TIP: In the HP SIM Version C.05.00 environment, Serviceguard clusters must have unique
names. To avoid issues with duplicate names in your configuration, do one the following:
•
Upgrade HP SIM
• Rename the clusters so they have unique names, deleting and recreating the Serviceguard
packages
Insight Dynamics components organize applications into workloads. Capacity Advisor collects
utilization data for both systems and workloads. As a package fails over from one system to
another, one of the workloads that Capacity Advisor is tracking might also move from one system
to another. Capacity Advisor continues to monitor the workload on the old system until the
workload is updated or edited to change the host name to that of the new host. Serviceguard
packages and Capacity Advisor workloads are defined independently but can overlap. A
Serviceguard workload is associated with one Serviceguard package in the Virtualization Manager
and Capacity Advisor environment.
With the latest release of Virtualization Manager, certain sub-operating system workloads are
associated with Serviceguard packages. With this change, the capcollect command
automatically concatenates the utilization of these Serviceguard-package workloads as they
move from one cluster node to another. This significantly simplifies the use of Capacity Advisor
in a Serviceguard environment.
NOTE: Capacity Advisor assumes that Serviceguard-package workloads have been correctly
defined so that there is a reasonably close 1:1 relationship between a Capacity Advisor workload
and the Serviceguard-package workload. If multiple workloads are associated with the same
Serviceguard package, Capacity Advisor results might be difficult to interpret.
The first Serviceguard-package workload created on a system also has an OTHER workload
associated with it for the system where it is running (for example, such a workload would have
a name such as system_name.OTHER). The OTHER workload for systems with
Serviceguard-package workloads in a Serviceguard cluster is associated with the system, not
with the Serviceguard-package workloads. It does not move as the Serviceguard package running
on the system moves to another system in the cluster. If all the Serviceguard-package workloads
on a cluster member move to other nodes in the cluster, the OTHER workload for that system
disappears from the display, and its utilization data becomes inaccessible until a
Serviceguard-package workload is run on that system. For additional information about this
capability, see the Virtualization Manager documentation; for more information about workloads,
including the OTHER workload, see the “Workloads” topic in Virtualization Manager Help online.
Using Serviceguard to migrate HP Integrity VM guests
When Serviceguard manages a configuration that contains Integrity VM, failover of a virtual
machine changes the UUID of the virtual machine. Several components of Insight Dynamics use
the UUID as a search key, and they treat the single virtual machine as two distinct virtual
machines, one with the previous UUID and one with the later UUID. Capacity Advisor treats
this as two or more different system traces for a failed-over virtual machine. By default, these
system workloads are named domainname, domainname.2, domainname.3, and so on. Each system
Using Serviceguard to migrate HP Integrity VM guests 115