The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,861 other subscribers

Archive for the ‘Infrastructure’ Category

b0rk does fun things with DNS: CNAME records at the root of the domain; technically not allowed, definitely not recommended, but somehow work for web browsing

Posted by jpluimers on 2023/12/21

[Wayback/Archive] 🔎Julia Evans🔍 on Twitter: “I’ve always heard that you can’t create CNAME records at the root of the domain. But apparently you can? It seems to work fine as far as I can tell but I’m curious about the possible consequences. (yes, I registered cnameroot.com just to make this tweet) “

Read the rest of this entry »

Posted in Cloud, Cloudflare, DNS, Infrastructure, Internet, Power User | Leave a Comment »

Ookla speedtest CLI for Windows has some undocumented arguments to accept license and GDPR

Posted by jpluimers on 2023/10/11

I had speedtest-cli running on MacOS and various Linux machines, but not yet on Windows (see for instance my post Ubuntu: Fixing the myserious “Failed to stop apt-daily.timer: Connection timed out”).

[Wayback/Archive] Install and Test Internet Speed with Speedtest CLI Command Line – NEXTOFWINDOWS.COM reminded me there is a Speedtest CLI for Windows download at at [Wayback/Archive] Speedtest CLI: Internet speed test for the command line, but I am a an automation/scripting/devops person, so luckily there are also [Wayback/Archive] Chocolatey Software | Speedtest by Ookla (don’t get [Wayback/Archive] Ookla.Speedtest download, as that is the GUI version).

Both the Chocolatey and winget packages are named the same, so that is quite confusing. This is how I have set them apart:

Read the rest of this entry »

Posted in *nix, *nix-tools, Batch-Files, Chocolatey, DevOps, GDPR/DS-GVO/AVG, Internet, ISP, KPN, Notepad++, Power User, Privacy, Scripting, SpeedTest, Windows, xs4all | 2 Comments »

Looking for maintainer(s) for fritzcap (Python project that captures calls from a Fritz!Box)

Posted by jpluimers on 2023/07/12

Given my health uncertainty, I am looking for maintainers for the fritzcap project (it captures calls from a Fritz!Box modem/router and is written in Python).

History

The fritzcap project was originally started in2007 by [Wayback/Archive] spongebob | IP Phone Forum, first as a binary fritzcap.exe Windows executable (see his first post at [Wayback/Archive] FritzBox: Tool für Etherreal Trace und Audiodaten-Extraktion | IP Phone Forum). In 2010 it became an open source Python project at [Wayback/Archive] Google Code Archive – Long-term storage for Google Code Project Hosting.

Read the rest of this entry »

Posted in About, Audio, Cloud, Communications Development, Containers, Development, Docker, ffmpeg, Fritz!, Fritz!Box, fritzcap, Hardware, HTTP, Infrastructure, Internet protocol suite, Media, Network-and-equipment, Personal, Power User, Python, Scripting, Software Development, TCP | Leave a Comment »

An unexpected turn of events when Jeff Geerling posted “I’m hosting my website on a FARM!”

Posted by jpluimers on 2023/07/06

Some links on the unexpected turn of events after [Archive] Jeff Geerling (@geerlingguy) / Twitter posted

First his site got more traffic because of the post, then within an hour traffic exploded because of a DDoS overflowing both his Raspberry Pi cluster and his mobile data capacity.

Jeff will likely do blog posts on these and update the underlying GitHub repository at [Wayback/Archive] geerlingguy/turing-pi-2-cluster: Turing Pi 2 Cluster , but until then (since his Tweets were not threaded), this is what happened on 20220209 as it taught me a few bits:

Read the rest of this entry »

Posted in Cloud, Cloudflare, Containers, Development, Docker, Hardware Development, Infrastructure, Internet, Kubernetes (k8n), LifeHacker, OpenSpeedTest, Power User, Raspberry Pi, SpeedTest | Leave a Comment »

I learned about the “YAML-NOrway Law.”

Posted by jpluimers on 2023/06/15

Every time I use YAML, I bump into things even I copy paste from exact working configurations.

Today I learned I’m not just alone, but there is even a term for it: “YAML-NOrway Law.”

[Wayback/Archive] I’d like to propose the “YAML-NOrway Law.” “Anyone who uses YAML long enough wil… | Hacker News

I’d like to propose the “YAML-NOrway Law.”

“Anyone who uses YAML long enough will eventually get burned when attempting to abbreviate Norway.”

Example:

  NI: Nicaragua
  NL: Netherlands
  NO: Norway # boom!

`NO` is parsed as a boolean type, which with the YAML 1.1 spec, there are 22 options to write “true” or “false.”[1] For that example, you have wrap “NO” in quotes to get the expected result.

This, along with many of the design decisions in YAML strike me as a simple vs. easy[2] tradeoff, where the authors opted for “easy,” at the expense of simplicity. I (and I assume others) mostly use YAML for configuration. I need my config files to be dead simple, explicit, and predictable. Easy can take a back seat.

[1]: [Wayback/Archive] http://yaml.org/type/bool.html [2]: [Wayback/Archive] https://www.infoq.com/presentations/Simple-Made-Easy

Even a key Ansible author seems to regret using YAML: [Archive] Kevin Honka on Twitter: “@hikhvar @isotopp jap :) Muss da immer an den Spruch des entwicklers von Ansible denken: Hätte ich gewusst, wie einfach es ist in Python eine DSL zu bauen, hätte ich nie YAML verwendet” / Twitter

