I really like NetBox and call myself a NetBox noob too dangerous in many places. I’m currently working on my first NetBox plugin for OpenNMS. I run a mix of workloads on classic virtual machines and also in Kubernetes with containers. The Plugin - NetBox - Kubernetes situation hit me quickly. I’m in the lucky situation of having known Peter Eckel for a very long time. He is the maintainer of the NetBox DNS Plugin and his valuable advice to me was:
Continue reading
A while back I wrote about using two Claude accounts side by side. A private subscription and a corporate team account, two config dirs and a pair of shell aliases so the tokens don’t bleed into each other. That part still works fine. But after living with it for a few months, I learned where it falls short, so here is the grown-up version.
The aliases only solved which account pays.
They did nothing about how Claude behaves.
Each config dir grew its own CLAUDE.md, and the moment you maintain two of anything by hand, they drift.
I’d tighten a commit convention in one account and forget the other.
The work account learned a guardrail the private one never got.
What I really wanted was the same baseline everywhere, conventional commits, SHA-pinned GitHub Actions, license headers, no matter which hat I’m wearing.
I had to scratch one of my itches. I have to work with SBOMs and I couldn’t find something, so I’m announcing blitsbom — a browser-only SBOM viewer. Software Bills of Materials are everywhere now. Procurement asks for one. Compliance wants one filed. A regulator’s auditor will, at some point, want to look at one. The trouble is that the moment you actually want to read an SBOM — to skim what’s in a build, see which components are copyleft — your options are oddly bad. You either ship the file off to a SaaS scanner, install a heavyweight platform, or squint at 280,000 lines of JSON in your editor.
Continue reading
I’ve been a quiet user of CoolModFiles.com for years. It’s a tiny web player that grabs a random MOD file from modarchive.org and plays it. No login, no library, no algorithm — just a play button and a wave of nostalgia from the Amiga and PC tracker scene. The README says “no black magic involved” and that’s exactly the appeal: a digital amplifier for a corner of the demoscene most people never knew existed.
Continue reading
Just something a few might be interested in. I’m in a fortunate situation where I have a private Claude account and also signed in to a corporate Claude team account.
I would like to make sure I spent the tokens from the work subscription only on work-related items and the tokens from my private account on my own stuff. What works for me pretty well is having two Claude config dirs and a shell alias like this:
Continue reading
When you’re someone like me, who has operated and maintained software for yourself or others, the Release Notes are pretty important. Pure software developers or stakeholders often overlook the importance of this topic, as they simply have to deal with Release Notes when building or generating them. They are often an afterthought and just another box to check on a release procedure list. Here are some reasons why spending some time on your Release Note is worth it.
Continue reading
We have seen two major outages in the last weeks caused by AWS and Azure networking issues. Both outages had a significant impact on services running in the cloud and affected a large number of users. The self-hosting people were laughing about it, but some got struck with the recent Docker 29.0.0 release. It simply increased the minimal API version from 1.24 to 1.44.
This change broke Traefik and some tooling, like the testcontainers-java. The maintainers of Traefik already released a fix, and probably created some stress for them. A lot of issues poped up in their GitHub repository, like this one https://github.com/traefik/traefik/pull/12256. I felt sorry for them, many users use their stuff - including me - to drive HTTP/HTTPS traffic to their websites. It was great to see how quickly shared workarounds. The Traefik maintainers were able to provide and ship a fix in a new release very quickly. All you need to do is upgrade to 3.6.1, and you are good to go again.
Continue reading
I’m maintaining container images in the OpenNMS ecosystem. My local machine is a Mac with Apple Silicon. While I was upgrading some base images using RHEL UBI 10 / CentOS 10 images, I noticed the following error message.
0.112 Fatal glibc error: CPU does not support x86-64-v3
That happens if you try to run on an emulated x86 architecture running on ARM. After some investigation, I’ve found an article in the Red Hat developer forum talking about upgrading the Microarchitecture level from v2 to v3. The problem introduced is that v3 isn’t supported. I’m using Orbstack and you can reproduce this problem simply running the following docker command.
Continue reading
This document describes how you can set up a lab environment for testing gNMI using a virtual HPE Juniper router running Junos 24.2 R1-S2.5. It shows how you can collect metrics for interfaces and CPU utilization collected with OpenNMS. This isn’t something I do every day, so I just preserve this here for my future self and the ones who want to get up to speed a bit quicker.
You need the following environment to get a lab running:
Continue reading
I remember the first time I tried to get an open-source project compiled and deployed. The distribution of Linux at this point was Slackware. Build or installation instructions didn’t exist, and without handholding on IRC, it would not have been possible for me. That was 30 years ago, people in IRC were very self-selected, patient, and helpful. When you have skilled patient people in IRC and you can communicate what you did, what exactly failed, and what you would have expected - your learning experience is pretty impressive. Nevertheless, it does not scale well. People nowadays expect things to work with a click of a button. They are even not keen on reading clear instructions.
Continue reading