Skip to main content

Mr Bumpy Lives

I do not know what made me think of it ... I was in the garage just looking around and I did not see anything in particular. Maybe I was thinking of simpler times...

I was late to the dot-com thing... and I was late to the unix thing... and I was late to the silicon valley thing.

The startup I worked for could not decide who it's customer was and how it was going to make money. It took a great deal of time for them to figure it out and in the end we could have done much better but the chasm between senior management and the people who got them there grew.

I had no management training and I never had a mentor. I learned by watching my manager and by treating others as I wanted to be treated. I also interviewed a lot. I stumbled upon the Silicon Valley method of stupid question interviewing after visiting Amazon about 25 years ago.

While I was an OS/2 user and like the early Macs; OS/2 was long since dead and the Mac was still too expensive. I was just starting to get into Solaris and then I had Slackware Linux running on a pocket sized Sony laptop. I had heard about linux sysadmins giving themselves silly alias or usernames. I happened to watch an episode of "Bump In The Night" and I liked the Mr Bumpy character... So everything I did was attributed to that alias.

Just like the dot-com that passed me over, so did my interest in aliases although my Indian Princess name is Chief Gummy Bear and I thought I would use it as my trail name. OS/2 is not quite dead yet but there isn't much interest. It is the sort of thing that textbooks will be written and studied. Sadly while Linux/BSD have been my thing for over 25 years by now it is sub-optimal. Systems like erlang on xen seem to be the way to go.

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…