Somewhere in the tread, Kris mentioned [Wayback/Archive] Code rant: The Configuration Complexity Clock:

It seems to be a recurring issue in both Kris’ and my life: One needs to actually fail in order to get a feel for reality.

Via [Archive] Kris on Twitter: “Die YAML Spezifikation gelesen. yaml-dox-url Jetzt habe ich Alpträume. “Erkläre Node Tags, Complex Keys mit ?, resolved und unresolved tags, und partial representation.”” / Twitter

[Wayback/Archive] YAML Ain’t Markup Language (YAML™) revision 1.2.2

–jeroen

Read the rest of this entry »

Posted in Configuration Management, Infrastructure, YAML | Leave a Comment »

GitLab pages on a custom domain are nice, but be aware of intermittent 502 and certificate errors

Posted by jpluimers on 2023/06/05

Reminder to self GitLab pages on the gitlab.com are free, so Setting up a GitLab project so it is served over https as a gitlab.io and a custom subdomain comes with two caveats:

  1. Intermittent HTTP error 502 Bad Gateway
  2. Intermittent NET::ERR_CERT_COMMON_NAME_INVALID (Chrome) or SSL_ERROR_BAD_CERT_DOMAIN (Firefox):

–jeroen

Read the rest of this entry »

Posted in Cloud, Development, GitLab, Infrastructure, Power User, Source Code Management | Leave a Comment »

The CPU load average metric often is not a good one to alert on

Posted by jpluimers on 2023/04/20

Boy I wish threads with more than one person could be saved by the ThreadReaderApp.

Anyway:

[WayBack] Thread by @mipsytipsy: oh boy.. i was just idly musing over how the single most ubiquitous/useless metric is “CPU load average”, lol i wonder if you could use CPU…

oh boy.. i was just idly musing over how the single most ubiquitous/useless metric is “CPU load average”, lol

i wonder if you could use CPU load alerts to score how modern and powerful a team’s toolchain is, like a Waffle House Index for tooling. 🤔

 

…oh oh! but i was gonna say, this thread between @drk and @shelbyspees is a killer nanotutorial in how to ask better questions about your code — where to start, how to drill down and dig in, how to instrument, and how to approach such an open-ended exploratory jaunt. 👏🐝❤️

it’s a really good illustration of this thing we end up saying all the time, which is “don’t fear the future, it is simpler and clearer and *easier* here! the way you are doing it NOW is the hard way!” 😖

time for cpu load average to go the way of the PC LOAD LETTER …

0:00
/ 0:01

 

 

Read the rest of this entry »

Posted in *nix, Cloud, Development, DevOps, Infrastructure, Power User, Software Development, Systems Architecture | Leave a Comment »

smile.amazon.de: AmazonSmile Is Ending (in fact it already has ended)

Posted by jpluimers on 2023/04/07

I missed this 2 weeks ago, but in fact “AmazonSmile Is Ending” means it has already ended. Amazon.de purchases do not help charity any more.

[Wayback/Archive] smile.amazon.de

AmazonSmile Is Ending

Thank you for your support over the past decade. We appreciate your help in donating more than $450 million across hundreds of thousands of charities worldwide. Moving forward, we are excited to focus on other philanthropic initiatives.

You can continue shopping on http://www.amazon.de for the same selection of products you know and love.

in German:

AmazonSmile wird eingestellt

Wir danken Ihnen für Ihre Unterstützung in den letzten sieben Jahren. Mit Ihrer Hilfe konnten hunderttausende gemeinnützige Organisationen weltweit mit mehr als 450 Millionen US-Dollar unterstützt werden. Amazon wird sein soziales Engagement künftig auf andere Bereiche fokussieren.

Sie können weiterhin auf http://www.amazon.de einkaufen, wo Sie die gleiche Produktauswahl vorfinden.

–jeroen

Posted in Amazon.com/.de/.fr/.uk/..., Cloud, Infrastructure | Leave a Comment »

Need to take a look a Scaleway

Posted by jpluimers on 2023/04/05

Based on

I need to take a look at Scaleway, at least at thee links via [Wayback/Archive] scaleway instance – Google Search:

Related blog post: Dave Anderson on Twitter: “Cool minor @Tailscale moment: I’m recommissioning a server that got moved from a different network, so all its network config was wrong, and generally I couldn’t get at it over the network, only IPKVM console. But then my ping over Tailscale started working?!” / Twitter

–jeroen

Posted in Cloud, Infrastructure, Power User, Scaleway, Scoop, Windows | 1 Comment »

howisthecloud (@howisthecloud) / Twitter

Posted by jpluimers on 2023/02/09

Getting the latest cloud outages is easy: just follow [Archive] howisthecloud (@howisthecloud) / Twitter

Feeding cloud provider statuses from all over the Internets. Currently tweeting AWS,SFDC,Heroku,GoogleApps,Azure,Sakura,Rackspace,Pivotal statuses. By

I used it to keep an eye on the december 2021 US-EAST-1 AWS outage I wrote about in Does it still hold: “Never keep anything important on AWS in US-EAST-1”?.

–jeroen

Posted in Amazon.com/.de/.fr/.uk/..., AWS Amazon Web Services, Azure Cloud, Cloud, Infrastructure, Uncategorized | Leave a Comment »