Skip to main content

The problem with patch Tuesday

I'm not sure what or went the origin of Patch Tuesday came about but the where is unmistakable. Microsoft. It's not a bad thing to patch a kernel or a whole OS this way, however, scheduling and actually deploying can be a challenge for most operations. By comparison CoreOS does not rely on the customer to perform the patch. CoreOS performs the patch, releases a new version of the OS, and pushes an update to the customer hardware which then installs the update in an A/B fashion.


** at about 18:00 the speaker makes the comment; if you think you are going to cherry-pick the patches you are [mistaken or maybe a fool].

** earlier in the presentation he talks about the "contract" the Linux Kernel has with it's users.

So my point... [a] Apple distributes patches periodically. Their quality is typically pretty good but the patches are certainly not weekly. Given the Linux mantra I might feel differently about this now. But it's an all or nothing proposition. [b] Microsoft pushes updates every Tuesday but the user can cherry-pick which patches to apply. This means that there is some combination of patches that will fail based on the complexity of it all. At least every Apple computer that is current has a very similar footprint.

The CoreOS plan to replace then entire OS means that cruft is not going to linger. But it also means a different OPS strategy is needed in order to minimize the interruption to the user. Which it probably a better problem to have.

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…