Everything is a Freaking DNS problem - high-availability http://127.0.0.1:8080/blog/taxonomy/term/673/0 en Wholesale High Availability http://127.0.0.1:8080/blog/node/750 <p><a href="http://techthoughts.typepad.com/managing_computers/2008/10/using-virtualization-to-provide-ha-at-wholesale.html" rel="nofollow">Alan</a> just coined WholeSale HA. The idea of rebooting a whole virtual machine rather than just failing over 1 service.</p> <p>He wants to have the best of both worlds in 1 framework, he however doesn't specify what parts he likes from the WholeSale HA setup</p> <p>Yes you want to use it coupled with hardware predictive failure analysis tools. In order to achieve Higher Availabilty, but I don't think the WholeSale HA part is real HA.</p> <p>WholeSale HA isn't going to be fast enough for most of the business critical environments.<br /> You simply cannot afford to reboot or even boot a full machine and the related downtime that brings for your service.</p> <p>So yes a best effort combination, but with a strong focus on the application state would be preferred. WholeSale is a good start .. but it's definitely not where you want to stop.</p> http://127.0.0.1:8080/blog/node/750#comments alan robertson ha high-availability linux-ha vapourware virtualization Sat, 25 Oct 2008 13:56:28 +0000 Kris Buytaert 750 at http://127.0.0.1:8080/blog Integrating HA and Virtualization http://127.0.0.1:8080/blog/node/533 <p><a href="http://techthoughts.typepad.com/managing_computers/2007/12/how-managed-vir.html ">Alan Robertson</a> is discussing how Managed Virtualization (including HA) conflicts with System Management</p> <p>He has some interesting points regarding managing infrastructure , in his vision there are just too much layers that don't talk to eachother .<br /> He also points out some of the issues with CIM and SNMP .</p> <p>Alan thinks the ideal way to go is to have your HA solution manage your Virtualization also.</p> <p>I`m wondering if this doesn't add too much complexity.</p> <p>If you are already making sure the services in your virtual machines are highly available, then why would you want to add another layer of complexity ? Surely the idea of being able to migrate virtual machines around sounds tempting but do we really need that extra layer of complexity ? </p> <p>I've explained that migrating a virtual machine to another server won't help you when your apps crash or when your physical server fails.</p> <p>But keeping an overview of which services are running where from 1 place seems like an interesting idea. </p> <p>I've been tinkering about using the resource concept of Linux-HA however to serve another purpose than pure high availability. You might want to use its constraints to define how many virtual machines should run on and how much resources they can use on a certain physical machine. Hence create a loadbalancing infrastructure with it.</p> <p>(I`m really really hoping someone now replies to this with a url which gives me a HAResource that does Live Migration :))</p> http://127.0.0.1:8080/blog/node/533#comments high-availability linux-ha virtualization Mon, 17 Dec 2007 20:59:32 +0000 Kris Buytaert 533 at http://127.0.0.1:8080/blog