Core Compute Platform

Simply allow providing RISC-V ISA disk images to provide ISA longevity.

There's doesn't seem to be an easy way to determine which user created a droplet either in the UI, DO CLI or via the v2 API. In the UI the creator information is not included in the droplets list or droplet detail view. In the detail view droplet history it does show a Create event but does not show who actioned the event. The only way to work out who created a droplet is to search the Project's activity feed (which can be huge) for the relevant droplet create entry. In the v2 API the droplet resource does not include creator information (but does contain created_at ). There is also no way to fetch a Project's activity feed to cross-reference with the droplet. Request #1 Show the user that created the Droplet in both the droplet list and droplet detail view. Request #2 Provide the user that created the droplet in the droplet resource. Request #3 The first two requests may start feature creep to show creators of other resource types, to avoid this would it be possible to just provide v2 API access to a Project's activity feed?

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

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.

We can resize our droplet by just shutting down it , but it will more exiting if we can resize our droplet without shutting down.

After upgrade droplet OS to the new version, the older version is still listed in the control panel UI. The problem could be resolved in many ways: 1) Do not show the OS version for users at all; 2) Allow the user to write the OS version themselves; 3) Each droplet has a do-agent and a droplet-agent, but why can't they take the OS version and update the control panel UI?

Hi, It would be really nice to be able to add an auto-scale pooler to existing Droplets. I know the current workaround is to take a snapshot of a Droplet, create a new one using that snapshot, and then add an auto-scale pooler to it. But that doesn't work well if you're using third-party software to manage your DigitalOcean account. For example, if you're using Laravel Forge to manage your Laravel app, you can't easily add an auto-scale pooler to the server that's already been provisioned.

The usage graph shows a different timezone whereas we follow GST which makes it difficult for us to analyse the usage graph. Timezone for usage graphs should be configurable

The "Droplet Console" is no such thing. It's a web-based ssh shell interface. When our ssh service went offline this went with it. Consoles have no dependencies on an ssh shell, and thus this should be renamed to "Droplet SSH shell". The "Recovery Console" should be renamed (back) to "Droplet Console", to reflect it's capabilities. While this console is typically only used for emergency system recovery, that does not justify this name. The description of the recovery console, and it's very name, implies that a reboot is necessary to use the recovery console (in linux, "recovery mode" means rebooting into single-user runlevel 1). Nothing in the description implies or explicitly states that the recovery console allows live, virtual-console access to the system (which in fact it does). This naming confusion delayed recovery of our ssh service by hours when a simple ssh service restart was all that was needed (because of an unrelated, temporary memory consumption issue). Our entire server admin team missed the fact that the recovery console was actually a virtual console. Fixing this naming confusion will reduce the number of tickets submitted to the Digital Ocean support team too.