Skip to main content

Why do you want to walk the AT?

There are several interview vlogs where the interviewer asks hikers why they are hiking the AT. The answers vary.

  • walking to school in the north east
  • trying to find myself
  • trying to hid
  • because it's hard
  • because it's there
and so on.

In the meantime I have been thinking about my own reasons for want to hike the AT. At first it was to completely disconnect but then I started to watch gear reviews and everyone seems to have an iPhone. So I gave up on that idea... even with a few dead spots I imagine it's not complete. Carry a big enough battery and making it between cities or towns is a snap.

And then I was thinking about my gear. I've been flopping between a tent and a hammock. Without having been on the AT I have no idea which is better for the task. I imagine that there are pluses and minuses depending on the exact time of year and the type of weather I might encounter. As I emerged from that part of my internal conflict I realized I was only going to be on the trail for 3 to 4 days and so anything goes. I need only the barest of essentials and after that it's luxury.

The essentials for 3 - 4 days in Georgia in the summer
  • clean water
  • simple food high in calories
  • basic shelter
I think we can live in the same underwear for 4 days.

While I was no closer to deciding on tent vs hammock I kept searching and just today I made the final tip toward a hammock. I had decided to buy an ENO but had not puled the trigger. The price was OK but then as I started to add the accessories the price started to climb again. I started to learn about whoopie slings and hand made webbing and I was back on track.

One ENO vs Hobo video and I was ready. One blog about the Bindle and I was sold. I don't know what my AT mission is anymore. I thought it was unplugging. Maybe it wpuld be nice to be ALONE for a short time to collect my thoughts. It could be that I'm looking for a way to recharge my reserves. And it could be that I just need to wipe the turd from my shoes.

But the metaphor that bindle represents for Jake is also the physical manifestation that I need to survive for 4 days. And when I finish I hope to see what he sees.

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…