Skip to main content

Solostove Campfire

This is what a suburban campfire looks like:

It's a Swedish Torch(right) that I re-purposed as an anvil to process three segments of birch(left). I processed the wood, started a fire in my solo campfire, ate some toasted marshmallows.

My solo stove looked like:

It's the largest of the solo stoves and is great for 5-7 participants.  SUCCESS!!

In the meantime I learned a few things:

  • even though I made Vaseline and Cotton ball tinder I did not use it and I think I won't. Alternatively having unmodified cotton balls might have multiple purposes and separately hand sanitizer too.
  • skinning the bark from the birch logs and then igniting them directly with my steel worked perfectly. I had to remember to peel the coating from the rod and it still took a few strokes.
  • I had a made a featherstick just to test my Mora knife but it was ideal for getting the fire started.
  • At first my Mora hand ax seemed lite to the task but after getting into my rythm and some confidence it worked really well. I think my Schrade ax would have been too heavy and I would likely have tired quickly. (being in shape helps)
  • My mora knife was awesome. I never tried batoning or my Schrade full tang.
  • I never tried my fatwood; which I had tried last week.
I need to learn a little more about the Birch wood. It is supposed to have a resin in the bark that is good for ignition but I'm concerned about the health potential of the vaporized resin; if any. On the otherhand none of the OTHER wood offered by home depot offered their origin other than to describe it as hardwood without any indication of food safety.

Finally I totally underestimated the amount of time and energy it was going to take to process all that wood for 45 minutes of fire. Meaning I'd need a lot more more fuel for an evening of fire and at least double to make dinner for 4. I can only hope that there was also a proper campfire ring where I can make a Swedish torch.

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…