2-Node XenServer configured with HALizard NoSan Installer
-
First let me start off with RTFM. I didn't at first and was proved a fool. That out of the way, once You read it, it's very simple. Albeit I was reading it, and simply misunderstood a few of the steps.
Namely: Do not enable HA from within XenCenter, it disables HALizard so there are no conflicts.
Platform Two Dell R730's configured with 8x4TB Drives in RAID 10, 96GB of RAM and dual E5-2640v3 2.6Ghz CPUs.
Total Price $16.614 (Price may vary)
To configure the servers, I've installed XenServer 6.5 (not 7 I know) to both systems direct to USB, leaving the entire array available for HALizard and VM Storage.
Once the servers were updated, you can wget the HALizard NoSan installer script.
Connect two ports on each server directly together, this will be the BOND'd interface for HALizard to fail-over should something occur to either server.
Again RTFM when configuring this setup. I did, but skipped ahead at parts and was confused on some results. @halizard helped to sort me out, so I have to give them props for that.
Once you run the script on the first server you'll be asked which server this is, etc, on the first server, you'll configure it as the first in the pool. I used the stock BOND configuration of 10.10.10.1, 10.10.10.2 and 10.10.10.3 making my life super simple. I don't have to make any changes to the configs. Also being a private LAN between the servers there is no reason to not use them since I'm not in this address space anyways.
-
Once the BOND was setup, all I had to do was complete following the guide, the entire process only took 2 days to complete (because of my first time setting it up)
Of critical note, do not enable HA from within XenCenter (XenServer) as this disables HALizard.
Failover of a allocated VM between the host with six 1500GB drives + a 350GB C drive takes ~ two minutes, but it's complete live migration.
So you'd never know the system was moving if you were using it.
-
Great, thanks for sharing!
