4 ms·

Anyone using this in production yet?

by r4um 13y ago

polvi 13y ago
Lots of people playing with it... it is in a similar state as Docker, in that it is "pre-production" but people ignore that...
lbotos 13y ago
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/ https://coreos.com/docs/quickstart/
- derefr 13y ago
  So your system isn't Highly Available enough to survive random reboots, then?
  - lbotos 13y ago
    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. :)
    - derefr 13y ago
      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/ http://12factor.net/ principles in your Docker containers. (I think Heroku does something similar by spontaneously killing containers every once in a while.)
- robszumski 13y ago
  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-reboot-after-update/ http://coreos.com/docs/cluster-management/debugging/prevent-...
  - lbotos 13y ago
    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?
    - robszumski 13y ago
      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.
bashcoder 13y ago
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.

Anyone using this in production yet?

by r4um 13y ago

Anyone using this in production yet?

polvi 13y ago

Lots of people playing with it... it is in a similar state as Docker, in that it is "pre-production" but people ignore that...

lbotos 13y ago

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/ https://coreos.com/docs/quickstart/

derefr 13y ago
So your system isn't Highly Available enough to survive random reboots, then?
- lbotos 13y ago
  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. :)
  - derefr 13y ago
    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/ http://12factor.net/ principles in your Docker containers. (I think Heroku does something similar by spontaneously killing containers every once in a while.)
robszumski 13y ago
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-reboot-after-update/ http://coreos.com/docs/cluster-management/debugging/prevent-...
- lbotos 13y ago
  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?
  - robszumski 13y ago
    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.

bashcoder 13y ago

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.