3 ms·
From the systems/operations side of things.. Ganeti: rock solid clustered virtualization suite. OpenBSD: no fuzz server/router distro. Ceph: clustered networ
by ymse 10y ago
From the systems/operations side of things..
Ganeti: rock solid clustered virtualization suite.
OpenBSD: no fuzz server/router distro.
Ceph: clustered network storage without tears.
Varnish: covers any HTTP needs. Add haproxy or nginx for HTTPS.
Corosync/Pacemaker: Designed for reliability. Leave VRRP where it belongs (I'm looking at you keepalived).
xCAT: Little-known but widely used datacenter lifecycle management suite. Comes with cluster-aware shell, native remote consoles, BMC provisioning, unattended installs, DNS and much more.
Guix: The package manager for the future.
Things that make me want to tear my eyes out:
Openstack: keeps breaking inexplicably, nightmare to configure and maintain. Terrible documentation.
Vyatta: Don't even want to talk about it.
RHEL: Upgrades systemd 207->219 in minor release. Backports unstable kernel patches. Requires EPEL for lots of standard software. RabbitMQ logging has been broken more than two months (BZ 1324922).
- mwpmaybe 10y ago> Corosync/Pacemaker: Designed for reliability. Leave VRRP where it belongs (I'm looking at you keepalived). I just set up a floating IP address for the first time today and went with keepalived. Why would you recommend Corosync/Pacemaker over keepalived?
- ymse 10y agoIf you need just the floating IP address, keepalived is fine. I'm mostly bitter from spending days tracking down a race condition stemming from its notification scripts, which wasn't really keepaliveds fault per se. But if you need to start/move/constraint/notify anything along with the IP, or require sub-second failover, Corosync/Pacemaker is a far better choice. However due to their complexity, for just a floating IP address, keepalived is unfortunately the best option for Linux (I usually have OpenBSD in that spot).
- mwpmaybe 10y agoThanks for the explanation. Out of sheer curiosity (and because I run BSD-based pfSense and FreeNAS at home), how do you handle floating IPs and that sort of thing on OpenBSD?
- ymse 10y agoOpenBSD invented a similar protocol to VRRP called CARP back when VRRP was patent-encumbered[0]. Configuring it is deceptively simple: just create an interface with ifconfig called "carpN", specifying VID, password and IP address[1]. You can also make it load-balance traffic between your carp hosts if desired[2]. Give it a go for your next firewall/server build :) 0: https://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol https://en.wikipedia.org/wiki/Common_Address_Redundancy_Prot... 1: https://www.openbsd.org/faq/pf/carp.html https://www.openbsd.org/faq/pf/carp.html 2: http://man.openbsd.org/OpenBSD-current/man4/carp.4 http://man.openbsd.org/OpenBSD-current/man4/carp.4