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.
-
Kenn Ejima
- Sep 11 2018
- Future consideration
-
Nov 12, 2018
Admin response
Hey everyone, You can now see which, if any, of your droplets are running on the same hardware by hitting the API. The endpoints are: /v2/droplets/:id/neighbors /v2/reports/droplet_neighbors You can read more about how to leverage this new feature in the API changelog: https://developers.digitalocean.com/changelog/ Thanks again for helping us make DO better! Sam Gimbel Product Manager
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +430
Related ideas
btw this is called anti-afinity
Attachments Open full size
yes please. This whole HA idea doesn't make sense if a rack can goes down with all my droplets in it.
Attachments Open full size
I too need that!
Attachments Open full size
Yes, I would like to have access to such an identifier too.
Attachments Open full size
I really want this too. Then we can really make our developments redundant.
Regards,
S.
Attachments Open full size
That was my comment below. Apologies.
Regards,
S.
Attachments Open full size
+3
Attachments Open full size
+2
I suggested this a few weeks ago. Glad other people think like me.
Attachments Open full size
+2
Attachments Open full size
+3
Or even better, allow them to be in totally different "zones" within the datacenter like vps.net do.
Attachments Open full size
+3, I like the concept of having multiple "zones" located within the same data center that you can choose to deploy to.
Attachments Open full size
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.
Attachments Open full size
+1
Attachments Open full size
This would be a great feature, kinda similar to EC2 availability zones.
Very useful for master/slave replications schemes.
Attachments Open full size
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.
Attachments Open full size
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?
Attachments Open full size
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.
Attachments Open full size
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*)
Attachments Open full size
+1
Attachments Open full size
+1
Attachments Open full size