On 2009-03-05T15:30:05, Sebastian Reitenbach <[email protected]>
wrote:
> Hi,
>
> right now, as far as I can see, the Xen live migration doesn't work together
> with Xen.
You mean, together with memory management via the RA. That is true.
> 1. create a XenMigrationHelperResource, that can do the following:
> - figure out the amount of running domU's
> - figure out the amount of maximum available memory per host
> - post both values into the CIB, using attrd_updater
> - resize memory on the domU's running on the same host as where the
> XenMigrationHelperResource runs on
>
> 2. using this resource, in e.g. a two node cluster:
> - create a group, ordered but not collocated
> - first add the XenMigrationHelperResource
> - then the corresponding Xen resource
That is a horrible hack. You can do that, but I don't see that being
merged in the resources package, sorry ...
The real issue is that Pacemaker does not take system resources (like
memory, CPU, IO, but for Xen, memory is what matters most) into account
during resource placement decisions.
Integrating this with the policy engine is the right path forward.
> Is this something that could work out, or maybe I think too
> complicated, and I overlooked sth. to solve the problem much more
> easier?
I fear the problem is not trivial, and necessarily complicated. So you
might as well go in the right direction ;-)
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
