Skip to main content

Review: SOL Shelter Kit

The SOL Shelter Kit is a cost effective and almost complete shelter kit.  While the ziplock pouch includes [1] reflective plastic coated Mylar tarp [2] 4x 4" stakes [3] 4x guy lines; by itself and in bare terrain it is only useful as ground tarp. In order to make a proper lean-to or A-Frame you'll need additional gear.

  • at least 25" of cordage for a ridgeline
  • two trees or static objects within reach of the cordage; optionally trekking poles or some branches
  • 4 small pebbles for attaching the included cordage to the tarp
Needed some extra gear to deploy the lean-to



I think the overhang was a little too big but the height was 48".


Not sure what happened. This was just 5 minutes later. The tie-outs survived but the ridgeline fell over. There must be some sweet spot for the ridgeline preventing it from moving north or south. Optionally I could use a prusik knot and tension the tarp on the ridgeline which would extend to the north/south stability. However, after adjusting the ridgeline and poles things are holding.

NOTE: The small 4" C-stakes provided with the SOL are solid. There is something to be said for the torque I was able to get then the folded over portion of the stake was closer to the ground.

The SOL products are pretty robust but like any piece of kit you need to have the confidence that it will work ever time and that it will take an expected amount of punishment. If you depended on this tarp in a *cough* survival circumstance you better have some confidence how long it will last. For example I'd prefer to have gorilla taped reinforced grommets instead of stones as they are not always available and depending on the location the types of stones might have different effects on the tarp. Whereas a grommet would have a consistent effect and only add very minimal cost which I would gladly pay.


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…