Skip to main content

Solo Shakedown

I have not weighed my pack yet but I can already tell it might not be big enough.


Once I've added some snacks, water, and more fuel this pack is going to weigh more than I expected. This shakedown is going to be the first of many. It's not a question of getting stronger or endurance it's what most hikers call comfort. And yet many of my 3's and C's of Survival have not been packed.

I have a few of the Cs

Container - cup in my cook kit
Cordage - part of my hammock
Cover - liner, emergency blanket, rain jacket with hook, baseball cap
Combustion - fero rod

And I need some more

Container - 2x liter Smart bottles, 2x liter platypus bags, Renovo filter, water tabs, pack liner
Cut - Swiss Army Farmer, Mora 8" and a Silky saw
Cordage - 25' for bear bag
Cover - reflectix, sun screen, mosquito repellent, mosquito net, change of socks, tyvek, camp shoes
Combustion - lighter

and I have not decided if I'm going with ma pillow luxury item.

Looking at the contents of my 40L pack I've already seen some room for improvement.
  • the cook kit could use space better by using a smaller fuel bottle or a better pot
  • the big reflective tar is 10x10 and can be replaced with a piece of reflectix for the hammock or tyvek for the floor
  • the first aid kit can be repackaged in a Ziploc to save space and weight
  • only 1 microtowel instead of 2
  • stop treating the freeze dried food like gold and pack it smaller (beef mac n cheese did not fold well as there seems to be an inner pack)

Packing a little more creatively and I managed to get everything in with plenty of room for more.

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…