News for hackers. Stuff that matters.
Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by r4um on Thursday March 27, 2014 @12:54PM (#7481660)
Anyone using this in production yet?
Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by polvi on Thursday March 27, 2014 @01:18PM (#7481830)
Lots of people playing with it... it is in a similar state as Docker, in that it is "pre-production" but people ignore that...
Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by bashcoder on Thursday March 27, 2014 @04:14PM (#7483116)
I'm not, but I'm watching several of the Github repos and doing fresh EC2 installs and tests whenever they release a new version. I'm very much a fan of the project, but I would not use it in production at this point.

CoreOS is still alpha, which is exemplified in this release, which requires a fresh install and isn't upgradeable from the previous release with their auto-update feature.

Also the team is still working out where to put things, filesystems, and how to best integrate etcd, networkd, systemd, etc., with their fleet system for a fully automated, auto-scalable, auto-discovering, self-healing clustering system. All that stuff has come a long way in recent weeks, and I'm very glad to see a distro geared towards both Docker and clustering.

Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by lbotos on Thursday March 27, 2014 @02:07PM (#7482095)
I want to but I'm waiting until they at least hit "beta".

"During our alpha period, Chaos Monkey (i.e. random reboots) is built in and will give you plenty of opportunities to test out systemd." <- https://coreos.com/docs/quickstart/

Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by robszumski on Thursday March 27, 2014 @02:16PM (#7482193)
Totally understandable, but if you want to get started now, the chaos monkey can be turned off: http://coreos.com/docs/cluster-management/debugging/prevent-...
Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by lbotos on Thursday March 27, 2014 @02:22PM (#7482250)
You may want to clarify in the docs those steps will stop chaos monkey. As I read it, I understood it as it will keep me on a specific version of coreos not stop the chaos monkey. Am I misunderstanding?
Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by robszumski on Thursday March 27, 2014 @02:29PM (#7482323)
The "random" reboots are the update process completing. If there is no update available, your machine will not reboot. Following those instructions will still enable the update to download, but not to be applied until you choose.

Our release cadence through the alpha has been about once a week, so 1 "random" reboot a week.

Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by derefr on Thursday March 27, 2014 @02:22PM (#7482247)
So your system isn't Highly Available enough to survive random reboots, then?
Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by lbotos on Thursday March 27, 2014 @02:29PM (#7482318)
My personal server isn't, no. It's not "omg it's making me money critical" but it's also not a temp dev box. :)
Re:CoreOS Update: btrfs, docker 0.9, add users, writable /et... by derefr on Thursday March 27, 2014 @02:36PM (#7482395)
I guess I might be weird, but I love playing with HA distributed-failover tech for its own sake. fleetd means never having to say "oops, it crashed."

I almost think it's worth it to switch the Chaos Monkey's toggle around: disabled in dev, but enabled in test and prod, to ensure you're using http://12factor.net/ principles in your Docker containers. (I think Heroku does something similar by spontaneously killing containers every once in a while.)