I just wish there was a bit more people testing CoreOS on bare metal with PXE. There are pretty decent docs on it:<p><a href="https://coreos.com/docs/running-coreos/bare-metal/booting-with-pxe/" rel="nofollow">https://coreos.com/docs/running-coreos/bare-metal/booting-wi...</a><p><a href="http://coreos.com/blog/boot-on-bare-metal-with-pxe/" rel="nofollow">http://coreos.com/blog/boot-on-bare-metal-with-pxe/</a><p>But I've not heard a lot from people with clusters of them. Perhaps I'll have to snag a small cluster of lab boxes and give it a go myself!
This is an especially exciting time for container visualization, considering Docker has their first 1.0.0 release candidate. (Docker 0.11)<p>I hope the CoreOS team manages to reach what they would consider a "stable, and production ready version of CoreOS" sometime around (after, but around) when Docker 1.0.0 lands.
CoreOS is awesome and "makes you do cloud right" by forcing you to do things like make sure your app can die and restart cleanly and make you store your data in a resilient way.<p>I'm super excited by this release and look forward to this shaping the way people do cloud.
Does anyone know of a tutorial on how to easily get, for example, a Django app (nginx + uwsgi + postgres + redis) running on CoreOS with Docker? I'm afraid all these parts of the stack are too many to wrap one's head around without being familiar with each layer.
Locksmith looks awesome. Is there a way for services to cause their node to retain its lock for some time after a reboot, for example to allow replication to catch up or similar?
What hoops do you have to do to download a release of this system? Either I'm blind (very possible) or you either have to join their developer network, pay them or build it from scratch on github?
I use CoreOS for my research, VM allocation problems, and it works well when I send them jobs via Docker HTTP API, it is easy to maintain them, it works fast. Hope to see final soon.