Hello everyone. I haven't seen any activity on this list before now so please forgive me if anything here has already been discussed.
Firstly, about myself: I'm using Pacemaker+OpenAIS on SLES on production systems serving millions of web requests, sending hundreds of thousands of emails and load-balancing MySQL clusters. I've been doing this for about 2 years now and been pretty active in the Linux-HA and Pacemaker mailing lists. I wrote this HowTo for making MySQL load-balanced and master-master replicated: http://www.clusterlabs.org/wiki/Load_Balanced_MySQL_Replicated_Cluster . I've been a long-time user of Ubuntu and with Canonical pushing Server into the Enterprise I really want to see Ubuntu come up with a good cluster stack. In fact my next HA project is being based on Lucid with good results so far. I'd just like to pick up on a few points from the spec and the UDS notes: = UDS Lucid = == Status == * Stay with RHCS?? When I've looked into RHCS previously, it's been a little too far off the mainstream of Linux-HA so it's difficult to get documentation from anywhere but Red Hat and it now looks like they are going more in line with Pacemaker and Corosync by employing Andrew Beekhof. * Pacemaker: Too unstable. Why is Pacemaker too unstable? It's used for the HA component of SLES and I see lots of people using it on lots of different distros with success. * Heartbeat: Linbit is trying to push users to use Pacemaker + Heartbeat 3.0 to provide an update patch from Heartbeat 2.x I don't think Linbit are trying to push anyone on to Heartbeat 3.0, they are supporting Heartbeat as it was effectively unmaintained and it's another source of revenue for them to be able to support users with mission-critical DRBD + Heartbeat style clusters. I think most would agree that Corosync is the way forward as a cluster messaging layer. == ToDo == * Be more active in upstream. Ubuntu users join upstream irc channel(#linux-cluster and #linux-ha) to ask for help. + the Pacemaker, OpenAIS, Linux-HA, DRBD etc. mailing lists. * Documentation, Documentation, Documentation * Would be a nice idea to also document software proxies (squid, ctdb for samba, pgpool, etc) * Track Linbit changes for Heartbeat 3.0 to provide and update path from Heartbeat 2.1.x to pacemaker + heartbeat 3.0. I think Heartbeat 3.0 should be low-priority for Ubuntu-cluster-stack. Corosync and OpenAIS are where it's all happening now. * What about LoadBalancing. * keepalived for software * If we use this one, we need to support bonding out of the box ldirectord is also fine, it works and is an interface to LVS, just as keepalived is. Regards, Darren Mansell
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
