51–60 of 63 posts
Digital Ocean is doing lots of advertising but their servers are not holding the traffic.
I had my website hosted with them and I was literally unable to connect on it via SSH due to the low quality of their link.
I was disappointed with DreamHost, moved to Digital Ocean, now I am testing Linode.
This is exciting to me from a technological standpoint.
1. One of first large public projects written in Go (after docker) 2. One of the first large public projects using Raft. (consensus algorithm aimed to replace Paxos)
I am really looking forward to seeing how this project turns out. Personally, I wouldn't move any of my projects onto CoreOs for at least a few years.
Other than that, I always question how they plan to make money. Consulting model?
Marketing, marketing and marketing... Digital Ocean is doing lots of advertising but their servers are not holding the traffic. I had my website hosted with them and I was literally unable to connect on it via SSH due to the low quality of their link. I was disappointed with DreamHost, moved to Digital Ocean, now I am testing Linode.
Earlier quoted context omitted.
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…
CoreOS is not a drop-in replacement for Ubuntu; migrating to it requires re-deploying your services inside Docker containers. I would think you might want to run your service implementations in parallel and then cut over later. Can you not move IP's between Digitalocean droplets?
Marketing, marketing and marketing... Digital Ocean is doing lots of advertising but their servers are not holding the traffic. I had my website hosted with them and I was literally unable to connect on it via SSH due to the low quality of their link. I was disappointed with DreamHost, moved to Digital Ocean, now I am testing Linode.
Also whilst you are testing Linode have a look into their behaviour the last few times they were hacked. They deliberately withheld information from their customers. Pretty despicable company if you ask me.
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.
For what use case? Doesn't using Docker for everything take you into 'golden master image' dead-ends, as outlined by the Opscode guys in comments to a Docker blog post last year [1].
What Lamont and Joshua had to say in that thread resonated, but I haven't really looked into DevOps approaches with Docker.
I'm also not sure what you mean by 'endless Ruby Chef scripts'?
[1] http://blog.relateiq.com/why-docker-why-not-chef/#comment-43...
Digital Ocean doesn't load the kernel from the current system image, but instead uses a prestored external kernel associated with the image. This means that upgrade to the kernel from within the droplet (e.g. distribution security updates) are ignored (See http://digitalocean.uservoice.com/forums/136585-digital-ocea... ). There is a workaround using kexec (see https://www.alextomkins.com/2013/11/digitalocean-debian-k…
Digital Ocean doesn't load the kernel from the current system image, but instead uses a prestored external kernel associated with the image. This means that upgrade to the kernel from within the droplet (e.g. distribution security updates) are ignored (See http://digitalocean.uservoice.com/forums/136585-digital-ocea... ). There is a workaround using kexec (see https://www.alextomkins.com/2013/11/digitalocean-debian-k…
WHAT?? They still haven't fixed this? Unbelievable.