Skip to main content

hiking shakedown

Next weekend I'm going to do a shakedown hike to campground about 3 miles from my home. There is no doubt that I will look out of place in my community because hikers are not the sort of people you see every day and while there is a major highway that is the most direct route I'm going to walk through my community instead as it should be safer.

My back should be a little lighter in that I won't carrying as much food but until I determine if there is a water community water source I'll probably carry 2 days worth of water. I also won't need 4 days of socks and underwear, however, i will probably carry my saw and bushcraft knife so I can make a campfire. I will also have to select my shirt and shorts ahead of time so I can pre-treat them with permethrin.

Part of a 1 day shakedown is figuring out what the typical activities are going to be during the day.

  • wake up
  • breakfast
  • bio break
  • pack up
  • hike
  • check-in at the campground
  • camp shoes
  • setup camp
  • get water
  • collect tinder and wood
  • wash socks
  • tend the fire
  • make dinner
  • recharge electronics
  • treat blisters etc
  • read a book
  • sleep
  • repeat
One interesting thing about this suburban hike is that I won't be pooping in peoples' backyards. 

Next I need to anticipate some disaster scenarios for this hike:
  • rain - tyvek, rain gear, waterproof liner, pack cover, if the hammock is not protected by the tarp then consider the emergency blanket
  • spill my fuel or lose starter - eat dry food
  • damaged gear - gorilla tape
  • spill water - It's a bit early in the process to start filtering canal water. There is a store across the street from the campground
  • no fire material or starter - go without. It's Florida after all and we're in the 80s
  • get run over by a car - call 911
**I must keep in mind this is just an exercise. I'm not trying to find out what my tolerances are or to pivot into survival mode. If any of the critical systems fail then call it a FAIL and call for an extraction and try again next week

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…