Skip to main content

hiking gear - size and weight maters

Three things I like about SOL gear is that it's light, compact, and inexpensive. Generally speaking; one recurring complaint I have about most gear sites is that although they might get the size or weight right. At least there is no way to know what things are until you've actually help them in your hand.

left: This SOL blanket is light and packs small. It could fit in a front or rear pocket nicely.
center: The SOL Sport Utility Blanket is also small and it could fit in a cargo pocket.
right: The Snugpak Stasha is the same size as the others, however, folding is not recommended as it will compromise the fabric and even so it does not fold to the same as the SOL. It's also heavier and more expensive.

left: the SOL emergency bivy can actually be folded to half it's size.
inside-left: the SOL emergency bivy XL
inside-right: SOL thermal bivy
right: 2gosystems bivy - very heavy and huge.

The truth in the matter is more noticeable in the ponchos.

left: SOL poncho with thermal reflection material (embrace the rain but stay warm doing it)
center: sea to summit ultra-sil tarp poncho - expensive and delicate
right: although this is the same bivy as above the 2gosystems-BOB is actually about the same size.

Popular posts from this blog

Prometheus vs Bosun

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


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…