Digital Ocean now offering Core OS.



  • The newly available image, currently based on the CoreOS alpha channel, provides developers with the ability to quickly build server clusters and effortlessly deploy their applications in a fault tolerant manner.

    Users can leverage docker containers to distribute applications throughout their cluster easily, and any single node can manage the entire cluster. Additionally, CoreOS features automated OS upgrades that ensure safe updating of the host system and allow for rollbacks if needed.

    Who's doing the guide for this one? 😛



  • Wonder if CoreOS can be used to run a dual-NodeBB setup, with one instance being a dev environment and the other being the production environment, and then switch between them as needed with updates and stuff.



  • @luke said:

    Wonder if CoreOS can be used to run a dual-NodeBB setup, with one instance being a dev environment and the other being the production environment, and then switch between them as needed with updates and stuff.

    Would be good if it could. 👍



  • @luke said:

    Wonder if CoreOS can be used to run a dual-NodeBB setup, with one instance being a dev environment and the other being the production environment, and then switch between them as needed with updates and stuff.

    This is actually a good idea. Reminds me of Heroku's Postgres db forking. If this can be done (through some magics and with the help of pixie dust), our NodeBB installation should (virtually) have no downtime.



  • @aixnr said:

    @luke said:

    Wonder if CoreOS can be used to run a dual-NodeBB setup, with one instance being a dev environment and the other being the production environment, and then switch between them as needed with updates and stuff.

    This is actually a good idea. Reminds me of Heroku's Postgres db forking. If this can be done (through some magics and with the help of pixie dust), our NodeBB installation should (virtually) have no downtime.

    NodeBB has no downtime on 0.5.1 due to a reload feature that doesn't require a restart. 👍



  • @a_5mith Even if you need to update NodeBB?



  • @luke said:

    @a_5mith Even if you need to update NodeBB?

    Believe so. Taken from this blog post

    I'm glad to say that I did end up figuring out the second problem, and NodeBB now comes with a "Reload" functionality in addition to the existing "Restart":

    The results?

    • Reloads are now transparent and do not kick existing connections off. Admins used to be afraid to swap plugins because a server restart incurred downtime. Not anymore!

    • Occasionally, incompatible plugins break NodeBB. The new reload system will catch errors as they occur, display them to the admin, and continue serving the old assets, meaning NodeBBs will no longer be left dead in the water when a plugin breaks.

    • End users won't notice a reload, as connections are maintained. Restart downtimes are reduced to near-zero, as a parallel instance is started and seamlessly switched over when ready.


Log in to reply
 

Suggested Topics

| |