Skip to main content

Where did all my folders go?

I've been cleaning my desk and so I need to make my undesirable knives go away. I have a box an so they are officially away. In my first pass all but one is a folder. Many suck so bad I wouldn't even pay the postage or even try to recycle them. Here they are:



  • The Ganzo blade finally took an edge but the blade is starting to get wobbly. I'm not going to even play with that. Someone will get hurt.
  • The black HK has a nice action and lock but the size and shape of the blade makes the serrated edge a pain in the ass.
  • The CRKT KISS is just crapy quality
  • The CRKT Squid is nice all around except the edge. The Hallow grind sucks.
  • The Pazoda2 is too small for anything... anything that small and I'm going SAK Classic SD
  • Promithi's quality is the worst. I'm not sure it makes a good bottle opener since there are so many other ways to do that.
What remains is two SAK SDs, a SAK Hunter Pro, and a SAK Farmer. At the moment the Farmer is my favorite except that I need a toothpick but it's not absolute. It is funny that that which remains are only SAK.

They make a good knife and I want more.

SAK = Swiss Army Knife - usually manufactured by Victorinox

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…