Hi Robert, Thanks for clarifying it and providing some background. I knew that the HASI and pretty much everything behind it was a demo for Brainshare but that's the kind of thing we needed so bad and we use ever since (in production for more than a year). Failures are rare but the HASI did its job great several times ever since. Perhaps I shouldn't use it in prod but it's still cool stuff. :)
> It's been a while, but iirc, registered VMs still show up even if not running; > because they are still known/declared resources to Xen... Only if the VM was created by YaST GUI or some other utility perhaps manually registered with xm new. All my HA managed VMs are clones and because I change only the memory and disk bits in the xm config I do not suffer from VM showing up in virtman unless its running(of course all xenstores were cleaned at some stage). > Afaik today, it's still possible to start a VM without registering it, and > iirc Yes, That's what I have been doing and I appreciated that I wasn't forced to use the xenstore, old school still works ;) > that's still enough also to support migration (the Xen RA was extended later > to support live migrate issued by Heartbeat). There might be some other Correct. I can only see problem around traditional (on ocfs2 in HASI) config files that xen cuts the support for it one day. If that happens then something we may need to work out for xenstore. Not sure if it's possible to actually run the xentore tdb on ocfs2 mount on all HASI nodes? That's what we do for the config files so in theory it should work. Somebody had similar issue in another topic recently about syncing xenstore and I think 1 db would be the answer not the sync. Thanks, Ivan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
