Skip to main content

Not Cheap Enough - Google

Several years ago I purchased the domain and connected it to the free google apps offering... the domain was taken by a domain squatter who would not take my offer; but that's another story.

Now that Google is getting serious about their hardware support and closed the free google apps product Google is trying to entice me to move over to the paid google for work. (They also cal it Chrome for work).

I use my domain for both my family and work communication. Maybe I should have more than one domain but this is no different than using my cell phone for company business. The telco has not adequately solved the multiple phone number problem so why should I solve the same email problem. I have one phone number and one email address.

There are a number of good reasons to buy into Chrome for work although I've prefer Chrome for Home or Chrome for SOHO. Remote deactivate, unlimited data, kiosk and signage features, maybe even monitoring my kids. (they have iPads too and we just configured our "family sharing" feature and it's passable for now.)

I have 3 chromebooks, 4 chromeboxes, 4 chromecasts, 1 chromeaudio, 1 chromebit and 1 android phone. Between the Chrome for work and annual device licensing I'm looking at $1130. That just seems unreasonable.

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…