clocker

The end-price of a single Clocker device to the client is ~10$ (depending on amount).

The bonus is, that the fewer cores are clocker higher, becuase they still have the same temperature budget as the higher models.

My experience is that a skilled clocker can have 10ms precision if you take away the reaction times.

Of course, Clocker supports pluggable SDN providers so if your networking demands are not met by Weave you can change to another provider.

The paper is mostly ephemeral I find the things I want to look back at historically are what I did when which is in clocker, old scribbles are just that.

The latest version of Clocker does support Calico as well, now!

Just came across this app called Clocker and started using it.

See my comment on TAForObvReasons - If you invest in a Safari Content Clocker that allows custom rules, you can effectively do the same thing as a hosts file.

It is very, very unfortunate Clocker doesn't document how to not use Weave (for example, simply use whatever is already in place) as the rest of Clocker rocks, and the seemingly hard dependency on Weave makes it un-deployable for serious production use.

At the moment, Clocker can deploy a Kubernetes cluster with an HAProxy load-balanced set of masters and an auto-scalable cluster of workers, using Canal (Flannel and Calico) [3] for networking.

For the Kubernetes cluster deployment in Clocker [1] we use the features of Apache jclouds [2] and Brooklyn to support pretty much any cloud, public or private.

I've been looking for a way to build in support for networking between Docker hosts in my clocker.io software, to simplify deploying applications into a cloud hosted Docker environment.

- Clocker: Easy way to keep track of your friends and colleagues in different time zones.

Clocker (Clojure), Focker (F#), Rocker (Ruby)...

For those on macOS, I use the app Clocker[0].