Skip to main content

"survival" - you don't know the meaning of the word

I went for a day hike with some friends. It's round trip is about 5 miles but the water level is everything from 6 to 32 inches deep. NO DRY LAND TO BE HAD.



I woke up at 0500 and headed to the ranger station. While I waited for Tom and Bill to arrive I ate, drank water, refilled my bottles and went to the bathroom. We finally got on the trail at 0800(just after sunrise) and you'll see later that we got off the trail at 1715 (just before sunset).

Technically we walked south 2.5 miles and then back; as Tom describes the effort it was like hiking 15 miles. Along the way we had many encounters:
  • big birds and little birds
  • alligator turtle
  • one alligator in our path.... twice (same alligator)
  • 4-5 alligators at Robert's Lake
We also rested and ate lunch at the Kayak Campground, it's unofficial and under water.

"survival"
  • the soles of my boot came off. We spent 2 hours cumulative repairing them
  • I had finished my water with 200 yards left in the hike
  • I did not eat enough at lunch break
  • my right leg cramped on the trail
  • toes cramped all day long


We exited the trail at sunset. Any longer and we would have been using headlamps. With 1.5 to 2 miles left in the hike (just after the first boot failure) I started to mentally go through my gear for a "survival plan". And there is nothing that any of those "I'm a survivalist" was going to make this a success. Instead it was "Living with a SEAL" that won the day.

But like they say in the movie Frozen.  It was the best day ever. And it was the hardest physical experience of my life.

UPDATE: the hat seemed like a good idea at the time but it practice it was not.

UPDATE:  My android phone tracked my every step:
overview - ranger station to roberts lake

The area around the lake

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…