This script could be a replacement for the traditional "xm" command. In HA stack if the domU is specified as Xen OCF resource it then cannot be started, stopped, migrated, managed with traditional utilities because HA simply wouldn't know what happened to the resource. As a panic action it could reset the node where the monitor operation of the domU failed and cause further/unforeseen problems .
The script is not gonna solve your misconfigured HA issues, it really needs a well defined policy and a well working system.
It's advised that you set up resource stickiness in HA with a score of INFINITY, I usually set up alias as well for my root account to replace the traditional xm command:
dom0:~ # echo "alias xm='/etc/xen/scripts/xm-ha'" >> ~/.bashrc
dom0:~ # source ~/.bashrc
The script could be located at /etc/xen/scripts (need that to be added to the search path also). If it's shared (via OCFS2) all nodes will pick up changes to it instantly. (if any)
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.