Deploy to physically separated hardware
If you have MySQL with master-slave setup and both are on the same physical host, you're totally screwed when there is a hardware failure - both master and slave are dead and there's no point in even doing replication.
Or, if you have 2 Rails application servers and they are on the same host, it's an SPOF.
In other words, whenever you have multiple droplets in a project, you need to confirm if any combination of droplets are on the same host or not.
Right now, we have to write a support ticket to confirm if those droplets aren't on the same host. But it's been quite a hassle to do so, as all of our servers need such a redundancy.
It would be great if there's a self-service way to verify that ourselves. Or better yet, offer a way to explicitly create a droplet on a different host.
Right now, some customers might be at risk that unknowingly have multiple droplets on the same host and learn the hard way when it goes down, that it had been an SPOF. Nobody wins from this.
This feature will save time for both customers and DO support staff. Win-win.
For the record, Linode offers this by showing the host name (like newark313) on the dashboard.
Can you add some sort of underlying host identifier to the droplet info in the ui and api so that I can know which of my droplets are on the same underlying hardware object.
Id like to make sure that I dont deploy multiple web server nodes on the same host etc, in case there is ever a host issue, it would only effect one of the droplets
I really need this, it's a pain to keep asking if my new droplets are on the same physical hardware every time :(
+1 - Multiple zones within the same region seems like a good idea (NY1, NY2, SF1, SF2). But at least having the ability to see the physical host or force a different physical host would be great. For now I will have Web and SQL droplets in NY and SF for redundancy.
Now I have to put the master in SF and the slave in NY to just ensure they are not physically together.
Jeffrey A. commented
Would love to see a reply from DigitalOcean on this.
Justin Keller commented
Have your create algorithm automatically do this, and show the host machine under each droplet.
Nick Walke commented
This along with multiple IPs, and elastic IPs, are keeping DO from getting business class customers. I can't refer any of our clients to DO because of this.
Any updates from DO?
Alice Bevan-McGregor commented
Trevor Kensiski commented
Linode also by default puts you on separate hosts, its how they designed their systems.
I agree, we need this functionality to be default. There are some cases where I wouldn't mind if the machines were on the same physical box. (2 separate projects and there is overlap of projects on the same host). But each of my projects need to be on separate physical machines.
I know it sucks, being the new guys on the market, but the top dogs (Linode, Rack Space, Liquid Web, Amazon all provide this feature as well as multiple other ones that we are all requesting *cough* floating IP for host failover *cough*)
Vincent van Megen commented
It's now on the first page of suggestions, would like to hear about this from staff? For now I could ask the staff to see if my droplets are on different physical hardware, but would be a lot easier to see it myself.
I agree with this idea and there are one or two others on here regarding the same issue. What's baffling me is the lack of official response to this idea.
Why is there no official response?
Is there an issue with this information being public?
I concur, being a current linode customer (9 years). Trying to find a fail-over cloud provider, but too many missing, yet critical features on DO.
Frederico Araujo commented
This would be a great feature, kinda similar to EC2 availability zones.
Very useful for master/slave replications schemes.
Mark Tooth commented
this would be good. Could be an option when applicable..
don't / do deploy to (same host as dropdown of other droplets in that dc)
the counter is also nice. For example a mysql box and a web-box on the same pysical hw would also be nice. then a backup of each on different hardware.
Estel Smith commented
+3, I like the concept of having multiple "zones" located within the same data center that you can choose to deploy to.
Scott Robertson commented
Or even better, allow them to be in totally different "zones" within the datacenter like vps.net do.