Skip to main content

what is in your wallet?

I'm starting to think that preparing for hiking a segment of the AT is more like motorcycle maintenance than what I thought it was going to be. Recently I posted a comment on a hiker's gear review:
Looks like you have traded some big money for lightweight. But you've got some comfort items too. In the last month my AT segment pack has evolved from all the comfort of tenting in the backyard to sleeping under my poncho on a garbage bag. I've decided to partition my pack into 4 categories. Bindle (things I need), Survival (things for safety), Extra (just a little above the Bindle) and Luxury (something like a coffee press that takes me over the top). Things come in and out of my pack depending on the weather. Going north I do not need a puffy jacket until the weather drops to the 50 or 60s.
 What I think I have discovered is that this seems to be a metaphor for life. In my bindle might be 3 square meals a day, and my survival depends on my faith, extra items might be money to get the girls to summer camp and luxury might be a VW instead of a Yugo.  Of course these containers can hold things and thoughts.

One thing about a traditional hobo bindle is that it is characterized by a bandanna or handkerchief. And as such should hold the things we hold dear. As I look back on my yesterday I wonder if I'm carrying the right things in my bindle.

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…