Skip to main content

Ten Essentials

I'm not certain who "they" are but they made some recommendations pertaining to the top ten essentials. They also said that they were transitioning from specific recommendations to systems.

  • navigation
  • sun protection
  • insulation
  • illumination
  • nutrition
  • hydration
  • first aid
  • repair kit
  • fire
  • emergency shelter
I'm not sure what they are trying to protect themselves from. By including insulation and sun protection that might suggest a 4-season kit. By naming these systems they are leaving the actual selection up to you. Where I struggle with this list is the overlap with the 5-C's.
  • cut
  • cordage
  • cover
  • container
  • combustion
These are no less "systems", however, by saying CUT it's clear you need a knive, saw and/or an ax. A knife could be included but it's closer to 7 degrees instead of obvious. In the 5-C's cover starts with your clothes and expands out from there to include some sort of shelter.

I've been meaning to look into the 7-Cs.

UPDATE - I was watching ALONE Fan Questions and Alan, season 1 winner, was demonstrating how to get your bearing. He said all you needed was a straight stick, a couple of rocks, and time. (see the boy scout manual for the details) But made the point... if you're in survival mode then navigation like that may not be necessary. However, being able to read signs from a distance like a certain type of reed that is only present near water might indicate a river or creak is nearby.

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…