[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] highly available xen

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Thu, 17 Feb 2005 21:04:25 +1100
  • Delivery-date: Thu, 17 Feb 2005 10:05:45 +0000
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
  • Thread-index: AcUU2A8/Fsfk12GfQs6U6csfMBXtig==
  • Thread-topic: highly available xen

Has anyone done any work in developing some heartbeat scripts (or any
other method) for making  xen domains highly available across multiple
physical machines?

By my reckoning the hurdles to overcome are:
. make absolutely sure that the same domain doesn't start twice and hose
it's filesystem (I've done this. It isn't pretty)
. migrate a domain in the case of an orderly shutdown
. restart a domain on another physical server in the case of a complete
xen crash
. add some smarts to know how many domains a physical server can support
. prioritise critical domains over non-critical domains (eg a primary
mail server might take priority over a secondary dns server)

Any thoughts?


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.