summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-04-21 11:44:58 +0300
committerPaul Buetow <paul@buetow.org>2024-04-21 11:44:58 +0300
commit73c837385e4e8132cd729d82b509b1b97012dbb4 (patch)
treec519200abf1576921d2bc9fbcdd17317e015482d
parentea309ae500ebbed11c8388b1661ada02dddc0238 (diff)
Update content for md
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md18
-rw-r--r--index.md2
-rw-r--r--uptime-stats.md2
3 files changed, 20 insertions, 2 deletions
diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
index f5477fe3..39f0c59c 100644
--- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
+++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
@@ -27,6 +27,24 @@ _____|_:_:_| (o)-(o) |_:_:_|--'`-. ,--. ksh under-water (((\'/
```
+```
+Table of contents:
+ KISS high-availability with OpenBSD
+ My auto-failover requirements
+ My HA solution
+ Only OpenBSD base installation required
+ !/bin/ksh
+ Race condition (e.g. script execution aborted in the middle of the previous run)
+ Fairly cheap and geo-redundant
+ Failover time and split-brain
+ Failover support for multiple protocols
+ Let's encrypt TLS certificates
+ Weekly auto-failover for Let's Encrypt automation
+ Monitoring
+ Rex automation
+ More HA
+```
+
I have always wanted a highly available setup for my personal websites. I could have used off-the-shelf hosting solutions or hosted my sites in an AWS S3 bucket. I have used technologies like (in unsorted and slightly unrelated order) BGP, LVS/IPVS, ldirectord, Pacemaker, STONITH, scripted VIP failover via ARP, heartbeat, heartbeat2, Corosync, keepalived, DRBD, and commercial F5 Load Balancers for high availability at work.
But still, my personal sites were never highly available. All those technologies are great for professional use, but I was looking for something much more straightforward for my personal space - something as KISS (keep it simple and stupid) as possible.
diff --git a/index.md b/index.md
index 476ff591..a5cc8da9 100644
--- a/index.md
+++ b/index.md
@@ -1,6 +1,6 @@
# foo.zone
-> This site was generated at 2024-04-16T23:39:21+03:00 by `Gemtexter`
+> This site was generated at 2024-04-21T11:44:45+03:00 by `Gemtexter`
```
|\---/|
diff --git a/uptime-stats.md b/uptime-stats.md
index b9a2b326..d0014c0b 100644
--- a/uptime-stats.md
+++ b/uptime-stats.md
@@ -1,6 +1,6 @@
# My machine uptime stats
-> This site was last updated at 2024-04-16T23:39:21+03:00
+> This site was last updated at 2024-04-21T11:44:45+03:00
The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine.