Skip to main content

Hennesey Snakeskin and an ENO DryFly

Initially I was not very happy with this recommendation. My ENO DryFly is not one of the biggest they offer but at the time I was OK with it. When I doubled checked the dimensions I wanted a larger fly but in hindsight this one will be sufficient.


Hiking the AT I wanted a tarp that would double as a ground shelter in case I was force to seek shelter in a non-optimal location. For the same reason a hammocks should leave a smaller footprint.


I did not realize that the package was going to come with two skins and for a moment I thought I had order too many. After watching a hennessey hammock setup I realized I was supposed to use both tubes.



This was a pain in the ass because the cords were still bundled and I had not "pre" organized the tarp so sliding the skins was a pain.


Finally I had to lie one end to a chair. This made some steps easier. I do not think it's going to fit right until I complete my shakedown. Looking here it seems that the working ends of the tarp provide some compression but I don't think it's going to get to the size of the ENO stuff sack.

Before I made my purchase I had emailed the support team at ENO and they recommended the Hennessey skin. XL. Until that last eureka moment I was still pretty pissed at them. In the end it seems to have been the right purchase even thought the documentation let me down and the same for Amazon. (Thank you youtubers)


PS I tried to skin my ENO doublenext hammock. That was a bit of a disaster. [a] the skin was not long enough. [b] the bundle near the carabiner was too tight for the end. [c] using both skins would have been a waste. [d] the compression sack does a better job compressing the hammock.

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…