Skip to main content

Day Hike to Robert's Lake in Big Cypress - Gear

Heading out on a day Hike tomorrow to Robert's Lake in Florida's Big Cypress. I've hiked with these guys before and they go SUL because they know exactly what and where they are going. Last time I brought a hammock and rainfly and I never opened them up, The same for other food and supplies. This time we are looking at almost 8 hours on the trail with a stop for lunch.


The gear from right to left.

  • sitting/kneeling pad
  • 9oz hammock with webbing cinch straps
  • head net
  • SOL shelter
  • SOL poncho
  • fire kit - SAK, juke twine, dryr lint
  • cook kit - Stanley with 1 cup, Olicamp ION stove, 4oz canister fuel, fero rod
  • clothes - change of underware, socks, shirt
  • food - poptarts, peanut butter bars, Mac n Cheese, mashed potatoes
  • small folding chair
  • saw (doing some trail maint.)
  • gaiters
  • DIY hydration tube
  • first aid and water kit
  • headlamp, whistle, compass
  • cone hat
  • bandanna
  • schemog
It's under 10 pounds but I think I can lighter. One thing I have not checked on yet is just how deep the water is where we are going. That would help me decide on the right pack. I could also leave the stove behind.

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…