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

11–20 of 63 posts

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

#11

Post by wastedhours »

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?

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

#12

Post by STRML »

fsaintjacques wrote: post #3
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.

etcd is not a magical replacement for a configuration system.

Just curious - what do you see as its shortcomings?

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

#13

Post by kapilvt »

STRML wrote: post #12
fsaintjacques wrote: post #3

Earlier quoted context omitted.

etcd is not a magical replacement for a configuration system.

Just curious - what do you see as its shortcomings?

its not about its shortcomings, its a database. your saying it replaces chef and opsworks. you're missing a few pieces to make that picture.

ie. how do i update the load balancer as i add capacity to my web app, how do i setup a new db instance and open up the firewall rules to an app on a different host. etc.

docker, and etcd are both nice pieces, but they don't make a complete picture. nor does fleet imo.

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

#14

Post by gnepzhao »

kapilvt wrote: post #13
STRML wrote: post #12

Earlier quoted context omitted.

Just curious - what do you see as its shortcomings?

its not about its shortcomings, its a database. your saying it replaces chef and opsworks. you're missing a few pieces to make that picture. ie. how do i update the load balancer as i add capacity to my web app, how do i setup a new db instance and open up the firewall rules to an app on a different host. etc. docker, and etcd are both nice pieces, but they don't make a complete picture. nor does fleet imo.

+1

If you want to do orchestration of both the infra and the app, you need things like opsworks.

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

#15

Post by HorizonXP »

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 direct control.

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

#16

Post by waffle_ss »

STRML wrote: post #12
fsaintjacques wrote: post #3

Earlier quoted context omitted.

etcd is not a magical replacement for a configuration system.

Just curious - what do you see as its shortcomings?

For one thing, it's not production ready yet: https://github.com/coreos/etcd/blob/769c043537263dd5701f5254...

Another is that your configuration is wide open to every node in the cluster (e.g. your Web app's etcd client can read the key that stores the master database user password). Hope you never get hacked!

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

#17

Post by geerlingguy »

kapilvt wrote: post #13
STRML wrote: post #12

Earlier quoted context omitted.

Just curious - what do you see as its shortcomings?

its not about its shortcomings, its a database. your saying it replaces chef and opsworks. you're missing a few pieces to make that picture. ie. how do i update the load balancer as i add capacity to my web app, how do i setup a new db instance and open up the firewall rules to an app on a different host. etc. docker, and etcd are both nice pieces, but they don't make a complete picture. nor does fleet imo.

Don't forget Ansible; out of the box, it can perform pretty much any of the glue operations necessary to manage a set of containers and servers.

It's still pretty early, so much of the tooling will need more improvement before container-based infrastructure gets more mainstream (e.g. enterprise, smaller teams) uptake.

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

#20

Post by aduitsis »

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…

Similarly, I created a new coreos droplet just to play around, neglected to add the cloud_config yaml configuration. I couldn't find a setting to add it to the droplet afterwards.
Post reply on HN