Skip to main content

Collision of ideas

blah blah blah bushcraft... blah blah blah camping... blah blah blah living with a SEAL.
Last night I was running reports and while the reports were running I watched some videos from "homemade wonderlust". It's not the first AT (Appalachian Trail) video I had watched but it was the second presenter. The first video was gear, then hygiene; which was more about pooping on the AT, and the last few were about just hiking away. The other presenter was telling a broader story and HW was telling a personal story.

In both videos I noticed a few things. These hikers have made interesting choices when it comes to cost, weight, and space. For example the Big Agnes tent is just about 2lbs but costs about $450. On the other hand using an aluminium cook pot with a home made cozy instead of a titanium pot. While there must be some knowledge acquired when in the action but common sense suggests that there is an advantage in fuel savings by using freeze dried meals instead of carrying the fuel needed for actual cooking.

Assuming 15 miles a day and 2300 miles I thing that's about 153 days. Assuming a mix of provisions where at least one meal a day were freeze dried that's about $1500; assuming that it costs $10 per meal and frankly it does not. One complaint about freeze dried means was that a pouch might represent 5 meals and in terms of calorie count and cost it was a little off-putting.

The one remarkable thing was WL's drive. And that is how I connected with Living with a SEAL. From what I can tell, WL did what she needed to do. Whether it was one food in front of the other, reducing swelling by putting her feet in a creek, or detouring home to quickly bury her late dog. Maybe some day my daughter's will read this and see those accomplishments as a role model.

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…