Skip to main content

LED bulbs the actual life

You're in the dark because the light bulb in the room has died and you're all out of spares. You head over to the local home or grocery store to get a replacement and you are face with an endless variety of shapes, sizes, wattage, lumens, incandescent, fluorescent, neon, and LED. The interesting thing is the prices are anywhere from $1.00 to $150.00 depending on the product's proximity to the front of the store and whether it is WiFi enabled and has multiple colors.

I do not remember when and if it's still enacted by incandescent bulbs were being taken out of circulation. And at the time of inflection the prices of the alternatives was crazy high. Now as things start to settle I have come to accept the fact that I will convert to LED. But there is one serious issue.

Look closely to the bottom left of the packaging above. "Last 22+ years" and "Lasts 10 years". There are 2 problems with this claim. [a] there is no way to guarantee the lifetime and in fact there is no such guarantee. [b] How would you know if it did not last 22 years? In the earlier model we accepted that the cheap price of the bulb meant that a replacement was $0.50 or less away. It was also reasonable to have a few dozen spares in storage. And in the case of an electrical storm replacing the bulbs would only cost $100 or less depending on the number of bulbs. My home requires 55 bulbs of different sizes, watts, and decor. At $5.00 a bulb that would cost about $300.

Still, the issue is that bulb lifetime is meaningless if there are no guarantees. So now what?

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…