Skip to main content

Deis 1.0.0 was released

I'm happy that the Deis team has decided to release their 1.0.0 offering. In many respects it seems a bit more polished than previous versions; and while I would prefer to write a rave review there are still too many things to hate. I've just looked at the Deis issues list and there are only 5 issues submitted in the last 24 hours. My personal experience suggests that either their user-base is low or version 1 has not been adopted yet.

Here is a list of the bugs I'm reporting:

  • no single installation path; all paths cross
  • in order to install deisctl with the curl | sh -s 1.0.0 command the user needs to run the command as the SUDO because the core user cannot create the /opt/bin.
  • the the sudo ln -fs command cannot be executed because the /usr/local... folder is readonly.
  • the output from the curl+sh command includes some console control characters that make reading the message difficult.
  • the documentation refers to exporting some values. These values are wrong.
  • it's easy to forget or skip the requirement to configure the DNS
  • deisctl install platform works ok but start times out.
The deis team probably thinks it's competing with the Google Kubernetes team, however, that could not be further from the reality. Kuberbetes is still young. Google is going after a different user with it's K8s platform... and frankly I think it's other GoLang and container offerings are stronger.

Deis, while it does not have a proper user interface is competing with


Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

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…