downgrade option, not just upgrade
We should have the possibility to also downgrade droplets, not just upgrade. Sometimes we need a lot of power for some operations, but then we don't for some time, or maybe not at all anymore, so it would be nice to be able to downgrade a droplet, not just to upgrade it.
The current solution is to create a new one with a smaller plan, but this means configuring, installing and doing all that stuff which takes time and is not portable.
-
Mircea
- Sep 11 2018
- Will not implement
-
Sep 11, 2018
Admin Response
Hi everyone, There seems to be some confusion in this thread I wanted to clear up: When resizing using our "Flexible" option you are always able to downgrade to your original size. However, when using our permanent resize or creating a new Droplet you will not be able to downgrade to a smaller size. This is because we never shrink the filesystem of a Droplet to prevent the possibility of data corruption. For more information on our Resize feature check out this community tutorial https://www.digitalocean.com/community/tutorials/how-to-resize-your-droplets-on-digitalocean.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- and 1253 more
Related ideas
it's a dumb idea -> create a new droplet, copy files, test, destroy the old one
Attachments Open full size
Just use the minimal one droplet specification and just scale it horizontally.
Attachments Open full size
There is a better way to handle this, versus downgrading a droplet.
Some instances are built without a floating ip since one was not needed to begin with, but they later become needed.
Give us the ability to move ip addresses from one droplet to another. If you cancel a droplet you lose the ip address unless you ordered a floating ip.
Attachments Open full size
The fast-resize down will allow you to resize down to the original size that the droplet was created at, but not lower as that would require shrinking the drive partition.
Thanks
Attachments Open full size
It's not that much hustle to make a backup, boot up a new droplet and select the backup in question, destroy the old one?
Attachments Open full size
@Robin J.
It would have a new IP though, would it not?
Attachments Open full size
If i remember well that was an option in the past but now i see its gone. It was a great option.. i used it to go from 512mb to 1gb then 2gb(ram) and then i downgraded back to 1gb because it was better (my usage was lower) . Please DO do it back.
Attachments Open full size
The correct way to downgrade would be to take a snapshot of your droplet, and boot up a new instance with your snapshot. Shouldn't be anything else to it.
Attachments Open full size
If we could downgrade using the API the same droplet that would be awesome because we could use a script that checks the resources, if there is a spike the script would upgrade the droplet, if spike is gone then the script would downgrade.
We could start big projects on small droplets, once the project grows automatically it will resize the droplet to make sure it has everything it needs.
Attachments Open full size
To downgrade by creating a snapshot and then using it to create a new droplet doesn't make sense either - the IP address will be different, right? That's not a downgrade, that's a new droplet/"host".
Why is it possible to downgrade in my account? Is that because it's a very new account?
Attachments Open full size
yeah.. I agree.. I do upgrade and downgrade depends on usage. can we please get this option?
Attachments Open full size
Even if it was just an button that automated the shutdown - > snapshot -> deletion -> recreation from snapshot with the same IP.
Attachments Open full size
I think part of the issue is that upgrades don't actually change the amount of allocated space you receive, which is incredibly annoying. So downgrading would essentially mean free space.
Attachments Open full size
Currently you need to create a Snapshot, destroy and recreate... I second this.
Attachments Open full size
What there really should be is a "slow resize" option which might take a little longer but allows you to upgrade/downgrade to any size.
That way there are less steps and less frustration when you have to do a real upgrade/downgrade that the fast upgrade option doesn't support.
Attachments Open full size
I wonder why you have to do this twice in step b and c: "create a new droplet from the snapshot image" ?
Attachments Open full size
I agree about downgrade option, as far as it (as upgrade) only touch the CPU and RAM.
Resizing (down) filesystems implies to front with corner cases, file mounts, etc...
Attachments Open full size
I like the idea of being able to downgrade but lets say if i upgraded my hard disk and then downgraded, would i loose data? Also i like the idea of being able to upgrade/downgrade via the api.
Attachments Open full size
Or, how about a way to port a snapshot to a new Droplet (with, perhaps, a warning to the User that this will only work if the Droplets have the same architecture profile.
Attachments Open full size
Addendum to my last comment: The ability to port a snapshot to a new Droplet would, actually, be a great way to transition during a downgrade. The original Droplet could stay live, while the Downgrade Droplet is tested, then change the DNS nameserver records to finalize.
Attachments Open full size