Core Compute Platform

It would be great if we could download a snapshot. I would use snapshot to replicate development environment on my local computer, I believe many others will do the same. Thanks

You can only transfer droplet snapshots to another user. This means you can't keep the same IP and need to setup everything again. Making droplets themselves transferrable would make things simpler.

Creation of cancel button command, to delayed or not response actions in the server.

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.

Recovery ISO currently based on Ubuntu 18.04 and for example the XFS support is lacking - kernel 4.x does not support all the features of kernel 5.x. So in essence it is possible to install a droplet with an os that is not supported by the recovery iso atm. Keep the Recovery ISO in sync with LTS releases, or provide two ISOs, old one as "stable" and automatically updated "latest".

When creating a snapshot all users to write notes with the snapshot. say 4000+ characters so that we can write down ./configure options on the server for that snapshot so when I recompile PHP i can see what was and wasn't enabled on the last/current version.

Set a flag on a resource that will prevent it being accidentally deleted? Specifically we are using Terraform to provision things, and do not want a typo or anything to result in important resources being removed. I know Terraform has a “prevent_destroy” option, but this does not work if somebody accidentally renames the resource for example. It would be ideal if DO could have a flag which would prevent deletion at the service provider level.

At the moment automatic backups are taken 'every few days' (I can't find how many days exactly, but I know it's way too many). I was having the following idea: Users pay 1$ per month to enable automatic backups Depending on their plan, they have a few slots available (you'll unlock additional slots by upgrading to a better plan) You can choose your own interval (twice a day, once a day, once a week) If you run out of slots, the oldest backup will be destroyed automatically to make space for a new backup This way everyone can choose their own interval but everyone will get and pay the same.