HP Integrity Online VM Migration and GUI management tools

19
Special considerations for working in a gWLM environment
As of gWLM version 4.1, there is an integration issue with Integrity VM version 4.1. Because of this,
HP strongly recommends not using these products together until either patches or a new version of the
product are available.
What you might see
For the initial release of the online migration capability, there have been no enhancements made to
gWLM to track the migrations. However, this tool can continue to be used with the following
considerations:
• Each guest (workload) can have only one policy assigned to it, no matter how many different SRDs
it appears in.
• When in gWLM (on the SRD tab in the VSE Virtualization Manger), you find that migrate-able
guests that are not on the host/SRD currently being viewed are shown in gray as a non-running
workload.
• Unlike guests that are configured as HP Serviceguard packages, there are no icons to indicate that
the workload is running in a different SRD.
Workarounds
In addition to being clear on the scope of the SRD (one per host, unless the hosts are either nPars in
the same complex or are members of the same GiCAP group) and of the policies (one per guest,
regardless of the number of hosts), custom policies need to be defined prior to creating the SRDs. If
you find that you need to modify a policy after creating the SRDs, make a new policy that meets your
requirements and modify the SRDs to associate the new policy with the appropriate guests. After the
new association is made, manually redeploy the affected SRDs from within gWLM.