- Who we are
- What we know
- What we've created
- Hints and Kinks
- Checking Corosync cluster membership
- Configuring radosgw to behave like Amazon S3
- Downgrading to DRBD 8.3
- Fencing in Libvirt/KVM virtualized cluster nodes
- Fencing in VMware virtualized Pacemaker nodes
- GFS2 in Pacemaker (Debian/Ubuntu)
- Interleaving in Pacemaker clones
- Maintenance in active Pacemaker clusters
- Managing cron jobs with Pacemaker
- Mandatory and advisory ordering in Pacemaker
- Migrating virtual machines from block-based storage to RADOS/Ceph
- Network connectivity check in Pacemaker
- OCFS2 in Pacemaker (Debian/Ubuntu)
- Solid-state drives and Ceph OSD journals
- Solve a DRBD split-brain in 4 steps
- Testing Pacemaker clusters
- Totem "Retransmit List" in Corosync
- Turning Ceph RBD Images into SAN Storage Devices
- Which OSD stores a specific RADOS object?
- Presentations
- Ceph Tutorial (LCA 2013)
- Ceph: The Storage Stack for OpenStack (OpenStack Israel 2013)
- Die eigene Cloud mit OpenStack Essex (German, LinuxTag 2012)
- Fencing (LCE 2011)
- GlusterFS in HA Clusters (LCEU 2012)
- GlusterFS und Ceph (German, CeBIT 2012)
- Hands-On With Ceph (LCEU 2012)
- High Availability Update (OpenStack Summit Fall 2012)
- High Availability in OpenStack (CloudOpen 2012)
- High Availability in OpenStack (OpenStack Conference Spring 2012)
- Highly Available Cloud: Pacemaker integration with OpenStack (OSCON 2012)
- Mit OpenStack zur eigenen Cloud (German, CLT 2012)
- Mit OpenStack zur eigenen Cloud (German, OSDC 2012)
- More Reliable, More Resilient, More Redundant (OpenStack Summit April 2013)
- MySQL HA Deep Dive (MySQL Conference 2012)
- MySQL High Availability Deep Dive (PLUK 2012)
- MySQL High Availability Sprint (PLUK 2011)
- OpenStack Essex im Praxistest (German, Linuxwochen Wien 2012)
- OpenStack High Availability Update (Grizzly and Havana)
- Roll Your Own Cloud (LCA 2011)
- Storage Replication in HPHA (LCA 2012)
- Zen of Pacemaker (LCA 2012)
- hastexo in 100 Seconds
- Technical documentation
- News releases
- Hints and Kinks
- What we do
- What we charge
- What others say

About our blogs
All hastexo blog posts represent the opinion of the post's author, and do not necessarily reflect hastexo's corporate policy or point of view.
Related stuff
Speaking at the 2012 Percona Live MySQL Conference
Submitted by florian on Mon, 2012-02-27 15:39
This year, I have the pleasure of returning to the MySQL Conference & Expo as a speaker. Percona have picked up the torch that O'Reilly had held as the conference organizers, and they're putting together a 3-day conference this year. I am co-presenting a tutorial with Yves Trudeau from Percona.
Our tutorial is called High Availability Deep Dive: Pacemaker, DRBD, MySQL Replication, and more! and it's going to be the only full-day tutorial offered in this year's conference. In it, Yves and I are going to cover
-
An overview of the Pacemaker cluster stack (the classic "this is Pacemaker" introduction)
-
DRBD-backed MySQL replication (another classic and widely deployed scenario)
-
MySQL replication under Pacemaker management (a new option which Yves has vastly improved through a big patch set to the MySQL RA).
Do I expect this talk to be controversial? Definitely. The amount of "Pacemaker is terrible" and "Pacemaker is unsuitable for managing highly available databases" that has been around the blogosphere lately is pretty mind-boggling.
But strangely enough, most of the things brought forward against Pacemaker by its detractors seem like a time-warp back to about 2007.
-
"We must use XML to manage Pacemaker!" Nonsense. In fact, that was never true – the release of Pacemaker as a separate project and the release of the crm shell coincided. Ever since, Pacemaker configuration has been as text-based as MySQL itself.
-
"All Pacemaker can do is react to node failure!" Nothing could be further from the truth. Pacemaker has some of the most sophisticated resource monitoring and auto-recovery capabilities under the sun.
-
"OK. But all it can do to react to resource failure is kill a daemon!" Bogus again. It will happily do whatever the resource agent specifies. Or the admin, through the configuration.
In our tutorial, we're going to dispel a few of these myths. We certainly make no claims as to Pacemaker being the one and only solution for MySQL HA, but it's one that serves lots of use cases excellently.
Needless to say, I'll also hang around for the conference proper, and I'm very much looking forward to seeing lots of familiar faces. I'll also remain in the Bay Area for some time after the MySQL conference – more on that in a day or two.
- florian's blog
- Login or register to post comments
