Skip to main content

simple ground tarp setup

As I continue to test my gear and skills here is the ground setup I had in mind:

In the end I was able to reuse some stakes and reduce the number of guy lines.

UPDATE: adding a bugnet to this configuration means that I need 10x 5', 2x 10', and 1x 25' segments of rope to reduce the number of stakes. Then again maybe Shepard hooks would be better.

light weight and cheap reflective tarp.

I started by staking down the footprint to prevent it from blowing away. I spread the tarp over top and re-staked the head section. fabricated the ridgeline and then staked down the footer.

the lines at the footer are nearly 45deg 
The trekking poles are set to approximately 44in although I intended it to be 48in so I could sit upright at the foot.

plenty of room
Most bug nets are shaped like a pyramid assuming the head is below the peak. In this configuration the peak is by the foot but it should work if the netting is taught.

5 minutes of modest wind

Since I had recycled the footprint's stakes for the tarp... just 5 minutes later the footprint was a mess.

at 48 inches
I reset the tarp's ridgeline to 48 inches. At this height the tarp was a little less stable. To correct I moved the trekking poles toward the head and angled the ridgeline stakes further still. I also added small badge clips to the loops on the tarp. And then I added the bugnet.

In conclusion this setup did not take very long but there is a strong argument for deploying the tarp first and the footprint second so it might remain dry or at least less muddy. 48in is a nice height. There are still some on site issues like direction of the rain and if there is rain at all. One could argue against the bug net in winter except that there is some critter protection there too. And as for the rain there is nothing like a mylar blanket. The tarp is meant to keep the direct rainfall off your body and gear.

FAIL:

  • wrong size cordage - needed 25', 6x 3', 6x 10'.
  • although I deployed 10 stakes I could have used 2 more although cordage could have reduced that number
UPDATE: total weight was 1350g

UPDATE: the SOL version of this configuration is 250g lighter and packs considerably smaller.



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…