On 2012-09-24T08:45:39, Ulrich Windl <[email protected]> wrote:
> So I select on unique attribute name for Xen migration, specify that
> in the Xen resource, and then define that attribute per node, using
> one of the node's own IP addresses?
Yes. The idea is that this allows you to override the IP address we'd
pick from the hostname look-up.
> I feel that being able to specify an interface (address & netmask)
> (assuming the resolver lists that interface for the node) would be
> much easier.
If you set nothing, we *will* pick an IP address from the resolver.
Having the resolver return IP addresses from several network segments is
usually not a good idea (mostly for routing and because it'd sort-of
defeat the purpose of keeping that network exclusive for such purposes).
But we'd accept a patch that would make such filtering optional, that's
for sure ;-)
I could also see an option that, instead of specifying an IP address,
specified a network like you describe, or allowed one to name a NIC; and
then populate the ip node attribute automatically on the first
start/probe on that node.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
