fleet

systemd-fleet, by the original CoreOS folks. https://github.com/coreos/fleet I used this when it was brand new for a bit and it was so incredibly smooth and worked so well. It solved the problem of controlling systemd units remotely so well. I'm pretty sure the only reason it never actually took off was kubernetes and coreos's acquisition, however it actively solves the 'other half' of the k8s problem which is managing the state of the host itself.

Funny, because when we built Fleet (https://github.com/coreos/fleet/) Kubernetes didn't exist.

https://github.com/coreos/fleet I feel like fleet deserved more of a shot than it ultimately got.

This made me remember Fleet[0], which I used in the past on CoreOS. It was a very good abstraction for my simple cluster. It felt as robust as a managed cloud service. It's a shame it didn't catch on (and also what happened to CoreOS). [0] https://github.com/coreos/fleet

We were working on this at CoreOS before Kubernetes came about – called fleet https://github.com/coreos/fleet. Distributed systemd units run across a cluster, typically running containers or golang binaries with a super minimal OS underneath. I always thought it was cool but it definitely had its challenges and Kubernetes is better in most ways, IMO.

Like https://github.com/coreos/fleet?

Figure out how to revive https://github.com/coreos/fleet as something native in systemd?

What you describe is essentially the original CoreOS fleet[0] project. It's distributed systemd init files. [0] https://github.com/coreos/fleet#fleet---a-distributed-init-s... I find it ironic half of k8s mojo, etcd, came out of this project as well.

This is roughly correct. The README says it best: https://github.com/coreos/fleet#current-status Also, as you mention there are very compelling reasons that when Kubernetes came on the scene 2 years ago we started contributing heavily instead of trying to compete. We started to say something with fleet and Kubernetes completed our sentence: https://github.com/coreos/fleet/blob/master/Documentation/fl... Overall, we recommend everyone use Kubernetes as the way to orchestrate containers.

Sorry I wasn't clear. That's exactly the advice. Design systems so that they can crash harmlessly in the small, and availability and scalability come to you quite naturally. I agree the (distant) second best alternative is to do as you suggest: to try to rely on a paxos implementation that keeps a stable leader and tries to keep track of liveness. That's pretty hard too! Besides all of aphyr's jepsen test series, check this shit out: https://github.com/coreos/fleet/issues/1289 . Tough! Tough even when you think you know what you're doing. And of course no help against freak occurrences where you can't elect a stable leader any more, or you flap leaders, or the election gets stuck. Currently the only known-good implementation of raft is in Idris. Do you know Idris? I sure as hell don't. Fortunately I know ants. Ants can die in g

I'm not a sysadmin but recently started using CoreOS to deploy small web apps. Could anyone explain to me like I'm 5 what's the difference between those cluster schedulers and something like CoreOS' fleet (https://github.com/coreos/fleet)?

CoreOS already has a project named Fleet[0]. [0] - https://github.com/coreos/fleet

Yea, I absolutely want to make the spec a schema once we get further along. We would have done it from the beginning but it makes discussing the spec a lot harder since it raises the bar from "I understand JSON syntax" to "I understand JSON and JSON Schema". In any case I am a huge JSON schema fan, we use it in a number of APIs to make client bindings code generated. For example: https://github.com/coreos/fleet/blob/master/schema/v1.json Update: Sorry, I thought you were taking a look at the appc spec, would appreciate your feedback on appc too.

"the problem of orchestrating a bunch of Docker machines is still unsolved." I don't know about that. Mesos was already mentioned: http://mesos.apache.org/ There's also Kubernetes which has recently started working on Fedora and CoreOS: https://github.com/GoogleCloudPlatform/kubernetes And there is CoreOS's fleet system, although this is more low level and would still need orchestration: https://github.com/coreos/fleet