- 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?
- 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)
- 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.
“Rackspace”, “Fanatical Support” and the Rackspace logo are trademarks or registered trademarks of Rackspace US, Inc.
“OpenStack” is a trademark or registered trademark of the OpenStack Foundation.
A few words about collaborating with Rackspace
Submitted by florian on Wed, 2012-12-12 16:22
Earlier today, we announced a case study describing some of the work we've been doing with Rackspace in recent months, and this is a good opportunity to add some personal thoughts.
In dealing with Rackspace, we've come to the impression that their reputation as an excellent service provider (and employer) is extremely well deserved. Pretty much everyone we interacted with was enormously professional, brilliant, and passionate about their work. I'm sure you can follow my reasoning about just how exceptional they are when I tell you that even their legal team was and is a pleasure to work with.
And besides that, they have been excellent in driving, and then deliberately letting go of, OpenStack. Troy Toman — one of those delightful Rackers that we had the pleasure to interact with personally — summed it up nicely in his OpenStack Summit keynote from September: they're taking pride in the fact that Rackspace's participation in OpenStack, in terms of relative code contribution, is declining (although I'm rather positive that in terms of absolute lines of code or features added, it's still on the rise, just because OpenStack is growing so darn fast). That's a really strong testament to a platform that has managed to scale corporate walls and create its own vibrant and thriving community.
Rackspace were also kind enough to give us a tour of their Rackspace Open Cloud offering when it first went public, and I would strongly encourage you to take a look if you're currently running on any other public cloud, or planning to do so. They've put together a simple-yet-elegant UI in front of a massive OpenStack infrastructure, and if you're at all interested in the cloud, you should by all means give it a whirl.
Relative to the Herculean effort that the Rackspace team has thrown behind the largest public OpenStack cloud to date, our contribution in the infrastructure HA space was surely a minor one. But it's great to be a part of this. Thanks guys, for the pleasure of being able to work with you.