Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

techcrunch.com

Post reply on HN
Print view View original

21–30 of 63 posts

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#21

Post by waffle_ss »

This image uses the CoreOS Alpha channel, which is not supposed to be used for production[1]. It "closely tracks current development work and is released frequently" so I would be using it with the knowledge that things might break. In other words, CoreOS on DigitalOcean should only be used for trying out CoreOS and not for running production apps (for now). But if I were going to do that, there is already a Vagrant setup[2] that is super easy to use. Hopefully DigitalOcean will provide a CoreOS Stable image soon.

On the subject of DigitalOcean images, there was a severe Docker bug[3] the last month or so that made Linux kernel 3.15 unusable. Linode let me easily select a 3.14 kernel to use for my host OS to get around the bug, but DigitalOcean doesn't have that level of granularity. So DigitalOcean either needs to provide more fine-tuned configuration of images or provide a CoreOS Stable image before I would think of using it for production Docker containers.

Finally, CoreOS is still an enormous pain[4] to install on Linode, so I hope this gives Linode a strong nudge to make it easier to install there.

[1]: https://coreos.com/releases/

[2]: https://coreos.com/docs/running-coreos/platforms/vagrant/

[3]: https://github.com/docker/docker/issues/6345

[4]: http://serverfault.com/a/620513/85897

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#22

Post by drcode »

wastedhours wrote: post #11
STRML wrote: post #2

This is actually really big news for anyone running or interested in running a Docker-based PaaS system such as Deis or Flynn. DigitalOcean's cheap instances are a great match for Docker containers. As of Deis 0.8.0 it only runs on CoreOS, and I believe most other DIY PaaS systems are moving the same way. IMO Docker + etcd is a far more sane configuration than endless Ruby Chef scripts, or worse, Amazon OpsWorks.

I'm really out of touch with Docker and CoreOS, so please forgive my ignorance if this is a ridiculous Q: could this combo be used for spinning up machines with specific apps for thin clients? Or is it more about scaling one app?

Essentially it lets you run 20 super-lightweight VMs on a single machine... Each one of those could be running different apps, and Docker makes it really easy to build a custom machine image using a single script (called a Dockerfile) using any standard linux OS as a base.

So yes, powering 20 thin clients running different apps from a single server is a perfect use case.

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#23

Post by andrewsomething »

cdnsteve wrote: post #18

So this means DigitalOcean, when running CoreOS via Docker for your deployment, means you no longer need to worry about OS level updates? Is this now handled by DigitalOcean?

Droplets running CoreOS will receive automatic updates through the normal CoreOS update service.

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#24

Post by lsllc »

waffle_ss wrote: post #21

This image uses the CoreOS Alpha channel, which is not supposed to be used for production[1]. It "closely tracks current development work and is released frequently" so I would be using it with the knowledge that things might break. In other words, CoreOS on DigitalOcean should only be used for trying out CoreOS and not for running production apps (for now). But if I were going to do that, there is already a Vagrant…

Vultr have supported CoreOS for a while (and FreeBSD!)

https://coreos.com/docs/running-coreos/cloud-providers/vultr...

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#25

Post by andrewsomething »

waffle_ss wrote: post #21

This image uses the CoreOS Alpha channel, which is not supposed to be used for production[1]. It "closely tracks current development work and is released frequently" so I would be using it with the knowledge that things might break. In other words, CoreOS on DigitalOcean should only be used for trying out CoreOS and not for running production apps (for now). But if I were going to do that, there is already a Vagrant…

The Alpha channel contains some work to interoperate with the DigitalOcean metadata service properly. CoreOS promotes images roughly every two weeks. So in that time, the first Beta will become available on DigitalOcean and about two weeks after that the Stable channel will be available as well.

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#26

Post by wastedhours »

drcode wrote: post #22
wastedhours wrote: post #11

Earlier quoted context omitted.

I'm really out of touch with Docker and CoreOS, so please forgive my ignorance if this is a ridiculous Q: could this combo be used for spinning up machines with specific apps for thin clients? Or is it more about scaling one app?

Essentially it lets you run 20 super-lightweight VMs on a single machine... Each one of those could be running different apps, and Docker makes it really easy to build a custom machine image using a single script (called a Dockerfile) using any standard linux OS as a base. So yes, powering 20 thin clients running different apps from a single server is a perfect use case.

Great, thanks for that! Not a sysadmin by trade so didn't know whether I'd misinterpreted how it worked.

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#27

Post by totallymike »

cdnsteve wrote: post #18

So this means DigitalOcean, when running CoreOS via Docker for your deployment, means you no longer need to worry about OS level updates? Is this now handled by DigitalOcean?

CoreOS has a pretty great update mechanism. You can read about it here: https://coreos.com/using-coreos/updates/

In short, CoreOS maintains two OS partitions, A and B. When an update is available, it is automatically downloaded to the B partition, and upon reboot the B partition becomes active, effectively rotating the partitions.

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#28

Post by raiyu »

kapilvt wrote: post #19

one nice unrelated thing that didn't make any of the blog posts, digital ocean now supports userdata when launching instances via console or the api! but it looks like they still need to update their other os images to install cloudinit.

When we began the work to integrate with CoreOS we saw that it was a perfect opportunity to build out the metadata service, which is why we decided to delay that initial launch until we rolled out this service.

After we've had a chance to work through some of the bugs that customers will uncover that we've missed in our testing we'll move forward to updating the rest of our images for this new metadata service and launching it publicly for production consumption for all customers.

Thanks

Re: DigitalOcean Partners with CoreOS for Large-Scale Cluster Deployments

#30

Post by [deleted] »

HorizonXP wrote: post #15
beigeotter wrote: post #10

You can find the DigitalOcean tutorials on using CoreOS here: https://www.digitalocean.com/community/tutorial_series/getti...

This was useful, as I couldn't figure out how to add the cloud-config files I use for my Vagrant-base CoreOS cluster. Here's another question: If I have a droplet up and running already, anyone know how I might change it from Ubuntu to the new CoreOS image? I'd rather change it than create a new one to maintain the same public IP, or else I have to have my DNS records updated, which takes time, and is outside my dire…

[deleted]
Post reply on HN