Skip to main content

When a ridgeline isn't

In a previous post I was having trouble with my ridgeline.

After a short period the center started to sag but then I did some lite reading and discovered a few improvements.

  • lay the tarp put
  • set the initial position of the stakes under the tarp (presumably under the corners)
  • loosely secure the tie-outs
  • deploy the ridgeline
  • secure the tarp over the ridgeline
  • and done...
But I still had some sag. 

So I moved the stakes out in order to get some east/west tension. I also tried making the lines more taught. But it still sagged.  Since the last thing I wanted to do was a prusik knot on the ridgeline that's exactly what I did.

I still hated using a rock but one thing was clear. Grommets mean that my solutions might be limited to how the grommets function or the options they give me. In this case the tarp is going to take a beating but I can convert my lean-to into an a-frame fairly easily. And if I had grommets I might not consider that that was an option if the grommets were in fixed positions.

There is still room for improvement. The tension is not equal on all sides.

One other thing to note. The prusik knots would not have been possible if I were not home with a box of cordage. So it would be a good idea to take some extra cord with me wherever I go.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


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…