Systemd template for Docker containers
Here's a systemd service template for running Dockerized services, for example the Prometheus Blackbox Exporter.
Filesystem Tuning
A while back, I promised I'd write about file system tuning someday. Since it hasn't really happened yet, I thought I'd do it now.
Setting up Ceph FS on a Proxmox cluster
Proxmox apparently does not yet support running CephFS, but it can be done using a bunch of manual steps. Here's how.
Getting LetsEncrypt certs non-invasively using nginx and webroot
I finally found a nice way to get LetsEncrypt certificates integrated with websites behind a reverse-proxy.
Problem: I don't want certbot messing with my server configs, and I don't want to shut down my main web server just so I can get a cert using --standalone.
Bash hotkeys
Do you know Ctrl-r, Ctrl-w, !! or Alt-.? Here's why you should.
Asterisk + Sipgate + IPv6
My internet provider force-migrated me to Dual-Stack Light the other day, so now I have IPv6 at home. It did cost me my IPv4 address though, so I'm not sure yet if I should be stoked or not. But anyway, now that I have it, I wanted to at least try it out.
Manually creating a Ceph OSD
When setting up the Ceph Server scenario for Proxmox, the PVE guide suggests to use the pveceph createosd command for creating OSDs. Unfortunately, this command assumes that you want to dedicate a complete harddrive to your OSD and format it using ZFS. I tend to disagree: Not only do I prefer RAIDs because their caches eliminate latency. I also always have LVM in between so that I'm flexible with the disk space allocation. And I'm not really a huge fan of ZFS ever since it bit me, albeit they fixed that issue by now. Still, I'm staying with my trusty XFS.
That of course means that I'll have to create my OSDs differently because pveceph createosd` isn't going to work. Here's how I do it.
Ceph CRUSH map with multiple storage tiers
At work, we're running a virtualization server that has two kinds of storage built-in: An array of fast SAS disks, and another one of slow-but-huge SATA disks. We're running OSDs on both of them, and I wanted to distinguish between them when creating RBD images, so that I could choose the performance characteristics of the pool. I'm not sure if this post is outdated by now (Jan 2018), there's a "class" thing in crush map all of a sudden. However, here's what we're currently running.
Cross-compiling Rust programs for Raspbian
I just figured out how to cross-compile Rust programs for Raspberry Pis running Rasbian Stretch. Host system is an amd64 laptop running Debian unstable.