alauda

Check https://github.com/hyperhq/hykins

It's an OSS, so guess the first step is to build the technology, then licensing.

Video is here: https://www.youtube.com/watch?v=JCldsRNuGkc&feature=youtu.be

Having a CLI doesn't mean they are close. In Google cloud, you still work with VMs, cluster, schedulers. In Hyper, you work only with Docker, everything is container native!

Per-second is perfect for Serverless, Data mining, CI/CD, etc. It is simply not cost effective to go with per hour/minute rate.

Why "low traffic sites"?

The bigger sizes? Yes, but the small ones work pretty sweet. And the per-second billing!

Had you tried hyper.sh? All you need is the compose file, no more terraform and ansible.

Checkout https://github.com/jenkinsci/hyper-slaves-plugin. This plugin will launch your buildjobs as on-demand containers in Hyper.sh, then you don't even need the long-running huge VM!

Guys, you really want to give a look to hyper.sh, if you are frustrated with running containers in production.

Take a look at hyper.sh, if you are using docker.

The idea of Swarm is the cluster works like one single virtual host. In that case, checkout hyper.sh. You don't care about the cluster thing at all in it, because their entire cloud works like one host.

What do you mean "configure Docker"?

Check out hyper.sh. They allow to launch a Docker image in ~3-5s, without the need to maintain a VM cluster. You can use an API service to automate the provisioning, and then forget about the infra thing.

I don't think rkt is a valid candidate. People are already used to the basic of Docker command. There is no reason to change to something else. If rkt decides to reproduce the feature set, how is that different from a fork?